Bug: Newest Nightly Build Mis-aligns Lyrics

• May 17, 2019 - 19:27
Reported version
3.x-dev
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

The newest nightly build consistency mis-aligns lyric text in scores created with Beta 3.1. For some reason, the Nightly Build changes the offsets even when they are zero. When I reset all the offsets to zero in the Beta 3.1, the lyrics in the Nightly build were less skewed. However, the original unaltered score demonstrates a significant bug where zero offsets are given a value in the Nightly Build.

To duplicate, compare score in Beta 3.1 and Nightly Build.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.6864, revision: a18d446

See the original post, for screenshots and score.
https://musescore.org/en/node/289294

Comments

• May 17, 2019 - 22:07

Thanks for reporting! There are a couple of things going on, one is an easy fix (although took a while to track down), the other more complicated. It has to do with the fact you have for some reason turned off the "follow staff size" option for all of these lyrics, which is throwing off the calculations of the distance to get above the staff. Is there a reason you've done that (turned off that option) rather than choose a larger font if you want small staff size?

You also have a negative minimum top distance in your lyrics style, which combined with the follow staff size, really means 3.0.5 is displaying this incorrectly - that negative value is being ignored. The changes in 3.1 are now allowing it. But I may end up disabling negative lyrics top/bottom distances just for the sake of compatibility.

Reply

• May 17, 2019 - 23:38
Status active ⇒ PR created

Actually, never mind, the code does handle those things. The easy fix will be good for scores created in 3.0, and almost everything you might have done in earlier 3.1 builds. The one thing that will fail are the autoplaced syllables you actually tried to apply an offset to using an earlier 3.1 build, which didn't succeed but you didn't realize it, and now those offsets will be honored. A quick fix for those cases would be to re-save the score in 3.0.5 before importing into 3.1. Or just reset those syllables. Again, only an issue for autoplaced syllables you tried to set a manual offset on, only when saved in earlier pre-released 3.1 builds.

Reply