Stem direction not automatically redrawn when beam direction is not explicitly changed.

• Oct 28, 2017 - 23:07
Reported version
2.1
Type
Functional
Severity
S4 - Minor
Status
active
Project
MuseScore

Open the attached file.
Set the beaming for the A on the second beat to middle.
Set the beaming on the C to either none or start

Expected result: Stem direction on the C changes to down

Actual result: Stem direction remains up.

Note: Selecting the C and pressing ctrl+R sets the direction correctly.

I used 5 notes, because that is how I found the bug. It only requires 4 notes to reproduce. The duration of the note, as long as it's beamed, doesn't seem to have an affect. I tested this with a couple of other beams like this, and the stem remained wrong. It also displayed the wrong stem direction when the beam is down and the lone note should have an upward stem. This is not limited to the last note either. I also found this when I had a series of notes connected and one in the middle is set to no beaming. This does not seem to happen if there are only 2 or 3 beamed notes.

Attachment Size
stem direction.mscz 3.47 KB

Comments

• Oct 29, 2017 - 16:29

Actually, the stem direction fixes itself as soon as the score is laid out for any reason - even just pressing Ctrl+A. So it's just a temporary glitch. But of course, still a bug, and should be fixed. It happens in master/3.0 builds as well, but since that version will have more intelligence about what needs to be laid out, Ctrl+A doesn't fix it. You need to actually edit something to force MuseScore to re-layout that measure.

Reply

• Feb 15, 2018 - 21:32
Title Stem direction not updated when beaming is changed. ⇒ Stem direction not automatically redrawn when beam direction is not explicitly changed.

Came up again in #262215: Stem direction not automatically redrawn when beam direction is not explicitly changed..

The name was updated to indicate what is actually happening. If the beam direction should be changed, but the user does not explicitly change the stem direction it is not redrawn until the next time MuseScore redraws the measure.

Some things the user does that does not explicitly change the direction includes removing a note from a group of beams. For example, an A on the treble clef should have the beam up in voice 1. If the note was part of a beamed group with the beams pointed down, the A will remain with stem down until the user does something else to cause the note to be redrawn.

Reply