Corrupted File

• Nov 16, 2024 - 23:06

I was working on this one last night. Turned my computer back on, and it appears to be corrupted and unopenable. The backup is the same. Any help?

Comments

• Nov 16, 2024 - 23:36

The file you attached could not be recovered.
Musescore saves backup files in a hidden .mscbackup folder, which is located in the same place as your project file.
There should be a file named .name_of_your_file.mscz~
where "name_of_your_file" is the name of your project file.
Copy it to another location, remove the ~ from the file name and try to open it.

Reply

• Nov 17, 2024 - 11:30

This won't help with your current file but, given that this is an on-going issue with MS4, you could implement a file versioning scheme to mitigate any future losses. It is very easy to manage, requires no extra software and costs you nothing but a few seconds of your time.

See https://musescore.org/en/node/369244

Reply

• Nov 17, 2024 - 14:02

It is an MS4 issue; I have seen many reports of it from MS4 users so it definitely hasn't gone away.

Is there any data that implicates a specific OS and that it's related to zipping the file. If so then an option to set the default to mscx could be useful. (Maybe there is already such an option.) I don't know which version the OP is using.

Reply

• Nov 17, 2024 - 14:49

@yonah_ag The source of this problem may be disk write cache. The Microsoft website writes: turning disk write caching on may increase operating system performance; however, it may also result in loss of information if a power failure, equipment failure, or software failure occurs.
https://superuser.com/questions/845270/what-could-cause-the-files-to-be…
https://community.notepad-plus-plus.org/topic/13302/fix-corrupted-txt-f…

Reply

• Nov 17, 2024 - 15:11

But disk write caching could be a common denominator. I presume other OSes also do this so the Microsoft info could be relevant.

I held back from updating from MS2 to MS3 because of reports of file corruption but eventually I did and I have never suffered from a corrupted file, (I'm now on 3.7), but I still implement score versioning.

File versioning is so easy to implement, (I use a plugin), that it would be a useful option to have in the core MS program.

Example:
FV04.png

Reply

• Nov 17, 2024 - 14:59

>Is there any data that implicates... that it's related to zipping the file.<

I've read chatter on the forum about the possibility of file corruption occuring during compression (zipping the file).
In my experience, as files have been submitted over the years, I have noticed that
...some were posted with file size 0kb, so obviously nothing there
...some were posted with a reasonable file size but contained kilobytes of zeroes rather than score data.
...a (very) few I was able to fix with a zip repair tool.
Finally...
...one was actually a pdf masquerading with a MuseScore .mscz file extension (I think Jojo solved this one).

I also recall some kind of reporting thread in the forum which collected information from people encountering this corruption issue.

Reply

Do you still have an unanswered question? Please log in first to post your question.