musescore / musescore/MuseScore
recalculating Ambitus gives wrong result
@XiaoMigros is already working on this.
Since Oct 17, 2025.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Other type of issue
Bug description
I’m not sure whether this should be classified as an engraving or a file corruption bug because I don’t know what’s going on.
After adding some notes and recalculating ambitus the lower limit is not correct, instead it is set to c♭♭♭ (the second value of the tonal pitch class enum). The first undo changes it to e♯♯♯ (the second to last). The second undo changes it to the correct thing before recalculation. Note that the upper limit is incorrect too. Just have a look at the screen recording.
Steps to reproduce
- Create new score.
- Input some notes.
- Add ambitus.
- Add some notes that extend the ambitus.
- Recalculate ambitus via Properties tab.
- Undo.
- Undo.
Screenshots/Screen recordings
https://github.com/musescore/MuseScore/assets/7814361/2b076bd0-95e0-482a-9e6e-077f1bcc7c86
MuseScore Version
4.1.1, also current master
Regression
I don't know
Operating system
Manjaro Linux
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.
Assessment
This issue has not been assessed yet.