[Production Verification] Cubase shows MG disconnected in Remote Manager

Support & Troubleshooting Cubase
1

This is happening a lot now. I end up having to close Cubase, close midi server, close windows midi, restart all and that does not always work. I sometimes do this 2-3 times, it takes like 10 or so minutes to eventually get it to work. (Windows 11, Cubase 15 Pro, latest updates on all)

mg dis
mg dis906Ă—724 17.7 KB

2

This may have something to do with Windows Midi services, but not sure. It does give me other problems.

3

Thanks for the additional information. This may be addressed by MetaServer Windows 6.0.4 RC1.

MetaServer 6.0.4 includes a correction for stale or unopenable Windows MIDI Services endpoints. MetaServer now attempts to reconcile and restore its MetaGrid, Cubase and Cubase Sync ports without requiring repeated application restarts or a Windows reboot.

You can download MetaServer Windows 6.0.4 RC1 directly here:

https://metagrid.app/downloads/rc/metaserver/windows/6.0.4/RC1/MetaServer-6.0.4-RC1-Windows.exe

If you are a member of the MetaGrid Pro beta program, you can download the complete test package—including MetaGrid Pro 1.7.4—from the beta forum:

https://forum.metagrid.app/t/150

Please install the available release-candidate builds and let us know whether Cubase still shows MetaGrid as disconnected. If the problem continues, please capture a MetaServer support package before restarting Cubase, MetaServer or Windows MIDI Services. That will show whether the failure remains in Windows MIDI endpoint recovery or sits within the Cubase integration state.

1 Like
4

Installed the new server but same problem, shows disconnected in cubase. However, I was able to get it to work this time by closing metaserver (which quit fine!) and restart. Then i launched cubase again and it was working.

Also, I tried to email from metaserver, but the email bounced back!! "Delivery to the following recipient failed permanently:
help@metasystem.io

Technical details of permanent failure:

550 No such recipient here"

I will send you the log file here by DM.

5

Thank you—this is useful verification. The fact that restarting MetaServer restored the Cubase connection, while MetaServer itself now quits correctly, shows that the release candidate improves part of the recovery path but does not yet make the initial endpoint recovery fully automatic.

Please send the log file directly to help@metagrid.app. The bounced address opened from MetaServer is also a defect; thank you for flagging it. The contact address in MetaServer will be corrected.

We will compare your log with the recovery sequence in MetaServer 6.0.4 before marking this issue as resolved.

1 Like
6

MetaServer Windows 6.0.4 is now publicly available and includes the Windows MIDI Services endpoint-recovery correction relevant to this report.

MetaServer now detects stale MetaServer-owned virtual endpoints, reconciles them and performs bounded readiness retries when newly created APP endpoints are not immediately available. This is intended to restore the MetaGrid ports without repeatedly restarting Cubase, MetaServer, Windows MIDI Services or Windows.

Please update to MetaServer Windows 6.0.4 and test several Cubase start/quit cycles while leaving MetaServer and Windows MIDI Services running. Confirm whether the MetaGrid MIDI Remote devices remain connected each time.

If Cubase shows MG disconnected again, please capture a MetaServer support package before restarting any service or application and let us know whether the MetaGrid ports are visible in Cubase’s MIDI port list at that moment.

1 Like