Midi Remote Manager Surfaces Disappear Cubase 14 Pro

Support & Troubleshooting Cubase
1

I added both surfaces in the midi remote manager. When I exit and come back into Cubase they are gone. How do I make them permanent?

And now, none of my grids work at all. They worked the first time I set it up, but never again after.

I really need to get this to work again. I followed the video exactly.

Windows 11

2

Same experience here.

3

A post was merged into an existing topic: :bug: MIDI feedback on Metasystem Cubase Sync crashing MGP/MetaServer on Windows

4

Thank you Guys for your findings. We can’t replicate this on our test systems and also none of the Beta testers have reported this. We will do our best to solve it. I will make separate threads for each issue reported here:

  1. MIDI Feedback crashing MGP/MetaServer on Windows
    https://forum.metagrid.app/t/midi-feedback-on-metasystem-cubase-sync-crashing-mgp-
    metaserver-on-windows/506/2

  2. MIDI ports don’t stay permanent on Windows

What is the name of your MIDI port you have created in LoopMIDI - the controllers are hardcoded to find Metasystem - Cubase Sync - In and Metasystem - Cubase Sync - Out. Please make sure your ports are named as specified. Let me know.

@

5

I am still having issues. My server crashed on starting up Cubase, I am starting a new thread for that. (that’s why no grids were working of course)

I create the surfaces exactly, they work fine. I close Cubase, open Cubase, and they are gone. That is still happening. It might be a Cubase issue, but I do not know. But now I have to create new surfaces every time I open Cubase.

Screenshots of my setup:
metagrid.zip (415.3 KB)

6

OK - can you add the Metasystem - Cubase Sync port in the MetaServer MIDI port config - it is not assigned there. Are the ports kept in Generic Remote devices?

7

I added the sync port. Still not saving the surfaces. The ports do stay in the Generic Remote. (when I close a session and open a new session the surface stays, it is only when i close Cubase and restart)

Screenshot 2025-02-11 103410
Screenshot 2025-02-11 103410574×626 12.9 KB

8

Just came here to add that here, too, midi remotes do not persist in Cubase after quitting and re-opening. A custom midi-remote I created for another device does persist; it’s only the Metagrid Pro devices that dissapear.

I also cannot get Cubase to read the selected channel fader data from Metagrid Pro, however the faders do move when triggered from Cubase via mouse and/or from my fader unit running MCU. I can, however, get transport buttons to functional bi-directional as normal.

I am getting odd behavior on the selected track title; it shows the track name but appends an “?” after it.

Finally, there also seems to be an issue with connecting to Metagrid Server via TCP mode in that, if the connection is lost to Metagrid server, it will see my PC but not re-connect unless I quit Metagrid Server and launch it again.