Note beams messed up at save
Hi, I have a big score (22 instruments + 243 measures) and a few of the measures have a lay-out problem.
Sometimes the beams look good but then after save they no longer look good. I have tried several options, i.e. make the measure wider, re-enter the notes, disable autoplacement for this measure.
This happens to a few random bars but seems to be only the first bar of a new page. I am using system breaks to get a nice number of measures on 1 page.
The Note-Correct picture is before I press Save, the Notes-incorrect is after Save. It is annoying as this also shows in the exported PDF, making the music not really usable.
Have you seen this issue before and perhaps any advise on what I can try?
I am using MuseScore 3.1.
| Attachment | Size |
|---|---|
| Notes-Correct.PNG | 17.92 KB |
| Notes-incorrect.PNG | 21.56 KB |
Comments
We'd need to see your score (not just a picture) in order to say with absolute certainty, but I'd say there is a very very good chance you are seeing #289933: Layout shift in measure at start of system, which is fixed in the current nightly builds and the next update.
In reply to We'd need to see your score … by Marc Sabatella
Hi Marc, I looked at all details in the issue you referenced and my score does seem to meet all these requirements for this to occur. I was able to use a workaround by inserting a blank measure with a minimal length of 1 beat, not including it in the measure count and hiding the rests and barline.
Other measures I could fix by decreasing the layout strech. Look forward to get the 3.2 version soon, so I can confirm for sure my issue has been fixed.
In reply to Hi Marc, I looked at all… by Henk De Groot
You can already test by downloading a nightly build via the Download menu above. Or, as I suggested, simply attaching your score (even just that initial section).
In reply to You can already test by… by Marc Sabatella
I have tested with the nightly build and the score displays correct. So glad the issue was already identified and that there even is already a fix available. Thank you!