Slurs are not saved if connecting with rests, and leads to a crash
Nightly, October 23 (fc3ea8e) / Windows7
First reported here: http://musescore.org/en/node/37531
1. Open this file, from "My First Score"/Nightly:
test.mscz
(If opened by Beta1, no matter, I have checked, same result, the issue is previous to the Beta1.)
2. Add slurs on the first note (measure 1), and on the first notes (measure 2, on voices 1 and 2). Like this.
3. Save the score.
4. Reopen
Result: correct for the slur connected to an other note (measure 2, Voice 1)
But the slurs are lost if connected to a rest (measure 1), except in measure 3, where the start of the slur of the Voice 2 (connected to a rest) remained in place.
That may be edited.
Attachment | Size |
---|---|
test.mscz | 1.64 KB |
test1.jpg | 17.74 KB |
result.jpg | 15.65 KB |
edited.jpg | 18.96 KB |
Comments
This issue is occured in July, between:
- July 3 (Nightly, e9e0e34, correct)
- and this one (July 8), incorrect: https://github.com/musescore/MuseScore/commit/f97c0a451b
So, related to the fix of this issue: #27321: Crash when you press the S key on the last selected note
See also the section "What links here" (in the same issue report).
So maybe also with this other fix (?):
https://github.com/musescore/MuseScore/commit/c0618b13bdc749a520dc85e96…
1. Open this file: test slur voice2.mscz -> Add a slur on the B (half note, voice 2)
2. Copy-paste the measure 2 (staff1) in the measure 2 (staff 2) : result : you see the slur crossing the staff
3. "I" -> Select staff 2 -> Add linked staff (same staff type always) -> Ok
Result: crash
Additionnal note: if, at the step #2, you copy-paste the measure 2 (staff 1) in an other measure of the staff 2 (first, third, fourth), the slur is definitively lost.
Consequently, add a linked staff do not lead to this crash.
Definitively lost? You notice, in this case (copy-paste in a measure, except measure 2), that adding a linked staff allows the return to the slur in the staff 3!
If you return to "I", you see that the staff 3 is now linked to staff1. Why?
Fixed in e5a34fefbe
Automatically closed -- issue fixed for 2 weeks with no activity.