musescore / musescore/MuseScore
MusicXML exports chord symbols on grand staves incorrectly, moving them to the top staff
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Import/export issue
Bug description
Chord symbols on grand staves are not correctly exported to MusicXML.
- Start new score with a grand staff instrument.
- Enter multiple chord symbols, some on the upper staff, some on the lower staff.
- Export the file to MusicXML.
On importing the file back into MuseScore, all chord symbols have moved to the upper staff.
It has been confirmed that this is an export problem rather than an import problem.
MuseScore Version
checked in 4.4.1, but also occurs in 4.3.2; earlier versions have not been checked
Additional context
This issue has been significantly edited by @cbjeukendrup, because previously it discussed not only this MusicXML export problem but also a MIDI export problem that turned out to be unrelated.
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
Reproduce the grand-staff case in MuseScore 4.4.1 by placing chord symbols on both staves and exporting and reimporting MusicXML. Trace the MusicXML export path and compare the staff assignment of exported chord symbols; done means symbols remain on their original upper or lower staff after round-tripping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100