I can’t answer why the universe is the way it is.
But until Steinberg makes it easier with a re-architected remote control API (which apparently they’re working on), I’m using the following workaround, which is quirky, but seems to work:
Make a Generic Remote for each desired hardware controllers
– (I know you can’t give them custom names, but I won’t let that stop me)
In each Generic Remote, configure 8 or 16 controls for use as one or both of
– VST Quick Controls
– Track Quick Controls
Use the upper part of the window to midi learn the controls you’re flying in from that hardware controller.
Use the lower part of the window to assign what Cubase is supposed to do with them
VST Quick Controls can be targeted via
VST Quick Controls | Device | Quick Control 1
VST Quick Controls | Device | Quick Control 2
VST Quick Controls | Device | Quick Control 7
VST Quick Controls | Device | Quick Control 8
Track Quick Controls is a lot less obvious but this worked for me:
- Select an Audio or Instrument track in your project which has all 8 Track Quick Controls assigned (doesn’t matter what they are assigned to, but they have to be assigned to something),
- then, in the Generic Remote settings, you should be able to find and configure the following:
Mixer | Selected | Quick Controls > QuickControl1
Mixer | Selected | Quick Controls > QuickControl2
Mixer | Selected | Quick Controls > QuickControl7
Mixer | Selected | Quick Controls > QuickControl8
The result on my setup looks like this:
NOTE, that bottom half shows whatever the Track Quick Controls are on the currently selected track - (very confusing indeed) - but it works. Like when you have a different track selected and go back into the Generic Remote settings, that window shows different things in the Value/Action column.
This kind of setup allows me to have several different controllers simultaneously connected to Quick Controls.
Important undocumented trap (no error message if done wrong): When setting up Generic Remotes configurations: The Control Names have to be unique within a Generic Remote configuration, since they serve as the key linking the top and bottom half (mapping the hardware remote and the Cubase software connections respectively).