Target app for macros not working in 1.7.5?

[magnumpraw]

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?

[magnumpraw]

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.

[MetaGrid_Admin]

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:

MetaGrid Pro 1.7.6 Hot Fix Released

MetaGrid Pro 1.7.6 is now available on the App Store for iPadOS and Mac Catalyst. This focused hot fix addresses two issues reported after the previous production release. Important: MetaGrid Pro 1.7.6 requires MetaServer Mac 6.1.4 or MetaServer Windows 6.0.4. Fixed Fixed incorrect MIDI-port assignment for newly created Cubase MIDI 2–9 and Cubase Sync buttons. Fixed a crash that could occur when editing a button after moving it. Thank you to everyone who reported these issues and helped us …

The later question about fader routing is separate from this button fix and is not part of the 1.7.6 hot fix.

[magnumpraw]

thanks for the quick fix.

Is there a way for faders to send on the extra Cubase MIDI ports?