Page bounding rectangle seems to be calculated wrong

• Jun 4, 2018 - 14:47

I have the following system:

 MuseScore nightly build version 2.2.1, revision 51b8386

 MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports)
 Operating system version: 10.13.4 (17E202)
 Processor: 2,3 GHz Intel Core i5
 Memory: 8 GB 2133 MHz LPDDR3
 GPU: Intel Iris Plus Graphics 640 1536 MB

If I create a new score and add some staffs and at the end a vertical frame, then I have some empty space under the vertical frame. If I increase the vertical frame then a page break happens, but there should be no page break, because there is too much space free on the page. Here are the steps to reproduce it:

  • open MuseScore
  • create an empty score in wizard, name it "Test"
  • add 11 violin staffs with 12 bars and leave all other wizard options to default
  • select the first bar in last staff
  • append a vertical frame, it is initially created with height = 10sp
  • select "Show page margins" in View menu to see the page margins
  • now you should see that there is much space below the vertical frame
  • if you increase the height of vertical frame to 11sp you see the difference to 10sp is minimal
  • there is again much space available on page
  • if you increase the height of vertical frame to 12sp you get a page break

There is enough space on the page to have a vertical frame with at least 15sp or more, so the page break should not happen. You can also reproduce that with staffs, normally the staff would have enough space on page 1, but it is moved to page 2.


Comments

I assume you are in a country that uses A4 paper size? Or you have a custom style set as default in Edit / Preferences / Score? For me, the vertical frame instantly goes to a second page. But I can reproduce with my page size set to A4.

I believe what is happening here is that we are are trying to fit not just the frame but to also respect the margins set in Style / General / Page. In particular, we allocate enough room for the "Music bottom margin" of 7.0sp. Reduce that to 0 and you will see it fits all the way until you hit the border.

It's debatable whether we should worry about the "Music bottom margin" for vertical frames, since the main purpose is to allow enough room below the staff for notes on ledger lines, dynamics, etc. In any case, MuseScore will have an entirely different system for allocating space between staves etc, but it's pretty far from being ready. Feel free to experiment and provide feedback, though!

In reply to by Marc Sabatella

Yes in my country the A4 portrait is used as default. But I do not understand your description about the margins. I have described in my steps that you need to activate the "Show page margins", so that you can see where your real available paper ends. I do not speak about the space outside of the margins, I speak about the inner content. And in the inner content is enough space, so that there should by a vertical frame height of 15sp or more possible. There should not happen a page break until we reach the page bottom margin line with the inner content.

In reply to by Jojo-Schmitz

Ahhhhh thanks. I do not understand Marc correctly and I skipped the important information in my mind, that he spokes about Style > General > Page Setting. I thought he mean the normal page margin settings. Your screenshot corrected that in my mind, thanks. And sorry to Marc :-)

I set now the "Music bottom margin" to zero. It works for me.
But now I asked myself, what does then the "Music top margin"?
I has also a value of 7sp, but the music has no space at top and when I increase that value nothing is changed.

In reply to by Jojo-Schmitz

Yes thanks, that works for me. When I remove the title frame then I could adjust the music top margin. Maybe my last try to increase it was not enough :-)

So this seems to me that these values are to define some static header and footer space.

Ok then this is by design and maybe this post can be ignored by the developer.

In reply to by Jojo-Schmitz

I think the behavior is not ideal. To me, the main purpose of these music margins is to allow room for notes and other markings above/below the staff to not extend into the margins - so the staff itself doesn't hit the marign, but stays some distance away from it. As such, it seems it should only apply to staves, not to frames. So to me, it's correct that the music top margin is ignored when placing a frame at the top of a page, but I think the music bottom margin should probably also be ignored when placing a frame at the bottom of the measure. At least, I can't think of a good reason for applying the music bottom margin to a frame at the bottom of a page.

But I recognize there are differences in how we process the top versus bottom of a page. The top of the page is much simpler to handle than the bottom, because of the whole business of trying to figure out how many systems we can fit on the page based on min system distance, then filling things up to max system distance, etc. So even if it's not deliberate that we honor the music bottom margin for frames, it could be a hard-to-avoid consequence of the whole algorithm.

Do you still have an unanswered question? Please log in first to post your question.