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.