You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Find a system where the first visible staff is not actually the first of the piece, because one or more over it are empty and therefore hidden
Add a stave spacer up
Extending it up won't stop to the page or the page margin, and therefor won't move the system down as wanted
Please note that the problem doesn't appear in the opposite direction – with lower staves hidden and staff spacer dows, which correctly stop at page margins allowing the system to be moved up
Supporting files, videos and screenshots
Uncorrect behaviour with the hidden upper staves:
Correct behaviour with hidden lower staves:
What is the latest version of MuseScore Studio where this issue is present?
4.4 (also 4.5 beta)
Regression
No (same back to at least 3.6)
Operating system
Windows 11
Additional context
No response
Checklist
This report follows the guidelines for reporting bugs and issues
I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
I have attached all requested files and information to this report
I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
The text was updated successfully, but these errors were encountered:
spscores
changed the title
Stae spacer up not working when upper instruments are hidden
Stave spacer up not working when upper instruments are hidden
Mar 1, 2025
Issue type
Engraving bug (incorrect score rendering)
Description with steps to reproduce
Supporting files, videos and screenshots
Uncorrect behaviour with the hidden upper staves:

Correct behaviour with hidden lower staves:

What is the latest version of MuseScore Studio where this issue is present?
4.4 (also 4.5 beta)
Regression
No (same back to at least 3.6)
Operating system
Windows 11
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: