Crash while opening Capella capx file

• Sep 27, 2020 - 14:16
Reported version
3.5
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
MuseScore

Try to open file

Attachment Size
Scan_0012.capx 20.35 KB

Comments

• Sep 27, 2020 - 15:18
Frequency Many ⇒ Once

A Debug build crashes with a failed assertion:
Fatal: ASSERT: "!_notes.empty()" in file ...MuseScore\libmscore\chord.cpp, line 880
or
Fatal: ASSERT: "!_notes.empty()" in file ...\MuseScore\libmscore\chord.cpp, line 71
or with this stack trace:
1 Ms::Chord::upNote chord.cpp 73 0x8cf44b
2 Ms::Chord::computeUp chord.cpp 921 0x8d2ca1
3 Ms::Score::getNextMeasure layout.cpp 2734 0x984757
4 Ms::Score::collectSystem layout.cpp 3662 0x989e8d
5 Ms::LayoutContext::collectPage layout.cpp 4461 0x98f644
6 Ms::LayoutContext::layout layout.cpp 4774 0x9912cc
7 Ms::Score::doLayoutRange layout.cpp 4762 0x99122f
8 Ms::Score::update cmd.cpp 302 0xac0e96
9 Ms::Score::update score.h 749 0xebe7fa
10 Ms::readScore file.cpp 2499 0x4c5ac2
11 Ms::MuseScore::readScore file.cpp 383 0x4b263e
12 Ms::MuseScore::openScore file.cpp 361 0x4b24fe
13 Ms::MuseScore::doLoadFiles file.cpp 338 0x4b2310
14 Ms::MuseScore::openFiles file.cpp 303 0x4b1f7e
15 Ms::MuseScore::cmd musescore.cpp 6267 0x43058e
16 Ms::MuseScore::cmd musescore.cpp 6058 0x42f49b
17 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 523 0x5a340c
18 QMetaObject::activate(QObject *, int, int, void * *) 0x68a947c8
19 QActionGroup::hovered(QAction *) 0x2ad94db2
20 QActionGroup::qt_static_metacall(QObject *, QMetaObject::Call, int, void * *) 0x2ad9573c
...

I guess this relates to how Capella does the equivalent to MuseScore's "Hide empty staves", or rather how MuseScore deals with that on importing a Capella score

Reply

• Sep 27, 2020 - 19:53

It apparently is a SATB + Piano score, with the Piano starting while SATB are not shown, so that score uses Capella's variant of "Hide empty staves".

Reply

• Sep 27, 2020 - 21:56

Thanks for the reply! I never had this problem before recently. Is there a way to ignore that in MuseScore or fix this somehow, or do I need to add the empty scores to the Capella file?

Reply

• Sep 27, 2020 - 22:10

You could try to show all staves in Capella and then import the result in MuseScore.
Better still though would to use MusicXML to export from Capella and import to MuseScore

Reply

• Sep 28, 2020 - 17:46
Status active ⇒ fixed

Thank you so much. That worked just fine saving the Capella file in XML format. I'm not sure why this started happening, maybe the latest update to MuseScore. Anyway, it is fixed. Thanks again for your help!

Reply

• Sep 28, 2020 - 17:56
Status fixed ⇒ active
Workaround No ⇒ Yes

Well, this is good for you, still MuseScore shouldn't crash on that capx file, not everyone has the luxury to have a full Capella version to open a capx and export to MusicXML

Reply