corrupted score
i was imputting Rachmaninoff's Rhapsody on a Theme of Paganini reduction for 2 pianos so i could listen to it as a part of my collection of manually putting rachmaninoff pieces in musecore i was on variation 17 and changed the time signature on piano 1 to 12/8 and piano 2 to common time, a couple measures later i switched the piano 1 to 6/8 and piano 2 to 2/4 and when i was imputting a 2nd voice for piano 1 my score generated rests that shouldnt belong it gave me rests of all kinds from 16th to 256 and the measure only had 8th notes, i deleted the measure but when i went to reopen the file it never would open and now i am begging anyone to please help me restore my file even if it means cutting off chunks of it for me to be able to work on it, please and thank you for help.
| Attachment | Size |
|---|---|
| Rachmaninoff Rhapsody on a theme of Paganini.mscz | 507.11 KB |
Comments
I opened the MSCZ file in Ark, extracted the MSCX (uncompressed file), opened it in Bluefish editor and removed one of the measures where 12/8 was entered. This then allowed me to open it in MS 4.4.4 with errors.
I've attached two files:
Test1 is still corrupted but you can open it, try to repair it yourself and maybe copy some of the later bars to another score.
Test2 has been cropped after about measure 620 - everything beyond that gone but everything before then intact.
In reply to I opened the MSCZ file in… by underquark
thank you so so much
I cut the score down to 625 measures.
Can you reproduce this issue again?
In reply to I cut the score down to 625… by mercuree
the issue was musecore didnt like it when i made piano 1 6/8 when the other piano 2 was in 2/4, i think that is what made the voicing unstable
In reply to the issue was musecore didnt… by cactuarkid
That might be a know issue, with local time signatures
I opened it with 3.7 and could not find any error!
In reply to I opened it with 3.7 and… by HildeK
But opening that in 4.4.4 makes it go into an endless loop. Same as the original file
Confirmed, latest development build too goes into an endless loop, seems best to report this in the issue tracker on GitHub
I was able to reproduce the freeze from scratch. Are there steps you could do here? eg removing rests from voice2?
Video: https://github.com/user-attachments/assets/20f5f826-522b-41a6-b6b7-a269…
In reply to I was able to reproduce the… by mercuree
Reported on github https://github.com/musescore/MuseScore/issues/26001
In reply to Reported on github https:/… by mercuree
This issue was already reported on this forum a few days back and understood (local time signature, and voice change of a note): https://musescore.org/en/node/373427
But I hadn't taken the time to report it on Github (or to check whether this was already known, given the liabilities of local time signatures!)
Thanks for doing so.