Bad layout of beam with first note set to beam middle
Open the attached 2.x score in version 3. There is a floating beam in measure 1 that appears to be connected to the group of four eighth notes in that measure.
(At this point, you can delete the group of four eighth notes and the floating beam will also disappear.)
Perform a relayout by moving a note up and then down in pitch with the arrow keys. The floating beam will move to measure 12 and one of the beams that should appear in that measure is missing. The space between the lines will also become very large.
If at any point, you click on either the beam of the four eighth notes or the floating beam and move an end handle, the program will crash.
Also, if you delete the group of four eighth notes (after performing a relayout), the beam will initially still appear.
(Tested in version 3.0.1)
| Attachment | Size |
|---|---|
| A_Porcupine_Dance.mscz | 13.31 KB |
Comments
Problem seems to relate to beams being set inappropriate to "beam middle" - mostly the first note of the bottom staff, although it seems there may be more to it than that.
The bad layout can be fixed by changing the beam properties for the first note of the bottom staff to either "auto beam" or "beam start".
A test from scratch:
1. Create a blank piano score. Insert a line break in the score so that there are at least two measures on the second line.
2. In the first measure, top staff, insert a group of beamed eighth notes.
3. In the last measure, top staff, insert a group of beamed eighth notes.
4. Click on the first eighth note in the first measure and change the beam properties to beam middle. The beam in the last measure becomes badly laid out and the space between the two staves on the first line becomes very large.
5. Click on any of the beams and adjust one of the edit handles. MuseScore will crash.
I can no longer reproduce with version 3.3.4
Automatically closed -- issue fixed for 2 weeks with no activity.