musescore / musescore/MuseScore
MuseScore 4.2 doesn't "remember" microtonal accidentals
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Bug description
I don't know if this is an already known issue, so I'm writing this report.
If we have multiple of a note in a measure, and the first one has an accidental, but the rest have no accidentals, then the accidental applies to them all. But MuseScore doesn't reflect this for microtonal accidentals. The first one is tuned correctly, but the rest are still treated as natural. In order for the playback to sound all of them correctly, the microtonal accidental needs to be added to all notes.
I don't quite know how MuseScore works with accidentals, but it seems clear that it isn't working with microtonal accidentals in the same way as it is working with regular accidentals.
Nonetheless, adding preliminary microtonal support is a good step for MuseScore. I can't wait to see it become implemented more fully.
Steps to reproduce
- Put a quarter note F in a measure
- Give it a half-sharp (or another microtonal accidental)
- Input more Fs in the same measure
- Musescore doesn't "remember" the half-sharp accidental for them
Screenshots/Screen recordings
MuseScore Version
4.2
Regression
No.
Operating system
Windows 10
Additional context
No response
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, so begin by locating the accidental-state and playback handling for repeated notes in a measure. Reproduce the steps with a half-sharp in MuseScore 4.2, then verify that later matching notes inherit the microtonal accidental for playback without requiring repeated symbols.
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
- Mostly clear
- Newbie friendliness
- 42/100