musescore / musescore/MuseScore
Repetition of the accidental when notating two or more performers on the same staff
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
I suggest implementing a function in MuseScore Studio in which each note in the chord (as well as in each voice) has its own accidental and does not relate to subsequent notes belonging to other performers.
This applies only to those staffs on which 2 or more performers are notated. This does not apply to staffs for single instruments such as harp, piano, etc.
Thus, each note of a particular performer should have its own accidental, for example:
Problem to be solved
Choral music and orchestral parts often double up two (or more) parts on one staff in a score. Therefore, for clarity, it is necessary to confirm or cancel each accidental in every part. This guarantees that essential accidentals are not omitted when instrumental parts are extracted, or when different voices read from a single stave in a vocal score.
Prior art
As far as I know, both Sibelius, Finale and Dorico do this.
Additional context
No response
Checklist
- This request follows the guidelines for reporting issues
- I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
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
The issue names no source files, tests, or entry points. Start by locating the accidental-notation and multi-voice staff logic, then determine how performer-specific state is represented. Done means each performer’s notes receive independent accidental confirmation or cancellation on shared staves, while single-instrument staves retain current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100