I thought this issue was fixed with the memory leak in Metaserver but alas, it has reared its ugly head once again.
During my latest session in Cubase, my macros were becoming unresponsive. So I would tap the button again and again. Then 5-7 seconds later all of them would offload causing havoc in Cubase. I restated Metaserver because that used to fix it. But then my second iPad wouldn’t connect no matter how many times I unplugged/plugged, restarted Metaserver, restarted MGP. Nothing worked. So I had to quit my session altogether and restart my PC. Quite the workflow killer indeed.
This whole unplug/plug thing to get two iPads to connect is ridiculous. Once it’s up an running MGP is awesome. But initially, when doing battle with the USB cables, it certainly doesn’t come across as a ‘Pro’ piece of software unfortunately.
When you run multiple tablets over USB, through hubs, while Cubase is under heavy load, you’re stacking several fragile layers at once: iOS USB networking, macOS USB stack, Cubase automation load, and the server bridge. Any one of those can stall temporarily and it looks like the control software is the culprit.
Even extremely expensive “pro” systems behave the same way sometimes:
Avid EuCon systems randomly drop surfaces or batch-fire commands when the network stalls. In the past I used to have super expensive Euphonix MC Pro and the command stacking in Cubase on Windows was a regular thing. Not an excuse - but reality check.
Steinberg MIDI Remote can freeze or buffer commands when Cubase is under heavy project load.
OSC controllers often queue messages and dump them all at once if the host stalls for a few seconds.
What you described — taps queuing up and firing 5–7 seconds later — is almost always a temporary host stall / message backlog.
Regarding the connection issues: USB device negotiation between macOS and multiple iPads can be particularly unreliable, especially when hubs are involved. That’s unfortunately an Apple USB networking quirk more than anything else. Many pro setups end up switching to dedicated Wi-Fi or wired Ethernet adapters for that reason.
That said — we’re very aware of these pain points.
We’re a few days away from releasing MetaGrid 1.6.17, which includes a lot of low-level improvements, particularly around: