Stacked Dynamics in Chords in the Same Voice

• Aug 2, 2020 - 14:22

OS: macOS High Sierra (10.13), Arch.: x86_64, MuseScore version (64-bit):, revision: 148e43f

This might not be a bug, but it definitely feels like an unintended feature. When you select a chord and try to apply a dynamic from the palette by double clicking, it applies the dynamic to each note of the chord, so you get multiple dynamic markings stacked on top of each other. I don't think I have to explain why this is not just unintuitive but a real bother. Please let me know if there is a workaround (besides just deleting one dynamic) or if there is some use case for this "feature" that I'm looking over.

Attachment Size
Musescore-Stacked-Dynamics.gif 2.81 MB


That is a range selection and MuseScore (IMHO rightfully) assumes you want to affect all notes in the selected range.
Better (correct) workflow: enter the notes and then without leaving note input mode double click the desired dynamic

In reply to by Jojo-Schmitz

Well then agree to disagree. As far as I can tell this only happens to dynamics, not articulation or line elements, and dynamics can't be copied in this way, so it only happens when selecting from the palette, which is unintuitive. If this is intended to be a feature which users can reliably, it should apply to ALL types of elements and in ALL situations. And I disagree that there is a "correct" workflow. What you described is the intended workflow, but IMO software like MuseScore shouldn't railroad the user like that.

In reply to by tvav

That's why I put "correct" in parens. You asked for a better way, that is it.
Feel free to file a "suggestion" in the issue tracker for getting this changed/improved, but a range selection for applying dynamics doesn't really make any sense (even if it seems to in that specific one chord case)

scusi per la domanda non inerente all'argomento ma volevo sapere che software usa per fare il video.gif in allegato.
Grazie per una sua risposta.

AFAIAA, MS3.5 in its tentative state (release candidate), and presumably with its future actual release will/does not apply multiple dynamics to a chord when highlighted via range-selection. A real workaround, therefore, is to use 3.5 when released, and until then use the release candidate:

Do you still have an unanswered question? Please log in first to post your question.