This is an issue I have with several macros. I create a PLE that works fine in Cubase (15 Pro, on W11 latest versions), I assign a macro in the generic remote to run that PLE. In MG, I assign that macro to a button. WHen I press that button, I do get the expected behavior of the PLE, but I also get unexpected behavior. In one case the pan jumps to the right, in another case a track gets muted, and in another case a track gets soloed! For instance, I have a macro to hide disabled tracks (macro 011). I press the button and the disabled tracks do get hidden, but then a track gets ‘m’ muted.
Hi Brett,
Thanks for the screenshots. We checked the mappings, and Macro 011 sends MIDI channel 10, CC21. The Selected Channel mute control uses the same message on a separate MIDI port. Pan and solo also share messages with nearby macro slots. That makes a second control mapping receiving the macro’s MIDI traffic our leading explanation, although we still need to check your routing.
The MIDI input shown for Generic Remote 4 is correct: Metasystem - Cubase. On the native Windows setup, the MetaGrid Pro Selected Channel surface should use Metasystem - Cubase Sync for both input and output.
Could you check the Selected Channel ports and send a screenshot of the MIDI Remote device list showing its input and output? Please also show the MIDI input assignments for the other Generic Remote devices in Studio Setup—an older mixer mapping could be receiving the same messages.
For a quick isolation test, keep Generic Remote 4 unchanged, temporarily disable only the Selected Channel script in MIDI Remote Manager, and try Macro 011 once in a test project. Then re-enable the script. Does it still hide the disabled tracks, and does the unwanted mute disappear? Steinberg’s instructions for disabling and enabling a script.
If the mute still occurs during that test, please also show the button’s complete macro in MetaGrid Pro so we can check its actions and target.
I was busy today so I will check all this tomorrow.
Why would the macros send MIDI messages? Aren’t these macros specifically for users to program? If not, then what are the macros that do not have any extra midi messages on them?
I actually remember having an issue a long time ago where MG was sending messages to CC for no reason. I had to turn off midi out somewhere, I forgot. Not sure if that is the same problem.
Thanks.
Well, not sure what I did, but it is now working properly. At first, there was no Commands for some reason, so I added it. I went into generic remote 4 (where my macro is) and i changed it to not Metasystem then back to Metasystem Cubase then pressed okay. It then worked fine, no surprising behaviors anymore on any macro. It was acting strange for 2 weeks but now it’s okay!
Here’s all my screen shots anyway.
BTW, what is the Metasystem Midi loop used for? I use Metasystem Sync and Metasystem Cubase, but not Metasystem Midi.
Thanks 
Oh, and why does macro have several functions?