Hi everyone,
Since updating to Dorico 6.0.2, I’ve noticed two changes in dynamics behaviour that feel like regressions compared to how things worked before. I’d like to know if others are experiencing the same issues, and whether these are intentional changes or bugs.
Issue 1: Existing dynamic gets deleted when adding a hairpin+dynamic via popover
Steps to reproduce:
- Place an mf dynamic on a note (e.g. a chord: B + F)
- Select the note and open the dynamics popover (Shift+D)
- Type
>p and confirm
Expected behaviour (pre-6.0.2): The mf is retained, and the hairpin + p is added after it, so the result is mf > p.
Actual behaviour (6.0.2): The existing mf is deleted, leaving only the hairpin + p.
This is quite disruptive to my workflow, as I often build up dynamics incrementally. Is there a new way to achieve the old behaviour, or is this an unintended regression?
Note: this happens only outside of Note Input Mode
Issue 2: Dynamics applied to both voices on a two-voice chord
Steps to reproduce:
- Have a chord where the two notes belong to different voices (e.g. B in Voice 1 stem up, F in Voice 1 stem down)
- Select the chord and add a dynamic via the popover
Expected behaviour (pre-6.0.2): The dynamic is applied only to the selected voice.
Actual behaviour (6.0.2): The dynamic is applied to both voices simultaneously, resulting in duplicated dynamics.
Has this behaviour been changed intentionally, or is it a bug? How can I go back to the previous behaviour?
Thanks in advance for any clarification. I’m happy to provide a project file if that would help diagnose the issues.
The second case is a bug - we hope to be able to fix that in a forthcoming release.
The first case is a result of some bugfixes and improved consistency in this area - previously it was possible to end up appending dynamics even where this didn’t make any sense. What I would suggest if you want to preserve the existing dynamic is that you select the “mf” dynamic itself (rather than the note), hit Enter, then right-arrow to the end of the popover and then type in “>p”.
2 Likes
Thank you very much for the quick and clear response, it’s really appreciated.
Regarding the first case: I completely understand the reasoning behind the change, and I’m glad the team is working towards greater consistency. That said, I’d like to gently ask whether it might be possible to make the old behaviour available as an option, perhaps a preference or a modifier key, for those who relied on it as part of their workflow.
I’m well aware that I’m just one voice among many, and I don’t want to overstate my case. But I’ve been working this way for years, and given the nature of my work (I enter dynamics constantly and in large quantities), the previous method was something I had deeply internalised. The workaround you suggested works, of course, but it does add a few extra steps that, multiplied over hundreds of dynamic markings, add up.
I imagine there might be others in a similar situation. If restoring the old behaviour isn’t feasible or desirable, I completely understand, just wanted to flag it as something worth considering.
Do you think it would be possible for me to go back to the previous version?
Thanks again for your time.
I also tried to select the notes, re-enter mf + >p, but this time that’s what happens:
I’m not sure, but I think this will be related to the bug I mentioned in my earlier post - one of the staves here has two voices, and Dorico isn’t handling that correctly.
3 Likes
Thank you for your replies, Richard. I’ve actually found a few other bugs, all related to dynamics, that made my workflow actually much slower. I really hope you guys look into those
It got fixed in the recent patch!