1 @c -*- coding: utf-8; mode: texinfo; -*-
2 @node Changing defaults
3 @chapter Changing defaults
6 The purpose of LilyPond's design is to provide the finest output
7 quality as a default. Nevertheless, it may happen that you need to
8 change this default layout. The layout is controlled through a large
9 number of proverbial ``knobs and switches.'' This chapter does not
10 list each and every knob. Rather, it outlines what groups of controls
11 are available and explains how to lookup which knob to use for a
15 @cindex Program reference
17 The controls available for tuning are described in a separate
23 @ref{Top,Program reference,,lilypond-internals}.
26 lists all different variables, functions and options available in
27 LilyPond. It is written as a HTML document, which is available
28 @uref{http://@/lilypond@/.org/@/doc/@/v2.7/@/Documentation/@/user/@/lilypond@/-internals/,on@/-line},
29 but is also included with the LilyPond documentation package.
31 There are three areas where the default settings may be changed:
35 Output: changing the appearance of individual
36 objects. For example, changing stem directions or the location of
40 Context: changing aspects of the translation from music events to
41 notation. For example, giving each staff a separate time signature.
44 Global layout: changing the appearance of the spacing, line
45 breaks, and page dimensions.
48 Then there are separate systems for typesetting text (like
49 @emph{ritardando}) and selecting different fonts. This chapter also
52 Internally, LilyPond uses Scheme (a LISP dialect) to provide
53 infrastructure. Overriding layout decisions in effect accesses the
54 program internals, which requires Scheme input. Scheme elements are
55 introduced in a @code{.ly} file with the hash mark
56 @code{#}.@footnote{@ref{Scheme tutorial} contains a short tutorial
57 on entering numbers, lists, strings, and symbols in Scheme.}
61 * Interpretation contexts::
62 * The \override command::
66 @node Interpretation contexts
67 @section Interpretation contexts
69 When music is printed, a lot of notational elements must be added to the
70 input, which is often bare bones. For example, compare the input and
71 output of the following example:
73 @lilypond[quote,verbatim,relative=2,fragment]
77 The input is rather sparse, but in the output, bar lines, accidentals,
78 clef, and time signature are added. LilyPond @emph{interprets} the
79 input. During this step, the musical information is inspected in time
80 order, similar to reading a score from left to right. While reading,
81 the input, the program remembers where measure boundaries are, and what
82 pitches need explicit accidentals. This information can be presented on
83 several levels. For example, the effect of an accidental is limited
84 to a single staff, while a bar line must be synchronized across the
87 Within LilyPond, these rules and bits of information are grouped in
88 so-called Contexts. Examples of context are @context{Voice},
89 @context{Staff}, and @context{Score}. They are hierarchical, for
90 example, a @context{Staff} can contain many @context{Voice}s, and a
91 @context{Score} can contain many @context{Staff} contexts.
93 Each context has the responsibility for enforcing some notation rules,
94 creating some notation objects and maintaining the associated
95 properties. So, the synchronization of bar lines is handled at
96 @context{Score} context. The @context{Voice} may introduce an
97 accidental and then the @context{Staff} context maintains the rule to
98 show or suppress the accidental for the remainder of the measure.
100 For simple scores, contexts are created implicitly, and you need not
101 be aware of them. For larger pieces, such as piano music, they must be
102 created explicitly to make sure that you get as many staves as you
103 need, and that they are in the correct order. For typesetting pieces
104 with specialized notation, it can be useful to modify existing or
105 to define new contexts.
108 A complete description of all available contexts is in the program
111 @internalsref{Contexts}.
114 Translation @arrow{} Context.
117 @c [TODO: describe propagation]
121 * Creating contexts::
122 * Changing context properties on the fly::
123 * Modifying context plug-ins::
124 * Layout tunings within contexts::
125 * Changing context default settings::
126 * Defining new contexts::
129 @node Creating contexts
130 @subsection Creating contexts
132 For scores with only one voice and one staff, correct contexts are
133 created automatically. For more complex scores, it is necessary to
134 create them by hand. There are three commands that do this.
136 The easiest command is @code{\new}, and it also the quickest to type.
137 It is prepended to a music expression, for example
141 @cindex Context, creating
144 \new @var{type} @var{music expression}
148 where @var{type} is a context name (like @code{Staff} or
149 @code{Voice}). This command creates a new context, and starts
150 interpreting the @var{music expression} with that.
152 A practical application of @code{\new} is a score with many
153 staves. Each part that should be on its own staff, is preceded with
156 @lilypond[quote,verbatim,relative=2,ragged-right,fragment]
157 << \new Staff { c4 c }
162 @cindex @code{\context}
164 Like @code{\new}, the @code{\context} command also directs a music
165 expression to a context object, but gives the context an extra name. The
169 \context @var{type} = @var{id} @var{music}
172 This form will search for an existing context of type @var{type}
173 called @var{id}. If that context does not exist yet, it is created.
174 This is useful if the context is referred to later on. For example, when
175 setting lyrics the melody is in a named context
178 \context Voice = "@b{tenor}" @var{music}
182 so the texts can be properly aligned to its notes,
185 \new Lyrics \lyricsto "@b{tenor}" @var{lyrics}
190 Another possibility is funneling two different music expressions into
191 one context. In the following example, articulations and notes are
196 arts = @{ s4-. s4-> @}
199 They are combined by sending both to the same @context{Voice} context,
202 << \new Staff \context Voice = "A" \music
203 \context Voice = "A" \arts
206 @lilypond[quote,ragged-right]
210 \new Staff \context Voice = "A" \music
211 \context Voice = "A" \arts
215 With this mechanism, it is possible to define an Urtext (original
216 edition), with the option to put several distinct articulations on the
219 @cindex creating contexts
221 The third command for creating contexts is
223 \context @var{type} @var{music}
228 This is similar to @code{\context} with @code{= @var{id}}, but matches
229 any context of type @var{type}, regardless of its given name.
231 This variant is used with music expressions that can be interpreted at
232 several levels. For example, the @code{\applyOutput} command (see
233 @ref{Running a function on all layout objects}). Without an explicit
234 @code{\context}, it is usually applied to @context{Voice}
237 \applyOutput #@var{function} % apply to Voice
240 To have it interpreted at the @context{Score} or @context{Staff} level use
244 \context Score \applyOutput #@var{function}
245 \context Staff \applyOutput #@var{function}
249 @node Changing context properties on the fly
250 @subsection Changing context properties on the fly
254 @cindex changing properties
256 Each context can have different @emph{properties}, variables contained
257 in that context. They can be changed during the interpretation step.
258 This is achieved by inserting the @code{\set} command in the music,
261 \set @var{context}.@var{prop} = #@var{value}
265 @lilypond[quote,verbatim,relative=2,fragment]
267 \set Score.skipBars = ##t
271 This command skips measures that have no notes. The result is that
272 multi-rests are condensed. The value assigned is a Scheme object. In
273 this case, it is @code{#t}, the boolean True value.
275 If the @var{context} argument is left out, then the current bottom-most
276 context (typically @context{ChordNames}, @context{Voice}, or
277 @context{Lyrics}) is used. In this example,
279 @lilypond[quote,verbatim,relative=2,fragment]
281 \set autoBeaming = ##f
286 the @var{context} argument to @code{\set} is left out, so automatic
287 beaming is switched off in the current @internalsref{Voice}. Note that
288 the bottom-most context does not always contain the property that you
289 wish to change -- for example, attempting to set the @code{skipBars}
290 property (of the bottom-most context, in this case @code{Voice}) will
293 @lilypond[quote,verbatim,relative=2,fragment]
299 Contexts are hierarchical, so if a bigger context was specified, for
300 example @context{Staff}, then the change would also apply to all
301 @context{Voice}s in the current stave. The change is applied
302 `on-the-fly', during the music, so that the setting only affects the
303 second group of eighth notes.
305 @cindex @code{\unset}
307 There is also an @code{\unset} command,
309 \unset @var{context}.@var{prop}
313 which removes the definition of @var{prop}. This command removes
314 the definition only if it is set in @var{context}, so
317 \set Staff.autoBeaming = ##f
321 introduces a property setting at @code{Staff} level. The setting also
322 applies to the current @code{Voice}. However,
325 \unset Voice.autoBeaming
329 does not have any effect. To cancel this setting, the @code{\unset}
330 must be specified on the same level as the original @code{\set}. In
331 other words, undoing the effect of @code{Staff.autoBeaming = ##f}
334 \unset Staff.autoBeaming
337 Like @code{\set}, the @var{context} argument does not have to be
338 specified for a bottom context, so the two statements
341 \set Voice.autoBeaming = ##t
342 \set autoBeaming = ##t
350 Settings that should only apply to a single time-step can be entered
351 with @code{\once}, for example in
353 @lilypond[quote,verbatim,relative=2,fragment]
355 \once \set fontSize = #4.7
360 the property @code{fontSize} is unset automatically after the second
363 A full description of all available context properties is in the
364 program reference, see
366 @internalsref{Tunable context properties}.
369 Translation @arrow{} Tunable context properties.
373 @node Modifying context plug-ins
374 @subsection Modifying context plug-ins
376 Notation contexts (like Score and Staff) not only store properties,
377 they also contain plug-ins, called ``engravers'' that create notation
378 elements. For example, the Voice context contains a
379 @code{Note_head_engraver} and the Staff context contains a
380 @code{Key_signature_engraver}.
382 For a full a description of each plug-in, see
384 @internalsref{Engravers}.
387 Program reference @arrow Translation @arrow{} Engravers.
389 Every context described in
391 @internalsref{Contexts}
394 Program reference @arrow Translation @arrow{} Context.
396 lists the engravers used for that context.
399 It can be useful to shuffle around these plug-ins. This is done by
400 starting a new context, with @code{\new} or @code{\context}, and
401 modifying it like this,
406 \new @var{context} \with @{
417 where the @dots{} should be the name of an engraver. Here is a simple
418 example which removes @code{Time_signature_engraver} and
419 @code{Clef_engraver} from a @code{Staff} context,
421 @lilypond[quote,relative=1,verbatim,fragment]
426 \remove "Time_signature_engraver"
427 \remove "Clef_engraver"
434 In the second staff there are no time signature or clef symbols. This
435 is a rather crude method of making objects disappear since it will affect
436 the entire staff. The spacing is adversely influenced too. A more
437 sophisticated method of blanking objects is shown in @ref{Common tweaks}.
439 The next example shows a practical application. Bar lines and time
440 signatures are normally synchronized across the score. This is done
441 by the @code{Timing_translator} and @code{Default_bar_line_engraver}.
442 This plug-in keeps an administration of time signature, location
443 within the measure, etc. By moving thes engraver from @code{Score} to
444 @code{Staff} context, we can have a score where each staff has its own
447 @cindex polymetric scores
448 @cindex Time signatures, multiple
450 @lilypond[quote,relative=1,ragged-right,verbatim,fragment]
452 \remove "Timing_translator"
453 \remove "Default_bar_line_engraver"
456 \consists "Timing_translator"
457 \consists "Default_bar_line_engraver"
463 \consists "Timing_translator"
464 \consists "Default_bar_line_engraver"
473 @node Layout tunings within contexts
474 @subsection Layout tunings within contexts
476 Each context is responsible for creating certain types of graphical
477 objects. The settings used for printing these objects are also stored by
478 context. By changing these settings, the appearance of objects can be
481 The syntax for this is
484 \override @var{context}.@var{name} #'@var{property} = #@var{value}
487 Here @var{name} is the name of a graphical object, like @code{Stem} or
488 @code{NoteHead}, and @var{property} is an internal variable of the
489 formatting system (`grob property' or `layout property'). The latter is a
490 symbol, so it must be quoted. The subsection @ref{Constructing a
491 tweak} explains what to fill in for @var{name}, @var{property}, and
492 @var{value}. Here we only discuss the functionality of this command.
497 \override Staff.Stem #'thickness = #4.0
501 makes stems thicker (the default is 1.3, with staff line thickness as a
502 unit). Since the command specifies @context{Staff} as context, it only
503 applies to the current staff. Other staves will keep their normal
504 appearance. Here we see the command in action:
506 @lilypond[quote,verbatim,relative=2,fragment]
508 \override Staff.Stem #'thickness = #4.0
514 The @code{\override} command changes the definition of the @code{Stem}
515 within the current @context{Staff}. After the command is interpreted
516 all stems are thickened.
518 Analogous to @code{\set}, the @var{context} argument may be left out,
519 causing it to default to @context{Voice}, and adding @code{\once} applies
520 the change during one timestep only
522 @lilypond[quote,fragment,verbatim,relative=2]
524 \once \override Stem #'thickness = #4.0
529 The @code{\override} must be done before the object is
530 started. Therefore, when altering @emph{Spanner} objects, like slurs or
531 beams, the @code{\override} command must be executed at the moment when
532 the object is created. In this example,
535 @lilypond[quote,fragment,verbatim,relative=2]
536 \override Slur #'thickness = #3.0
538 \override Beam #'thickness = #0.6
543 the slur is fatter but the beam is not. This is because the command for
544 @code{Beam} comes after the Beam is started. Therefore it has no effect.
546 Analogous to @code{\unset}, the @code{\revert} command for a context
547 undoes an @code{\override} command; like with @code{\unset}, it only
548 affects settings that were made in the same context. In other words, the
549 @code{\revert} in the next example does not do anything.
552 \override Voice.Stem #'thickness = #4.0
553 \revert Staff.Stem #'thickness
556 Some tweakable options are called ``subproperties'' and reside inside
557 properties. To tweak those, use
560 \override Stem #'details #'beamed-lengths = #'(4 4 3)
566 Internals: @internalsref{OverrideProperty}, @internalsref{RevertProperty},
567 @internalsref{PropertySet}, @internalsref{Backend}, and
568 @internalsref{All layout objects}.
573 The back-end is not very strict in type-checking object properties.
574 Cyclic references in Scheme values for properties can cause hangs
578 @node Changing context default settings
579 @subsection Changing context default settings
581 The adjustments of the previous subsections (@ref{Changing context
582 properties on the fly}, @ref{Modifying context plug-ins}, and
583 @ref{Layout tunings within contexts}) can also be entered separately
584 from the music, in the @code{\layout} block,
593 \override Stem #'thickness = #4.0
594 \remove "Time_signature_engraver"
605 takes the existing definition for context @context{Staff} from the
606 identifier @code{\Staff}.
611 \override Stem #'thickness = #4.0
612 \remove "Time_signature_engraver"
616 affect all staves in the score.
618 Other contexts can be modified analogously.
620 The @code{\set} keyword is optional within the @code{\layout} block, so
636 It is not possible to collect context changes in a variable, and apply
637 them to one @code{\context} definition by referring to that variable.
639 The @code{\RemoveEmptyStaffContext} will override your current
640 @code{\Staff} variable. If you wish to change the defaults for a
641 staff that uses @code{\RemoveEmptyStaffContext}, you must do so
642 after calling @code{\RemoveemptyStaffContext}, ie
647 \RemoveEmptyStaffContext
649 \override Stem #'thickness = #4.0
655 @node Defining new contexts
656 @subsection Defining new contexts
658 Specific contexts, like @context{Staff} and @code{Voice}, are made of
659 simple building blocks, and it is possible to compose engraver
660 plug-ins in different combinations, thereby creating new types of
663 The next example shows how to build a different type of
664 @context{Voice} context from scratch. It will be similar to
665 @code{Voice}, but prints centered slash noteheads only. It can be used
666 to indicate improvisation in Jazz pieces,
668 @lilypond[quote,ragged-right]
671 \type "Engraver_group"
672 \consists "Note_heads_engraver"
673 \consists "Text_engraver"
674 \consists Pitch_squash_engraver
675 squashedPosition = #0
676 \override NoteHead #'style = #'slash
677 \override Stem #'transparent = ##t
681 \accepts "ImproVoice"
685 a4 d8 bes8 \new ImproVoice { c4^"ad lib" c
686 c4 c^"undress" c_"while playing :)" c }
692 These settings are again done within a @code{\context} block inside a
693 @code{\layout} block,
703 In the following discussion, the example input shown should go on the
704 @dots{} in the previous fragment.
706 First, the context gets a name. Instead of @context{Voice} it
707 will be called @context{ImproVoice},
713 Since it is similar to the @context{Voice}, we want commands that work
714 on (existing) @context{Voice}s to remain working. This is achieved by
715 giving the new context an alias @context{Voice},
721 The context will print notes, and instructive texts
724 \consists Note_heads_engraver
725 \consists Text_engraver
728 but only on the center line,
731 \consists Pitch_squash_engraver
732 squashedPosition = #0
735 The @internalsref{Pitch_squash_engraver} modifies note heads (created
736 by @internalsref{Note_heads_engraver}) and sets their vertical
737 position to the value of @code{squashedPosition}, in this case@tie{}@code{0},
740 The notes look like a slash, without a stem,
743 \override NoteHead #'style = #'slash
744 \override Stem #'transparent = ##t
748 All these plug-ins have to cooperate, and this is achieved with a
749 special plug-in, which must be marked with the keyword @code{\type}.
750 This should always be @internalsref{Engraver_group},
753 \type "Engraver_group"
761 \type "Engraver_group"
762 \consists "Note_heads_engraver"
763 \consists "Text_engraver"
764 \consists Pitch_squash_engraver
765 squashedPosition = #0
766 \override NoteHead #'style = #'slash
767 \override Stem #'transparent = ##t
772 Contexts form hierarchies. We want to hang the @context{ImproVoice}
773 under @context{Staff}, just like normal @code{Voice}s. Therefore, we
774 modify the @code{Staff} definition with the @code{\accepts}
775 command,@footnote{The opposite of @code{\accepts} is @code{\denies},
776 which is sometimes needed when reusing existing context definitions.}
787 Putting both into a @code{\layout} block, like
797 \accepts "ImproVoice"
802 Then the output at the start of this subsection can be entered as
810 c c_"while playing :)"
819 @node The \override command
820 @section The \override command
822 In the previous section, we have already touched on a command that
823 changes layout details: the @code{\override} command. In this section,
824 we will look in more detail at how to use the command in practice.
825 First, we will give a few versatile commands that are sufficient
826 for many situations. The next section will discuss the general use of
832 * Constructing a tweak::
833 * Navigating the program reference::
834 * Layout interfaces::
835 * Determining the grob property::
836 * Objects connected to the input::
843 @subsection Common tweaks
845 @c Should we point at ly/property-init.ly ? -gp
846 Some overrides are so common that predefined commands are provided as
847 short-cuts, for example, @code{\slurUp} and @code{\stemDown}. These
848 commands are described in
852 @c @ref{Notation manual},
855 under the sections for slurs and stems
858 The exact tuning possibilities for each type of layout object are
859 documented in the program reference of the respective
860 object. However, many layout objects share properties, which can be
861 used to apply generic tweaks. We mention a few of these:
864 @item The @code{extra-offset} property, which
865 @cindex @code{extra-offset}
866 has a pair of numbers as value, moves objects around in the printout.
867 The first number controls left-right movement; a positive number will
868 move the object to the right. The second number controls up-down
869 movement; a positive number will move it higher. The units of these
870 offsets are staff-spaces. The @code{extra-offset} property is a
871 low-level feature: the formatting engine is completely oblivious to
874 In the following example, the second fingering is moved a little to
875 the left, and 1.8 staff space downwards:
877 @cindex setting object properties
879 @lilypond[quote,fragment,relative=1,verbatim]
882 \once \override Fingering
883 #'extra-offset = #'(-0.3 . -1.8)
888 Setting the @code{transparent} property will cause an object to be printed
889 in `invisible ink': the object is not printed, but all its other
890 behavior is retained. The object still takes up space, it takes part in
891 collisions, and slurs, ties, and beams can be attached to it.
893 @cindex transparent objects
894 @cindex removing objects
895 @cindex hiding objects
896 @cindex invisible objects
897 The following example demonstrates how to connect different voices
898 using ties. Normally, ties only connect two notes in the same
899 voice. By introducing a tie in a different voice,
901 @lilypond[quote,fragment,relative=2]
910 and blanking the first up-stem in that voice, the tie appears to cross
913 @lilypond[quote,fragment,relative=2,verbatim]
915 \once \override Stem #'transparent = ##t
923 The @code{padding} property for objects with
924 @cindex @code{padding}
925 @code{side-position-interface} can be set to increase the distance between
926 symbols that are printed above or below notes. We provide two
927 examples; a more elaborate explanation is in @ref{Constructing a
930 @lilypond[quote,fragment,relative=1,verbatim]
932 \override Script #'padding = #3
936 @lilypond[quote,fragment,relative=1,verbatim]
937 % This will not work, see below:
938 \override MetronomeMark #'padding = #3
942 \override Score.MetronomeMark #'padding = #3
947 Note in the second example how important it is to figure out what
948 context handles a certain object. Since the @code{MetronomeMark} object
949 is handled in the Score context, property changes in the @code{Voice}
950 context will not be noticed.
954 Some tweakable options are called ``subproperties'' and reside inside
955 properties. To tweak those, use
958 \override Stem #'details #'beamed-lengths = #'(4 4 3)
962 More specific overrides are also possible. The next section
963 discusses in depth how to figure out these statements for yourself.
966 @node Constructing a tweak
967 @subsection Constructing a tweak
969 The general procedure of changing output, that is, entering
973 \override Voice.Stem #'thickness = #3.0
977 means that we have to determine these bits of information:
980 @item the context: here @context{Voice}.
981 @item the layout object: here @code{Stem}.
982 @item the layout property: here @code{thickness}
983 @item a sensible value: here @code{3.0}
987 @cindex internal documentation
988 @cindex finding graphical objects
989 @cindex graphical object descriptions
991 @cindex @code{\override}
992 @cindex internal documentation
994 We demonstrate how to glean this information from the notation manual
995 and the program reference.
997 @node Navigating the program reference
998 @subsection Navigating the program reference
1000 Suppose we want to move the fingering indication in the fragment
1003 @lilypond[quote,fragment,relative=2,verbatim]
1009 If you visit the documentation on fingering instructions (in
1010 @ref{Fingering instructions}), you will notice that there is written:
1015 Program reference: @internalsref{FingerEvent} and @internalsref{Fingering}.
1021 This fragment points to two parts of the program reference: a page
1022 on @code{FingerEvent} and one on @code{Fingering}.
1024 The page on @code{FingerEvent} describes the properties of the music
1025 expression for the input @code{-2}. The page contains many links
1026 forward. For example, it says
1029 Accepted by: @internalsref{Fingering_engraver},
1033 That link brings us to the documentation for the Engraver, the
1037 This engraver creates the following layout objects: @internalsref{Fingering}.
1040 In other words, once the @code{FingerEvent}s are interpreted, the
1041 @code{Fingering_engraver} plug-in will process them.
1042 The @code{Fingering_engraver} is also listed to create
1043 @internalsref{Fingering} objects,
1046 Lo and behold, that is also the
1047 second bit of information listed under @b{See also} in the Notation
1048 manual. By clicking around in the program reference, we can follow the
1049 flow of information within the program, either forward (like we did
1050 here), or backwards, following links like this:
1054 @item @internalsref{Fingering}:
1055 @internalsref{Fingering} objects are created by:
1056 @b{@internalsref{Fingering_engraver}}
1058 @item @internalsref{Fingering_engraver}:
1059 Music types accepted: @b{@internalsref{fingering-event}}
1061 @item @internalsref{fingering-event}:
1062 Music event type @code{fingering-event} is in Music expressions named
1063 @b{@internalsref{FingerEvent}}
1066 This path goes against the flow of information in the program: it
1067 starts from the output, and ends at the input event.
1069 The program reference can also be browsed like a normal document. It
1070 contains a chapter on
1072 @internalsref{Music definitions},
1075 @code{Music definitions}
1077 on @internalsref{Translation}, and the @internalsref{Backend}. Every
1078 chapter lists all the definitions used, and all properties that may be
1082 @node Layout interfaces
1083 @subsection Layout interfaces
1085 @cindex interface, layout
1086 @cindex layout interface
1089 The HTML page that we found in the previous section, describes the
1090 layout object called @internalsref{Fingering}. Such an object is a
1091 symbol within the score. It has properties that store numbers (like
1092 thicknesses and directions), but also pointers to related objects. A
1093 layout object is also called a @emph{Grob}, which is short for Graphical
1094 Object. For more details about Grobs, see @internalsref{grob-interface}.
1096 The page for @code{Fingering} lists the definitions for the
1097 @code{Fingering} object. For example, the page says
1100 @code{padding} (dimension, in staff space):
1106 which means that the number will be kept at a distance of at least 0.6
1110 Each layout object may have several functions as a notational or
1111 typographical element. For example, the Fingering object
1112 has the following aspects
1116 Its size is independent of the horizontal spacing, unlike slurs or beams.
1119 It is a piece of text. Granted, it is usually a very short text.
1122 That piece of text is typeset with a font, unlike slurs or beams.
1125 Horizontally, the center of the symbol should be aligned to the
1126 center of the notehead.
1129 Vertically, the symbol is placed next to the note and the staff.
1132 The vertical position is also coordinated with other super- and subscript
1136 Each of these aspects is captured in so-called @emph{interface}s,
1137 which are listed on the @internalsref{Fingering} page at the bottom
1140 This object supports the following interfaces:
1141 @internalsref{item-interface},
1142 @internalsref{self-alignment-interface},
1143 @internalsref{side-position-interface}, @internalsref{text-interface},
1144 @internalsref{text-script-interface}, @internalsref{font-interface},
1145 @internalsref{finger-interface}, and @internalsref{grob-interface}.
1148 Clicking any of the links will take you to the page of the respective
1149 object interface. Each interface has a number of properties. Some of
1150 them are not user-serviceable (``Internal properties''), but others
1153 We have been talking of @emph{the} @code{Fingering} object, but actually it
1154 does not amount to much. The initialization file
1155 @file{scm/@/define@/-grobs@/.scm} shows the soul of the `object',
1160 (avoid-slur . around)
1161 (slur-padding . 0.2)
1162 (staff-padding . 0.5)
1163 (self-alignment-X . 0)
1164 (self-alignment-Y . 0)
1165 (script-priority . 100)
1166 (stencil . ,ly:text-interface::print)
1167 (direction . ,ly:script-interface::calc-direction)
1168 (font-encoding . fetaNumber)
1169 (font-size . -5) ; don't overlap when next to heads.
1170 (meta . ((class . Item)
1171 (interfaces . (finger-interface
1173 text-script-interface
1175 side-position-interface
1176 self-alignment-interface
1177 item-interface))))))
1181 As you can see, the @code{Fingering} object is nothing more than a
1182 bunch of variable settings, and the webpage in the Program Reference
1183 is directly generated from this definition.
1185 @node Determining the grob property
1186 @subsection Determining the grob property
1189 Recall that we wanted to change the position of the @b{2} in
1191 @lilypond[quote,fragment,relative=2,verbatim]
1197 Since the @b{2} is vertically positioned next to its note, we have to
1198 meddle with the interface associated with this positioning. This is
1199 done using @code{side-position-interface}. The page for this interface
1203 @code{side-position-interface}
1205 Position a victim object (this one) next to other objects (the
1206 support). The property @code{direction} signifies where to put the
1207 victim object relative to the support (left or right, up or down?)
1212 below this description, the variable @code{padding} is described as
1217 (dimension, in staff space)
1219 Add this much extra space between objects that are next to each other.
1223 By increasing the value of @code{padding}, we can move away the
1224 fingering. The following command inserts 3 staff spaces of white
1225 between the note and the fingering:
1227 \once \override Voice.Fingering #'padding = #3
1230 Inserting this command before the Fingering object is created,
1231 i.e., before @code{c2}, yields the following result:
1233 @lilypond[quote,relative=2,fragment,verbatim]
1234 \once \override Voice.Fingering #'padding = #3
1241 In this case, the context for this tweak is @context{Voice}. This
1242 fact can also be deduced from the program reference, for the page for
1243 the @internalsref{Fingering_engraver} plug-in says
1246 Fingering_engraver is part of contexts: @dots{} @b{@internalsref{Voice}}
1249 @node Objects connected to the input
1250 @subsection Objects connected to the input
1252 In some cases, it is possible to take a short-cut for tuning graphical
1253 objects. For objects that result directly from a piece of the input,
1254 you can use the @code{\tweak} function, for example
1256 @lilypond[relative=2,fragment,verbatim,ragged-right]
1259 \tweak #'color #red d
1261 \tweak #'duration-log #1 a
1262 >4-\tweak #'padding #10 -.
1265 As you can see, properties are set directly in the objects directly,
1266 without mentioning the grob name or context where this should be
1269 This technique only works for objects that are directly connected to
1270 an @internalsref{event} from the input, for example
1273 @item note heads, caused by chord-pitch.
1274 @item articulation signs, caused by articulation instructions
1277 It notably does not work for stems and accidentals (these are caused
1278 by note heads, not by music events), clefs (these are not caused by
1279 music inputs, but rather by the change of a property value).
1281 In a similar vein, objects may be parenthesized by prefixing
1282 @code{\parenthesize} to the music event,
1284 @lilypond[relative=2,fragment,verbatim,ragged-right]
1295 @node Difficult tweaks
1296 @subsection Difficult tweaks
1298 There are a few classes of difficult adjustments.
1304 Another difficult adjustment is the appearance of spanner objects,
1305 such as slur and tie. Initially, only one of these objects is created,
1306 and they can be adjusted with the normal mechanism. However, in some
1307 cases the spanners cross line breaks. If this happens, these objects
1308 are cloned. A separate object is created for every system that it is
1309 in. These are clones of the original object and inherit all
1310 properties, including @code{\override}s.
1313 In other words, an @code{\override} always affects all pieces of a
1314 broken spanner. To change only one part of a spanner at a line break,
1315 it is necessary to hook into the formatting process. The
1316 @code{after-line-breaking} callback contains the Scheme procedure that
1317 is called after the line breaks have been determined, and layout
1318 objects have been split over different systems.
1320 In the following example, we define a procedure
1321 @code{my-callback}. This procedure
1325 determines if we have been split across line breaks
1327 if yes, retrieves all the split objects
1329 checks if we are the last of the split objects
1331 if yes, it sets @code{extra-offset}.
1334 This procedure is installed into @internalsref{Tie}, so the last part
1335 of the broken tie is translated up.
1337 @lilypond[quote,verbatim,ragged-right]
1338 #(define (my-callback grob)
1340 ; have we been split?
1341 (orig (ly:grob-original grob))
1343 ; if yes, get the split pieces (our siblings)
1344 (siblings (if (ly:grob? orig)
1345 (ly:spanner-broken-into orig) '() )))
1347 (if (and (>= (length siblings) 2)
1348 (eq? (car (last-pair siblings)) grob))
1349 (ly:grob-set-property! grob 'extra-offset '(-2 . 5)))))
1352 \override Tie #'after-line-breaking =
1359 When applying this trick, the new @code{after-line-breaking} callback
1360 should also call the old one @code{after-line-breaking}, if there is
1361 one. For example, if using this with @code{Hairpin},
1362 @code{ly:hairpin::after-line-breaking} should also be called.
1365 @item Some objects cannot be changed with @code{\override} for
1366 technical reasons. Examples of those are @code{NonMusicalPaperColumn}
1367 and @code{PaperColumn}. They can be changed with the
1368 @code{\outputProperty} function, which works similar to @code{\once
1369 \override}, but uses a different syntax,
1373 #"Score.NonMusicalPaperColumn" % Grob name
1374 #'line-break-system-details % Property name
1375 #'((next-padding . 20)) % Value