"File “” is critically corrupted and cannot be processed" message!
Please help! Last night I finished the score I need to turn in tomorrow. I had to make some corrections, so today I tried to open the MuseScore file but the message "File “” is critically corrupted and cannot be processed". I don't know what to do because if the MuseScore file doesn't open, I would have to start from scratch again, and I don't have enough time. Please, if anyone knows what to do in this case, I appreciate the help!!
| Attachment | Size |
|---|---|
| Alimento Espiritual.mscz | 33.54 KB |
Comments
The score does a a few very strange measure lengths, of "xxxx/786", while the max. denominator is 128 (in Mu4 and Mu3.7, was 64 in Mu3.6.2)
I corrected those, check whether this is what you want
I was able to save the score from the "Rap Motilonas" mark.
The first part needs to be rewritten.
To do this, add the required number of measures at the beginning and rewrite it.
In reply to I was able to save the score… by HildeK
Mine would be fully revovered, having divided numerator and denominator of the offending messages by 6
In reply to Mine would be fully… by Jojo-Schmitz
I didn't know where the limit of the denominator could be. But of course: the shortest note is 1/128! Then I also realized that you divided by 6.
And you asked the most important question: "How did you manage to get the score into that state"
In reply to I didn't know where the… by HildeK
I didn't know that either, the error message in 3.7 told me 😉
Followed by at look into the source code
In reply to I didn't know that either,… by Jojo-Schmitz
Looking into the source code is not my world, even if I occasionally write some C for a µC :-).
In the 3.7 error message it only says: MSCX error at line 492: invalid bar length: 1728/768
In reply to I didn't know where the… by HildeK
Notes can go shorter, IIRC 1024 is the shortest
Brings up 2 question:
How íd you manage to get the score into that state
Why doesn't Mu4 report this the same way as Mu3 does, Mu4 writes the error only to the log, Mu3 prints it
Here one of them, in German
MSCX Fehler in Zeile 0: Ungültige Taktlänge: 1728/768
as taken from MU4's log. Note the line number is wrong too, Mu3 reports
MSCX Fehler in Zeile 492: Ungültige Taktlänge: 1728/768
And directly in the error dialog...
Reported the latter in https://github.com/musescore/MuseScore/issues/20728
Or try one of these that will open in there respective versions. Or maybe in both, hard to tell any more. I didn't have to rewrite in the first section. I did have to remove the 4/4 and the 6/8. Then add a measure and C+P some sections to the left one beat.