attaching controllers to plug ins?

[Igloo]

Is there a way to attach hardware controlers (e.g. UC33-e) to plug-ins yet? I have a template where I can control DP's mixer (volume, pan, send) but will MOTU ever develop a way to control Proton, Bassline, etc. or MW eq?

[carrythebanner]

You can control DP's included instruments (Bassline et al.) with NRPNs – check out the DP 5.13 update notes PDF. If you want to use CCs, you can use Reassign Continuous Data MIDI plug-ins to convert CCs to NRPNs.

[TnMike]

I'm trying to record the leslie speed on B4II through automation and can't seem to figure it out. Should I be doing it through MIDI and a hardware controller?

[shergar]

Trying to tweak the cutoff of a Module12 cell using my Evolution MK-425C MIDI controller & I'm struggling.

I am used to assigning normal MIDI controller numbers and that's no problem, with Modula as it learns the controller knobs with an easy control click on whichever parameter I want to play with. All of the other plug ins don't.

The NRPN no for cutoff on Module12 on cell 4 is 417 - how do i program this into my controller keyboard, or should I be using the reassign MIDI data to change the NRPN to a MIDI number?

Generally confused and frustrated by the whole process and this looks like the place to ask - help please.

[Patico]

Hey Shergar,

I am on the same muddy water...I sadly see that nobody has answered your problem.
Did yoi manage to get over it? and how did you do?
I see in the DP manual these NRPNs, but there is no way to use them as such in any assignment templates.
Things that are related are the lsp and msp, but ho do you get tose from the NRPN numbers?
Thanks!

[yoonchul]

Yes I am wondering this as well. I am looking to control model12 in particular. I am looking at getting a controller that transmit nrpn, e.g. microkontrol or axiom. I see the list of nrpn values for individual cell parameters in the addendum but these controllers that transmit nrpn require me to input a msb and lsb number to make up this nrpm value. The reassign continuous data plugin works for me but is not a viable option as I want to be able to control for 8 cells - sample start and end, pitch, and filter value as well as cell volume. This would require 8x5 = 40 plugins and the max inserts on a channel is 20. If no one knows how to break these nrpn numbers down into their msb and lsb constituents, is there a way to daisy chain MIDI tracks before going to the instrument track so that I can have more than 20 MIDI plugin inserts?

on a side note - is there any way to control the buttons for rec enable, mute and solo buttons for a track via MIDI? I looked in the manual but it states that the attach MIDI controller command only works for faders and knobs on the mixer.

Thanks!

[Tonio]

Yes I am wondering this as well. I am looking to control model12 in particular. I am looking at getting a controller that transmit nrpn, e.g. microkontrol or axiom. I see the list of nrpn values for individual cell parameters in the addendum but these controllers that transmit nrpn require me to input a msb and lsb number to make up this nrpm value. The reassign continuous data plugin works for me but is not a viable option as I want to be able to control for 8 cells - sample start and end, pitch, and filter value as well as cell volume. This would require 8x5 = 40 plugins and the max inserts on a channel is 20. If no one knows how to break these nrpn numbers down into their msb and lsb constituents, is there a way to daisy chain MIDI tracks before going to the instrument track so that I can have more than 20 MIDI plugin inserts?

on a side note - is there any way to control the buttons for rec enable, mute and solo buttons for a track via MIDI? I looked in the manual but it states that the attach MIDI controller command only works for faders and knobs on the mixer.

Thanks!

This thread should help you w/ Axiom transport controls.

http://www.motunation.com/forum/viewtop ... =1&t=30997

T

[DJeff]

Novation's Nocturn works fine for all MOTU's and other plugs in DP...

cheers

[Frodo]

Not sure if this helps at all, but--

If you go to Region> Create Continuous Data and choose "Effect Automation", all the available effects will appear under the particular VI name of your choice. VI names and their available automation parameters only appear when the VIs are locked and loaded.

OTOH-- if you are in the SE, and you choose your VI from the INSERT menu, all of the parameters for that instrument will appear-- you make your choice and go from there. Sometimes it's necessary to dot in a starting parameter, otherwise DP might reset itself as if that parameter had never been selected. So, for example, if you have a Model12 locked and loaded in DP6 and are working in the SE-- choose "Instrument: Model12" from the Insert sticky menu. Another window opens with all of Model12's available automation parameters. Pick your parameter and you get a pencil for the cursor. Put in the starting parameter and the pencil changes back to an arrow afterwards. If you click anywhere else in the SE before you've set the starting parameter, the pencil will change back to an arrow and you have to start your automation assignment again.

If, however, you have an audio track with a plugin on an insert, that effect AND it's automation parameters will appear in Region> Create Continuous Data--- Effect Automation. Likewise, that effect and its automation parameters will appear as an option in the SE in the Insert sticky menu.

How to assign those automation parameters to an external controller hingers greatly upon how your controller handles automation setups. Basically, it's a matter of assigning the appropriate controller number to the controller that corresponds with the control parameter you've set up in DP.

Confusing? Redundant? Thoughts?

[BobK]

Novation's Nocturn works fine for all MOTU's and other plugs in DP...

Explain, please. Unless I'm missing something big, this needs some qualification. I got a Nocturn a couple of weeks ago and set up some custom maps. As far as I know, the only knob on the Nocturn you can use to control DP's MAS plug-ins is the Speed Dial, which works on wherever you place the cursor. You CANNOT map any MAS plug-in to the other 8 knobs or 8 buttons on the Nocturn using its Automap Universal software, which only works with AU, VST, RTAS, and TDM plug-ins. You can also use the Nocturn for limited mixing functions in DP, but that's it.

For AU plug-ins that support automation, the Nocturn seems to have potential, but there are some limitations: The Nocturn software automatically imports automation parameters, but it maps them to the hardware controls in the order that the plug-in exports them. The resulting default maps always require considerable tweaking to be useful, because parameters are usually not assigned to the proper type of control; for example, EQ gain or frequency can be mapped to a push-button when it should be assigned to a knob.

The Nocturn's manual incorrectly states that Novation has prepared maps for some commonly-used plug ins; I asked them why I didn't find any of these maps, and they said that in fact the only maps they made are for a few Novation products (and they're not stored in the folder location given in the manual, so don't look for them there!).

Bottom line: be prepared to spend some time tweaking the default controller maps.

The Nocturn's usefulness for controlling plugs via automation depends on how well the developer has implemented automation for a given plug-in. For example, Metric Halo's Channel Strip and Native Instruments' B4II have very thorough implementation, with every parameter automatable. I cleaned up the map for Channel Strip and can now control it entirely from the Nocturn. (Next time I have a mix project, I'll see if having hardware control really makes a difference!) In contrast, Arturia's Minimoog V has pretty poor AU automation implementation: none of the rocker or toggle switches are automatable, and I found that four of the available parameters don't seem to do anything (I'm awaiting for a reply from Arturia about this). Arturia also gave the parameters somewhat cryptic abbreviations, making the mapping process more tedious.

You CAN control every function on the Minimoog V' via the Nocturn's MIDI client, but to me that's not very useful since the plug-in doesn't provide MIDI feedback, with the result that the Nocturn doesn't display parameter values, and the Minimoog's knobs jump to the Nocturn's default values when you touch a knob.

Novation's US tech support guy said that there are potential problems using the Nocturn with Waves plug-ins, and that Waves wasn't very cooperative. However, I had no problems using the Nocturn with Renaissance Comp and Vox (haven't tried the others in that bundle yet). I also got the Nocturn to play well with Scarbee's Vintage Keyboard Effects (VKFX).

[mike_o]

I have made my own custom control templates on the ReMote SL 25 using the NRPN #'s listed in the MOTU PDF update, when the number goes beyond 127, you simply have to subtract 128 as many times as you can and use that # as your MSB, use the remainder as your LSB, as far as I can tell you cannot program the nocturn to use NRPN #'s, only the ReMote SL series can do this through the hardware template editor, not through automap. I use my nocturn with automap in live and my remote SL with a CC#'s template. in DP I disconnect my Nocturn and just use the remote sl as I can jump from the mackie HUI emulation mixer and transport controls to automap to my custom NRPN # templates, which is absolutely aweome, I would recomend forgetting the nocturn for DP and save a little more to get a ReMote SL 25 or a zero unit if you already have a keyboard.


hope this helps. as in nrpn # 128 would be msb 1, lsb 0, 256 would be msb 1 lsb 127,

MSB=most significant byte, thats your bank cout
LSB=least significant byte, thats your parameter #

I hope this helps everyone.

model 12 nrpn # 417 would be msb 3 lsb 33, 417 - 128 = 289, 289 - 128=161, 161-128 = 33, as in #417 can have 128 subtracted 3 times before you get a # leftover smaller than 128, thats your bank count(MSB) the remaining #(less than 128) is your controller(LSB) # for that bank, you are basically counting up your banks of 128, then finding the actual nrpn # for that bank from the remainder.

only the dp VI's have NRPN #'s, the MW EQ and other utility and FX plugs do not have them.

I am actually in Ireland visiting family right now, but when I get home in a few days I will post my remote sl templates for the Modulo, Basslin, Proton, Polysynth, nanosampler and MX4 V.2, I still need to make the time to create a model 12 templates set, when I do I will upload it.

[yoonchul]

Thank you Mike for understanding what I was asking and for such a detailed response! I'm gonna have to create an excel spreadsheet for the calculations but I'm psyched to have this info.

[mike_o]

if you get the msb and lsb #'s for the model 12 all laid out, could you post them?, save me the math.

[DJeff]

Hey BobK sorry for the late reply due to christmas vacation... Actually you're right, Nocturn does not work with MOTU plugs... I use it a lot in Ableton and Taktor... It works with my Ohmforce plugs in DP, but I don't use it as extensively as I do in Ableton...

cheers

[yoonchul]

if you get the msb and lsb #'s for the model 12 all laid out, could you post them?, save me the math.

Yes of course - I'm in the process of getting a controller that I lent out back because I realized it has the ability to transmit nrpn. Once I have the numbers and have tested them, I'll post them for you.