MetaGrid Pro 1.6.19 brings connection reliability improvements, a storage cleanup, and a clearer view of your purchases.
Important: MetaServer Mac 6.0.1 needed:
https://forum.metagrid.app/t/metaserver-downloads/24/8
IMPROVED:
- Settings → Subscription Plans now lists all your purchased add-ons and presets
- Briefly switching to another app no longer drops the server connection (stays alive up to 30 seconds in the background)
- Custom icons are now capped at 512×512 px — a one-time cleanup runs automatically if MetaGrid Pro was using several GB of storage
FIXED:
- Grid Sync now delivers to the correct device
- Grid import from Files or AirDrop no longer gets interrupted by a disconnect
- Fixed auto-reconnect after a WiFi heartbeat timeout
- Fixed connection failures on servers with multiple network interfaces
- Fixed Early Supporter purchase restore
If you’re still experiencing any connectivity issues after updating, please let us know in this thread — and if you can share logs from MetaGrid Pro and MetaServer, that will help us investigate quickly.
1 Like
Support ticket has been submitted. My iPad will connect for a few moments then continuously ask me to reconnect to my computer. I’m on Windows 10
Metagrid Pro Team,
Windows 10, Ipads 7-8 , OS 18.7.7
I’m writing as a long-time user who genuinely appreciates the concept and potential of your software. Metagrid Pro has become an important part of my workflow, and that’s exactly why I feel the need to raise this concern.
Over the past couple of years, both I and many other users on the forum have repeatedly encountered stability issues. While it’s great to see ongoing development and new features being introduced, the core experience is still too unreliable. Frequent disconnections, crashes, and inconsistent performance make it difficult to depend on the software in real working conditions.
At this point, the main issue isn’t a lack of features — it’s stability. Many of us find ourselves spending more time troubleshooting and reconnecting than actually working on our music projects. This turns what should be a powerful creative tool into a source of frustration.
I kindly ask you to consider prioritizing stability and reliability over adding new features. A solid, dependable foundation would make a far bigger difference to users than additional functionality that we can’t consistently use.
There is a lot of goodwill in the community, and people truly want Metagrid Pro to succeed. Focusing on fixing crashes, improving connection reliability, and ensuring consistent performance would go a long way toward restoring confidence.
Thank you for your hard work and for listening to your users.
Best regards,
Newest update with crash
End of the result IS , I wiped out completely all new updates and re-installed old Metaserver and 1.5.7 Metagrid.
Is there any place where we can re-download older versions of Metaserver and Metagrid for unpredictable situations like this ?
Hi Ivan,
Thank you for taking the time to write this up so thoughtfully — and for the trust you’ve placed in MetaGrid Pro as part of your workflow. We genuinely appreciate feedback like this.
We hear you on stability. If you look through the changelog, the majority of our releases over the past year have been focused exactly on what you’re describing — connection reliability, crash fixes, and under-the-hood improvements. This is already our top priority, and it will remain so.
That said, we want to be honest about the nature of these issues: MetaGrid Pro operates across an enormous range of hardware and software combinations — different iPads, macOS and Windows versions, Wi-Fi routers, USB configurations, DAWs, and system permission setups. Many of the problems users experience are highly setup-dependent and simply do not reproduce on our test systems. Without logs and a detailed description of the specific scenario, we are often working blind.
This is exactly why we need your help. If you are experiencing crashes or disconnections, please reach out directly at help@metagrid.app, describe your setup and the exact situation where the issue occurs, and attach the logs from MetaGrid Pro and MetaServer. That information is invaluable and directly feeds into our fixes.
