Stems of beamed notes don't respond to direction change in Inspector if beam direction conflicts

• Nov 12, 2017 - 04:01
Type
Graphical (UI)
Severity
S4 - Minor
Status
active
Regression
No
Workaround
No
Project
MuseScore

When I tried to select all the closed high-hat notes in a score (see snippet attached), using Select / More - Same staff, voice, pitch, and then redirect their stems upward using Inspector, Inspector says it changed them all to to point up but they are all still pointing down. After chatting with another user, this bug isn't just limited to drums.

"An additional note. I checked what happens when I try to flip the stems in the guitar also. When I selected one note, the stem would flip. When I selected to consecutive connected individual notes, they would not flip. When I selected the two chords as a selection, the stems flipped. I couldn't use the inspector to change stem directions at all on that either, so it seems this is not a drum problem but all beamed notes problem." (Mike320)

Attachment Size
Drum Closed High-hat stem direction bug.mscz 16.05 KB

Comments

• Nov 12, 2017 - 16:30
Title Stems of beamed ⇒ Stems of beamed notes don't respond to direction change in Inspector

The issue is that for beamed notes, the been has its own direction property that also needs to be set. We do this automatically if a single note is selected but not for multiple notes it seems.

Reply

• Nov 12, 2017 - 18:44
Title Stems of beamed notes don't respond to direction change in Inspector ⇒ Stems of beamed notes don't respond to direction change in Inspector if beam direction conflicts

Actually, it's not about whether multiple notes are selected or not - just a matter of whether the beam direction conflicts. if the beam direction is auto, then flipping the stem via the Inspector works fine. Only if the beam direction is explicitly set to in a way that conflicts with the desired stem direction does MuseScore give up. Still, we should consider "doing what I mean, not what I say" in this case.

Reply