MSCZ File Corrupted (Crashes Upon Opening) After Editing Gliss
Hi there!
After finishing a complete score, I promptly saved my work and continued to work on another score in the session. I made a great deal of changes (unsaved) and proceeded to add in a glissando where one was needed. It went to the wrong note and after adjusting it (and accidentally directing it in the wrong direction), MuseScore crashed.
Worried about my scores, I restored my session (only to find that it had crashed again). I went through the scores that had been open in the session and only one of them seemed to have been corrupted, but it was not the one that had the adjusted glissando in it, but the one I had saved five minutes prior (the one with the glissando was able to be reopened with all my changes, sans the gliss).
I can't tell where it would have been corrupted and frankly, I spent a lot of hard work on that score that worked like a charm before the session crashed.
I've looked up previous issues and bugs, but I've only seen the duplication of a glissasndo and the files corrupted in those cases were the files altered (not before saving).
MuseScore Version: 2.0.3 revision 3c7a69d
Thank you so much for your help!
| Attachment | Size |
|---|---|
| scv37104.mscz | 25.53 KB |
Comments
See #112656: Crash when opening score with a duplicate Glissando
The MuseScore songbook app for Android crashes ob it too.
Should work (deleted glissando in mscx file)
In reply to Should work (deleted by kuwitt
Was it a duplicate glissando too? If so the 2ND issue of thus sort today, happened at least another 4 times before.
We'd really need some steps to reproduce
In reply to Was it a duplicate glissando by Jojo-Schmitz
Jepp:
In reply to Was it a duplicate glissando by Jojo-Schmitz
Jojo: What I did was I attached a gliss and I started moving it backwards (by accident) and suddenly it crashed. I couldn't tell if maybe it connected to a previous note in a prior measure and that caused the crash, but as far as I was aware, it hadn't and crashed upon the gliss going backwards.
In reply to Should work (deleted by kuwitt
Thank you so much, it works now!
By chance, how did you edit the file to remove the glissando?
In reply to Thank you so much, it works by MLHuntley
Extract the mscx inside the mscz using e.g..7zip, then using a plain text editor on that, search for gliss, spot the duplicate, delete the corresponding lines, save.
In reply to Thank you so much, it works by MLHuntley
There are two native file formats in MuseScore:
https://musescore.org/en/handbook/file-formats-0#musescore-native-format
A mszc file is a compressed mscx file (like a zip file).
So I extracted the the mscx file from the mscz file with a file archiver and opened this file with a text editor and delete the double glissando part.
I opened the repaired mscx file with MuseScore and saved it again with the mscz extension.
In reply to There are two native file by kuwitt
Great, now I can fix this if it happens again! Thank you so much!
In reply to Great, now I can fix this if by MLHuntley
You're welcome :-)
But above: Don't forget to report if something like this or similar happens again ;-).