musescore / musescore/MuseScore
Importing MuseScore 2.0 files can place notes in wrong octaves
@cbjeukendrup is already working on this.
Since Mar 14, 2023.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
File corruption
Bug description
Opening certain files created in MuseScore 2.x.x in 3.x.x or 4.x.x erroneously places some notes one octave higher.
Steps to reproduce
- Open the attached file (tico_tico_no_fuba_clarinet.mscz) in MuseScore >3.0, including the latest 4.0.2.
- Compare it with the PDF exported from MuseScore 2.x or open in MuseScore 2.x.
- Observe that many notes are erroneously transposed one octave higher.
Screenshots/Screen recordings
How it should be, and how it is in MuseScore 2.0.x: the interval in the second measure is D4-G4.
How it is in 3.x and 4.x: that interval is D4-G5. It's just one instance, some phrases are entirely an octave up.
MuseScore Version
3.2.3, 4.0.2
Regression
Yes, this used to work in Musescore 2.x and now is broken
Operating system
Linux
Additional context
MuseScore 2.0.x file: https://baturin.org/music/transcriptions/tico_tico_no_fuba_clarinet.mscz
PDF exported with 2.0.3: https://baturin.org/music/transcriptions/tico_tico_no_fuba_clarinet.pdf
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.