file corruption
I started a score in version 3 and transferred it over to version 4 after it was released. At some point, I don't remember quite when, I began getting a notification that the file was corrupted and have not been able to find any way to fix it. I looked at forums from V3 about file corruption issues but they all relied on using the "show details" feature in the corruption notification, which it seems has been removed. The score still opens and exports as pdf and mp3, and I'm able to work on it and make changes, but I'm not able to publish it online on MuseScore (it comes up with an error message when I try to export or open it). Any help would be greatly appreciated.
Comments
Please attach the score.
See:
https://musescore.org/en/node/289899
In reply to Please attach the score. See… by Jm6stringer
Here's the musescore file:
In reply to Here's the musescore file: by atomicgopher2
Look at Measure 129, staff 15 and Measure 129, staff 18:
![Meas.129.png]( "Meas.129.png")
![fix.png]( "fix.png")
Also...
In 4/4 it would be better to have the eighth note at beat 1 followed by an eighth rest. Beat 2 should show a quarter rest. Beat 3 should show a half rest. This will total 4 beats (with beat 3 clearly exposed):
Same for the other instruments.
In reply to Look at Measure 129, staff… by Jm6stringer
Thank you so much for the help! I'll make those changes pronto. Even if it doesn't help with the corruption issue I'm still glad you helped catch the mistake in my scoring :)
In reply to Look at Measure 129, staff… by Jm6stringer
Update: i deleted and re-entered the measure (this time i decided to use a quarter note instead) and that seems to have fixed everything. Thanks so much for the help!
In reply to Update: i deleted and re… by atomicgopher2
Glad it's all sorted. Looks like it published okay on musescore.com
I have experienced a similar problem (as a Linux Mint user). I spent 4 hours yesterday working on updating a M3 arrangement for my band which today came up as corrupted. No way to see why, and no matter what bad bars I deleted, more and more errors appeared. My general warning is that if you have a significant library of MuseScore 3 work, back it up very securely and do not save a MuseScore 4 file over the top of your M3 work.
MuseScore 4 looks and feels great to use, but it is at best a beta. To a serious arranger there are several issues that make it not ready for real productive work. This corruption issue is certainly one. I believe it stems from the fact that there is no way in M4 to actually delete parts. You can open and close parts, but the remnants remain. This file corruption issue spread over the parts and continued to spread further. In M3 I would have just deleted the parts and reopened new ones from the score. That option is no longer available at this time.
Related issues:
1. M4 works fine from the AppImage, but immediately after I used it for the first time, M3.6 refused to load. When I went into Linux Mint Software Manager to reinstall M3.6, it allowed me to uninstall 3.6, but when it reinstalled it was actually MuseScore 4. I was happy to see this native installation on Mint until I realised it was impossible to to get MuseHub to install MuseSounds on this version even though they were still working in the AppImage version.
2. MuseScore 3.6 installation package is a bit difficult to find on MuseScore.org to reinstall that way. But found this link to an AppImage version that works nicely and allows me safely to get back to my real work until M4 is really ready.
https://github.com/musescore/MuseScore/releases/download/v3.6.2/MuseSco…
In reply to I have experienced a similar… by Dave McGuinness
Yeah I think I'm starting to get the same sense about the software. Really impressive changes but still needs some tuning. Thanks for the github link by the way; I originally uninstalled V3 after downloading V4 cause all my projects were still wanting to open there, but i think it's probably a better idea to concentrate work in V3 for the time being.