I can't open any of my files.
I am a high school student, and I've been working on a project to be played in my high school band for our end of year concert. I'm expected to have all the parts ready to go, and yet I can't open my files at all. It is a big project, roughly 250 measures, but before today everything was running and playing just fine. If someone could please help me to get this to work, that would be amazing.
Comments
In order to help, we'd need to attach one of the files you are having trouble with, and explain what goes wrong when you try to load it. Also, say what version of MuseScore you are using and what OS you are on. Meanwhile, see for https://musescore.org/en/node/52116 information on recovering from a backup copy.
In reply to In order to help, we'd need by Marc Sabatella
Thing is, it won't let me link the file because it can't read it as a file. When I tried to link it, it said "file cannot be read". The problem is that it simply says "error: cannot read file". I'm using MuseScore 2.0.2 on Windows 10
In reply to Thing is, it won't let me by ohmygazzers
I'm not sure how you are trying to "link" the file, but if the filenames ends in ".mscz", you can attach it here - just click the "File attachments" link right below where you type your reply.
It seems like perhaps there was a crash that happened at the exact moment you tried saving that particular file, but if so, then only that one file would be affected, and you should still be able to recover a backup version as explained in https://musescore.org/en/node/52116. If truly *all* of your files simultaneously became unreadable, then I'm afriad the problem might be more serious - your hard disk might be failing. In which case, hopefully you made a backup of the disk at some point, as it probably needs to be replaced.
Here is the file that I cannot get to open at all.
In reply to Here is the file that I by ohmygazzers
Indeed, that particular file does seem corrupted. If this is the only file corrupted on your machine, then hoepfully your disk has not failed, and you will be able to recover from one of the backups MuseScore creates, as explained in the link I posted previously.
In reply to Indeed, that particular file by Marc Sabatella
Where exactly would I find these hidden files that I need?
In reply to Where exactly would I find by ohmygazzers
The backup file (starting with a period) is in the same folder as the score itself. The autosave filesare in a folder whose location depends on what OS you are on; the article I linked to explains where to find it for most common operating systems.
In reply to The backup file (starting by Marc Sabatella
I did what the page said and yet it still will not open the file for me. Is it pretty much a bust at this point?
In reply to I did what the page said and by ohmygazzers
Well, merely locating the backup file wouldn't help you open the original - you need to rename that backup (to remove the leading period and trailing comma) and try to open *that*. Are you sayng that file wouldn't open either? Can you attach it here?
What about the autosave file - did you try to oen all the files in that folder to see if any of them are your score?
In reply to I did what the page said and by ohmygazzers
For Windows 10, also see:
https://musescore.org/en/node/89781#comment-395831
Regards.
In reply to Indeed, that particular file by Marc Sabatella
Marc, I managed to open that file with Notepad, but there's almost nothing in it. It contains these few lines of code:
PK ÕK}H@´b]• Í META-INF/container.xmlUŽ±
Â0 ÷~EÈÞVÁ!mQÁI·º¸[>]BòÚÒ÷$Òþ½êxËÝ©jì½xbS!×ÙJ
$ÃÖQ[Èk}Jw²*e˜¢v„¡L„P96Îã0Ó‚Eóð>½ëزîÎØ"Yànè†Í6v°'rsP‡ .h=N)™ †M6ë3ÊùíÎòo+ÿ‹«|qö
...and then a huge stack of totally blank lines. (Note that I had to put the > in the second line in square brackets to prevent the website from misinterpreting the code-string.)
Any guesses as to what went wrong?
In reply to Marc, I managed to open that by Recorder485
There is a bug in 2.0.2 (already fixed for the coming 2.0.3 release) where if MuseScore (or OS) crashes *while* saving a file, you can get this sort of corrupted file. Generally the backup and/or autosave file should still be good, though.