Art Conductor in Logic Pro 12.3

Thanks for the detailed report. Let’s start with one simple check using a single affected articulation, such as Glissando Up.

First, select that articulation directly from Logic Pro’s Articulation Set dropdown and confirm that it works. Then select exactly the same articulation from MetaGrid and watch the dropdown in Logic.

Please let me know whether the Logic dropdown:

  • changes to the correct articulation;
  • changes to a different articulation; or
  • does not change at all.

If possible, please attach a short screen recording showing both tests. This will establish whether the problem occurs before Logic receives the selection or later when the articulation set sends its CC3 variation to SINE Player.

Hi, here we go :

Articulation “Glissando Oct Up” :

First, select that articulation directly from Logic Pro’s Articulation Set dropdown and confirm that it works.

-> it works after the 1st strike of a midi note

Then select exactly the same articulation from MetaGrid and watch the dropdown in Logic.

-> it changes to Glissandi Trill 2oct

Articulation “Waving Long”

First, select that articulation directly from Logic Pro’s Articulation Set dropdown and confirm that it works.

-> it works

Then select exactly the same articulation from MetaGrid and watch the dropdown in Logic.

-> no change at all

I made a screenshot video capture you can find here

Thank you for running these checks and providing the screen recording. The results clearly show that the problem occurs before SINE Player processes the articulation: one MetaGrid selection changes Logic to the wrong articulation, while the other does not change the selected articulation at all.

I will analyse the affected articulation mappings together with Rinus and compare the MetaGrid/PlugTools selections with the corresponding Logic articulation IDs. I will update this topic when the cause has been identified or when we need any additional information.

I do actually have the same problem as Zikayan. However I haven’t found a solution yet. Everything is set up. But the Test from PlugTools to Metagrid doesn’t work. However using shortcuts from PlugTools on my MetaGrid profile do actually work, just the connection to Art Conductor doesn’t.

Status: No Data received .

In my case, I think it has to do with metaserver itself as the logs always shows that the Midi Port Setups do not work.

Hi, any news about our issue with Peteris Vasks Strings articulations ?

Thanks for following up. We still have your examples and screen recording: Glissando Oct Up selects Glissandi Trill 2oct, while Waving Long does not change the articulation when triggered from MetaGrid, although both work from Logic’s Articulation Set menu.

This appears to be specific to the Art Conductor/PlugTools handling of these Peteris Vasks Strings articulations and their CC-based variations. We will follow this up with Rinus.

In the meantime, could you confirm whether the same two examples still fail with the latest PlugTools version and the latest Peteris Vasks Strings articulation sets? Please include the exact versions currently installed.

Hi there, thanks for paying attention to that particular case.

My Plugtools version is 5.3 build 2.

Art Conductor (including Peter Vasks Strings articulation sets) is 26.

Metaserver is 6.1.3

Hi again,

Babylon Waves just released a 26.8 version of Art Conductor with a fix : “FIX: Some Orchestral Tools instruments had MIDI channel set without reason”. No more precisions. I don’t know what it is actually about, but it doesn’t change anything to my particular issue.

Best,

Yan

Thanks for the details, Yan, and sorry for the delay. We have your recording and the two specific examples: Glissando Oct Up selects Glissandi Trill 2oct from MetaGrid, while Waving Long leaves Logic’s articulation unchanged. Both work from Logic’s Articulation Set menu. We’ve recorded PlugTools 5.3 build 2, MetaServer 6.1.3, and your finding that Art Conductor 26.8 did not resolve this issue. You do not need to repeat those tests or send the recording again.

@Speakerfood, could you help compare how those two Peteris Vasks Strings selections are mapped in PlugTools with the corresponding Logic articulation IDs? In particular, does the selection differ between the Logic menu and the MetaGrid path with PlugTools 5.3 build 2 and Art Conductor 26.8? We have not confirmed where the mismatch occurs or a fix.

Yan, when convenient, please share your current Logic Pro and MetaGrid Pro versions and builds. We’ll update this thread when the comparison gives us a concrete finding or next step.

Hi,

Logic Pro is 12.3.1

Metagrid Pro is 6.1.3 Build 4335

Thanks, Yan—that confirms Logic Pro 12.3.1. It looks like 6.1.3 build 4335 is your MetaServer version. Could you also share the MetaGrid Pro version and build from your iPad?

Rinus has replied and said he’ll look into the Glissando Oct Up and Waving Long issue today. We already have your recording, so there’s no need to send it again. We’ll update this thread when we have his findings.

I’ve confirmed that from the PlugTools side everything works as expected. This is what was tested:

PlugTools 5.3b2, MetaServer 6.1.6, MetaGrid Pro 1.7.7, Art Conductor 26.8.0
Loaded ‘02 Violin I First Chair Gestures’ on an instrument track
MetaGrid shows all articulations
Tested every articulation, LP switches correctly as seen from the drop down menu in the Plug-In window

However, I don’t own the library itself so I can’t test if the articulation actually triggers the correct variation in the instrument itself, so I’m passing this issue to Babylonwaves.

Thanks, Rinus, for checking this and for passing it to Babylonwaves. Your test confirms that articulation selection responded correctly in Logic. Since you don’t have the Peteris Vasks Strings library, the actual instrument behavior remains unverified.

We’ll await Babylonwaves’ findings on Yan’s two reported cases: Glissando Oct Up selecting Glissandi Trill 2oct, and Waving Long not changing the articulation when triggered from MetaGrid, while both work from Logic’s Articulation Set menu.

Yan, we still have your recording and examples, so there’s no need to repeat the tests or resend anything at this stage. The case remains open pending Babylonwaves’ investigation.