# Art Conductor doesn't connect to Metagrid/PlugTools **URL:** \ **Category:** Logic Pro\ **Created:** [September 12, 2026, 12:31pm UTC](https://forum.metagrid.app/t/art-conductor-doesnt-connect-to-metagrid-plugtools/1630 "2026-09-12T12:31:25Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Niclas](https://avatars.discourse-cdn.com/v4/letter/n/ba8739/32.png) [@Niclas](https://forum.metagrid.app/u/Niclas)\ **Post date:** [September 12, 2026, 12:31pm UTC](https://forum.metagrid.app/t/art-conductor-doesnt-connect-to-metagrid-plugtools/1630/1 "2026-09-12T12:31:26Z")
Hi, I’m having trouble getting Art Conductor to work in MetaGrid Pro. PlugTools connects to Logic Pro without any issue, but the Art Conductor connection to MetaGrid never comes up — MetaGrid’s status stays on “No Data Received” no matter what I try. **Setup:** - MetaServer: 6.1.3, Build 4335 - PlugTools: 5.3, Build 2 - Art Conductor: Art Conductor 26 (Logic) - macOS 26.6.2, Apple Silicon, German keyboard layout - Connected via USB, iPad **What works:** - General MetaGrid Pro controls - Logic Pro shortcuts/commands - PlugTools shortcuts I’ve set up myself - Test Logic Pro Connection in PlugTools → Passed **What doesn’t work:** - Test Metagrid Connection in PlugTools → never completes. It asks me to perform an action to test the connection, but the test just hangs waiting for that action indefinitely. - MetaGrid’s Art Conductor object shows Status: No Data Received permanently. **MetaServer console log (on every launch):** ```auto [midi-port] MIDI client created [midi-port] created source port: Metasystem – MIDI – In [midi-port] created destination port: Metasystem – MIDI – Out [midi-port] FAILED MIDIPortConnectSource for port 0 (Metasystem – MIDI – In): OSStatus=-50 [midi-port] FAILED MIDIObjectSetIntegerProperty(uniqueID=0) for midiPortIn0: OSStatus=-50 [midi-port] port 0 initialized (metasystem) [midi-port] created source port: Metasystem – StudioPro – In [midi-port] created destination port: Metasystem – StudioPro – Out [midi-port] FAILED MIDIPortConnectSource for port 2 (Metasystem – StudioPro – In): OSStatus=-50 [midi-port] FAILED MIDIObjectSetIntegerProperty(uniqueID=0) for midiPortIn2: OSStatus=-50 [midi-port] port 2 initialized (studioOne) [midi-port] created source port: Metasystem – Logic – In [midi-port] created destination port: Metasystem – Logic – Out [midi-port] FAILED MIDIPortConnectSource for port 3 (Metasystem – Logic – In): OSStatus=-50 [midi-port] FAILED MIDIObjectSetIntegerProperty(uniqueID=0) for midiPortIn3: OSStatus=-50 [midi-port] port 3 initialized (logic) ``` All three MIDI ports MetaServer creates fail with the identical `OSStatus=-50` error, every single launch — including right after a full Mac restart, so it’s not a session/cache issue. Since it hits every port and not just one, it looks like it sits in MetaServer’s own MIDI setup rather than being specific to PlugTools or Art Conductor. Is this a known bug, and is there a fix or workaround? ---
**Author:** ![MetaGrid\_Admin](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/metagrid_admin/32/21_2.png) [@MetaGrid\_Admin](https://forum.metagrid.app/u/MetaGrid_Admin)\ **Post date:** [September 16, 2026, 8:43am UTC](https://forum.metagrid.app/t/art-conductor-doesnt-connect-to-metagrid-plugtools/1630/2 "2026-09-16T08:43:13Z")
Thanks for the detailed report and for including the connection-test results. We have recorded misleading MIDI startup diagnostics in MetaServer 6.1.3, so these log lines alone do not establish why Art Conductor receives no data. MetaServer Mac 6.1.5, build 4342, is now available. Could you please update and retest with that version? Please also let us know: - Your MetaGrid Pro version and build - Your iPadOS and Logic Pro versions - The selected track and Art Conductor articulation set - The exact action you perform during the PlugTools “Test MetaGrid Connection” test If the test still waits indefinitely, please send the MetaServer and MetaGrid Pro support packages privately to [help@metagrid.app](mailto:help@metagrid.app) immediately after reproducing it. Please include the test time and timezone so the two packages can be correlated. We have not yet confirmed that the newer MetaServer version resolves this particular Art Conductor failure, so the current-build result will help us isolate the functional problem from the older diagnostic messages. ---
**Author:** ![briansteckler](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/briansteckler/32/487_2.png) [@briansteckler](https://forum.metagrid.app/u/briansteckler)\ **Post date:** [October 19, 2026, 11:21pm UTC](https://forum.metagrid.app/t/art-conductor-doesnt-connect-to-metagrid-plugtools/1630/3 "2026-10-19T23:21:55Z")
EDIT: I found the pesky checkbox in the PlugTools Preferences, Art Conductor Tab. Sneaky that that one is left unchecked on install. I’m having this issue since installing PlugTools over PlugSearch. I’m on MetaServer 6.1.6 4346 iPad version 1.7.7, Logic 12.3.1 Same on all my tracks with articulation sets. Tried reassigning the sets, no change. Looking in the PlugTools Console I see “Warning UDP Received, but Connect To MetaGrid not enabled” ---
**Author:** ![MetaGrid\_Admin](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/metagrid_admin/32/21_2.png) [@MetaGrid\_Admin](https://forum.metagrid.app/u/MetaGrid_Admin)\ **Post date:** [October 24, 2026, 7:15am UTC](https://forum.metagrid.app/t/art-conductor-doesnt-connect-to-metagrid-plugtools/1630/4 "2026-10-24T07:15:40Z")
Thanks for posting the solution, Brian! Glad you found it and got the connection working. For anyone encountering the same “Connect To MetaGrid not enabled” warning, check that **Connect to MetaGrid** is enabled in **PlugTools → Preferences → Art Conductor**. Niclas, could you check that setting too and let us know whether it resolves your original connection issue?