Importing old .ove file makes MuseScore crash
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S1 - Blocker
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
I have an old .ove file that I would like to import into MuseScore and work on it. But when I opened it, MuseScore simply crashes. There is no error message so I'm not sure what's wrong.
Is there any log file?
I would like to upload the .ove file but your webpage doesn't allow it.
Thanks
Fix version
3.3.0
Comments
You can upload any file by zipping it first. All kinds of zip files can be uploaded.
Oh! Thanks a lot!
I think there is something wrong with the code for importing pedal markings from .ove files. I have not yet been able to correct the code, but I was able to modify it so that I could open your score. MuseScore informed me that measures 31 and 50 had the wrong number of beats, so I fixed them for you.
OK, thanks!
I realized that the ove contained some Chinese characters. Are they also the cause of the crash?
I managed to find an old Overture 4 program. I then opened the ove file inside it and removed all Chinese characters that I found. I saved it to a new file which I opened in MuseScore but it still crashed.
Do you want the new ove file without Chinese characters to have a try?
In reply to OK, thanks!… by Horinius
Chinese characters do not cause MuseScore to crash. Did you try to open the score that I uploaded?
See https://musescore.org/en/node/276097
In reply to Chinese characters do not… by mattmcclinch
Yes, I opened it and it seemed good. Thanks.
Let's continue the discussion on the forum.
it is a crash after all...
In reply to (No subject) by Jojo-Schmitz
A little following up:
Tried in MuseScore 3.0.5 Microsoft Store app and v. 3.0.4 and 3.1.0 native app
They all crashed unfortunately.
See https://github.com/musescore/MuseScore/pull/5205 for the patch that prevents the crash.
The .ove file discussed in this issue contains some "pedal down" marking but no corresponding "pedal up" one, I am not sure whether it is a correct situation for .ove files so it would be good if someone more familiar with .ove format could help with handling such cases.
In reply to See https://github.com… by dmitrio95
I'm no expert in music notation, but given that, as mattmcclinch pointed out, there were some measures having wrong number of beats in the file I uploaded, I think I can safely suppose that Overture does not check the validity of its data and would allow anything even totally wrong being put inside the file.
In other words, IMO, having incomplete pedal marks in .ove files might be "normal" situation, but it's certainly not correct according to musical notation standard.
That being said, MuseScore should not crash. I mean, MuseScore is able to deal with incomplete measures, it should be programmed to deal with all other anomalies. It would be nice for it to show a dialog to user telling him that some errors were found: what they are and why they are not imported.
If it's not possible to prevent it to crash, it would at least be nice if it can "dump a log file" before dying :)
Fixed in branch master, commit 82fd5a2b76
fix #276084: fix a crash on importing .ove file with no pedal end denoted
I merged a fix for a crash, but the suggestion on showing a dialog in case of such errors is reasonable indeed. I opened a separate issue for that: #292401: Show a dialog reporting errors spotted in .ove import.
In reply to I merged a fix for a crash,… by dmitrio95
😄👍
@dmitrio95 Fixed then since you opened a separate issue.
Hm, I probably changed a status by accident here.
Automatically closed -- issue fixed for 2 weeks with no activity.
I have tested ver 3.3.0 and 3.4.1 with MSI installer, and 3.3.4 from Microsoft Store, and I can confirm that MuseScore no longer crashes.
Thanks :)
As a result, this bug is resolved. Please close it.
It is closed since last September ;-)