Lyrics don't overlap stave elements

• Sep 14, 2013 - 07:42
Reported version
3.0
Type
Functional
Severity
S4 - Minor
Status
closed
Project

1. Open attached score (produced in 1.3).

Desired result: The lyric of the first note spreads to the beginning of the system.

Lyric of first note doesn't spread to the beginning of system (Desired result).png

Actual result: The lyric of the first note does not enter the area of clefs, key and time signatures.

Lyric of first note doesn't spread to the beginning of system (Actual result).png

Note: The expected result was produced using LilyPond 2.16.1.

Using MuseScore 2.0 Nightly Build (6d72a89) - Mac 10.7.5.


Comments

Title Lyric of first note doesn't spread to the beginning of system Lyrics don't overlap stave elements

Yes, it's not limited to the first note.

It should spread into the area of nearby rests and other elements, including clefs, key and time signatures.

Status (old) fixed active

No, I did not implement this particular optimization, because there would be no way to automatically prevent overlap. The original example will still produce the layout shown as "actual".

Status (old) fixed needs info

I doubt this was the Chen Lung's intention:

Screen Shot 2016-08-29 at 11.49.38 AM.png

This fix has good results for the initial system, but not on subsequent systems.

Interesting, it seems it is the presence of a time signature that causes the margin to be obeyed for the first system but not for others. Try adding a time signature to any subseuent system and the marign is then respected. A key signature has the same effect.

Actually, FWIW, I do wonder about what the desired behavior would be here. Currently for systems other than the first, if you don't want the lyric to extend into the margin, you can manually adjust it. But for the first system, if you *do* want it to extend into the margin, there is no way to make that happen. Moving the lyric to the left just moves it relative to the note it is attached to, moving the note to the right to keep the lyric out of the margin.

In the end, it's probably not a hugely important question as it would probably be relatively uncommon (which is why this subject almost never comes up).

Perhaps a bigger issue: the I don't remember how it was before this change, but currently, a very long syllable at the beginning of a measure will collide with a syllable in a previous measure:

lyric overlap.png

It's the same problem we have with chord symbols (in 2.0.3 as well as current master) - the automatic spacing works *within* a measure only, not *between* measure.

I believe negative and positive leading space for the segment are manual adjustments that solve each problem, respectively. I've opened up some piano/vocal scores with this fix and they look a lot better out of the box than 2.0 because it is less likely that long syllables respace notes, particularly at the beginning of a measure (in 2.0, this was almost guaranteed to happen if a syllable immediately after a barline had more than three letters in it).

Also, it's worth mentioning is that a long syllable under beamed quaver (etc...) overlap with next syllable:

(lyrics: Al- lelele- - lu- ja)
strech.png

Windows 7-64, ea88600

As I understand, the initial topic is about lyrics overlapping the space under the clef and key signatures. Overlapping syllables is due to the separate (already existed) issue.
Marc stated "I did not implement this particular optimization, because there would be no way to automatically prevent overlap."

True I was unable to implement a proper fix for this due to the limitations of our older layout algorithm. But presumably it would be possible now, and I agree it should be addressed, so I wouldn't call it by design.