Export to *.mxl creates incomplete stave
Using MuseScore 2.0.1 on Windows 7
I have come across a reproducible error involving import of a Sibelius *.xml, when the contents are then exported to *.mxl by MuseScore:
1. In MuseScore, open XML file generated by Sibelius 6.2 in MusicXML 3.0 format
2. MuseScore reports one error on import:
"Bar 157 Stave 10 incomplete. Expected: 4/4; Found: 20/16"
3. Ignore the error, import into MuseScore
4. Correct the error in bar 157 by deleting all notes in voice 1 of stave 10 and adjusting rests; save as *.mscz file
5. Export as *.mxl file, close MuseScore
6. Then import the *.mxl file into MuseScore
7. MuseScore now shows multiple errors for a different earlier bar:
Bar 67 Stave 2 incomplete. Expected: 33/32; Found: 3959/3840
Bar 67 Stave 3 incomplete. Expected: 33/32; Found: 3959/3840
Bar 67 Stave 4 incomplete. Expected: 33/32; Found: 3959/3840
Bar 67 Stave 5 incomplete. Expected: 33/32; Found: 3959/3840
Bar 67 Stave 6 incomplete. Expected: 33/32; Found: 3959/3840
Bar 67 Stave 8 incomplete. Expected: 33/32; Found: 3959/3840
Example files attached. I am guessing that the first error in bar 157 must be the fault of Sibelius. But the later error at bar 67 seems to be introduced by MuseScore?
I'd be grateful for any comments.
| Attachment | Size |
|---|---|
| FOR_THE_FALLEN_xml_from_Sibelius.zip | 176.24 KB |
| FOR_THE_FALLEN_corrected_bar_157.mscz | 106.21 KB |
| FOR_THE_FALLEN_exported_by_MuseScore.mxl | 148.4 KB |
Comments
I see a different error in a current development build when exporting that mscz as mxl and then importing the mxl again:
Fatal error: line 42 column 19 Element credit is missing child element.
Loading anyway then shows the errors you mentioned.
In reply to I see a different error in a by Jojo-Schmitz
Measure 67 in part 3 contains a measure with an unusual duration (3132 instead of 3072). which may be causing the MuseScore issue with this measure.
Will investigate further, but this will take a few days.
You could try to run the file through the experimental MusicXML sanitizer:
http://www.musicxmlsanitizer.io/
I never used it, but they say ( http://forums.makemusic.com/viewtopic.php?f=12&t=2931 ) that it can perform some analysis on the score also about the sematic and correc it.
In reply to You could try to run the file by ABL
Many thanks, I tried the MusicXML Sanitizer. It couldn't handle the original file which I posted on the MuseScore forum (about 147,000 lines of XML). But it did run through a MusicXML file of about 18,500 lines and produced a log and a "sanitized" version. The sanitized version was only a clean-up of wrong indentations and didn't attempt to correct the two errors identified in the log. The log also includes several "FIX TODO" remarks, so I think it's still early days for this validator.
Log example:
![MusicXML_Sanitizer_log.png]( "MusicXML_Sanitizer_log.png")