musescore / musescore/MuseScore
Incorrect engraving following interactions with clefs and multimeasure rests
Open
@ajuncosa is already working on this.
Since Aug 13, 2026.
engraving
P1
regression nightly
- 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
Adjacent to multimeasure rests, clefs may fail to draw, stop breaking MMRests where expected, or draw in the wrong place when using the Position relative to barline property.
Supporting files, videos and screenshots
- In a new score, add a clef after a few bars, then open the part. Notice that the clef breaks the MMRest as expected.
- Select the clef and toggle the Position relative to barline property a couple of times between Before and After.
RESULT: The multimeasure rest is no longer broken, and the clef is drawn at the end of the score. - Start adding notes from the start. Notice that when notes are added to the bar following the clef change, the notes are drawn at staff positions relative to the new clef - even though it is not being drawn.
- Continue adding notes until the system breaks. The new clef is drawn at the start of the new system (still not drawn at the point it was added).
- Add a system break where the new clef should be drawing. Notice that the clef at the start of the system is the previous clef, but the notes are drawn relative to the new clef.
https://github.com/user-attachments/assets/bacd5bd6-e480-4e6e-826d-55907f21e14d
In which versions of MuseScore Studio is this issue present?
Nightly main
Regression
Yes, this works in the latest released version and is broken in the nightly builds
Operating system
macOS 26.6.1
Additional context
Other bugs presented following the steps above in 4.7.x, but the particular results observed here are new.
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.
Assessment
This issue has not been assessed yet.