Slurs have lost their custom positions

• Dec 5, 2018 - 12:13
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
MuseScore

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4191, revision: d9ccbb1

Open the attached score (created in 2.x), once with a reset and once without a reset.

Expected result: The custom positions of the slurs in measures 2 and 4 should be retained in both cases.
Actual result: The custom positions of the slurs in measures 2 and 4 are lost, and there is a collision with the staccatto dots in measure 2.

Attachment Size
slur_positions_lost.mscz 10.48 KB

Comments

• Dec 5, 2018 - 14:18
Priority ⇒ P1 - High

I can see hoping for them to be retained if you don't choose reset, not sure why you'd expect that if you do.

I suspect slur layout code has changed too much to make it viable to reproduce 2.x appearance, but definitely something to investigate further.

Reply

• Dec 7, 2018 - 03:47
Priority P0 - Critical ⇒ P1 - High
Workaround No ⇒ Yes

My call - with reset, of course custom positions are lost. Would be better if slurs avoid staccato in these situations, no doubt.

Without reset, they are kept, but since defaults differ (2.x slurs crossed the stems, 3.0 don't), it's not reasonable to expect the same manual adjustments to produce the same results.

There is room for improvement on both counts, but not I think "critical" in the sense we are using.

Reply