Sperated a score into "Parts" and now the score crashes musescore everytime it is opened.
Title pretty much says it all, its a fairly big score. I'd like to get the score or musescore fixed in someway since the automatic backup is a step back for me.
Comments
Attach the file if you want.
Try to delete the Parts and generate them again.
Are you using 3.5.2? On which operating system?
In reply to Attach the file if you want… by Shoichi
Thats the thing, I can't even open the file w/o musescore crashing. OS is Windows and yes I'm using 3.5.2.
In reply to Thats the thing, I can't… by BRITANIC10
And...attach the score here?
In reply to And...attach the score here? by Shoichi
Here it is
In reply to Here it is by BRITANIC10
Indeed. 3.5.2 crashes on loading that score, in 3.5.2, and on Windows (7)
In reply to Indeed. 3.5.2 crashes on… by Jojo-Schmitz
Also in previous versions (3.4/2X)
In reply to Here it is by BRITANIC10
the latest development code in a debug build crashes on a failed assertion:
Fatal: ASSERT: "!_notes.empty()" in file ...\libmscore\chord.cpp, line 880
Stack trace at that point (rater: immediately before):
1 Ms::mscoreMessageHandler musescore.cpp 3947 0x42282d
2 qt_message_print(QtMsgType, QMessageLogContext const&, QString const&) 0x68892398
3 qt_message(QtMsgType, QMessageLogContext const&, const char *, char *) 0x68892499
4 QMessageLogger::fatal(const char *, ...) const 0x68c001a2
5 qt_assert(const char *, const char *, int) 0x68bffd67
6 Ms::Chord::computeUp chord.cpp 880 0x925195
7 Ms::Score::getNextMeasure layout.cpp 2927 0x9da120
8 Ms::Score::collectLinearSystem layoutlinear.cpp 177 0xbab932
9 Ms::Score::layoutLinear layoutlinear.cpp 192 0xbab9d0
10 Ms::Score::doLayoutRange layout.cpp 4868 0x9e6610
11 Ms::Score::update cmd.cpp 302 0x5313e0
12 Ms::Score::update score.h 754 0xeef82a
13 Ms::readScore file.cpp 2513 0x4c968d
14 Ms::MuseScore::readScore file.cpp 383 0x4b5f2c
15 Ms::MuseScore::openScore file.cpp 361 0x4b5dec
16 Ms::MuseScore::doLoadFiles file.cpp 338 0x4b5bfe
17 Ms::MuseScore::openFiles file.cpp 303 0x4b586c
18 Ms::MuseScore::cmd musescore.cpp 6275 0x43170a
19 Ms::MuseScore::cmd musescore.cpp 6069 0x430664
20 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 524 0x5e3c7e
...
Ther debugger tells me the issue seems to be with a chord containing no notes, in measure 163. that shouldn't be possible but somehow it happened. Were by by chance generating parts from voices? This feature should work well now, but it isn't that well tested.
In reply to Ther debugger tells me the… by Marc Sabatella
Yeah, I don't know the validity of that chord problem. When ever I open that score, weather through backup or before it completly corupted, it would give my a "your score is corupted" message and say that in four staffs out of 20 in some measure it said that it was 10/8 instead of 4/4 and I went and checked it (even in the "Measure properties") and it wasn't. But I did check 163 anyway and 9 chords, 3 are tied over from the previous measure, the other six are just normal chords played in eighths, and the other satffs just have rests.
I don't know if it was through voices or not. I just went into the tool and clicked "All Parts", it auto-generated them and I clicked "OK". After that the window disappeared and it sat for a few seconds like it was tryign to work on making the parts and then crashed
In reply to Yeah, I don't know the… by BRITANIC10
OK, thats not the voice feature then, you would have needed to mess with the rest of dialog for that (like to have two flute parts from one staff).
If you post your backup version, we might be able to tracked down where the error came from.
In reply to OK, thats not the voice… by Marc Sabatella
This is the only back I have of it. Although, I did redo the arranging on it with a different file and then made a copy of that file. After I made the copy file I decided to try to make a part again, not only did it corupt the main file that I was doing it on but it also corupted the copy that I made prior to trying the tool again.
In reply to This is the only back I have… by BRITANIC10
That one is corrupt:
Measure 71, Staff 14 incomplete. Expected: 4/4; Found: 10/8
Measure 71, Staff 15 incomplete. Expected: 4/4; Found: 10/8
Measure 71, Staff 16 incomplete. Expected: 4/4; Found: 10/8
Measure 71, Staff 17 incomplete. Expected: 4/4; Found: 10/8
In reply to This is the only back I have… by BRITANIC10
OK, I have a fixed version of your original score for you, attached. Somehow in measure 164 (the first 4/4 measure after the 3/4 at the start of Don't Let Me Down) something was off in the linked tab staff. You can actually see it being strange in the backup file too. Open it (rename it first if necessary to remove the trailing comma) and play with the last sixteenth in the top staff, you'll see that the two notes kind of merge into one on the tab staff.
I managed to open your original file - not the backup - in a debug version of MuseScore I created that won't crash immediately on that error, then I deleted those notes and resaved. The result opens just fine. You'll need to re-enter the notes.
If you can think of anything unusual about how that measure was created, that would help us understand how to prevent this from happening in the future. I'm guessing the title of the file is a clue there was some cut and paste involved near that point?