Glissando with anchor change via Shift+Down lost on save/reload

• Apr 10, 2019 - 19:41
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.5.5992, revision: 58dd23d

I write this:
Gliss01.PNG

and when I close the document and open it again, this appears:
Gliss02.PNG

Comments

• Apr 10, 2019 - 20:35

I can confirm it's possible to add the three glissandi and they are preserved if you use drag to change the anchors, but they disappear if you use Shift+arrow. So almost certain a duplicate indeed, and since an issue apparently filed for that one, this will do. We just need confirmation that Shift+Down was used rather than drag.

Looking at the MSCX files written in the two cases, I see all glisses are always written to the file but, the bad one has an extra "notes" tag within the "location" tag on the end note. I've never looked at this code so I don't have an idea offhand about what these are for, but it probably wouldn't be too hard to sort out.

Reply

• Apr 10, 2019 - 20:36
Title Three glissandos in a chord. Two disappear ⇒ Glissando with anchor change via Shift+Down lost on save/reload
Severity S4 - Minor ⇒ S3 - Major
Priority ⇒ P1 - High

Reply

• May 5, 2019 - 20:12

I've filed a similar issue in #288723 .
1. If it's amended with SHIFT + up/down, it disappears
2. If it's amended by dragging an anchor, it resets to default position.
In the attachement: the number 2 scenario.

Attachment Size
2gliss.PNG 8.48 KB

Reply

Fix version
3.2.0