Open Music XML file generated from Sibelius 7 not loading the correct instruments
I have tried to open/import a MusicXML file generated from Sibelius 7 and failed...
I have attached the file I have been using for this work.
As far as I can discern there is NO issue with the notes, position, accenting or other embellishments.
The only and most important part of an import is the correct instruments... this is a Drumset score and Musescore transposes the instruments, it does however keep the voices (P1,P2) just chooses or fails to use the correct drum/cymbal.
Please fix this.
| Attachment | Size |
|---|---|
| D-10_30.xml | 79.72 KB |
Comments
I'm not sure, but it looks as if Sibelus' XML doesn't contain enopugh information for a drum staff:
Wasn't Sibelius 7 first released before 2014? If you could get the original Sibelius file, perhaps someone with a more current version could open that and then generate a new XML. Even version 7.5 is almost 9 years old. In the mean time, the XML standard has been revised multiple times (currently version 4) and the attached XML is version 2. It is possible Sibelius 7 simply is not generating a proper XML that current notation programs can read.
The problem is that Sibelius and MuseScore use almost totally different drum definitions. Plus the "hands and feet" notation in Musescore that Sibelius doesn't use. Doesn't make any difference how old the file is. Musescore Drum palette notation is like nothing I have ever seen. So much so that I don't write drumset part in MuseScore.
In reply to The problem is that Sibelius… by bobjp
Not knowing anything about drums I can't comment on that, but I thought musicXML (not my expertise either) was at least conceptualized to be a kind of "universal translator" so that even if the final implementation was done differently by various notation programs, you could still have an editable starting point that would let you end up with output that would be usable by a musician. Like the middleman between a wholesaler and retailer, if the XML standard has any value at all it seems it should at least be able to get a reasonable amount of data transfered from one program to another, whether it be drums or something else. I assume the main question here is whether the problem is in the XML standard itself, how Sibelius implements XML during export, how Musescore reads/interprets the XML, or some mixture of problems with all three. Which leads back to the same question as to whether by using the current Sibelius version to export in (hopefully) XML4 might be better read by Musescore. Only way to know is to try it.
In reply to Not knowing anything about… by garytemp
It seems to me that mxl cares more about notes than what the instrument is. For example the original score an mxl is made from might say "Violin 1". This is supposed to be the first violin section. But Musescore interprets it as solo violin 1. Because the original score doesn't say "Violins". Plural. Not necessarily the fault of either program. Just the way mxl seems to work.
And drums are not assigned to the same lines and spaces between programs.
In reply to The problem is that Sibelius… by bobjp
Srtangely the file DID handle the P1 and P2 (hands and feet) just assigned weird instruments to them. I was able to delete the offending note/instrument (render it to a pause) and then insert the correct (in this case kick) and the score looked correct - it's just very tedious to do this on even a small set of measures
You may want to try the Dolet plugin for Sibelius, it is said to produce better MusicXML export
Thank you all for your help and input
I am going to try and use the Dolet plugin as it seems to be the most likely to help
Other insights to the issue may 'unfortunately' prove to be true... sad face
I'll post to this thread after I get some results
The attached file simply does not contain any information about the instruments, MuseScore cannot load what is not present. To make matters worse, MuseScore does not even recognize the file as containing a drum score (the staff properties show a standard staff). Note head and position are imported from MusicXML, but MuseScore makes no assumptions wrt instrument assignment, it just displays what is in the file.
If MuseScore would recognize the file as a drum score, the "edit drumset" window could perhaps be used to fix the instrument assignments.
In reply to The attached file simply… by Leon Vinken
I have to agree that - if Musescore were to open a method to 'reassign' an instrument then we could all 'self help' fix a poor/broken import. Being able to select the correct staff would also be required.
I have attached the resultant import as an example of the problem. I could perform the following to repair the score but it was not worth the time - faster to re-write:
1. Delete the note
2. Go into add notes
3. Replace the rest with the desired drum instrument
4. Exit add notes
Repeat steps 1 through 4
I have often wanted to just swap a tom or other drum and this would also be easy to do with this enhancement
And FWIW, Sibelius did an equally poor job of reading drum mxl from MuseScore.
I have conducted a test using the Dolet plugin on Sibelius 7 - sadly the file generated produced the same incorrect instrumentation identical to the one that was created from Sibelius in my first attempt.
I am now convinced that a capability within Musescore is the way forward. This feature/enhancement would allow the user to change the uploaded instrument to one that corrects the score. I feel this would be used and well received by the community as it has multiple uses apart from correcting a poor import of an xml file.
In reply to I have conducted a test… by Dumptillyoudrop
The question is: Does MuseScore do a bad job of importing or does Sibelius do a bad job of exporting?
In reply to The question is: Does… by HildeK
And is it still the case with the latest Sibelius versions.
In reply to And is it still the case… by graffesmusic
I suggested trying that 4 days ago. If the OP can't update for whatever reason, I suspect there are other users here with the current version who could test it out, if the original offending Sibelius file was posted.
In reply to I suggested trying that 4… by garytemp
The original file was posted to this thread see above - I can always repost it if needed
And yes I did see your post it was what prompted me to try the Dolet and as I said I got the exact same result in Musescore (sad face)...
In reply to And is it still the case… by graffesmusic
I don't have access to them - so unfortunately I can't say either yes or no
In reply to The question is: Does… by HildeK
I believe another in this thread confirmed that the MusicXML generated by Sibelius was missing some key components - so I assume that Sibelius is the initiator of the problem. However Musescore should be able to address the file in such a way that the 'user' can 'fix' the import manually... IMHO
In reply to I believe another in this… by Dumptillyoudrop
I export mxl from Sibelius and into MU4 all the time. For the most part, everything is fine. One exception being what I posted above about solo and section labels. The other being drumset problems.
Look, a trumpet part is going to be a trumpet part in the mxl. And it will be a trumpet part in whatever notation program opens that mxl. But MU4 drum definitions are very, very different from Sibelius. And probably from any other notation program. MU4 isn't programed to read every other notation software drum definitions. Just like Sibelius can't read MU4 drum notation properly.
As I understand it, mxl isn't and can't be perfect.
In reply to I export mxl from Sibelius… by bobjp
It is drums that I am using, playing and scoring. Your comments play neatly into my suggestion for a Musescore enhancement - you are right in that MusicXML 'can't be correct all the time'. SO having a capability to edit the resultant import will rectify the discrepancies of the import and allow for the use of any and all MusicXML deficiencies...
In reply to It is drums that I am using,… by Dumptillyoudrop
What do you mean by "edit the resultant import". When would this take place? Before you open it in MU4? You are already doing it after you open it. MU4 ( or any notation software) doesn't know what a "discrepancy" is. It only produces what it thinks it sees. We know it isn't correct. But the software can't. I'm not trying to be negative. Just practical.
In reply to What do you mean by "edit… by bobjp
My idea for the solution would be to edit the score after the import in the normal score screen - the import has loaded a significant amount of the information notes, rests, accents, even the 2 voices - the only issue is the instrument that has been selected by Musescore. Select the note you wish to alter and with a key short cut bring up a selection window showing all available instruments. You could alternatively expose the input screen (at the bottom of the score window) and select the appropriate instrument from there. A global replace would also be of benefit.