Take this note with a mf dynamic, you want to modify that dynamic with a decrescendo
You get the following
I’m curious, why didn’t this change the existing dynamic as I wanted? Confusing behavior to me, I keep hitting this. More confusing, the MIDI roll knows the right thing to do and only has a single mf>
Maybe there’s a good reason for this but I’m not following.
That’s a behavior I have experienced and I don’t think it’s really what the Team would want Dorico to do. I suppose it’s technically boring and problematic to solve.
I’ve experienced this as well. I’m just spitballing here, but I believe it has to do with the fact that the mf and mf> are two distinct types of objects… If you just change mf to ff, it will work because those are the same object types.
It’s unexpected behavior, but I’m sure there is a reason (my guess is above).
Dunno, but OOP wise I’d expect that the dynamic popover creates a dynamic object. Those are subclassed into volume (mf, f, …), volume change (<>), accent, etc. This design would be better encapsulation and separation of concerns, and is how you would be chain up successive dynamics, especially for playback. If that’s true then mf to mf> would just be adding a ‘>’ vol-change object after the volume object.
Anyhow this is all speculating; sounds like it’s not what users expect and it is a known issue, so probably in the backlog.
confusing and not what I’d expect but does the job 
