you are correct that LogicPro unfortunately only offers three keyswitches per articulation, it used to only offer one!

But still three is often not enough. You can write your own Scripter scripts. Its actually not that difficult to write a simple scripter script that will insert 5-6 keyswitches per articulation ID. I can do a tutorial on that if there is enough interest. Its obviously not as easy as adding them directly to the articulation set, but once you do one script like this, the 2nd and 3rd scripts would be relatively easy. I can write a script in literally 10 minutes that will handle the keyswitches for a Synchron instrument...its not a big deal...but it does require a little bit of scripting prowess, which a lot of orchestrators don't have and don't have any inclination to learn...so I get that...

@Telemachus said:

Hello,

I am looking for a workaround with as minimal configuration effort and as close to the original synchron presets as possible.

Another option if you’re not wedded to Logic Pro is to use Studio One, where VSL has recently used S1’s Sound Variations API so that all the articulations are automatically available to you for all Synchron and Synchron-ized products. 

See https://www.vsl.co.at/en/News/VSL_StudioOnehttps://www.vsl.co.at/en/News/VSL_StudioOne 

I switched from Logic to S1 for this reason (admittedly as a newbie, so I hadn’t invested a lot of effort into Logic).  But S1 is very intuitive, and it’s incredible to be able to have all of Synchron Strings Pro’s 127 articulations available instantly.  Or the 3420 artics of Sy Dim Strings I ! (well, that eye popping number is because of the 6 string position options and 8 group configurations.)  Not to sound like a shill for S1, but you can try it for a month for $15.

Still crying wolf, xxx (aka the dude who has the answer to life, the universe and everything, lol)? Of course you didn't mention that Ivan gave you the spanking you deserved for trying to publicly trash his good product and good professional reputation. In your world of one, nobody is allowed to take offence at your offences uh?

Here is a short tutorial I posted on the LogicForum 10 months ago with an example script for handling keyswitching using LogicPro Scripter.

https://www.logicprohelp.com/forum/viewtopic.php?f=45&t=149373&p=781561&hilit=keyswitch#p781561

It can easily be expanded to as many keyswitches per articulationID as you want.

I am going to post a little more info to that thread today also..  I would post these tips directly here, but this forum has very limited formatting options so its easier to explain more clearly at the other one dedicated to LogicPro.

for that, check out the input "switch" section of the articulation set.  You can set it up so that as you play in your parts, you hit some designated keyswitches (which do not necessarily need to match the output keyswitches)...and by those keyswitches, LogicPro will automatically assign an articulationID to each note as you play it in.  Check that out and see where you get, if you are comfortable with performing the keyswitches that way, its a nice way to play in your part and end up with articulationID's in your track instead of embedded keyswitches.

also, when you use the input switch mechanism to automatically assign art id's as you perform....the notes getting assigned articulationID's will echo THRU the script and into your instrument...so... what I mean is you can use whatever set of keyswitches you want for performing the parts in and assigning art id's based on those keyswitches...  Then LogicPro will echo those notes through the articulation set output section which ordinarily might include completely different keyswitches then whatever was used for the input.....or...in this case if you are going to use a script, then leave the articulation set OUTPUT section blank...and the script will add those output keyswitches..including while you're performing it in...you'll hear the correct articulation as you play because that mechanism will do it both while you perform it and later when you play it back...based off the articulationID.

Hope that makes sense.