Conflicting flag directions for sub-beams
Steps to reproduce bug
1. Open "David.mscz" (attached below)
Expected behavior: 32nd beam should point the same direction as the 16th beam immediately above it. (See LilyPond reference rendering at the bottom half of "Capture.PNG")
Actual behavior: 32nd beam points an opposite direction from the 16th beam immediately above it. (See highlighted notes in the top half of "Capture.PNG").
Discussion: I guess the more important rule in this instance is to point the same direction as the beam one level higher. If the beams on either side are equal then the current algorithm is correct (see measure 2).
MuseScore version: 0.9.6 stable.
(Operating System: Windows 7)
first reported by chen lung: http://musescore.org/en/node/6371
| Attachment | Size |
|---|---|
| David.mscz | 1.69 KB |
| Capture.PNG | 74.16 KB |
Comments
With the attached score, click on the the first chord and click 'double dot'.
It applies it to the next chord (with the flag direction issue).
Is this error related? Using 0.9.6.3 and 10.4.11.
fixed in r3772
#2: flags look ok now in Flags.mscz
Seems hard to port back in branch no? Something that can be done?
Automatically closed -- issue fixed for 2 weeks with no activity.
Is it fixed?
Found it in 3953.
cheng lung, this is fixed on the "trunk", not the stable "branch". To understand these two terms read the last section of How to write a good bug report: step-by-step instructions , "Responses".
I thought the nightly build (3953) was the trunk? That's what I tested it on.
Okay, then I'm unable to reproduce.
I opened "David.mscz" (above) in nightly trunk r. 3955, Windows 7.
Odd!
I have the 1.0 pre-release 2 in the same place (both that and the Nightly Build are on the desktop). Using Mac 10.4.11.
I think it's fixed in MuseScore 2.0 nightly build (3996).
Actually, I'm not sure it is now (looking at another score ).
Perhaps partially?
Using MuseScore 2.0 nightly build (3996).
Marking as active since cheng lung's file still shows problems.
http://musescore.org/sites/musescore.org/files/Abrupt%20Note.mscz
3.jul (ws) - fixed subbeam logic
Does this entry in the log refer to this issue? It's still active (using this ).
Using MuseScore 2.0 Nightly Build (4483) - Mac 10.6.8.
fixed in r4524
Automatically closed -- issue fixed for 2 weeks with no activity.