I am trying to import this MusicXML file from MuseScore and it keeps an Hanging at 55%.
I am importing straight from the Hub and same issue. Does this happen to others
Here too.
Jesper
The file appears to be corrupted. Can you resave it as mxml without any options selected if that’s possible in MuseScore? I’ve never used MuseScore so please pardon my ignorance.
It imports to Finale, but an export from Finale also hangs.
Jesper
How odd. Just for fun, I opened it in my old Sibelius crossgrade. On attempting to import, there are 24 instruments called “Section End” which I don’t understand. I allowed Sibelius to substitute Piano for that Section End instrument and it opened the file. I then saved to a musicXML file from Sibelius and it still hangs at 55%.
So, Dorico attempting to open an export from Finale and Sibelius (both able to open the file) or your original from MuseScore does not work but causes Dorico to hang. I suspect this is a bug in Dorico where it is unable to handle some sort of error exception. I think we need help from @Ulf.
Edit: You might want to try to export again from MuseScore…to see if this issue persists.
Maybe check the original MuseScore document, and see if there is anything strange there.
Good point. I’m uncertain as the unit used to describe % Complete on Dorico imports but it would probably be reasonable to start looking somewhere between measures 65-75 initially. I would also check individual parts in MuseScore just to see if something inadvertently was tacked onto one of the parts.
I will add another aspect to this conundrum: Dorico must be forced to quit on my Mac even though I cancelled the import operation. Nothing else functions after closing that hung import window at 55%. This suggests further to me that Dorico has a problem handling an exception in that file. (I have not selected any xml import properties in Preferences in Dorico.) Note that both Sibelius and Finale could open the original file without hanging.
To test, I opened the original xml file in both Silbelius and Finale. I saved from both application in both compressed and uncompressed musicXML formats. All formats from both apps. Will MuseScore import and open the file that you shared? That might be key to finding the cause.
Thank You all for your help…I don’t realy use MuseScore that much -I am engraving a work for a freinds fatherr and all Ihad to start with is a pdf so Iused the xml converter from MuseScore.
But I will try starting with MuseScore settings..I forgot About Finale… Might try double convert…
Same number and result from me. Must be a Dorico Issue…Thank you. BTW, the midi import works fine
I think I’ve identified the issue. The musicxml file has a piano dynamic (p) repeated something like 1650 times in a row in measure 108 of the Violoncello part. Attached is a fixed file with the repetitions removed:
AAS 1st Movement XML_fixed.musicxml (2.7 MB)
@3shamrocksmusic I would be curious to see the original MuseScore file, if you are comfortable sharing it. I wonder if it really has 1650 dynamic markings on top of each other there!!
For anyone who is curious about the problematic part of the xml file, it starts at line 112942 and has this text over and over:
<direction placement="below">
<direction-type>
<dynamics>
<p/>
</dynamics>
</direction-type>
<sound dynamics="54.44"/>
</direction>
Excellent sleuthing!
Opening the fixed file, it is also apparent there are hundreds of redundant clefs… I wonder where they came from?
Optical Music Recognition is not easy 
omg.LOL. Thank you so much! It was even on a measure in the cellos that had rests…
I am sort of new at xml…how did you find that? Been a Finale user from version 3.1 to its demise…never really needed xml until this project…Friend’s Dad is a composer, they are trying to get this performed and all they have is a pdf…which they realized is incomplete. The symphony’s 1st movement is like 15 minutest long so optical scanning really is the most efficient way to go…Thanks again everyone for you help!
All OMR software has limitations and may require quite a lot of manual post-processing before it produces satisfactory MusicXML. Usually it’s best to try and fix problems like this close to the source.
Wow! Great job finding the issue!
Sorry, MusicXML is all handled on Dorico side, so I have no clue on that end.
Even if the contents of the XML file are musical nonsense, it seems like the file is technical valid according to MusicXML Tools
I think a program should never crash when feeded valid input, so this is a bug on Dorico’s side.
I think the developers will be thankful for this reproducible case
Thanks for responding. Hopefully someone from Dorico side will be able to give some feedback.