1( I’m on a Mac M2 running OSX 15.7.2, and when I download the metagrid server, it doesn’t allow me to open up the options to ensure cubase is checked.
I’m watching the mac cubase setup video, and when adding a mack control device, I don’t see a Metasystem MCU in the drop down.
The selected track grid on the ipad works, at least the volume fader. But the play button, record and transport controls dont work. Some buttons work, some dont.
Every time I restart Cubase, it doesn’t keep these new midi remote devices. How can I save them?
Whenever I open up my laptop after it sits, the server wont connect. A lot of times it just wont connect.
Thanks for the detailed report — let’s go through each point and get this working.
MetaGrid Server won’t show the “Options” window on macOS 15.7.2
I need a bit more information here. What exactly happens when you click Options in MetaServer? Does the button not react, or does the window appear empty? Also, are you running the Universal version from Applications, not directly from the DMG? This will help narrow it down.
Cubase → No “Metasystem MCU” in the Mackie Control device list
Please confirm whether you’ve created the virtual ports in LoopMIDI. Cubase won’t show “Metasystem MCU” unless a matching LoopMIDI device exists. Did you create a device called “Metasystem MCU” (In/Out)? After creating it, restart MetaServer and Cubase.
Some controls work, some don’t (transport buttons not responding)
This usually indicates Cubase is using partial or incorrect port mappings. Please send screenshots of:
Cubase → Studio Setup → MIDI Remote → your Metasystem device
Cubase → Studio Setup → MIDI Port Setup
This will help identify the routing issue.
Cubase doesn’t keep the MIDI Remote devices after restart
Make sure LoopMIDI starts first, then MetaServer, then Cubase. If Cubase launches before the ports exist, it will drop the configuration on the next start.
Server doesn’t reconnect after waking the laptop
I need more details here. Are you connecting the iPad via Wi-Fi or USB? When it fails, what does MetaServer show under “Connections”? Does restarting MetaServer restore the connection? The fix depends on the connection type.
Send the missing details/screenshots and we’ll sort out the rest.
@MetaGrid_Admin Thanks for all the guidance. I figured out some of the steps, but I’m not headed in a good direction here.
I was able to get into the app once and see that I still can’t access all the functionality of the Cubase templates. Things like volume sliders, Solo, and mute work, but record, play, and any MIDI editing functionality don’t work. I’ve attached screenshots.
It appears Cubase now keeps the MIDI remote devices after a restart. But what is LoopMIDI, isn’t that just for windows? I’m on a Mac.
The big problem now is that after updating the metaserver just today, my ipad won’t find my computer. It did for a bit and then it kept asking me to backup. I would say yes, and then it would ask again right away. It kept doing that multiple times.
After that was done, when I was in, it kept “searching computer”. This is when ipad is plugged in.
When my ipad is not plugged in via USB, it shows the name of my computer, but it says “Can’t find this computer on your network”. I’ve tried restarting Metaserver both when it’s plugged in or not, it doesn’t change anything. I would love to use this app no matter if I’m plugged in or wireless.
@MetaGrid_Admin I just want to confirm, even when the iPad is connected to my computer, the app is now constantly scanning for my computer. I have fiber optics, so the network shouldn’t be a problem.
Yes I’m on the latest MGP and Metaserver and am connected via USB. I’m not using a VPN or anything like that.
Not sure why it had 2 command remotes installed. When I initially tried creating one, it kept saying it couldn’t save the device because it didn’t contain any elements. But then when I restarted Cubase, it was there so it probably kept both. One author was from you guys, one was from me. When I deleted the one in my name, both were gone when I restarted Cubase. The one that was in your name wasn’t active anyway.
I tried again to create the commands one again, but it keeps giving me the same warning. It simply will not create the commands remote.
It’s a fairly long usb cable, I think 6 or 8 feet and it’s connected to a powered hub. I don’t have room on my laptop because I have an audio interface and 2 monitors.
@MetaGrid_Admin Good news is, it seems more stable today. It might have taken a day for the updates to reflect. Still can’t use all the functionality of the Cubase templates though.
Also, I switch between different iPad apps a lot, and when I’m on Metagrid for a bit, the iPad quick switcher on the bottom fades out, and it doesn’t allow me to switch apps quickly. I know you guys want me to stay in Metagrid, but is there any way I can turn that off?
Just to clarify — this isn’t a MetaGrid Pro–specific issue. iPads are very picky about USB signal quality. Long cables (especially non-Apple or non-certified ones) and USB hubs are common causes of unstable or failing USB connections.
A few things worth knowing:
Long passive cables weaken the data signal, even if they charge the iPad fine.
Many third-party cables don’t meet proper USB-IF data specs, which leads to random dropouts.
USB hubs can introduce signal loss, voltage instability, or bandwidth limitations, especially cheaper ones or hubs that weren’t designed with high-quality data transfer in mind.
Combining a hub + a long cable multiplies these problems, and iPads will simply give up if the signal isn’t clean enough.
The fastest way to confirm the root cause:
Use a short, high-quality USB-C → USB-C cable directly from your iPad to your Mac (no hub in between).
If that works — and in most cases it does — the hub or the long cable is the culprit.
If you’re out of ports, a reliable Thunderbolt/USB-C dock (CalDigit, OWC, etc.) or an active USB-C cable is a far better option than long passive cables or low-end hubs.
That fading isn’t something MetaGrid Pro is doing intentionally — iPadOS automatically hides the quick app switcher after a few seconds when an app is in “active interaction” mode (anything that uses continuous touch, gesture tracking, or background communication). MetaGrid happens to trigger that behavior because of how it maintains the connection and updates the UI in real time.
Unfortunately, there’s no setting we can toggle to force the switcher to stay visible — iPadOS doesn’t expose any API to control or override that system behavior.
The good news is:
Swiping up from the bottom edge always brings the switcher back instantly.
Using multitasking gestures tends to be more reliable than relying on the auto-visible bar.
So don’t worry — we’re not trying to trap you inside MetaGrid. It’s just iPadOS doing its usual “I know better” thing.
If Apple ever exposes a way to request persistent switcher visibility, we’ll happily support it.
