We’ve been working tirelessly over the past two days to fix MIDI Remote integration for Cubase on Windows and get the Windows server running smoothly. After digging deep, we identified the root causes—specific aspects of how LoopMIDI and Cubase handle MIDI—and we’re happy to deliver a new MetaServer 5.1.2 Beta that brings:
Fully functional MIDI Remote integration for Cubase on Windows
No more unexpected server disconnections
Please note that this is a Beta build, so we encourage testing and feedback. The good news is that MetaGrid Pro 1.6.6 still supports earlier MetaServer versions, so you can easily roll back if needed.
Fixed:
No more feedback
No disconnecting
No more “?” question marks on the parameters
Not fixed:
No MIDI communication. Getting no MIDI from Metagrid whatsoever today after updating.
Not all faders are filling in. 5/8 of them are still blank blocks
I’m also now not getting any automatic scene switching. It works maybe a couple times and then stops.
OK, it seems that we are still not there. Working hard… The lack of persistence may be caused by the crash on your system. On all our test systems the controllers are automatically loaded on restart - also you don’t need to configure them - once put in the respective location in the specified location and the ports are properly named, they are auto configured when Cubase launches.
Fully functional MIDI Remote integration for Cubase on Windows
