The last update about the MIDI Remote selected track situation with Cubase on Windows was roughly 4 months ago. The last thing said on the subject was that the ball was in Steinberg’s court to fix it, and they aren’t answering emails. Is that still the case? Are Windows users just doomed to have broken functionality? I am a part of the Cubase 15 Beta. Maybe if I had more information about what the exact problem was, I could push the issue a little harder on their end and bring it to their attention.
3 Likes
I´m also interested in the actual status !
We got dead silence from Steinberg - we pinged them several times - neither PM nor any other stuff got back to us. It is very frustrating for us - but that’s the way it is. We can’t do anything more on our side - our controller is scripted correctly per their specs.
1 Like
This is so disheartening. Thank you for sharing. It was the feature I was looking forward to the most. Hopefully Steinberg pulls their heads out of their *sses and fix it. I can’t imagine Metagrid is the only platform that this issue affects.
It looks like Steinberg bit off more than they can chew with the MIDI Remote. Their forum is full of threads on the topic with zero response from the moderators.
I searched the forum, but can’t actually find a thread that outlines the issues you guys are facing. I have eight huge MIDI Remotes set up with hundreds of grids and everything updates and works flawlessly here in Cubase on Windows. All my plugin grids update to reflect the current state of the open plugin on the selected track as well as the fader positions, solo/mute/sends and transport.
I’m very envious. Windows 11 latest version? CPU? Wifi or USB? I must know how you have it working so well. I’ve tried everything.
We are specifically talking about faders, plugins, and inserts dynamically filling in names. For instance with Quick Controls - On my QC Fader Grid, the parameter names should fill in automatically depending on which track is selected. Instead, 2 or 3 of them fill in correctly and the rest stay blank. The blank ones do not function as a fader at all, so at any given time 3-6 of my faders are just flat out broken.
Windows latest 
CPU - i7 13700KF
USB
To clarify, I have dedicated grids for specific plugins. I am not using the QC dynamic names feature i.e. if I have e.g. a compressor on a track, I manually open my ‘Compressor’ grid (which has every parameter covered - I am not restricted to 8 QC’s 
. Then when I open that plugin via Cubase’s ‘View Insert’ function, as long as the plugin’s Focus Quick Controls Indicator (little blue square) is lit, my grid updates.
If you need any assistance, don’t hesitate to ask me any questions you may have.
Here is my Imager grid as an example.
1 Like
@JTB - your setup is massive and so impressive!
Your setup seems great! I understand that you’re not limited to 8 quick controls but so how are your grids linked to the focus quick control section to automatically update?
Very impressive! Although it doesn’t seem you experience the issue in question since you don’t use that feature. You’ve definitely inspired me not to let it hold me back! It just sounds like a ton of upkeep. Having a dedicated grid for every library and plugin I own sounds like a lot of time setting up and not writing music (to me) 
I use the Remote Control Editor (RCE) in Cubase.
I am using the ‘Parameter’ under ‘Selected Track’ in the Mapping Assistant, not the Focus Quick Controls.
Create as many faders as you think you may need. Maybe start with 50. Then assign them to these parameters (see below). This is only displaying 8 available parameters, so click the ‘===Setup===’ below ‘Parameters’ and type in 128 (max amount per bank) and hit enter.
Now when you have a track selected and a plugin in focus (little blue square -top right) your fader’s names on the MIDI Remote controller surface will update. Now just pick the parameter you want to control with MGP, create a fader in MGP and match the channel and CC number. BOOM!!
Yeah, but once you have it down it’s a pretty quick (and fun) process actually. And I will get those couple of hours back no doubt through not having to click.
What do you plan to do when the Generic Remote inevitably goes away?
I don’t use the GR. Everything has been redone in the MIDI Remote. Painful, but now I don’t have the Generic Remote’s EOL hanging over my head.
I see. I confused the Generic Remote with the Remote Control Editor! Very cool. May have to consider going this route.
1 Like