Song file corrupted?
I have been in the process of going back and updating my old scores with the new MuseScounds. The process had been completely smooth, until I reached this score. When I had tried uploading it earlier this month, the uploading screen was stuck perpetually loading.
When I went back to try and do it again today, MuseScore warned me that the file was "corrupted". I have absolutely no idea why this is occuring as all I did was update the soundfont and some of the notes.
| Attachment | Size |
|---|---|
| Stardust Crusaders (Jotaro Kujo's theme).mscz | 67.72 KB |
Comments
Do you use the latest version of MuseScore (4.0.2.)?
The mscz file is a zipped folder, so open it with a zip tool and extract the mscx file. Try to open that.
In version 3.6.2 it opens without problems.
Update to 4.0.2 first, that score stems from 4.0.1 (and is corrupt)
Then check How to fix MuseScore 4 corrupted files
I must admit though that I fail to see any corruptions (which are all reported in Bass Drum)
I opened it in MuS 3.6.2 and found a lot of totally empty measures, not even a whole rest in them.
Edit:
Yes, these empty measures are caused by an inconstistent naming convention between MuS 3.x and Mus 4.x in the mscx file.
MuS 4: <MeasureRepeat>
MuS 3: <RepeatMeasure>
That is really bad!
So the empty measures aren't the reason.
In reply to I opened it in MuS 3.6.2 and… by HildeK
Shopuldn't be a problem, not when going from Mu3 to Mu4:
And the way back isn't supported anyway.
I guess Mu3 doesn't report corruptions because it justr ignores that unknown tag?
In reply to Shopuldn't be a problem, not… by Jojo-Schmitz
The way back is not supported, yes. But unfortunately, it hinders cooperation.
The result is a completely empty measure that cannot even be edited. Corruptions are not reported but I need to double check if saving and reopening in 3.6.2 would report an error.
In reply to The way back is not… by HildeK
That's why I added it to my 3.7 😉
In reply to That's why I added it to my… by Jojo-Schmitz
Yes, I understood that. And also that I need a Github account to access 3.7, which I don't have so far.
I checked to see if saving and reopening the file in 3.6.2 then reports these errors. Yes it does.
And you can correct this only by adding the same instrument again and copying the 'good' measures into this new staff. Can be a lot of work...
In reply to Yes, I understood that. And… by HildeK
Or use search and replace on the mscx file before saving it with Mu3
In reply to Or use search and replace on… by Jojo-Schmitz
Good idea (why didn't I think of it myself?) and it works perfectly.
I suspect that the tag "measureRepeatCount" is simply ignored and works too as there are only single measure repeat sign in the above score.
[ replace "MeasureRepeat>" by "RepeatMeasure>" in the mscx file - for others having that problem ]
In reply to Good idea (why didn't I… by HildeK
If measureRepeatCount is 1, that's what Mu3 can handle, if it is 2 or 4, only Mu4 can. Mu3 would indeed just ignore it and handle as a single measure repeat
In reply to If measureRepeatCount is 1,… by Jojo-Schmitz
Yes, I thought so too.
In reply to I opened it in MuS 3.6.2 and… by HildeK
But I'll add that compatibilty fix to my 3.7
According to MuseScore, yes, I am using the latest version. I had scrapped the original base drum part entierly and replaced it what the one you see now. I do not recall if I just copied and pasted the notes over to the new one, but if I did, would that be a cause for the issue?
Nevertheless, this was working fine when I had initially began updating the score. I was not getting any corruption warnings until recently, after not having opened this score for nearly a month.
Also, how do I run the RepairAssistant qml file you've linked me to?
In reply to According to MuseScore, yes,… by Zenosphere
Since 3.6.2 only had the problem with the repeat measure signs and I corrected that, the file works without errors.
Maybe it will work correctly if you open it with 4.2. See attachment and check it. Maybe you need to add some more repeat measure signs - it is a large score :-).
In reply to Since 3.6.2 only had the… by HildeK
Works in 4.0.2, only the title frame texts lost their style
Just checked it. It works perfectly well now, I just had to go back and fix the text and make a small change to one part.
The completed version is now back online!
Thank you for your help!