musescore / musescore/MuseScore
Bracket persists after bracketed instrument deleted
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
Create 2 instances of the same instrument: in the attached score 2 bass recorders. The score will have a bracket around them.
Delete one instrument in the instruments panel. The bracket in the score persists around the remaining instruments.
(Seriously? I can not attach
Zuiderzee Ballade - selection.mscz.zip
musescore files to a Musescore ticket???)
Supporting files, videos and screenshots
Create 2 instances of the same instrument: in the attached score 2 bass recorders. The score will have a bracket around them.
Delete one instrument in the instruments panel. The bracket in the score persists around the remaining instruments.
(Seriously? I can not attach
Zuiderzee Ballade - selection.mscz.zip
musescore files to a Musescore ticket???)
In which versions of MuseScore Studio is this issue present?
OS: macOS Sequoia (15.7.2), Arch.: arm64, MuseScore Studio version (64-bit): 4.6.5-253511702, revision: github-musescore-musescore-653f38d
Regression
I was unable to check
Operating system
Mac OS sequoia 15.7.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.
Assessment
This issue has not been assessed yet.