Important Update for MetaGrid Pro & Cubase Users on Windows
We’ve encountered unexpected issues with our new Cubase MIDI Remote integration on Windows. While our in-house testing and beta feedback indicated everything was working correctly, many of you have reported crashes, disconnections, and missing MIDI actions when using the new MIDI port.
After further investigation, we’ve been able to replicate the issue on one additional test system, but the root cause remains unclear. The same JavaScript scripts work flawlessly on macOS, yet on some Windows machines, they behave unpredictably—specifically, the MIDI Sysex messages received from Cubase differ from what we see on macOS and other Windows machines. We’re unsure if this is an issue with Cubase itself or LoopMIDI, but this behavior is completely unexpected.
Given these challenges, we’ve decided to:
Prepare a new MetaGrid Pro build that will allow Cubase users to revert to the previous MetaServer version.
Temporarily mark MIDI Remote integration as Mac-only until we fully resolve the issue.
Continue investigating the root cause on Windows with high priority.
We’re deeply sorry for this setback—we were truly excited about this integration and understand your frustration. The new MGP build will be sent to Apple for review tomorrow, and we’ll keep you updated as we learn more.
Thank you for your patience and support. We’re committed to getting this right.
— The MetaGrid Pro Team