This update addresses critical issues affecting multi-device connectivity and Cubase MIDI Remote integration :
Fixed: Disconnection issues with single/multiple iPads connected to the same server on some user setups.
Fixed:MIDI communication with Cubase MIDI Remote .
Important Step for MIDI Remote Users:
Remove Metasystem - Cubase Sync - In & Metasystem - Cubase Sync - Out from LoopMIDI .
Recreate these ports from scratch.
Realign the port settings in MetaServer.
Note: The Cubase MIDI Remote implementation is not fully functional yet – the Inserts functionality is still not working as expected . We are waiting for Steinberg’s response , as this appears to be an API-level issue on their side.
Thanks for your patience—we’ll update you as soon as we have more news!
I can confirm that some 2-way communication does work now with the Metaserver 5.1.4 Hotfix and Cubase 14 on Windows. But there is a strange behavior with several VSTs. Instruments in the VSL Synchron player have multiple cc parameters (cc1, cc7, cc8, cc11, etc.) set automatically to ZERO when starting Cubase with the MIDI Remotes installed. This makes the VST’s unusable without resetting all cc levels. What would cause this action?
Pleased to report that with Metaserver 5.1.4 and MGP 1.6.7 BETA I have had no disconnections with incoming MIDI or my PC. And Snapshots work again. Yay!
But my 2 iPads still don’t reliably connect on launching Metaserver. I still need to unplug/plug one of them to get it to connect.
Oh, and somehow quitting Metaserver or launching it is affecting the audio coming out of my PC. I have had to restart my PC to get audio back a couple of times now.
I’ve been using it for an hour now and it’s just like Metagrid says:
Disconnection issues Fixed, MIDI communication with Cubase MIDI Remote Fixed and “Cubase MIDI Remote implementation is not fully functional yet”
I run *solely *Win Defender on my machine where Metaserver is *allowed
*as incoming rule - 5.0.0. and 5.1.1. slide through OK but 5.1.4
doesnt. It just doesnt show up in the bottom range and also cant be
activated per auto-upate within Metaserver 5.1.1 -strange! I add a
log-file that Metaserver produced, hoping that you can detect the reason
… best wishes from Austria!
(Attachment Metaserver_ExceptionLog.log is missing)
Another forced update to Metagrid today to version 1.6.6. (I thought I had switched off auto updates on the ipads but it happened anyway. Maybe that’s just how ios works?)
So I updated to metaserver 5.1.4. for windows. Unusable. I have two ipads and they just kept disconnecting all the time. This latest rolloout on windows seems to be unfit for purpose in my studio. I’ve returned to 5.0.3 for the time being.
Do other windows users have it working reliably? I’m not referring to Cubase midi remote setup. Just existing generic remotes and grids interacting correctly with 5.1.4.
Mine is working well here with 2 iPads on MGP 1.6.7 BETA 1 and Metaserver 5.1.4 on Win 11. No disconnections thus far. Just the initial connection to 2 iPads is unreliable and needs me to plug/unplug an iPad.
MetaServer Win 5.1.4.0 Hot Fix – Release Notes 
Fixed: Disconnection issues with single/multiple iPads connected to the same server on some user setups.
Important Step for MIDI Remote Users:
Remove Metasystem - Cubase Sync - In & Metasystem - Cubase Sync - Out from LoopMIDI .
Recreate these ports from scratch.
Realign the port settings in MetaServer.
Note: The Cubase MIDI Remote implementation is not fully functional yet – the Inserts functionality is still not working as expected . We are waiting for Steinberg’s response , as this appears to be an API-level issue on their side.
Download the latest update by auto-updating, our website or from here:
And Snapshots work again. Yay!