Beam Issues
1. Open attached score (produced in 1.2).
Result: Beam is too low.
Using MuseScore 2.0 Nightly Build (5554) - Mac 10.7.3.
| Attachment | Size |
|---|---|
| Beam Too Low.mscz | 1.44 KB |
| Beam Too Low.png | 25.51 KB |
Do you still have an unanswered question? Please log in first to post your question.
Comments
The issue in the original post appears to have been corrected - could Werner confirm this?
I suspect though, the beam may not be correct in the attached example (produced in 1.2. Therefore, I'm unable to properly test quasihemidemisemiquaver). I have also uploaded PDFs of how both the MuseScore Nightly Build and LilyPond handle it.
There's actually probably a mixture height-wise, rather than all being too low.
Using MuseScore 2.0 Nightly Build (5559) and LilyPond 2.15.36 - Mac 10.7.3.
In reply to The issue in the original by chen lung
The original issue is fixed. I added also a regression test for this.
Beams > triplebeams are not handled well yet. With a normal distance of the beam lines its not possible to touch a staff line for all beam line ends. Lilypond does a very good job by varying the line distance a little bit to achieve this.
Its also interesting to see that lilypond breaks this rule (maybe by intension) for triple beams, which normally cannot have a slant of 0.25 (first group in measure two, the beam line starts between two staff lines).
In reply to beams by [DELETED] 3
Thanks for explaining.
BTW, I have seen a few posts (links 1 and 2 ), in which there's doubt about some of Elaine Gould's 'Behind Bars', should you want to seek a second opinion on issues.
If you search Google, there is a PDF you can download called 'Creating Printed Music Automatically', if it helps.
In reply to If you search Google, there by chen lung
Thank you for the link. Its interesting reading.
Thank you for the fixes in 'Beam Too Low 2'.
Now, I have another score for you to try :).
Beam height varies, but there is another issue: The first beam in bar 2 is downstem in 1.2, but it is upstem in 2.0 Nightly Build. In LilyPond, it is downstem.
I have also attached PDFs of how MuseScore 2.0 Nightly Build (5572) and LilyPond 2.15.37-1 (via plugin in MuseScore 1.2) work - using Mac 10.7.3.
In reply to Thank you for the fixes in by chen lung
Updated.
In reply to Updated. by chen lung
If I flip the stem twice and save in 1.2, it appears the same in the trunk.
Using MuseScore 2.0 Nightly Build (5572) - Mac 10.7.3.
In reply to Thank you for the fixes in by chen lung
Different sources give different rules for stem direction on the middle line. Some sources say it should always go down. otherwise say it goes "inward" in a grand staff for piano - down on top staff, up on bottom staff. Others still say it goes the same direction as the previous stem. I personally prefer always down, so I see this particular change as an improvement.
In reply to Different sources give by Marc Sabatella
I'm not questioning the rules on stem direction generally - the example shows the trunk is changing something that was originally correct (if you view the score in 1.2), to something incorrect (ironically). In other situations, it would possibly be fine.
Hi Werner
I think the majority of issues in Beam Test 3 have been fixed - I don't know beam rules, but I'm not sure if it looks identical to LilyPond.
Can you confirm if it's fixed?
Using MuseScore 2.0 Nightly Build (5603) - Mac 10.7.3.
In reply to Hi Werner I think the by chen lung
It does not look like the lilypond rendering but should be ok. I am not sure about the slant in some beams. Lilypond renders them with zero slant which looks better but i know no rule for this pattern.
In reply to It does not look like the by [DELETED] 3
It might help if you Google for 'beam slants music'.
I privately sent Werner an example called 'Beam Test 4' - I think that has been fixed?
Now I move onto another issue (which was actually part in Beam Test 4, but I'm happy to post here): Sub-beams. I'm not familiar with the rules, but I'm guessing sub-beams must not impose within the space of neighbouring notes The less space the bar is given, the more apparent it becomes. The position of the notes likely contribute to the issue too.
Using MuseScore 2.0 Nightly Build (5607) - Mac 10.7.3.
In reply to I privately sent Werner an by chen lung
The broken beams are always the width of a normal note head. r5608 takes the stem width into account which makes the beams a bit shorter which looks better.
In reply to subbeams by [DELETED] 3
Okay.
I'm still a bit concerned that the broken sub-beam looks close to the other stem.
I don't know if that is attributed to stretch, or other things. I also notice the notes are more inward from the bar line, compared to LilyPond. Perhaps that is a setting in 'General...' (under 'Style')?
The sub-beam direction in LilyPond is different to MuseScore.
Using MuseScore 2.0 Nightly Build (5607) and LilyPond 2.15.38-1 - Mac 10.7.3.
In reply to The beam direction in by chen lung
If i understand right there is no static rule for the subbeam direction. It depends on the rhythmic structure. In lilypond you can switch the direction (if i understand their examples right). This feature is currently missing in MuseScore.
In reply to subbeams by [DELETED] 3
After observing, I think I found something that matches one of my thoughts (link ).
It might become more complicated with my example (and other instances), but should the sub-beam face the direction of the longest note found in the beam?
In reply to After observing, I think I by chen lung
Here is an example, in which this is challenged.
What direction should the sub-beam of the third note be?
Using MuseScore 2.0 Nightly Build (5608) and LilyPond 2.15.38-1 - Mac 10.7.3.
It is possible to change beam direction in Finale .
Regarding Beam Test 6: Perhaps it's better for the secondary beam to be leftward? Judging by the values (namely the evenness), it seems tidier: 3+2+1(= 1 and 1/2 beats)+2(= 1/2 beat).
Regarding Beam Test 7: Page 57 of the LilyPond documentation lists a similar example. For this, I think you're probably right - it depends on the user.
According to David Bolton, the sub-beam should point toward the beat division it is dividing.
He said about Beam Test 6: The 16th note is dividing the first half of beat 2. It isn't dividing the second half of beat 2, so the beam of the 16th note should point to the first half of beat 2.
Perhaps an issue could be filed (with a test suite), if desired.
Also see this: #17360: Semiquaver and shorter flags now face wrong way in groups of four notes
'Beam Test 6' appears to have been corrected.
'Beam Test 3' is still a problem, however. Also, comparing MuseScore and LilyPond, there is a slight height difference in the first beam in the anacrusis.
Using MuseScore 2.0 Nightly Build (a8835be) - Mac 10.7.4.