musescore / musescore/MuseScore
When hiding voices on a staff in a part, "All voices" dynamics/hairpins should not be hidden
Open
Nobody has claimed this yet.
engraving
P3
- 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
Expected behavior
When using the "Voices visible in the score" feature, dynamics and hairpins that have their "Voice assignment" set to any of the "All" options should stay visible even if voice 1 is hidden.
Current behavior (see video below)
- Create a piano score with at least two voices in the top staff
- Add a dynamic (and if necessarily, set its "Voice assignment" property to "All voices on instrument")
- Open the piano part
- In the instruments tab, expand piano and click the cog button next to "Treble clef"
- Uncheck voice 2. See that voice 2 notes disappear, but the dynamic remains
- Recheck voice 2.
- Uncheck voice 1. See that the dynamic disappears (because it technically "belongs" to voice 1 even if it's set to all voices)
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/773758b5-32d2-4936-be1c-97856e7c4b84
What is the latest version of MuseScore Studio where this issue is present?
Nightly - but found in https://github.com/musescore/MuseScore/pull/23756
Regression
No.
Operating system
macOS 14.5
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.