Beams offset for small upstem chords with slash heads
Ubutnu 14.04, GIT commit: 9cf181c
1) empty score
2) enter two beamed eighth notes with stems up
3) using Inspector, set both to "small" (chord property, not note) and head group to slash
Result: beams are offset, maybe by the different difference in width between normal and slash notehead):
Happens with other noteheads too, but most noticeably with slash and xcircle.
BTW, the effect is per note. That is, if you only alter the first note of the beamed pair, then you see the beam offset there but not on the second note, and vice versa.
This particular use case - small upstem beamed notes - is more common than you might think, as it is is commonly used to indicate "kicks" in drum parts and lead sheets.
Attachment | Size |
---|---|
slash-beam-offset.png | 1.56 KB |
Comments
After checking, this issue appears on September 9.
- I get on the Nightly c3754c0
this result:
- I receive on the Nightly 97928d8
this result:
Some proposals for the cause:
- This one, maybe? https://github.com/musescore/MuseScore/pull/1289/files
As I don't know very well, I indicate also (without be really convinced!)
these two others:
- https://github.com/musescore/MuseScore/pull/1291/files
and
- https://github.com/musescore/MuseScore/pull/1294/files
Thank you! You got it right with your first guess as to which commit caused the problem - it was mine :-). I added that code, but don't remember exactly what was going on. However, the issue I was fixing had to do with whole notes specifically, so one potential fix for this issue here would be to limit that line I added to only work for stemless chords. This seems to work, but I need to investigate and test further.
On further investigation, disabling this code for chords with stems *does* work and is safe enougn, but it also disables the centering that would otherwise take place. So if I want to keep that, I need to find another solution.
Found one :-). Just need time to add tests etc.
https://github.com/musescore/MuseScore/pull/1784
Fixed in d3184d2429
Automatically closed -- issue fixed for 2 weeks with no activity.