Problem with "corrupted files"
Hi, gang!!!
I tried to open an score, created with MuseScore 2.3.2, with MuseScore 3.0.1, and... I got very rare messages about "corruption":
https://musescore.org/sites/musescore.org/files/2019-01/Captura%20de%20…
But... If you see this image from the file:
https://musescore.org/sites/musescore.org/files/2019-01/Captura%20de%20…
There is no any kind of "corruption"!!!
So...
I used to get this kind of messages with files created with MuseScore 0.x and 1.x, and it was about some final empty bars, only.
This is not the case.
Is it a bug???
Blessings and Greetings from Chile!!!
JUAN
| Attachment | Size |
|---|---|
| Captura de pantalla_2019-01-21_00-16-25.png | 157.62 KB |
| Captura de pantalla_2019-01-21_00-17-46.png | 271.24 KB |
Comments
We would need to see the file to truly understand what's happening. You can probably see the corruption if you exchange voices 1 & 2 in the corrupt measure twice. Chances are it was corrupt in version 2, but version 3 actually saw it, or the algorithm is a little different. See https://musescore.org/en/node/54721
In reply to We would need to see the… by mike320
This is the file:
In reply to This is the file: by jotape1960
Here's a picture of measure 380
![measure 380.PNG]( "measure 380.PNG")
it shows the corruption you can see after I exchange voices 1 & 2 twice.
The only way to fix this is to reenter the measures.
In reply to Here's a picture of measure… by mike320
I see!!!
BTW: It is not the only circumstance when we would want MuseScore could to fix it automatically. Maybe in the future... ???
In reply to I see!!! BTW: It is not the… by jotape1960
If you have the version 2 file, it might help to attach it to see if a programmer can find a way to fix it so you won't have to reenter the measures in a future version. Corruptions like this should not arise during import.
Someone else will need to see what needs to be done to fix it and if a bug report is called for.
In reply to If you have the version 2… by mike320
Hi, Mike320!!!
I uploaded the original MIDI file version, and (from that) the MuseScore 2.3.2 version of the same file.
If you open whatever those versions, with MuseScore 2.3.2, there is not errors.
If you open the file version made by MuseScore 2.3.2 with the new MuseScore 3.0.1 portable... Then you will get the "corruption".
Maybe a bug???
In reply to Hi, Mike320!!! I uploaded… by jotape1960
I didn't look at the origin of the score. If you open the MIDI in MuseScore 3.0.1 there is no corruption either. As I said before, a programmer would need to decide if this is a bug. If you want to make sure it gets considered at a bug feel free to enter it into https://musescore.org/en/node/add/project_issue?pid=1236
Make sure you explain that the 2.3.2 score and 3.0 scores are both imported with no corruptions, but when you import the 2.3.2 into 3.0.1 there is a corruption. This is a bug, the issue is weather it will be fixed since 2.3.2 is no longer being fixed, but 3.0 shouldn't be corrupt.
In reply to I didn't look at the origin… by mike320
I prefer to wait somebody more expert than me decide if this is or not a bug. But... I think it is very weird!!!