Cubase 13 MIDI Remote

Ha ha, I’ve been away for a couple of days and I see that my OP has grown arms and legs. They should probably be new posts to avoid confusion, folks…

So, this is where I have become stuck: everything has been assigned correctly, but when I change track, my recently assigned parameters have suddenly changed to some hidden defaults, but hidden where? In Mixface (my controller), in MIDI Remote? Seemingly not in the RCE as it still displays my new assignments… hmmm, something somewhere is sneakily resetting things… I will investigate further, if I can be arsed… or maybe I’ll just make some music instead!

1 Like

The only thing that comes to mind is that there are plugins that manage their automation parameters internally. When using presets, some presets may or may not load their own automation management states. Moreover, there might or might not be an option (from within the plug-in) to bypass this behaviour, so that you always use the same automation “template”, let’s call it.

So, if you’re sure that all MIDI remote stuff has been set up correctly, maybe it’s time that you post some screenshots, of specific plug-ins and specific circumstances that this happens.

Or better yet, do a test with stock Cubase instruments like Padshops and Retrologues, and switch between tracks of those so that you are sure that the MIDI remote assignment/RCE synergy definitely works 100%.

Thanks gg, that’s a very good idea - I’ll get onto it at the weekend. Much appreciated.

Good morning, ggmanestraki, let me tell you what I’ve found as it’s still not working:

I created an instance of Padshop and an instance of Retrologue on respective tracks. I went through the assignment process, using the mapping assistant (MA) and the remote control editor (RCE). I assigned 8 random knobs on Padshop first and all was well. I then went and assigned 8 random knobs in Retrologue (in other words, not the built-in default assignments). This worked well, so I rebooted. Now Retrologue still behaved itself, but Padshop was back to some built-in defaults; when I reassigned everything to Padshop again, then Retrologue lost my assignments. I then noticed in Options on the plugins a ‘Save MIDI controller as default’ option which I clicked on each plugin after going through the whole process again, but it made no difference.
During this time the RCE editor always kept my new assignments; it’s the plugins that are over-riding them, or at least the first one assigned in each case… or it could be the MA that is doing it, but more likely the former.
In this process, I also have to click ‘Selected Track’ in the MA Focus Mode at the bottom, otherwise there is no change of plugins as I change track… this is reflected in the MA listing: it only changes of this focus mode is selected, which does make sense.
So there is a very stubborn overwriting of my assignments coming from the plugins, I believe… and these are Steinberg’s own, so I really have no idea. I’ve spent hours and hours on this and it’s very frustrating; I keep hoping - and expecting - it to suddenly work when I hit on the magic sequence of operations, but so far nothing. Oh well… perhaps there is still something left to try?
I should add that I’m not convinced about the RCE’s part in all this. It keeps displaying the correct assignments but doesn’t seem to have overall control of things; the mapping assistant and plugin itself seem to be in cahoots!

As @ggmanestraki suggested, it would be good to send a screenshot of your assignments in the mapping assistant window. Is its “Mappings” section exactly the same as the one I’ve attached in a previous post?

1 Like

AHA!!! I have it working now and it’s to do with me reassigning the track parameters at the end so that each line in the mapping assistant reads only ‘Parameter 1/Parameters/Instrument/Selected Track’ etc., and NOT the actual individual knob assignments… I will go through the process again making notes and try to recreate what works in as few steps as possible, now that I have a better understanding and I’ll send screenshots - how do I do that btw?

1 Like

Interestingly, when I switch between tracks now, with everything behaving as it should (yay!), the entries in the Mapping Assistant are completely blank!? How odd, but if it works, who am I to question the strange logic of the thing…

Unbelievable! I’ve created a third VST track, not a Steinberg instrument, and I have that working now, too… everything behaving itself; what an f’ing relief! I’m going to try again missing out the RCE stage as it might not be needed, we’ll see… meantime if someone can tell me how to add screenshots I will give a comprehensive breakdown on how I got it working. Just hoping it doesn’t now resort to it’s old tricks! But, definitely, the mapping assistant list has to only show the list of Parameters and not the actual knob assignments - don’t know why it went blank earlier, but now it simply doesn’t change from track to track, but the knob assignments thankfully do. I am nothing if not persistent! And I thank you all for being equally so.

Amazing… and so simple… the RCE is needed and the Parameters are assigned last… who’d have thunk it… can’t quite believe it… totally behaving itself like a well-disciplined child LOL…

1 Like

Good to know John. Here is a now needless video that I quickly put together. It’s not a tutorial, it’s just 3 minutes of me creating a new MIDI remote and doing the assignments.

The only thing left for the user would be to go into RCEs and refine their workflow. Move around parameters so that they have Distortion on knob no.1 instead of knob no. 14 for example.

Edit: This method of going into RCEs and deciding on a layout is suitable for a mostly permanent setup. If one wants to always control Cutoff from the first knob as long as the instrument is loaded and selected, this is the way.

But if someone wants the first knob to control Cutoff for this sound, but control Release for the next sound, and maybe Resonance for the next sound (we’re always talking about the same instrument), then I believe Quick Controls are better suited to that workflow instead.

1 Like

Thanks gg, I’ll watch your video later and see how it compares to the method that I will shortly detail for anyone interested - so how DO you add screenshots and video content??

You just drag the screenshot from the desktop to the window where you type your reply, or you can also Copy (Ctrl+C) the screenshot and Paste it (Ctrl+V) to a specific place


in your reply. The same goes with videos, but there is a size limit of 4MB, so it would be more convenient to again paste links to videos uploaded elsewhere (youtube for example)

I would go with the Track Quick Controls in this case :slight_smile:

EDIT: Since this is not supported in the MR, Focused Quick Controls would be a choice, and then editing the track quick controls.

1 Like

Thanks… I’ll get onto it soon.

RIGHT…Here goes how I’ve got MIDI Remote (MR) and my clever little Studiologic Mixface and the rather retro looking Remote Control Editor (RCE) to all work in harmony to produce the most satisfying and fully working knob concerto that I didn’t ever imagine was lurking in Cubase…!!

This is going to be HUGE, by the way, but I’ll do my best to be CLEAR…

So, for anyone new, there are instructions or links to videos earlier in this post from ggmanestraki on how to set your particular controller up with the correct number of Parameters on the right-hand pane of the MIDI Remote Mapping Assistant (MA) which relate to the knobs on the Remote Control Editor, available on each VST plugin by right-clicking near the top of the GUI. I chose, for test purposes, just to choose 8 parameters and 8 corresponding knobs on the RCE and my controller. With the RCE I deleted all previous entries and excess pages, so here it is with the Learn function activated and the first slot selected:

And here’s what the Mapping Assistant left-hand page looks like with the list of Parameters on the right-hand pane assigned to knobs on my controller:

And heres my MIDI Remote set up for my Mixface, with 8 knobs assigned (and a button for opening instrument edit). Oh yes, and I’ve also created two Instrument Tracks, one for Padshop and one for Retrologue:

Now that I’ve assigned these 8 Parameters as described in gg’s link, they are now set up for any new project, it seems, so for the demo I’m describing I didn’t have to go through that stage again - very handy indeed.

NOW THERE ARE JUST TWO SIMPLE STAGES TO COMPLETION.

STAGE 1 - Assigning the plugin knobs to your physical controller using the RCE and MIDI Remote Mapping Assistant.

  1. Open MIDI Remote in Edit mode and open the Mapping Assistant, if not already open. Note it may not be necessary to be in edit mode as long as the MA page is open.

  2. Have your first track selected and open the instrument edit so that you can see your plugin’s GUI, then right click near the top and open the RCE from the drop-down menu.

  1. Within the RCE, clear any existing assignments by clicking the button two to the left of the Learn button then select the first empty slot. Remember to have it in Learn Mode - see top right of RCE. See first screenshot above. Also, you can delete any unwanted pages, but it doesn’t really matter; I’ve just done it for clarity.

  2. Move your first physical knob on your controller (in my case Mixface).
    This will populate the left-hand box at the top of the MA page like so:

Screenshot 2024-10-05 at 21.45.09

Ignore the fact that in my case it’s labelled CH 1 Osc as that’s from a previous assignment. Yours should probably read Parameter 1.

  1. Move a knob or slider on your VST plugin (Padshop in this case) that you want assigned to Knob 1 on your controller. This will then populate the right-hand box above:

Screenshot 2024-10-05 at 21.58.59

YOU MAY HAVE TO DO THIS MORE THAN ONCE BEFORE IT ‘TAKES’

  1. Now click on Apply Mapping. If you come out of MIDI Remote edit mode and turn the first knob on your controller you should see both the MIDI Remote first knob moving and the RCE first knob moving, along with the correct VST plugin assigned knob or slider - so far so good. After checking, put the MIDI Remote back into edit mode - actually, this may not be necessary as long as the Mapping Assistant is still open.

NOW REPEAT THE ABOVE PROCESS FOR THE NUMBER OF PARAMETERS THAT YOU ASSIGNED AT THE BEGINNING (in my case, eight). Make sure the RCE stays in Learn Mode and at the end of the whole process, click the Apply button on the RCE, two to the right of the Learn button.
YOU CAN NOW CLOSE THE REMOTE CONTROL EDITOR. The Mapping Assistant page should now list all the assignments you just made:

STAGE 2: Re-assigning the Parameters on the Selected Track/Instrument/Parameters/Actions Parameters 1-8 (or how many you have previously assigned). This is in the Function Browser pane to the right of the mapping assistant, which you should already be familiar with: note the path is Selected Track/Instrument/Parameters/(Setup)/Actions/ Parameters 1… however many you need.

This is where I previously got stuck: you have to go back and reassign the parameters as explained below or it just won’t work.

  1. Select the first Parameter on the right-hand panel as I just described above.

  2. Move the corresponding knob on your hardware controller - you should see the VST plugin assigned knob moving and also the associated knob on the RCE if it’s still open.

  3. Hit ‘Apply Mapping’ again on the Mapping Assistant. This will change the entry in the list below and remove the wording of your assignment, i.e. Filter Cutoff or whatever and replace it with what you see below (in my case after all 8 were done):

THIS IS CRUCIAL. All the listings must read as above and not show the actual names of the assignments. This took me days to suss out, folks!

YOU CAN NOW MOVE ON TO THE NEXT TRACK AND DO EXACTLY THE SAME.

And now - ta da! - when you change tracks, your knob assignments will change too, to the ones assigned to the instrument on that track. Pretty f’ing genius, I think, but it took some figuring. Thanks to all those above who helped, particularly ggmanestraki, and although I feel I’ve added valuable new input here, apologies if it was already described this way earlier in my post and I just didn’t follow it right!

Byeee!

1 Like

Seems like you got it, except for the middle part, which is what was probably throwing you off. Let me explain:

This is backpedaling. If you notice in your screenshot

you have a “P” next to each assignment. What this means is that no matter what you’ve selected, no matter where you are in the project, knob 8 will select Layer A’s Grain Stereo Width for Padshop 01 (This, specific Padshop, it won’t work for another one two tracks down for example). It’s a direct assignment.

What is the use for this method? Let’s say you have 2 instruments in your project. And you have them playing together. Instrument 1 is a drum machine, instrument 2 is a synth. For whatever reason, you decide that you want knob 1 to control the drum machine’s Swing, knob 2 the drum machine’s pitch, knob 3 its double/half time. Knob 4 you want to control the synth’s cutoff, knob 5 the synth’s resonance, knob 6 the synth’s reverb.

The best way to do this would be as you have done. In the Mapping Assistant, click on knob 1, in the drum machine’s GUI click on the swing knob, Apply Mapping. This would lock the controls in place, and you would always have them so, for this project.

On the other hand, if at step 3 of the first Stage:

you just moved the parameters around, or rebuilt them from scratch - doesn’t matter -, you would be done and ready right there and then. Because the initial setup:

was for any parameter for the Selected Track. You don’t need to go in the mapping assistant at all once you’ve set this up like that.

Let me give you an example:

Let’s say that tomorrow you buy a new instrument. If you keep things as they are in the picture above, once you load that instrument and start turning knobs, you will see things moving in the instrument’s GUI. Now, here’s the crucial part.

Let’s say it’s all wrong. You don’t like what is being controlled by which knob, AT ALL. What do you do?

You get in the instrument’s RCE, and start moving things around, or erasing it all and doing it again. In the first cell, top left, you assign what knob 1 is supposed to control. In the second cell, you assign what knob 2 is supposed to control, etc etc…

If you don’t wan’t to dive in the list of parameters on the left, use learn mode instead. RCE’s learn mode that is, the little L on the top. How does it work? You click once on the cell you’re interested in populating, and you click once more on the actual control in the instrument’s GUI.

And that’s it! No need to touch anything else! You do that once for each plug-in (or more if you have second thoughts about what’s the ideal layout.)

I didn’t want to write so much, but I did out of fear that you would be spending twice the time needed otherwise, and eventually wreck your nerves.

Thanks gg, but I tried what you suggested and it didn’t work for me, presumably because we’ve devoloped a different way of working, or because it’s 6 o’clock on a Sunday morning; I still needed the final stage of reassigning the parameters. My procedure works 100% for my work flow for now, but I’ll check back to your notes in the future if necessary, as I am a newbie with this aspect of Cubase, whereas you seem to have been using the RCE quite extensively. Btw I am very happy with repetitive processes and appreciate your concerns for my nerves, but I’m doing okay!

I am just very pleased to have got what wasn’t working, working, and I’m not even sure how much I’ll use it… now onto assigning my expression pedal to respond differently to different track VSTs!

Now that I have everything set up, I can indeed just use the RCE to make changes using its Learn and Apply functions. My method is just a bit different, it seems: even with everything set to G for Global, I still need that final stage to get the track changes working.

I think the truth is that I find it hard to get inside someone elses head and have to figure things out my own way!

This particular thing we’re discussing is not hard eventually, not at all, but it’s a huge headscratcher until it all clicks together.

If you remember the very start of this thread, the whole point was to design things in such a way that you have just ONE page for any instrument. This one page is the last picture posted two posts above.

Parameter 1 for the instument on the selected track
Parameter 2 for the instrument on the selected track
Etc
Etc

That’s it. It’s intentionally vague, and amounts to the full work needed for the MIDI remote.

But moving on, the “WTF is parameter 1 for Sylenth?”, which is what interests us in the end after all, is the only job of the RCE. It defines what parameter 1 is, and allows you to change what parameter 1 is if you like.

Tweak away in the RCE, don’t mess with the Mapping Assistant anymore is what I suggest. (If the page is reading “G” Parameter x (Parameters|Instrument|Selected Track) that is)

Thanks, but I think I’m good now… all working, including my expression pedal which changes assignment for each track/VST… let’s enjoy making music now! :smiley:

1 Like