-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MU4 Issue] MSCZ files corrupted beyond repair, because of corrupted ZIP file #16339
Comments
For example: Original report: #15113 |
Original report: https://musescore.org/en/node/342465 |
Original report: https://discord.com/channels/818804595450445834/818804809784229898/1057744302765256874 |
See also https://musescore.org/en/node/271185 and the many "What links here". |
See also #16334 |
Original report: #16273 |
Original report: #16382 |
Original report: https://discord.com/channels/818804595450445834/818804809784229898/1076199931674644490 |
Please also check the 2 scores from https://musescore.org/en/node/345595 |
It seems we haven't had any similar reports anymore for some time, but to be honest I'm not monitoring MuseScore.org very actively. @Jojo-Schmitz and @MarcSabatella, you certainly have a better idea of the situation; are we indeed no longer getting reports about this, or still? |
We still do, unfortunatly, on a daily basis |
Too bad... Could you collect some of these and link them here? The more data we have, the more likely we'll find a pattern. |
Describe the bug
A few times per month, someone somewhere in the world reports a file corruption where the ZIP container file has become corrupted, so that nothing of the contained score can be saved.
This has been the case for years now, and it is exactly the same in MS3 and MS4 for years now.
The problem exists in several variants:
In this issue, we will collect cases of this. When adding a case, please make sure to add the following information:
Please keep comments clear and concise, and don't use this thread for long back-and-forth conversations, to avoid making it longer than necessary.
The text was updated successfully, but these errors were encountered: