File Corruption
Since updating to MuseScore 4, nearly every time I reopen a score, MuseScore tells me that the file is corrupted. Even after fixing the “corruption” (which is usually a few rests throughout the file), when I close and reopen again, the file becomes corrupted again. This has happened to most, if not all, of the files I have used with MuseScore 4. Anyone encountering the same problem? Any fixes?
Comments
Search on "corrupt 2022" for the many previous reports
Yes, I'm having the same issue. Not sure how the file got corrupted, but each time I open it I get the corrupted message, fix everything, save it and when I reopen it, I'm right back where I started.
From what I see so far of version 4, it is not very stable. Some instruments randomly quit playing when I do a playback, and the parts seem to be a mess.
Very disappointed.
In reply to Yes, I'm having the same… by HerbSmith
Well, the first thing to do is to join the file(s).
That's the only way we can start investigating the cause(s).
In reply to Well, the first thing to do… by cadiz1
Here it is. Tried Save As with a new name. Nothing seemed to help. Could not get it to produce a correct Baritone Sax part even after fixing all the anomalies I could find. Made a copy of the baritone sax part with another name and it was different, but still incorrect. I've spent days on this piece and I'm just spinning my wheels now.
In reply to Here it is. Tried Save As… by HerbSmith
All the instrument parts are scrambled. When I try to make a tie between notes across a measure, the whole program crashes. Various parts like bass guitar and drums wind up with crazy amounts of beats in a measure as though rests of various sizes are being randomly sprinkled in. Its all very confusing.
In reply to All the instrument parts are… by HerbSmith
FWIW, I played with this a bit.
I opened your score. MS4 said it was corrupt, but opened it anyway. I only scanned it but it looked and played OK. Parts were a mess.
I saved it as an mxl. When I opened the mxl, it still said corrupt and opened it anyway. Parts seem to be OK.
I saved it as an mscz. When I opened that it still said corrupt but opened anyway. Parts seemed to be OK.
I have no idea where the corruption is.
In reply to FWIW, I played with this a… by bobjp
FWIAW, i saved it as MusicXML and opened it in 3.6 because it reports where the corrupted bars and staves are. Unfortunately there are a lot:
(Bar Stave (s))
50 8
52 8
56 2
58 2
62 8
64 8
66 8
68 8
70 9
72 9
78 8
80 5
85 9
87 8
88 8
90 7
92 8
96 2, 5, 8, 9
98 5, 7, 8, 9
99 5
100 9
102 8, 9
In reply to FWIAW, i saved it as… by underquark
Well, I obviously spoke too soon. Parts weren't OK. Just better. I missed all the dotted half rests. I find it interesting that all the staff numbers are incorrect. One has been added to all of them.
In reply to All the instrument parts are… by HerbSmith
Ok, so I saved the corrupted file as a MusicXML file so I could open it with version 3.6.2. When opening it I was again told it was corrupt but it gave me a full listing of the issues it was having so I was able to track them all down and get it fixed. I obviously was not finding every issue. I saved it as a Musescore file and was then able to open it back in version 4. The only issue upon opening it in version 4 was that it picked up a piano (I think) voice for the drumset, which was easily corrected. Does version 4 give a list of issues somewhere? It doesn't on the opening window when it says its corrupted as it does in version 3.6.2. I've attached the corrected version 4 file, in case anyone is interested.
In reply to Ok, so I saved the corrupted… by HerbSmith
That details dialog about corruptions is supposed to come back in a later release
In reply to Ok, so I saved the corrupted… by HerbSmith
I think all this corrupted stuff happened when I did a 44 measure copy, added a 44 measure block of measures later in the original piece and then pasted that copied block into the space I created for it. The piece was fine up to that point. That's the only thing I can think of that could have scrambled things the way it did.
thanks!