Crash when a staff containing hyphens is unticked "Visible" in a score with multimeasure rests

• Nov 17, 2016 - 19:39
Reported version
2.1
Type
Functional
Severity
S5 - Suggestion
Status
closed
Project

Trying to print PDFs of parts for musicians but when I show just the drum part muse score closes Go_The_Distance D.mscz . Any ideas?


Comments

Are you trying to view parts by manually marking each staff visible or not as needed? Don't do that -it's way more more work and won't quite produce the correct results. Instread, use the built in parts facility - see File / Parts.

Anyhow, I can confirm a crash with this file if you do try to do what I guess you must be doing:

1) Edit / Instruments
2) Check "Visible" for drums and uncheck it for piano
3) OK

But the standard File / Parts facility works fine.

Thanks for the reply, that is how I've been doing it yeah! Never knew about the parts thing, I've opened it up but don't seem to be able to click anything. I've attached a pic... Screen Shot 2016-11-17 at 21.17.33.png

Click "New All" which will create new parts, one for each instrument. Then OK. You'll then see tabs for each part, and these save as part of your score and automatically update if you make changes to the score (and vice versa). See the Handbook under "Part extraction" for more information on how parts work.

Meanwhile, though, we do need to investigate the crash.

Title Musescore crashes when I show only the drum part Crash when a staff containing hyphens is unticked "Visible" in a score with multimeasure rests

To reproduce from scratch:

Steps (or load this test file: Flute Clarinet.mscz avanced just before the last step #4)

1) Create a new score for two instruments, eg for Flute and Bb Clarinet (2 measures is enough)

2) Add notes and lyrics in the flute staff, necessarly containing an hyphen

3) In Style -> General -> Tick "Create multimeasure rests"

4) "I" -> Untick "Visible" the Flute staff -> Ok

Result: crash
crash flute clarinette.jpg

. Reverse case: Flute Clarinet Reverse.mscz : untick "Visible" the Clarinet staff -> Crash:

- Notes:

1) No crash by deleting the first syllable with the hyphen (ie: ly-)

2) No crash if "Create multimeasure rests" is unticked (ie, in the presence of the lyrics and hyphen)

- Last note: exactly by the same way, there is no crash in the "original" file, after remove all lyrics with hyphens (around a dozen here) - or after untick Create multimeasure rests" -, and with the steps described in comment #1 (to sum: Check "Visible" for drums and uncheck it for piano): Go_The_Distance D, without hyphens.mscz

You have noticed this issue doesnt' occurs with the 3.0 under development and current nightlies eg 6a0fb3f. Ie with the final step: "I" -> Tick "Visible" drumset staff, and untick "Visible" Piano staff.
But there is another issue with these "Visible" staffs.

I guess you mean #141441: Untick "Visible" for all the staves/instruments causes a crash

The score from #1 is corrupt, measure 50, staff 5, some odd tuplet. For some stragne reason 2.0.3 doesn't detect that corruption, but 6a0fb3f does?

But no crash in 6a0fb3f. Would need to check whether it crashes in 2.0.4, unfortunatly there are no noghly builds available for it.
It does crash though it you make all staves invisible, but that's being worked at in the above mentioned issue

I note that in the master branch, the issue no longer appears on last 3 June.

More precisely, between mid-April and 3 June and this nightly: a41b109 the hyphen is not displayed, therefore, no possible crash.

With this nightly: c1726bb, the hyphen reappears, and the crash is fixed. So, somewhere surely between these two nightlies / commits mentioned.

- BUT , by continuing some tests, I observe a related crash until October 24th, with this test file and following steps: Flute Clarinet.mscz

1) Load the test file
2) "I" -> untick "Visible" for flute -> Ok
3) Undo
4) "I" -> now untick "Visible" for Bb clarinet -> Ok

Result: crash

I notice this specific crash is fixed with this nightly on October 25: f7d9650 (this one fails: ffb45f3)

- So, I don't know if the 2.0.4 includes this fix?