Dynamics placement above/below not remembered after importing MuseScore 2 file

• Dec 25, 2018 - 09:28
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

When importing a MuseScore 2 score with all of the dynamics in a given staff above the staff, MuseScore 3 (correctly) automatically sets their position to "Above", but doesn't remember this when saving the file.

Attachment Size
Test 3.0.mscz 8.35 KB
Test 2.3.2.mscz 8.24 KB
Screenshot 2018-12-25 at 5.23.39 PM.png 50.39 KB

Comments

• Dec 25, 2018 - 10:10

Sure 3.0 converts the 2.x offset to above staff into the position "Above"? I rather suspect it at first takes that offset, and on save "forgets" that or falls back to auto place.

Reply

• Dec 25, 2018 - 10:54

OK, I can confirm. It is very strange though, as in 2.x there is no property abobe/below, so I don't see why it would import it that way.
Also strange that this behavoir is independant of whether you use the reset position to defaults or not

Reply

• Dec 25, 2018 - 19:30
Priority ⇒ P1 - High

It imports that way because there is code to detect which elements are above versus below the staff based on their offsets and then assign placement appropriately. If it isn't saved, that usually means we forgot to set the property to unstyled after setting the value (and when I say "we", I mean "I", since at least some of this code is mine).

Reply

Fix version
3.0.1