Multiple Hardware Controller Templates vs MIDI Remote - tips on how to manage?

Cubase
1

Just getting into MR for the first time right now,

I have 32 Templates on my Novation 25SL MKII that I have setup for various purposes in my studio - different control schemes of hardware synth, split controls, etc.

What is the best way of integrated/communicating all 32 templates into MR? Do I have to create a MR for each template? and is there a method of template control, where if I switch templates, MR switches schemes?

edit

The 25SL MKII I believe doesn’t send any data when a Template is changed internally, but it can receive Template changes via program change messages.

Is it possible to create one MIDI Remote for the 25SL MKII, but have multiple templates with program changes sent to the 25SL? There doesn’t seem to be a UI way of doing this, can it be done via script?

And also, the Novation SLMKII has multiple inputs/outputs, it has 3 virtual USB MIDI Ports, and then two physical MIDI Din outputs… I use the two physical outputs for different signal splits to different synths, parameter linking, etc. And then I use the USB for more utility/data control like PLE Script triggering.

I had this setup and working with Generic Remote… Anything I need to be concerned with going forward with MR?

Just looking for general pointers/possibilities so I don’t waste my time pursuing something that isn’t possible/functioning properly.

Thankfully, GR is still implemented so I can fall back on it. calling @m.c

2

I had a quick look at the manual and programmer’s guide for this controller.
From what I see, we can send cc/sysex from the daw in order to update displays/buttons/pots. This is great.

There is a crucial part here. Do you have distinct cc messages per control per template? If yes, then in MR we can define layer zones using scripting. With layer zones, we can have the very same button (as an element with x,y coords) but with different cc message per layer. Then, we can bind host values or commands to whichever control/layer. The cool thing here is that after defining the layers using scripting, we can do the binding using the mapping assistant, no further scripting is required.

MR doesn’t receive messages for template switching. However it does something very good. When you change template on your controller, and alter a control, MR will recognize the midi message and set its UI to the layer containing this midi message.

Here, let me show you a tiny remote with just one button, two layers, just to have a quick look at the concept.
This is layer 1, where I’ve bound the control to the Mute property of the selected track:

εικόνα
εικόνα417×444 9.16 KB

And here’s the second layer, with the same control (as seen on our surface but with different CC message) bound to Solo:

εικόνα
εικόνα402×440 9.39 KB

You can see the labels showing the zone at the bottom of the surface. We can click there when we want to see what we have bound to different zones and of course edit our binding. Then, when working with the remote, it will refresh based on the midi message sent from our controller.

There are things doable in the Generic Remote, which are not directly doable using the mapping assistant, when it comes to feedback. Example: Say we need to turn a led on/off when the punch In state changes. This is not currently covered directly. We should script it. On the bright side, MR provides great feedback options, and from what I see, the SL MK2 exposes the sysex messages needed for this.

Honestly, if you’re covered with the GR and don’t have much needs for visual feedback, I don’t really see a reason to move to MR. The key here is “covered”. If you feel you want feedback and/or adding more complicated stuff (example, button presses+knobs turn) yeah, you should definitely give MR a try and see.

3

Thanks for this, good info.