Hello.
I’ve been creating an expression map for woodwinds. I setup two Portato articulations: Portato Long (triggered by Medium or longer Note Length) and Portato Short (triggered by lower than Medium Note Length).
The associated playing technique for both of them is Legato+Tenuto (I selected both to combine them in the selector as intended), and as described above via a Condition based on Note Length only one of them will be triggered.
When I tried it out I realized that, after a lot of testing, there is a bug that happens exclusively to notes which have BOTH a Legato Slur and the Tenuto markings: the bug causes their associated Note Length to be considered as Medium (or longer, I don’t know exactly how long) for the purposes of Condition requirements of Expression Maps, EVEN IF THEY ARE EXTREMELY SHORT (32th for example). This causes that it’s basically impossible to ever trigger the Portato Short this way, because no matter how short in duration the notes may be, because of the Legato+Tenuto they will be considered as Medium (or longer) Note Length.
I attach an screenshot, but based on my description it should be fairly easy to replicate.
Would you be able to attach an example project? This is much more helpful than a screenshot as we can see the whole expression map, playback options etc.
Hello.
For some reason, after I closed and opened Dorico, the bug fixed itself without me changing anything. Now the conditions for the expression map are properly applied. I should’ve tried that first I guess (I had been working for hours that day with Dorico always open and it just didn’t cross my mind).
I’ve kept the segment of music where the bug happened intact for now as I keep working on other expression maps. If the bug happens again I’ll post again with the project file but for now it seems it was a random thing that doesn’t seem to reoccur. Maybe a program restart was needed to update or reset some related data on the background or something.
1 Like
We have in the past had situations where the playback technique lane in the key editor wouldn’t correctly update after making edits to things that might affect playback (e.g. note duration, tempo). We think we’ve fixed those issues now, but it is possible that you’ve stumbled on a similar case. If so, it will be specific to a specific editing command, i.e. there will be some specific edit that doesn’t trigger the update when it should. Please let us know if you think you’ve found a command where this is going wrong.
1 Like
