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.
25 http://code.google.com/p/lilypond/issues/detail?id=68
31 @chapter Spacing issues
33 The global paper layout is determined by three factors: the page layout, the
34 line breaks, and the spacing. These all influence each other. The
35 choice of spacing determines how densely each system of music is set.
36 This influences where line breaks are chosen, and thus ultimately, how
37 many pages a piece of music takes.
39 Globally speaking, this procedure happens in four steps: first,
40 flexible distances (@q{springs}) are chosen, based on durations. All
41 possible line breaking combinations are tried, and a @q{badness} score
42 is calculated for each. Then the height of each possible system is
43 estimated. Finally, a page breaking and line breaking combination is chosen
44 so that neither the horizontal nor the vertical spacing is too cramped
47 Two types of blocks can contain layout settings:
48 @code{\paper @{@dots{}@}} and @code{\layout @{@dots{}@}}. The
49 @code{\paper} block contains page layout settings that are expected
50 to be the same for all scores in a book or bookpart, such as the
51 paper height, or whether to print page numbers, etc. See
52 @ref{Page layout}. The @code{\layout} block contains score layout
53 settings, such as the number of systems to use, or the space
54 between staff-groups, etc. See @ref{Score layout}.
61 * Horizontal spacing::
62 * Fitting music onto fewer pages::
69 This section discusses page layout options for the @code{\paper}
74 * Paper size and automatic scaling::
75 * Fixed vertical spacing paper variables::
76 * Flexible vertical spacing paper variables::
77 * Horizontal spacing paper variables::
78 * Other paper variables::
83 @subsection The @code{@bs{}paper} block
85 @code{\paper} blocks may be placed in three different places to form
86 a descending hierarchy of @code{\paper} blocks:
91 At the top of the input file, before all @code{\book},
92 @code{\bookpart}, and @code{\score} blocks.
95 Within a @code{\book} block but outside all the @code{\bookpart} and
96 @code{\score} blocks within that book.
99 Within a @code{\bookpart} block but outside all @code{\score} blocks
100 within that bookpart.
104 A @code{\paper} block cannot be placed within a @code{\score} block.
106 The values of the fields filter down this hierarchy, with the values
107 set higher in the hierarchy persisting unless they are over-ridden
108 by a value set lower in the hierarchy.
110 Several @code{\paper} blocks can appear at each of the levels, for
111 example as parts of several @code{\include}d files. If so, the
112 fields at each level are merged, with values encountered last taking
113 precedence if duplicated fields appear.
115 Settings that can appear in a @code{\paper} block include:
120 the @code{set-paper-size} scheme function,
123 @code{\paper} variables used for customizing page layout, and
126 markup definitions used for customizing the layout of headers,
131 The @code{set-paper-size} function is discussed in the next
132 section, @ref{Paper size and automatic scaling}. The
133 @code{\paper} variables that deal with page layout are discussed
134 in later sections. The markup definitions that deal with headers,
135 footers, and titles are discussed in
136 @ref{Custom titles headers and footers}.
138 Most @code{\paper} variables will only work in a @code{\paper}
139 block. The few that will also work in a @code{\layout} block are
140 listed in @ref{The layout block,,The @code{@bs{}layout} block}.
142 Except when specified otherwise, all @code{\paper} variables that
143 correspond to distances on the page are measured in millimeters,
144 unless a different unit is specified by the user. For example,
145 the following declaration sets @code{top-margin} to ten
154 To set it to @code{0.5} inches, use the @code{\in} unit suffix:
162 The available unit suffixes are @code{\mm}, @code{\cm},
163 @code{\in}, and @code{\pt}. These units are simple values for
164 converting from millimeters; they are defined in
165 @file{ly/paper-defaults-init.ly}. For the sake of clarity, when
166 using millimeters, the @code{\mm} is typically included in the
167 code, even though it is not technically necessary.
169 It is also possible to define @code{\paper} values using Scheme.
170 The Scheme equivalent of the above example is:
174 #(define top-margin (* 0.5 in))
180 @ref{Paper size and automatic scaling},
181 @ref{Custom titles headers and footers},
182 @ref{The layout block,,The @code{@bs{}layout} block}.
185 @file{ly/paper-defaults-init.ly}.
188 @node Paper size and automatic scaling
189 @subsection Paper size and automatic scaling
197 * Setting the paper size::
198 * Automatic scaling to paper size::
202 @node Setting the paper size
203 @unnumberedsubsubsec Setting the paper size
205 @q{A4} is the default value when no explicit paper size is set. However,
206 there are two functions that can be used to change it:
209 @item set-default-paper-size
212 #(set-default-paper-size "quarto")
215 which must always be placed at the toplevel scope, and
221 #(set-paper-size "tabloid")
225 which must always be placed in a @code{\paper} block.
228 If the @code{set-default-paper-size} function is used in the toplevel
229 scope, it must come before any @code{\paper} block.
230 @code{set-default-paper-size} sets the paper size for all pages,
231 whereas @code{set-paper-size} only sets the paper size for the pages
232 that the @code{\paper} block applies to. For example, if the
233 @code{\paper} block is at the top of the file, then it will apply the
234 paper size to all pages. If the @code{\paper} block is inside a
235 @code{\book}, then the paper size will only apply to that book.
237 When the @code{set-paper-size} function is used, it must be
238 placed @emph{before} any other functions used within the same
239 @code{\paper} block. See @ref{Automatic scaling to paper size}.
241 Paper sizes are defined in @file{scm/paper.scm}, and while it is
242 possible to add custom sizes, they will be overwritten on subsequent
243 software updates. The available paper sizes are listed in
244 @ref{Predefined paper sizes}.
246 @c An appendix entry exists for paper sizes but is not auto-generated
248 The following command can be used in the file to add a custom paper size
249 which can then be used with @code{set-default-paper-size} or
250 @code{set-paper-size} as appropriate,
253 #(set! paper-alist (cons '("my size" . (cons (* 15 in) (* 3 in))) paper-alist))
256 #(set-paper-size "my size")
260 The units @code{in} (inches), @code{cm} (centimeters) and @code{mm}
261 (millimeters) can all be used.
263 @cindex paper size, orientation
264 @cindex page, orientation
265 @cindex paper size, landscape
267 If the symbol @code{'landscape} is added to the paper size function,
268 pages will be rotated by 90 degrees, and wider line widths will be set
272 #(set-default-paper-size "a6" 'landscape)
275 Swapping the paper dimensions @emph{without} having the print rotated
276 (like when printing to postcard size, or creating graphics for inclusion
277 rather than a standalone document) can be achieved by appending
278 @samp{landscape} to the name of the paper size itself:
281 #(set-default-paper-size "a6landscape")
284 When the paper size ends with an explicit @samp{landscape} or
285 @samp{portrait}, the presence of a @code{'landscape} symbol @emph{only}
286 affects print orientation, not the paper dimensions used for layout.
290 @ref{Automatic scaling to paper size},
291 @ref{Predefined paper sizes}.
294 @file{scm/paper.scm}.
297 @node Automatic scaling to paper size
298 @unnumberedsubsubsec Automatic scaling to paper size
300 If the paper size is changed with one of the scheme functions
301 (@code{set-default-paper-size} or @code{set-paper-size}), the
302 values of several @code{\paper} variables are automatically scaled
303 to the new size. To bypass the automatic scaling for a particular
304 variable, set the variable after setting the paper size. Note
305 that the automatic scaling is not triggered by setting the
306 @code{paper-height} or @code{paper-width} variables, even though
307 @code{paper-width} can influence other values (this is separate
308 from scaling and is discussed below). The
309 @code{set-default-paper-size} and @code{set-paper-size} functions
310 are described in @ref{Setting the paper size}.
312 The vertical dimensions affected by automatic scaling are
313 @code{top-margin} and @code{bottom-margin} (see
314 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables}).
316 dimensions affected by automatic scaling are @code{left-margin},
317 @code{right-margin}, @code{inner-margin}, @code{outer-margin},
318 @code{binding-offset}, @code{indent}, and @code{short-indent} (see
319 @ref{Horizontal spacing paper variables,,Horizontal spacing @code{@bs{}paper} variables}).
321 The default values for these dimensions are set in
322 @file{ly/paper-defaults-init.ly}, using internal variables named
323 @code{top-margin-default}, @code{bottom-margin-default}, etc.
324 These are the values that result at the default paper size
325 @code{a4}. For reference, with @code{a4} paper the
326 @code{paper-height} is @code{297\mm} and the @code{paper-width} is
331 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables},
332 @ref{Horizontal spacing paper variables,,Horizontal spacing @code{@bs{}paper} variables}.
335 @file{ly/paper-defaults-init.ly},
336 @file{scm/paper.scm}.
339 @node Fixed vertical spacing paper variables
340 @subsection Fixed vertical spacing @code{@bs{}paper} variables
342 @warning{Some @code{@bs{}paper} dimensions are automatically
343 scaled to the paper size, which may lead to unexpected behavior.
344 See @ref{Automatic scaling to paper size}.}
346 Default values (before scaling) are defined in
347 @file{ly/paper-defaults-init.ly}.
351 @funindex paper-height
353 The height of the page, unset by default. Note that the automatic
354 scaling of some vertical dimensions is not affected by this.
359 The margin between the top of the page and the top of the
360 printable area. If the paper size is modified, this dimension's
361 default value is scaled accordingly.
364 @funindex bottom-margin
366 The margin between the bottom of the printable area and the bottom
367 of the page. If the paper size is modified, this dimension's
368 default value is scaled accordingly.
371 @funindex ragged-bottom
373 If this is set to true,
374 systems will be set at their natural spacing, neither compressed
375 nor stretched vertically to fit the page.
377 @item ragged-last-bottom
378 @funindex ragged-last-bottom
380 If this is set to false, then the last page,
381 and the last page in each section created with a @code{\bookpart} block,
382 will be vertically justified in the same way as the earlier pages.
388 @ref{Automatic scaling to paper size}.
391 @file{ly/paper-defaults-init.ly}.
397 The titles (from the @code{\header} block) are treated as a
398 system, so @code{ragged-bottom} and @code{ragged-last-bottom} will
399 add space between the titles and the first system of the score.
401 Explicitly defined paper-sizes will override any user-defined top or
402 bottom margin settings.
405 @node Flexible vertical spacing paper variables
406 @subsection Flexible vertical spacing @code{@bs{}paper} variables
408 In most cases, it is preferable for the vertical distances between
409 certain items (such as margins, titles, systems, and separate
410 scores) to be flexible, so that they stretch and compress nicely
411 according to each situation. A number of @code{\paper} variables
412 (listed below) are available to fine-tune the stretching behavior
415 Note that the @code{\paper} variables discussed in this section do
416 not control the spacing of staves within individual systems.
417 Within-system spacing is controlled by grob properties, with
418 settings typically entered inside a @code{\score} or
419 @code{\layout} block, and not inside a @code{\paper} block. See
420 @ref{Flexible vertical spacing within systems}.
423 * Structure of flexible vertical spacing alists::
424 * List of flexible vertical spacing paper variables::
428 @node Structure of flexible vertical spacing alists
429 @unnumberedsubsubsec Structure of flexible vertical spacing alists
431 Each of the flexible vertical spacing @code{\paper} variables is
432 an alist (association list) containing four @emph{keys}:
437 @code{basic-distance} -- the vertical distance, measured in
438 staff-spaces, between the @emph{reference points} of the two
439 items, when no collisions would result, and no stretching or
440 compressing is in effect. The reference point of a (title or
441 top-level) markup is its highest point, and the reference point of
442 a system is the vertical center of the nearest @code{StaffSymbol}
443 -- even if a non-staff line (such as a @code{Lyrics} context) is
444 in the way. Values for @code{basic-distance} that are less than
445 either @code{padding} or @code{minimum-distance} are not
446 meaningful, since the resulting distance will never be less than
447 either @code{padding} or @code{minimum-distance}.
450 @code{minimum-distance} -- the smallest allowable vertical
451 distance, measured in staff-spaces, between the reference points
452 of the two items, when compressing is in effect. Values for
453 @code{minimum-distance} that are less than @code{padding} are not
454 meaningful, since the resulting distance will never be less than
457 @c TODO: explain skylines somewhere and xref to it from here.
460 @code{padding} -- the minimum required amount of unobstructed
461 vertical whitespace between the bounding boxes (or skylines) of
462 the two items, measured in staff-spaces.
465 @code{stretchability} -- a unitless measure of the dimension's
466 relative propensity to stretch. If zero, the distance will not
467 stretch (unless collisions would result). When positive, the
468 significance of a particular dimension's @code{stretchability}
469 value lies only in its relation to the @code{stretchability}
470 values of the other dimensions. For example, if one dimension has
471 twice the @code{stretchability} of another, it will stretch twice
472 as easily. Values should be non-negative and finite. The value
473 @code{+inf.0} triggers a @code{programming_error} and is ignored,
474 but @code{1.0e7} can be used for an almost infinitely stretchable
475 spring. If unset, the default value is set to
476 @code{basic-distance}. Note that the dimension's propensity to
477 @emph{compress} cannot be directly set by the user and is equal to
478 (@code{basic-distance}@tie{}@minus{}@tie{}@code{minimum-distance}).
482 If a page has a ragged bottom, the resulting distance is the
488 @code{basic-distance},
491 @code{minimum-distance}, and
494 @code{padding} plus the smallest distance necessary to eliminate
499 For multi-page scores with a ragged bottom on the last page, the last
500 page uses the same spacing as the preceding page, provided there is
501 enough space for that.
503 Specific methods for modifying alists are discussed in
504 @ref{Modifying alists}. The following example demonstrates the
505 two ways these alists can be modified. The first declaration
506 updates one key-value individually, and the second completely
507 redefines the variable:
511 system-system-spacing.basic-distance = #8
512 score-system-spacing =
513 #'((basic-distance . 12)
514 (minimum-distance . 6)
516 (stretchability . 12))
521 @node List of flexible vertical spacing paper variables
522 @unnumberedsubsubsec List of flexible vertical spacing @code{@bs{}paper} variables
524 The names of these variables follow the format
525 @code{@var{upper}-@var{lower}-spacing}, where @code{@var{upper}}
526 and @code{@var{lower}} are the items to be spaced. Each distance
527 is measured between the reference points of the two items (see the
528 description of the alist structure above). Note that in these
529 variable names, the term @q{@code{markup}} refers to both
530 @emph{title markups} (@code{bookTitleMarkup} or
531 @code{scoreTitleMarkup}) and @emph{top-level markups} (see
532 @ref{File structure}). All distances are measured in
535 Default settings are defined in @file{ly/paper-defaults-init.ly}.
537 @c TODO: Where do headers/footers fit in? -mp
540 @item markup-system-spacing
541 @funindex markup-system-spacing
543 the distance between a (title or top-level) markup and the system
546 @item score-markup-spacing
547 @funindex score-markup-spacing
549 the distance between the last system of a score and the (title or
550 top-level) markup that follows it.
552 @item score-system-spacing
553 @funindex score-system-spacing
555 the distance between the last system of a score and the first
556 system of the score that follows it, when no (title or top-level)
557 markup exists between them.
559 @item system-system-spacing
560 @funindex system-system-spacing
562 the distance between two systems in the same score.
564 @item markup-markup-spacing
565 @funindex markup-markup-spacing
567 the distance between two (title or top-level) markups.
569 @item last-bottom-spacing
570 @funindex last-bottom-spacing
572 the distance from the last system or top-level markup on a page to
573 the bottom of the printable area (i.e. the top of the bottom
576 @item top-system-spacing
577 @funindex top-system-spacing
579 the distance from the top of the printable area (i.e. the bottom
580 of the top margin) to the first system on a page, when there is no
581 (title or top-level) markup between the two.
583 @item top-markup-spacing
584 @funindex top-markup-spacing
586 the distance from the top of the printable area (i.e. the bottom
587 of the top margin) to the first (title or top-level) markup on a
588 page, when there is no system between the two.
593 @ref{Flexible vertical spacing within systems}.
596 @file{ly/paper-defaults-init.ly}.
602 @node Horizontal spacing paper variables
603 @subsection Horizontal spacing @code{@bs{}paper} variables
605 @warning{Some @code{@bs{}paper} dimensions are automatically
606 scaled to the paper size, which may lead to unexpected behavior.
607 See @ref{Automatic scaling to paper size}.}
610 * paper variables for widths and margins::
611 * paper variables for two-sided mode::
612 * paper variables for shifts and indents::
616 @node paper variables for widths and margins
617 @unnumberedsubsubsec @code{@bs{}paper} variables for widths and margins
619 Default values (before scaling) that are not listed here are
620 defined in @file{ly/paper-defaults-init.ly}.
625 @funindex paper-width
627 The width of the page, unset by default. While @code{paper-width}
628 has no effect on the automatic scaling of some horizontal
629 dimensions, it does influence the @code{line-width} variable. If
630 both @code{paper-width} and @code{line-width} are set, then
631 @code{left-margin} and @code{right-margin} will also be updated.
632 Also see @code{check-consistency}.
637 When specified in a @code{\paper} block this defines the horizontal
638 extent available for the staff lines in un-indented systems. If left
639 unspecified, the paper's @code{line-width} is determined from
640 @code{(paper-width@tie{}@minus{}@tie{}left-margin@tie{}@minus{}@tie{}right-margin)}
641 If the paper's @code{line-width} is specified, and both
642 @code{left-margin} and @code{right-margin} are not, then the
643 margins will be updated to center the systems on the page
644 automatically. Also see @code{check-consistency}.
646 @code{line-width}s for individual scores can be specified in the
647 scores' @code{\layout} blocks. These values control the width of the
648 lines produced on a score-by-score basis. If @code{line-width} is not
649 specified for a score, it defaults to the paper's @code{line-width}.
650 Setting a score's @code{line-width} has no effect on the paper margins.
651 Staff lines, of a length determined by the score's @code{line-width},
652 are left-aligned within the paper area defined by the paper's
653 @code{line-width}. If the score and paper @code{line-width}s are equal,
654 the staff lines will extend exactly from the left margin to the right
655 margin, but if the score's @code{line-width} is greater than the
656 paper's @code{line-width} the staff lines will run over into the right
660 @funindex left-margin
662 The margin between the left edge of the page and the start of the
663 staff lines in unindented systems. If the paper size is modified,
664 this dimension's default value is scaled accordingly. If
665 @code{left-margin} is unset, and both @code{line-width} and
666 @code{right-margin} are set, then @code{left-margin} is set to
667 @code{(paper-width@tie{}@minus{}@tie{}line-width@tie{}@minus{}@tie{}right-margin)}.
668 If only @code{line-width} is set, then both margins are set to
669 @code{((paper-width@tie{}@minus{}@tie{}line-width)@tie{}/@tie{}2)},
670 and the systems are consequently centered on the page. Also see
671 @code{check-consistency}.
674 @funindex right-margin
676 The margin between the right edge of the page and the end of the
677 staff lines in non-ragged systems. If the paper size is modified,
678 this dimension's default value is scaled accordingly. If
679 @code{right-margin} is unset, and both @code{line-width} and
680 @code{left-margin} are set, then @code{right-margin} is set to
681 @code{(paper-width@tie{}@minus{}@tie{}line-width@tie{}@minus{}@tie{}left-margin)}.
682 If only @code{line-width} is set, then both margins are set to
683 @code{((paper-width@tie{}@minus{}@tie{}line-width)@tie{}/@tie{}2)},
684 and the systems are consequently centered on the page. Also see
685 @code{check-consistency}.
687 @item check-consistency
688 @funindex check-consistency
690 If this is true (the default value), print a warning if
691 @code{left-margin}, @code{line-width}, and @code{right-margin} do not
692 exactly add up to @code{paper-width}, and replace each of these
693 (except @code{paper-width}) with their default values (scaled to the
694 paper size if necessary). If set to false, ignore any
695 inconsistencies and allow systems to run off the edge of the page.
698 @funindex ragged-right
700 If set to true, systems will not fill the line width. Instead,
701 systems end at their natural horizontal length. Default:
702 @code{#t} for scores with only one system, and @code{#f} for
703 scores with two or more systems. This variable can also be set in
704 a @code{\layout} block.
707 @funindex ragged-last
709 If set to true, the last system in the score will not fill the
710 line width. Instead the last system ends at its natural
711 horizontal length. Default: @code{#f}. This variable can also be
712 set in a @code{\layout} block.
718 @ref{Automatic scaling to paper size}.
721 @file{ly/paper-defaults-init.ly}.
724 Explicitly defined paper-sizes will override any user-defined left or
725 right margin settings.
728 @node paper variables for two-sided mode
729 @unnumberedsubsubsec @code{@bs{}paper} variables for two-sided mode
731 Default values (before scaling) are defined in
732 @file{ly/paper-defaults-init.ly}.
740 @cindex binding gutter
742 If set to true, use @code{inner-margin}, @code{outer-margin} and
743 @code{binding-offset} to determine margins depending on whether
744 the page number is odd or even. This overrides @code{left-margin}
745 and @code{right-margin}.
748 @funindex inner-margin
750 The margin all pages have at the inner side if they are part of a
751 book. If the paper size is modified, this dimension's default
752 value is scaled accordingly. Works only with @code{two-sided} set
756 @funindex outer-margin
758 The margin all pages have at the outer side if they are part of a
759 book. If the paper size is modified, this dimension's default
760 value is scaled accordingly. Works only with @code{two-sided} set
764 @funindex binding-offset
766 The amount @code{inner-margin} is increased to make sure nothing
767 will be hidden by the binding. If the paper size is modified,
768 this dimension's default value is scaled accordingly. Works only
769 with @code{two-sided} set to true.
775 @ref{Automatic scaling to paper size}.
778 @file{ly/paper-defaults-init.ly}.
781 @node paper variables for shifts and indents
782 @unnumberedsubsubsec @code{@bs{}paper} variables for shifts and indents
784 Default values (before scaling) that are not listed here are
785 defined in @file{ly/paper-defaults-init.ly}.
789 @item horizontal-shift
790 @funindex horizontal-shift
792 @c This default value is buried in the middle of page.scm. -mp
794 The amount that all systems (including titles and system
795 separators) are shifted to the right. Default: @code{0.0\mm}.
800 The level of indentation for the first system in a score. If the
801 paper size is modified, this dimension's default value is scaled
802 accordingly. The space within @code{line-width} available for
803 the first system is reduced by this amount. @code{indent} may also
804 be specified in @code{\layout} blocks to set indents on a
805 score-by-score basis.
808 @funindex short-indent
810 The level of indentation for all systems in a score besides the
811 first system. If the paper size is modified, this dimension's
812 default value is scaled accordingly. The space within
813 @code{line-width} available for systems other than the first is
814 reduced by this amount. @code{short-indent} may also be specified in
815 @code{\layout} blocks to set short indents on a score-by-score
822 @ref{Automatic scaling to paper size}.
825 @file{ly/paper-defaults-init.ly}.
831 @node Other paper variables
832 @subsection Other @code{@bs{}paper} variables
835 * paper variables for line breaking::
836 * paper variables for page breaking::
837 * paper variables for page numbering::
838 * Miscellaneous paper variables::
842 @node paper variables for line breaking
843 @unnumberedsubsubsec @code{@bs{}paper} variables for line breaking
847 @item max-systems-per-page
848 @funindex max-systems-per-page
850 The maximum number of systems that will be placed on a page. This
851 is currently supported only by the @code{ly:optimal-breaking} algorithm.
854 @item min-systems-per-page
855 @funindex min-systems-per-page
857 The minimum number of systems that will be placed on a page. This
858 may cause pages to be overfilled if it is made too large. This is
859 currently supported only by the @code{ly:optimal-breaking} algorithm.
862 @item systems-per-page
863 @funindex systems-per-page
865 The number of systems that should be placed on each page.
866 This is currently supported only by the @code{ly:optimal-breaking} algorithm.
870 @funindex system-count
872 The number of systems to be used for a score. Default: unset.
873 This variable can also be set in a @code{\layout} block.
882 @node paper variables for page breaking
883 @unnumberedsubsubsec @code{@bs{}paper} variables for page breaking
885 Default values not listed here are defined in
886 @file{ly/paper-defaults-init.ly}
891 @funindex page-breaking
893 The page-breaking algorithm to use. Choices are
894 @code{ly:minimal-breaking}, @code{ly:page-turn-breaking},
895 @code{ly:one-line-breaking}, @code{ly:one-line-auto-height-breaking},
896 and @code{ly:optimal-breaking} (the default).
898 @item page-breaking-system-system-spacing
899 @funindex page-breaking-system-system-spacing
901 Tricks the page breaker into thinking that
902 @code{system-system-spacing} is set to something different than
903 it really is. For example, if
904 @code{page-breaking-system-system-spacing #'padding} is set to something
905 substantially larger than @code{system-system-spacing #'padding}, then the
906 page-breaker will put fewer systems on each page. Default: unset.
911 The number of pages to be used for a score, unset by default.
915 The following variables are effective only when @code{page-breaking}
916 is set to @code{ly:page-turn-breaking}. Page breaks are then chosen
917 to minimize the number of page turns. Since page turns are required
918 on moving from an odd-numbered page to an even-numbered one, a
919 layout in which the last page is odd-numbered will usually be
920 favoured. Places where page turns are preferred can be indicated
921 manually by inserting @code{\allowPageTurn} or automatically by
922 including the @code{Page_turn_engraver} (see @ref{Optimal page turning}).
924 If there are insufficient choices available for making suitable page
925 turns, LilyPond may insert a blank page either within a score, between
926 scores (if there are two or more scores), or by ending a score on an
927 even-numbered page. The values of the following three variables may
928 be increased to make these actions less likely.
930 The values are penalties, i.e. the higher the value the less likely
931 will be the associated action relative to other choices.
935 @item blank-page-penalty
936 @funindex blank-page-penalty
938 The penalty for having a blank page in the middle of a score. If
939 @code{blank-page-penalty} is large and @code{ly:page-turn-breaking} is
940 selected, then LilyPond will be less likely to insert a page in the
941 middle of a score. Instead, it will space out the music further to
942 fill the blank page and the following one. Default: 5.
944 @item blank-last-page-penalty
945 @funindex blank-last-page-penalty
947 The penalty for ending the score on an even-numbered page. If
948 @code{blank-last-page-penalty} is large and
949 @code{ly:page-turn-breaking} is selected, then LilyPond will be less
950 likely to produce a score in which the last page is even-numbered.
951 Instead, it will adjust the spacing in order to use one page more or
952 one page less. Default: 0.
954 @item blank-after-score-page-penalty
955 @funindex blank-after-score-page-penalty
957 The penalty for having a blank page after the end of one score and
958 before the next. By default, this is smaller than
959 @code{blank-page-penalty}, so that blank pages after scores are
960 inserted in preference to blank pages within a score. Default: 2.
968 @ref{Optimal page breaking},
969 @ref{Optimal page turning},
970 @ref{Minimal page breaking},
971 @ref{One-line page breaking}.
974 @file{ly/paper-defaults-init.ly}.
977 @node paper variables for page numbering
978 @unnumberedsubsubsec @code{@bs{}paper} variables for page numbering
980 Default values not listed here are defined in
981 @file{ly/paper-defaults-init.ly}
985 @cindex page numbers, auto-numbering
986 @item auto-first-page-number
987 @funindex auto-first-page-number
989 The page breaking algorithm is affected by the first page number
990 being odd or even. If set to true, the page breaking algorithm
991 will decide whether to start with an odd or even number. This
992 will result in the first page number remaining as is or being
993 increased by one. Default: @code{#f}.
995 @cindex page numbers, specify the first
996 @item first-page-number
997 @funindex first-page-number
999 The value of the page number on the first page.
1001 @item print-first-page-number
1002 @funindex print-first-page-number
1004 If set to true, a page number is printed on the first page.
1006 @cindex page numbers, suppress
1007 @item print-page-number
1008 @funindex print-page-number
1010 If set to false, page numbers are not printed.
1012 @cindex page numbers in roman numerals
1013 @item page-number-type
1014 @funindex page-number-type
1016 The type of numerals used for page numbers. Choices include
1017 @code{roman-lower}, @code{roman-upper} and @code{arabic}.
1018 Default: @code{'arabic}.
1024 @file{ly/paper-defaults-init.ly}.
1027 Odd page numbers are always on the right. If you want the
1028 music to start on page 1 there must be a blank page on the back
1029 of the cover page so that page 1 is on the right hand side.
1032 @node Miscellaneous paper variables
1033 @unnumberedsubsubsec Miscellaneous @code{@bs{}paper} variables
1037 @item page-spacing-weight
1038 @funindex page-spacing-weight
1040 The relative importance of page (vertical) spacing and line
1041 (horizontal) spacing. High values will make page spacing more
1042 important. Default: @code{10}.
1044 @item print-all-headers
1045 @funindex print-all-headers
1047 If set to true, this will print all headers for each @code{\score}
1048 in the output. Normally only the @code{piece} and @code{opus}
1049 header variables are printed. Default: @code{#f}.
1051 @item system-separator-markup
1052 @funindex system-separator-markup
1054 A markup object that is inserted between systems, often used for
1055 orchestral scores. Default: unset. The @code{\slashSeparator}
1056 markup, defined in @file{ly/titling-init.ly}, is provided as a
1057 sensible default, for example:
1059 @lilypond[quote,verbatim,noragged-right,line-width=30\mm]
1060 #(set-default-paper-size "a8")
1064 system-separator-markup = \slashSeparator
1070 \relative { c''1 \break c1 \break c1 }
1079 @file{ly/titling-init.ly}.
1085 The default page header puts the page number and the @code{instrument}
1086 field from the @code{\header} block on a line.
1090 @section Score layout
1092 This section discusses score layout options for the @code{\layout}
1096 * The layout block::
1097 * Setting the staff size::
1101 @node The layout block
1102 @subsection The @code{@bs{}layout} block
1106 While the @code{\paper} block contains settings that relate to the
1107 page formatting of the whole document, the @code{\layout} block
1108 contains settings for score-specific layout. To set score layout
1109 options globally, enter them in a toplevel @code{\layout} block.
1110 To set layout options for an individual score, enter them in a
1111 @code{\layout} block inside the @code{\score} block, after the
1112 music. Settings that can appear in a @code{\layout} block
1116 @item the @code{layout-set-staff-size} scheme function,
1117 @item context modifications in @code{\context} blocks, and
1118 @item @code{\paper} variables that affect score layout.
1121 The @code{layout-set-staff-size} function is discussed in the next
1122 section, @ref{Setting the staff size}. Context modifications are
1123 discussed in a separate chapter; see
1124 @ref{Modifying context plug-ins} and
1125 @ref{Changing context default settings}.
1127 The @code{\paper} variables that can appear in a @code{\layout}
1128 block, with default values taken from the @code{\paper} block are:
1133 @code{line-width}, @code{ragged-right} and @code{ragged-last}
1134 (see @ref{paper variables for widths and margins,,@code{@bs{}paper} variables for widths and margins})
1137 @code{indent} and @code{short-indent}
1138 (see @ref{paper variables for shifts and indents,,@code{@bs{}paper} variables for shifts and indents})
1142 (see @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking})
1146 Here is an example @code{\layout} block:
1153 \override StaffGrouper.staff-staff-spacing.basic-distance = #8
1157 \override TextScript.padding = #1
1158 \override Glissando.thickness = #3
1163 Multiple @code{\layout} blocks can be entered as toplevel expressions.
1164 This can, for example, be useful if different settings are stored in
1165 separate files and included optionally. Internally, when
1166 a @code{\layout} block is evaluated, a copy of the current
1167 @code{\layout} configuration is made, then any changes defined within
1168 the block are applied and the result is saved as the new current
1169 configuration. From the user's perspective the @code{\layout} blocks
1170 are combined, but in conflicting situations (when the same property
1171 is changed in different blocks) the later definitions take precedence.
1173 For example, if this block:
1179 \override TextScript.color = #magenta
1180 \override Glissando.thickness = #1.5
1185 is placed after the one from the preceding example the @code{'padding}
1186 and @code{'color} overrides for @code{TextScript} are combined, but
1187 the later @code{'thickness} override for @code{Glissando} replaces
1188 (or hides) the earlier one.
1190 @code{\layout} blocks may be assigned to variables for reuse later,
1191 but the way this works is slightly but significantly different from
1192 writing them literally.
1194 If a variable is defined like this:
1197 layoutVariable = \layout @{
1200 \override NoteHead.font-size = #4
1205 it will hold the current @code{\layout} configuration with the
1206 @code{NoteHead.font-size} override added, but this combination
1207 is @emph{not} saved as the new current configuration. Be aware
1208 that the @q{current configuration} is read when the variable is
1209 defined and not when it is used, so the content of the variable
1210 is dependent on its position in the source.
1212 The variable can then be used inside another @code{\layout} block,
1220 \override NoteHead.color = #red
1225 A @code{\layout} block containing a variable, as in the example above,
1226 does @emph{not} copy the current configuration but instead uses the
1227 content of @code{\layoutVariable} as the base configuration for the
1228 further additions. This means that any changes defined between the
1229 definition and the use of the variable are lost.
1231 If @code{layoutVariable} is defined (or @code{\include}d) immediately
1232 before being used, its content is just the current configuration plus
1233 the overrides defined within it. So in the example above showing the
1234 use of @code{\layoutVariable} the final @code{\layout} block would
1238 TextScript.padding = #1
1239 TextScript.color = #magenta
1240 Glissando.thickness = #1.5
1241 NoteHead.font-size = #4
1242 NoteHead.color = #red
1245 plus the @code{indent} and the @code{StaffGrouper} overrides.
1247 But if the variable had already been defined before the first
1248 @code{\layout} block the current configuration would now contain
1252 NoteHead.font-size = #4 % (written in the variable definition)
1253 NoteHead.color = #red % (added after the use of the variable)
1256 If carefully planned, @code{\layout} variables can be a valuable tool
1257 to structure the layout design of sources, and also to reset the
1258 @code{\layout} configuration to a known state.
1262 @ref{Changing context default settings}.
1268 @node Setting the staff size
1269 @subsection Setting the staff size
1271 @cindex font size, setting
1272 @cindex staff size, setting
1273 @funindex layout file
1274 @funindex magnification->font-size
1276 @funindex set-global-staff-size
1277 @funindex layout-set-staff-size
1279 The default @strong{staff size} is 20 points, which corresponds to
1280 a staff height of 7.03mm (one point is equal to 100/7227 of an
1281 inch, or 2540/7227 mm). The staff size may be changed in three
1287 To set the staff size globally for all scores in a file (or in a
1288 @code{\book} block, to be precise), use
1289 @code{set-global-staff-size}:
1292 #(set-global-staff-size 14)
1296 The above example sets the global default staff size to 14pt
1297 (4.92mm) and scales all fonts accordingly.
1300 To set the staff size for a single score within a book, use
1301 @code{layout-set-staff-size} inside that score's @code{\layout}
1308 #(layout-set-staff-size 14)
1314 To set the staff size for a single staff within a system, use the
1315 @code{\magnifyStaff} command. For example, traditionally engraved
1316 chamber music scores with piano often used 7mm piano staves while
1317 the other staves were typically between 3/5 and 5/7 as large
1318 (between 60% and 71%). To achieve the 5/7 proportion, use:
1326 \new PianoStaff @{ @dots{} @}
1331 If you happen to know which @code{fontSize} you wish to use, you
1332 could use the following form:
1338 \magnifyStaff #(magstep -3)
1340 \new PianoStaff @{ @dots{} @}
1345 To emulate the look of traditional engraving, it is best to avoid
1346 reducing the thickness of the staff lines.
1351 @subheading Automatic font weight at different sizes
1353 The Feta font provides musical symbols at eight different
1354 sizes. Each font is tuned for a different staff size: at a smaller size
1355 the font becomes heavier, to match the relatively heavier staff lines.
1356 The recommended font sizes are listed in the following table:
1358 @multitable @columnfractions .15 .2 .22 .2
1359 @item @b{font name} @tab @b{staff height (pt)} @tab @b{staff height (mm)} @tab @b{use}
1360 @item feta11 @tab 11.22 @tab 3.9 @tab pocket scores
1361 @item feta13 @tab 12.60 @tab 4.4 @tab
1362 @item feta14 @tab 14.14 @tab 5.0 @tab
1363 @item feta16 @tab 15.87 @tab 5.6 @tab
1364 @item feta18 @tab 17.82 @tab 6.3 @tab song books
1365 @item feta20 @tab 20 @tab 7.0 @tab standard parts
1366 @item feta23 @tab 22.45 @tab 7.9 @tab
1367 @item feta26 @tab 25.2 @tab 8.9 @tab @c modern rental material?
1372 @ref{Selecting notation font size}.
1378 @code{layout-set-staff-size} does not change the distance between the
1392 @subsection Line breaking
1396 @funindex \autoBreaksOff
1397 @funindex \autoBreaksOn
1398 @funindex \autoLineBreaksOff
1399 @funindex \autoLineBreaksOn
1400 @cindex manual line breaks
1401 @cindex breaking lines
1403 Line breaks are normally determined automatically. They are
1404 chosen so that lines look neither cramped nor loose, and
1405 consecutive lines have similar density.
1407 To manually force a line break at a bar line, use the
1408 @code{\break} command:
1410 @lilypond[quote,ragged-right,verbatim]
1417 By default, a @code{\break} in the middle of a measure is ignored,
1418 and a warning is printed. To force a line break in the middle of
1419 a measure, add an invisible bar line with @w{@samp{\bar ""}}:
1421 @lilypond[quote,ragged-right,verbatim]
1430 A @code{\break} occurring at a bar line is also ignored if the
1431 previous measure ends in the middle of a note, such as when a
1432 tuplet begins and ends in different measures. To allow
1433 @code{\break} commands to work in these situations, remove the
1434 @code{Forbid_line_break_engraver} from the @code{Voice} context.
1435 Note that manually forced line breaks have to be added in parallel
1438 @lilypond[quote,ragged-right,verbatim]
1440 \remove "Forbid_line_break_engraver"
1443 { c''2. \tuplet 3/2 { c4 c c } c2. | }
1444 { s1 | \break s1 | }
1449 Similarly, line breaks are normally forbidden when beams cross bar
1450 lines. This behavior can be changed by setting
1451 @code{\override Beam.breakable = ##t}:
1453 @lilypond[quote,ragged-right,verbatim]
1455 \override Beam.breakable = ##t
1461 The @code{\noBreak} command forbids a line break at the bar line
1462 where it is inserted.
1464 Within a score, automatic line breaking is prevented within music
1465 lying between @code{\autoLineBreaksOff} and @code{\autoLineBreaksOn}
1466 commands. If automatic page breaks should also be prevented, the
1467 commands @code{\autoBreaksOff} and @code{\autoBreaksOn} should be
1468 used. Manual breaks are unaffected by these commands. Note that
1469 inhibiting automatic line breaks may cause music to run over the
1470 right margin if it cannot all be contained within one line.
1472 Automatic line breaks (but not page breaks) may be enabled at single
1473 bar lines by using @code{\once \autoLineBreaksOn} at a bar line.
1474 This identifies a permitted rather than a forced line break.
1476 The most basic settings influencing line spacing are @code{indent}
1477 and @code{line-width}. They are set in the @code{\layout} block.
1478 They control the indentation of the first line of music, and the
1479 lengths of the lines.
1481 If @code{ragged-right} is set to true in the @code{\layout} block,
1482 then systems end at their natural horizontal length, instead of
1483 being spread horizontally to fill the whole line. This is useful
1484 for short fragments, and for checking how tight the natural
1487 @c TODO Check and add para on default for ragged-right
1489 The option @code{ragged-last} is similar to @code{ragged-right},
1490 but affects only the last line of the piece.
1500 @cindex regular line breaks
1501 @cindex four bar music.
1503 For line breaks at regular intervals use @code{\break} separated
1504 by skips and repeated with @code{\repeat}. For example, this
1505 would cause the following 28 measures (assuming 4/4 time) to be
1506 broken every 4 measures, and only there:
1511 s1 \noBreak s1 \noBreak
1512 s1 \noBreak s1 \break
1514 @{ @var{the actual music@dots{}} @}
1522 @code{\autoBreaksOff},
1523 @code{\autoBreaksOn},
1524 @code{\autoLineBreaksOff},
1525 @code{\autoLineBreaksOn}.
1530 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
1531 {using-an-extra-voice-for-breaks.ly}
1535 @ref{paper variables for line breaking}
1536 @ref{The layout block}.
1541 Internals Reference:
1542 @rinternals{LineBreakEvent}.
1546 Placing @code{\autoLineBreaksOff} or @code{\autoBreaksOff} before
1547 any music will cause error messages to appear. Always place these
1548 commands after some music.
1552 @subsection Page breaking
1554 This section describes the different page breaking methods, and
1558 * Manual page breaking::
1559 * Optimal page breaking::
1560 * Minimal page breaking::
1561 * One-line page breaking::
1562 * One-line-auto-height page breaking::
1563 * Optimal page turning::
1567 @node Manual page breaking
1568 @unnumberedsubsubsec Manual page breaking
1570 @funindex \pageBreak
1571 @funindex \noPageBreak
1572 @funindex \autoPageBreaksOn
1573 @funindex \autoPageBreaksOff
1574 @cindex page breaking, manual
1576 The default page breaking may be overridden by inserting
1577 @code{\pageBreak} or @code{\noPageBreak} commands. These commands
1578 are analogous to @code{\break} and @code{\noBreak}. They should
1579 be inserted at a bar line. These commands force and forbid a
1580 page-break from happening at that bar line. Of course, the
1581 @code{\pageBreak} command also forces a line break.
1583 The @code{\pageBreak} and @code{\noPageBreak} commands may also be
1584 inserted at top-level, between scores and top-level markups.
1586 Within a score, automatic page breaks are prevented within music
1587 lying between @code{\autoPageBreaksOff} and @code{\autoPageBreaksOn}
1588 commands. Manual page breaks are unaffected by these commands.
1590 There are also analogous settings to @code{ragged-right} and
1591 @code{ragged-last} which have the same effect on vertical spacing.
1592 If @code{ragged-bottom} is set to @code{#t} the systems will not
1593 be justified vertically. When @code{ragged-last-bottom} is set
1594 to @code{#t}, as it is by default, empty space is allowed at the
1595 bottom of the final page (or the final page in each
1596 @code{\bookpart}). See
1597 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables}.
1599 Page breaks are computed by the @code{page-breaking} function.
1600 LilyPond provides several algorithms for computing page breaks,
1601 including @code{ly:optimal-breaking}, @code{ly:page-turn-breaking} and
1602 @code{ly:minimal-breaking}. The default is
1603 @code{ly:optimal-breaking}, but the value can be changed in the
1604 @code{\paper} block:
1608 page-breaking = #ly:page-turn-breaking
1614 When a book has many scores and pages, the page breaking problem
1615 may be difficult to solve, requiring large processing time and
1616 memory. To ease the page breaking process, @code{\bookpart}
1617 blocks are used to divide the book into several parts: the page
1618 breaking occurs separately on each part. Different page breaking
1619 functions may also be used in different book parts.
1624 subtitle = "Preface"
1627 %% In a part consisting mostly of text,
1628 %% ly:minimal-breaking may be preferred
1629 page-breaking = #ly:minimal-breaking
1631 \markup @{ @dots{} @}
1635 %% In this part, consisting of music, the default optimal
1636 %% page breaking function is used.
1638 subtitle = "First movement"
1640 \score @{ @dots{} @}
1648 @code{\noPageBreak},
1649 @code{\autoPageBreaksOn},
1650 @code{\autoPageBreaksOff}.
1655 @ref{paper variables for page breaking}.
1662 The @code{\once} prefix is ineffective with @code{\autoPageBreaksOn}
1663 and @code{\autoPageBreaksOff}. If auto page breaking is off and is
1664 then turned on to permit a page break, it must remain on for a few
1665 bars (the precise number of bars depends on the score) before being
1666 turned off, else the opportunity to break the page will not be taken.
1668 @node Optimal page breaking
1669 @unnumberedsubsubsec Optimal page breaking
1671 @funindex ly:optimal-breaking
1673 The @code{ly:optimal-breaking} function is LilyPond's default
1674 method of determining page breaks. It attempts to find a page
1675 breaking that minimizes cramping and stretching, both horizontally
1676 and vertically. Unlike @code{ly:page-turn-breaking}, it has no
1677 concept of page turns.
1684 @node Minimal page breaking
1685 @unnumberedsubsubsec Minimal page breaking
1687 @funindex ly:minimal-breaking
1689 The @code{ly:minimal-breaking} function performs minimal
1690 computations to calculate the page breaking: it fills a page with
1691 as many systems as possible before moving to the next one. Thus,
1692 it may be preferred for scores with many pages, where the other
1693 page breaking functions could be too slow or memory demanding, or
1694 a lot of texts. It is enabled using:
1698 page-breaking = #ly:minimal-breaking
1707 @node One-line page breaking
1708 @unnumberedsubsubsec One-line page breaking
1710 @funindex ly:one-line-breaking
1712 The @code{ly:one-line-breaking} function is a special-purpose
1713 page breaking algorithm that puts each score on its own page, and
1714 on a single line. No titles or margins are typeset; only the score is
1717 The page width is adjusted so that the longest score fits on
1718 one line. In particular, @code{paper-width}, @code{line-width}
1719 and @code{indent} variables in the @code{\paper} block are ignored,
1720 although @code{left-margin} and @code{right-margin} are still honored.
1721 The height of the page is left unmodified.
1724 @node One-line-auto-height page breaking
1725 @unnumberedsubsubsec One-line-auto-height page breaking
1727 @funindex ly:one-line-auto-height-breaking
1729 The @code{ly:one-line-auto-height-breaking} function works just like
1730 @code{ly:one-line-breaking} except the page height is automatically
1731 modified to fit the height of the music. Specifically, the
1732 @code{paper-height} variable in the @code{\paper} block is set so that
1733 it spans the height of the tallest score plus the @code{top-margin} and
1734 @code{bottom-margin}.
1736 Note that the @code{top-system-spacing} setting will affect the
1737 vertical position of the music. Set it to @code{##f} in a paper block
1738 to simply place the music between the top and bottom margins.
1741 @node Optimal page turning
1742 @unnumberedsubsubsec Optimal page turning
1744 @funindex ly:page-turn-breaking
1746 Often it is necessary to find a page breaking configuration so
1747 that there is a rest at the end of every second page. This way,
1748 the musician can turn the page without having to miss notes. The
1749 @code{ly:page-turn-breaking} function attempts to find a page
1750 breaking minimizing cramping and stretching, but with the
1751 additional restriction that it is only allowed to introduce page
1752 turns in specified places.
1754 There are two steps to using this page breaking function. First,
1755 you must enable it in the @code{\paper} block, as explained in
1756 @ref{Page breaking}. Then you must tell the function where you
1757 would like to allow page breaks.
1759 There are two ways to achieve the second step. First, you can
1760 specify each potential page turn manually, by inserting
1761 @code{\allowPageTurn} into your input file at the appropriate
1764 If this is too tedious, you can add a @code{Page_turn_engraver} to
1765 a Staff or Voice context. The @code{Page_turn_engraver} will scan
1766 the context for sections without notes (note that it does not scan
1767 for rests; it scans for the absence of notes. This is so that
1768 single-staff polyphony with rests in one of the parts does not
1769 throw off the @code{Page_turn_engraver}). When it finds a
1770 sufficiently long section without notes, the
1771 @code{Page_turn_engraver} will insert an @code{\allowPageTurn} at
1772 the final bar line in that section, unless there is a @q{special}
1773 bar line (such as a double bar), in which case the
1774 @code{\allowPageTurn} will be inserted at the final @q{special}
1775 bar line in the section.
1777 @funindex minimumPageTurnLength
1778 The @code{Page_turn_engraver} reads the context property
1779 @code{minimumPageTurnLength} to determine how long a note-free
1780 section must be before a page turn is considered. The default
1781 value for @code{minimumPageTurnLength} is
1782 @code{(ly:make-moment 1/1)}. If you want to disable page turns,
1783 set it to something @q{very large}.
1786 \new Staff \with @{ \consists "Page_turn_engraver" @}
1789 R1 | % a page turn will be allowed here
1791 \set Staff.minimumPageTurnLength = #(ly:make-moment 5/2)
1792 R1 | % a page turn will not be allowed here
1794 R1*2 | % a page turn will be allowed here
1799 @funindex minimumRepeatLengthForPageTurn
1800 With volta repeats, the @code{Page_turn_engraver} will only
1801 allow a page turn during the repeat if there is enough time at the
1802 beginning and end of the repeat to turn the page back. If the
1803 repeat is very short, the @code{Page_turn_engraver} can also be
1804 used to disable page turns by setting a value for the context
1805 property @code{minimumRepeatLengthForPageTurn} where as
1806 @code{Page_turn_engraver} only allows turns in repeats whose
1807 duration is longer than this value.
1809 The page turning commands, @code{\pageTurn}, @code{\noPageTurn}
1810 and @code{\allowPageTurn}, may also be used at top-level, in
1811 top-level markups and between scores.
1816 @funindex \noPageTurn
1818 @funindex \allowPageTurn
1819 @code{\allowPageTurn}.
1824 @ref{paper variables for line breaking}.
1830 Use only one @code{Page_turn_engraver} per score. If there are
1831 more, they will interfere with each other.
1836 @ref{Vertical spacing}.
1842 @node Vertical spacing
1843 @section Vertical spacing
1845 @cindex vertical spacing
1846 @cindex spacing, vertical
1848 Vertical spacing is controlled by three things: the amount of
1849 space available (i.e., paper size and margins), the amount of
1850 space between systems, and the amount of space between staves
1854 * Flexible vertical spacing within systems::
1855 * Explicit staff and system positioning::
1856 * Vertical collision avoidance::
1860 @node Flexible vertical spacing within systems
1861 @subsection Flexible vertical spacing within systems
1863 @cindex distance between staves
1864 @cindex staff distance
1865 @cindex space between staves
1866 @cindex space inside systems
1868 Three separate mechanisms control the flexible vertical spacing
1869 within systems, one for each of the following categories:
1874 @emph{ungrouped staves},
1877 @emph{grouped staves} (staves within a staff-group such as
1878 @code{ChoirStaff}, etc.), and
1881 @emph{non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
1886 @c TODO: Clarify this. This almost implies that non-staff lines
1887 @c have NO effect on the spacing between staves. -mp
1889 The height of each system is determined in two steps. First, all
1890 of the staves are spaced according to the amount of space
1891 available. Then, the non-staff lines are distributed between the
1894 Note that the spacing mechanisms discussed in this section only
1895 control the vertical spacing of staves and non-staff lines within
1896 individual systems. The vertical spacing between separate
1897 systems, scores, markups, and margins is controlled by
1898 @code{\paper} variables, which are discussed in
1899 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables}.
1902 * Within-system spacing properties::
1903 * Spacing of ungrouped staves::
1904 * Spacing of grouped staves::
1905 * Spacing of non-staff lines::
1909 @node Within-system spacing properties
1910 @unnumberedsubsubsec Within-system spacing properties
1912 @funindex staff-affinity
1913 @funindex staffgroup-staff-spacing
1914 @funindex staff-staff-spacing
1915 @funindex nonstaff-unrelatedstaff-spacing
1916 @funindex nonstaff-relatedstaff-spacing
1917 @funindex nonstaff-nonstaff-spacing
1918 @funindex default-staff-staff-spacing
1919 @funindex minimum-Y-extent
1920 @funindex extra-offset
1921 @funindex self-alignment-X
1923 @funindex VerticalAxisGroup
1925 The within-system vertical spacing mechanisms are controlled by
1926 two sets of grob properties. The first set is associated with the
1927 @code{VerticalAxisGroup} grob, which is created by all staves and
1928 non-staff lines. The second set is associated with the
1929 @code{StaffGrouper} grob, which can be created by staff-groups,
1930 but only if explicitly called. These properties are described
1931 individually at the end of this section.
1933 The names of these properties (except for @code{staff-affinity})
1934 follow the format @code{@var{item1}-@var{item2}-spacing}, where
1935 @code{@var{item1}} and @code{@var{item2}} are the items to be
1936 spaced. Note that @code{@var{item2}} is not necessarily below
1937 @code{@var{item1}}; for example,
1938 @code{nonstaff-relatedstaff-spacing} will measure upwards from the
1939 non-staff line if @code{staff-affinity} is @code{UP}.
1941 Each distance is measured between the @emph{reference points} of
1942 the two items. The reference point for a staff is the vertical
1943 center of its @code{StaffSymbol} (i.e. the middle line if
1944 @code{line-count} is odd; the middle space if @code{line-count} is
1945 even). The reference points for individual non-staff lines are
1946 given in the following table:
1948 @multitable {Non-staff line} {Reference point}
1949 @headitem Non-staff line @tab Reference point
1950 @item @code{ChordNames} @tab baseline
1951 @item @code{NoteNames} @tab baseline
1952 @item @code{Lyrics} @tab baseline
1953 @item @code{Dynamics} @tab mid-height of @q{m}
1954 @item @code{FiguredBass} @tab highest point
1955 @item @code{FretBoards} @tab top line
1958 In the following image, horizontal lines indicate the positions
1959 of these reference points:
1961 @lilypond[quote,noragged-right,line-width=110\mm]
1962 #(define zero-space '((padding . -inf.0) (basic-distance . 0)))
1964 alignToZero = \with {
1965 \override VerticalAxisGroup.nonstaff-relatedstaff-spacing = #zero-space
1966 \override VerticalAxisGroup.nonstaff-nonstaff-spacing = #zero-space
1967 \override VerticalAxisGroup.staff-affinity = #DOWN
1968 \remove Text_engraver % avoid having two
1969 \consists Text_engraver
1971 lowerCaseChords = \with {
1972 chordNameLowercaseMinor = ##t
1975 #(define-music-function
1978 #{ s1*0^\markup { \upright {\typewriter #context } } #})
1981 \context { \Dynamics \alignToZero }
1982 \context { \FiguredBass \alignToZero }
1983 \context { \Lyrics \alignToZero }
1984 \context { \NoteNames \alignToZero }
1985 \context { \ChordNames \alignToZero \lowerCaseChords }
1986 \context { \FretBoards \alignToZero }
1989 \override DynamicText.self-alignment-X = #-1
1990 \override FretBoard.X-offset = #1.75
1991 \override InstrumentName.minimum-Y-extent = #'(-1 . 2)
1997 %% These contexts have reference points at the baseline:
1998 %% ChordNames, NoteNames, and Lyrics
2000 \new ChordNames { \chords { \labelContext "ChordNames" g1:m } }
2001 \new NoteNames { s1 |\labelContext "NoteNames" g1 | }
2002 \new Lyrics { \lyrics { \skip 1*2 | \labelContext "Lyrics" ghijk1 | } }
2003 \new RhythmicStaff \with { instrumentName = #"baseline " } s1*3
2006 %% The reference point for Dynamics is the midline of 'm' in the font
2008 \new Dynamics { \labelContext "Dynamics" s1\mp s\fp }
2009 \new RhythmicStaff \with { instrumentName = #"mid-height " } s1*3
2012 %% The reference point for FiguredBass is its highest point
2014 \new FiguredBass { \labelContext "FiguredBass" \figuremode { <6 5>1 } }
2015 \new RhythmicStaff \with { instrumentName = #"highest point " } s1
2018 %% The reference point for FretBoards is the top line
2019 \include "predefined-guitar-fretboards.ly"
2021 \new FretBoards { \labelContext "FretBoards" \chordmode { e1 } }
2022 \new RhythmicStaff \with { instrumentName = #"top line " } s1
2026 Each of the vertical spacing grob properties (except
2027 @code{staff-affinity}) uses the same alist structure as the
2028 @code{\paper} spacing variables discussed in
2029 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables}.
2031 for modifying alists are discussed in @ref{Modifying alists}.
2032 Grob properties should be adjusted with an @code{\override} inside
2033 a @code{\score} or @code{\layout} block, and not inside a
2034 @code{\paper} block.
2036 The following example demonstrates the two ways these alists can
2037 be modified. The first declaration updates one key-value
2038 individually, and the second completely re-defines the property:
2042 \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #10
2046 \override VerticalAxisGroup.default-staff-staff-spacing =
2047 #'((basic-distance . 10)
2048 (minimum-distance . 9)
2050 (stretchability . 10))
2054 To change any spacing settings globally, put them in the
2055 @code{\layout} block:
2061 \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #10
2066 Standard settings for the vertical spacing grob properties are
2067 listed in @rinternals{VerticalAxisGroup} and
2068 @rinternals{StaffGrouper}. Default overrides for specific types
2069 of non-staff lines are listed in the relevant context descriptions
2070 in @rinternals{Contexts}.
2073 @subsubheading Properties of the @code{VerticalAxisGroup} grob
2075 @code{VerticalAxisGroup} properties are typically adjusted with an
2076 @code{\override} at the @code{Staff} level (or equivalent).
2079 @item staff-staff-spacing
2081 Used to determine the distance between the current staff and the
2082 staff just below it in the same system, even if one or more
2083 non-staff lines (such as @code{Lyrics}) are placed between the two
2084 staves. Does not apply to the bottom staff of a system.
2086 Initially, the @code{staff-staff-spacing} of a
2087 @code{VerticalAxisGroup} is a Scheme function that applies the
2088 properties of the @code{StaffGrouper} if the staff is part of a
2089 group, or the @code{default-staff-staff-spacing} of the staff
2090 otherwise. This allows staves to be spaced differently when they
2091 are grouped. For uniform spacing regardless of grouping, this
2092 function may be replaced by a flexible-spacing alist, using the
2093 complete-redefinition form of override shown above.
2095 @item default-staff-staff-spacing
2096 A flexible-spacing alist defining the @code{staff-staff-spacing} used for
2097 ungrouped staves, unless @code{staff-staff-spacing} has been explicitly
2098 set with an @code{\override}.
2100 @item staff-affinity
2101 The direction of the staff to use for spacing the current
2102 non-staff line. Choices are @code{UP}, @code{DOWN}, and
2103 @code{CENTER}. If @code{CENTER}, the non-staff line will be
2104 placed equidistant between the two nearest staves on either side,
2105 unless collisions or other spacing constraints prevent this.
2106 Adjacent non-staff lines should have non-increasing
2107 @code{staff-affinity} from top to bottom, e.g. a non-staff line
2108 set to @code{UP} should not immediately follow one that is set to
2109 @code{DOWN}. Non-staff lines at the top of a system should use
2110 @code{DOWN}; those at the bottom should use @code{UP}. Setting
2111 @code{staff-affinity} for a staff causes it to be treated as a
2112 non-staff line. Setting @code{staff-affinity} to @code{#f} causes
2113 a non-staff line to be treated as a staff. Setting
2114 @code{staff-affinity} to @code{UP}, @code{CENTER}, or @code{DOWN}
2115 causes a staff to be spaced as a non-staff line.
2117 @item nonstaff-relatedstaff-spacing
2118 The distance between the current non-staff line and the nearest
2119 staff in the direction of @code{staff-affinity}, if there are no
2120 non-staff lines between the two, and @code{staff-affinity} is
2121 either @code{UP} or @code{DOWN}. If @code{staff-affinity} is
2122 @code{CENTER}, then @code{nonstaff-relatedstaff-spacing} is used
2123 for the nearest staves on @emph{both} sides, even if other
2124 non-staff lines appear between the current one and either of the
2125 staves. This means that the placement of a non-staff line depends
2126 on both the surrounding staves and the surrounding non-staff lines.
2127 Setting the @code{stretchability} of one of these types of spacing to
2128 a small value will make that spacing dominate. Setting the
2129 @code{stretchability} to a large value will make that spacing have
2132 @item nonstaff-nonstaff-spacing
2133 The distance between the current non-staff line and the next
2134 non-staff line in the direction of @code{staff-affinity}, if both
2135 are on the same side of the related staff, and
2136 @code{staff-affinity} is either @code{UP} or @code{DOWN}.
2138 @item nonstaff-unrelatedstaff-spacing
2139 The distance between the current non-staff line and the staff in
2140 the opposite direction from @code{staff-affinity}, if there are no
2141 other non-staff lines between the two, and @code{staff-affinity}
2142 is either @code{UP} or @code{DOWN}. This can be used, for
2143 example, to require a minimum amount of padding between a
2144 @code{Lyrics} line and the staff to which it does not belong.
2148 @subsubheading Properties of the @code{StaffGrouper} grob
2150 @code{StaffGrouper} properties are typically adjusted with an
2151 @code{\override} at the @code{StaffGroup} level (or equivalent).
2154 @item staff-staff-spacing
2155 The distance between consecutive staves within the current
2156 staff-group. The @code{staff-staff-spacing} property of an
2157 individual staff's @code{VerticalAxisGroup} grob can be
2158 overriden with different spacing settings for that staff.
2160 @item staffgroup-staff-spacing
2161 The distance between the last staff of the current staff-group and
2162 the staff just below it in the same system, even if one or more
2163 non-staff lines (such as @code{Lyrics}) exist between the two
2164 staves. Does not apply to the bottom staff of a system. The
2165 @code{staff-staff-spacing} property of an individual staff's
2166 @code{VerticalAxisGroup} grob can be overriden with different
2167 spacing settings for that staff.
2172 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables},
2173 @ref{Modifying alists}.
2176 @file{ly/engraver-init.ly},
2177 @file{scm/define-grobs.scm}.
2179 Internals Reference:
2180 @rinternals{Contexts},
2181 @rinternals{VerticalAxisGroup},
2182 @rinternals{StaffGrouper}.
2185 @node Spacing of ungrouped staves
2186 @unnumberedsubsubsec Spacing of ungrouped staves
2188 @emph{Staves} (such as @code{Staff}, @code{DrumStaff},
2189 @code{TabStaff}, etc.) are contexts that can contain one or more
2190 voice contexts, but cannot contain any other staves.
2192 The following properties affect the spacing of @emph{ungrouped}
2196 @item @code{VerticalAxisGroup} properties:
2198 @item @code{default-staff-staff-spacing}
2199 @item @code{staff-staff-spacing}
2203 These grob properties are described individually above; see
2204 @ref{Within-system spacing properties}.
2206 Additional properties are involved for staves that are part of a
2207 staff-group; see @ref{Spacing of grouped staves}.
2209 The following example shows how the @code{default-staff-staff-spacing}
2210 property can affect the spacing of ungrouped staves.
2211 The same overrides applied to @code{staff-staff-spacing} would
2212 have the same effect, but would also apply in cases where the staves
2213 are combined in a group or groups.
2215 @lilypond[verbatim,quote,staffsize=16]
2219 \override VerticalAxisGroup.default-staff-staff-spacing =
2220 #'((basic-distance . 8)
2221 (minimum-distance . 7)
2227 % The very low note here needs more room than 'basic-distance
2228 % can provide, so the distance between this staff and the next
2229 % is determined by 'padding.
2230 \new Staff { b,2 r | }
2232 % Here, 'basic-distance provides enough room, and there is no
2233 % need to compress the space (towards 'minimum-distance) to make
2234 % room for anything else on the page, so the distance between
2235 % this staff and the next is determined by 'basic-distance.
2236 \new Staff { \clef bass g2 r | }
2238 % By setting 'padding to a negative value, staves can be made to
2239 % collide. The lowest acceptable value for 'basic-distance is 0.
2241 \override VerticalAxisGroup.default-staff-staff-spacing =
2242 #'((basic-distance . 3.5)
2244 } { \clef bass g2 r | }
2245 \new Staff { \clef bass g2 r | }
2251 @file{scm/define-grobs.scm}.
2256 Internals Reference:
2257 @rinternals{VerticalAxisGroup}.
2260 @node Spacing of grouped staves
2261 @unnumberedsubsubsec Spacing of grouped staves
2263 In orchestral and other large scores, it is common to place staves
2264 in groups. The space between groups is typically larger than the
2265 space between staves of the same group.
2267 @emph{Staff-groups} (such as @code{StaffGroup}, @code{ChoirStaff},
2268 etc.) are contexts that can contain one or more staves
2271 The following properties affect the spacing of staves inside
2275 @item @code{VerticalAxisGroup} properties:
2277 @item @code{staff-staff-spacing}
2279 @item @code{StaffGrouper} properties:
2281 @item @code{staff-staff-spacing}
2282 @item @code{staffgroup-staff-spacing}
2286 These grob properties are described individually above; see
2287 @ref{Within-system spacing properties}.
2289 The following example shows how properties of the
2290 @code{StaffGrouper} grob can affect the spacing of grouped staves:
2292 @lilypond[verbatim,quote,staffsize=16]
2296 \override StaffGrouper.staff-staff-spacing.padding = #0
2297 \override StaffGrouper.staff-staff-spacing.basic-distance = #1
2302 \new PianoStaff \with {
2303 \override StaffGrouper.staffgroup-staff-spacing.basic-distance = #20
2318 @file{scm/define-grobs.scm}.
2323 Internals Reference:
2324 @rinternals{VerticalAxisGroup},
2325 @rinternals{StaffGrouper}.
2328 @node Spacing of non-staff lines
2329 @unnumberedsubsubsec Spacing of non-staff lines
2331 @emph{Non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
2332 etc.) are contexts whose layout objects are engraved like staves
2333 (i.e. in horizontal lines within systems). Specifically,
2334 non-staff lines are non-staff contexts that contain the
2335 @rinternals{Axis_group_engraver}.
2337 The following properties affect the spacing of non-staff lines:
2340 @item @code{VerticalAxisGroup} properties:
2342 @item @code{staff-affinity}
2343 @item @code{nonstaff-relatedstaff-spacing}
2344 @item @code{nonstaff-nonstaff-spacing}
2345 @item @code{nonstaff-unrelatedstaff-spacing}
2349 These grob properties are described individually above; see
2350 @ref{Within-system spacing properties}.
2352 The following example shows how the
2353 @code{nonstaff-nonstaff-spacing} property can affect the spacing
2354 of consecutive non-staff lines. Here, by setting the
2355 @code{stretchability} key to a very high value, the lyrics are
2356 able to stretch much more than usual:
2358 @lilypond[verbatim,quote,staffsize=16]
2362 \override VerticalAxisGroup.nonstaff-nonstaff-spacing.stretchability = #1000
2369 \override VerticalAxisGroup.staff-staff-spacing = #'((basic-distance . 30))
2372 \override VerticalAxisGroup.staff-affinity = #UP
2375 \override VerticalAxisGroup.staff-affinity = #CENTER
2376 } \lyricmode { center }
2378 \override VerticalAxisGroup.staff-affinity = #DOWN
2379 } \lyricmode { down }
2386 @file{ly/engraver-init.ly},
2387 @file{scm/define-grobs.scm}.
2392 @c @lsr{spacing,page-spacing.ly},
2393 @c @lsr{spacing,alignment-vertical-spacing.ly}.
2395 Internals Reference:
2396 @rinternals{Contexts},
2397 @rinternals{VerticalAxisGroup}.
2400 @node Explicit staff and system positioning
2401 @subsection Explicit staff and system positioning
2403 One way to understand the flexible vertical spacing mechanisms
2404 explained above is as a collection of settings that control the
2405 amount of vertical padding between staves and systems.
2407 It is possible to approach vertical spacing in a different way
2408 using @code{NonMusicalPaperColumn.line-break-system-details}.
2409 While the flexible vertical spacing mechanisms specify vertical
2410 padding, @code{NonMusicalPaperColumn.line-break-system-details}
2411 can specify exact vertical positions on the page.
2413 @code{NonMusicalPaperColumn.line-break-system-details} accepts
2414 an associative list of three different settings:
2417 @item @code{X-offset}
2418 @item @code{Y-offset}
2419 @item @code{alignment-distances}
2422 Grob overrides, including the overrides for @code{NonMusicalPaperColumn}
2423 below, can occur in any of three different places in an input file:
2426 @item in the middle of note entry directly
2427 @item in a @code{\context} block
2428 @item in the @code{\with} block
2431 When we override @code{NonMusicalPaperColumn}, we use the usual
2432 @code{\override} command in @code{\context} blocks and in the
2433 @code{\with} block. On the other hand, when we override
2434 @code{NonMusicalPaperColumn} in the middle of note entry,
2435 use the special @code{\overrideProperty} command. Here are some
2436 example @code{NonMusicalPaperColumn} overrides with the special
2437 @code{\overrideProperty} command:
2440 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2443 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2446 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2450 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2451 #'((alignment-distances . (15)))
2453 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2456 (alignment-distances . (15)))
2459 To understand how each of these different settings work, we begin
2460 by looking at an example that includes no overrides at all.
2462 @c \book { } is required in these examples to ensure the spacing
2463 @c overrides can be seen between systems. -np
2465 @lilypond[verbatim,quote,staffsize=16]
2466 \header { tagline = ##f }
2467 \paper { left-margin = 0\mm }
2477 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2480 \repeat unfold 15 { d'4 d' d' d' }
2487 This score isolates line- and page-breaking information in a dedicated
2488 voice. This technique of creating a breaks voice will help keep layout
2489 separate from music entry as our example becomes more complicated.
2492 Explicit @code{\breaks} evenly divide the music into six measures per
2493 line. Vertical spacing results from LilyPond's defaults. To set
2494 the vertical startpoint of each system explicitly, we can set
2495 the @code{Y-offset} pair in the @code{line-break-system-details}
2496 attribute of the @code{NonMusicalPaperColumn} grob:
2498 @lilypond[verbatim,quote,staffsize=16]
2499 \header { tagline = ##f }
2500 \paper { left-margin = 0\mm }
2506 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2509 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2512 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2516 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2519 \repeat unfold 15 { d'4 d' d' d' }
2526 Note that @code{line-break-system-details} takes an associative list of
2527 potentially many values, but that we set only one value here. Note,
2528 too, that the @code{Y-offset} property here determines the exact vertical
2529 position on the page at which each new system will render.
2531 Now that we have set the vertical startpoint of each system
2532 explicitly, we can also set the vertical distances between staves
2533 within each system manually. We do this using the @code{alignment-distances}
2534 subproperty of @code{line-break-system-details}.
2536 @lilypond[verbatim,quote,staffsize=16]
2537 \header { tagline = ##f }
2538 \paper { left-margin = 0\mm }
2544 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2546 (alignment-distances . (10)))
2548 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2550 (alignment-distances . (15)))
2552 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2554 (alignment-distances . (20)))
2557 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2560 \repeat unfold 15 { d'4 d' d' d' }
2567 Note that here we assign two different values to the
2568 @code{line-break-system-details} attribute of the
2569 @code{NonMusicalPaperColumn} grob. Though the
2570 @code{line-break-system-details} attribute alist accepts many
2571 additional spacing parameters (including, for example, a corresponding
2572 @code{X-offset} pair), we need only set the @code{Y-offset} and
2573 @code{alignment-distances} pairs to control the vertical startpoint of
2574 every system and every staff. Finally, note that @code{alignment-distances}
2575 specifies the vertical positioning of staves but not of staff groups.
2577 @lilypond[verbatim,quote,staffsize=16]
2578 \header { tagline = ##f }
2579 \paper { left-margin = 0\mm }
2585 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2587 (alignment-distances . (30 10)))
2589 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2591 (alignment-distances . (10 10)))
2593 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2595 (alignment-distances . (10 30)))
2598 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2601 \new Staff { \repeat unfold 15 { d'4 d' d' d' } }
2602 \new Staff { \repeat unfold 15 { e'4 e' e' e' } }
2609 Some points to consider:
2612 @item When using @code{alignment-distances}, lyrics and other non-staff lines
2613 do not count as a staff.
2615 @item The units of the numbers passed to @code{X-offset},
2616 @code{Y-offset} and @code{alignment-distances} are interpreted as multiples
2617 of the distance between adjacent staff lines. Positive values move staves
2618 and lyrics up, negative values move staves and lyrics down.
2620 @item Because the @code{NonMusicalPaperColumn.line-break-system-details}
2621 settings given here allow the positioning of staves and systems anywhere
2622 on the page, it is possible to violate paper or margin boundaries or even
2623 to print staves or systems on top of one another. Reasonable values
2624 passed to these different settings will avoid this.
2632 @node Vertical collision avoidance
2633 @subsection Vertical collision avoidance
2635 @funindex outside-staff-priority
2636 @funindex outside-staff-padding
2637 @funindex outside-staff-horizontal-padding
2639 Intuitively, there are some objects in musical notation that belong
2640 to the staff and there are other objects that should be placed outside
2641 the staff. Objects belonging outside the staff include things such as
2642 rehearsal marks, text and dynamic markings (from now on, these will
2643 be called outside-staff objects). LilyPond's rule for the
2644 vertical placement of outside-staff objects is to place them as close
2645 to the staff as possible but not so close that they collide with
2648 LilyPond uses the @code{outside-staff-priority} property to determine
2649 whether a grob is an outside-staff object: if @code{outside-staff-priority}
2650 is a number, the grob is an outside-staff object. In addition,
2651 @code{outside-staff-priority} tells LilyPond in which order the objects
2654 First, LilyPond places all the objects that do not belong outside
2655 the staff. Then it sorts the outside-staff objects according to their
2656 @code{outside-staff-priority} (in increasing order). One by one, LilyPond
2657 takes the outside-staff objects and places them so that they do
2658 not collide with any objects that have already been placed. That
2659 is, if two outside-staff grobs are competing for the same space, the one
2660 with the lower @code{outside-staff-priority} will be placed closer to
2663 A listing of outside-staff-priorities may be found in
2664 @rlearning{The outside-staff-priority property}.
2666 @lilypond[quote,ragged-right,verbatim]
2670 \once \override TextScript.outside-staff-priority = #1
2671 c4_"Text"\pp % this time the text will be closer to the staff
2673 % by setting outside-staff-priority to a non-number,
2674 % we disable the automatic collision avoidance
2675 \once \override TextScript.outside-staff-priority = ##f
2676 \once \override DynamicLineSpanner.outside-staff-priority = ##f
2677 c4_"Text"\pp % now they will collide
2681 The vertical padding around outside-staff objects
2682 can be controlled with @code{outside-staff-padding}.
2684 @lilypond[quote,ragged-right,verbatim,staffsize=18]
2686 \once \override TextScript.outside-staff-padding = #0
2687 a'4-"outside-staff-padding = #0"
2688 \once \override TextScript.outside-staff-padding = #3
2689 d-"outside-staff-padding = #3"
2690 c-"default outside-staff-padding"
2691 b-"default outside-staff-padding"
2697 By default, outside-staff objects are placed so they avoid
2698 a horizontal collision with previously-positioned grobs. This
2699 can lead to situations in which objects are placed close to each
2701 As shown in the example below, setting @code{outside-staff-horizontal-padding}
2702 increases the horizontal spacing required, and in this case moves the text up
2703 to prevent it from getting too close to the ledger lines.
2705 @lilypond[quote,ragged-right,verbatim]
2709 \once \override TextScript.outside-staff-horizontal-padding = #1
2719 @node Horizontal spacing
2720 @section Horizontal spacing
2722 @cindex horizontal spacing
2723 @cindex spacing, horizontal
2726 * Horizontal spacing overview::
2727 * New spacing area::
2728 * Changing horizontal spacing::
2730 * Proportional notation::
2734 @node Horizontal spacing overview
2735 @subsection Horizontal spacing overview
2737 The spacing engine translates differences in durations into stretchable
2738 distances (@q{springs}) of differing lengths. Longer durations get
2739 more space, shorter durations get less. The shortest durations get a
2740 fixed amount of space (which is controlled by
2741 @code{shortest-duration-space} in the @rinternals{SpacingSpanner}
2742 object). The longer the duration, the more space it gets: doubling a
2743 duration adds @code{spacing-increment} of space to the note.
2745 For example, the following piece contains lots of half, quarter, and
2746 8th notes; the eighth note is followed by 1 note head width (NHW).
2747 The quarter note is followed by 2 NHW, the half by 3 NHW, etc.
2749 @lilypond[quote,verbatim]
2757 Normally, @code{spacing-increment} is set to 1.2 staff space, which is
2758 approximately the width of a note head, and
2759 @code{shortest-duration-space} is set to 2.0, meaning that the
2760 shortest note gets 2.4 staff space (2.0 times the
2761 @code{spacing-increment}) of horizontal space. This space is counted
2762 from the left edge of the symbol, so the shortest notes are generally
2763 followed by one NHW of space.
2765 If one would follow the above procedure exactly, then adding a single
2766 32nd note to a score that uses 8th and 16th notes, would widen up the
2767 entire score a lot. The shortest note is no longer a 16th, but a 32nd,
2768 thus adding 1 NHW to every note. To prevent this, the shortest
2769 duration for spacing is not the shortest note in the score, but rather
2770 the one which occurs most frequently.
2773 The most common shortest duration is determined as follows: in every
2774 measure, the shortest duration is determined. The most common shortest
2775 duration is taken as the basis for the spacing, with the stipulation
2776 that this shortest duration should always be equal to or shorter than
2779 These durations may also be customized. If you set the
2780 @code{common-shortest-duration} in @rinternals{SpacingSpanner}, then
2781 this sets the base duration for spacing. The maximum duration for this
2782 base (normally an 8th), is set through @code{base-shortest-duration}.
2784 @funindex common-shortest-duration
2785 @funindex base-shortest-duration
2786 @funindex stem-spacing-correction
2789 Notes that are even shorter than the common shortest note are
2790 followed by a space that is proportional to their duration relative to
2791 the common shortest note. So if we were to add only a few 16th notes
2792 to the example above, they would be followed by half a NHW:
2794 @lilypond[quote,verbatim]
2795 \relative { c''2 c4. c8 | c4. c16[ c] c4. c8 | c8 c c4 c c }
2799 In the @emph{Essay on automated music engraving}, it was explained
2800 that stem directions influence spacing (see
2801 @ressay{Optical spacing}). This is controlled with the
2802 @code{stem-spacing-correction} property in the
2803 @rinternals{NoteSpacing}, object. These are generated for every
2804 @rinternals{Voice} context. The @code{StaffSpacing} object
2805 (generated in @rinternals{Staff} context) contains the same
2806 property for controlling the stem/bar line spacing. The following
2807 example shows these corrections, once with default settings, and
2808 once with exaggerated corrections:
2810 @lilypond[quote,ragged-right]
2814 \override Staff.NoteSpacing.stem-spacing-correction = #1.5
2815 \override Staff.StaffSpacing.stem-spacing-correction = #1.5
2821 Proportional notation is supported; see @ref{Proportional notation}.
2824 Essay on automated music engraving:
2825 @ressay{Optical spacing}.
2830 Internals Reference:
2831 @rinternals{SpacingSpanner},
2832 @rinternals{NoteSpacing},
2833 @rinternals{StaffSpacing},
2834 @rinternals{NonMusicalPaperColumn}.
2837 There is no convenient mechanism to manually override spacing. The
2838 following work-around may be used to insert extra space into a score,
2839 adjusting the padding value as necessary.
2842 \override Score.NonMusicalPaperColumn.padding = #10
2845 No work-around exists for decreasing the amount of space.
2848 @node New spacing area
2849 @subsection New spacing area
2851 @funindex \newSpacingSection
2852 @cindex new spacing area
2853 @cindex spacing area, new
2854 @cindex notes, spacing horizontally
2856 New sections with different spacing parameters can be started with
2857 @code{newSpacingSection}. This is useful when there are
2858 sections with a different notions of long and short notes.
2860 In the following example, the time signature change introduces a new
2861 section, and hence the 16ths notes are automatically spaced slightly
2864 @lilypond[verbatim,quote]
2868 c8 c c4 c16[ c c8] c4
2875 The @code{\newSpacingSection} command creates a new
2876 @code{SpacingSpanner} object at that musical moment.
2877 If the automatic spacing adjustments do not give the required spacing,
2878 manual @code{\override}s may be applied to its properties. These must
2879 be applied at the same musical moment as the @code{\newSpacingSection}
2880 command itself. They will then affect the spacing of all the following
2881 music until the properties are changed in a new spacing section, for
2884 @lilypond[verbatim,quote]
2889 \override Score.SpacingSpanner.spacing-increment = #2
2892 \revert Score.SpacingSpanner.spacing-increment
2902 Internals Reference:
2903 @rinternals{SpacingSpanner}.
2906 @node Changing horizontal spacing
2907 @subsection Changing horizontal spacing
2909 Horizontal spacing may be altered with the
2910 @code{base-shortest-duration} property. Here
2911 we compare the same music; once without altering
2912 the property, and then altered. Larger values
2913 of @code{ly:make-moment} will produce smaller
2914 music. Note that @code{ly:make-moment} constructs
2915 a duration, so @code{1 4} is a longer duration
2918 @lilypond[verbatim,line-width=12\cm]
2921 g'4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2922 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2923 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2924 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2929 @lilypond[verbatim,line-width=12\cm]
2932 g'4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2933 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2934 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2935 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2940 \override SpacingSpanner.base-shortest-duration = #(ly:make-moment 1/16)
2949 By default, spacing in tuplets depends on various non-duration
2950 factors (such as accidentals, clef changes, etc). To disregard
2951 such symbols and force uniform equal-duration spacing, use
2952 @code{Score.SpacingSpanner.uniform-stretching}. This
2953 property can only be changed at the beginning of a score,
2955 @lilypond[quote,ragged-right,verbatim]
2959 \tuplet 5/4 { c8 c c c c } c8 c c c
2962 c8 c c c \tuplet 5/4 { c8 c c c c }
2968 \override SpacingSpanner.uniform-stretching = ##t
2974 When @code{strict-note-spacing} is set, notes are spaced without
2975 regard for clefs, bar lines, and grace notes,
2977 @lilypond[quote,ragged-right,fragment,verbatim]
2978 \override Score.SpacingSpanner.strict-note-spacing = ##t
2979 \new Staff \relative {
2980 c''8[ c \clef alto c \grace { c16 c } c8 c c] c32[ c] }
2989 @subsection Line width
2992 @cindex breaking pages
2995 @funindex line-width
2996 @funindex ragged-right
2997 @funindex ragged-last
2999 @c Although line-width can be set in \layout, it should be set in paper
3000 @c block, to get page layout right.
3001 @c Setting indent in \paper block makes not much sense, but it works.
3003 @c Bit verbose and vague, use examples?
3004 The most basic settings influencing the spacing are @code{indent} and
3005 @code{line-width}. They are set in the @code{\layout} block. They
3006 control the indentation of the first line of music, and the lengths of
3009 If @code{ragged-right} is set to true in the @code{\layout} block, then
3010 systems ends at their natural horizontal length, instead of being spread
3011 horizontally to fill the whole line. This is useful for
3012 short fragments, and for checking how tight the natural spacing is.
3013 The normal default setting is false, but if the score has only one
3014 system the default value is true.
3017 @cindex vertical spacing
3019 The option @code{ragged-last} is similar to @code{ragged-right}, but
3020 only affects the last line of the piece. No restrictions are put on
3021 that line. The result is similar to formatting text paragraphs. In a
3022 paragraph, the last line simply takes its natural horizontal length.
3023 @c Note that for text there are several options for the last line.
3024 @c While Knuth TeX uses natural length, lead typesetters use the same
3025 @c stretch as the previous line. eTeX uses \lastlinefit to
3026 @c interpolate between both these solutions.
3041 @node Proportional notation
3042 @subsection Proportional notation
3044 LilyPond supports proportional notation, a type of horizontal spacing
3045 in which each note consumes an amount of horizontal space exactly
3046 equivalent to its rhythmic duration. This type of proportional spacing
3047 is comparable to horizontal spacing on top of graph paper. Some late
3048 20th- and early 21st-century scores use proportional notation to
3049 clarify complex rhythmic relationships or to facilitate the placement
3050 of timelines or other graphics directly in the score.
3052 LilyPond supports five different settings for proportional notation,
3053 which may be used together or alone:
3056 @item @code{proportionalNotationDuration}
3057 @item @code{uniform-stretching}
3058 @item @code{strict-note-spacing}
3059 @item @code{\remove "Separating_line_group_engraver"}
3060 @item @code{\override PaperColumn.used = ##t}
3063 In the examples that follow, we explore these five different
3064 proportional notation settings and examine how these settings interact.
3066 We start with the following one-measure example, which uses classical
3067 spacing with ragged-right turned on.
3069 @c The initial pitch is not necessary as long as RhythmicStaff is
3070 @c not preceded by other material in the score, but we don't want
3072 @lilypond[quote,verbatim,ragged-right]
3075 \new RhythmicStaff {
3076 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3082 Notice that the half note which begins the measure takes up far less
3083 than half of the horizontal space of the measure. Likewise, the
3084 sixteenth notes and sixteenth-note quintuplets (or twentieth notes)
3085 which end the measure together take up far more than half the
3086 horizontal space of the measure.
3088 In classical engraving, this spacing may be exactly what we want
3089 because we can borrow horizontal space from the half note and conserve
3090 horizontal space across the measure as a whole.
3092 On the other hand, if we want to insert a measured timeline or other
3093 graphic above or below our score, we need proportional notation. We
3094 turn proportional notation on with the proportionalNotationDuration
3097 @lilypond[quote,verbatim,ragged-right]
3100 \new RhythmicStaff {
3101 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3107 proportionalNotationDuration = #(ly:make-moment 1/20)
3113 The half note at the beginning of the measure and the faster notes in
3114 the second half of the measure now occupy equal amounts of horizontal
3115 space. We could place a measured timeline or graphic above or below
3118 The @code{proportionalNotationDuration} setting is a context setting
3119 that lives in @code{Score}. Remember that context settings can appear
3120 in one of three locations within our input file -- in a @code{\with}
3121 block, in a @code{\context} block, or directly in music entry preceded
3122 by the @code{\set} command. As with all context settings, users can
3123 pick which of the three different locations they would like to
3124 set @code{proportionalNotationDuration} in to.
3126 The @code{proportionalNotationDuration} setting takes a single argument,
3127 which is the reference duration against that all music will be spaced.
3128 The LilyPond Scheme function @code{make-moment} takes two arguments
3129 -- a numerator and denominator which together express some fraction of
3130 a whole note. The call @code{(ly:make-moment 1/20)} therefore produces
3131 a reference duration of a twentieth note. Values such as
3132 @code{(ly:make-moment 1/16)}, @code{(ly:make-moment 1/8)}, and
3133 @code{(ly:make-moment 3/97)} are all possible as well.
3135 How do we select the right reference duration to pass to
3136 @code{proportionalNotationDuration}? Usually by a process of trial
3137 and error, beginning with a duration close to the fastest (or smallest)
3138 duration in the piece. Smaller reference durations space music loosely;
3139 larger reference durations space music tightly.
3141 @lilypond[quote,verbatim,ragged-right]
3144 \new RhythmicStaff {
3145 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3151 proportionalNotationDuration = #(ly:make-moment 1/8)
3158 \new RhythmicStaff {
3159 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3165 proportionalNotationDuration = #(ly:make-moment 1/16)
3172 \new RhythmicStaff {
3173 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3179 proportionalNotationDuration = #(ly:make-moment 1/32)
3185 Note that too large a reference duration -- such as the eighth note,
3186 above -- spaces music too tightly and can cause note head collisions.
3187 Also that proportional notation in general takes up more horizontal
3188 space than classical spacing. Proportional spacing provides rhythmic
3189 clarity at the expense of horizontal space.
3191 Next we examine how to optimally space overlapping tuplets.
3193 We start by examining what happens to our original example, with
3194 classical spacing, when we add a second staff with a different type of
3197 @lilypond[quote,verbatim,ragged-right]
3200 \new RhythmicStaff {
3201 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3203 \new RhythmicStaff {
3204 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3210 The spacing is bad because the evenly spaced notes of the bottom staff
3211 do not stretch uniformly. Classical engravings include very few complex
3212 triplets and so classical engraving rules can generate this type of
3213 result. Setting @code{proportionalNotationDuration} fixes this.
3215 @lilypond[quote,verbatim,ragged-right]
3218 \new RhythmicStaff {
3219 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3221 \new RhythmicStaff {
3222 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3228 proportionalNotationDuration = #(ly:make-moment 1/20)
3234 But if we look very carefully we can see that notes of the second half
3235 of the 9-tuplet space ever so slightly more widely than the notes
3236 of the first half of the 9-tuplet. To ensure uniform stretching, we
3237 turn on @code{uniform-stretching}, which is a property of
3238 @code{SpacingSpanner}.
3240 @lilypond[quote,verbatim,ragged-right]
3243 \new RhythmicStaff {
3244 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3246 \new RhythmicStaff {
3247 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3253 proportionalNotationDuration = #(ly:make-moment 1/20)
3254 \override SpacingSpanner.uniform-stretching = ##t
3260 Our two-staff example now spaces exactly, our rhythmic
3261 relationships are visually clear, and we can include a measured
3262 timeline or graphic if we want.
3264 Note that the LilyPond's proportional notation package expects
3265 that all proportional scores set the SpacingSpanner's
3266 'uniform-stretching attribute to ##t. Setting
3267 proportionalNotationDuration without also setting the
3268 SpacingSpanner's 'uniform-stretching attribute to ##t will, for
3269 example, cause Skips to consume an incorrect amount of horizontal
3272 The SpacingSpanner is an abstract grob that lives in the Score
3273 context. As with our settings of proportionalNotationDuration,
3274 overrides to the SpacingSpanner can occur in any of three
3275 different places in our input file – in the Score \with block, in
3276 a Score \context block, or in note entry directly.
3278 There is by default only one @code{SpacingSpanner} per @code{Score}. This
3279 means that, by default, @code{uniform-stretching} is either turned on for the
3280 entire score or turned off for the entire score. We can, however,
3281 override this behavior and turn on different spacing features at
3282 different places in the score. We do this with the command
3283 @code{\newSpacingSection}. See @ref{New spacing area}, for more info.
3285 Next we examine the effects of the @code{Separating_line_group_engraver} and
3286 see why proportional scores frequently remove this engraver. The following
3287 example shows that there is a small amount of @qq{prefatory} space
3288 just before the first note in each system.
3290 @lilypond[quote,verbatim,ragged-right]
3303 The amount of this prefatory space is the same whether after a time
3304 signature, a key signature or a clef. @code{Separating_line_group_engraver}
3305 is responsible for this space. Removing @code{Separating_line_group_engraver}
3306 reduces this space to zero.
3308 @lilypond[quote,verbatim,ragged-right]
3314 \remove "Separating_line_group_engraver"
3322 non-musical elements like time signatures, key signatures, clefs and
3323 accidentals are problematic in proportional notation. None of these
3324 elements has rhythmic duration. But all of these elements consume
3325 horizontal space. Different proportional scores approach these
3326 problems differently.
3328 It may be possible to avoid spacing problems with key signatures
3329 simply by not having any. This is a valid option since most
3330 proportional scores are contemporary music. The same may be true
3331 of time signatures, especially for those scores
3332 that include a measured timeline or other graphic. But these scores
3333 are exceptional and most proportional scores include at least some
3334 time signatures. Clefs and accidentals are even more essential.
3336 So what strategies exist for spacing non-musical elements in a
3337 proportional context? One good option is the @code{strict-note-spacing}
3338 property of @code{SpacingSpanner}. Compare the two scores below:
3340 @lilypond[quote,verbatim,ragged-right]
3342 \set Score.proportionalNotationDuration = #(ly:make-moment 1/16)
3343 c''8 8 8 \clef alto d'2 2
3347 \set Score.proportionalNotationDuration = #(ly:make-moment 1/16)
3348 \override Score.SpacingSpanner.strict-note-spacing = ##t
3349 c''8 8 8 \clef alto d'2 2
3353 Both scores are proportional, but the spacing in the first score
3354 is too loose because of the clef change. The spacing of the second
3355 score remains strict, however, because strict-note-spacing is
3356 turned on. Turning on strict-note-spacing causes the width of
3357 time signatures, key signatures, clefs and accidentals to play no
3358 part in the spacing algorithm.
3360 In addition to the settings given here, there are other settings
3361 that frequently appear in proportional scores. These include:
3364 @item @code{\override SpacingSpanner.strict-grace-spacing = ##t}
3365 @item @code{\set tupletFullLength = ##t}
3366 @item @code{\override Beam.breakable = ##t}
3367 @item @code{\override Glissando.breakable = ##t}
3368 @item @code{\override TextSpanner.breakable = ##t}
3369 @item @code{\remove "Forbid_line_break_engraver" in the Voice context}
3372 These settings space grace notes strictly, extend tuplet brackets to
3373 mark both rhythmic start- and stop-points, and allow spanning elements
3374 to break across systems and pages. See the respective parts of the manual
3375 for these related settings.
3379 @ref{New spacing area}.
3385 @node Fitting music onto fewer pages
3386 @section Fitting music onto fewer pages
3388 Sometimes you can end up with one or two staves on a second
3389 (or third, or fourth@dots{}) page. This is annoying, especially
3390 if you look at previous pages and it looks like there is plenty
3391 of room left on those.
3393 When investigating layout issues, @code{annotate-spacing} is an
3394 invaluable tool. This command prints the values of various layout
3395 spacing variables; for more details see the following section,
3396 @ref{Displaying spacing}.
3399 * Displaying spacing::
3400 * Changing spacing::
3404 @node Displaying spacing
3405 @subsection Displaying spacing
3407 @funindex annotate-spacing
3408 @cindex spacing, display of layout
3410 To graphically display the dimensions of vertical layout variables
3411 that may be altered for page formatting, set
3412 @code{annotate-spacing} in the @code{\paper} block:
3414 @lilypond[verbatim,quote,papersize=a6landscape]
3417 \paper { annotate-spacing = ##t }
3423 All layout dimensions are displayed in staff-spaces, regardless
3424 of the units specified in the @code{\paper} or @code{\layout} block.
3425 In the above example, @code{paper-height} has a value of 59.75
3426 @code{staff-spaces}, and the @code{staff-size} is 20 points (the
3427 default value). Note that:
3429 @multitable {1 staff-space} {staff-size)/4 * (25.4/72.27) mm}
3432 @tab = (25.4/72.27) mm
3435 @tab = (@code{staff-size})/4 pts
3437 @tab = (@code{staff-size})/4 * (25.4/72.27) mm
3442 In this case, one @code{staff-space} is approximately equal to
3443 1.757mm. Thus the @code{paper-height} measurement of 59.75
3444 @code{staff-spaces} is equivalent to 105 millimeters, the height
3445 of @code{a6} paper in landscape orientation. The pairs
3446 (@var{a},@var{b}) are intervals, where @var{a} is the lower
3447 edge and @var{b} the upper edge of the interval.
3451 @ref{Setting the staff size}.
3457 @node Changing spacing
3458 @subsection Changing spacing
3460 The output of @code{annotate-spacing} reveals vertical dimensions
3461 in great detail. For details about modifying margins and other
3462 layout variables, see @ref{Page layout}.
3464 Other than margins, there are a few other options to save space:
3468 Force systems to move as close together as possible (to fit as
3469 many systems as possible onto a page) while being spaced so that
3470 there is no blank space at the bottom of the page.
3474 system-system-spacing = #'((basic-distance . 0.1) (padding . 0))
3475 ragged-last-bottom = ##f
3481 Force the number of systems. This can help in two ways. Just
3482 setting a value, even the same value as the number of systems
3483 being typeset by default, will sometimes cause more systems to
3484 be fitted onto each page, as an estimation step is then bypassed,
3485 giving a more accurate fit to each page. Also, forcing an actual
3486 reduction in the number of systems may save a further page. For
3487 example, if the default layout has 11 systems, the following
3488 assignment will force a layout with 10 systems.
3497 Force the number of pages. For example, the following
3498 assignment will force a layout with 2 pages.
3507 Avoid (or reduce) objects that increase the vertical size of a
3508 system. For example, volta brackets for alternative repeat endings
3509 require extra space. If these endings are spread over two systems,
3510 they take up more space than if they were on the same system.
3511 As another example, dynamics that @q{stick out} of a system
3512 can be moved closer to the staff:
3514 @lilypond[verbatim,quote]
3517 e4 c g-\tweak X-offset #-2.7 \f c
3522 Alter the horizontal spacing via @code{SpacingSpanner}. For more
3523 details, see @ref{Changing horizontal spacing}. The following
3524 example illustrates the default spacing:
3526 @lilypond[verbatim,quote]
3539 The next example modifies @code{common-shortest-duration} from a
3540 value of @code{1/4} to @code{1/2}. The quarter note is the most
3541 common and shortest duration in this example, so by making this
3542 duration longer, a @q{squeezing} effect occurs:
3544 @lilypond[verbatim,quote]
3556 \override SpacingSpanner.common-shortest-duration =
3557 #(ly:make-moment 1/2)
3564 The @code{common-shortest-duration} property cannot be modified
3565 dynamically, so it must always be placed in a @code{\context}
3566 block so that it applies to the whole score.
3573 @ref{Changing horizontal spacing}.