This is consistent behaviour:
After taking a short break MGP goes dim. On returning to my iPads, I tap the screen, MGP lights up, but when I tap a button, it goes into scanning mode. It then presents wifi only (never USB) I tap it, and get the ‘Connecting…’ pop up, which always results in ‘Connection Failed’. So I must quit MGP and re launch it. If it does in fact reconnect, there is no MIDI getting through to my PC. So I must relaunch MGP anyway.
MGP 1.7.3
Metaserver 6.0.3
I experience a similar sequence of events. I’m on a mac running Tahoe and an iPad air gen 4. Like you, after the scan after MGP has been dimmed on my iPad it efficiently connects to WIFI and claims that USB is not available. I then disconnect in the menu, and then rescan, and then USB is available. I don’t think I have to force a relaunch. That used to be the case for me but the last update eliminated that step for me.
Connectivity in 1.7.3 is still all over the place on PC. I can literally be just staring at my computer monitor i.e. zero input/activity, and MGP will just drop off and go into radar mode. And depending on the day, USB will just not be available
I have 2 iPads connected at the moment, but Metaserver looks like this:
And on one of my iPads in Settings, ‘Network & Transports’ indicates that ‘USB peer Responded’. On my other iPad I get ‘No peer detected’. 
Also, I have had to restart my computer several times after finding that no MIDI is getting through to my PC after MGP goes to sleep. Maybe something to do with Cubase. And no matter if I restart MGP, Metaserver, LoopMIDI, nothing fixes it.
Will it ever actually just work? After all these updates (I started on 1.6.5), how can connectivity still be this flimsy?
Thanks to both of you for the detailed reports. The Mac and Windows symptoms described here overlap corrections included in the current MetaGrid Pro and MetaServer release-candidate stack.
MetaGrid Pro 1.7.4 includes improvements to sleep/wake recovery, automatic reconnection and USB/Wi-Fi transport selection.
MetaServer Mac 6.1.4 RC1 makes USB reconnection self-healing after iPad suspension or stale USB-session state. It can be downloaded directly here:
https://metagrid.app/downloads/rc/metaserver/macos/6.1.4/RC1/MetaServer-6.1.4-RC1-macOS.dmg
MetaServer Windows 6.0.4 RC1 adds recovery for stale or unopenable Windows MIDI Services endpoints, including cases where MIDI ports previously remained unavailable until Windows was restarted. It can be downloaded directly here:
https://metagrid.app/downloads/rc/metaserver/windows/6.0.4/RC1/MetaServer-6.0.4-RC1-Windows.exe
If you are members of the MetaGrid Pro beta program, the complete test package—including MetaGrid Pro 1.7.4—is available in the beta forum:
https://forum.metagrid.app/t/150
Please test with the appropriate MetaServer RC1. If the problem continues, capture a MetaServer support package before restarting MetaGrid Pro, MetaServer, Cubase or Windows MIDI Services.
For the two-iPad Windows setup, please also include screenshots of Network & Transports from both iPads and the MetaServer device list while the failure is present. That will show whether the remaining problem is client reconnection, USB enumeration or Windows MIDI endpoint recovery.
Just installed the new Metaserver and it still goes into scanning mode without any input/activity. But it did re-connect okay. I’ll keep you updated.
Nope. It’s exactly the same as the old version. After waking up, it goes into radar mode and then presents only Wi-Fi followed by ‘connecting…’ ‘Connection Failed’
Basically identical behaviour to the last version i.e. no improvement what so ever.
MetaGrid Pro 1.7.4 and MetaServer Windows 6.0.4 are now publicly available with coordinated sleep, reconnection and MIDI-endpoint recovery improvements relevant to this report.
MetaGrid Pro now refreshes connection discovery after foreground recovery, reconciles rediscovered Wi-Fi endpoints and avoids presenting Wi-Fi as required when a usable USB transport exists. MetaServer Windows can also recover stale or temporarily unopenable Windows MIDI Services endpoints without requiring a complete Windows reboot.
Please update the complete production stack and repeat the original scenario:
If either iPad enters radar mode, loses USB or reconnects without MIDI working, please capture support packages from that iPad and MetaServer before restarting any application or Windows. Please identify which iPad failed and which transports were shown at the time.
Seems to be working okay here with USB and Wi-Fi. At least the first sleep test worked. I did initially get a crash though.
USB seems to be showing up more consistently too. But on relaunching MGP USB is still mostly missing. Even with tapping refresh. But with an unplug/plug of the USB cable, both iPads are displaying USB again.
I opened Chrome and MGP on one iPad went into radar mode followed by only Wi-Fi connection available.
Nope. Still busted. It won’t wake up now after about an hour. Tapping the iPad screen does nothing. MGP is stuck in dimmed state.
Plus launching Cubase causes the radar to kick in.
Thank you for the detailed follow-up, JTB. Additional sleep, dimmed-overlay, USB relaunch and connection-recovery improvements have since been released in MetaGrid Pro 1.7.5.
Could you please repeat the test using MetaGrid Pro 1.7.5 with MetaServer Windows 6.0.4? The most useful checks would be:
If MetaGrid Pro still crashes or becomes stuck, please send a new MetaGrid Pro support package and the corresponding iPad crash report from Settings → Privacy & Security → Analytics & Improvements → Analytics Data. Look for a recent file beginning with MetaGrid or MetaGridPro and ending in .ips.
Total Trainwreck.
I had MGP running, launched Cubase and Metaserver crashed. I relaunched Metaserver and iPads couldn’t find any computers. I relaunched MGP and connected but there was no MIDI getting through. Meanwhile, I’m getting radar screens popping up all over the place. Oh, NOW MIDI is getting through somehow, Yay!
Very frustrating.
Thank you for the report. We have not been able to reproduce this behaviour on our test systems, so diagnostics from the affected setup will be essential.
Could you please reproduce the problem once more and send us:
Please capture the support packages before restarting MetaServer or MetaGrid Pro, if possible. You can send the files privately to help@metagrid.app and mention topic 1608 in the email.
The sequence is particularly important here: MetaServer crashes after Cubase launches, the iPads temporarily cannot discover the computer, and MIDI remains unavailable after reconnecting. Matching diagnostics from the same occurrence should show where that recovery chain breaks.
