Multi-page scores yield invalid MusicXML

• Jun 4, 2020 - 18:42
Reported version
3.x-dev
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
MuseScore

As far as I can tell, any score of more than one page yields an invalid MusicXML when exported. In particular, there is a validation error regarding the system-distance tag at the top of the second page (either that or the error is spurious; the score does actually load if you ignore it).

Simple steps to reproduce:

1) default empty score
2) add page break after measure 4
3) export to MusicXML
4) try to import

Result: "Fatal error: line 125 column 27 Element system-distance is not defined in this scope."

If you go to Edit / Preferences / Export and turn off "Export all layouts", there is no error. Any of the other settings seem to be good.

Comments

• Jun 4, 2020 - 20:13

There are two obvious errors in the export:
- elements top-system-distance and system-distance are in incorrect order
- element system-distance contains an incorrect value

Probably my mistake, am investigating. I consider this a showstopper for 3.5, as every MusicXML export including all layout information will be invalid.

Reply

• Jun 6, 2020 - 23:10

FWIW, if a fix isn't forthcoming soon enough, I'd be fine with a temporary hack of simply ignoring the "Export all layouts" option (btw, that "s" isn't really appropriate here) and treating it for now as if the user specified "Export all system and page breaks" instead.

Reply

Fix version
3.5.0