Spiccato expression acts different for Vln I vs Vln 2

As you can see below, my expression maps for Violin 1 and Violin 2 are defined exactly the same, but when I apply them to notes, I get different results. The ‘spicc’ technique is being detected incorrectly as ‘staccato’ for Violin 1, but correctly as ‘spiccato’ for Violin 2.

For clarity, Violin 1 is assigned to channel 2 in the endpoint setup and Violin 2 is assigned to channel 4 in the endpoint setup.

Can you upload your project, pretty please?

Sure, give me a minute.

Ok, I don’t know why, but the expression maps are setup the same, but after I hacked and chopped in the copy of my project down to the two measures in question, the problem has gone away. For copyright reasons, I don’t want to send the complete project. Other than deleting everything but the affected two measures, that’s ALL I did. For some reason, deleting everything else fixed my problem, but obviously I can’t do that to my actual project.

Any ideas of what might be causing my problem?

The way I understand it, to display spiccato as notes with dots, you simply modify the ‘spiccato’ entry in the expression map to use the spiccato key switch as the assigned one and simply add the word ‘staccato’ to the name of the entry in the expression map like ‘spiccato + staccato’. Then when you notate with dots and the word, ‘spiccato’ over the affected notes, the spiccato will be active and the does will be there by virtue of the ’ + staccato’ in the expression map entry. Which, in my pared down version is the case.

What was happening is that for my Violin 2 the only difference I could tell was the expression map mutual exclusion rules had ‘staccato’ in the ‘string’ set, but not ‘spiccato’ because you obviously can’t have both in the mutual exclusion rules, otherwise what I’m trying to do as described above would not work. In the mutual exclusion rules for Violin 1 I had to remove BOTH ‘staccato’ and ‘spiccato’ from the mutual exclusion rules for some reason to get the spiccato effect I wanted.

If you’re finding that the problem goes away after cutting down the project, that suggests to me that another playing technique is active somewhere before the staccato+spiccato passage, and so Dorico is ending up trying to find a combination of this as-yet unknown playing technique together with staccato+spiccato. To test this theory, try adding a “nat.” playing technique just before the staccato+spiccato passage. Do you now get the expected playback?


That’s what it was. Thank, Daniel!