I’m running into a MIDI Remote behavior that I’m trying to understand, and I’m hoping someone can confirm whether this is expected behavior or if I’m missing a step.
Setup
Cubase 15 Elements
AKAI MIDIMIX Pro
MIDI Remote (not Generic Remote)
Plugins mapped via MIDI Remote (example: PA bx_console SSL 4000 E)
I successfully created a MIDI Remote mapping page for the bx_console SSL 4000 E and others. The mapping works perfectly when the plugin is inserted in Insert Slot 1 on a track (where I created the mappings).
The problem is, as soon as I insert the same plugin into Insert Slot 2 (or any other slot) on the same track, the MIDI Remote mappings show up as “missing” and the controller no longer controls the plugin.
I do notice that the Cubase Function shows up as “Control (plugin | 1 | Inserts | Selected Track)” I guess that means Insert Slot 1.
Does this mean that plugin mappings in MIDI Remote are inherently slot-dependent? Is there a way to make plugin mappings follow the focused plugin window, regardless of which insert slot the plugin is in? Do I have to create a Mapping Page for every plugin I use for each Insert Slot???
Is this just a limitation of the MIDI Remote feature in Cubase 15, or am I approaching plugin mapping the wrong way? I don’t want to be limited to 8 Quick Controls. Mapping out a plugin like a Console is a bit of a game changer, being able to control the entire plugin in a logical fashion with real knobs, buttons, and sliders.
Thanks - Rick
Here are screen shots of my mapping and project setup.
Yes, the plugin must be on the same slot on every channel. Simply place the all chanelstrip plugins in the same slot. Then you can change channels and adjust parameters in the plugin only with the controller. You don’t have to use a mouse and keyboard.
That’s a bummer. I guess I need to decide where every plugin that I want to use the MIDIMIX on is going to live in my inserts or build a map for multiple insert slots.
I’m not super familiar with the Mapping Assistant since I write my scripts with the API plus I also have a different Cubase version than you. But basically you should look for this function to bind your controller to:
In addition, there should be a setting somewhere to follow plugin window in focus. I don’t know where that is for the mapping assistant. The API has the function .followPluginWindowInFocus() so I’m assuming there’s something similar for using the mapping assistant.
Writing your own JavaScript using the MR API opens up some more customization compared to the mapping assistant, but it can be time consuming and the learning curve is a bit steep. Especially if you do not have experience writing JS.
That said, having your controller follow the insert plugin in focus should be possible by only using the mapping assistant.
