when I save my uncorrupted file, close, and then reopen it, it becomes corrupted.

• Apr 23, 2025 - 06:03

Have tried this multiple times to no avail.

I was able to upload it to musescore.com in its uncorrupted form.

I tried uninstalling MSS, but it did not work.

I tried copying and pasting to a new file, which did not work. I may have to reenter the whole file.

It doesn't happen with older files.

There was a power failure while the file was open, which may be the problem.

The score seems to be fine. The parts are where the problem shows up. It may have something to do with the time signatures.

By the way, MuseScore.com could not make a YouTube video of it so far.

Attachment Size
Sinfonia #70 orig.mscz 1.24 MB

Comments

• Apr 23, 2025 - 07:14

In what format did you download this score from musescore.com? In any case, given your difficulties with this score, my choice was to export it in MusicXML format. The first effect of this is to simply delete (not just reset) the parts. But that's not all. It often has the virtue of resetting other parameters, which very often stabilizes the file permanently. I then recreated the parts. If you had done the layout, of course, it's very annoying. Forget my suggestion if it's too much work for you (and do an individual reset of the “sick” parts), but at least you've got a healthy file again.
See: 1Sinfonia #70 orig.mscz

Reply

• Apr 23, 2025 - 08:15

Exporting in MusicXML format is much simpler and quicker (and it's the same procedure as for any other format, mp3, pdf etc.). The other advantage, apart from getting rid of the parts, is that it can also act on the main score, to rectify certain things (I can't think of a precise or recent example though)

Reply

• Apr 23, 2025 - 10:54

I was able to reproduce the problem in a new, much simpler, shorter score. There appears to be a problem with the change in meter near the DC al Coda. Also, with the change in meter before the end. Curiously, as I went to copy and paste the error report, the problem disappeared. I post the file here as a formality. Still, there are the same problems with sinfonia #70 remaining.

Attachment Size
experimental1.mscz 98.83 KB

Reply

• Apr 23, 2025 - 11:06

This version is with notes and errors in the parts, same file.
Incomplete measure: Part score: Flute, measure 8, staff 1. Found: 1/1. Expected: 6/8.
Incomplete measure: Part score: Flute, measure 9, staff 1. Found: 15/8. Expected: 6/8.
Incomplete measure: Part score: Flute, measure 10, staff 1. Found: 7/8. Expected: 6/8.
Incomplete measure: Part score: Flute, measure 11, staff 1. Found: 1/1. Expected: 6/8.
Incomplete measure: Part score: Flute, measure 12, staff 1. Found: 15/8. Expected: 6/8.
Incomplete measure: Part score: Flute, measure 13, staff 1. Found: 7/8. Expected: 6/8.
Incomplete measure: Part score: Flute, measure 14, staff 1. Found: 1/1. Expected: 6/8.
Incomplete measure: Part score: Flute, measure 15, staff 1. Found: 15/8. Expected: 6/8.
Incomplete measure: Part score: Flute, measure 16, staff 1. Found: 7/8. Expected: 6/8.
Incomplete measure: Part score: Flute, measure 17, staff 1. Found: 17/8. Expected: 12/8.
Incomplete measure: Part score: Flute, measure 18, staff 1. Found: 21/8. Expected: 12/8.
Incomplete measure: Part score: Flute, measure 19, staff 1. Found: 25/8. Expected: 12/8.
Incomplete measure: Part score: Flute, measure 20, staff 1. Found: 24/8. Expected: 12/8.
Incomplete measure: Part score: Flute, measure 21, staff 1. Found: 24/8. Expected: 12/8.
Incomplete measure: Part score: Flute, measure 22, staff 1. Found: 24/8. Expected: 12/8.
Incomplete measure: Part score: Flute, measure 23, staff 1. Found: 24/8. Expected: 12/8.
Incomplete measure: Part score: Flute, measure 24, staff 1. Found: 24/8. Expected: 12/8.
Incomplete measure: Part score: Flute, measure 25, staff 1. Found: 24/8. Expected: 12/8.
Incomplete measure: Part score: Flute, measure 26, staff 1. Found: 24/8. Expected: 12/8.
Incomplete measure: Part score: Flute, measure 27, staff 1. Found: 24/8. Expected: 12/8.

Attachment Size
experimental1.mscz 100.05 KB

Reply

• Apr 23, 2025 - 12:55

Basically, your score is corrupted. An example: delete the last time signature 12/8 and you get a crash. Then, if you export it in MusicXML format, you also see that there's a problem, since this export has deleted the 9/8, and you see the corruption of the following measures (with the little "+" above the staves).
corruption.png
Just put back a 9/8 to stabilize the problem.
fix.png
I can't reproduce from scratch, at least after a few first attempts. It's worth continuing to try, there may be a certain sequence of actions required to trigger the problem.
In the meantime, could you provide the original link to the file on musescore.com? It's possibly an "old" file (I mean from a previous major version) and something would go wrong with the new version? All this has to be checked, of course.

EDIT: as advice, it's pointless in your posts to report all the corrupted measures (as here: https://musescore.org/en/node/378016#comment-1290823).
We can see for ourselves when we open your scores, and this makes your posts unnecessarily cluttered.

Reply

• Apr 23, 2025 - 18:06

thank you for the advice. I only use the latest version 4.501. the experimental1 file is new, as is the sinfonia #70. The former was not posted to musescore.com. I did not use templates or reuse files.

Reply

• Apr 23, 2025 - 21:23

So, after further investigation, I can reproduce from scratch. Tricky issue. I need to refine to understand all the ins and outs (there's no single scenario, rather two or more) , but I could file the bug report right now, since I have a test file and the step that triggers the problem/corruption. It's a bit late here, so I'll finalize things tomorrow.

Reply

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