Hi Folks
Any ideas with this? Scenes suddenly have stopped working. I can see in MG the correct macro is triggering (scene 001,002 etc)
In Cubase, I can see that a message is being received in the activity thing at the bottom of the arrange window
In the LPE editor, I can trigger those specific scene commands from the editor which work as intended.
Cubase commands built into Metagrid seem to be working as normal. Not sure where the problem is coming from.
Thanks for the help!
Hmmm, can you check the MIDI port assignment in the Generic Remote devices?
Can you show scroll down to the scenes list on this screen and see if the scenes have assigned the corresponding macros?
Also can you verify that you are getting MIDI CC data in Cubase when you press the buttons in MGP with a scene macro assigned?
Hiya
Yes can confirm I can see midi activity monitor light up when pressing a scene command
This is a screen grab of both windows scrolled down. Does this look correct?
OK, do the following test - select the Scene 001 in the upper pane (part with MIDI assignments) and check the Learn checkbox, create a button in MGP with the Scene001 command assigned and press the command and see if the assigned values change.
Are you using Pause instructions at all? I have a long standing template (based on the JononotBono PLE scenes) that had been happily working with Cubase 14 until a few days ago. Then suddenly PLE scenes wouldn’t work anymore. I had pauses built into the Macros, and when I removed these the scenes and macros have started to work again.
No idea what changed to cause this, but that is the mysterious wonderworld that is Metagrid…
@Redleaf Can you please send me the macro with pauses that was problematic? We have tested the Pause action and they work as expected in all applications we have tested including Cubase.
Hi @MetaGrid_Admin Sorry didn’t get back to your suggestion, and thanks for the help. Actually managed to fix this on my own.
Realised I had created an additional midi remote script to send some other type of commands that worked a bit better through there. I guess it took over the midi port that the scenes use? I disabled this script and the scenes now work again as normal. The midi remote in general, plus the MG scripts now in Midi remote and midi ports in general confuse the hell out of me 
As an aside, is there a way to create another midi remote page?
Currently have the ‘Selected Channel’ midi remote active (I don’t use the new CB channel page, but do use the track selection for articulation pages, so I think this is still necessary)
And then there is the ‘Commands’ Midi remote (I guess necessary as well?) but not sure how this is different from the generic remote stuff I set up.
Like I said the actual communication between CB and MG still confuses me.
Thanks again for all the help
I’ve sent you the buttons directly.
MetaGrid Pro 1.6.10 will feature additional MIDI ports that would will be able to use for you custom MIDI Remote devices.
