1 @c -*- coding: utf-8; mode: texinfo; -*-
4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. For details, see the Contributors'
8 Guide, node Updating translation committishes..
16 Negative numbers are allowed:
17 > Are you sure? The following works well
19 > first-page-number = -2
21 > and prints page number -1 on the second page, for example.
24 In 5.2.1 the @refbugs (line 495 in spacing.itely on master) it
27 "@code{layout-set-staff-size} does not change the distance between
31 Could we add a sentence:
32 "Use instead the pair fontSize = #@var{N}
33 \override StaffSymbol #'staff-space = #(magstep
35 inside the Staff context to change the size of the font and the
37 staff lines accordingly."
39 Actually I found, that the @internalsref{StaffSymbol} at line 481
40 sends to an incomplete
41 documentation. The property staff-space is not explained here. I
42 thought Y-extent might be of
43 help, but it is in turn explained by x-space which again is
44 missing from the list. Who has the
45 knowledge to fix this?
49 http://code.google.com/p/lilypond/issues/detail?id=68
55 @chapter Spacing issues
57 The global paper layout is determined by three factors: the page layout, the
58 line breaks, and the spacing. These all influence each other. The
59 choice of spacing determines how densely each system of music is set.
60 This influences where line breaks are chosen, and thus ultimately, how
61 many pages a piece of music takes.
63 Globally speaking, this procedure happens in four steps: first,
64 flexible distances (@q{springs}) are chosen, based on durations. All
65 possible line breaking combinations are tried, and a @q{badness} score
66 is calculated for each. Then the height of each possible system is
67 estimated. Finally, a page breaking and line breaking combination is chosen
68 so that neither the horizontal nor the vertical spacing is too cramped
71 Settings which influence layout may be placed in two blocks.
72 The @code{\paper @{...@}} block is placed outside any
73 @code{\score @{...@}} blocks and contains settings that
74 relate to the entire document. The @code{\layout @{...@}}
75 block is placed within a @code{\score @{...@}} block and
76 contains settings for that particular score. If you have
77 only one @code{\score @{...@}} block the two have the same
78 effect. In general the commands shown in this chapter can
86 * Horizontal spacing::
87 * Fitting music onto fewer pages::
92 @section Paper and pages
94 This section deals with the boundaries that define the area
95 within which music can be printed.
104 @subsection Paper size
109 Two functions are available for changing the paper size:
110 @code{set-default-paper-size} and @code{set-paper-size}.
111 @code{set-default-paper-size} must be placed in the toplevel
112 scope, and @code{set-paper-size} must be placed in a @code{\paper}
116 #(set-default-paper-size "a4")
121 #(set-paper-size "a4")
126 @code{set-default-paper-size} sets the size of all pages, whereas
127 @code{set-paper-size} only sets the size of the pages that the
128 @code{\paper} block applies to. For example, if the @code{\paper}
129 block is at the top of the file, then it will apply the paper size
130 to all pages. If the @code{\paper} block is inside a
131 @code{\book}, then the paper size will only apply to that book.
133 Common paper sizes are available, including @code{a4},
134 @code{letter}, @code{legal}, and @code{11x17} (also known as
135 tabloid). Many more paper sizes are supported by default. For
136 details, see @file{scm/@/paper@/.scm}, and search for the
137 definition of @code{paper-alist}.
139 @c TODO add a new appendix for paper sizes (auto-generated) -pm
141 @warning{The default paper size is @code{a4}.}
143 Extra sizes may be added by editing the definition of
144 @code{paper-alist} in the initialization file
145 @file{scm/@/paper@/.scm}, however they will be overridden on a
151 If the symbol @code{'landscape} is supplied as an argument to
152 @code{set-default-paper-size}, pages will be rotated by 90
153 degrees, and wider line widths will be set accordingly.
156 #(set-default-paper-size "a6" 'landscape)
159 Setting the paper size will adjust a number of @code{\paper}
160 variables, such as margins. To use a particular paper size with
161 altered @code{\paper} variables, set the paper size before setting
167 @file{scm/@/paper@/.scm}.
173 @node Page formatting
174 @subsection Page formatting
178 Margins, headers, and footers and other layout variables are
179 automatically set according to the paper size.
181 Default margin values are accessible in
182 @file{ly/@/paper@/-defaults@/-init@/.ly}. They apply to the default
183 paper size (a4, unless specified differently) and are scaled
184 accordingly for other paper sizes.
186 This section lists and describes a number of paper variables that
190 * Fixed vertical dimensions::
191 * Flexible vertical dimensions::
192 * Horizontal dimensions::
193 * Other layout variables::
197 @node Fixed vertical dimensions
198 @unnumberedsubsubsec Fixed vertical dimensions
202 @funindex paper-height
204 The height of the page. Default: the height of the current paper
205 size. For details, see @ref{Paper size}.
210 The margin between the top of the page and the top of the
211 printable area. Default: @code{5\mm}.
214 @funindex bottom-margin
216 The margin between the bottom of the printable area and the bottom
217 of the page. Default: @code{6\mm}.
221 @node Flexible vertical dimensions
222 @unnumberedsubsubsec Flexible vertical dimensions
224 In most cases, it is preferable for the vertical distances between
225 certain items (such as margins, titles, systems, and separate
226 scores) to be flexible, so that they stretch and compress nicely
227 according to each situation. A number of @code{\paper} variables
228 (listed below) are available to fine-tune the stretching behavior
231 Note that the @code{\paper} variables discussed in this section do
232 not control the spacing of staves within individual systems.
233 Within-system spacing is controlled by grob properties, with
234 settings typically entered inside a @code{\score} or @code{layout}
235 block, and not inside a @code{\paper} block. See
236 @ref{Flexible vertical spacing within systems}.
239 @subsubheading Structure of spacing alists for @code{\paper} variables
241 Each of these variables is an alist (association list) containing
245 @item @code{padding} -- the minimum required amount of
246 unobstructed vertical whitespace between two items, measured in
247 staff-spaces. This can be thought of as the minimum height of an
248 unobstructed (invisible) rectangle that extends from the leftmost
249 to the rightmost point of the combined items.
251 @item @code{space} -- the default vertical distance, measured in
252 staff-spaces, between the @emph{reference points} of the two
253 items, when no collisions would result, and no stretching or
254 compressing is in effect. The reference point of a (title or
255 top-level) markup is its highest point, and the reference point of
256 a system is the vertical center of the nearest @code{StaffSymbol}
257 -- even if a non-staff line (such as a @code{Lyrics} context) is
258 in the way. Values for @code{space} that are less than either
259 @code{padding} or @code{minimum-distance} are not meaningful,
260 since the resulting distance will never be less than either
261 @code{padding} or @code{minimum-distance}.
263 @item @code{minimum-distance} -- the minimum required vertical
264 distance, measured in staff-spaces, between the reference points
265 of the two items, when compressing is in effect. Values for
266 @code{minimum-distance} that are less than @code{padding} are not
267 meaningful, since the resulting distance will never be less than
270 @item @code{stretchability} -- a unitless measure of the
271 dimension's relative propensity to stretch. If zero, the distance
272 will not stretch (unless collisions would result). When positive,
273 the significance of a particular dimension's @code{stretchability}
274 value lies only in its relation to the @code{stretchability}
275 values of the other dimensions. For example, if one dimension has
276 twice the @code{stretchability} of another, it will stretch twice
277 as easily. Values should be non-negative and finite. The value
278 @code{+inf.0} triggers a @code{programming_error} and is ignored,
279 but @code{1.0e7} can be used for an almost infinitely stretchable
280 spring. If unset, the default value is set to @code{space}. Note
281 that the dimension's propensity to @emph{compress} cannot be
282 directly set by the user and is equal to
283 (@code{space}@tie{}@minus{}@tie{}@code{minimum-distance}).
286 If a page has a ragged bottom, the resulting distance is the
291 @item @code{minimum-distance}, and
292 @item @code{padding} plus the smallest distance necessary to
293 eliminate collisions.
296 Specific methods for modifying alists are discussed in
297 @ref{Modifying alists}. The flexible vertical @code{\paper}
298 dimensions variables can only be set within a @code{\paper} block.
300 The following example demonstrates the two ways these alists can
301 be modified. The first declaration updates one key-value
302 individually, and the second complete re-defines the variable:
306 system-system-spacing #'space = #8
308 score-system-spacing =
311 (minimum-distance . 6)
312 (stretchability . 12))
316 The initialized default settings for these variables are defined
317 in @file{ly/paper-defaults-init.ly}.
320 @subsubheading Flexible vertical dimension @code{\paper} variables
322 The names of these variables follow the format
323 @code{@var{upper}-@var{lower}-spacing}, where @code{@var{upper}}
324 and @code{@var{lower}} are the items to be spaced. Each distance
325 is measured between the reference points of the two items (see the
326 description of the alist structure above). Note that in these
327 variable names, the term @q{@code{markup}} refers to both
328 @emph{title markups} (@code{bookTitleMarkup} or
329 @code{scoreTitleMarkup}) and @emph{top-level markups} (see
330 @ref{File structure}).
333 @item markup-system-spacing
334 @funindex markup-system-spacing
336 the distance between a (title or top-level) markup and the system
339 @item score-markup-spacing
340 @funindex score-markup-spacing
342 the distance between the last system of a score and the (title or
343 top-level) markup that follows it.
345 @item score-system-spacing
346 @funindex score-system-spacing
348 the distance between the last system of a score and the first
349 system of the score that follows it, when no (title or top-level)
350 markup exists between them.
352 @item system-system-spacing
353 @funindex system-system-spacing
355 the distance between two systems in the same score.
357 @item markup-markup-spacing
358 @funindex markup-markup-spacing
360 the distance between two (title or top-level) markups.
362 @item last-bottom-spacing
363 @funindex last-bottom-spacing
365 the distance from the last system or top-level markup on a page to
366 the bottom of the printable area (i.e. the top of the bottom
369 @item top-system-spacing
370 @funindex top-system-spacing
372 the distance from the top of the printable area (i.e. the bottom
373 of the top margin) to the first system on a page, when there is no
374 (title or top-level) markup between the two.
376 @item top-markup-spacing
377 @funindex top-markup-spacing
379 the distance from the top of the printable area (i.e. the bottom
380 of the top margin) to the first (title or top-level) markup on a
381 page, when there is no system between the two.
387 The header and footer are created by the functions
388 @code{make-footer} and @code{make-header}, defined in
389 @code{\paper}. The default implementations are in
390 @file{ly/paper-defaults.ly} and @file{ly/titling-init.ly}.
392 The page layout itself is done by two functions in the
393 @code{\paper} block, @code{page-music-height} and
394 @code{page-make-stencil}. The former tells the line-breaking
395 algorithm how much space can be spent on a page, the latter
396 creates the actual page given the system to put on it.
398 You can define @code{\paper} block values in Scheme. In that case
399 @code{mm}, @code{in}, @code{pt}, and @code{cm} are variables
400 defined in @file{paper-defaults.ly} with values in millimeters.
401 That is why the value @w{@code{2 cm}} must be multiplied in the
406 #(define bottom-margin (* 2 cm))
418 ragged-last-bottom = ##t
422 This second example centers page numbers at the bottom of every page.
426 print-page-number = ##t
427 print-first-page-number = ##t
428 oddHeaderMarkup = \markup \fill-line @{ " " @}
429 evenHeaderMarkup = \markup \fill-line @{ " " @}
430 oddFooterMarkup = \markup @{ \fill-line @{
431 \bold \fontsize #3 \on-the-fly #print-page-number-check-first
432 \fromproperty #'page:page-number-string @} @}
433 evenFooterMarkup = \markup @{ \fill-line @{
434 \bold \fontsize #3 \on-the-fly #print-page-number-check-first
435 \fromproperty #'page:page-number-string @} @}
441 @ref{Flexible vertical spacing within systems}.
447 @node Horizontal dimensions
448 @unnumberedsubsubsec Horizontal dimensions
451 There are a few variables that determine the horizontal dimensions
457 @funindex binding-offset
459 The amount @code{inner-margin} is increased
460 to make sure nothing will be hidden by the binding.
461 Works only with @code{two-sided} set to true. Default:
464 @item horizontal-shift
465 @funindex horizontal-shift
467 The amount that all systems (including titles and system
468 separators) are shifted to the right. Default: @code{0.0}.
473 The level of indentation for the first system in a score.
474 Default: @code{15\mm}.
477 @funindex inner-margin
479 The margin all pages have at the inner side if they are part
480 of a book. Works only with @code{two-sided} set to true.
481 Default: @code{10\mm}.
484 @funindex left-margin
486 The margin between the left edge of the page and the beginning of
487 each system. Default: @code{10\mm}.
492 The width of music systems. Default: @code{paper-width} minus
493 @code{left-margin} and @code{right-margin}.
496 @funindex outer-margin
498 The margin all pages have at the outer side if they are part
499 of a book. Works only with @code{two-sided} set to true.
500 Default: @code{20\mm}.
503 @funindex paper-width
505 The width of the page. Default: the width of the current paper
506 size. For details, see @ref{Paper size}.
509 @funindex right-margin
511 The margin between the right edge of the page and the end of
512 each system. Default: @code{10\mm}.
515 @funindex short-indent
517 The level of indentation for all systems in a score besides the
518 first system. Default: @code{0}.
522 If some values are not set, defaults will be taken. Their exact
523 value is adjusted, depending on the paper size specified. Currently,
524 the following values are affected by this scaling:
527 @item @var{left-margin}
528 @item @var{right-margin}
529 @item @var{top-margin}
530 @item @var{bottom-margin}
531 @item @var{head-separation}
532 @item @var{foot-separation}
534 @item @var{short-indent}
537 The settings for @code{line-width}, @code{left-margin},
538 @code{right-margin} and @code{paper-width} depend on
539 each other, but they do not have to be specified
548 In this example, only @code{left-margin} is set. The value for
549 @code{right-margin} will remain default, @code{line-width} is
550 calculated automatically.
558 Here @code{left-margin} and @code{right-margin} will be set
559 to the same value. Therefore, @code{line-width} is subtracted
560 from @code{paper-width} and divided by two. That means systems
561 are centered on the page, if only @code{line-width} is
564 Some checks occur to ensure the values are set correctly.
565 If the values do not match or systems would run off the page,
566 a warning is printed and default values are set.
577 These checks can be avoided by setting @code{check-consistency}
585 check-consistency = ##f
589 @warning{If @code{paper-width} is manually set, @code{line-width},
590 @code{left-margin}, @code{indent}, and @code{short-indent} may
591 have to be adjusted as well.}
599 @node Other layout variables
600 @unnumberedsubsubsec Other layout variables
602 These variables can be used to adjust page layout in general.
606 @item auto-first-page-number
607 @funindex auto-first-page-number
609 The page breaking algorithm is affected by the first page number
610 being odd or even. If set to true, the page breaking algorithm
611 will decide whether to start with an odd or even number. This
612 will result in the first page number remaining as is or being
613 increased by one. Default: @code{##f}.
617 TODO: this variable is used, but I don't know what it does. -pm
618 @item blank-after-score-page-force
619 @funindex blank-after-score-page-force
625 @item blank-last-page-force
626 @funindex blank-last-page-force
628 The penalty for ending the score on an odd-numbered page.
631 @item blank-page-force
632 @funindex blank-page-force
634 The penalty for having a blank page in the middle of a
635 score. This is not used by @code{ly:optimal-breaking} since it will
636 never consider blank pages in the middle of a score. Default:
639 @item check-consistency
640 @funindex check-consistency
642 If set to true, check whether @code{left-margin}, @code{right-margin} and
643 @code{line-width} fit each other. Also make sure that their combination
644 does not exceed the available @code{paper-width}. Default: @code{##t}.
646 @item first-page-number
647 @funindex first-page-number
649 The value of the page number on the first page. Default:
652 @item max-systems-per-page
653 @funindex max-systems-per-page
655 The maximum number of systems that will be placed on a page. This
656 is currently supported only by the @code{ly:optimal-breaking} algorithm.
659 @item min-systems-per-page
660 @funindex min-systems-per-page
662 The minimum number of systems that will be placed on a page. This
663 may cause pages to be overfilled if it is made too large. This is
664 currently supported only by the @code{ly:optimal-breaking} algorithm.
667 @item page-breaking-system-system-spacing
668 @funindex page-breaking-system-system-spacing
670 Tricks the page breaker into thinking that
671 @code{system-system-spacing} is set to something different than
672 it really is. For example, if
673 @code{page-breaking-system-system-spacing #'padding} is set to something
674 substantially larger than @code{system-system-spacing #'padding}, then the
675 page-breaker will put fewer systems on each page. Default: unset.
680 The number of pages to be used for a score. Default: unset.
682 @item page-spacing-weight
683 @funindex page-spacing-weight
685 The relative importance of page (vertical) spacing and line
686 (horizontal) spacing. High values will make page spacing more
687 important. Default: @code{#10}.
689 @item print-all-headers
690 @funindex print-all-headers
692 If set to true, this will print all headers for each \score in the
693 output. Normally only the piece and opus header variables are
694 printed. Default: @code{##f}.
696 @item print-first-page-number
697 @funindex print-first-page-number
699 If set to true, a page number is printed on the first page.
702 @item print-page-number
703 @funindex print-page-number
705 If set to false, page numbers are not printed. Default:
709 @funindex ragged-bottom
711 If set to true, systems will not spread vertically across the
712 page. This does not affect the last page. Default: @code{##f}.
714 This should be set to true for pieces that have only two or three
715 systems per page, for example orchestral scores.
718 @funindex ragged-last
720 If set to true, the last system in the score will not fill the
721 line width. Instead the last system ends at its natural
722 horizontal length. Default: @code{##f}.
724 @item ragged-last-bottom
725 @funindex ragged-last-bottom
727 If set to false, systems will spread vertically across the last
728 page. Default: @code{##t}.
730 Pieces that amply fill two pages or more should have this set to
733 It also affects the last page of book parts, ie parts of a book created
734 with @code{\bookpart} blocks.
737 @funindex ragged-right
739 If set to true, systems will not fill the line width. Instead,
740 systems end at their natural horizontal length. Default:
743 If the score has only one system, the default value is @code{##t}.
745 @item system-separator-markup
746 @funindex system-separator-markup
748 A markup object that is inserted between systems. This is often
749 used for orchestral scores. Default: unset.
751 The markup command @code{\slashSeparator} is provided as a sensible
754 @lilypond[quote,ragged-right]
755 #(set-default-paper-size "a6" 'landscape)
758 \relative c' { c1 \break c1 }
761 system-separator-markup = \slashSeparator
767 @funindex system-count
769 The number of systems to be used for a score.
772 @item systems-per-page
773 @funindex systems-per-page
775 The number of systems that should be placed on each page.
776 This is currently supported only by the @code{ly:optimal-breaking} algorithm.
783 @cindex binding gutter
785 If set to true, use @code{inner-margin}, @code{outer-margin} and
786 @code{binding-offset} to determine margins depending on whether
787 the page number is odd or even. This overrides @code{left-margin}
788 and @code{right-margin}. Default: @code{##f}.
800 The default page header puts the page number and the @code{instrument}
801 field from the @code{\header} block on a line.
803 The titles (from the @code{\header@{@}} section) are treated as a
804 system, so @code{ragged-bottom} and @code{ragged-last-bottom} will
805 add space between the titles and the first system of the score.
809 @section Music layout
812 * Setting the staff size::
817 @node Setting the staff size
818 @subsection Setting the staff size
820 @cindex font size, setting
821 @cindex staff size, setting
822 @funindex layout file
824 The default @strong{staff size} is set to 20 points.
825 This may be changed in two ways:
827 To set the staff size globally for all scores in a file (or
828 in a @code{book} block, to be precise), use @code{set-global-staff-size}.
831 #(set-global-staff-size 14)
835 This sets the global default size to 14pt staff height and scales all
838 To set the staff size individually for each score, use
843 #(layout-set-staff-size 15)
848 The Feta font provides musical symbols at eight different
849 sizes. Each font is tuned for a different staff size: at a smaller size
850 the font becomes heavier, to match the relatively heavier staff lines.
851 The recommended font sizes are listed in the following table:
854 @multitable @columnfractions .15 .2 .22 .2
857 @tab @b{staff height (pt)}
858 @tab @b{staff height (mm)}
900 @c modern rental material?
905 These fonts are available in any sizes. The context property
906 @code{fontSize} and the layout property @code{staff-space} (in
907 @rinternals{StaffSymbol}) can be used to tune the size for individual
908 staves. The sizes of individual staves are relative to the global size.
913 @ref{Selecting notation font size}.
921 @code{layout-set-staff-size} does not change the distance between the
926 @subsection Score layout
930 While @code{\paper} contains settings that relate to the page formatting
931 of the whole document, @code{\layout} contains settings for score-specific
938 \override VerticalAxisGroup #'minimum-Y-extent = #'(-6 . 6)
941 \override TextScript #'padding = #1.0
942 \override Glissando #'thickness = #3
950 @ref{Changing context default settings}.
962 * Optimal page breaking::
963 * Optimal page turning::
964 * Minimal page breaking::
966 * Using an extra voice for breaks::
971 @subsection Line breaking
974 @cindex breaking lines
976 Line breaks are normally determined automatically. They are chosen
977 so that lines look neither cramped nor loose, and consecutive
978 lines have similar density. Occasionally you might want to
979 override the automatic breaks; you can do this by specifying
980 @code{\break}. This will force a line break at this point. However,
981 line breaks can only occur at the end of @q{complete} bars, i.e.,
982 where there are no notes or tuplets left @q{hanging} over the bar
983 line. If you want to have a line break where there is no bar line,
984 you can force an invisible bar line by entering @code{\bar ""},
985 although again there must be no notes left hanging over in any of
986 the staves at this point, or it will be ignored.
988 The opposite command, @code{\noBreak}, forbids a line break at the
989 bar line where it is inserted.
991 The most basic settings influencing line spacing are @code{indent}
992 and @code{line-width}. They are set in the @code{\layout} block.
993 They control the indentation of the first line of music, and the
994 lengths of the lines.
996 If @code{ragged-right} is set to true in the @code{\layout} block,
997 then systems end at their natural horizontal length, instead of
998 being spread horizontally to fill the whole line. This is useful
999 for short fragments, and for checking how tight the natural
1002 @c TODO Check and add para on default for ragged-right
1004 The option @code{ragged-last} is similar to @code{ragged-right},
1005 but affects only the last line of the piece.
1017 @cindex regular line breaks
1018 @cindex four bar music.
1020 For line breaks at regular intervals use @code{\break} separated by
1021 skips and repeated with @code{\repeat}. For example, this would
1022 cause the following 28 measures (assuming 4/4 time) to be broken
1023 every 4 measures, and only there:
1026 << \repeat unfold 7 @{
1027 s1 \noBreak s1 \noBreak
1028 s1 \noBreak s1 \break @}
1029 @emph{the real music}
1034 A linebreaking configuration can be saved as a @code{.ly} file
1035 automatically. This allows vertical alignments to be stretched to
1036 fit pages in a second formatting run. This is fairly new and
1037 complicated. More details are available in
1050 Internals Reference:
1051 @rinternals{LineBreakEvent}.
1059 Line breaks can only occur if there is a @q{proper} bar line. A note
1060 which is hanging over a bar line is not proper, such as
1062 @lilypond[quote,ragged-right,relative=2,verbatim]
1063 c4 c2 << c2 {s4 \break } >> % this does nothing
1064 c2 c4 | % a break here would work
1065 c4 c2 c4 ~ \break % as does this break
1069 This can be avoided by removing the @code{Forbid_line_break_engraver}.
1070 Note that manually forced line breaks have to be added in parallel
1073 @lilypond[quote,ragged-right,verbatim]
1075 \remove Forbid_line_break_engraver
1077 c4 c2 << c2 {s4 \break } >> % now the break is allowed
1082 Similarly, line breaks are normally forbidden when beams cross bar
1083 lines. This behavior can be changed by setting
1084 @code{\override Beam #'breakable = ##t}.
1088 @subsection Page breaking
1090 The default page breaking may be overridden by inserting
1091 @code{\pageBreak} or @code{\noPageBreak} commands. These commands are
1092 analogous to @code{\break} and @code{\noBreak}. They should be
1093 inserted at a bar line. These commands force and forbid a page-break
1094 from happening. Of course, the @code{\pageBreak} command also forces
1097 The @code{\pageBreak} and @code{\noPageBreak} commands may also be
1098 inserted at top-level, between scores and top-level markups.
1100 There are also analogous settings to @code{ragged-right} and
1101 @code{ragged-last} which have the same effect on vertical spacing:
1102 @code{ragged-bottom} and @code{ragged-last-bottom}. If set to
1103 @code{##t} the systems on all pages or just the last page
1104 respectively will not be justified vertically.
1106 For more details see @ref{Vertical spacing}.
1108 Page breaks are computed by the @code{page-breaking} function. LilyPond
1109 provides three algorithms for computing page breaks,
1110 @code{ly:optimal-breaking}, @code{ly:page-turn-breaking} and
1111 @code{ly:minimal-breaking}. The default is @code{ly:optimal-breaking},
1112 but the value can be changed in the @code{\paper} block:
1116 #(define page-breaking ly:page-turn-breaking)
1122 When a book has many scores and pages, the page breaking problem may be
1123 difficult to solve, requiring large processing time and memory. To ease
1124 the page breaking process, @code{\bookpart} blocks are used to divide
1125 the book into several parts: the page breaking occurs separately on each
1126 part. Different page breaking functions may also be used in different
1132 subtitle = "Preface"
1135 %% In a part consisting mostly of text,
1136 %% ly:minimal-breaking may be preferred
1137 #(define page-breaking ly:minimal-breaking)
1139 \markup @{ @dots{} @}
1143 %% In this part, consisting of music, the default optimal
1144 %% page breaking function is used.
1146 subtitle = "First movement"
1148 \score @{ @dots{} @}
1155 @funindex \pageBreak
1157 @funindex \noPageBreak
1158 @code{\noPageBreak}.
1167 @node Optimal page breaking
1168 @subsection Optimal page breaking
1170 @funindex ly:optimal-breaking
1172 The @code{ly:optimal-breaking} function is LilyPond's default method of
1173 determining page breaks. It attempts to find a page breaking that minimizes
1174 cramping and stretching, both horizontally and vertically. Unlike
1175 @code{ly:page-turn-breaking}, it has no concept of page turns.
1183 @node Optimal page turning
1184 @subsection Optimal page turning
1186 @funindex ly:page-turn-breaking
1188 Often it is necessary to find a page breaking configuration so that there is
1189 a rest at the end of every second page. This way, the musician can turn the
1190 page without having to miss notes. The @code{ly:page-turn-breaking} function
1191 attempts to find a page breaking minimizing cramping and stretching, but with
1192 the additional restriction that it is only allowed to introduce page turns
1193 in specified places.
1195 There are two steps to using this page breaking function. First, you
1196 must enable it in the @code{\paper} block, as explained in @ref{Page
1197 breaking}. Then you must tell the function where you would like to allow
1200 There are two ways to achieve the second step. First, you can specify each
1201 potential page turn manually, by inserting @code{\allowPageTurn} into your
1202 input file at the appropriate places.
1204 If this is too tedious, you can add a @code{Page_turn_engraver} to a Staff or
1205 Voice context. The @code{Page_turn_engraver} will scan the context for
1206 sections without notes (note that it does not scan for rests; it scans for
1207 the absence of notes. This is so that single-staff polyphony with rests in one
1208 of the parts does not throw off the @code{Page_turn_engraver}). When it finds
1209 a sufficiently long section without notes, the @code{Page_turn_engraver} will
1210 insert an @code{\allowPageTurn} at the final bar line in that section, unless
1211 there is a @q{special} bar line (such as a double bar), in which case the
1212 @code{\allowPageTurn} will be inserted at the final @q{special} bar line in
1215 @funindex minimumPageTurnLength
1216 The @code{Page_turn_engraver} reads the context property
1217 @code{minimumPageTurnLength} to determine how long a note-free section must
1218 be before a page turn is considered. The default value for
1219 @code{minimumPageTurnLength} is @code{#(ly:make-moment 1 1)}. If you want
1220 to disable page turns, you can set it to something very large.
1223 \new Staff \with @{ \consists "Page_turn_engraver" @}
1226 R1 | % a page turn will be allowed here
1228 \set Staff.minimumPageTurnLength = #(ly:make-moment 5 2)
1229 R1 | % a page turn will not be allowed here
1231 R1*2 | % a page turn will be allowed here
1236 @funindex minimumRepeatLengthForPageTurn
1237 The @code{Page_turn_engraver} detects volta repeats. It will only allow a page
1238 turn during the repeat if there is enough time at the beginning and end of the
1239 repeat to turn the page back. The @code{Page_turn_engraver} can also disable
1240 page turns if the repeat is very short. If you set the context property
1241 @code{minimumRepeatLengthForPageTurn} then the @code{Page_turn_engraver} will
1242 only allow turns in repeats whose duration is longer than this value.
1244 The page turning commands, @code{\pageTurn}, @code{\noPageTurn} and
1245 @code{\allowPageTurn}, may also be used at top-level, between scores and
1252 @funindex \noPageTurn
1254 @funindex \allowPageTurn
1255 @code{\allowPageTurn}.
1266 There should only be one @code{Page_turn_engraver} in a score. If there is more
1267 than one, they will interfere with each other.
1270 @node Minimal page breaking
1271 @subsection Minimal page breaking
1273 @funindex ly:minimal-breaking
1275 The @code{ly:minimal-breaking} function performs minimal computations to
1276 calculate the page breaking: it fills a page with as many systems as
1277 possible before moving to the next one. Thus, it may be preferred for
1278 scores with many pages, where the other page breaking functions could be
1279 too slow or memory demanding, or a lot of texts. It is enabled using:
1283 #(define page-breaking ly:minimal-breaking)
1293 @node Explicit breaks
1294 @subsection Explicit breaks
1296 Lily sometimes rejects explicit @code{\break} and @code{\pageBreak}
1297 commands. There are two commands to override this behavior:
1300 \override NonMusicalPaperColumn #'line-break-permission = ##f
1301 \override NonMusicalPaperColumn #'page-break-permission = ##f
1304 When @code{line-break-permission} is overridden to false, Lily will insert
1305 line breaks at explicit @code{\break} commands and nowhere else. When
1306 @code{page-break-permission} is overridden to false, Lily will insert
1307 page breaks at explicit @code{\pageBreak} commands and nowhere else.
1309 @lilypond[quote,verbatim]
1318 \repeat unfold 2 { c'8 c'8 c'8 c'8 } \break
1319 \repeat unfold 4 { c'8 c'8 c'8 c'8 } \break
1320 \repeat unfold 6 { c'8 c'8 c'8 c'8 } \break
1321 \repeat unfold 8 { c'8 c'8 c'8 c'8 } \pageBreak
1322 \repeat unfold 8 { c'8 c'8 c'8 c'8 } \break
1323 \repeat unfold 6 { c'8 c'8 c'8 c'8 } \break
1324 \repeat unfold 4 { c'8 c'8 c'8 c'8 } \break
1325 \repeat unfold 2 { c'8 c'8 c'8 c'8 }
1330 \override NonMusicalPaperColumn #'line-break-permission = ##f
1331 \override NonMusicalPaperColumn #'page-break-permission = ##f
1343 @node Using an extra voice for breaks
1344 @subsection Using an extra voice for breaks
1346 Line- and page-breaking information usually appears within note entry directly.
1351 \repeat unfold 2 @{ c'4 c'4 c'4 c'4 @}
1353 \repeat unfold 3 @{ c'4 c'4 c'4 c'4 @}
1358 This makes @code{\break} and @code{\pageBreak} commands easy to enter but mixes
1359 music entry with information that specifies how music should lay out
1360 on the page. You can keep music entry and line- and page-breaking
1361 information in two separate places by introducing an extra voice to
1362 contain the breaks. This extra voice
1363 contains only skips together with @code{\break}, @code{pageBreak} and other
1364 breaking layout information.
1366 @lilypond[quote,verbatim]
1376 \repeat unfold 2 { c'4 c'4 c'4 c'4 }
1377 \repeat unfold 3 { c'4 c'4 c'4 c'4 }
1378 \repeat unfold 6 { c'4 c'4 c'4 c'4 }
1379 \repeat unfold 5 { c'4 c'4 c'4 c'4 }
1385 This pattern becomes especially helpful when overriding
1386 @code{line-break-system-details} and the other useful but long properties of
1387 @code{NonMusicalPaperColumnGrob}, as explained in @ref{Vertical spacing}.
1389 @lilypond[quote,verbatim]
1393 \overrideProperty "Score.NonMusicalPaperColumn"
1394 #'line-break-system-details #'((Y-offset . 0))
1397 \overrideProperty "Score.NonMusicalPaperColumn"
1398 #'line-break-system-details #'((Y-offset . 35))
1401 \overrideProperty "Score.NonMusicalPaperColumn"
1402 #'line-break-system-details #'((Y-offset . 70))
1405 \overrideProperty "Score.NonMusicalPaperColumn"
1406 #'line-break-system-details #'((Y-offset . 105))
1410 \repeat unfold 2 { c'4 c'4 c'4 c'4 }
1411 \repeat unfold 3 { c'4 c'4 c'4 c'4 }
1412 \repeat unfold 6 { c'4 c'4 c'4 c'4 }
1413 \repeat unfold 5 { c'4 c'4 c'4 c'4 }
1422 @ref{Vertical spacing}.
1428 @node Vertical spacing
1429 @section Vertical spacing
1431 @cindex vertical spacing
1432 @cindex spacing, vertical
1434 Vertical spacing is controlled by three things: the amount of
1435 space available (i.e., paper size and margins), the amount of
1436 space between systems, and the amount of space between
1437 staves inside a system.
1440 * Flexible vertical spacing within systems::
1441 * Explicit staff and system positioning::
1442 * Vertical collision avoidance::
1446 @node Flexible vertical spacing within systems
1447 @subsection Flexible vertical spacing within systems
1449 @cindex distance between staves
1450 @cindex staff distance
1451 @cindex space between staves
1452 @cindex space inside systems
1454 Three separate mechanisms control the flexible vertical spacing
1455 within systems, one for each of the following categories:
1458 @item @emph{ungrouped staves},
1459 @item @emph{grouped staves} (staves within a staff-group such as
1460 @code{ChoirStaff}, etc.), and
1461 @item @emph{non-staff lines} (such as @code{Lyrics},
1462 @code{ChordNames}, etc.).
1465 The height of each system is determined in two steps. First, all
1466 of the staves are spaced according to the amount of space
1467 available. Then, the non-staff lines are distributed between the
1470 Note that the spacing mechanisms discussed in this section only
1471 control the vertical spacing of staves and non-staff lines within
1472 individual systems. The vertical spacing between separate
1473 systems, scores, markups, and margins is controlled by
1474 @code{\paper} variables, which are discussed in
1475 @ref{Flexible vertical dimensions}.
1478 * Within-system spacing properties::
1479 * Spacing of ungrouped staves::
1480 * Spacing of grouped staves::
1481 * Spacing of non-staff lines::
1485 @node Within-system spacing properties
1486 @unnumberedsubsubsec Within-system spacing properties
1488 The within-system vertical spacing mechanisms are controlled by
1489 two sets of grob properties. The first set is associated with the
1490 @code{VerticalAxisGroup} grob, which is created by all staves and
1491 non-staff lines. The second set is associated with the
1492 @code{StaffGrouper} grob, which can be created by staff-groups,
1493 but only if explicitly called. These properties are described
1494 individually at the end of this section.
1496 Except for the @code{staff-affinity} property (of the
1497 @code{VerticalAxisGroup} grob), each of these grob properties is
1498 stored as an alist (association list), and each uses the same
1499 alist structure as the @code{\paper} spacing variables discussed
1500 in @ref{Flexible vertical dimensions}.
1502 The @emph{reference point} for a staff is the vertical center of
1503 its @code{StaffSymbol} (i.e. the middle line if @code{line-count}
1504 is odd; the middle space if @code{line-count} is even).
1506 The reference points for individual non-staff lines are given in
1507 the following table:
1509 @multitable {Non-staff line} {Reference point}
1510 @headitem Non-staff line @tab Reference point
1511 @item @code{ChordNames} @tab baseline
1512 @item @code{NoteNames} @tab baseline
1513 @item @code{Lyrics} @tab baseline
1514 @item @code{Dynamics} @tab vertical center
1515 @item @code{FiguredBass} @tab highest point
1516 @item @code{FretBoards} @tab top line
1519 In the following image, horizontal lines indicate the positions
1520 of these reference points:
1522 @lilypond[quote,noragged-right,line-width=110\mm]
1523 #(define zero-space '((padding . -inf.0) (space . 0)))
1525 alignToZero = \with {
1526 \override VerticalAxisGroup #'nonstaff-relatedstaff-spacing = #zero-space
1527 \override VerticalAxisGroup #'nonstaff-nonstaff-spacing = #zero-space
1529 lowerCaseChords = \with {
1530 chordNameLowercaseMinor = ##t
1532 staffAffinityDown = \with {
1533 \override VerticalAxisGroup #'staff-affinity = #DOWN
1536 #(define-music-function
1537 (parser location context)
1539 #{ s1*0^\markup { \typewriter $context } #})
1542 \context { \Dynamics \alignToZero }
1543 \context { \FiguredBass \alignToZero }
1544 \context { \Lyrics \alignToZero }
1545 \context { \NoteNames \alignToZero }
1546 \context { \ChordNames \alignToZero \lowerCaseChords }
1547 \context { \FretBoards \alignToZero \staffAffinityDown }
1549 \override BarLine #'stencil = ##f
1550 \override DynamicText #'self-alignment-X = #-1
1551 \override FretBoard #'X-offset = #1.75
1552 \override TextScript #'minimum-Y-extent = #'(-2 . 3)
1553 \override TimeSignature #'stencil = ##f
1557 %% These contexts have reference points at the baseline:
1558 %% ChordNames, NoteNames, and Lyrics
1560 \new ChordNames { \chords { g1:m } }
1561 \new NoteNames { s1 | g1 | }
1562 \new RhythmicStaff {
1563 \set RhythmicStaff.instrumentName = #"baseline "
1565 \labelContext "ChordNames" s1 |
1566 \labelContext "NoteNames" s1 |
1567 \labelContext "Lyrics" s1 |
1569 \new Lyrics { \lyrics { \skip 1*2 | ghijk1 | } }
1572 %% The reference point for Dynamics is its vertical center
1574 \new RhythmicStaff {
1575 \set RhythmicStaff.instrumentName = #"vertical center "
1576 \labelContext "Dynamics" s1*3
1578 \new Dynamics { s2\mp s\fp }
1581 %% The reference point for FiguredBass is its highest point
1583 \new RhythmicStaff {
1584 \set RhythmicStaff.instrumentName = #"highest point "
1585 \labelContext "FiguredBass" s1
1587 \new FiguredBass { \figuremode { <6 5>1 } }
1590 %% The reference point for FretBoards is the top line
1591 \include "predefined-guitar-fretboards.ly"
1593 \new FretBoards { \chordmode { e1 } }
1594 \new RhythmicStaff {
1595 \set RhythmicStaff.instrumentName = #"top line "
1596 \labelContext "FretBoards " s1
1601 Specific methods for modifying alists are discussed in
1602 @ref{Modifying alists}. Grob properties should be adjusted with
1603 an @code{\override} inside a @code{\score} or @code{\layout}
1604 block, and not inside a @code{\paper} block.
1606 The following example demonstrates the two ways these alists can
1607 be modified. The first declaration updates one key-value
1608 individually, and the second completely re-defines the property:
1612 \override VerticalAxisGroup #'staff-staff-spacing #'space = #10
1616 \override VerticalAxisGroup #'staff-staff-spacing =
1619 (minimum-distance . 9)
1620 (stretchability . 10))
1624 To change any spacing settings globally, put them in the
1625 @code{\layout} block:
1631 \override VerticalAxisGroup #'staff-staff-spacing #'space = #10
1636 The global defaults for the following grob properties are defined
1637 in @file{scm/define-grobs.scm}:
1640 @item @code{StaffGrouper} properties:
1642 @item @code{staff-staff-spacing}
1643 @item @code{staffgroup-staff-spacing}
1645 @item @code{VerticalAxisGroup} properties:
1647 @item @code{default-staff-staff-spacing}
1648 @item @code{nonstaff-unrelatedstaff-spacing}
1652 Default overrides for specific types of non-staff lines can be
1653 found in the relevant context definitions in
1654 @file{ly/engraver-init.ly}.
1657 @subsubheading Properties of the @code{VerticalAxisGroup} grob
1659 @code{VerticalAxisGroup} properties are typically adjusted with an
1660 @code{\override} at the @code{Staff} level (or equivalent).
1663 @item staff-staff-spacing
1664 The distance between the current staff and the staff just below it
1665 in the same system, even if one or more non-staff lines (such as
1666 @code{Lyrics}) are placed between the two staves. Does not apply
1667 to the bottom staff of a system. For a grouped staff, if
1668 @code{staff-staff-spacing} is set, it will be used instead of the
1669 relevant @code{StaffGrouper} property
1670 (@code{staff-staff-spacing} or @code{staffgroup-staff-spacing}).
1671 If unset, the @code{default-staff-staff-spacing} property is used,
1672 unless the staff is part of a staff-group and the appropriate
1673 @code{StaffGrouper} property is set.
1675 @item default-staff-staff-spacing
1676 The value to use for @code{staff-staff-spacing} when it is unset,
1677 for ungrouped staves and for grouped staves that do not have the
1678 relevant @code{StaffGrouper} property set
1679 (@code{staff-staff-spacing} or @code{staffgroup-staff-spacing}).
1681 @item staff-affinity
1682 The direction of the staff to use for spacing the current
1683 non-staff line. Choices are @code{UP}, @code{DOWN}, and
1684 @code{CENTER}. If @code{CENTER}, the non-staff line will be
1685 placed equidistant between the two nearest staves on either side,
1686 unless collisions or other spacing constraints prevent this.
1687 Adjacent non-staff lines should have non-increasing
1688 @code{staff-affinity} from top to bottom, e.g. a non-staff line
1689 set to @code{UP} should not immediately follow one that is set to
1690 @code{DOWN}. Non-staff lines at the top of a system should use
1691 @code{DOWN}; those at the bottom should use @code{UP}. Setting
1692 @code{staff-affinity} to @code{#f} will cause a non-staff line to
1693 be treated as a staff. Conversely, setting @code{staff-affinity}
1694 (to @code{UP}, @code{DOWN}, or @code{CENTER}) for a staff will
1695 cause it to be treated as a non-staff line.
1697 @c TODO: verify last clause below ("even if other...")
1699 @item nonstaff-relatedstaff-spacing
1700 The distance between the current non-staff line and the nearest
1701 staff in the direction of @code{staff-affinity}, if there are no
1702 non-staff lines between the two, and @code{staff-affinity} is
1703 either @code{UP} or @code{DOWN}. If @code{staff-affinity} is
1704 @code{CENTER}, then @code{nonstaff-relatedstaff-spacing} is used for the
1705 nearest staves on @emph{both} sides, even if other non-staff lines
1706 appear between the current one and either of the staves.
1708 @item nonstaff-nonstaff-spacing
1709 The distance between the current non-staff line and the next
1710 non-staff line in the direction of @code{staff-affinity}, if both
1711 are on the same side of the reference staff, and
1712 @code{staff-affinity} is either @code{UP} or @code{DOWN}.
1714 @item nonstaff-unrelatedstaff-spacing
1715 The distance between the current non-staff line and the staff in
1716 the opposite direction from @code{staff-affinity}, if there are no
1717 other non-staff lines between the two, and @code{staff-affinity}
1718 is either @code{UP} or @code{DOWN}. This can be used, for
1719 example, to require a minimum amount of padding between a
1720 @code{Lyrics} line and the staff to which it does not belong.
1724 @subsubheading Properties of the @code{StaffGrouper} grob
1726 @code{StaffGrouper} properties are typically adjusted with an
1727 @code{\override} at the @code{StaffGroup} level (or equivalent).
1730 @item staff-staff-spacing
1731 The distance between consecutive staves within the current
1732 staff-group. The @code{staff-staff-spacing} property of an
1733 individual staff's @code{VerticalAxisGroup} grob will be used
1734 instead for any staves in the staff-group that have it set. If
1735 both @code{staff-staff-spacing} and @code{staff-staff-spacing}
1736 are unset, the @code{default-staff-staff-spacing} property of each
1737 staff's @code{VerticalAxisGroup} grob is used.
1739 @item staffgroup-staff-spacing
1740 The distance between the last staff of the current staff-group and
1741 the staff just below it in the same system, even if one or more
1742 non-staff lines (such as @code{Lyrics}) exist between the two
1743 staves. Does not apply to the bottom staff of a system. The
1744 @code{staff-staff-spacing} property of an individual staff's
1745 @code{VerticalAxisGroup} grob will be used instead for any staves
1746 in the staff-group that have it set. If both
1747 @code{staffgroup-staff-spacing} and @code{staff-staff-spacing} are
1748 unset, the @code{default-staff-staff-spacing} property of each
1749 staff's @code{VerticalAxisGroup} grob is used.
1753 @node Spacing of ungrouped staves
1754 @unnumberedsubsubsec Spacing of ungrouped staves
1756 @emph{Staves} (such as @code{Staff}, @code{DrumStaff},
1757 @code{TabStaff}, etc.) are contexts that can contain one or more
1758 voice contexts, but cannot contain any other staves.
1760 The following properties affect the spacing of @emph{ungrouped}
1764 @item @code{VerticalAxisGroup} properties:
1766 @item @code{staff-staff-spacing}
1770 These grob properties are described individually above; see
1771 @ref{Within-system spacing properties}.
1773 Additional properties are involved for staves that are part of a
1774 staff-group; see @ref{Spacing of grouped staves}.
1776 The following example shows how the @code{staff-staff-spacing}
1777 property can affect the spacing of ungrouped staves:
1779 @lilypond[verbatim,quote,staffsize=16]
1783 \override VerticalAxisGroup #'staff-staff-spacing =
1786 (minimum-distance . 7))
1791 % The very low note here needs more room than 'space can
1792 % provide, so the distance between this staff and the next is
1793 % determined by 'padding.
1794 \new Staff { b,2 r | }
1796 % Here, 'space provides enough room, and there is no need to
1797 % compress the space (towards 'minimum-distance) to make room
1798 % for anything else on the page, so the distance between this
1799 % staff and the next is determined by 'space.
1800 \new Staff { \clef bass g2 r | }
1802 % By setting 'padding to a negative value, staves can be made to
1803 % collide. The lowest acceptable value for 'space is 0.
1805 \override VerticalAxisGroup #'staff-staff-spacing =
1808 } { \clef bass g2 r | }
1809 \new Staff { \clef bass g2 r | }
1814 @node Spacing of grouped staves
1815 @unnumberedsubsubsec Spacing of grouped staves
1817 In orchestral and other large scores, it is common to place staves
1818 in groups. The space between groups is typically larger than the
1819 space between staves of the same group.
1821 @emph{Staff-groups} (such as @code{StaffGroup}, @code{ChoirStaff},
1822 etc.) are contexts that can contain one or more staves
1825 The following properties affect the spacing of staves inside
1829 @item @code{VerticalAxisGroup} properties:
1831 @item @code{staff-staff-spacing}
1832 @item @code{default-staff-staff-spacing}
1834 @item @code{StaffGrouper} properties:
1836 @item @code{staff-staff-spacing}
1837 @item @code{staffgroup-staff-spacing}
1841 These grob properties are described individually above; see
1842 @ref{Within-system spacing properties}.
1844 The following example shows how properties of the
1845 @code{StaffGrouper} grob can affect the spacing of grouped staves:
1847 @lilypond[verbatim,quote,staffsize=16]
1851 \override StaffGrouper #'staff-staff-spacing #'padding = #0
1852 \override StaffGrouper #'staff-staff-spacing #'space = #1
1857 \new PianoStaff \with {
1858 \override StaffGrouper #'staffgroup-staff-spacing #'space = #20
1872 @node Spacing of non-staff lines
1873 @unnumberedsubsubsec Spacing of non-staff lines
1875 @emph{Non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
1876 etc.) are contexts whose layout objects are engraved like staves
1877 (i.e. in horizontal lines within systems). Specifically,
1878 non-staff lines are non-staff contexts that create the
1879 @code{VerticalAxisGroup} layout object.
1881 The following properties affect the spacing of non-staff lines:
1884 @item @code{VerticalAxisGroup} properties:
1886 @item @code{staff-affinity}
1887 @item @code{nonstaff-relatedstaff-spacing}
1888 @item @code{nonstaff-nonstaff-spacing}
1889 @item @code{nonstaff-unrelatedstaff-spacing}
1893 These grob properties are described individually above; see
1894 @ref{Within-system spacing properties}.
1896 The following example shows how the
1897 @code{nonstaff-nonstaff-spacing} property can affect the spacing
1898 of consecutive non-staff lines. Here, by setting the
1899 @code{stretchability} key to a very high value, the lyrics are
1900 able to stretch much more than usual:
1902 @lilypond[verbatim,quote,staffsize=16]
1906 \override VerticalAxisGroup
1907 #'nonstaff-nonstaff-spacing #'stretchability = #1000
1914 \override VerticalAxisGroup #'staff-staff-spacing = #'((space . 30))
1917 \override VerticalAxisGroup #'staff-affinity = #UP
1920 \override VerticalAxisGroup #'staff-affinity = #CENTER
1921 } \lyricmode { center }
1923 \override VerticalAxisGroup #'staff-affinity = #DOWN
1924 } \lyricmode { down }
1932 @file{ly/engraver-init.ly},
1933 @file{scm/define-grobs.scm}.
1938 @c @lsr{spacing,page-spacing.ly},
1939 @c @lsr{spacing,alignment-vertical-spacing.ly}.
1941 Internals Reference:
1942 @rinternals{Contexts},
1943 @rinternals{VerticalAxisGroup},
1944 @rinternals{StaffGrouper},
1945 @rinternals{VerticalAlignment},
1946 @rinternals{Axis_group_engraver}.
1949 @node Explicit staff and system positioning
1950 @subsection Explicit staff and system positioning
1952 One way to understand the @code{VerticalAxisGroup} and @code{\paper}
1953 settings explained in the previous two sections is as a collection of
1954 different settings that primarily concern the amount of vertical padding
1955 different staves and systems running down the page.
1957 It is possible to approach vertical spacing in a different way using
1958 @code{NonMusicalPaperColumn #'line-break-system-details}. Where
1959 @code{VerticalAxisGroup} and @code{\paper} settings specify vertical padding,
1960 @code{NonMusicalPaperColumn #'line-break-system-details} specifies exact
1961 vertical positions on the page.
1963 @code{NonMusicalPaperColumn #'line-break-system-details} accepts an associative
1964 list of three different settings:
1967 @item @code{X-offset}
1968 @item @code{Y-offset}
1969 @item @code{alignment-distances}
1972 Grob overrides, including the overrides for @code{NonMusicalPaperColumn}
1973 below, can occur in any of three different places in an input file:
1976 @item in the middle of note entry directly
1977 @item in a @code{\context} block
1978 @item in the @code{\with} block
1981 When we override @code{NonMusicalPaperColumn}, we use the usual
1982 @code{\override} command in @code{\context} blocks and in the
1983 @code{\with} block. On the other hand, when we override
1984 @code{NonMusicalPaperColumn} in the middle of note entry,
1985 use the special @code{\overrideProperty} command. Here are some
1986 example @code{NonMusicalPaperColumn} overrides with the special
1987 @code{\overrideProperty} command:
1990 \overrideProperty NonMusicalPaperColumn
1991 #'line-break-system-details #'((X-offset . 20))
1993 \overrideProperty NonMusicalPaperColumn
1994 #'line-break-system-details #'((Y-offset . 40))
1996 \overrideProperty NonMusicalPaperColumn
1997 #'line-break-system-details #'((X-offset . 20) (Y-offset . 40))
1999 \overrideProperty NonMusicalPaperColumn
2000 #'line-break-system-details #'((alignment-distances . (15)))
2002 \overrideProperty NonMusicalPaperColumn
2003 #'line-break-system-details #'((X-offset . 20) (Y-offset . 40)
2004 (alignment-distances . (15)))
2007 To understand how each of these different settings work, we begin
2008 by looking at an example that includes no overrides at all.
2010 @c \book { } is required in these examples to ensure the spacing
2011 @c overrides can be seen between systems. -np
2014 \header { tagline = ##f }
2015 \paper { left-margin = 0\mm }
2025 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2028 \repeat unfold 15 { d'4 d' d' d' }
2035 This score isolates line- and page-breaking information in a dedicated
2036 voice. This technique of creating a breaks voice will help keep layout
2037 separate from music entry as our example becomes more complicated.
2038 See @ref{Using an extra voice for breaks}.
2040 Explicit @code{\breaks} evenly divide the music into six measures per
2041 line. Vertical spacing results from LilyPond's defaults. To set
2042 the vertical startpoint of each system explicitly, we can set
2043 the @code{Y-offset} pair in the @code{line-break-system-details}
2044 attribute of the @code{NonMusicalPaperColumn} grob:
2047 \header { tagline = ##f }
2048 \paper { left-margin = 0\mm }
2054 \overrideProperty #"Score.NonMusicalPaperColumn"
2055 #'line-break-system-details #'((Y-offset . 0))
2057 \overrideProperty #"Score.NonMusicalPaperColumn"
2058 #'line-break-system-details #'((Y-offset . 40))
2060 \overrideProperty #"Score.NonMusicalPaperColumn"
2061 #'line-break-system-details #'((Y-offset . 80))
2064 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2067 \repeat unfold 15 { d'4 d' d' d' }
2074 Note that @code{line-break-system-details} takes an associative list of
2075 potentially many values, but that we set only one value here. Note,
2076 too, that the @code{Y-offset} property here determines the exact vertical
2077 position on the page at which each new system will render.
2079 Now that we have set the vertical startpoint of each system
2080 explicitly, we can also set the vertical distances between staves
2081 within each system manually. We do this using the @code{alignment-distances}
2082 subproperty of @code{line-break-system-details}.
2085 \header { tagline = ##f }
2086 \paper { left-margin = 0\mm }
2092 \overrideProperty #"Score.NonMusicalPaperColumn"
2093 #'line-break-system-details #'((Y-offset . 20)
2094 (alignment-distances . (15)))
2096 \overrideProperty #"Score.NonMusicalPaperColumn"
2097 #'line-break-system-details #'((Y-offset . 60)
2098 (alignment-distances . (15)))
2100 \overrideProperty #"Score.NonMusicalPaperColumn"
2101 #'line-break-system-details #'((Y-offset . 100)
2102 (alignment-distances . (15)))
2105 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2108 \repeat unfold 15 { d'4 d' d' d' }
2115 Note that here we assign two different values to the
2116 @code{line-break-system-details} attribute of the
2117 @code{NonMusicalPaperColumn} grob. Though the
2118 @code{line-break-system-details} attribute alist accepts many
2119 additional spacing parameters (including, for example, a corresponding
2120 @code{X-offset} pair), we need only set the @code{Y-offset} and
2121 @code{alignment-distances} pairs to control the vertical startpoint of
2122 every system and every staff. Finally, note that @code{alignment-distances}
2123 specifies the vertical positioning of staves but not of staff groups.
2126 \header { tagline = ##f }
2127 \paper { left-margin = 0\mm }
2133 \overrideProperty #"Score.NonMusicalPaperColumn"
2134 #'line-break-system-details #'((Y-offset . 0)
2135 (alignment-distances . (30 10)))
2137 \overrideProperty #"Score.NonMusicalPaperColumn"
2138 #'line-break-system-details #'((Y-offset . 60)
2139 (alignment-distances . (10 10)))
2141 \overrideProperty #"Score.NonMusicalPaperColumn"
2142 #'line-break-system-details #'((Y-offset . 100)
2143 (alignment-distances . (10 30)))
2146 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2149 \new Staff { \repeat unfold 15 { d'4 d' d' d' } }
2150 \new Staff { \repeat unfold 15 { e'4 e' e' e' } }
2157 Some points to consider:
2160 @item When using @code{alignment-distances}, lyrics and other non-staff lines
2161 do not count as a staff.
2163 @item The units of the numbers passed to @code{X-offset},
2164 @code{Y-offset} and @code{alignment-distances} are interpreted as multiples
2165 of the distance between adjacent staff lines. Positive values move staves
2166 and lyrics up, negative values move staves and lyrics down.
2168 @item Because the @code{NonMusicalPaperColumn #'line-break-system-details}
2169 settings given here allow the positioning of staves and systems anywhere
2170 on the page, it is possible to violate paper or margin boundaries or even
2171 to print staves or systems on top of one another. Reasonable values
2172 passed to these different settings will avoid this.
2181 @node Vertical collision avoidance
2182 @subsection Vertical collision avoidance
2184 @funindex outside-staff-priority
2185 @funindex outside-staff-padding
2186 @funindex outside-staff-horizontal-padding
2188 Intuitively, there are some objects in musical notation that belong
2189 to the staff and there are other objects that should be placed outside
2190 the staff. Objects belonging outside the staff include things such as
2191 rehearsal marks, text and dynamic markings (from now on, these will
2192 be called outside-staff objects). LilyPond's rule for the
2193 vertical placement of outside-staff objects is to place them as close
2194 to the staff as possible but not so close that they collide with
2197 LilyPond uses the @code{outside-staff-priority} property to determine
2198 whether a grob is an outside-staff object: if @code{outside-staff-priority}
2199 is a number, the grob is an outside-staff object. In addition,
2200 @code{outside-staff-priority} tells LilyPond in which order the objects
2203 First, LilyPond places all the objects that do not belong outside
2204 the staff. Then it sorts the outside-staff objects according to their
2205 @code{outside-staff-priority} (in increasing order). One by one, LilyPond
2206 takes the outside-staff objects and places them so that they do
2207 not collide with any objects that have already been placed. That
2208 is, if two outside-staff grobs are competing for the same space, the one
2209 with the lower @code{outside-staff-priority} will be placed closer to
2212 @lilypond[quote,ragged-right,relative=2,verbatim]
2215 \once \override TextScript #'outside-staff-priority = #1
2216 c4_"Text"\pp % this time the text will be closer to the staff
2218 % by setting outside-staff-priority to a non-number,
2219 % we disable the automatic collision avoidance
2220 \once \override TextScript #'outside-staff-priority = ##f
2221 \once \override DynamicLineSpanner #'outside-staff-priority = ##f
2222 c4_"Text"\pp % now they will collide
2225 The vertical padding between an outside-staff object and the
2226 previously-positioned grobs can be controlled with
2227 @code{outside-staff-padding}.
2229 @lilypond[quote,ragged-right,relative=2,verbatim]
2230 \once \override TextScript #'outside-staff-padding = #0
2231 a'^"This text is placed very close to the note"
2232 \once \override TextScript #'outside-staff-padding = #3
2233 c^"This text is padded away from the previous text"
2234 c^"This text is placed close to the previous text"
2238 By default, outside-staff objects are placed only to avoid
2239 a horizontal collision with previously-positioned grobs. This
2240 can lead to situations in which objects are placed very close to each
2241 other horizontally. The vertical spacing between staves can
2242 also be set so that outside staff objects are interleaved.
2243 Setting @code{outside-staff-horizontal-padding}
2244 causes an object to be offset vertically so that such a situation
2247 @lilypond[quote,ragged-right,relative=2,verbatim]
2248 % the markup is too close to the following note
2252 % setting outside-staff-horizontal-padding fixes this
2254 \once \override TextScript #'outside-staff-horizontal-padding = #1
2266 @node Horizontal spacing
2267 @section Horizontal spacing
2269 @cindex horizontal spacing
2270 @cindex spacing, horizontal
2273 * Horizontal spacing overview::
2274 * New spacing area::
2275 * Changing horizontal spacing::
2277 * Proportional notation::
2281 @node Horizontal spacing overview
2282 @subsection Horizontal spacing overview
2284 The spacing engine translates differences in durations into stretchable
2285 distances (@q{springs}) of differing lengths. Longer durations get
2286 more space, shorter durations get less. The shortest durations get a
2287 fixed amount of space (which is controlled by
2288 @code{shortest-duration-space} in the @rinternals{SpacingSpanner}
2289 object). The longer the duration, the more space it gets: doubling a
2290 duration adds a fixed amount (this amount is controlled by
2291 @code{spacing-increment}) of space to the note.
2293 For example, the following piece contains lots of half, quarter, and
2294 8th notes; the eighth note is followed by 1 note head width (NHW).
2295 The quarter note is followed by 2 NHW, the half by 3 NHW, etc.
2297 @lilypond[quote,verbatim,relative=1]
2298 c2 c4. c8 c4. c8 c4. c8 c8
2302 Normally, @code{spacing-increment} is set to 1.2 staff space, which is
2303 approximately the width of a note head, and
2304 @code{shortest-duration-space} is set to 2.0, meaning that the
2305 shortest note gets 2.4 staff space (2.0 times the
2306 @code{spacing-increment}) of horizontal space. This space is counted
2307 from the left edge of the symbol, so the shortest notes are generally
2308 followed by one NHW of space.
2310 If one would follow the above procedure exactly, then adding a single
2311 32nd note to a score that uses 8th and 16th notes, would widen up the
2312 entire score a lot. The shortest note is no longer a 16th, but a 32nd,
2313 thus adding 1 NHW to every note. To prevent this, the shortest
2314 duration for spacing is not the shortest note in the score, but rather
2315 the one which occurs most frequently.
2318 The most common shortest duration is determined as follows: in every
2319 measure, the shortest duration is determined. The most common shortest
2320 duration is taken as the basis for the spacing, with the stipulation
2321 that this shortest duration should always be equal to or shorter than
2322 an 8th note. The shortest duration is printed when you run
2323 @code{lilypond} with the @code{--verbose} option.
2325 These durations may also be customized. If you set the
2326 @code{common-shortest-duration} in @rinternals{SpacingSpanner}, then
2327 this sets the base duration for spacing. The maximum duration for this
2328 base (normally an 8th), is set through @code{base-shortest-duration}.
2330 @funindex common-shortest-duration
2331 @funindex base-shortest-duration
2332 @funindex stem-spacing-correction
2335 Notes that are even shorter than the common shortest note are
2336 followed by a space that is proportional to their duration relative to
2337 the common shortest note. So if we were to add only a few 16th notes
2338 to the example above, they would be followed by half a NHW:
2340 @lilypond[quote,verbatim,relative=2]
2341 c2 c4. c8 c4. c16[ c] c4. c8 c8 c8 c4 c4 c4
2345 In the @emph{Essay on automated music engraving}, it was explained
2346 that stem directions influence spacing (see @ressay{Optical
2347 spacing}). This is controlled with the
2348 @code{stem-spacing-correction} property in the
2349 @rinternals{NoteSpacing}, object. These are generated for every
2350 @rinternals{Voice} context. The @code{StaffSpacing} object
2351 (generated in @rinternals{Staff} context) contains the same
2352 property for controlling the stem/bar line spacing. The following
2353 example shows these corrections, once with default settings, and
2354 once with exaggerated corrections:
2356 @lilypond[quote,ragged-right]
2360 \override Staff.NoteSpacing #'stem-spacing-correction = #1.5
2361 \override Staff.StaffSpacing #'stem-spacing-correction = #1.5
2367 Proportional notation is supported; see @ref{Proportional notation}.
2374 Internals Reference:
2375 @rinternals{SpacingSpanner},
2376 @rinternals{NoteSpacing},
2377 @rinternals{StaffSpacing},
2378 @rinternals{NonMusicalPaperColumn}.
2383 There is no convenient mechanism to manually override spacing. The
2384 following work-around may be used to insert extra space into a score,
2385 adjusting the padding value as necessary.
2387 \override Score.NonMusicalPaperColumn #'padding = #10
2390 No work-around exists for decreasing the amount of space.
2393 @node New spacing area
2394 @subsection New spacing area
2396 New sections with different spacing parameters can be started with
2397 @code{newSpacingSection}. This is useful when there are
2398 sections with a different notions of long and short notes.
2400 In the following example, the time signature change introduces a new
2401 section, and hence the 16ths notes are spaced wider.
2403 @lilypond[relative=1,verbatim,quote]
2406 c8 c c4 c16[ c c8] c4
2412 The @code{\newSpacingSection} command creates a new
2413 @code{SpacingSpanner} object, and hence new @code{\override}s
2414 may be used in that location.
2421 Internals Reference:
2422 @rinternals{SpacingSpanner}.
2425 @node Changing horizontal spacing
2426 @subsection Changing horizontal spacing
2428 Horizontal spacing may be altered with the
2429 @code{base-shortest-duration} property. Here
2430 we compare the same music; once without altering
2431 the property, and then altered. Larger values
2432 of @code{ly:make-moment} will produce smaller
2433 music. Note that @code{ly:make-moment} constructs
2434 a duration, so @code{1 4} is a longer duration
2437 @lilypond[verbatim,line-width=12\cm]
2440 g4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2441 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2442 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2443 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2448 @lilypond[verbatim,line-width=12\cm]
2451 g4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2452 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2453 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2454 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2459 \override SpacingSpanner
2460 #'base-shortest-duration = #(ly:make-moment 1 16)
2469 By default, spacing in tuplets depends on various non-duration
2470 factors (such as accidentals, clef changes, etc). To disregard
2471 such symbols and force uniform equal-duration spacing, use
2472 @code{Score.SpacingSpanner #'uniform-stretching}. This
2473 property can only be changed at the beginning of a score,
2475 @lilypond[quote,ragged-right,verbatim]
2494 \override SpacingSpanner #'uniform-stretching = ##t
2500 When @code{strict-note-spacing} is set, notes are spaced without
2501 regard for clefs, bar lines, and grace notes,
2503 @lilypond[quote,ragged-right,relative=2,verbatim]
2504 \override Score.SpacingSpanner #'strict-note-spacing = ##t
2505 \new Staff { c8[ c \clef alto c \grace { c16[ c] } c8 c c] c32[ c32] }
2515 @subsection Line length
2518 @cindex breaking pages
2521 @funindex line-width
2522 @funindex ragged-right
2523 @funindex ragged-last
2525 @c Although line-width can be set in \layout, it should be set in paper
2526 @c block, to get page layout right.
2527 @c Setting indent in \paper block makes not much sense, but it works.
2529 @c Bit verbose and vague, use examples?
2530 The most basic settings influencing the spacing are @code{indent} and
2531 @code{line-width}. They are set in the @code{\layout} block. They
2532 control the indentation of the first line of music, and the lengths of
2535 If @code{ragged-right} is set to true in the @code{\layout} block, then
2536 systems ends at their natural horizontal length, instead of being spread
2537 horizontally to fill the whole line. This is useful for
2538 short fragments, and for checking how tight the natural spacing is.
2539 The normal default setting is false, but if the score has only one
2540 system the default value is true.
2543 @cindex vertical spacing
2545 The option @code{ragged-last} is similar to @code{ragged-right}, but
2546 only affects the last line of the piece. No restrictions are put on
2547 that line. The result is similar to formatting text paragraphs. In a
2548 paragraph, the last line simply takes its natural horizontal length.
2549 @c Note that for text there are several options for the last line.
2550 @c While Knuth TeX uses natural length, lead typesetters use the same
2551 @c stretch as the previous line. eTeX uses \lastlinefit to
2552 @c interpolate between both these solutions.
2568 @node Proportional notation
2569 @subsection Proportional notation
2571 LilyPond supports proportional notation, a type of horizontal spacing
2572 in which each note consumes an amount of horizontal space exactly
2573 equivalent to its rhythmic duration. This type of proportional spacing
2574 is comparable to horizontal spacing on top of graph paper. Some late
2575 20th- and early 21st-century scores use proportional notation to
2576 clarify complex rhythmic relationships or to facilitate the placement
2577 of timelines or other graphics directly in the score.
2579 LilyPond supports five different settings for proportional notation,
2580 which may be used together or alone:
2583 @item @code{proportionalNotationDuration}
2584 @item @code{uniform-stretching}
2585 @item @code{strict-note-spacing}
2586 @item @code{\remove Separating_line_group_engraver}
2587 @item @code{\override PaperColumn #'used = ##t}
2590 In the examples that follow, we explore these five different
2591 proportional notation settings and examine how these settings interact.
2593 We start with the following one-measure example, which uses classical
2594 spacing with ragged-right turned on.
2596 @lilypond[quote,verbatim,ragged-right]
2599 \new RhythmicStaff {
2603 c'16 c'16 c'16 c'16 c'16
2610 Notice that the half note which begins the measure takes up far less
2611 than half of the horizontal space of the measure. Likewise, the
2612 sixteenth notes and sixteenth-note quintuplets (or twentieth notes)
2613 which end the measure together take up far more than half the
2614 horizontal space of the measure.
2616 In classical engraving, this spacing may be exactly what we want
2617 because we can borrow horizontal space from the half note and conserve
2618 horizontal space across the measure as a whole.
2620 On the other hand, if we want to insert a measured timeline or other
2621 graphic above or below our score, we need proportional notation. We
2622 turn proportional notation on with the proportionalNotationDuration
2625 @lilypond[quote,verbatim,ragged-right]
2628 \new RhythmicStaff {
2632 c'16 c'16 c'16 c'16 c'16
2639 proportionalNotationDuration = #(ly:make-moment 1 20)
2645 The half note at the beginning of the measure and the faster notes in
2646 the second half of the measure now occupy equal amounts of horizontal
2647 space. We could place a measured timeline or graphic above or below
2650 The @code{proportionalNotationDuration} setting is a context setting
2651 that lives in @code{Score}. Remember that context settings can appear
2652 in one of three locations within our input file -- in a @code{\with}
2653 block, in a @code{\context} block, or directly in music entry preceded
2654 by the @code{\set} command. As with all context settings, users can
2655 pick which of the three different locations they would like to
2656 set @code{proportionalNotationDuration} in to.
2658 The @code{proportionalNotationDuration} setting takes a single argument,
2659 which is the reference duration against that all music will be spaced.
2660 The LilyPond Scheme function @code{make-moment} takes two arguments
2661 -- a numerator and denominator which together express some fraction of
2662 a whole note. The call @code{#(ly:make-moment 1 20)} therefore produces
2663 a reference duration of a twentieth note. Values such as
2664 @code{#(ly:make-moment 1 16)}, @code{#(ly:make-moment 1 8)}, and
2665 @code{#(ly:make-moment 3 97)} are all possible as well.
2667 How do we select the right reference duration to pass to
2668 @code{proportionalNotationDuration}? Usually by a process of trial
2669 and error, beginning with a duration close to the fastest (or smallest)
2670 duration in the piece. Smaller reference durations space music loosely;
2671 larger reference durations space music tightly.
2673 @lilypond[quote,verbatim,ragged-right]
2676 \new RhythmicStaff {
2680 c'16 c'16 c'16 c'16 c'16
2687 proportionalNotationDuration = #(ly:make-moment 1 8)
2694 \new RhythmicStaff {
2698 c'16 c'16 c'16 c'16 c'16
2705 proportionalNotationDuration = #(ly:make-moment 1 16)
2712 \new RhythmicStaff {
2716 c'16 c'16 c'16 c'16 c'16
2723 proportionalNotationDuration = #(ly:make-moment 1 32)
2729 Note that too large a reference duration -- such as the eighth note,
2730 above -- spaces music too tightly and can cause note head collisions.
2731 Also that proportional notation in general takes up more horizontal
2732 space than classical spacing. Proportional spacing provides rhythmic
2733 clarity at the expense of horizontal space.
2735 Next we examine how to optimally space overlapping tuplets.
2737 We start by examining what happens to our original example, with
2738 classical spacing, when we add a second staff with a different type of
2741 @lilypond[quote,verbatim,ragged-right]
2744 \new RhythmicStaff {
2748 c'16 c'16 c'16 c'16 c'16
2751 \new RhythmicStaff {
2753 c'8 c'8 c'8 c'8 c'8 c'8 c'8 c'8 c'8
2760 The spacing is bad because the evenly spaced notes of the bottom staff
2761 do not stretch uniformly. Classical engravings include very few complex
2762 triplets and so classical engraving rules can generate this type of
2763 result. Setting @code{proportionalNotationDuration} fixes this.
2765 @lilypond[quote,verbatim,ragged-right]
2768 \new RhythmicStaff {
2772 c'16 c'16 c'16 c'16 c'16
2775 \new RhythmicStaff {
2777 c'8 c'8 c'8 c'8 c'8 c'8 c'8 c'8 c'8
2784 proportionalNotationDuration = #(ly:make-moment 1 20)
2790 But if we look very carefully we can see that notes of the second half
2791 of the 9-tuplet space ever so slightly more widely than the notes
2792 of the first half of the 9-tuplet. To ensure uniform stretching, we
2793 turn on @code{uniform-stretching}, which is a property of
2794 @code{SpacingSpanner}.
2796 @lilypond[quote,verbatim,ragged-right]
2799 \new RhythmicStaff {
2803 c'16 c'16 c'16 c'16 c'16
2806 \new RhythmicStaff {
2808 c'8 c'8 c'8 c'8 c'8 c'8 c'8 c'8 c'8
2815 proportionalNotationDuration = #(ly:make-moment 1 20)
2816 \override SpacingSpanner #'uniform-stretching = ##t
2822 Our two-staff example now spaces exactly, our rhythmic
2823 relationships are visually clear, and we can include a measured
2824 timeline or graphic if we want.
2826 Note that the LilyPond's proportional notation package expects
2827 that all proportional scores set the SpacingSpanner's
2828 'uniform-stretching attribute to ##t. Setting
2829 proportionalNotationDuration without also setting the
2830 SpacingSpanner's 'uniform-stretching attribute to ##t will, for
2831 example, cause Skips to consume an incorrect amount of horizontal
2834 The SpacingSpanner is an abstract grob that lives in the Score
2835 context. As with our settings of proportionalNotationDuration,
2836 overrides to the SpacingSpanner can occur in any of three
2837 different places in our input file – in the Score \with block, in
2838 a Score \context block, or in note entry directly.
2840 There is by default only one @code{SpacingSpanner} per @code{Score}. This
2841 means that, by default, @code{uniform-stretching} is either turned on for the
2842 entire score or turned off for the entire score. We can, however,
2843 override this behavior and turn on different spacing features at
2844 different places in the score. We do this with the command
2845 @code{\newSpacingSection}. See @ref{New spacing area}, for more info.
2847 Next we examine the effects of the @code{Separating_line_group_engraver} and
2848 see why proportional scores frequently remove this engraver. The following
2849 example shows that there is a small amount of @qq{preferatory} space
2850 just before the first note in each system.
2852 @lilypond[quote,verbatim,ragged-right]
2865 The amount of this preferatory space is the same whether after a time
2866 signature, a key signature or a clef. @code{Separating_line_group_engraver}
2867 is responsible for this space. Removing @code{Separating_line_group_engraver}
2868 reduces this space to zero.
2870 @lilypond[quote,verbatim,ragged-right]
2876 \remove Separating_line_group_engraver
2884 Nonmusical elements like time signatures, key signatures, clefs and
2885 accidentals are problematic in proportional notation. None of these
2886 elements has rhythmic duration. But all of these elements consume
2887 horizontal space. Different proportional scores approach these
2888 problems differently.
2890 It may be possible to avoid spacing problems with key signatures
2891 simply by not having any. This is a valid option since most
2892 proportional scores are contemporary music. The same may be true
2893 of time signatures, especially for those scores
2894 that include a measured timeline or other graphic. But these scores
2895 are exceptional and most proportional scores include at least some
2896 time signatures. Clefs and accidentals are even more essential.
2898 So what strategies exist for spacing nonmusical elements in a
2899 proportional context? One good option is the @code{strict-note-spacing}
2900 property of @code{SpacingSpanner}. Compare the two scores below:
2902 @lilypond[quote,verbatim,ragged-right]
2904 \set Score.proportionalNotationDuration = #(ly:make-moment 1 16)
2914 \set Score.proportionalNotationDuration = #(ly:make-moment 1 16)
2915 \override Score.SpacingSpanner #'strict-note-spacing = ##t
2925 Both scores are proportional, but the spacing in the first score
2926 is too loose because of the clef change. The spacing of the second
2927 score remains strict, however, because strict-note-spacing is
2928 turned on. Turning on strict-note-spacing causes the width of
2929 time signatures, key signatures, clefs and accidentals to play no
2930 part in the spacing algorithm.
2932 In addition to the settings given here, there are other settings
2933 that frequently appear in proportional scores. These include:
2936 @item @code{\override SpacingSpanner #'strict-grace-spacing = ##t}
2937 @item @code{tupletFullLength = ##t}
2938 @item @code{\override Beam #'breakable = ##t}
2939 @item @code{\override Glissando #'breakable = ##t}
2940 @item @code{\override TextSpanner #'breakable = ##t}
2941 @item @code{\remove Forbid_line_break_engraver in the Voice context}
2944 These settings space grace notes strictly, extend tuplet brackets to
2945 mark both rhythmic start- and stop-points, and allow spanning elements
2946 to break across systems and pages. See the respective parts of the manual
2947 for these related settings.
2952 @ref{New spacing area}.
2958 @node Fitting music onto fewer pages
2959 @section Fitting music onto fewer pages
2961 Sometimes you can end up with one or two staves on a second
2962 (or third, or fourth...) page. This is annoying, especially
2963 if you look at previous pages and it looks like there is plenty
2964 of room left on those.
2966 When investigating layout issues, @code{annotate-spacing} is an
2967 invaluable tool. This command prints the values of various layout
2968 spacing variables; for more details see the following section,
2969 @ref{Displaying spacing}.
2972 * Displaying spacing::
2973 * Changing spacing::
2977 @node Displaying spacing
2978 @subsection Displaying spacing
2980 @funindex annotate-spacing
2981 @cindex spacing, display of layout
2983 To graphically display the dimensions of vertical layout variables
2984 that may be altered for page formatting, set
2985 @code{annotate-spacing} in the @code{\paper} block:
2987 @c need to have \book{} otherwise we get the separate systems. -hwn
2988 @lilypond[verbatim,quote]
2989 #(set-default-paper-size "a6" 'landscape)
2992 \paper { annotate-spacing = ##t }
2998 All layout dimensions are displayed in staff-spaces, regardless
2999 of the units specified in the @code{\paper} or @code{\layout} block.
3000 In the above example, @code{paper-height} has a value of 59.75
3001 @code{staff-spaces}, and the @code{staff-size} is 20 points (the
3002 default value). Note that:
3004 @multitable {1 staff-space} {staff-size)/4 * (25.4/72.27) mm}
3007 @tab = (25.4/72.27) mm
3010 @tab = (@code{staff-size})/4 pts
3012 @tab = (@code{staff-size})/4 * (25.4/72.27) mm
3017 In this case, one @code{staff-space} is approximately equal to
3018 1.757mm. Thus the @code{paper-height} measurement of 59.75
3019 @code{staff-spaces} is equivalent to 105 millimeters, the height
3020 of @code{a6} paper in landscape orientation. The pairs
3021 (@var{a},@var{b}) are intervals, where @var{a} is the lower
3022 edge and @var{b} the upper edge of the interval.
3027 @ref{Setting the staff size}.
3033 @node Changing spacing
3034 @subsection Changing spacing
3036 The output of @code{annotate-spacing} reveals vertical dimensions
3037 in great detail. For details about modifying margins and other
3038 layout variables, see @ref{Page formatting}.
3040 Other than margins, there are a few other options to save space:
3044 Force systems to move as close together as possible (to fit as
3045 many systems as possible onto a page) while being spaced so that
3046 there is no blank space at the bottom of the page.
3050 system-system-spacing = #'((padding . 0) (space . 0.1))
3051 ragged-last-bottom = ##f
3057 Force the number of systems. This can help in two ways. Just
3058 setting a value, even the same value as the number of systems
3059 being typeset by default, will sometimes cause more systems to
3060 be fitted onto each page, as an estimation step is then bypassed,
3061 giving a more accurate fit to each page. Also, forcing an actual
3062 reduction in the number of systems may save a further page. For
3063 example, if the default layout has 11 systems, the following
3064 assignment will force a layout with 10 systems.
3073 Avoid (or reduce) objects that increase the vertical size of a
3074 system. For example, volta repeats (or alternate repeats) require
3075 extra space. If these repeats are spread over two systems, they
3076 will take up more space than one system with the volta repeats and
3077 another system without. For example, dynamics that @q{stick out} of
3078 a system can be moved closer to the staff:
3080 @lilypond[verbatim,quote,relative=1]
3082 e4 c g-\tweak #'X-offset #-2.7 -\tweak #'Y-offset #2.5 \f c
3086 Alter the horizontal spacing via @code{SpacingSpanner}. For more
3087 details, see @ref{Changing horizontal spacing}. The following
3088 example illustrates the default spacing:
3090 @lilypond[verbatim,quote]
3103 The next example modifies @code{common-shortest-duration} from a
3104 value of @code{1/4} to @code{1/2}. The quarter note is the most
3105 common and shortest duration in this example, so by making this
3106 duration longer, a @q{squeezing} effect occurs:
3108 @lilypond[verbatim,quote]
3120 \override SpacingSpanner
3121 #'common-shortest-duration = #(ly:make-moment 1 2)
3128 The @code{common-shortest-duration} property cannot be modified
3129 dynamically, so it must always be placed in a @code{\context}
3130 block so that it applies to the whole score.
3137 @ref{Page formatting},
3138 @ref{Changing horizontal spacing}.