Import of Musescore into Sibelius
Hi there,
I get the error message attached when I import into Sibelius, and wondering what is causing it. I've gone into Musescore and export in the different xml and mxl formats but it doesn't seem to make a difference. Thanks for your help!
Cheers,
Ben
| Attachment | Size |
|---|---|
| 1.JPG | 24.53 KB |
Comments
Hard to say without seeing the score. If you attach the MSCZ file you started with here, we can investigate and see if the exported MusicXML is valid and if not, how to work around it.
In reply to Hard to say without seeing… by Marc Sabatella
Thanks Marc, I've attached the file and the export. I downloaded it from here: https://musescore.com/user/13648236/scores/4860798
Also, what version of Sibelius.
In reply to Also, what version of… by bobjp
hi Bob, it says 2022.10. I'm on an annual subscription so it should be the latest version. thanks!
The error message suggests MuseScore produced invalid MusicXML. To find the cause and solve it, the score in MuseScore format would be required, please attach it.
In reply to The error message suggests… by Leon Vinken
Hi Leon, here's the scores attached. For reference, I found it here under my musescore subsciption:
https://musescore.com/user/13648236/scores/4860798
In reply to Hi Leon, here's the scores… by benjohnthomas
Just an idea: If you use MS4, the exported xml file uses the musicxml version 4 schema.
I am not sure if Sibelius can handle v4.
Could someone confirm that latest Sibelius can import xml v4 exported from MS4?
In reply to Just an idea: If you use MS4… by graffesmusic
To check validity of xml file (on Linux but this should also work on Windows)
-install xmlint
-download schema from musicxml github
xmllint --schema musicxml-3.1/schema/musicxml.xsd .musicxml --noout
or
xmllint --schema musicxml-4.0/schema/musicxml.xsd .musicxml --noout
In reply to To check validity of xml… by graffesmusic
It seems that text between < and > is ignored on the forum
should be :
xmllint --schema musicxml-3.1/schema/musicxml.xsd filename.musicxml --noout
or
xmllint --schema musicxml-4.0/schema/musicxml.xsd filename.musicxml --noout
In reply to It seems that text between <… by graffesmusic
The forum filters out potential html/xml tags
xmllint --schema musicxml-<x.y>/schema/musicxml.xsd<filename>.musicxml --nooutxmllint --schema musicxml-<x.y>/schema/musicxml.xsd <filename>.musicxml --noout
;-)
In reply to xmllint --schema musicxml-[x… by jeetee
Try one of these. I got the same error but 7.5.1 opened your mxl anyway.
In reply to Try one of these. I got the… by bobjp
Thanks Bob, I tried the .mxl and it worked really well, all text came through. Thanks for taking the time to look into this, I really appreciate it!
Regards,
Ben
In reply to To check validity of xml… by graffesmusic
Thanks for that, will save the link for future! Ben
In reply to Just an idea: If you use MS4… by graffesmusic
Sibelius 7.5.1 can open Compressed and Outdated xml from MU4.
The issue is caused by a bug in MuseScore's MusicXML exporter triggered by a number of rests in the drum part with a huge Y offset. This leads to an invalid display-step and display-octave in the MusicXML generated. Fixed file attached (created by manually editing the XML file).
Issue reproduces with MuseScore 3.6.2, but not with MuseScore 4.0, no further follow-up required.
In reply to The issue is caused by a bug… by Leon Vinken
As I said, I was able to open the OP mxl in Sibelius 7.5.1. Perhaps there is a change in newer versions. It may also be that Sibelius does not utilize different voices in drumset parts the same way MuseScore does. Sibelius might not know quite how to handle MuseScore drumset parts. So the drum part imports with everything in the wrong octave and unnecessary rests. Which I didn't fix in my exports. Just evidence that it can be done. Plenty of further follow-up required.
Also note that MuseScore will export as three different kinds of mxl. Perhaps following up using each of these might find one that works better.
In reply to As I said, I was able to… by bobjp
> Also note that MuseScore will export as three different kinds of mxl
Care to elaborate?
In reply to > Also note that MuseScore… by jeetee
In reply to [inline:mxl export.png] by bobjp
The file contents of all three is identical though. Just like musescore has mscx (text) and mscz (zipped) the mxl is nothing more than a zipped musicxml.
The xml (outdated) version only uses the different file extension for those programs that don't follow the musicxml recommended extension.
But the information contained in all three formats is identical.
In reply to The file contents of all… by jeetee
Then there must be something different about the envelope.
I opened the OP's original mscz, and changed it to page view. Maybe I shouldn't have done that but whatever. Then I exported it in each of the three mxl formats.
Compressed: Sibelius opened after 2 different warnings. MuseScore opened it after saying it wasn't a valid file (?)
Outdated: Sibelius opened after two warnings. MuseScore opens after saying it is not a valid file.
Uncompressed: Not a viable file for Sibelius. Won't open. Doesn't even see it. MuseScore opens it after saying it is not valid file.
Sibelius also said the two files it did open where not valid mxl's, just like MuseScore did.
The content may be identical, but there seems to be more to it than that.
In reply to Then there must be something… by bobjp
Now change the .musicxml file and rename it to .xml and you'll see those two are identical too.
In reply to Now change the .musicxml… by jeetee
Which proves the neccessity of the "outdated" .xml format once again...
In reply to Then there must be something… by bobjp
Then open the .mxl with e.g WinZip or 7Zip and pull out the .xml inside and see that that too is identical
In reply to Then there must be something… by bobjp
What I find interesting here is that MuseScore says Its own exports are not valid/
In reply to What I find interesting here… by bobjp
That's the bug Leon identified, fixed in MuseScore 4
In reply to The issue is caused by a bug… by Leon Vinken
Leon,
Thankyou so much for looking into this and fixing the file - I've been able to open it in Sibelius with the parts I was after looking perfect with all articulation and dynamics. Thanks again!
Ben
In reply to The issue is caused by a bug… by Leon Vinken
Further investigation shows the bug has not yet been fixed in MuseScore 4. It just does not trigger because the Y offset is not imported and remains at a sensible value.
Submitted issue https://github.com/musescore/MuseScore/issues/14795.