Too many notes in measure to fit on page leads to layout problems
In Ver 2.1 The beams in long scales such as the Don Juan by Liszt does not remain within the page bust spreads across all visible pages. I've included screenshots. Don't know if this has been fixed in 2.2. I haven't checked to see if it occurs without a midi file, but it was a downloaded midi file, and Ver 2.1 doesn't seem to be rendering those long scales keeping them within the scope of the page, or identifying the scale of "x-length or number of of notes" and rendering them as scalar grace notes so that it would fit within the page or measure, rather than span across the pages as the images I've included shows.
Attachment | Size |
---|---|
Musescore_Scale beams anomaly unusually spans pages.jpg | 456.59 KB |
Musescore_Scale beams anomaly unusually spans pages2.jpg | 482.29 KB |
Musescore_Scale beams anomaly unusually spans pages3.jpg | 459.1 KB |
Musescore_Scale anomaly unusually spans pages.jpg | 457.94 KB |
Comments
Un-tested if this mis-rendering is affected in printing
No crash, no corruption, so not critical
Please share the score showing the problem, images don't help in troubleshooting
Indeed, we would need you to attach the actual score with the problem in order to investigate. There is a known bug if you try to extend beams across barlines and this extends across systems. Perhaps that is what you are doing, in which case, the solution is to not do that :-)
Using the MIDI file provided in https://musescore.org/en/2.2#comment-826890, I can see the problem, for example in measure 32. There are simply far too many notes in the measure to fit on a line of music given the current settings (a measure full of 64th notes on ledger lines).
There is no good way to handle this, but probably we should figure out something more graceful.
See #72041: Handle measure with too many notes to fit on a single system
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.