Issues importing Music XML File from ScanScore
Has anyone had any luck opening .xml files from ScanScore? I recently purchased the software to convert some of my pdfs into a MuseScore friendly format. However, every time I try to open a converted file, I receive a message along these lines:
"Fatal error: line 26 column 22 Element staff-layout is not defined in this scope"
I select to load the file anyways. However, it doesn't load properly. When looking at the conversion on ScanScore, the results look almost flawless; loading into MuseScore is a total bust though!
| Attachment | Size |
|---|---|
| Sometimes I feel like a motherless child.xml | 285.22 KB |
Comments
The error reported is harmless and does not cause the problem.
Will investigate, which may take a few days. Probably a bug in MuseScore's MusicXML parser, in which case I will provide a fix.
In reply to The error reported is… by Leon Vinken
Some things to correct yet
In reply to The error reported is… by Leon Vinken
Same issue as https://musescore.org/en/node/315904.
In reply to Same issue as https:/… by Leon Vinken
or #315904: [MusicXML import] incomplete import from ScoreScan XML file ;-)
In reply to The error reported is… by Leon Vinken
Fix available in pull request https://github.com/musescore/MuseScore/pull/7442
Hi, Mark,
According to the MusicXML specification, if the element defaults contains an element staff-layout, it must appear before the element lyric-font (if present). In this file, at the location cited by the error message, it is after the element lyric-font. This is seemingly an encoding error on the part of ScanScore.
The required sequence of subordinate elements is shown here:
https://usermanuals.musicxml.com/MusicXML/Content/CT-MusicXML-defaults…
Best regards, and stay safe.
Doug
In reply to Hi, Mark, According to the… by Doug Kerr
Hi, Mark,
There are a number of odd things in this MusicXML file. For one thing, in part 3 (which has just two half notes), after the note elements there is a backup element with a duration of the entire musical time length of the measure. I can't see why that would be needed (or tolerable) at this place.
This sort of thing is likely the cause of the 97 other error messages. But I have not analyzed any of the others! (I'm an old guy, and it's time for my nap.)
Best regards,
Doug