Was just trying to set up some new buttons using Cubase MIDI 3 or 4 target app, but the buttons only send on the normal MGP midi channel even though I’ve chosen the correct target app in the button settings.
Older buttons I’ve already made send properly on the target app for MIDI 3 or 4, but nothing I make that’s NEW will send on any of the extra Cubase MIDI apps.
Bug?
also, do faders not work on the extra Cubase MIDI ports?
When I create a fader, the “Target App for Macros” option is not there.
Thank you for reporting this and for clearly distinguishing the behaviour of existing buttons from newly created ones.
The MIDI-routing problem affecting new buttons created for Cubase MIDI 2–9 and Cubase Sync has been fixed in MetaGrid Pro 1.7.6, which is now available as the production release for iOS/iPadOS and Mac Catalyst.
Production announcement and release notes:
The later question about fader routing is separate from this button fix and is not part of the 1.7.6 hot fix.
thanks for the quick fix.
Is there a way for faders to send on the extra Cubase MIDI ports?
The current fader editor doesn’t have the Target App for Macros selector, so Cubase MIDI 2–9 cannot be selected directly there. That is a limitation of the existing fader setup.
For ordinary MIDI CC control or recording on an instrument track, you can use the Metasystem – MIDI port and assign the required MIDI channel and CC number to each fader. Our fader setup guide explains the CC settings.
Could you tell us what you need the extra ports for—separate custom MIDI Remote surfaces, or recording CC data on instrument tracks? Do you also need feedback from Cubase to the faders?
More flexible fader output routing is part of the Meta-Controller work planned for MetaGrid Pro 2. For your current setup, those details will help us suggest an appropriate route.
I was wanting to use the extra midi ports to create my own Cubase Remote for the control room:
Headphone control, monitor switching, etc.
Yes, would need feedback from Cubase to the faders.
ALSO … I can get buttons to work using the extra midi ports but was running into issues with bi-directionality. I could get buttons sending on MIDI 4 to change buttons in Cubase, but when I manually changed the button in Cubase, the button in MGP didn’t respond. Is it currently not possible to have bi-directionality with the extra MIDI ports?
Thanks for all your work!
Thanks—that clarifies what you’re building.
For the Control Room faders, the current fader editor has no target-port selector, so I can’t give you a supported way to send them through Cubase MIDI 4 with matching feedback today.
Buttons are different: Cubase MIDI 4 isn’t intended to be send-only. A latching button can respond to incoming MIDI CC, but sending a command to Cubase does not by itself make Cubase send its changed state back. The custom MIDI Remote surface needs an output mapping, and the button’s Toggle From External Sources settings need to match the returning channel, CC, and on/off values.
Could you show us one monitor-switching button as an example? Please include its target and macro action, both external-source states, and the custom surface’s input and output port assignments in Cubase. The Mac port pair for that route is Metasystem - Cubase 4 - In/Out. Please also tell us your Cubase version. That will let us check whether this button can work with the current setup or whether its Cubase mapping is only sending commands without returning state.
More flexible controller routing and feedback are part of the Meta-Controller work for MetaGrid Pro 2, but I don’t want to promise this particular Control Room setup before it has been tested.
Here’s a vid showing what I’m trying to do.
I’m on Cubase 15.0.30