musescore / musescore/MuseScore
Removing soloed instrument leaves other instruments muted
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
- Open score with more than one instrument (see attached score below)
- Solo one instrument
- Remove that instrument
Actual behaviour: All other instruments remain muted
Expected behaviour: Other instruments should be unmuted
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/56d1f3b5-f049-4815-ad82-f2bbb0a732b4
What is the latest version of MuseScore Studio where this issue is present?
4.5.2 and nightly:
OS: Windows 10 Version 22H2 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.0-251950329, revision: github-musescore-musescore-1def3c6
Regression
I was unable to check
Operating system
Windows 10
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 by reproducing the issue with the attached SoloInstrumentBug.zip in MuseScore Studio: solo one instrument, then remove it and observe the remaining instruments. Trace the solo and instrument-removal interaction until the mute state is updated; done means removing the soloed instrument leaves all other instruments audible, with coverage for the reported steps.
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
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100