Thankyou for your reply, i didnt realise about mapping pages.
Does anyone know of where i can find what list of CC numbers are used by the launchkey by default so i dont duplicate any?
Ive had to make my own script to use the custom modes which is controlled using midi ports where as the built in script for the launchkey uses the midi controller port so is this a different language to normal midi? or does this mean i can interfere with the messages from the built in script with my own if i ended up using the same CC numbers on both scripts?
Plus i dont want to be sending cc messages and inadvertally altering something else that cubase might already have assigned. Is there somewhere in cubase that i can find what cc numbers are already assigned to things such as mod wheel as an example?
No, itās just a different port. So in regards to what is unique, itās a combination of the Port, Channel and MIDI CC#, as each MIDI Remote script is defined by the port used.
i.e. these are all different:
Port: Launchkey1 | Channel: 1 | CC:100
Port: Launchkey1 | Channel: 2 | CC:100
Port: Launchkey2 | Channel: 2 | CC:100
The MIDI Remote will stop the controls youāve assigned from going into the sequencer area, so you donāt need to worry about that.
The only concern is if you ever wanted to control plugins by specific CC values and you DO want them to filter to the main sequencer/timelineā¦
But to be honest, youāre better to use automation for plugin control than MIDI CC - thatās kinda the point of the MIDI Remote. The main instance where MIDI CC control of plugins is advantageous in Cubase is if youāre using a MIDI LFO tool to automatically modulate a plugin parameter. Or some plugins just donāt offer VST automation IDās for their controls so youāre forced to go that route.
Personally, the safest options for MIDI CC assignments outside of the standard definitions are
the ranges CC 20-31 and CC 102-119. Many controllers ship with CC70ā¦ onwards mapped, but these are widely used for instrument parameters. I tend to go from CC20 for rotaries and then CC102ā¦ for buttons or faders.
I donāt know if that helps, or confuses you more!
Hi, I donāt know what I am doing wrong. but when I map my rotary controls (Novation Zero SL MkII) to the parameters
they do not necessarily map to the most useful parameters within the plugin. Without working out what each parameter does and selecting the ones I want is there any way of redefining which parameter does which?
Any other unrelated question regards the
I have only seen the focus field greyed-out. Do you know what would change that?
Thanks for your posts.
With @skijumptoes permission, Iāll add another small, but hopefully useful detail.
When we decide upon huge parameter banks for plug-ins, e.g. 32 parameters, upon first glance performance is abysmal. Knobs turn together following other knobs on their own, and performance is horrible. Of course, this happens because ofā¦ Remote Control Editor (RCE), or rather, how plug-in parameters are passed to the MIDI remote.
If we donāt touch anything and just roll with the defaults, thereās a high probability that a 8 parameter plug-in will just duplicate the parameters over and over until it reaches the MIDI remoteās parameter bank size.
However.
If we open the RCE for our plug-in, create as many pages are needed to reach 32 parameters (our MIDI remoteās bank size), and then assign just those parameters that the plug-in offers (Just 2 parameters? Assign those, leave the 30 rest controls empty. 64? Create more pages to fit them all, and weāll just bank parameters from the MIDI remote.), we immediately see that performance is stellar!
Not trying to teach grannies to suck eggs, but I often completely forget about the RCE, and blame the Remote when itās not at fault actually. Maybe others are like me a bit and do the same mistake.
By the way, how annoying is it trying to get the RCE to show for the channel strip plug-ins? The controls are so tightly packed that I need to pixel hunt for free space to right click!
Yeah, it gets in a loop almost that when you touch one parameter it echos it out to the other duplicate params. You definitely need to create new pages and create some blanks.
The other annoyance is if you use multiple devices, youāre kinda stuck to the order of RCE - I arrange in blocks of 8, so if you use something a little quirky such as a 5 or 6 rotary controller, or 9 fader controller - you kinda have to adhere to the global RCE set, which in my case is blocks of 8.
I hope there is a better solution in future, maybe to embrace the RCE more and start to work on improving it? i.e. get access via the MIDI Remote mapping assistant in a newer/nicer method.
And perhaps have āglobalā RCE maps, and ādevice specificā ones for those that want a different mapping per MIDI Remote device, there could just be an RCE selection within the ===setup=== dialog, for example.
That said, MIDI 2.0 will most likely supersede a lot of this. I just hope SB are ahead of the curve and weāre not having to dismantle what weāre building today.
Always been a pain, MCU wasnāt too bad if you wanted quick access as it had āCStripā mode. I tend to have a page within MIDI Remote for channel strip elements and use itās native mappings, just much easier to work with.
Just thinking though, can you go to generic view on the channel strip items (where it lists the parameters) - I canāt remember(?).
Although, It does mean that a basic mapping has about 5 pages minimum now:
1-Mixer page - For volumes
2-Quick Control Page - For Focus quick controls
3-Selected Track Instrument page - For multi-parameter/multi page instrument mappings
4-Selected Track Insert Page - As above, for inserts
5-Channel strip page - For pre-gain, Low/Hi cut filters etc.
I mean, itās pretty clumsy as pages 2,3 and 4 should just be under one page really. But after all these years iām just thankful that we have native options, and a lot more is within our control, even if itās quite a heavy process to understand and optimise as best as possible.
Using a controller with a display makes the whole āWhat f----ing page am I on?ā moments a little easier too!
True! You have to make compromises, or plan ahead that plug-in A will be controlled by hardware device A, so it gets RCE setup A, while plug-in B will be controlled by hardware device B, so it gets RCE setup B.
My thoughts exactly.
I donāt think so! Plus, some strip plug-ins are worse than others on this particular aspect. But itās just a small inconvenience. (For quite a while, it didnāt occur to me that the RCE was available for those Channel Strip plug-ins, since I had +never+ right clicked in empty space up to that point. The first time I did was a revelation! )
Agreed. Itās also the shape of the controller that plays a huge part. For example, if you have just 4 pots and 4 buttons, you can still build a fairly quick EQ section, where you assign Freq, Gain, Q, Type to knobs, and 4 page changes to the buttons, each one leading to a direct EQ band. (Press button 1, tweak lows, press 4, tweak highs etcā¦ Using/changing between 4 pages, of course.)
The main problem I have with this exceptionally modular nature of MIDI remote is exactly āpage-tisā, where Iām churning out pages like mad, āin case I need themā. Selected Channelās Sends 1-8 on faders? Check! Flipped Sends Mixer, to control 1 send at a time for all channels? Itās just 8 pages more. Check! And then itās a puzzle of how to make an intuitive ācall-center options menuā to have all these available at any time, which falls into DAW controller designer territory (Iām really curious to see what type of controller Steinberg will come up with when they do!)
But, Iām really happy to have this pleasant headache. The Remote is fast. Personally, I find it suits me more than the Generic, in the sense that assignments are easier, building is easier and faster, I spend less time from thought to implementation. Ok, some stuff is not there yet, but they will be in time.
Regarding Quick Controls.
I donāt know how you guys are using them, but I find I donāt have a use for them before I do. I just have them assigned there, and when I see that Iām reaching for a specific parameter too often, I just plop them there for the track so that I donāt have to go remote diving each time I want to control it. For example, I might assign a drum plug-inās dynamics to control them after having recorded them, during playback. Or a particular kit pieceās tuning. Or a delayās mix knob to control it live. Theyāre just sitting there until the need arises, I canāt bring myself to think of static QC assignments for a track, or plug-ins. Iād rather have a solid RCE setup and control the parameters directly.
It would be interesting to discuss just workflows of the MIDI remote, and see how people expect it to work, how we are currently using it, what the advantages and disadvantages of each workflow are. We would all learn much I think!
No worries, my fridge is full of eggs. I have had some success with mapping the RCE to a plugin. I have 16 rotaries so I defined 16 parameters in the MIDI Remote editor. I then opened a delay plugin and the RCE page loaded the default from the plugin. I then dragged them around until they were where I wanted them, (I had no success using the Learn function and selecting the control and then the parameter from the drop down list, the designation did not change) however, I made an error and deleted one of the parameters that I required. Obviously once you have accepted the changes the Default becomes what you accept (in my case, not what I want). Do you (a) know how to solve this? (b)where the parameter files are stored? and (c) how do you save these as separate banks? I may have got the wrong end of the stick with how this works, so any help would be appreciated.
If you want to make an occupied cell blank, select the cell and then choose no parameter from the field on the left. The same goes if you want to assign a parameter thatās not there already in the factory default.
Unless itās a completely different disaster. In that case, please send screenshots!
You can get to the parameter files, as I tried to see if you could share with users and sure enough you can. i.e.:
I wouldnāt mess about with them too much though, best to stick to the GUI I thinkā¦ However, I would be cool if ever got to the point of sharing RCE presets.
Further to my reply re third party plugins whose parameters canāt be retrieved from the pick list if accidentally deleted, There is no issues with the Steinberg native plugins, but the Plugin Alliance plugs do exhibit this issue. However, the SSL Native plugins seem fine. Iāll add other compliant third party plugs as I find them. To avoid these issues, I open enough new rows to accommodate all the parameters I need and then delete the original rows when Iām happy itās correct.
So, when you click restore to factory settings those plug-ins stay blank? But all their parameters are still there for assignment in the list on the left, arenāt they?
Use control+drag to swap parameters around, instead of overwriting them, or dragging them to empty cells first. I find it goes faster for me this way.
)
