Applying beam properties to rests produces strange beams/stems in neighbouring notes
If there is no note to connect to, applying beam properties to a note or rest shouldn't be applicable.
1. Create score.
2. Enable 'Note Entry'.
3. Enter semiquaver rest.
4. Enter semiquaver next to the rest.
5. Disable 'Note Entry'.
6. Select rest.
7. Double-click 'Beam start' (from Beam Properties).
Result:
In 1.1, the semiquaver note has a flag of a crotchet.
In the trunk, there is half of a beamed semiquaver.
Using MuseScore 1.1 and 2.0 Nightly Build (4674) - Mac 10.6.8.
Comments
In step 6, I should say "select the first rest" (the semiquaver).
Think it's just rests.
Not sure of the rules on why it's happening (was able to do the treble clef in this score, so doesn't happen in every instance), but I can provide another example:
1. Open attached score.
2. Click the first semiquaver rest in the bass clef.
3. In 'Beam Properties', double-click 'Middle of beam'.
Using MuseScore 1.1 and 2.0 Nightly Build (4683) - Mac 10.6.8.
Forgot to attach score - it's as if I'm posting for the sake of it :D.
I found this .
Could the semiquaver with a partial beam actually be correct?
I think the behaviour is correct and intended. The "middle beam" property means that the note/rest should be beamed. The naming of the property is probably misleading. It does not necessarily beam the neighbour rests/notes.
Beams starting with a rest are also common. Sometimes a short stem is attached from beam to rest (which is not supported in MuseScore).
Although it's differently angled in MuseScore, it may generally be called a 'straight flag style' (see Lilypond's page ).
Following the same steps in current build (b424d8ef47) results in the stem for the note extending all the way off the page. The beam is correct - it shows the partial beam as it should - just the stem is messed up.
Fixed in 4f768005c5
Automatically closed -- issue fixed for 2 weeks with no activity.