Export to MusicXML
I exported my score to MusicXML. Then tried to open it in MuseScore. It said that the file is not a valid MusicXML file, and gave the error:
Fatal error: line 44 column 19 Element credit is missing child element.
Help! Please!
Do you still have an unanswered question? Please log in first to post your question.
Comments
Can you share the mscz and the XML file?
Which Version of MuseScore, what OS?
In reply to Can you share the mscz and by Jojo-Schmitz
Thanks for the prompt response. I am using the latest MuseScore 2.1 with Windows 10. The score is Copyrighted, and I rather not share it. Sorry.
In reply to Thanks for the prompt by Hamid-2016
Can you provide a stipped down version (delete all notes and lyrics for example) of that score, that still shows this behavoir?
In reply to Can you provide a stipped by Jojo-Schmitz
Without the notes, the error does not show. The empty file can be saved in MusicXML, and then opened in MuseScore; without the error. But then, I have no score. Could the problem be with the notes?
In reply to Without the notes, the error by Hamid-2016
strange, I'd have though 'credit' isn't something that applies to notes?
Anyway, without seeing a score causing the problem or a very clear step-by-step description how to reproduce there's little to no chance of finding and fixing this.
In reply to strange, I'd have though by Jojo-Schmitz
The error text should provide the clue to the issue, and its resolution:
Fatal error: line 44 column 19 Element credit is missing child element.
Where is line 44, column 19 Element credit?
What is the Child Element?
In reply to The error text should provide by Hamid-2016
That is an error message from the XML validator, and clear enough as such (line 44, column 19 in the XML file you import), question is the context, and this is what we Need the score for
Perhaps you can do some diagnosing yourself and narrow the problem down to something that can be duplicated.
the MSCZ file is simply a zip file that contains a few file including one that is called name.mscx where name is the name of the MSCZ file. This MSCX file is and XML file. If you open it in a XML editor, the error should be reported in the editor. There are plenty of free XML editors out there. You can then look at the previous
Measure number=
statement to determine which measure the error is in.
You can then trim down the score to include perhaps 3-5 measures including the offending measure and see if the error is duplicated. These few measures should not violate a copyright but rather be covered by fair use. You might be able to duplicate the problem by setting the notes to something like a scale if you feel better about that.
If the error is before the first measure (which is possible due to how early it is in the file), then you can save the file to include the first measure so it can be examined.
In reply to Perhaps you can do some by mike320
Thanks for the guidance. Here is an issue with Exporting the score to MusicXML: some of notes shifted position. The MuseScore file is not exactly identical to its MusicXML version. Is this a known phenomenon?
In reply to Thanks for the guidance. Here by Hamid-2016
That some settings are lost on XML export is to be expected
In reply to Thanks for the guidance. Here by Hamid-2016
Think of MusicXML as a kind of "generic" representation of a score, designed to be kind of a "least common denominator" between all the different formats used by all the different notation programs. It is indeed perfectly normal that some fine details of layout etc will not be preserved in the conversion to or from MusicXML. This is true for pretty much any notation program.
If you consider what happens if you take a paragraph of English text it through Google Translate to French and back, I'd say MusicXML conversion should be expected to be only slightly better.