Is there any chance you could add LAN connectivity to MGP???
I take the lack of an answer here as a NO???
Another Question… Are you ever going to get the MetaServer app signed by MS???
Apologies - I missed that one completely - here are the answers:
- LAN
LAN connectivity is already supported in MetaGrid Pro. In the app and docs it is usually shown as the “Wi-Fi” transport, but technically it works over the local network, so your computer can be connected by Ethernet while the iPad connects over Wi-Fi, as long as both devices are on the same LAN/subnet and can reach each other.
If automatic discovery does not work, it is usually caused by router isolation, guest Wi-Fi, VPN/firewall rules, or blocked local network permissions. In that case, you can use the IP address shown in MetaServer’s Network settings to add the computer manually in MetaGrid Pro.
- MS Signing
Yes, we will be signing MetaServer and the installer with Microsoft Trusted Signing - currently pending with MS.
my bad for not being clear enough here. I have a Ethernet network adapter connected to my iPad and my Desktop (Windows) is also connected via ethernet. So im taking about Ethernet to Ethernet via my router. Will MGP & MetaServer communicate over ethernet…???
Yes, MetaGrid Pro and MetaServer should communicate over Ethernet-to-Ethernet through your router, as long as both the iPad and the Windows desktop are on the same local network and can reach each other.
In MetaGrid Pro this connection may still be labelled “Wi-Fi,” but that button really means the local network/IP transport. It is not limited to wireless Wi-Fi only.
If the desktop does not appear automatically, use Manual Setup in MetaGrid Pro and enter the IP address shown in MetaServer’s Network tab. Also make sure Windows Firewall allows MetaServer on the active Ethernet/private network profile.
This isnt working for me. ipad can talk to desktop via R-Kontrol, TouchOSC, Fender Studio Remote, FLStudio Remote. So im not having a problem using ethernet from the ipad. Just cannot get MGP to connect via ethernet. The moment i enable Wifi on the ipad the connection is there.
@Muzik4Life Ok, thanks for the feedback - can you send the logs from MetaServer and MetaGrid - we will analyze it in depth and see what we can do to improve this.
So here is the funny thing.. I checked the logs to see if there was anything that would point be in the right direction… There isnt any data to do with failed attempts to connect via LAN. The log system doesn’t even see any attempts of me trying to connect via LAN at all.. Logs everything else but LAN connections.
Thanks, that makes sense now. This is not a general Ethernet/network issue on your setup.
We checked the MetaGrid Pro connection path and found that the current iPad network discovery code is still tied to the iPad Wi-Fi interface. So when Wi-Fi is disabled and the iPad is connected only through an Ethernet adapter, MetaGrid Pro may not send discovery/connect packets over that wired interface at all. That matches what you are seeing: MetaServer logs no LAN connection attempt, but everything appears immediately when Wi-Fi is enabled.
So yes, this is something we need to fix on the MetaGrid Pro side. For now the workaround is to keep Wi-Fi enabled for MetaGrid Pro, even if the desktop itself is wired by Ethernet. We’ll add proper iPad Ethernet adapter support so the local-network transport works over wired Ethernet as well.
Wifi isnt setup in my work space. The only stable connection i have is Ethernet. Please let me know when you have solved this problem. Thx.
Thanks for the additional detail. We have confirmed that this is a current limitation in the iPad discovery path: MetaGrid Pro can fail to discover or connect when the iPad is using only a wired Ethernet adapter.
The fix is scheduled for the MetaGrid Pro 1.7.4 hotfix, and a deeper review of discovery and connection handling has started for cases where wired Ethernet is the iPad’s only active network interface. I will update this thread when the fix is ready for verification.
1 Like
Status update: this correction has been implemented and is 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 correction and report the result here. If you are not a beta tester, no action is required—the correction is 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 install the matching MetaServer 6.1.4 Beta 1 for macOS or 6.0.4 Beta 1 for Windows from https://forum.metagrid.app/t/latest-metaserver-beta-builds.
Please test the new Local Network Interface setting in both Automatic and Wired Ethernet modes, including reconnecting after switching modes. Report the host platform, adapter model, connection result, and support packages from MetaGrid Pro and MetaServer.
Tried the link provided and its dead. Please add a working link. Thx.
Update. Link isnt dead (my bad) rather its says “access denied”. 
Thanks for checking. The link is working, but it points to a beta-testing area that is available only to authorized beta testers.
This topic was updated primarily to let everyone know that the correction has been implemented and is now being verified. If you are not currently a beta tester, you do not need to do anything—the correction is planned for the upcoming production hotfix.
MetaGrid Pro 1.7.4 is now publicly available and includes support for connecting an iPad through a compatible wired-Ethernet adapter.
In MetaGrid Pro, open Settings → Connections → Local Network Interface and select the wired-Ethernet interface. Automatic remains the default, while the explicit wired option performs a controlled network rebind without disabling USB.
Please update to MetaGrid Pro 1.7.4 and use MetaServer Mac 6.1.4 or MetaServer Windows 6.0.4, then let us know whether the iPad connects successfully in the Ethernet-only setup described in this topic.
i have to ditch Metagrid from my workflow. Completely unreliable on windows, problems take far to long to fix for me. and the recent update made all my templates non-functional.. I dont have the time to spend working out problems with this app.
Good luck with this project.
All the best.
Thank you for letting us know. The template problem appears to be separate from the original wired-Ethernet issue, and we would like to understand exactly what changed after the update.
Could you please tell us:
- Which MetaGrid Pro and MetaServer versions you are currently using?
- Which version you updated from?
- What does “non-functional” mean in this case: do the templates fail to open, appear incorrectly, or open normally but their buttons and commands no longer work?
- Does this affect every template or only particular profiles?
- If possible, could you send a backup containing one affected template to help@metagrid.app?
We understand that you do not want to spend more time troubleshooting. Even a brief description and one affected backup would allow us to investigate this without asking you to perform extensive tests.
Sorry but i just dont have the time right now to troubleshoot. I also cant have software/apps that fail to work as advertised then having to wait weeks/months for solutions. On the surface Metagrid is a great idea but for me metagrid isn’t baked enough for my to keep within my workflow, the app is just unreliable and where im working on big projects i need consistency. I will check back in the new year (time permitting) to see what progress has been made.
all the best.