Another crash cost me another composition.
Another crash cost me another composition. (Not that they are only good . . . but nevertheless.)
The attached file will not open.
It seems too small anyway.
Can you salvage anything?
| Attachment | Size |
|---|---|
| 2010-08-28.mscz | 165 bytes |
Comments
Not that they are "ANY" good.
There are two more files without the .mscz associated with the composition.
One of which the page will not let me upload. The other I couldn't tell which was which so I decided to try to upload the original along with it and got accused of trying to upload the same thing more than once and got flagged, so I am afraid to try again. It is is even smaller and starts with a dot.
It's actually the larger file.
Can you salvage anything?
I just get a blank score, no anything.
I could open it, after removing the "," from the extension. I saved it, maybe it helps you.
If you use MuseScore 0.9.6.2 and autosave is on. You should be able to find your files in the session directory.
~/Library/Application Support/MusE/MuseScore/on macC:\Users\\AppData\Local\MusE\MuseScore\on windows vista and laterJust a fractured fragment.
Thanks for the effort, though.
Thanks for the info.
I'm running XP where should I look?
Can they be found in XP?
Would this be the location in XP?
~\Local Settings\Application Data\MusE\MuseScore
I found "a" version of the file. But THE most recent version is corrupted even in this folder. While it should be bigger, It is smaller in size and clicking it only produces a crash. Lost a lot of effort.
Why should autosave get corrupted?
I would say that with a program so prone to crashes that a more elaborate backing up system should be developed. Prehaps one that periodically autosaves under file names that are time dependent, maybe eliminating the older autosaves after say 4 or 5 have been made. Something like file name "autosave filename date time" or "autosave filename 1" . . . "autosave filename 2" up to "autosave filename 5" or some number of saves deteremined by the user.
The way it is now a very bad program clitch autosaves a useless corrupted file.
Why should autosave get corrupted?
I would say that with a program so prone to crashes, and crashes that LOSE DATA, that a more elaborate backing up system should be developed. Prehaps one that periodically autosaves under file names that are time dependent, maybe eliminating the older autosaves after say 4 or 5 have been made. Something like file name "autosave filename date time" or "autosave filename 1" . . . "autosave filename 2" up to "autosave filename 5" or some number of saves deteremined by the user.
The way it is now a very bad program clitch autosaves a useless corrupted file.
I see there is a file called session in that folder, what does that contain?
The session file contains the list of open files if MuseScore crashes. And that happens a very few time for me, on a recent OS, and a recent version of MuseScore. You can upgrade to 0.9.6.2, just use the download link on MuseScore.
The autosave system could be indeed improved to use rolling files.
As far as I understand your first attached file is only 165 bytes and is not a valid zip file so apparently MuseScore crashes while writing the file right? Then we can't find why it crashes, except if you know if there was something special.
I close this bug report since it can be reproduced. It's better using the forum for your support request.
Closed