Request to adjust lyrics top/bottom margins for compatibility on import
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.1.4922, revision: 598057d
Open the attached file (created in 2.x). Take the reset. Decrease layout stretch of measures 6-10 to bring them onto the same system. Notice the extra large gaps between the lower lyrics lines and the staff beneath in systems 2 and 3. These were not there in 2.x.
A similar issue, #280428: Too much space allocated around tab staff with"beamed" notes?
| Attachment | Size |
|---|---|
| piano_song.mscz | 31.78 KB |
Comments
Change Format > Style... > Lyrics > Min. bottom marging from 3.0sp to its default of 2.0sp or even lower.
Debatable whether this is by design or should get autocorrected on import, so I'll leave it open for the time being
Certainly not a bug though, at most a feature request
I should have added that the issue is present even if you don't reset the score. Does this suggest it's a bug?
No. It takes the style values from 2.x, reset via that dialog only works on shapes and positions. That much is by design.
The lyrics marign is simply being treated different betwene MuseScore 2 & 3. Previously it set the margin from the bottom of the lyric to the top of the next staff, now it sets the distance to the skyline. So previously you had to kind of guesstimate what sort of lyric margin would give you the result you actually wanted, and often it wasn't really possible to get the deal spacing without resorting to spacers, because depending on what was on the next staff, the actual spacing below the lyrics would differ from system to system. Now, this margin setting means what it really should have meant all along - the actual amount of extra space below lyrics, independent of anything else.
There probably isn't a straightforward way to get the MuseScore 3 layout algorithms to behave the way MuseScore 2 did. But probably we can come up with some sort hack to just reduce the margin from what was specified in the original file, with the idea being to be both closer to the original layout but also better in the ways the new algorithm now allows.
What reasons could have changing those values in 2.x have had, other than to avoid collisions? It that is the sole purpose (or at least covers the vast majority of cases), I guess we could just drop them on import and reset to the 3.x defaults?
I don't do enough vocal scores to really say, but yeah, I do suspect most people did indeed use this setting as a hack in that way and just going with the defaults may indeed make more sense. We could also consider a lower default, FWIW, even for new scores.
I do almost exclusively vocal scores, and for me this certainly is the case. And yes, 1sp for upper and also lower border makes sense to me. but I can live with the current defaults
OK, unless someone has other ideas, I'm planning to submit a PR that basically ignores top/bottom margin settings made in 2.x in favor of the 3.0 defaults. At least, for cases where the user is creating a larger than default margin. Smaller margins seem worth preserving.
https://github.com/musescore/MuseScore/pull/4689
I didn't actually preserve smaller margins after all, there is just no way to do it meaningfully.
Fixed in branch master, commit 0c42d579e1
fix #281414: import of lyrics spacing settings
Automatically closed -- issue fixed for 2 weeks with no activity.