David Nalesnik wrote Sunday, November 02, 2014 1:08 PM > Yes, I would say it's definitely a bug. This is a bit of misuse of > self-alignment-X, but the same happens with this line: > > \once \override DynamicText.self-alignment-X = #5 > > So, possibly it's a problem with the Dynamics context?
After a little more experimentation, it turns out it's the way the Dynamics context works. I'm guessing from experimenting, rather than reading code, but it seems just the notes above and below all the dynamics in a system are selected and a line is centered between the lowest of the notes above a dynamic mark and the highest of the notes below a dynamic mark. All the dynamics are then placed along this line and the distance between the staves is adjusted so there is (just) no overlap. Notes without dynamics are permitted to 'poke through' the dynamics line. This rather clumsy example illustrates it. \new PianoStaff << \new Staff { e' d, d e' e' d e' e' } \new Dynamics { s\f s s s\p s s\f s s } \new Staff { a'' a'' a'' e''' a'''' a'' e''' a'' } >> So if a dynamics mark is moved far enough horizontally so 'its' notes are no longer considered we get the effect observed. After all this I found issues 1127 and 3299! Should have looked first. Trevor _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user