musescore / musescore/MuseScore
MusicXML pedal import failure in lower versions
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
No response
Steps to reproduce
Seems something is wrong with pedal export, or its later import in older versions:
Take the attached score,
export to MusicXML (attached too), import in Mu3 (the official way from Mu4 back to Mu3), gives:
Fatal error: line 108 column 73 Content of attribute type does not match its type definition: String content is not listed in the enumeration facet..
<direction placement="below">
<direction-type>
<pedal type="resume" line="yes" sign="yes" default-y="-65.00"/>
</direction-type>
</direction>
It is the type="resume" it complains about
pedal.zip
Mu 4.1.1 doesn't complain, but screws up on import quite badly:
Screenshots/Screen recordings
No response
MuseScore Version
4.2.0 Beta and latest master
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Windows 11
Additional context
I believe this is related to #20224 (for 4.2.0) and https://github.com/musescore/MuseScore/pull/20219 (for master/4.3.0)
It might be older than that though, not sure whether #20224 in in 4.2.0 Beta?
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
Start by reproducing the report with the attached pedal.zip: export the score to MusicXML and import it in MuseScore 3, then inspect the generated pedal element with type="resume". Trace the MusicXML pedal import/export handling and compare the accepted pedal types across versions. Done means the exported file is accepted by older MuseScore versions and the pedal notation imports without corruption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, xml
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100