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
14 The controls available for tuning are described in a separate
15 document, the @internalsref{Program reference} manual. That manual
16 lists all different variables, functions and options available in
17 LilyPond. It is written as a HTML document, which is available
18 @uref{http://lilypond.org/doc/Documentation/user/out-www/lilypond-internals/,on-line},
19 but is also included with the LilyPond documentation package.
21 There are three areas where the default settings may be changed:
24 @item Output: changing the appearance of individual
25 objects. For example, changing stem directions, or the location of
28 @item Context: changing aspects of the translation from music events to
29 notation. For example, giving each staff a separate time signature.
31 @item Global layout: changing the appearance of the spacing, line
32 breaks and page dimensions.
35 Then, there are separate systems for typesetting text (like
36 @emph{ritardando}) and selecting different fonts. This chapter also
39 Internally, LilyPond uses Scheme (a LISP dialect) to provide
40 infrastructure. Overriding layout decisions in effect accesses the
41 program internals, so it is necessary to learn a (very small) subset
42 of Scheme. That is why this chapter starts with a short tutorial on
43 entering numbers, lists, strings and symbols in Scheme.
49 * Interpretation contexts::
57 @section Scheme tutorial
61 @cindex Scheme, in-line code
62 @cindex accessing Scheme
63 @cindex evaluating Scheme
66 LilyPond uses the Scheme programming language, both as part of the
67 input syntax, and as internal mechanism to glue together modules of
68 the program. This section is a very brief overview of entering data in
69 Scheme.@footnote{If you want to know more about Scheme, see
70 @uref{http://www.schemers.org}.}
72 The most basic thing of a language is data: numbers, character
73 strings, lists, etc. Here is a list of data types that are relevant to
78 Boolean values are True or False. The Scheme for True is @code{#t}
79 and False is @code{#f}.
81 Numbers are entered in the standard fashion,
82 @code{1} is the (integer) number one, while @code{-1.5} is a
83 floating point number (a non-integer number).
85 Strings are enclosed in double quotes,
90 Strings may span several lines
97 Quotation marks and newlines can also be added with so-called escape
98 sequences. The string @code{a said "b"} is entered as
103 Newlines and backslashes are escaped with @code{\n} and @code{\\}
108 In a music file, snippets of Scheme code are introduced with the hash
109 mark @code{#}. So, the previous examples translated in LilyPond are
120 For the rest of this section, we will assume that the data is entered
121 in a music file, so we add @code{#}s everywhere.
123 Scheme can be used to do calculations. It uses @emph{prefix}
124 syntax. Adding 1 and 2 is written as @code{(+ 1 2)} rather than the
132 The arrow @result{} shows that the result of evaluating @code{(+ 1 2)}
133 is @code{3}. Calculations may be nested; the result of a function may
134 be used for another calculation.
142 These calculations are examples of evaluations; an expression like
143 @code{(* 3 4)} is replaced by its value @code{12}. A similar thing
144 happens with variables. After defining a variable
150 variables can also be used in expressions, here
153 twentyFour = #(* 2 twelve)
156 the number 24 is stored in the variable @code{twentyFour}.
158 The @emph{name} of a variable is also an expression, similar to a
159 number or a string. It is entered as
165 The quote mark @code{'} prevents Scheme interpreter from substituting
166 @code{24} for the @code{twentyFour}. Instead, we get the name
169 This syntax will be used very frequently, since many of the layout
170 tweaks involve assigning (Scheme) values to internal variables, for
174 \override Stem #'thickness = #2.6
177 This instruction adjusts the appearance of stems. The value @code{2.6}
178 is put into a the @code{thickness} variable of a @code{Stem}
179 object. This makes stems almost twice as thick as their normal size.
180 To distinguish between variables defined in input files (like
181 @code{twentyFour} in the example above), and internal variables, we
182 will call the latter ``properties.'' So, the stem object has a
183 @code{thickness} property.
185 Two-dimensional offsets (X and Y coordinates) as well as object sizes
186 (intervals with a left and right point) are entered as @code{pairs}. A
187 pair@footnote{In Scheme terminology, the pair is called @code{cons},
188 and its two elements are called car and cdr respectively.} is entered
189 as @code{(first . second)} and, like symbols, they must be quoted,
192 \override TextScript #'extra-offset = #'(1 . 2)
195 This assigns the pair (1, 2) to @code{extra-offset} variable of the
196 TextScript object. This moves the object 1 staff space to the right,
199 The two elements of a pair may be arbitrary values, for example
204 #'("blah-blah" . 3.14159265)
207 A list is entered by enclosing its elements in parentheses, and adding
208 a quote. For example,
214 We have been using lists all along. A calculation, like @code{(+ 1
215 2)} is also a list (containing the symbol @code{+} and the numbers 1
216 and 2). Normally lists are interpreted as calculations, and the Scheme
217 interpreter substitutes the outcome of the calculation. To enter a
218 list, we stop evaluation. This is done by quoting the list with a
219 quote @code{'} symbol. For calculations, do not use a quote.
221 Inside a quoted list or pair, there is no need to quote anymore. The
222 following is a pair of symbols, a list of symbols and a list of lists
227 #'(staff clef key-signature)
232 @section File structure
234 The following items may be present in a @file{.ly} file at toplevel
237 @item An output definition, such as @code{\bookpaper}, @code{\midi}
238 and @code{\paper}. Such a definition at toplevel changes the default
239 settings for the block entered.
241 @item An @code{\header} block. This sets the global header block. This
242 is the block containing the definitions for book-wide settings, like
243 composer, title, etc.
245 @item An @code{\addquote} statement. See @ref{Quoting other voices}
246 for more information.
248 @item A @code{\score} block. This score will be collected with other
249 toplevel scores, and combined as a single @code{\book}.
251 This behavior can be changed by setting the variable
252 @code{toplevel-score-handler} at toplevel. The default handler is
253 defined in the init file @file{scm/lily.scm}.
255 @item A @code{\book} block formats the block
257 This behavior can be changed by setting the variable
258 @code{toplevel-book-handler} at toplevel. The default handler is
259 defined in the init file @file{scm/lily.scm}.
262 @item A compound music expression, such as
267 This will add the piece in a @code{\score}, and formats it into a
268 single book together with all other toplevel @code{\score}s and music
271 This behavior can be changed by setting the variable
272 @code{toplevel-music-handler} at toplevel. The default handler is
273 defined in the init file @file{scm/lily.scm}.
277 The following example shows three things which may be entered at
281 % movements are non-justified by default
293 At any point in a file, any of the following lexical instructions can
297 @item @code{\version}
298 @item @code{\include}
299 @item @code{\encoding}
300 @item @code{\renameinput}
305 @node Interpretation contexts
306 @section Interpretation contexts
308 When music is printed, a lot of notation elements must be added to the
309 input, which is often bare bones. For example, compare the input and
310 output of the following example:
312 @lilypond[verbatim,relative=2,fragment]
316 The input is rather sparse, but in the output, bar lines, accidentals,
317 clef, and time signature are added. LilyPond @emph{interprets} the
318 input. During this step, the musical information is inspected in time
319 order, similar to reading a score from left to right. While reading,
320 the program remembers where measure boundaries are, and what pitches
321 need explicit accidentals. This information can be presented on
322 several levels. For example, the effect of an accidental is limited
323 to a single stave, while a bar line must be synchronized across the
326 Within LilyPond, these rules and bits of information are grouped in
327 so-called Contexts. Examples of context are @context{Voice},
328 @context{Staff}, and @context{Score}. They are hierarchical, for
329 example, a @context{Staff} can contain many @context{Voice}s, and a
330 @context{Score} can contain many @context{Staff} contexts.
332 Each context has the responsibility for enforcing some notation rules,
333 creating some notation objects and maintaining the associated
334 properties. So, the synchronization of bar lines is handled at
335 @context{Score} context. The @context{Voice} may introduce an
336 accidentals and then the @context{Staff} context maintains the rule to
337 show or suppress the accidental for the remainder of the measure.
339 For simple scores, contexts are created implicitly, and you need not
340 be aware of them. For larger pieces, such as piano music, they must be
341 created explicitly to make sure that you get as many staves as you
342 need, and that they are in the correct order. For typesetting pieces
343 with specialized notation, it can be useful to modify existing or
347 Full description of all available contexts is in the program
350 @internalsref{Contexts}.
353 Translation @arrow{} Context.
356 @c [TODO: describe propagation]
360 * Creating contexts::
361 * Changing context properties on the fly::
362 * Modifying context plug-ins::
363 * Layout tunings within contexts::
364 * Changing context default settings::
365 * Defining new contexts::
366 * Which properties to change::
369 @node Creating contexts
370 @subsection Creating contexts
372 For scores with only one voice and one staff, correct contexts are
373 created automatically. For more complex scores, it is necessary to
374 create them by hand. There are three commands which do this.
376 The easiest command is @code{\new}, and it also the quickest to type.
377 It is prepended to a music expression, for example
381 @cindex Context, creating
384 \new @var{type} @var{music expression}
388 where @var{type} is a context name (like @code{Staff} or
389 @code{Voice}). This command creates a new context, and starts
390 interpreting @var{music expression} with that.
392 A practical application of @code{\new} is a score with many
393 staves. Each part that should be on its own staff, is preceded with
396 @lilypond[verbatim,relative=2,raggedright,fragment]
397 << \new Staff { c4 c }
402 @cindex @code{\context}
404 Like @code{\new}, the @code{\context} command also directs a music
405 expression to a context object, but gives the context an extra name. The
409 \context @var{type} = @var{id} @var{music}
412 This form will search for an existing context of type @var{type}
413 called @var{id}. If that context does not exist yet, it is created.
414 This is useful if the context is referred to later on. For example, when
415 setting lyrics the melody is in a named context
418 \context Voice = "@b{tenor}" @var{music}
422 so the texts can be properly aligned to its notes,
425 \new Lyrics \lyricsto "@b{tenor}" @var{lyrics}
430 Another possibility is funneling two different music expressions into
431 one context. In the following example, articulations and notes are
439 They are combined by sending both to the same @context{Voice} context,
442 << \new Staff \context Voice = "A" \music
443 \context Voice = "A" \arts
446 @lilypond[raggedright]
449 \relative c'' << \new Staff \context Voice = "A" \music
450 \context Voice = "A" \arts
454 With this mechanism, it is possible to define an Urtext (original
455 edition), with the option put several distinct articulations on the
458 @cindex @code{\context}
459 @cindex creating contexts
461 The third command for creating contexts is
463 \context @var{type} @var{music}
468 This is similar to @code{\context} with @code{= @var{id}}, but matches
469 any context of type @var{type}, regardless of its given name.
471 This variant is used with music expressions that can be interpreted at
472 several levels. For example, the @code{\applyoutput} command (see
473 @ref{Running a function on all layout objects}). Without an explicit
474 @code{\context}, it is usually is applied to @context{Voice}
477 \applyoutput #@var{function} % apply to Voice
480 To have it interpreted at the @context{Score} or @context{Staff} level use
484 \context Score \applyoutput #@var{function}
485 \context Staff \applyoutput #@var{function}
489 @node Changing context properties on the fly
490 @subsection Changing context properties on the fly
494 @cindex changing properties
496 Each context can have different @emph{properties}, variables contained
497 in that context. They can be changed during the interpretation step.
498 This is achieved by inserting the @code{\set} command in the music,
501 @code{\set } @var{context}@code{.}@var{prop}@code{ = #}@var{value}
505 @lilypond[verbatim,relative=2,fragment]
507 \set Score.skipBars = ##t
511 This command skips measures that have no notes. The result is that
512 multi rests are condensed. The value assigned is a Scheme object. In
513 this case, it is @code{#t}, the boolean True value.
515 If the @var{context} argument is left out, then the current bottom-most
516 context (typically @context{ChordNames}, @context{Voice}, or
517 @context{Lyrics}) is used. In this example,
519 @lilypond[verbatim,relative=2,fragment]
521 \set autoBeaming = ##f
526 the @var{context} argument to @code{\set} is left out, and the current
527 @internalsref{Voice} is used.
529 Contexts are hierarchical, so if a bigger context was specified, for
530 example @context{Staff}, then the change would also apply to all
531 @context{Voice}s in the current stave. The change is applied
532 `on-the-fly', during the music, so that the setting only affects the
533 second group of eighth notes.
535 @cindex @code{\unset}
537 There is also an @code{\unset} command,
539 @code{\unset }@var{context}@code{.}@var{prop}
543 which removes the definition of @var{prop}. This command removes
544 the definition only if it is set in @var{context}. In
547 \set Staff.autoBeaming = ##f
548 \unset Voice.autoBeaming
552 the current @context{Voice} does not have the property, and the
553 definition at @context{Staff} level remains intact. Like @code{\set},
554 the @var{context} argument does not have to be specified for a bottom
557 Settings that should only apply to a single time-step can be entered
558 easily with @code{\once}, for example in
560 @lilypond[verbatim,relative=2,fragment]
562 \once \set fontSize = #4.7
567 the property @code{fontSize} is unset automatically after the second
570 A full description of all available context properties is in the
571 program reference, see
573 @internalsref{Tunable-context-properties}.
576 Translation @arrow{} Tunable context properties.
580 @node Modifying context plug-ins
581 @subsection Modifying context plug-ins
583 Notation contexts (like Score and Staff) not only store properties,
584 they also contain plug-ins, called ``engravers'' that create notation
585 elements. For example, the Voice context contains a
586 @code{Note_head_engraver} and the Staff context contains a
587 @code{Key_signature_engraver}.
589 For a full a description of each plug-in, see
591 @internalsref{Engravers}.
594 Program reference @arrow Translation @arrow{} Engravers.
596 Every context described in
598 @internalsref{Contexts}
601 Program reference @arrow Translation @arrow{} Context.
603 lists the engravers used for that context.
606 It can be useful to shuffle around these plug-ins. This is done by
607 starting a new context, with @code{\new} or @code{\context}, and
608 modifying it like this,
611 \new @var{context} \with @{
621 where the @dots{} should be the name of an engraver. Here is a simple
622 example which removes @code{Time_signature_engraver} and
623 @code{Clef_engraver} from a @code{Staff} context,
625 @lilypond[relative=1, verbatim,fragment]
630 \remove "Time_signature_engraver"
631 \remove "Clef_engraver"
638 In the second stave there are no time signature or clef symbols. This
639 is a rather crude method of making objects disappear since it will affect
640 the entire staff. The spacing will be adversely influenced too. A more
641 sophisticated methods of blanking objects is shown in @ref{Common
644 The next example shows a practical application. Bar lines and time
645 signatures are normally synchronized across the score. This is done
646 by the @code{Timing_engraver}. This plug-in keeps an administration of
647 time signature, location within the measure, etc. By moving the
648 @code{Timing_engraver} engraver from Score to Staff context, we can
649 have a score where each staff has its own time signature.
651 @cindex polymetric scores
654 @lilypond[relative=1,raggedright,verbatim,fragment]
656 \remove "Timing_engraver"
659 \consists "Timing_engraver"
665 \consists "Timing_engraver"
674 @node Layout tunings within contexts
675 @subsection Layout tunings within contexts
677 Each context is responsible for creating certain types of graphical
678 objects. The settings used for printing these objects are also stored by
679 context. By changing these settings, the appearance of objects can be
682 The syntax for this is
685 \override @var{context}.@var{name}@code{ #'}@var{property} = #@var{value}
688 Here @var{name} is the name of a graphical object, like @code{Stem} or
689 @code{NoteHead}, and @var{property} is an internal variable of the
690 formatting system (`grob property' or `layout property'). The latter is a
691 symbol, so it must be quoted. The subsection @ref{Constructing a
692 tweak} explains what to fill in for @var{name}, @var{property}, and
693 @var{value}. Here we only discuss functionality of this command.
698 \override Staff.Stem #'thickness = #4.0
702 makes stems thicker (the default is 1.3, with staff line thickness as a
703 unit). Since the command specifies @context{Staff} as context, it only
704 applies to the current staff. Other staves will keep their normal
705 appearance. Here we see the command in action:
707 @lilypond[verbatim,relative=2,fragment]
709 \override Staff.Stem #'thickness = #4.0
715 The @code{\override} command is executed during the interpreting phase,
716 and changes the definition of the @code{Stem} within
717 @context{Staff}. After the command all stems are thickened.
719 Analogous to @code{\set}, the @var{context} argument may be left out,
720 causing it to default to @context{Voice}, and adding @code{\once} applies
721 the change during one timestep only
723 @lilypond[fragment,verbatim,relative=2]
725 \once \override Stem #'thickness = #4.0
730 The @code{\override} must be done before the object is
731 started. Therefore, when altering @emph{Spanner} objects, like slurs or
732 beams, the @code{\override} command must be executed at the moment when
733 the object is created. In this example,
736 @lilypond[fragment,verbatim,relative=2]
737 \override Slur #'thickness = #3.0
739 \override Beam #'thickness = #0.6
744 the slur is fatter and the beam is not. This is because the command for
745 @code{Beam} comes after the Beam is started. Therefore it has no effect.
747 Analogous to @code{\unset}, the @code{\revert} command for a context
748 undoes a @code{\override} command; like with @code{\unset}, it only
749 affects settings that were made in the same context. In other words, the
750 @code{\revert} in the next example does not do anything.
753 \override Voice.Stem #'thickness = #4.0
754 \revert Staff.Stem #'thickness
762 Internals: @internalsref{OverrideProperty}, @internalsref{RevertProperty},
763 @internalsref{PropertySet}, @internalsref{All-backend-properties}, and
764 @internalsref{All-layout-objects}.
769 The back-end is not very strict in type-checking object properties.
770 Cyclic references in Scheme values for properties can cause hangs
774 @node Changing context default settings
775 @subsection Changing context default settings
777 The adjustments of the previous chapters can also be entered separate
778 from the music, in the @code{\paper} block,
787 \override Stem #'thickness
788 \remove "Time_signature_engraver"
799 takes the existing definition @context{Staff} from the identifier
800 @code{Staff}. This works analogously to other contexts.
805 \override Stem #'thickness
806 \remove "Time_signature_engraver"
810 affect all staves in the score.
812 The @code{\set} keyword is optional within the @code{\paper} block, so
825 It is not possible to collect changes in a variable, and apply them to
826 one @code{\context} definition by referring to that variable.
829 @node Defining new contexts
830 @subsection Defining new contexts
832 Specific contexts, like @context{Staff} and @code{Voice}, are made of
833 simple building blocks, and it is possible to compose engraver
834 plug-ins in different combinations, thereby creating new types of
837 The next example shows how to build a different type of
838 @context{Voice} context from scratch. It will be similar to
839 @code{Voice}, but print centered slash noteheads only. It can be used
840 to indicate improvisation in Jazz pieces,
842 @lilypond[raggedright]
845 \type "Engraver_group_engraver"
846 \consists "Note_heads_engraver"
847 \consists "Text_engraver"
848 \consists Pitch_squash_engraver
849 squashedPosition = #0
850 \override NoteHead #'style = #'slash
851 \override Stem #'transparent = ##t
855 \accepts "ImproVoice"
860 a4 d8 bes8 \new ImproVoice { c4^"ad lib" c
861 c4 c^"undress" c_"while playing :)" c }
867 These settings are again done within a @code{\context} block inside a
878 In the following discussion, the example input shown should go on the
879 @dots{} in the previous fragment.
881 First, name the context gets a name. Instead of @context{Voice} it
882 will be called @context{ImproVoice},
888 Since it is similar to the @context{Voice}, we want commands that work
889 on (existing) @context{Voice}s to remain working. This is achieved by
890 giving the new context an alias @context{Voice},
896 The context will print notes, and instructive texts
899 \consists Note_heads_engraver
900 \consists Text_engraver
903 but only on the center line,
906 \consists Pitch_squash_engraver
907 squashedPosition = #0
910 The @internalsref{Pitch_squash_engraver} modifies note heads (created
911 by @internalsref{Note_heads_engraver}) and sets their vertical
912 position to the value of @code{squashedPosition}, in this case
913 @code{0}, the center line.
915 The notes look like a slash, without a stem,
918 \override NoteHead #'style = #'slash
919 \override Stem #'transparent = ##t
923 All these plug-ins have to cooperate, and this is achieved with a
924 special plug-in, which must be marked with the keyword @code{\type}.
925 This should always be @internalsref{Engraver_group_engraver},
928 \type "Engraver_group_engraver"
931 Putting together, we get
936 \type "Engraver_group_engraver"
937 \consists "Note_heads_engraver"
938 \consists "Text_script_engraver"
939 \consists Pitch_squash_engraver
940 squashedPosition = #0
941 \override NoteHead #'style = #'slash
942 \override Stem #'transparent = ##t
947 Contexts form hierarchies. We want to hang the @context{ImproVoice}
948 under @context{Staff}, just like normal @code{Voice}s. Therefore, we
949 modify the @code{Staff} definition with the @code{\accepts}
950 command,@footnote{The opposite of @code{\accepts} is @code{\denies},
951 which is sometimes when reusing existing context definitions. }
962 Putting both into a @code{\paper} block, like
972 \accepts "ImproVoice"
977 Then the output at the start of this subsection can be entered as
985 c c_"while playing :)"
993 @node Which properties to change
994 @subsection Which properties to change
997 There are many different properties. Not all of them are listed in
998 this manual. However, the program reference lists them all in the
999 section @internalsref{Tunable-context-properties}, and most properties
1000 are demonstrated in one of the
1002 @uref{../../../../input/test/out-www/collated-files.html,tips-and-tricks}
1011 @section Tuning output
1013 In the previous section, we have already touched on a command that
1014 changes layout details, the @code{\override} command. In this section,
1015 we will look at in more detail how to use the command in practice.
1016 First, we will give a a few versatile commands, which are sufficient
1017 for many situations. The next section will discuss general use of
1021 There are situations where default layout decisions are not
1022 sufficient. In this section we discuss ways to override these
1025 Formatting is internally done by manipulating so called objects
1026 (graphic objects). Each object carries with it a set of properties
1027 (object or layout properties) specific to the object. For example, a
1028 stem object has properties that specify its direction, length, and
1031 The most direct way of tuning the output is to alter the values of
1032 these properties. There are two ways of doing that: First, you can
1033 temporarily change the definition of one type of object, thus
1034 affecting a whole set of objects. Second, you can select one specific
1035 object, and set a layout property in that object.
1037 Do not confuse layout properties with translation
1038 properties. Translation properties always use a mixed caps style
1039 naming, and are manipulated using @code{\set} and @code{\unset}:
1041 \set Context.propertyName = @var{value}
1044 Layout properties are use Scheme style variable naming, i.e. lower
1045 case words separated with dashes. They are symbols, and should always
1046 be quoted using @code{#'}. For example, this could be an imaginary
1047 layout property name:
1049 #'layout-property-name
1056 * Constructing a tweak::
1057 * Navigating the program reference::
1058 * Layout interfaces::
1059 * Determining the grob property::
1060 * Difficult tweaks::
1066 @subsection Common tweaks
1068 Some overrides are so common that predefined commands are provided as
1069 a short-cut, for example, @code{\slurUp} and @code{\stemDown}. These
1070 commands are described in
1074 @ref{Notation manual}, under the sections for slurs and stems
1077 The exact tuning possibilities for each type of layout object are
1078 documented in the program reference of the respective
1079 object. However, many layout objects share properties, which can be
1080 used to apply generic tweaks. We mention a few of these:
1083 @item The @code{extra-offset} property, which
1084 @cindex @code{extra-offset}
1085 has a pair of numbers as value, moves around objects in the printout.
1086 The first number controls left-right movement; a positive number will
1087 move the object to the right. The second number controls up-down
1088 movement; a positive number will move it higher. The units of these
1089 offsets are staff-spaces. The @code{extra-offset} property is a
1090 low-level feature: the formatting engine is completely oblivious to
1093 In the following example, the second fingering is moved a little to
1094 the left, and 1.8 staff space downwards:
1096 @cindex setting object properties
1098 @lilypond[fragment,relative=1,verbatim]
1101 \once \override Fingering
1102 #'extra-offset = #'(-0.3 . -1.8)
1107 Setting the @code{transparent} property will cause an object to be printed
1108 in `invisible ink': the object is not printed, but all its other
1109 behavior is retained. The object still takes up space, it takes part in
1110 collisions, and slurs, and ties and beams can be attached to it.
1112 @cindex transparent objects
1113 @cindex removing objects
1114 @cindex hiding objects
1115 @cindex invisible objects
1116 The following example demonstrates how to connect different voices
1117 using ties. Normally, ties only connect two notes in the same
1118 voice. By introducing a tie in a different voice,
1120 @lilypond[fragment,relative=2]
1129 and blanking a stem in that voice, the tie appears to cross voices:
1131 @lilypond[fragment,relative=2,verbatim]
1133 \once \override Stem #'transparent = ##t
1141 The @code{padding} property for objects with
1142 @cindex @code{padding}
1143 @code{side-position-interface} can be set to increase distance between
1144 symbols that are printed above or below notes. We only give an
1145 example; a more elaborate explanation is in @ref{Constructing a
1148 @lilypond[fragment,relative=1,verbatim]
1150 \override Script #'padding = #3
1156 More specific overrides are also possible. The next section
1157 discusses in depth how to figure out these statements for yourself.
1160 @node Constructing a tweak
1161 @subsection Constructing a tweak
1163 The general procedure of changing output, that is, entering
1167 \override Voice.Stem #'thickness = #3.0
1171 means that we have to determine these bits of information:
1174 @item the context: here @context{Voice}.
1175 @item the layout object: here @code{Stem}.
1176 @item the layout property: here @code{thickness}
1177 @item a sensible value: here @code{3.0}
1181 @cindex internal documentation
1182 @cindex finding graphical objects
1183 @cindex graphical object descriptions
1185 @cindex @code{\override}
1187 @cindex internal documentation
1189 We demonstrate how to glean this information from the notation manual
1190 and the program reference.
1192 The program reference is a set of HTML pages, which is part of the
1193 documentation package. On Unix systems, it is typically in
1194 @file{/usr/share/doc/lilypond}. If you have them, it is best to
1195 bookmark them in your webbrowser, because you will need them. They
1196 are also available on the web: go to the
1197 @uref{http://lilypond.org,LilyPond website}, click ``Documentation'',
1198 select the correct version, and then click ``Program reference.''
1200 If you have them, use the local HTML files. They will load faster,
1201 and they are exactly matched to LilyPond version installed.
1204 @node Navigating the program reference
1205 @subsection Navigating the program reference
1207 Suppose we want to move the fingering indication in the fragment
1210 @lilypond[fragment,relative=2,verbatim]
1216 If you visit the documentation of @code{Fingering} (in @ref{Fingering
1217 instructions}), you will notice that there is written:
1222 Program reference: @internalsref{FingerEvent} and @internalsref{Fingering}.
1226 This fragments points to two parts of the program reference: a page
1227 on @code{FingerEvent} and on @code{Fingering}.
1229 The page on @code{FingerEvent} describes the properties of the music
1230 expression for the input @code{-2}. The page contains many links
1231 forward. For example, it says
1234 Accepted by: @internalsref{Fingering_engraver},
1238 That link brings us to the documentation for the Engraver, the
1242 This engraver creates the following layout objects: @internalsref{Fingering}.
1245 In other words, once the @code{FingerEvent}s are interpreted, the
1246 @code{Fingering_engraver} plug-in will process them.
1247 The @code{Fingering_engraver} is also listed to create
1248 @internalsref{Fingering} objects,
1251 Lo and behold, that is also the
1252 second bit of information listed under @b{See also} in the Notation
1253 manual. By clicking around in the program reference, we can follow the
1254 flow of information within the program, either forward (like we did
1255 here), or backwards, following links like this:
1259 @item @internalsref{Fingering}:
1260 @internalsref{Fingering} objects are created by:
1261 @b{@internalsref{Fingering_engraver}}
1263 @item @internalsref{Fingering_engraver}:
1264 Music types accepted: @b{@internalsref{fingering-event}}
1265 @item @internalsref{fingering-event}:
1266 Music event type @code{fingering-event} is in Music objects of type
1267 @b{@internalsref{FingerEvent}}
1270 This path goes against the flow of information in the program: it
1271 starts from the output, and ends at the input event.
1273 The program reference can also be browsed like a normal document. It
1274 contains a chapter on
1276 @internalsref{Music-definitions},
1281 on @internalsref{Translation}, and the @internalsref{Backend}. Every
1282 chapter lists all the definitions used, and all properties that may be
1286 @node Layout interfaces
1287 @subsection Layout interfaces
1289 @internalsref{Fingering} is a layout object. Such an object is a
1290 symbol within the score. It has properties, which store numbers (like
1291 thicknesses and directions), but also pointers to related objects.
1292 A layout object is also called @emph{grob},
1294 which is short for Graphical Object.
1297 The page for @code{Fingering} lists the definitions for the
1298 @code{Fingering} object. For example, the page says
1301 @code{padding} (dimension, in staff space):
1306 which means that the number will be kept at a distance of at least 0.6
1310 Each layout object may have several functions as a notational or
1311 typographical element. For example, the Fingering object
1312 has the following aspects
1315 @item Its size is independent of the horizontal spacing, unlike slurs or beams
1317 @item It is a piece of text. Granted, it's usually a very short text.
1319 @item That piece of text is typeset with a font, unlike slurs or beams.
1320 @item Horizontally, the center of the symbol should be aligned to the
1321 center of the notehead
1322 @item Vertically, the symbol is placed next to the note and the staff.
1325 vertical position is also coordinated with other super and subscript
1329 Each of these aspects is captured in a so-called @emph{interface},
1330 which are listed on the @internalsref{Fingering} page at the bottom
1333 This object supports the following interfaces:
1334 @internalsref{item-interface},
1335 @internalsref{self-alignment-interface},
1336 @internalsref{side-position-interface}, @internalsref{text-interface},
1337 @internalsref{text-script-interface}, @internalsref{font-interface},
1338 @internalsref{finger-interface}, and @internalsref{grob-interface}.
1341 Clicking any of the links will take you to the page of the respective
1342 object interface. Each interface has a number of properties. Some of
1343 them are not user-serviceable (``Internal properties''), but others
1346 We have been talking of `the' @code{Fingering} object, but actually it
1347 does not amount to much. The initialization file
1348 @file{scm/define-grobs.scm} shows the soul of the `object',
1353 (print-function . ,Text_item::print)
1355 (staff-padding . 0.6)
1356 (self-alignment-X . 0)
1357 (self-alignment-Y . 0)
1358 (script-priority . 100)
1359 (font-encoding . number)
1361 (meta . ((interfaces . (finger-interface font-interface
1362 text-script-interface text-interface
1363 side-position-interface self-alignment-interface
1368 as you can see, @code{Fingering} is nothing more than a bunch of
1369 variable settings, and the webpage is directly generated from this
1372 @node Determining the grob property
1373 @subsection Determining the grob property
1376 Recall that we wanted to change the position of the @b{2} in
1378 @lilypond[fragment,relative=2,verbatim]
1384 Since the @b{2} is vertically positioned next to its note, we have to
1385 meddle with the interface associated with this positioning. This is
1386 done using @code{side-position-interface}. The page for this interface
1390 @code{side-position-interface}
1392 Position a victim object (this one) next to other objects (the
1393 support). The property @code{direction} signifies where to put the
1394 victim object relative to the support (left or right, up or down?)
1399 below this description, the variable @code{padding} is described as
1403 (dimension, in staff space)
1405 add this much extra space between objects that are next to each
1410 By increasing the value of @code{padding}, we can move away the
1411 fingering. The following command inserts 3 staff spaces of white
1412 between the note and the fingering:
1414 \once \override Fingering #'padding = #3
1417 Inserting this command before the Fingering object is created,
1418 i.e. before @code{c2}, yields the following result:
1420 @lilypond[relative=2,fragment,verbatim]
1421 \once \override Fingering
1429 In this case, the context for this tweak is @context{Voice}, which
1430 does not have to be specified for @code{\override}. This fact can
1431 also be deduced from the program reference, for the page for the
1432 @internalsref{Fingering_engraver} plug-in says
1435 Fingering_engraver is part of contexts: @dots{} @b{@internalsref{Voice}}
1438 @node Difficult tweaks
1439 @subsection Difficult tweaks
1441 There are two classes of difficult adjustments. First, when there are
1442 several of the same objects at one point, and you want to adjust only
1443 one. For example, if you want to change only one note head in a chord.
1445 In this case, the @code{\applyoutput} function must be used. The
1446 next example defines a Scheme function @code{set-position-font-size}
1447 that sets the @code{font-size} property, but only
1448 on objects that have @internalsref{note-head-interface} and are at the
1452 #(define ((set-position-font-size pos size) grob origin current)
1454 ((interfaces (ly:grob-property grob 'interfaces))
1455 (position (ly:grob-property grob 'staff-position)))
1458 ; is this a note head?
1459 (memq 'note-head-interface interfaces)
1461 ; is the Y coordinate right?
1465 (set! (ly:grob-property grob 'font-size) size))))
1469 \applyoutput #(set-position-font-size -2 4)
1475 A similar technique can be used for accidentals. In that case, the
1476 function should check for @code{accidental-interface}.
1478 Another difficult adjustment is the appearance of spanner objects,
1479 such as slur and tie. Initially, only one of these objects is created,
1480 and they can be adjust with the normal mechanism. However, in some
1481 cases the spanners cross line breaks. If this happens, these objects
1482 are cloned. A separate object is created for every system that it is
1483 in. These are clones of the original object and inherit all
1484 properties, including @code{\override}s.
1486 In other words, an @code{\override} always affects all pieces of a
1487 broken spanner. To change only one part of a spanner at a line break,
1488 it is necessary to hook into the formatting process. The
1489 @code{after-line-breaking-callback} property contains the Scheme procedure
1490 that is called after line breaks have been determined, and layout
1491 objects have been split over different systems.
1493 In the following example, we define a procedure
1494 @code{my-callback}. This procedure
1498 determines if we have been split across line breaks
1500 if yes, retrieves all the split objects
1502 checks if we are the last of the split objects
1504 if yes, it sets @code{extra-offset}.
1507 This procedure is installed into @internalsref{Tie}, so the last part
1508 of broken tie is translated up.
1511 @lilypond[verbatim,raggedright]
1512 #(define (my-callback grob)
1515 ; have we been split?
1516 (orig (ly:grob-original grob))
1518 ; if yes, get the split pieces (our siblings)
1519 (siblings (if (ly:grob? orig) (ly:spanner-broken-into orig) '() )))
1522 (if (and (>= (length siblings) 2)
1523 (eq? (car (last-pair siblings)) grob))
1524 (ly:grob-set-property! grob 'extra-offset '(-2 . 5))
1528 \override Tie #'after-line-breaking-callback =
1535 When applying this trick, the new @code{after-line-breaking-callback}
1536 should also call the old @code{after-line-breaking-callback}, if there
1537 is one. For example, if using this with @code{Slur},
1538 @code{Slur::after_line_breaking} should also be called.
1544 * Selecting font sizes::
1550 @node Selecting font sizes
1551 @subsection Selecting font sizes
1553 The most common thing to change about the appearance of fonts is their
1554 size. The font size of any context can be easily changed by setting
1555 the @code{fontSize} property for that context. Its value is a number:
1556 negative numbers make the font smaller, positive numbers larger. An
1557 example is given below:
1559 @lilypond[fragment,relative=1,verbatim]
1560 c4 c4 \set fontSize = #-3
1563 This command will set @code{font-size} (see below) in all layout
1564 objects in the current context. It does not change the size of
1565 variable symbols, such as beams or slurs.
1567 The font size is set by modifying the @code{font-size} property. Its
1568 value is a number indicating the size relative to the standard size.
1569 Each step up is an increase of approximately 12% of the font size. Six
1570 steps is exactly a factor two. The Scheme function @code{magstep}
1571 converts a @code{font-size} number to a scaling factor.
1573 LilyPond has fonts in different design sizes: the music fonts for
1574 smaller sizes are chubbier, while the text fonts are relatively wider.
1575 Font size changes are achieved by scaling the design size that is
1576 closest to the desired size.
1578 The @code{font-size} mechanism does not work for fonts selected
1579 through @code{font-name}. These may be scaled with
1580 @code{font-magnification}.
1583 One of the uses of @code{fontSize} is to get smaller symbols for cue
1584 notes. An elaborate example of those is in
1585 @inputfileref{input/test,cue-notes.ly}.
1588 @cindex @code{font-style}
1592 The following commands set @code{fontSize} for the current voice:
1594 @cindex @code{\tiny}
1596 @cindex @code{\small}
1598 @cindex @code{\normalsize}
1603 @cindex magnification
1607 @node Font selection
1608 @subsection Font selection
1610 Font selection for the standard fonts, @TeX{}'s Computer Modern fonts,
1611 can also be adjusted with a more fine-grained mechanism. By setting
1612 the object properties described below, you can select a different font;
1613 all three mechanisms work for every object that supports
1614 @code{font-interface}:
1618 @item @code{font-encoding}
1619 is a symbol that sets layout of the glyphs. Choices include @code{ec}
1620 for @TeX{} EC font encoding, @code{fetaBraces} (for piano staff
1621 braces), @code{fetaMusic} (the standard music font, including ancient
1622 glyphs), @code{fetaDynamic} (for dynamic signs) and @code{fetaNumber}
1623 for the number font.
1626 @item @code{font-family}
1627 is a symbol indicating the general class of the typeface. Supported are
1628 @code{roman} (Computer Modern), @code{sans}, and @code{typewriter}.
1630 @item @code{font-shape}
1631 is a symbol indicating the shape of the font, there are typically
1632 several font shapes available for each font family. Choices are
1633 @code{italic}, @code{caps}, and @code{upright}.
1635 @item @code{font-series}
1636 is a symbol indicating the series of the font. There are typically several
1637 font series for each font family and shape. Choices are @code{medium}
1642 Fonts selected in the way sketched above come from a predefined style
1645 The font used for printing a object can be selected by setting
1646 @code{font-name}, e.g.
1648 \override Staff.TimeSignature
1649 #'font-name = #"cmr17"
1653 Any font can be used, as long as it is available to @TeX{}. Possible
1654 fonts include foreign fonts or fonts that do not belong to the
1655 Computer Modern font family. The size of fonts selected in this way
1656 can be changed with the @code{font-magnification} property. For
1657 example, @code{2.0} blows up all letters by a factor 2 in both
1661 @cindex font magnification
1667 Init files: @file{ly/declarations-init.ly} contains hints how new
1668 fonts may be added to LilyPond.
1672 No style sheet is provided for other fonts besides the @TeX{}
1673 Computer Modern family.
1675 @cindex font selection
1676 @cindex font magnification
1677 @cindex @code{font-interface}
1681 @section Text markup
1686 @cindex typeset text
1688 LilyPond has an internal mechanism to typeset texts. You can access it
1689 with the keyword @code{\markup}. Within markup mode, you can enter texts
1690 similar to lyrics: simply enter them, surrounded by spaces:
1693 @lilypond[verbatim,fragment,relative=1]
1694 c1^\markup { hello }
1695 c1_\markup { hi there }
1696 c1^\markup { hi \bold there, is \italic anyone home? }
1699 @cindex font switching
1701 The markup in the example demonstrates font switching commands. The
1702 command @code{\bold} and @code{\italic} apply to the first following
1703 word only; enclose a set of texts with braces to apply a command
1706 \markup @{ \bold @{ hi there @} @}
1710 For clarity, you can also do this for single arguments, e.g.
1713 \markup { is \italic { anyone } home }
1716 @cindex font size, texts
1719 In markup mode you can compose expressions, similar to mathematical
1720 expressions, XML documents, and music expressions. The braces group
1721 notes into horizontal lines. Other types of lists also exist: you can
1722 stack expressions grouped with @code{<} and @code{>} vertically with
1723 the command @code{\column}. Similarly, @code{\center-align} aligns
1724 texts by their center lines:
1726 @lilypond[verbatim,fragment,relative=1]
1727 c1^\markup { \column < a bbbb c > }
1728 c1^\markup { \center-align < a bbbb c > }
1729 c1^\markup { \line < a b c > }
1733 Markups can be stored in variables, and these variables
1734 may be attached to notes, like
1736 allegro = \markup { \bold \large { Allegro } }
1737 { a^\allegro b c d }
1741 Some objects have alignment procedures of their own, which cancel out
1742 any effects of alignments applied to their markup arguments as a
1743 whole. For example, the @internalsref{RehearsalMark} is horizontally
1744 centered, so using @code{\mark \markup @{ \left-align .. @}} has no
1747 Similarly, for moving whole texts over notes with
1748 @code{\raise}, use the following trick:
1750 "" \raise #0.5 raised
1753 The text @code{raised} is now raised relative to the empty string
1754 @code{""} which is not visible. Alternatively, complete objects can
1755 be moved with layout properties such as @code{padding} and
1756 @code{extra-offset}.
1763 Init files: @file{scm/new-markup.scm}.
1768 Text layout is ultimately done by @TeX{}, which does kerning of
1769 letters. LilyPond does not account for kerning, so texts will be
1770 spaced slightly too wide.
1772 Syntax errors for markup mode are confusing.
1774 Markup texts cannot be used in the titling of the @code{\header}
1775 field. Titles are made by La@TeX{}, so La@TeX{} commands should be used
1783 * Overview of text markup commands::
1787 @subsection Text encoding
1789 Texts can be entered in different encodings. The encoding of the
1790 file can be set with @code{\encoding}.
1796 This command may be placed anywhere in the input file. The current
1797 encoding is passed as an extra argument to @code{\markup} commands,
1798 and is passed similarly to lyric syllables.
1800 If no @code{\encoding} has been specified, then the encoding is taken
1801 from the @code{\paper} block (or @code{\bookpaper}, if @code{\paper}
1802 does not specify encoding). The variable @code{inputencoding} may be
1803 set to a string or symbol specifying the encoding, e.g.
1807 inputencoding = "latin1"
1811 Normal strings, are unaffected by @code{\encoding}. This means that
1812 the following will usually not produce ba@ss{}tuba in the title.
1816 title = "Grazing cow"
1817 instrument = "Baßtuba"
1821 Rather, you should say
1823 instrument = \markup { Baßtuba }
1827 or set @code{inputencoding} in the @code{\bookpaper} block.
1829 There is a special encoding, called @code{TeX}. This encoding does not
1830 reencode text for the font used. Rather, it tries to guess the width
1831 of @TeX{} commands, such as @code{\"}. Strings encoded with @code{TeX}
1832 are passed to the output back-end verbatim.
1835 @cindex @code{\encoding}
1836 @cindex inputencoding
1837 @cindex @TeX{} commands in strings
1841 @subsection Nested scores
1843 It is possible to nest music inside markups, by adding a @code{\score}
1844 block to markup expression. Such a score must contain a @code{\paper}
1847 @lilypond[verbatim,raggedright]
1851 \relative { c4 d e f }
1861 @node Overview of text markup commands
1862 @subsection Overview of text markup commands
1864 @include markup-commands.tely
1868 @section Global layout
1870 The global layout determined by three factors: the page layout, the
1871 line breaks, and the spacing. These all influence each other. The
1872 choice of spacing determines how densely each system of music is set,
1873 which influences where line breaks are chosen, and thus
1874 ultimately how many pages a piece of music takes. This section
1875 explains how to tune the algorithm for spacing.
1877 Globally spoken, this procedure happens in three steps: first,
1878 flexible distances (``springs'') are chosen, based on durations. All
1879 possible line breaking combination are tried, and the one with the
1880 best results --- a layout that has uniform density and requires as
1881 little stretching or cramping as possible --- is chosen.
1883 After spacing and linebreaking, the systems are distributed across
1884 pages, taking into account the size of the page, and the size of the
1890 * Setting global staff size::
1891 * Vertical spacing::
1892 * Horizontal spacing::
1894 * Line length and line breaking::
1902 @node Setting global staff size
1903 @subsection Setting global staff size
1905 @cindex font size, setting
1906 @cindex staff size, setting
1907 @cindex @code{paper} file
1909 The Feta font provides musical symbols at eight different
1910 sizes. Each font is tuned for a different staff size: at a smaller size
1911 the font becomes heavier, to match the relatively heavier staff lines.
1912 The recommended font sizes are listed in the following table:
1914 @multitable @columnfractions .25 .25 .25 .25
1917 @tab @b{staff height (pt)}
1918 @tab @b{staff height (mm)}
1960 @c modern rental material ?
1964 These fonts are available in any sizes. The context property
1965 @code{fontSize} and the layout property @code{staff-space} (in
1966 @internalsref{StaffSymbol}) can be used to tune size for individual
1967 staves. The size of individual staves are relative to the global size,
1968 which can be set in the following manner:
1971 #(set-global-staff-size 14)
1974 This sets the global default size to 14pt staff height, and scales all
1979 This manual: @ref{Selecting font sizes}.
1984 * Vertical spacing::
1985 * Horizontal spacing::
1990 @node Vertical spacing
1991 @subsection Vertical spacing
1993 @cindex vertical spacing
1994 @cindex distance between staves
1995 @cindex staff distance
1996 @cindex between staves, distance
1997 @cindex staves per page
1998 @cindex space between staves
2000 The height of each system is determined automatically by LilyPond, to
2001 keep systems from bumping into each other, some minimum distances are
2002 set. By changing these, you can put staves closer together, and thus
2003 put more systems onto one page.
2005 Normally staves are stacked vertically. To make
2006 staves maintain a distance, their vertical size is padded. This is
2007 done with the property @code{minimumVerticalExtent}. It takes a pair
2008 of numbers, so if you want to make it smaller from its, then you could
2011 \set Staff.minimumVerticalExtent = #'(-4 . 4)
2013 This sets the vertical size of the current staff to 4 staff spaces on
2014 either side of the center staff line. The argument of
2015 @code{minimumVerticalExtent} is interpreted as an interval, where the
2016 center line is the 0, so the first number is generally negative. The
2017 staff can be made larger at the bottom by setting it to @code{(-6
2020 The piano staves are handled a little differently: to make cross-staff
2021 beaming work correctly, it is necessary that the distance between staves
2022 is fixed beforehand. This is also done with a
2023 @internalsref{VerticalAlignment} object, created in
2024 @internalsref{PianoStaff}. In this object the distance between the
2025 staves is fixed by setting @code{forced-distance}. If you want to
2026 override this, use a @code{\context} block as follows:
2031 \override VerticalAlignment #'forced-distance = #9
2036 This would bring the staves together at a distance of 9 staff spaces,
2037 measured from the center line of each staff.
2041 Internals: Vertical alignment of staves is handled by the
2042 @internalsref{VerticalAlignment} object.
2047 @node Horizontal spacing
2048 @subsection Horizontal Spacing
2050 The spacing engine translates differences in durations into
2051 stretchable distances (``springs'') of differing lengths. Longer
2052 durations get more space, shorter durations get less. The shortest
2053 durations get a fixed amount of space (which is controlled by
2054 @code{shortest-duration-space} in the @internalsref{SpacingSpanner} object).
2055 The longer the duration, the more space it gets: doubling a
2056 duration adds a fixed amount (this amount is controlled by
2057 @code{spacing-increment}) of space to the note.
2059 For example, the following piece contains lots of half, quarter, and
2060 8th notes, the eighth note is followed by 1 note head width (NHW).
2061 The quarter note is followed by 2 NHW, the half by 3 NHW, etc.
2062 @lilypond[fragment,verbatim,relative=1] c2 c4. c8 c4. c8 c4. c8 c8
2066 Normally, @code{spacing-increment} is set to 1.2, which is the
2067 width of a note head, and @code{shortest-duration-space} is set to
2068 2.0, meaning that the shortest note gets 2 NHW of space. For normal
2069 notes, this space is always counted from the left edge of the symbol, so
2070 the shortest notes are generally followed by one NHW of space.
2072 If one would follow the above procedure exactly, then adding a single
2073 32th note to a score that uses 8th and 16th notes, would widen up the
2074 entire score a lot. The shortest note is no longer a 16th, but a 32nd,
2075 thus adding 1 NHW to every note. To prevent this, the
2076 shortest duration for spacing is not the shortest note in the score,
2077 but the most commonly found shortest note. Notes that are even
2078 shorter this are followed by a space that is proportional to their
2079 duration relative to the common shortest note. So if we were to add
2080 only a few 16th notes to the example above, they would be followed by
2083 @lilypond[fragment,verbatim,relative=2]
2084 c2 c4. c8 c4. c16[ c] c4. c8 c8 c8 c4 c4 c4
2087 The most common shortest duration is determined as follows: in every
2088 measure, the shortest duration is determined. The most common short
2089 duration, is taken as the basis for the spacing, with the stipulation
2090 that this shortest duration should always be equal to or shorter than
2091 1/8th note. The shortest duration is printed when you run lilypond
2092 with @code{--verbose}. These durations may also be customized. If you
2093 set the @code{common-shortest-duration} in
2094 @internalsref{SpacingSpanner}, then this sets the base duration for
2095 spacing. The maximum duration for this base (normally 1/8th), is set
2096 through @code{base-shortest-duration}.
2098 @cindex @code{common-shortest-duration}
2099 @cindex @code{base-shortest-duration}
2100 @cindex @code{stem-spacing-correction}
2101 @cindex @code{spacing}
2103 In the Introduction it was explained that stem directions influence
2104 spacing. This is controlled with @code{stem-spacing-correction}
2105 property in @internalsref{NoteSpacing}, which are generated for every
2106 @internalsref{Voice} context. The @code{StaffSpacing} object
2107 (generated at @internalsref{Staff} context) contains the same property
2108 for controlling the stem/bar line spacing. The following example
2109 shows these corrections, once with default settings, and once with
2110 exaggerated corrections:
2112 @lilypond[raggedright]
2116 \override Staff.NoteSpacing #'stem-spacing-correction = #1.5
2117 \override Staff.StaffSpacing #'stem-spacing-correction = #1.5
2123 @cindex SpacingSpanner, overriding properties
2125 Properties of the @internalsref{SpacingSpanner} must be overridden
2126 from the @code{\paper} block, since the @internalsref{SpacingSpanner} is
2127 created before any property commands are interpreted.
2129 \paper @{ \context @{
2131 \override SpacingSpanner #'spacing-increment = #3.0
2138 Internals: @internalsref{SpacingSpanner}, @internalsref{NoteSpacing},
2139 @internalsref{StaffSpacing}, @internalsref{SeparationItem}, and
2140 @internalsref{SeparatingGroupSpanner}.
2144 Spacing is determined on a score wide basis. If you have a score that
2145 changes its character (measured in durations) halfway during the
2146 score, the part containing the longer durations will be spaced too
2149 There is no convenient mechanism to manually override spacing. The
2150 following work-around may be used to insert extra space into a score.
2152 \once \override Score.SeparationItem #'padding = #1
2155 No work-around exists for decreasing the amount of space.
2164 @subsection Line breaking
2167 @cindex breaking lines
2169 Line breaks are normally computed automatically. They are chosen such
2170 that lines look neither cramped nor loose, and that consecutive lines
2171 have similar density.
2173 Occasionally you might want to override the automatic breaks; you can
2174 do this by specifying @code{\break}. This will force a line break at
2175 this point. Line breaks can only occur at places where there are bar
2176 lines. If you want to have a line break where there is no bar line,
2177 you can force an invisible bar line by entering @code{\bar
2178 ""}. Similarly, @code{\noBreak} forbids a line break at a
2182 @cindex regular line breaks
2183 @cindex four bar music.
2185 For line breaks at regular intervals use @code{\break} separated by
2186 skips and repeated with @code{\repeat}:
2188 << \repeat unfold 7 @{
2189 s1 \noBreak s1 \noBreak
2190 s1 \noBreak s1 \break @}
2191 @emph{the real music}
2196 This makes the following 28 measures (assuming 4/4 time) be broken every
2197 4 measures, and only there.
2201 @code{\break}, and @code{\noBreak}.
2202 @cindex @code{\break}
2203 @cindex @code{\noBreak}
2207 Internals: @internalsref{BreakEvent}.
2209 @node Line length and line breaking
2210 @subsection Line length and line breaking
2213 @cindex breaking pages
2215 @cindex @code{indent}
2216 @cindex @code{linewidth}
2218 The most basic settings influencing the spacing are @code{indent} and
2219 @code{linewidth}. They are set in the @code{\paper} block. They
2220 control the indentation of the first line of music, and the lengths of
2223 If @code{raggedright} is set to true in the @code{\paper}
2224 block, then the lines are justified at their natural length. This
2225 useful for short fragments, and for checking how tight the natural
2229 @cindex vertical spacing
2231 The option @code{raggedlast} is similar to @code{raggedright}, but
2232 only affects the last line of the piece. No restrictions are put on
2233 that line. The result is similar to formatting paragraphs. In a
2234 paragraph, the last line simply takes its natural length.
2237 @node Multiple movements
2238 @subsection Multiple movements
2240 @cindex bibliographic information
2243 @cindex Engraved by LilyPond
2245 A document may contains multiple pieces of music. Examples of these
2246 are an etude book, or an orchestral part with multiple movements.
2247 Each movement is entered with a @code{\score} block,
2255 The movements are combined together to
2256 @code{\book} block is used to group the individual movements.
2270 The header for each piece of music can be put inside the @code{\score}
2271 block. The @code{piece} name from the header will be printed before
2272 each movement. The title for the entire book can be put inside the
2273 @code{\book}, but if it is not present, the @code{\header} which is at
2274 the top of the file is inserted.
2276 @cindex Engraved by LilyPond
2277 @cindex signature line
2282 title = "Eight miniatures"
2283 composer = "Igor Stravinsky"
2287 \header @{ piece = "Romanze" @}
2291 \header @{ piece = "Menuetto" @}
2298 Titles are created for each @code{\score} block, and over a
2301 The contents of the titles are taken from the @code{\header} blocks.
2302 The header block for a book supports the following
2305 The title of the music. Centered on top of the first page.
2307 Subtitle, centered below the title.
2309 Name of the poet, left flushed below the subtitle.
2311 Name of the composer, right flushed below the subtitle.
2313 Meter string, left flushed below the poet.
2315 Name of the opus, right flushed below the composer.
2317 Name of the arranger, right flushed below the opus.
2319 Name of the instrument, centered below the arranger.
2321 To whom the piece is dedicated.
2323 Name of the piece, left flushed below the instrument.
2326 This is a demonstration of the fields available,
2332 subtitle = "(and (the) subtitle)"
2333 subsubtitle = "Sub sub title"
2335 composer = "Composer"
2336 texttranslator = "Text Translator"
2338 arranger = "Arranger"
2339 instrument = "Instrument"
2360 Different fonts may be selected for each element, by using a
2361 @code{\markup}, e.g.
2365 title = \markup { \italic { The italic title } }
2369 A more advanced option is to change the Scheme functions
2370 @code{make-book-title} and @code{make-score-title} functions, defined
2371 in the @code{\bookpaper} of the @code{\book} block. These functions
2372 create a block of titling, given the information in the
2373 @code{\header}. The init file @file{ly/titling.scm} shows how the
2374 default format is created, and it may be used as a template for
2388 @subsection Page breaking
2390 The default page breaking may be overriden by inserting
2391 @code{\pageBreak} or @code{\noPageBreak} commands. These commands are
2392 analogous to @code{\break} and @code{\noBreak}. They should be
2393 inserted with a bar line. These commands force and forbid a page-break
2396 Page breaks are computed by the @code{page-breaking} function in the
2397 @code{\bookpaper} block.
2401 @cindex @code{\pageBreak}
2403 @cindex @code{\noPageBreak}
2407 @subsection Paper size
2411 @cindex @code{papersize}
2413 To change the paper size, there are two commands,
2415 #(set-default-paper-size "a4")
2417 #(set-paper-size "a4")
2420 The second one sets the size of the @code{\paper} block that it is in.
2424 @subsection Page layout
2428 @cindex header, page
2429 @cindex footer, page
2431 LilyPond will do page layout, setting margins and adding headers and
2432 footers to each page.
2434 The default layout responds to the following settings in the
2435 @code{\bookpaper} block
2440 The width of the page
2442 The height of the page
2444 Margin between header and top of the page
2446 Margin between footer and bottom of the page
2448 Margin between the left side of the page and the beginning of the music.
2450 The length of the paper line.
2452 Distance between top-most music system and the page header
2454 Distance between bottom-most music system and the page footer
2456 If set to true, systems will not be spread across the page.
2457 @item raggedlastbottom
2458 If set to true, systems will not be spread to fill the last page.
2466 raggedlastbottom = ##t
2470 You can also define these values in scheme. In that case @code{mm},
2471 @code{in}, @code{pt} and @code{cm} are variables defined in
2472 @file{book-paper-defaults.ly} with values in millimeters. That's why the
2473 value has to be multiplied in the example above.
2477 #(define bottommargin (* 2 cm))
2484 The option rightmargin is defined but doesn't set the right margin
2485 yet. The value for the right margin has to be defined adjusting the
2486 values of the leftmargin and linewidth.
2488 The default page header puts the page number and the @code{instrument}
2489 field from the @code{\header} block on a line.
2497 The default footer is empty, except for the first page, where it the
2498 @code{copyright} field from @code{\header} is inserted, and the last
2499 page, where @code{tagline} from @code{\header} is added. The default
2500 tagline is ``Engraved by LilyPond (@var{version})''.@footnote{Nicely
2501 printed parts are good PR for us, so please leave the tagline if you
2504 The header and footer are created by the functions @code{make-footer}
2505 and @code{make-header}, defined in @code{\bookpaper}. The default
2506 implementations are in @file{scm/page-layout.scm}.
2508 The following settings influence the header and footer layout.
2511 @item printpagenumber
2512 this boolean controls whether a pagenumber is printed.
2517 The page layout itself is done by two functions:
2518 @code{page-music-height} and @code{page-make-stencil}. The former
2519 tells the line-breaking algorithm how much space can be spent on a
2520 page, the latter creates the actual page given the system to put on it.
2525 Examples: @inputfileref{input/test/,page-breaks.ly}