[Beta Verification] MetaGrid Pro connection fails until app restart

Hi Everyone

About a month ago I wrote about the connectivity changes introduced in MetaGrid Pro 1.7, the challenges we encountered in some real-world setups, and the work we had started to make the new connection engine even more robust.

Today, MetaGrid Pro 1.7.3 is available, and I’d like to share what we’ve accomplished.

Over the past few weeks our primary focus has been connectivity—not just fixing individual issues, but improving how MetaGrid Pro understands and manages the connection between your iPad and your computer. Sleep and wake cycles, USB reconnects, network changes, MetaServer restarts, backgrounding, unstable cables, host availability, timing differences—these are the kinds of situations that happen every day in real studios, and they all need to be handled gracefully.

The biggest addition in 1.7.3 is Connection Monitor.

Connection Monitor gives MetaGrid Pro a much deeper understanding of what’s happening behind the scenes. It provides detailed diagnostics, recent connection history, host discovery information, transport status, and recovery details—all built directly into the app. It also makes troubleshooting significantly faster by allowing you to send a complete diagnostic package whenever support is needed.

Connectivity is rarely the result of a single bug. It’s usually the interaction between iPadOS, macOS or Windows, USB, Wi-Fi, hubs, security permissions, MetaServer, and the application you’re controlling. Connection Monitor helps make those interactions visible, allowing both you and us to understand what’s happening much more quickly.

Alongside Connection Monitor, version 1.7.3 includes numerous stability improvements and refinements across the connection engine, many of them driven directly by the reports and diagnostic logs you’ve shared over the past month. Those real-world reports helped us identify patterns that simply don’t appear in controlled development environments, making MetaGrid Pro more resilient across a wide variety of hardware and workflows.

MetaGrid Pro 1.7 introduced a new foundation for connectivity. With 1.7.3, that foundation is significantly more mature, more transparent, and better equipped to deal with the complexities of real production environments.

Please update to MetaGrid Pro 1.7.3 and install the latest MetaServer (Mac 6.1.3 / Windows 6.0.3). If you continue to experience connection issues, you can now send diagnostics directly from the app using Connection Monitor, giving us far better insight into what’s happening on your system.

Finally, thank you to everyone who shared feedback, logs, screenshots, and detailed descriptions. Your reports have had a direct impact on this release and continue to help make MetaGrid Pro stronger with every update.

Unfortunately, this didn’t resolve any issues for me on Win11. Still not detecting devices between Metagrid on iPad and Metaserver on Windows over Ethernet (Windows) and iPads (Wifi).

@automatic80 Please send us the logs from MetaGrid Pro and MetaServer.

MetaServer_Logs.zip (943.6 KB)

MetaGridPro-Support-Package-20260710-233652.zip (5.2 KB)

Sure - attached both logs.

Thanks for sending the diagnostics. We can see that both iPads are discovering STUDIO-W11 successfully through Bonjour and network broadcast, and MetaServer is responding to them. The failure happens afterward: MetaGrid Pro does not start the connection because its saved Wi-Fi connection type does not match the transport used to rediscover the same computer.

We have confirmed this as a MetaGrid Pro reconnect issue and added it to the 1.7.4 hotfix scope.

As a temporary test, please tap the Wi-Fi connection for STUDIO-W11 explicitly in the computer picker and let me know whether it connects. This will help confirm the automatic reconnect path while we prepare the fix.

Tried the temp test, but nothing happens when pressing the wi-fi on STUDIO-W11 computer picker on either iPad. On Metaserver, the WiFi remains idle with “no devices connected”. Looking forward to 1.7.4! :slight_smile:

Thanks for testing this. That is an important result: the problem is not limited to automatic reconnect. Explicitly selecting the Wi-Fi connection for STUDIO-W11 also fails to start a connection on both iPads.

We have started a deeper investigation covering both MetaGrid Pro and MetaServer Windows. We are tracing the connection from server discovery through manual selection and the connection request, and comparing the Windows behavior with MetaServer Mac.

This remains in the MetaGrid Pro 1.7.4 hotfix scope. I will update this thread when we have identified the exact cause or have a build ready for verification.

I’m still having to manually force quit the iPad app each time I power up the studio. I can click the Wi-fi computer picker, hit refresh, and it gives me “Connection Failed”. Once I force quit the app, it connects fine. This is on 2 different iPads connecting to the same computer.

After the latest update I have much better experience connecting two iPads on PC with latest MGP and not using Loop MIDI, the only time I have a problem turns out Cubase does not load the midi remote driver in some projects which seems to be Cubase related.

Important note: When I disable IPv6 and toggled Enable TCP to “OFF”, the iPads do connect now. Get a warning about stability (“needs attention”) with fluctuating reponse time, but I do get a connection. If I enable TCP and disable “disable IPv6” (sorry, those toggles are strangely worded) the connection will not work…and it specifically has to be both of these settings changed. Doing one or the other does nothing.

Thanks for the update. Before force-quitting MetaGrid Pro the next time this happens, please export a Connection Monitor support package from one of the affected iPads and collect the MetaServer logs.

Please send both files from the same failed connection attempt, before restarting either MetaGrid Pro or MetaServer. This should show which connection state is cleared when the app is restarted.

Status update: these corrections have been implemented and are currently included in the MetaGrid Pro 1.7.4 Hot Fix beta.

This post is primarily an informational update for everyone following this issue. If you are already a member of the beta program, you are welcome to verify the corrections and report the result here. If you are not a beta tester, no action is required—the corrections are planned for the upcoming production hotfix.

The beta downloads and TestFlight build are available only to authorized beta testers, so the linked beta resources may show “Access denied” for other forum members.

Beta testers can use MetaServer Mac 6.1.4 Beta 1 or MetaServer Windows 6.0.4 Beta 1 from https://forum.metagrid.app/t/latest-metaserver-beta-builds.

Please test both automatic reconnect and explicit selection from the computer picker over Wi-Fi and USB. If a failure remains, capture matching MetaGrid Pro and MetaServer support packages immediately after the failed attempt, before restarting either side.