Musescore crashes when opening musicxml file
S2 - Critical
1) Open the attached musicxml file created with Capella-Scan Version 9
2) Musescore crashes
I opened musicxml files created by Capella Scan previously sucessfully. Anyway Musescore should not just crash when opening a file.
|Rebel Les Eléments Caprice.musicxml||843.45 KB|
The artifacts from PR #9000 open it without crashing (so one of the numerours fixes in it seems to fix that), but report corruptions:
In reply to The artifacts from PR #9000… by Jojo-Schmitz
Sorry Jojo but what does that mean?
See How to fix a score that contains corruptions
In reply to See How to fix a score that… by Jojo-Schmitz
I do not get even the dialog that warns about corrupt xml. Musescore just crashes, no dialog or message box, nothing just dialog asking for details about crash.
Use the mscz file I attached or the artifacts from PR #9000 to load without crash. And then fix the corruptions.
That crash is critical, but certainly not blocking you from using MuseScore entirely
MuseScore 4 doesn't crash on it either , so this issue is fixed
It also reports corruptions, but these are like caused the by exporing software rather the importing one.
Seems it is Capella's Cap2Music.py
Not sure, might be worth a separate issue, reg. the corruption when importing such a file
OTOH MuseScore's PDF import, using Audiveris, pretty frequently has the same issue
In reply to (No subject) by Jojo-Schmitz
I'm not at my computer right now but what version of Musescore could open the file? As far as I know I have latest 3.6 and it bombs out straight after trying to open the file, no warning at all. Now I have not tried version 4 but thats just an alpha so I would not use it for production work. I am actually producing parts from a score for rehearsals and I still have several other movements to do and I don't want to run into the same problem again.
As said: the Articfacts from PR #9000 (basically a development build, needs a GitHub account) and the MuseScore 4 Beta 2 and later nighly builds.
The former produced what I attached above, so just take that and fix the corruptions MuseScore 3.6.2 reports on it.
Thanks. I am not getting into a development build but I'll try 4 beta if the problem occurs again. Thank you very much again for your help. Really appreciated.
The MuseScore 4 Beta has the disadvantage that the mscz files it creates can't be read with MuseScore 3 anymore.
But you'd need neither, just take the mscz I attached further up, it does work with MuseScore 3 (and 4, if need be)
Automatically closed -- issue fixed for 2 weeks with no activity.