LilyPond Beginnershandleiding

Hoofdstuk 4: Tweaking output 122
This necessarily uses an override for the accidental stencil which will not be covered until later.
The stencil type must be a procedure, here changed to print the contents of the text property
of Accidental, which itself is set to be a sesquisharp sign. This sign is then moved further away
from the note head by overriding right-padding.
The staff-padding property
staff-padding can be used to align objects such as dynamics along a baseline at a fixed height
above the staff, rather than at a height dependent on the position of the note to which they are
attached. It is not a property of DynamicText but of DynamicLineSpanner. This is because the
baseline should apply equally to all dynamics, including those created as extended spanners. So
this is the way to align the dynamic marks in the example taken from the previous section:
\dynamicUp
% Extend width by 1 unit
\override DynamicText.extra-spacing-width = #'(-0.5 . 0.5)
% Align dynamics to a base line 2 units above staff
\override DynamicLineSpanner.staff-padding = #2
a4\f b\mf c\mp b\p
f mf
mp
p
The self-alignment-X property
The following example shows how this can resolve the collision of a string fingering object with
a note’s stem by aligning the right edge with the reference point of the parent note:
\voiceOne
\once \override StringNumber.self-alignment-X = #RIGHT
2
2
The staff-position property
Multimeasure rests in one voice can collide with notes in another. Since these rests are typeset
centered between the bar lines, it would require significant effort for LilyPond to figure out
which other notes might collide with it, since all the current collision handling between notes
and between notes and rests is done only for notes and rests that occur at the same time. Here’s
an example of a collision of this type:
>
The best solution here is to move the multimeasure rest down, since the rest is in voice two.
The default in \voiceTwo (i.e. in the second voice of a construct) is that