C-Major/a-minor and atonal key signatures cause other elements, like dynamics, to move up
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
PR created
Regression
Yes
Workaround
No
Project
Look at the sample score, the dynanmics at the start of the system and the next one. The one at the start is higher.
Move it sideways a bit and it'd eventually jumps down.
In a debug build switch on skyline then and see a small peak:
Culprit is the keysig:
<Measure> <voice> <KeySig> <accidental>0</accidental> </KeySig> <Dynamic> <subtype>mp</subtype> <velocity>64</velocity> </Dynamic> ...
Remove those 3 lines and that jump is gone
Happens in 3.6.2, not in 3.5.2
Attachment | Size |
---|---|
dynamics placement.mscz | 4.52 KB |
Comments
Maybe not or only partially a regression, happens in 3.5.2 too, if setting the default distance of the dynamic to the same value, -1.5 rather then the 3.5.2 default of -3.
Somewhat related to #278907: First note of measure placed way too close to system header, if note is above staff, the same code that fixes it there for time sigs is used for key sigs too
See https://github.com/musescore/MuseScore/pull/7464 (3.x) and https://github.com/musescore/MuseScore/pull/7498 (master)
Fixed in branch master, commit b62e423326
Fix #317319: Remove unneeded skyline extension for time- and key signatures
awaiting the PR for 3.x to get merged too