Problem with Album/Joining Scores

• Apr 11, 2016 - 01:45

MuseScore 2.03, Windows 10 PC
First things first: MuseScore 2.03 is great!

I recently finished entering Schumann's Dichterliebe song cycle into MuseScore (as 16 individual scores), and I thought it would be a good opportunity to learn how to "Join Scores" under the Album Manager feature. However, it's kicking my butt. Maybe operator error, or maybe there's a bug.
All the songs are for piano & voice. There are minor differences in the style settings, but all have the same spatium size.
There are 16 songs in the cycle; I've only attached the first 8 for convenience (plus the "joined" first six songs as "Test 2".
Short version- With difficulty, I'm only able to get the first 6 songs joined. No success getting the 7th added. MuseScore crashes.
Long version (FYI I've done many, many, variations on the below, but all end with the same result: MuseScore crashes, unable to get more than 6 songs joined.)

1. Open MuseScore, no scores are open.
2. File>Album; click New>change name from Untitled to Test 1. Do not Join Scores or Close yet.
3. Add Score> select Dichterliebe 1 & 2.
4. Join Scores> keep name of Test 1>save to desired folder> Test 1 mscz is created. Good so far.
5. Add Score> select Dichterliebe 3.
6. Join Scores> Keep same name, save to same folder, accept "Test 1 already exists, replace?">Yes.
7. Add Score> select Dichterliebe 4.
8. Join Scores> Keep same name, save to same folder, accept "Test 1 already exists, replace?">Yes.
9. Popup message appears: X Runtime Error! Program (musescore.exe) This application has requested the Runtime to terminate it in an unusual way.
10. Acknowledge the message, new popup message: MuseScore.exe has stopped working.
11. Restart MS>new popup message: The previous session quit unexpectedly. Restore?>Yes.
12. Open Test 1 in MuseScore, despite the crash, all 4 songs are in the joined score. Note that, since the Album Manager was never closed prior to the crash, the album "Test 1" was not created.
13. Close the Test 1 score.
14. File>Album; click New> create new album "Test 2".
15. Add Score> select Test 1.mscz.
16. Close the album manager and save Test 2 to the desired folder.
17. File>Album>the Album Manager opens with the Test 2 album already selected. (This is unexpected; Album Manager should have opened with no albums showing.)
18. Add Score> select Dichterliebe 5>Join Scores> save with same name to same folder, accept "Test 2 already exists, replace?">Yes.
19. Add Score> select Dichterliebe 6>Join Scores> save with same name to same folder, accept "Test 2 already exists, replace?">Yes.
20. Popup message identical step 9 above appears. MuseScore crashes.
21. Restart MuseScore, open Test 2.mscz, on review all 6 songs are in the joined score.
22. Close the score Test 2.
23. File>Album>the Album Manager opens with the Test 2 album already selected. (This is unexpected; Album Manager should have opened with no albums showing.)
24. Repeat the exact steps above & attempt to join Dichterliebe 7 to Test 2 (which has songs 1-6).Join Scores> save with same name to same folder, accept "Test 2 already exists, replace?">Yes.
25. NEW popup message appears: "MuseScore has stopped working".
26. All further attempts to join 7 to the first 6 in Test 2 cause MuseScore to crash with the error message of step 25.

For what it's worth, on my very first attempt to join the scores, I selected all 8 at the very beginning of the Join Scores process. MuseScore crashed (sorry, I didn't document those steps; wasn't expecting a crash and assumed operator error). So I tried again using only a few scores at a time, and had somewhat better luck, but still not getting the desired result. I've reviewed the on-line Handbook section on albums & joining, however it's very sparse and was not much help.

Thanks in advance for the help.


Comments

The problem is due to the 7th score having an initial clef before first chord... I managed to join via album by first deleting that first bass clef from the top piano part of 7th score, and works (attached).

I had wrote code to handle the case for initial clefs when they are at the beginning of a staff (i.e. before the measure). However I might have overlooked the case where the initial clef is at the beginning of the measure before the first chord/rest...

Attachment Size
schumann1to8-withoutinitialclef7.mscz 69.64 KB

Wait, actually I'm able to join a score that has an clef before first chord-rest of first measure.

What I'm realizing now is that your score #7 has a very strange beginning. You have an initial clef for 1st staff and 3rd staff, but no initial clef for 2nd staff. The 2nd staff first measure does have a clef before first note. But I'm wondering how you were able to get that 2nd-staff setup without an initical clef in the first place:

score7_why-no-initial-clef.png

Did you do anything in particular to remove that initial clef. (My understanding is that there should always be an initial clef for all staves...even if there is another clef before the first chordrest in the first measure.

In reply to by ericfontainejazz

aha...I've discovered that I put before first chord-rest of a meausre:
start-with-two-clefs.png
Then I can remove that initial clef:
then-can-delete-initial-clef.png
Interestingly I'm only able to remove that initial clef if it has another clef immediately after in first segment of first measure...

My album initial-clef joining code did not account for this peculiar situation...

In reply to by marty strasinger

I think you might have stumbled upon two different types of crashes. The crash I wrote about above had to do joining a score that doesn't have an initial clef. But I can get other crashes just with the just the Album interface...here is one particular sequence of steps:

  1. New
  2. Add
  3. select score 1, 2, & 3
  4. join scores (successfully)
  5. then remove score 2 from list

Result: CRASH

In reply to by ericfontainejazz

It seems that this crash upon removing score 2 from list occurs during the score delete stage...here is call stack:

1	??			0x18	
2	Ms::TBox::~TBox	textframe.cpp	45	0x13041e7	
3	Ms::TBox::~TBox	textframe.cpp	46	0x1304222	
4	Ms::Score::~Score	score.cpp	419	0x1269143	
5	Ms::Score::~Score	score.cpp	437	0x12697d0	
6	Ms::AlbumItem::~AlbumItem	album.cpp	38	0xdbf1e0	
7	Ms::Album::remove	album.cpp	365	0xdc106d	
8	Ms::AlbumManager::removeClicked	albummanager.cpp	190	0xdc3040	
9	Ms::AlbumManager::qt_static_metacall	moc_albummanager.cpp	116	0x101128c	
10	QMetaObject::activate(QObject *, int, int, void * *)			0x7fffef484870	
11	QAbstractButton::clicked(bool)			0x7ffff05082f2	
12	??			0x7ffff0276484	
13	??			0x7ffff0277937	
14	QAbstractButton::mouseReleaseEvent(QMouseEvent *)			0x7ffff0277ab4	
15	QWidget::event(QEvent *)			0x7ffff01c0a58	
16	QApplicationPrivate::notify_helper(QObject *, QEvent *)			0x7ffff017c68c	
17	QApplication::notify(QObject *, QEvent *)			0x7ffff0182071	
18	QCoreApplication::notifyInternal2(QObject *, QEvent *)			0x7fffef458518	
19	QApplicationPrivate::sendMouseEvent(QWidget *, QMouseEvent *, QWidget *, QWidget *, QWidget * *, QPointer&, bool)			0x7ffff0180e45	
20	??			0x7ffff01da919	
...	

That probably doesn't mean anything to you...I'm just pasting here for others devs to look at. But basically it is trying to delete a TextBox element which has no actuall text in it. If you notice that score has a text box below title which has no text. If it save a copy of score 2 that doesn't include that empty text box, then I'm able to perform the above sequence of steps successfully. Completely seperate bug. Let me file this...

Thanks for discovering these. Album is relatively new feature, and hasn't had as many people using it to catch all corner cases.

In reply to by marty strasinger

Marty, I'm looking at that empty text box you have just below the title text box in score 2. I'm noticing if I double click it, then I don't see a cursor appear, and if it try typing some text, I don't see anything appear. I'm very confused... That text box seems broken, since I should always be able to type text inside of it. Do you remember the steps you took when creating that text box?

EDIT: I just realize you had set that text to invisible inside that text box. But I'm still getting a crash when deleting that text box...

In reply to by marty strasinger

Humm... I didn't *deliberately* remove the initial treble clef from the first system of the piano right hand part in 7 Ich grolle nicht, not sure how that happened. It wasn't intended, and the source document uses normal clef conventions.
Re: the not-visible text box below the title- that's where I put my standard caveats. For the album/joined score, it will be appropriate to only have it on the first score.
I'll have a go at joining the sons with these changes made & report back...

OK, here's a problem- it looks like 7 Ich grolle nicht is somehow corrupted.
1. Open the score, it presents with with no initial treble clef showing in the first system of the piano right hand.
2. Delete the bass clef in the piano right hand that's just before the very first note. This causes the treble clef to appear where it should, at the beginning of the system.
3. Save the score & close.
4. Re-open the score: back to square one; initial conditions the same as Step 1.
5. Re-open the score, completely delete the affected measure & re-enter it from scratch. Looks good...
6. Save, close & re-open the score, initial conditions the same as Step 1, no initial treble clef showing in the first system of the piano right hand.
Any ideas on how to correct it?
Is this a separate issue that should be entered separately?

Update: I had to recreate 7 Ich grolle nicht from scratch to remove the problem.
There may be a bug of some sort in *all* the Dichterliebe scores, but it's only presenting in the case of #7, due to putting the bass cleff at the very first note.
>> I initially recreated 7 "from scratch" using 1 Im wunderschonen Monat Mai as a template, and the problem re-appeared.
>> When started from scratch again using the MuseScore template for piano+voice, the problem is corrected.
>> Perhaps my initial issues with joining the scores are related to this same issue, that doesn't give any cues to it being there until you put the bass clef in front of the first note?

In reply to by marty strasinger

After step 3, when reopen, I actually see the corrected score open, where there is an initial treble clef in staff 2. I'm on 2.0.3, tried both on Arch Linux and Windows 8.1, so I don't know why you aren't getting the corrected version on reopen. Are you sure the score is indeeded being saved and that you are opening the score you saved?

In reply to by marty strasinger

I'm somehow having trouble replicating the error that you got at point 4. If you could try to produce the minimal steps required that produce that error, it would be helpful for me...not much I can really do right now without being able to reproduce it. I'm wondering if maybe there is something unusual about your preferences or other setup that is causing that to happen on your machine and not mine.

In reply to by ericfontainejazz

Re-checked & confirmed the problem is as described above. Details-
1. Open an archive version of the score that still has the cleffing problem. Save it as "7 Ich grolle nicht Confirm clef issue". (See attached.)
2. Confirm initial conditions: Missing G clef from beginning of 1st score of piano right hand. F clef is present just before the first note of piano right hand.
3. Delete the F clef just before the first note. The G clef instantly appears where it's supposed to be.
4. Save.
5. Insert new F clef in the right hand, just before the 1st note. No problem, & the G clef stays where it should at the beginning of the 1st system.
6. Save.
7. Close score.
8. Open score. Confirm problem is still there: Missing G clef from beginning of 1st score of piano right hand. F clef is present just before the first note of piano right hand.

Additional comment: earlier today, as a test using song 1 Im wunderschonen (which song 7 used as a template) I did the same change (F clef before first note in piano right hand) and observed the same problem. I did it again just now, and the problem did *not* appear upon saving & re-opening. Maybe operator error, but I'm trying to be very diligent in tracking this, so it seems unlikely.

In reply to by ericfontainejazz

OK marty, I've managed to reproduce the odd state of initial clefs of score #7, using these instructions: https://musescore.org/en/node/105721#comment-476436

The trick is changing the initial clef of staff 1 from a "generated" clef into a real clef (by dragging and dropping another clef ontop of the first measure. That produces a situation that when saved will not migrate the non-initial bass clef into an initial bass clef during save&reload.

In reply to by ericfontainejazz

The problem seems to be fixed!
Based on your comments, I went to a "bad" 7 Ich grolle nicht.
1. Open score, confirm the problem exists.
2. Delete the F clef before the first note, and a "new" G clef at the beginning of the system instantly appears.
3. From the Clef palette menu, drag another new G clef on top of the existing/new clef.
4. Save, Close, Re-open, problem is gone, all clefs are as they should be.

Continuing:
Applied the correction to all 16 scores in the song cycle (dropping a new G clef on top of the existing G clef in the piano right hand, on the assumption the problem is present in them all but only presenting on 7).
Easily created a complete Dichterliebe album & merged score with no problems.

Thanks very much!

Do you still have an unanswered question? Please log in first to post your question.