when using VSL Solo Strings, i’m trying to setup custom expression maps (key switches, like the espressivo patch) that are triggered by custom instruction words to trigger them in the notation script (like the word “espressivo”, similar to a “pizzicato” instruction in the notation script). Technically I understand the process of tying one to the other, but only some of these always work (like sul tasto, sul ponticello, pizzicato will always trigger the keyswitches by implementing the corresponding word in the notation script). Others however (custom made “espressivo” and others) are only getting triggered when being placed early in the script (as first or second), but not when they are coming after several other playing instruction words (coming third or fourth and so on). There is sort of a bug preventing it to work. Does anybody know how to fix this, or knows, what I’m doing wrong?
Could you upload a minimal project – just a few bars – showing the issue? Some things to check: Playing Techniques lane in Key Editor, Playback Technique articulation types (Attribute or Direction), Mutual Exclusion Groups.
If you have multiple playing techniques active at the same time, e.g., sul tasto and espressivo, you will need an additional entry in your expression map that combines both: sul tasto + espressivo
thank you for your replies. I’ve made a video to showcase the issue. It is on youtube, but I am not allowed to show it here. Is there any way to show it anyway?
The video instructions are repeated here:
"This video shows issues with Dorico Playback with custom expressions. Expression maps and settings for the notation instructions (the words “espressivo” and “pizzicato”) are shown. The notation instructions “espressivo” as well as “pizzicato” (as a test) are wired to trigger the VSL synchron Solo Strings: Violin I espressivo patch. The other notation words are wired to trigger their respective patches.
“Senza Sordino” triggers the senza sordino pathway (first order keyswitch) in the VSL synchron player. All following technques are coming from this branch (second to fourth order keyswitches).
You can see that in the beginning the “espressivo” instruction triggers the espressivo Patch (via keyswitches). “Legato” triggers the legato patch. Marcato however does not work. Pizzicato is wired to trigger the espressivo patch as well (as a test) and does so reliably. The “legato”, “espressivo” and “marcato” instructions do not work in bars 5, 6 and 7. Only in bar 8, the legato patch works again. The “espressivo” patch does not work in bar 9. However the “pizzicato” instruction works again and triggers the espressivo patch reliably."
It is in my opinion obvious that the issue is not the wiring of the expression map to the notation instruction. The “marcato” notation instruction didn’t trigger the marcato patch at all in this example. If I put the “marcato” instruction as second instruction, it works like the “espressivo” instruction. Like the “espressivo” instruction however, it stops working entirely after that.
The issue seems to be some sort of a cool down or a tilt with a quantity of data or some sort of blockage preventing some articulations to switch properly after a certain amount of prior keyswitches. I remember having had similar issues with Finale, only that the solution there seemed to be to not use more than 2 actions at once (2 keyswitches or 1 keyswitch+1CC-Change at once). That is why I created a branch structure, to trigger keyswitches consecutively instead of simultaneously, to prevent an overload with instructions that the program cannot handle.
If you could post a minimal project which demonstrates the issue, that’d be helpful. From your description, I think I understand the symptoms, but as to what’s causing it, there are many factors at play.
Have you checked the Playing Techniques lane in Key Editor to confirm Dorico is selecting the desired expression map switches at each moment?
I suspect the problem is down to a misconfiguration in your expression map, but without a project that allows us to reproduce the problem, it’s impossible to say.
Thanks for sending the project. I have little time now, so here’s some very quick info. If someone else hasn’t chimed in later, I’ll come back to this.
It appears to be an issue with how your Playback Techniques and expression map are configured. By the time marcato appears in m3, there are 3 active techniques (espressivo + legato + marcato), and since you don’t have a switch in your expression map which matches all 3 (together), Dorico selects Legato, which isn’t what you want. To fix this, you probably want to organize the Mutual Exclusion Groups to automatically cancel certain Playback Techniques set to Direction. Or, you can add switches with multiple Playback Techniques.
Also, Marcato is set to Attribute, which you might or might not want.
Ok, here’s more info. I think it’d be helpful to review 3 things to resolve the issue I mentioned:
Playing Techniques editor (lane in Key Editor) - This is essential reference when troubleshooting playback. Hover over the regions to view various info. There are fundamentally 2 parts of the flow (in the generic sense) from note to VST: (a) Playing Technique > Playback Technique > expression map switch, and (b) expression map switch actions > VST. The goal of “a” is selecting the correct expression map switch, and the Playing Techniques editor shows this. If the correct switch is not selected, you can focus on fixing “a”. If the correct switch is selected, you can focus on fixing “b”.
Playback Technique articulation type - This determines which notes Playback Techniques affect. There are 2 articulation types, Direction and Attribute, which are selected in the Playback Techniques dialog. See how changes here are reflected in the Playing Techniques editor.
Mutual Exclusion Groups - These set certain Playback Techniques to be cancelled when others are selected. Again, see how changes with these are reflected in the Playing Techniques editor.
Your issues seem to stem from “1a”, so I’d try sorting out 2 and 3. I’d also suggest implementing the Natural Playback Technique as it’s the baseline switch, and used, among other things, by the ord. Playing Technique.
Also, you appear to have ended up with two (different) definitions of marcato in your playing techniques (one in the common category and the other in strings). I don’t know how Dorico would try to interpret this.
thank you very much for your answers. As of now, I haven’t had the time to go deeper into this. It seems to be complicated. I can say though that youre right Eggsalad in that there are overlapping commands blocking each other. Is there any tutorial you can recommend to program expression maps to avoid these problems?