I installed the Logic Pro 12.3 update today and since that moment plugtools no longer shows the Art conductor artsets that until last night worked perfectly!
I restarted, checked the setup, scanned the Art Conductor folder three times…nothing:
For the rest Metaserver and Plugtools works well but Art Conductor is Dead!
…I restored version 12.2 of Logic pro with Time Machine and everything is working again…!
Hi, quite the same issue here. : Os 15.7.7, Logic 12.3, Plugsearch 4.2 b73, Metagrid server 6.1.2. Logic connection test is ok, but Metagrid connection is not.
Edit : I’ve updated plugsearch to plugsound, same issue.
Thanks for the additional report. In PlugTools, please open Preferences → Art Conductor, uncheck Connect to MetaGrid Pro, and then check it again.
Next, click both Test Logic Pro Connection and Test MetaGrid Connection. Please report the exact status or message shown by each test after toggling the setting.
Logic Pro 12.3 is working correctly with PlugTools and MetaGrid Pro on our test systems, so this does not appear to be a general Logic Pro 12.3 compatibility issue.
Logic can reset some MIDI settings during an update. Please open Logic Pro → Settings → MIDI and check the following:
Under General, enable MIDI 2.0.
Under Articulation Switches, set MIDI Remote to On / Global.
Set MIDI Channel to All / Global.
Open the Inputs section and confirm that PlugTools is enabled.
After checking these settings, restart Logic Pro and PlugTools, enable Connect to MetaGrid Pro again, and run both connection tests. Please report whether Test MetaGrid Connection now responds.
all was set corerctly, I followed step by step the video tutorial from Rinus Aart. Except about midi 2.0, but it doesn’t change anything in my case, and “PlugTools” that appears as “Plugtools Output” in the midi inputs tab.
Could you explain why the very same logic session makes Art Conductor working fine under Logic 12.0.1, and non responsive under logic 12.3 ?
Prefs trashed, midi settings reajusted, same issue…
But I noticed a strange behaviour : although Art Conductor is responsive under Logic 12.0.1, the Test Metagrid Connection under Plugsounds still doesn’t work.
I have just opened my Logic Pro 12.3 session also and tested this with the EW Hollywood Strings 2 ArtConductor patches. When I first enabled PlugTools and started Logic with my two tracks (V1,VC) with loaded ArtConductor patches, I was not getting any readout on MetaGrid Pro either.
However, once I carried out the Test for Logic and MGP in PlugTools they showed up.
I am using Logic Pro 12.3, PlugTools (5.1 build 4 ‘Latest’) and ArtConductor 11.10.2 patches as I never upgraded to 26. This as due to my moving to Cubase 15 as my main DAW.
UPDATE: I have now tried this with the latest 26.6.1 patches from Babylonwaves for Logic Pro and they also display correctly.
Mac Studio M2 Max 64GB and 1TB storage macOS Sequoia 15.7.7 Logic Pro 12.3 MetaGrid Pro 1.7.3 (build 35819)
Thanks, here the Test for MGP doesn’t work, either if I’m running Logic 12.0.1 or 12.3.
By the way, Metagrid server “Check for update” always give me the answer “Update Error. An error occured in retriveing update information. Please try agin later”.
Rinus has released a PlugTools update that corrects this issue when Logic Pro is running in French, Spanish, Portuguese, or Italian.
Please update PlugTools to the latest available version and test the Art Conductor integration again. After updating, run both Test Logic Pro Connection and Test MetaGrid Connection, then confirm whether the Art Conductor readout appears correctly in MetaGrid Pro.
The MetaServer Check for Update error is a separate issue. You can install the current MetaServer directly from Download — MetaGrid Pro while that updater problem is investigated.
Hi. Plugtools updated to 5.3 b1. No change. Anyway, I already tried to change Logic in English, with no result. Art Conductor on the iPad is still erratic, and the Metagrid test still gives no result. I will try with another iPad, even if the one I currently use was working perfectly untill the updates. Please, could you tell me if my Metagrid plan could be the cause ? It says “Premium (Early Supporter)”, do I have to subscribe to unlock this issue ?
Hi Zikayan, if you test with the MetaGrid app on the computer itself, does it work? Then we can see if it is a Logic Pro / MetaGrid issue, or an iPad issue.
Using Metagrid app on the computer is giving the exact same behaviour : “Test Metagrid connection” gives no result, and the display of Art Conductor on the Metagrid app when I switch from track to track is still erratic : sometimes it works, most of time it doesn’t.
I’ve reached the point where I think I’ll do without Art Conductor from now on.
Thanks for the test, that confirms that its not an iPad connection failure. And I understand your frustration. Let me check with MetaGrid what might be causing the issue.
We’ve found the issue, in the latest release of PlugTools selecting a track with the mouse prevents track change detection - so MetaGrid is not updated. You can update PlugTools / PlugSearch, the latest version fixes this issue.
Hi Rinnus, as you answer here, I report to you an exchange with Babylon team about an issue with some of their articulation sets that use midi CC, in order to access every articulations of some libraries, in my case the Orchestral Tools “Peter Vasks Strings”. Those variations are controlled via CC03 by default in the Sine Player, but they are integrated on the Articulation sets of Babylon Waves.
Here is my post
“as far I tested, are concerned every Peter Vasks Strings articulations with variations (ensembles or 1st chair), for example : variations glissando up and down on Gestures instruments, or sublte and expressive vibratos on Main instruments, or Measured Trills HT WT min3… Actually those variations articulations are ok when selecting from the Articulation list plugin window, but not from the ipad Remote : they have an erratic behaviour, or they are ineffective. Maybe it’s related to the 1.4 version of Sine Player that handles CC and a new performance mode ?”
Babylon Teams answer
“The articulation selection works fine here when I use the built-in dropdowns in Logic. If those work strangely on your iPad remote, I suggest that you get in touch with Speakerfood.”
