We’re thrilled to announce that we’ve started working on a Cubase Selected Channel MIDI Remote Device. This new feature will enable MetaGrid Pro to track the selected channel in Cubase and fully respond to MIDI bidirectional communication. It’s a big step toward making MGP even more integrated and powerful for your Cubase workflow!
Here’s the plan:
We’ll include all the standard features you’d expect for the selected channel, ensuring seamless operation right out of the gate.
But since we’re in the programming phase, we’d love to hear your ideas!
What features do you dream of having in this controller?
Have you seen cool implementations in other controllers that you think we should include?
This is your chance to help us shape this feature and make it exactly what you need. Whether it’s advanced functionality, workflow enhancements, or innovative new ideas, we’re all ears!
Drop your suggestions below, and let’s build something awesome together.
Your feedback is invaluable—let us know what you think!
AI Knob:
We have already added the AI knob feature that will enable you to control the value under mouse. Just imagine a gesture pad just for that :-).
2: I noticed that the panning faders are often at zero when you open MGP with cubase, which means that you have to reconfigure the panning each time, it would be good if the fader automatically took the parameters defined in cubase automatically when you change tracks.
thank you for this app really very practical to control cubase
Here comes the good news - we have managed to get the focus quick control and quick control parameter names so you will be able to display them in MetaGrid Pro. So happy about it. The sneak peak video should land this weekend.
I would also love the ability to add inserts and load specific FX Chain Presets to the selected channel. Not sure if this is possible within what Cubase offers, but it’s high on my list.
I was looking at Cubase 14 and how one can assign modulators to a track - and that at least in Kontakt and the VSL Synchron player, all parameter targets of the instrument are visible. Assuming this lives in some sort of .json file or the like, could this be read such that we could choose parameters we want to have assigned to buttons or faders and have a grid for that automatically generated, with names for the faders?
Nice work. Will the name on those plugin buttons update if I change, add or delete a plugin?. And I would suggest a Bypass button at the top instead of a slider. And why is the plugin UI not being displayed in Cubase?. Or maybe it is, but MGP is covering it?. And why is the order of the plugins reversed in MGP?.
yes, the plugin buttons will update when you change, add or delete a plugin. Regarding the bypass button at the top of the fader - we are space limited here - do you mean bypass a send? For bypassing the insert, you just tap the plugin button. And yes, MGP is covering the plugin UI The order is reversed due to the eronomic reasons to limit the hand movement to reach the items that should be more accessible - but if it messes with your Cubase brain, you will be easily able to rearrange that.
It’s a big step toward making MGP even more integrated and powerful for your Cubase workflow! 
We’ll include all the standard features you’d expect for the selected channel, ensuring seamless operation right out of the gate.
But since we’re in the programming phase, we’d love to hear your ideas!
What features do you dream of having in this controller?
Have you seen cool implementations in other controllers that you think we should include?
Drop your suggestions below, and let’s build something awesome together.
The order is reversed due to the eronomic reasons to limit the hand movement to reach the items that should be more accessible - but if it messes with your Cubase brain, you will be easily able to rearrange that.