Score has become corrupted

• Nov 26, 2024 - 15:52

After three months of working n a score, I finished it today. I have been listening through to the piece to see if there were any incorrect chords. I got about halfway through when I decided to leave it for a while. I tried to save and close the file, but was advised that the file had become corrupted. The explanation was that in measure 1366, it was saying that there was a quaver extra in the flute part over the score, and sure enough when I looked that was indeed the case. I don't even know how you can add an extra quaver in on one part and not the score (not to mention that this section was not something I'd even looked at today). I deleted the flute part from those bars and 'saved anyway' when it said that the issue had not been resolved. 'I'm hoping someone can fix my issue or show me how to fix it please. Bar 19 of movement 6 or thereabouts.

Attachment Size
Brahms - Serenade No. 1, Op. 11.mscz 2.41 MB

Comments

My 3.7 reported that measure 1367 of the flute is too long. As this measure is empty anyway, I simply deleted it. (Expected: 2/4. found 3/4). Then all is ok ...

Edit: Maybe you deleted it in the parts - I did it in the score because 3.7 does not read the parts.

Attachment Size
Brahms - Serenade No. 1, Op. 11-b.mscz 295.49 KB

Here MuseScore 4.4.3 doesn't even open that score, it just hangs and needs to get killed.
3.7 doesn't report any corruption, no wonder: 3.x doesn't even look at part when checking for corruptions.
The score stems from 4.3.1 -> better update to 4.4.3

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