Single Non-Last Measures Taking up a Whole Line
As you can see by the screenshot, for no reason I can tell certain (non final!) measures are deciding to take up way too much space.
I've tried adjusting the Measure Properties but the stretch value does nothing.
Looking for any help here.
Thank you
| Attachment | Size |
|---|---|
| Screenshot from 2019-01-13 21-17-17.png | 121.18 KB |
| MeasuresTooWide.mscz | 19.94 KB |
Comments
I don't think anyone can help you without the actual score (.mscz file). There's not enough info in the picture.
In reply to I don't think anyone can… by mike320
Attached!
In reply to Attached! by Bujiraso
That definitly isn't the same score as in the image
Hwoever: at that size (page witdh, staff spacing) those measures are just too busy to leave space for another measure that is equally busy
In reply to That definitly isn't the… by Jojo-Schmitz
Ace detective work, there! It's called an "example". It gets to the meat of the issue without letting people get lost on other things.
Also "too busy" ? It's seriously not. I am hand-copying this score from another score where three of those fit on a single line comfortably on a rather small page of paper.
is there a system break involved (and made to not show on screen)?
In reply to is there a system break… by Jojo-Schmitz
As in like (my words not yours:) "did I hit enter and then hide it like a tool"? No. :P
So just from the baby little bit of "d e b u g g i n g" I did (meaning, I deleted everything but the offending measures), I realize the issue is that MuseScore wants to draw these measures at 75% of the line, no matter what stretch I choose in the Measure Properties. Since 75% + 75% > 100%, then it cuts the line and draws the first measure as 100%. Repeat for all measures greater than 25% that follow.
This seems like a pretty consistent bug all around MuseScore. The sizing of measures is very much out of the control of the user and not necessarily for the best.
I think this might count as a defect. If I want to draw this messy measure within 10% of a line, that should be my user judgment to make. Sure it could make awful scores, but hey -- that's what sane defaults are for.
In the case it's currently blocking me from a sane default -- not having an entire measure of one chord kind take up an entire line.
Let me know how I can help, filing issues and the like.
If someone knows the code area to hack in, I can also try and pitch in, though I don't speak C++ (Java dev).
See:
https://musescore.org/en/handbook/3/page-settings
where you can decrease the scaling.