MuseScore crashed, can't access backup
Before you tell me to rename the .mscz, file, let me say that I already tried.
I was using the d74469c build for Windows, and though it was completely stable and everything worked fine, I managed to accidentally unplug my laptop while working on MuseScore (with Autosave set to 1 minute, but I guess that just autosaves over the score file, and not the .mscz, backup), and, because my laptop's battery is dead, it completely died and as such the file while now no longer open.
The nightlies seem to create the .mscz, backup file in the same directory as the saved score, and, well, that's all fine, but, the newest .mscz, file I have is from 3 pm today because I most likely had MuseScore open all along since then and worked on it and the autosave just auto-saved the score file, and not the backup.
Speaking of which, if I am correct in all of this, this is the worst backup system ever because regardless of the fact that one turns autosave down to 1 minute, if the file becomes corrupt, one will only have an ancient useless version of their score from the last time they closed the score and reopened it (if I understand this correctly)
I think you guys should change this so that the autosave not only save the score file, but also the .mscz, backup file to prevent people just like me from losing a days work on a score and then hating the guts out of MuseScore.
In any case, I've uploaded my broken .mscz file in case anyone can somehow do some magic trick and open it.
I even hit save before the laptop became unplugged, so it was not in an unsaved state at all, which prompts me to think why on earth does it become corrupt since there was no new data waiting to be written to it, MuseScore just did not close properly.
Perhaps you guys could do something about that too in future versions of MuseScore?
(BTW, I'm running Windows 10 64x Technical Preview with build 10130)
(and yes, I've checked appdata and every other possible MuseScore location folder for a backup file and there are none. Speaking of which, it might be good to update information on where backup files lie when someone uses the nightlies. You do want people to test them, right? Well, in that case, bugs will only come out when people like me actually do real work on a nightly, because that will test the nightly the most as compared to just random clicking of buttons. Ironing out of bugs only occurs when a company "eats its own dog food" as in actually testing their product on a daily basis. And from what I understand, the stable builds are nothing but a glorified nightly, the latest nightlies incorportaing the code from the stable build but perhaps having newer code that causes problem. Today I have not had any hangs or crashes or slowness at all through the nightly I was using, and, were it not for my stupid dead battery, I would have had a perfect day with it. But then again, I wouldn't have started this thread and you guys wouldn't have improved the backup mechanism. :D)