Yes I know for which purpose were the add-ons created for and use them as planned with other libraries. But what I’m trying to do with VSL is based on the same idea. The thing is that it actually works fine except for the articulations that trigger a built-in behavior by Dorico. I also use a similar CC setup to access or cross-fade from ord. to ponticello or tasto, or from vib. to non vib. with no problem at all.
In the case I have submitted to you, the cc20 to 127 command of the tremolo add-on switch does overrule the cc20 to 0 command of the natural base switch and trigger the tremolo sound. The problem is with the build-in tremolo simulation that Dorico generates. It only complies with the command to '“stop the simulation when an external sound is assigned” when it’s done through a base switch. So when the add-on tremolo switch is activated, I get my tremolo sound with Dorico’s simulation.
So to get my tremolo sounds, my two options are:
- use base switches, meaning I have to program every possible combinations where a tremolo is possible, which amounts to hundreds of entries;
- use a fake technique that will not trigger Dorico’s build-in simulation. The problem with this comes from the fact that tremolos can only be excluded from playback by deactivating the notes they’re attached to. So to trigger a tremolo sound, I have to create a second staff, enter the notes with the fake technique, hide the extra staff… well, a pain.
That could all be avoided if Dorico’s built-in simulations (for tremolos and also for trills, harmonics…) could react to add-on switches the same way they react to base switches or at least, if there was a local on/off toggle to override them. I have no idea if it’s a big programming job for the team, but it sure would be appreciated.