Musical piece crashes - problem is in .mscz file
I have a musical piece, currently unfinished, composed on MuseScore, which crashes (and shuts down MuseScore) almost every time a change is made. Even a small change, like adding a whole note, can crash the program. This happens with version 2.0.3 and with several nightly builds. So I assume the problem is in the .mscz file somewhere. There is no popup warning me that the file is corrupted.
I really don't want to start a new piece, and manually re-write every note, every dynamic marking, etc. So I tried to copy-and-paste onto a new blank file -- and that crashed, too.
Is there a way for me to look inside the .mscz file and find the bug?
Thank you for all answers.
shoes6
Comments
Could you attach here your score?
use the "File attachments" option at the bottom of the page, just above the Save and Preview buttons when you're typing your post.
But FWIW, an MSCZ file is just a ZIP archive. Open it normally, extract the MSCX file within it, open it in your favorite text editor, and have fun exploring. Unless you have built a debug version of MuseScore, though, you are unlikely to figure out the problem this way.
File attached as requested.
I repeat, this is a work in progress. It's not ready to be judged for its musical value.
Thank you.
In reply to File attached as requested. by shoes6
If your working with an nighly build, please do report issue in the Technology Preview forum
The problem occurs in all versions of musescore that I have, both old and new, so the fault is not in the build. If the .mscz file turns out to be innocent, then my next guess would be windows. Where should I start looking, for glitches in windows 8.1 that could crash musescore? I should have asked this earlier.
In reply to The problem occurs in all by shoes6
You made this with a nightly build. Save it with 2.0.3 and see what happens. Then 2.1 just to double check it. That will help confirm compatibility between 2.1 and 2.0.3. 2.0.3 knows this is a later version.
I really don't want to start a new piece, and manually re-write every note, every dynamic marking, etc
Then don't use a nightly build! There is a big big warning that these are not intended for anything serious and that they will crash.
In reply to I really don't want to start by [DELETED] 5
Here the fixed file: 11-19.mscz
The trigger of the crash was in measure 147 in the top staff (I added voluntarily after this a new dotted half note, but no matter). Corruption not detected by MuseScore (2.0.3 and current 2.1 dev.)
![culprit 147 top staff.jpg]( "culprit 147 top staff.jpg")
But the repairing (simply deleting the content of this measure, with Del) caused several other problems of corruption.
Time signatures added unnecessarily (eg two 4/4 immediately following one after another) seemed to have played a role in this corruption. I pass the details to fix this.
Thank you for all help.
One person asked for the "history" of the file. I worked on it with several nightly builds - sorry, I can't tell you which one(s) caused the problems.