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