musescore / musescore/MuseScore
Staff type changes are hidden during multimeasure rests
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
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
Staff type changes are hidden during MMRests. This can be problematic in parts, where a hidden staff type change may be causing (seemingly) unexplainable issues.
https://github.com/user-attachments/assets/0d4afbaa-dc2f-476f-9189-60df51223dab
Supporting files, videos and screenshots
Also, staff type changes do not break MMRests, which I think is debatable. In any case, staff type changes during an MMRest are unstable; in this example, observe that the music following the staff type changes is drawn on a 1-line staff with MMRests off, but a 3-line staff with MMRests on.
https://github.com/user-attachments/assets/b65fc877-05bd-484c-aeaf-972dd902e0ab
In which versions of MuseScore Studio is this issue present?
latest nightlies
Regression
No.
Operating system
macOS 26.6.2
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
Start with the attached minimal examples and compare the notation with multimeasure rests enabled and disabled, focusing on staff type changes and the following music. No source file, test, or entry point is named in the report; done means staff type changes remain visible and the affected music uses the correct staff type in both modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100