Deleted Work
Many times I have created songs in Musescore 2.0.3 but then before it is finished and uploaded, it gets "lost." Whenever I try to go and open the file Musescore will say the file is unreadable. Even if I opened the file just the day before. This has happened many times and I'm tired of losing my work and then scrambling to try and remember what I wrote. I have emailed Musescore directly but they've never been able to help me. I sent them the "unreadable" file but they said it had "nearly no information." Then they suggest opening up the version the Musescore AutoSaves then hides in the Hidden Files section of my computer. But when I found the file and tried to open it, Musescore again said it was unreadable. So it's really upsetting that even the failsafe Musescore created doesn't even work. I'm not sure if anyone would have a way of fixing the file, opening it somehow, or even creating it into a PDF so I can at least see it, but I just really need some help because I cannot remember a lot of what I wrote in my piece. I will attach the file that will not open down below.
P.S. If somehow anyone is able to fix the issue, please email me at brendan.summers@outlook.com
Thank you very much,
Brendan Summers
| Attachment | Size |
|---|---|
| Oasis.mscz | 35.5 KB |
Comments
Unfortunately, the file you attached won't open in my system, so I can't help you.
What version of MuseScore did you use to create it, and what OS (Operating System) are you running on your computer?
In reply to Unfortunately, the file you by Recorder485
Musescore 2.0.3 and my OS is Windows 10
I don't know anything about computers, but I think this has something related to https://musescore.org/en/node/15028
I saved your score as an xml file, opened it in my web browser, and this showed up:
I can see a small similarity with what the OP experienced on that thread. Again, I have nil knowledge of these things, and you should consult someone who has done fixes for these (ninozagreb, for example).
The file lost ist content, the .mscx file embeded in the mscz, so for this file all hopes are lost. Check whether you find a backup file
Are you sure this has happened "may times" using 2.0.3, and not some previous version? There were known bugs that would in rare cases cause this sort of corruption if a crash occured right in the middle of a save operation, but these were fixed for 2.0.3. It shouldn't actually be possible to create this type of condition any more. So if you are still seeing this, there must be something quite unusual about your workflow. Any insight you can give into what you might be doing that would lead to this would be helpful in understanding what might be happening.
At this point, though, disk failure seems a possible explanation.