Stems too short for 32nd and 64th notes
Steps to reproduce bug
1. Add a 32nd note or 64th note to an empty score
Expected behavior: Stem lengths should increase to accommodate the large number of flags.
Actual behavior: Stem lengths remain constant so 32nd and 64th flags extend past the note head.
Research:
Finale lengthens stems by one space for each addition flag starting from 32nd note.
- 32nd note stem: 1 space longer
- 64th note stem: 2 spaces longer
- 128th note stem: 3 spaces longer
Sibelius' flags are closer together than Finale's so it only lengthens stems by 3/4 space for each additional flag
- 32nd note stem: 3/4 space longer
- 64th note stem: 1 1/2 spaces longer
- 128th note stem: 2 1/4 spaces longer
LilyPond lengthens the stems by 3/4 space for each additional flag but then rounds up to the nearest 1/2 space.
- 32nd note stem: 1 space longer
- 64th note stem: 1 1/2 spaces longer
- 128th note stem: 2 1/2 spaces longer
Recommendation: LilyPond's stem lengths are the most sophisticated and produce the best results for MuseScore (The flags in the font MuseScore uses are especially designed for the stem lengths as they appear in Lilypond).
MuseScore version: 0.9.6.3 stable
(Operating System: Windows 7)
first reported by chen lung: http://musescore.org/en/node/7409
| Attachment | Size |
|---|---|
| Capture.PNG | 25.36 KB |
| stem lengths.mscz | 1.81 KB |
Comments
fixed in r3564
Stem length for 16th notes should remain one at one octave. The extra length shouldn''t start until 32nd notes. I corrected this in r. 3571 trunk.
Automatically closed -- issue fixed for 2 weeks with no activity.
Don't think it's fixed (2.0 pre-release - 3953).
See this .
This bug report is about the initial stem lengths for staves that are using voice 1 only. Multi-voice context adds some additional complexities (stem lengths are intentionally shortened but maybe too much). The thread you are linking to needs to be a separate bug.
It was nothing to do with voices - I had only used one.
Anyway, I don't know if it's a stem issue or just more space is needed between the notes. Could you please advice in that topic (score now attached), or here?
I guess I was thinking of this thread: http://musescore.org/en/node/6314 (it is still one voice but the stem is flipped the opposite way from normal which produces the same intentional shortening effect in MuseScore).
I would still use a different bug report though.
Still the same bug, is it not (with regards to creating a new report)?
Not sure if I should create a separate report, but an unbeamed hemidemisemiquaver based on a hemidemisemiquaver triplet is faulty.
I would suggest creating a new report. By the way I'm not able to reproduce starting from a new score (MuseScore 1.0, Windows 7)