Support MusicXML 4.0

• May 12, 2021 - 07:36
Reported version
3.6
Type
Functional
Frequency
Few
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

MusicXML 4.0 is due to get released by the 1st of June 2021 (see https://github.com/w3c/musicxml/milestone/2), a draft is ready, see https://w3c.github.io/musicxml/

Finale announced MusicXML 4 support for their soon to be released v27, see https://www.finalemusic.com/blog/finale-v27-is-coming-soon/

Seems about time for MuseScore to think about that too.

Relates to #270643: [EPIC] MusicXML import/export issues


Comments

To be perfectly clear on the implication of failing to do this:
- MusicXML 4.0 files not using new 4.0 features will load correctly without any error message
- MusicXML 4.0 files using new 4.0 features will fail schema validation, including the associated warning but ignoring the warning most likely still results in a correct import
The solution is to update the associated xsd files (3.x source code location mscore/schema, master src/importexport/musicxml/schema) and update and/or regenerate the MusicXML test files

Thank you for submitting this before I can come to it. One of the advantage of Musicxml 4 is support of system texts, which makes braille transcription of such texts more easier to be distinguished from staff texts. So all system texts and lines can be exported as directive="yes" or the one for system (I can't remember the exact attribute).