Split Staff on particular slur crashes MuseScore

• Mar 25, 2015 - 12:54
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

See http://musescore.org/en/node/52261#comment-244836 ff.

  1. open either of the attached scores in 2.0
  2. right-click into a staff -> split staff -> OK

expected result: staff gets split into 2 staves
actual result: crash

Reproduced with MuseScore 2.0 on Windows 7 (Enterprise, 64bit)

In 1.3 the split operation works as expected (using the -1.3 version of the attachments

Attachment Size
S85 - 1. Die launige Forelle-1.3.mscz 5.62 KB
S85 - 1. Die launige Forelle-2.0.mscz 53.87 KB

Comments

• Mar 25, 2015 - 13:15

The crash occurs while trying to lay out a slur, and it is attached to a chord with no notes. I guess when moving notes from one staff to the other, the slurs were not properly updated. Crash goes away if you first delete the slurs. But I'm not sure what's so special about the slurs in this score that cause the problem, as other scores with slurs seems to split fine. Maybe something about the specific arrangement of voices.

Reply

• Apr 9, 2015 - 13:06
Title Split Staff on a score imported from 1.3 crashes in 2.0 ⇒ Split Staff on particular slur crashes MuseScore

It's not linked to a 1.3 score I think.
Enter the following in My First Score and split the staff on C3. It will cause a crash.

Capture d'écran 2015-04-09 13.59.58.png

Reply

• Apr 10, 2015 - 10:30

From what I can see in the time, this issue occurs on last July 28 (with two steps)

- Between May 19 and July 3, I receive this (with a flute score). You notice that the slur is preserved in the first staff:
slur preserved.jpg

- On July 5, I receive a crash, maybe in reason of these commits ?
https://github.com/musescore/MuseScore/commit/3816d17e056b464cfeb056211…
and https://github.com/musescore/MuseScore/commit/abdf9f105fd53110dbcaad477…

From July 8, with this commit probably? : https://github.com/musescore/MuseScore/commit/f97c0a451b67462c5405dc0e6…,
the crash is fixed, and I get (so: without slur)
Split July 27.jpg

The behavior remains the same until July 28. With this Nightly: 43b8b02, I get the same result as the second image.

With this one: 40f14cd, I receive a new crash (the current result)
crash July 28on 40f14cd.jpg

I watched different commits on this day. For now, nothing obvious.
Some proposals without really know :(
- the same mentionned commit/Nightly? : https://github.com/musescore/MuseScore/commit/40f14cdceed34a51da565eac2…
- or ? https://github.com/musescore/MuseScore/commit/d6fcb0e4f67c51f87599b286d…
- or ? https://github.com/musescore/MuseScore/commit/cca02516063a03d8254bb7dfb…
- or ? https://github.com/musescore/MuseScore/commit/ae475eb0fd8cdc787cd2858ee…

Furthermore, I saw this conversation: https://github.com/musescore/MuseScore/pull/1933
Please, don't delete the pending slur (slur ending on a rest). It's a very useful feature (I agree with the commentary from Marc, in particular for: "L.V." / "let ring" indication for stringed instruments) . See this thread: https://musescore.org/en/node/37531
And the fix: https://github.com/musescore/musescore/commit/fd82ab6

Thanks.

Reply

• Apr 10, 2015 - 10:36

I already saw of course this PR. Thanks. But I don't know, with this PR, if the slur ending on a rest is preserved, as wished, or not?

Reply