Text Frame structure overlaps page number when placed at the top of the page

• Oct 30, 2021 - 13:38

I noticed that when I put a text frame at the top of a page, it overlaps with the page number by default. I can work around this by adding a new line before my text, but it would be nice if this sort of thing was handled automatically.



Yes, it was an oversight when the style settings were changed to move page numbers to the header instead of footer. The better workaround - and what will presumably be made the default - is to simply move the page number outside the score area and into the margin, by changing the Y offset Format / Style / Text Styles / Header. A value of -5 mm, for example, usually works, depending on what other style settings you might have in your score. You shouldn't need to resort to blank lines, which you'd have to do on every page and also it will look wrong if the layout changes and that text is no longer at the top of the page.

In reply to by Jojo-Schmitz

I have found similar problems with both headers and footers. Text above the staff, such as rehearsal marks, can extend into the header. Text below the staff such as dynamics often extend into the footer, especially when the footer contains a three or four line copyright.

I do have a work-around. I'll create a staff-text with something line a '.' and reposition that dot until it pushes the staff away from the header or footer, then I'll position the dot over the header or footer text until it is (almost) unnoticeable.

In reply to by Aaron Grosky

I've found a big problem with using the frames for this purpose - I don't see a way to add the frame to exactly one part. I need a solution that only affects the part that has the problem without obviously affecting the original score (on the original score the "." is sufficiently close to unnoticeable) or the other parts.

I suspect that, even if I went to all the other parts and reduced the height of the horizontal frame, the presence of the frame would change the formatting of those parts.

In reply to by Aaron Grosky

As I explained above, neither frames nor spacers are the right fix here. It's simply a matter of the MuseScore header text style default having been set inappropriately - it places the header in the score area where such collisions are then inevitable. Change it to what it should have been all along and no further adjustments are needed.

In reply to by Marc Sabatella

Thank you Marc. Changing the Y offset moves the header up. If this is the correct solution (it appears to be the best available in 3.6), then this should either be the default or is should be done automatically (e.g., Y offset is set according to height of the header or the footer). Also, the Y offset should be in points, not millimeters; otherwise one needs to convert pt. to mm., (for example, 8 pt. to mm., if I recall correctly, 8 pt. / 72 pt./in. * 25.4 mm./in. = 2.82 mm).

However, this works for the header as long as the height of the header is the same on all pages which have a header. Likewise, changing the Y offset should work for footers (should since I haven't tested it), but though headers are all likely to be the same height, footer are less likely since footers support only putting the copyright on the first page.

MuseScore has:
- Margins at the top and bottom.
- Below the top margin is the header and above the bottom margin is the footer.
- The staves should be fit between the bottom of the header and the top of the footer.
Better would be that the header and footer are treated like staves in that the top staff should not occlude the header and the bottom staff should not occlude the footer. This would allow the top staff to extent to the margin as long as the header is not in the way. A copyright notice would "push up' a staff with a dynamic in the middle, but not one with the same dynamic where it wouldn't overwrite the copyright.

In reply to by Aaron Grosky

Yes, as noted in the issues linked above, what we intended to do was keep the header and footer contents out of the way of the music contents. We just messed up. We fixed the footer text style when 3.0 was released, but no one noticed the header had the same issue because there was no default header. So the error in the header text style went unreported for years until we moved the page number there at 3.6. Unfortunately it's complicated to just change the default now because some scores may have implemented other workarounds that rely on the existing defaults. Plus of course, the official work has long been, 3.6.2 is the end of the road for MuseScore 3. But presumably it will be addressed for MuseScore 4, when we fully expect lots of things will change.

Meanwhile, to be the "right" solution is to play the header in a special area that is neither the page margin nor the music area. At least that's what I seem to recall most word processors etc doing. If I'm wrong, well, whatever they do, we should do too. As I note in a comment in one of the issues, we didn't invent the concept of a header, clearly there is established best practice here we should follow.

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