program shutdown while editing a file imported through Audiveris
The following score causes a program shutdown when clicking on the first break in the second staff of the last measure. It had been imported trough Audiveris before.
| Attachment | Size |
|---|---|
| Dona_dona.mscz | 19.28 KB |
Comments
Lastest nightly from the master branch claims the score corrupt:
Measure 26, staff 2, voice 2 too long. Expected: 4/4; Found: 108/4
Stack trace:
1 Ms::Measure::mmRest measure.h 243 0xdce628
2 Ms::Timeline::drawSelection timeline.cpp 1755 0x4c6057
3 Ms::Timeline::drawGrid timeline.cpp 1006 0x4c1fb1
4 Ms::Timeline::updateGrid timeline.cpp 2200 0x4c95d2
5 Ms::MuseScore::endCmd musescore.cpp 4688 0x49d7c2
6 Ms::ScoreView::mousePressEventNormal events.cpp 304 0x41b1c5
7 Ms::ScoreView::mousePressEvent events.cpp 328 0x41b438
8 ZN7QWidget5eventEP6QEvent 0x207acf0d
9 ?? 0x2ab9f6c8
But that may not be relevant to where/how it crashes in 2.1.
Anyway, fixed score attached
In reply to Lastest nightly from the… by Jojo-Schmitz
Danke!
Ich hatte es vor allem auch hochgeladen, um das Fehlerhandling von MuseScore zu stabilisieren. Abstürzen sollte es ja in so einem Fall nicht.
Und vielleicht auch als Hinweis an die Kollegen des Audiveris-Teams: 108 Ticks in einem Takt...
In reply to Danke!… by Bacchushlg
Right, it shouldn't crash. The question also is whether the problem is in MuseScore's XML import or in Audiveris' XML export
In reply to Right, it shouldn't crash… by Jojo-Schmitz
By the way: do you collect problems concerning Audiveris also in this Forum? I detected a typical misbehaviour of this import for multi-staff scores: from a certain point in the score the first staff is almost correct while the following ones are imported with a certain offset (first note of next measure appears as last note of the actual one).
I could provide some examples of this that might be forwarded to the developer(s).
In reply to By the way: do you collect… by Bacchushlg
No, Audiveris has a site of its own
In reply to No, Audiveris has a site of… by Jojo-Schmitz
Again a similar problem with a different file (also from Audiveris import).
Here the breakdown happens when clicking on the bow at the end of measure 21 (to next line).
In reply to Again a similar problem with… by Bacchushlg
Assuming you imported a MusicXML file, could you attach the examples in the original MusicXMLformat ? That will allow me to investigate if the import is incorrect.
In reply to Assuming you imported a… by Leon Vinken
The import through Audiveris creates a mscz-file directly.
I mainly sent this file to allow Musescore be more robust and not to crash in case of "wrong" input files.
In reply to Assuming you imported a… by Leon Vinken
@Leon for your information, the online pdf convertor on musescore.com has the following pipeline: pdf > audiveris > musicxml > musescore > mscz. Only the mscz is offered for download, not the musicxml file.
In reply to @Leon for your information,… by Thomas
Which isn't helping to investigate a possible XML import problem... could you somehow intercept the XMLs for the files at hand in this thread?
In reply to Which isn't helping to… by Jojo-Schmitz
I just re-did the import of the file (I had done this originally some month ago - in February to be exact).
The imported file does no more have this problem - so it seems the Audiveris conversion has been corrected at this point. So it seems it is no use to search for the reason of this problem (on Audiveris side).
In reply to I just re-did the import of… by Bacchushlg
More likely the musescore backend had been fixed, when 2.1 got released ;-)
In reply to More likely the musescore… by Jojo-Schmitz
@Thomas, thanks for the explanation. As I really hate it when MuseScore MusicXML import causes crashes, I would have liked to see the MusicXML file, to find and remove the cause.