musescore / musescore/MuseScore
Misplaced measure numbers when there are two cutaway staves at the top of each system
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Engraving bug (incorrect score rendering)
Description with steps to reproduce
Basically, issue #30253 is back, but now only when there are two cutaway staves at the top of system instead of just one.
- Create a score
- Add two piano instruments
- For both staves of the top piano, turn on Cutaway (in the layout panel)
- Notice measure numbers get placed where the top of the second staff would be if it were not hidden
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
OS: Ubuntu 25.10, Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.5-253511702, revision: github-musescore-musescore-653f38d
Regression
Choose option...
Operating system
Kubuntu 25.10 (Questing Quokka)
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the layout using two piano instruments and cutaway enabled on both staves of the top piano, then compare the result with issue #30253. Trace the engraving layout responsible for measure-number placement; done means measure numbers appear at the top of the visible system rather than at the hidden second staff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100