MetaGrid Pro — Known Issues and Bug Reporting Guide

Welcome to the MetaGrid Pro known-issues index. This topic lists confirmed,
user-visible issues that are currently being investigated, fixed, or verified.

Before creating a new bug report, please check the list below and search the
forum. If your symptoms match an existing issue, reply to its linked topic with
your versions, platform, and diagnostics. If they do not match, create a new
topic using the reporting checklist at the end of this post.

Last updated: July 12, 2026

Active known issues

Wi-Fi server is visible but does not connect

Status: Fix in progress for MetaGrid Pro 1.7.4
Affected: Confirmed with MetaGrid Pro 1.7.3, Windows 11 host over Ethernet, and iPads over Wi-Fi
Symptoms: MetaServer is visible in the computer picker, but automatic reconnect and explicit Wi-Fi selection may fail to start a connection.
Workaround: USB may remain available in some setups. If Wi-Fi selection does nothing, attach a MetaGrid Pro support package and MetaServer logs to the existing topic.
Discussion: Connectivity Improvements in 1.7.3

USB recovery after returning from another iPad app

Status: Investigating
Affected: Reported during MetaGrid Pro 1.7.3 testing; current production-version confirmation is requested
Symptoms: USB may reconnect slowly after MetaGrid Pro returns to the foreground, or remain unavailable until MetaServer restarts. Automatic Wi-Fi fallback may not occur.
Workaround: Manually selecting Wi-Fi may restore the connection. Capture logs before restarting MetaServer.
Discussion: https://forum.metagrid.app/t/1558/2

Mac wake can leave MetaGrid Pro on a black or unavailable screen

Status: Fix and verification in progress for MetaGrid Pro 1.7.4
Affected: MetaGrid Pro 1.7.2–1.7.3 with Mac sleep, display sleep, screen saver, or Lock Screen workflows
Symptoms: MetaGrid Pro on iPad or Mac may not return to its normal screen after the Mac wakes.
Workaround: Reconnect or restart the affected MetaGrid Pro/MetaServer session if normal recovery does not complete.
Discussion: [Needs Verification] Ipad metagrid, Mac metagrid do NOT wake up (on Mac wakeup) with a visible screen (Black)

AI Builder navigation can be hidden by Bluetooth keyboard controls

Status: Scheduled for MetaGrid Pro 1.7.4
Affected: iPad with a Bluetooth keyboard; confirmed on MetaGrid Pro 1.7.1 and later testing
Symptoms: The predictive-text or keyboard shortcut bar can cover the AI Builder Next control after typing.
Workaround: Temporarily disable the iPad keyboard shortcut/predictive control bar or dismiss the keyboard before continuing.
Discussion: [In Progress] AI Builder issue when using bluetooth keyboards with iPad

iPad wired-Ethernet-only connection is not discovered

Status: Confirmed; no release target announced
Affected: iPad connected only through a wired Ethernet adapter
Symptoms: Other local-network apps work, but MetaGrid Pro does not discover or connect to MetaServer. Enabling iPad Wi-Fi allows connection.
Workaround: Keep Wi-Fi enabled when using MetaGrid Pro.
Discussion: LAN connectivity?

MetaServer Windows shows an Ethernet address under the Wi-Fi label

Status: Fix planned for MetaServer Windows 6.0.4
Affected: MetaServer Windows 6.0.3 on computers with Ethernet and Wi-Fi interfaces
Symptoms: The status screen can display an Ethernet IPv4 address under the Wi-Fi label.
Workaround: Confirm the active interface and address in Windows network settings.
Discussion: METAGRID PRO APP shows incorrect WIFI ivp4 address

Cubase Selected Channel persistence requires verification on Windows

Status: Needs verification
Affected: MetaGrid Pro 1.7.3, MetaServer Windows 6.0.3, and Cubase 15
Symptoms: The Selected Channel MIDI Remote surface may disappear or become inactive after restarting Cubase. The plugin-list timeout path was fixed in MetaServer Windows 6.0.3, but persistence still needs confirmation.
Workaround: Reinstall or reload the Selected Channel integration and confirm that the current bundled script is installed.
Discussion: [Needs Verification] Cubase 15 + MetaGrid Pro Selected Channel not persisting / plugin list not loading (Windows 10)

Ableton Remote Script installation with a custom User Library

Status: Confirmed; under review
Affected: MetaServer Mac 6.1.2 when Ableton’s User Library is stored outside the default location
Symptoms: MetaServer installs the Remote Script under the default User Library, so Ableton does not offer MetaGrid Pro as a control surface.
Workaround: A symbolic link from the default Ableton User Library path to the configured external library works; a Finder alias does not.
Discussion: MGP, Logic and Live - bugs and wishes

Recently fixed

MetaGrid Pro 1.7.3

MetaGrid Pro 1.7.3 includes Connection Status diagnostics, improved support
packages, connection setup refinements, Cubase and Logic Pro improvements, and
multiple import/export and editing fixes.

Changelog: 📜 MetaGrid Pro Changelog - #24 by MetaGrid_Admin
Release announcement: MetaGrid Pro 1.7.3 Released

If a listed 1.7.3 fix still fails on your system, reply to its existing topic
with your current MetaGrid Pro, MetaServer, operating-system, and application
versions.

Before reporting a new bug

Please include:

  • MetaGrid Pro version
  • MetaServer version and whether it is Mac or Windows
  • iPadOS/macOS/Windows version
  • The controlled application and its version, when relevant
  • Connection type: USB, Wi-Fi, wired Ethernet, or a combination
  • Exact steps that trigger the problem
  • What you expected and what happened instead
  • Whether the issue reproduces after restarting MetaGrid Pro and MetaServer
  • A MetaGrid Pro support package and MetaServer logs captured immediately after reproduction

Do not post API keys, license information, email messages, private file paths,
or other sensitive data. If your report contains private information, contact
support instead of attaching it publicly.

Status meanings

  • Investigating — the symptom is confirmed or credible, but ownership or exact cause is still being established.
  • Fix in progress — canonical implementation work is active.
  • Needs verification — a fix or relevant build exists and customer/device confirmation is still required.
  • Fixed in X — the fix is included in the named production release.