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 margins
643 will be updated to center the systems on the page automatically. Also
644 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-page-breaking}, @code{ly:one-line-breaking},
896 @code{ly:one-line-auto-height-breaking}, and @code{ly:optimal-breaking}
899 @item page-breaking-system-system-spacing
900 @funindex page-breaking-system-system-spacing
902 Tricks the page breaker into thinking that
903 @code{system-system-spacing} is set to something different than
904 it really is. For example, if
905 @code{page-breaking-system-system-spacing #'padding} is set to something
906 substantially larger than @code{system-system-spacing #'padding}, then the
907 page-breaker will put fewer systems on each page. Default: unset.
912 The number of pages to be used for a score, unset by default.
916 The following variables are effective only when @code{page-breaking}
917 is set to @code{ly:page-turn-breaking}. Page breaks are then chosen
918 to minimize the number of page turns. Since page turns are required
919 on moving from an odd-numbered page to an even-numbered one, a
920 layout in which the last page is odd-numbered will usually be
921 favoured. Places where page turns are preferred can be indicated
922 manually by inserting @code{\allowPageTurn} or automatically by
923 including the @code{Page_turn_engraver} (see @ref{Optimal page turning}).
925 If there are insufficient choices available for making suitable page
926 turns, LilyPond may insert a blank page either within a score, between
927 scores (if there are two or more scores), or by ending a score on an
928 even-numbered page. The values of the following three variables may
929 be increased to make these actions less likely.
931 The values are penalties, i.e., the higher the value the less likely
932 will be the associated action relative to other choices.
936 @item blank-page-penalty
937 @funindex blank-page-penalty
939 The penalty for having a blank page in the middle of a score. If
940 @code{blank-page-penalty} is large and @code{ly:page-turn-breaking} is
941 selected, then LilyPond will be less likely to insert a page in the
942 middle of a score. Instead, it will space out the music further to
943 fill the blank page and the following one. Default: 5.
945 @item blank-last-page-penalty
946 @funindex blank-last-page-penalty
948 The penalty for ending the score on an even-numbered page. If
949 @code{blank-last-page-penalty} is large and
950 @code{ly:page-turn-breaking} is selected, then LilyPond will be less
951 likely to produce a score in which the last page is even-numbered.
952 Instead, it will adjust the spacing in order to use one page more or
953 one page less. Default: 0.
955 @item blank-after-score-page-penalty
956 @funindex blank-after-score-page-penalty
958 The penalty for having a blank page after the end of one score and
959 before the next. By default, this is smaller than
960 @code{blank-page-penalty}, so that blank pages after scores are
961 inserted in preference to blank pages within a score. Default: 2.
969 @ref{Optimal page breaking},
970 @ref{Optimal page turning},
971 @ref{Minimal page breaking},
972 @ref{One-page page breaking},
973 @ref{One-line page breaking},
974 @ref{One-line-auto-height page breaking}.
977 @file{ly/paper-defaults-init.ly}.
980 @node paper variables for page numbering
981 @unnumberedsubsubsec @code{@bs{}paper} variables for page numbering
983 Default values not listed here are defined in
984 @file{ly/paper-defaults-init.ly}
988 @cindex page numbers, auto-numbering
989 @item auto-first-page-number
990 @funindex auto-first-page-number
992 The page breaking algorithm is affected by the first page number
993 being odd or even. If set to true, the page breaking algorithm
994 will decide whether to start with an odd or even number. This
995 will result in the first page number remaining as is or being
996 increased by one. Default: @code{#f}.
998 @cindex page numbers, specify the first
999 @item first-page-number
1000 @funindex first-page-number
1002 The value of the page number on the first page.
1004 @item print-first-page-number
1005 @funindex print-first-page-number
1007 If set to true, a page number is printed on the first page.
1009 @cindex page numbers, suppress
1010 @item print-page-number
1011 @funindex print-page-number
1013 If set to false, page numbers are not printed.
1015 @cindex page numbers in roman numerals
1016 @item page-number-type
1017 @funindex page-number-type
1019 The type of numerals used for page numbers. Choices include
1020 @code{roman-lower}, @code{roman-upper} and @code{arabic}.
1021 Default: @code{'arabic}.
1027 @file{ly/paper-defaults-init.ly}.
1030 Odd page numbers are always on the right. If you want the
1031 music to start on page 1 there must be a blank page on the back
1032 of the cover page so that page 1 is on the right hand side.
1035 @node Miscellaneous paper variables
1036 @unnumberedsubsubsec Miscellaneous @code{@bs{}paper} variables
1040 @item page-spacing-weight
1041 @funindex page-spacing-weight
1043 The relative importance of page (vertical) spacing and line
1044 (horizontal) spacing. High values will make page spacing more
1045 important. Default: @code{10}.
1047 @item print-all-headers
1048 @funindex print-all-headers
1050 If set to true, this will print all headers for each @code{\score}
1051 in the output. Normally only the @code{piece} and @code{opus}
1052 header variables are printed. Default: @code{#f}.
1054 @item system-separator-markup
1055 @funindex system-separator-markup
1057 A markup object that is inserted between systems, often used for
1058 orchestral scores. Default: unset. The @code{\slashSeparator}
1059 markup, defined in @file{ly/titling-init.ly}, is provided as a
1060 sensible default, for example:
1062 @lilypond[quote,verbatim,noragged-right,line-width=30\mm]
1063 #(set-default-paper-size "a8")
1067 system-separator-markup = \slashSeparator
1073 \relative { c''1 \break c1 \break c1 }
1082 @file{ly/titling-init.ly}.
1088 The default page header puts the page number and the @code{instrument}
1089 field from the @code{\header} block on a line.
1093 @section Score layout
1095 This section discusses score layout options for the @code{\layout}
1099 * The layout block::
1100 * Setting the staff size::
1104 @node The layout block
1105 @subsection The @code{@bs{}layout} block
1109 While the @code{\paper} block contains settings that relate to the
1110 page formatting of the whole document, the @code{\layout} block
1111 contains settings for score-specific layout. To set score layout
1112 options globally, enter them in a toplevel @code{\layout} block.
1113 To set layout options for an individual score, enter them in a
1114 @code{\layout} block inside the @code{\score} block, after the
1115 music. Settings that can appear in a @code{\layout} block
1119 @item the @code{layout-set-staff-size} scheme function,
1120 @item context modifications in @code{\context} blocks, and
1121 @item @code{\paper} variables that affect score layout.
1124 The @code{layout-set-staff-size} function is discussed in the next
1125 section, @ref{Setting the staff size}. Context modifications are
1126 discussed in a separate chapter; see
1127 @ref{Modifying context plug-ins} and
1128 @ref{Changing context default settings}.
1130 The @code{\paper} variables that can appear in a @code{\layout}
1131 block, with default values taken from the @code{\paper} block are:
1136 @code{line-width}, @code{ragged-right} and @code{ragged-last}
1137 (see @ref{paper variables for widths and margins,,@code{@bs{}paper} variables for widths and margins})
1140 @code{indent} and @code{short-indent}
1141 (see @ref{paper variables for shifts and indents,,@code{@bs{}paper} variables for shifts and indents})
1145 (see @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking})
1149 Here is an example @code{\layout} block:
1156 \override StaffGrouper.staff-staff-spacing.basic-distance = #8
1160 \override TextScript.padding = #1
1161 \override Glissando.thickness = #3
1166 Multiple @code{\layout} blocks can be entered as toplevel expressions.
1167 This can, for example, be useful if different settings are stored in
1168 separate files and included optionally. Internally, when
1169 a @code{\layout} block is evaluated, a copy of the current
1170 @code{\layout} configuration is made, then any changes defined within
1171 the block are applied and the result is saved as the new current
1172 configuration. From the user's perspective the @code{\layout} blocks
1173 are combined, but in conflicting situations (when the same property
1174 is changed in different blocks) the later definitions take precedence.
1176 For example, if this block:
1182 \override TextScript.color = #magenta
1183 \override Glissando.thickness = #1.5
1188 is placed after the one from the preceding example the @code{'padding}
1189 and @code{'color} overrides for @code{TextScript} are combined, but
1190 the later @code{'thickness} override for @code{Glissando} replaces
1191 (or hides) the earlier one.
1193 @code{\layout} blocks may be assigned to variables for reuse later,
1194 but the way this works is slightly but significantly different from
1195 writing them literally.
1197 If a variable is defined like this:
1200 layoutVariable = \layout @{
1203 \override NoteHead.font-size = #4
1208 it will hold the current @code{\layout} configuration with the
1209 @code{NoteHead.font-size} override added, but this combination
1210 is @emph{not} saved as the new current configuration. Be aware
1211 that the @q{current configuration} is read when the variable is
1212 defined and not when it is used, so the content of the variable
1213 is dependent on its position in the source.
1215 The variable can then be used inside another @code{\layout} block,
1223 \override NoteHead.color = #red
1228 A @code{\layout} block containing a variable, as in the example above,
1229 does @emph{not} copy the current configuration but instead uses the
1230 content of @code{\layoutVariable} as the base configuration for the
1231 further additions. This means that any changes defined between the
1232 definition and the use of the variable are lost.
1234 If @code{layoutVariable} is defined (or @code{\include}d) immediately
1235 before being used, its content is just the current configuration plus
1236 the overrides defined within it. So in the example above showing the
1237 use of @code{\layoutVariable} the final @code{\layout} block would
1241 TextScript.padding = #1
1242 TextScript.color = #magenta
1243 Glissando.thickness = #1.5
1244 NoteHead.font-size = #4
1245 NoteHead.color = #red
1248 plus the @code{indent} and the @code{StaffGrouper} overrides.
1250 But if the variable had already been defined before the first
1251 @code{\layout} block the current configuration would now contain
1255 NoteHead.font-size = #4 % (written in the variable definition)
1256 NoteHead.color = #red % (added after the use of the variable)
1259 If carefully planned, @code{\layout} variables can be a valuable tool
1260 to structure the layout design of sources, and also to reset the
1261 @code{\layout} configuration to a known state.
1265 @ref{Changing context default settings}.
1271 @node Setting the staff size
1272 @subsection Setting the staff size
1274 @cindex font size, setting
1275 @cindex staff size, setting
1276 @funindex layout file
1277 @funindex magnification->font-size
1279 @funindex set-global-staff-size
1280 @funindex layout-set-staff-size
1282 The default @strong{staff size} is 20 points, which corresponds to
1283 a staff height of 7.03mm (one point is equal to 100/7227 of an
1284 inch, or 2540/7227 mm). The staff size may be changed in three
1290 To set the staff size globally for all scores in a file (or in a
1291 @code{\book} block, to be precise), use
1292 @code{set-global-staff-size}:
1295 #(set-global-staff-size 14)
1299 The above example sets the global default staff size to 14pt
1300 (4.92mm) and scales all fonts accordingly.
1303 To set the staff size for a single score within a book, use
1304 @code{layout-set-staff-size} inside that score's @code{\layout}
1311 #(layout-set-staff-size 14)
1317 To set the staff size for a single staff within a system, use the
1318 @code{\magnifyStaff} command. For example, traditionally engraved
1319 chamber music scores with piano often used 7mm piano staves while
1320 the other staves were typically between 3/5 and 5/7 as large
1321 (between 60% and 71%). To achieve the 5/7 proportion, use:
1329 \new PianoStaff @{ @dots{} @}
1334 If you happen to know which @code{fontSize} you wish to use, you
1335 could use the following form:
1341 \magnifyStaff #(magstep -3)
1343 \new PianoStaff @{ @dots{} @}
1348 To emulate the look of traditional engraving, it is best to avoid
1349 reducing the thickness of the staff lines.
1354 @subheading Automatic font weight at different sizes
1356 The Emmentaler font provides the set of @emph{Feta} musical glyphs in
1357 eight different sizes; each one tuned for a different staff size. The
1358 smaller the glyph size, the @qq{heavier} it becomes, so as to match the
1359 relatively thicker staff lines. Recommended glyphs sizes are listed in
1360 the following table:
1362 @multitable @columnfractions .15 .2 .22 .2
1363 @item @b{font name} @tab @b{staff height (pt)} @tab @b{staff height (mm)} @tab @b{use}
1364 @item feta11 @tab 11.22 @tab 3.9 @tab pocket scores
1365 @item feta13 @tab 12.60 @tab 4.4 @tab
1366 @item feta14 @tab 14.14 @tab 5.0 @tab
1367 @item feta16 @tab 15.87 @tab 5.6 @tab
1368 @item feta18 @tab 17.82 @tab 6.3 @tab song books
1369 @item feta20 @tab 20 @tab 7.0 @tab standard parts
1370 @item feta23 @tab 22.45 @tab 7.9 @tab
1371 @item feta26 @tab 25.2 @tab 8.9 @tab @c modern rental material?
1376 @ref{Selecting notation font size},
1377 @ref{The Emmentaler font}.
1383 @code{layout-set-staff-size} does not change the distance between the
1397 @subsection Line breaking
1401 @funindex \autoBreaksOff
1402 @funindex \autoBreaksOn
1403 @funindex \autoLineBreaksOff
1404 @funindex \autoLineBreaksOn
1405 @cindex manual line breaks
1406 @cindex breaking lines
1408 Line breaks are normally determined automatically. They are
1409 chosen so that lines look neither cramped nor loose, and
1410 consecutive lines have similar density.
1412 To manually force a line break at a bar line, use the
1413 @code{\break} command:
1415 @lilypond[quote,ragged-right,verbatim]
1422 By default, a @code{\break} command inserted in the @q{middle} of a
1423 measure will be ignored (and a warning message will be output during the
1424 compilation of the LilyPond file). Adding an invisible bar line
1425 -- @w{@samp{\bar ""}} -- before the @code{\break} command will force the
1428 @lilypond[quote,ragged-right,verbatim]
1438 A @code{\break} command that occurrs at a bar line will also ignored if
1439 the previous measure ends in the middle of a note (e.g., when a tuplet
1440 begins in one measure and ends in another). In this case remove the
1441 @code{Forbid_line_break_engraver} from the @code{Voice} context and,
1442 use a simultaneous music construction inserting the @code{\break} at the
1443 appropriate place in the second @q{voice}:
1445 @lilypond[quote,ragged-right,verbatim]
1447 \remove "Forbid_line_break_engraver"
1450 { c''2. \tuplet 3/2 { c4 c c } c2. | }
1451 { s1 | \break s1 | }
1456 Similarly, by default, line breaks are ignored when beams cross bar
1457 lines. Use the @code{\override Beam.breakable = ##t} command to force
1460 @lilypond[quote,ragged-right,verbatim]
1462 \override Beam.breakable = ##t
1468 The @code{\noBreak} command will prevent a line break at the bar line
1469 where it is inserted.
1471 Within a score, automatic line breaking is prevented within music
1472 lying between @code{\autoLineBreaksOff} and @code{\autoLineBreaksOn}
1473 commands. If automatic page breaks should also be prevented, the
1474 commands @code{\autoBreaksOff} and @code{\autoBreaksOn} should be
1475 used. Manual breaks are unaffected by these commands. Note that
1476 inhibiting automatic line breaks may cause music to run over the
1477 right margin if it cannot all be contained within one line.
1479 Automatic line breaks (but not page breaks) may be enabled at single
1480 bar lines by using @code{\once \autoLineBreaksOn} at a bar line.
1481 This identifies a permitted rather than a forced line break.
1483 The most basic settings influencing line spacing are @code{indent}
1484 and @code{line-width}. They are set in the @code{\layout} block.
1485 They control the indentation of the first line of music, and the
1486 lengths of the lines.
1488 If @code{ragged-right} is set to true in the @code{\layout} block,
1489 then systems end at their natural horizontal length, instead of
1490 being spread horizontally to fill the whole line. This is useful
1491 for short fragments, and for checking how tight the natural
1494 @c TODO Check and add para on default for ragged-right
1496 The option @code{ragged-last} is similar to @code{ragged-right},
1497 but affects only the last line of the piece.
1507 @cindex regular line breaks
1508 @cindex four bar music.
1510 For line breaks at regular intervals use @code{\break} separated
1511 by skips and repeated with @code{\repeat}. For example, this
1512 would cause the following 28 measures (assuming 4/4 time) to be
1513 broken every 4 measures, and only there:
1518 s1 \noBreak s1 \noBreak
1519 s1 \noBreak s1 \break
1521 @{ @var{the actual music@dots{}} @}
1529 @code{\autoBreaksOff},
1530 @code{\autoBreaksOn},
1531 @code{\autoLineBreaksOff},
1532 @code{\autoLineBreaksOn}.
1537 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
1538 {using-an-extra-voice-for-breaks.ly}
1542 @ref{paper variables for line breaking}
1543 @ref{The layout block}.
1548 Internals Reference:
1549 @rinternals{LineBreakEvent}.
1553 Placing @code{\autoLineBreaksOff} or @code{\autoBreaksOff} before
1554 any music will cause error messages to appear. Always place these
1555 commands after some music.
1559 @subsection Page breaking
1561 This section describes the different page breaking methods, and
1565 * Manual page breaking::
1566 * Optimal page breaking::
1567 * Minimal page breaking::
1568 * One-page page breaking::
1569 * One-line page breaking::
1570 * One-line-auto-height page breaking::
1571 * Optimal page turning::
1575 @node Manual page breaking
1576 @unnumberedsubsubsec Manual page breaking
1578 @funindex \pageBreak
1579 @funindex \noPageBreak
1580 @funindex \autoPageBreaksOn
1581 @funindex \autoPageBreaksOff
1582 @cindex page breaking, manual
1584 The default page breaking may be overridden by inserting
1585 @code{\pageBreak} or @code{\noPageBreak} commands. These commands
1586 are analogous to @code{\break} and @code{\noBreak}. They should
1587 be inserted at a bar line. These commands force and forbid a
1588 page-break from happening at that bar line. Of course, the
1589 @code{\pageBreak} command also forces a line break.
1591 The @code{\pageBreak} and @code{\noPageBreak} commands may also be
1592 inserted at top-level, between scores and top-level markups.
1594 Within a score, automatic page breaks are prevented within music
1595 lying between @code{\autoPageBreaksOff} and @code{\autoPageBreaksOn}
1596 commands. Manual page breaks are unaffected by these commands.
1598 There are also analogous settings to @code{ragged-right} and
1599 @code{ragged-last} which have the same effect on vertical spacing.
1600 If @code{ragged-bottom} is set to @code{#t} the systems will not
1601 be justified vertically. When @code{ragged-last-bottom} is set
1602 to @code{#t}, as it is by default, empty space is allowed at the
1603 bottom of the final page (or the final page in each
1604 @code{\bookpart}). See
1605 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables}.
1607 Page breaks are computed by the @code{page-breaking} function.
1608 LilyPond provides several algorithms for computing page breaks,
1609 including @code{ly:optimal-breaking}, @code{ly:page-turn-breaking} and
1610 @code{ly:minimal-breaking}. The default is
1611 @code{ly:optimal-breaking}, but the value can be changed in the
1612 @code{\paper} block:
1616 page-breaking = #ly:page-turn-breaking
1622 When a book has many scores and pages, the page breaking problem
1623 may be difficult to solve, requiring large processing time and
1624 memory. To ease the page breaking process, @code{\bookpart}
1625 blocks are used to divide the book into several parts: the page
1626 breaking occurs separately on each part. Different page breaking
1627 functions may also be used in different book parts.
1632 subtitle = "Preface"
1635 %% In a part consisting mostly of text,
1636 %% ly:minimal-breaking may be preferred
1637 page-breaking = #ly:minimal-breaking
1639 \markup @{ @dots{} @}
1643 %% In this part, consisting of music, the default optimal
1644 %% page breaking function is used.
1646 subtitle = "First movement"
1648 \score @{ @dots{} @}
1656 @code{\noPageBreak},
1657 @code{\autoPageBreaksOn},
1658 @code{\autoPageBreaksOff}.
1663 @ref{paper variables for page breaking}.
1670 The @code{\once} prefix is ineffective with @code{\autoPageBreaksOn}
1671 and @code{\autoPageBreaksOff}. If auto page breaking is off and is
1672 then turned on to permit a page break, it must remain on for a few
1673 bars (the precise number of bars depends on the score) before being
1674 turned off, else the opportunity to break the page will not be taken.
1676 @node Optimal page breaking
1677 @unnumberedsubsubsec Optimal page breaking
1679 @funindex ly:optimal-breaking
1681 The @code{ly:optimal-breaking} function is LilyPond's default
1682 method of determining page breaks. It attempts to find a page
1683 breaking that minimizes cramping and stretching, both horizontally
1684 and vertically. Unlike @code{ly:page-turn-breaking}, it has no
1685 concept of page turns.
1692 @node Minimal page breaking
1693 @unnumberedsubsubsec Minimal page breaking
1695 @funindex ly:minimal-breaking
1697 The @code{ly:minimal-breaking} function performs minimal
1698 computations to calculate the page breaking: it fills a page with
1699 as many systems as possible before moving to the next one. Thus,
1700 it may be preferred for scores with many pages, where the other
1701 page breaking functions could be too slow or memory demanding, or
1702 a lot of texts. It is enabled using:
1706 page-breaking = #ly:minimal-breaking
1715 @node One-page page breaking
1716 @unnumberedsubsubsec One-page page breaking
1718 @funindex ly:one-page-breaking
1720 The @code{ly:one-page-breaking} function is a special-purpose
1721 page breaking algorithm that automatically adjusts the page height to
1722 fit the music, so that everything fits on a single page. The
1723 @code{paper-height} variable in the paper block is ignored, but other
1724 settings work as usual. In particular, the spacing between the last
1725 system (or top level markup) and the footer can be customized with
1726 @code{last-bottom-spacing} in the paper block. The width of the page
1727 is left unmodified by default but can be set with @code{paper-width}
1731 @code{ly:one-page-breaking} is not currently compatible with
1735 @node One-line page breaking
1736 @unnumberedsubsubsec One-line page breaking
1738 @funindex ly:one-line-breaking
1740 The @code{ly:one-line-breaking} function is a special-purpose
1741 page breaking algorithm that puts each score on its own page, and
1742 on a single line. No titles or margins are typeset; only the score is
1745 The page width is adjusted so that the longest score fits on
1746 one line. In particular, @code{paper-width}, @code{line-width}
1747 and @code{indent} variables in the @code{\paper} block are ignored,
1748 although @code{left-margin} and @code{right-margin} are still honored.
1749 The height of the page is left unmodified.
1752 @node One-line-auto-height page breaking
1753 @unnumberedsubsubsec One-line-auto-height page breaking
1755 @funindex ly:one-line-auto-height-breaking
1757 The @code{ly:one-line-auto-height-breaking} function works just like
1758 @code{ly:one-line-breaking} except the page height is automatically
1759 modified to fit the height of the music. Specifically, the
1760 @code{paper-height} variable in the @code{\paper} block is set so that
1761 it spans the height of the tallest score plus the @code{top-margin} and
1762 @code{bottom-margin}.
1764 Note that the @code{top-system-spacing} setting will affect the
1765 vertical position of the music. Set it to @code{##f} in a paper block
1766 to simply place the music between the top and bottom margins.
1769 @node Optimal page turning
1770 @unnumberedsubsubsec Optimal page turning
1772 @funindex ly:page-turn-breaking
1774 Often it is necessary to find a page breaking configuration so
1775 that there is a rest at the end of every second page. This way,
1776 the musician can turn the page without having to miss notes. The
1777 @code{ly:page-turn-breaking} function attempts to find a page
1778 breaking minimizing cramping and stretching, but with the
1779 additional restriction that it is only allowed to introduce page
1780 turns in specified places.
1782 There are two steps to using this page breaking function. First,
1783 you must enable it in the @code{\paper} block, as explained in
1784 @ref{Page breaking}. Then you must tell the function where you
1785 would like to allow page breaks.
1787 There are two ways to achieve the second step. First, you can
1788 specify each potential page turn manually, by inserting
1789 @code{\allowPageTurn} into your input file at the appropriate
1792 If this is too tedious, you can add a @code{Page_turn_engraver} to
1793 a Staff or Voice context. The @code{Page_turn_engraver} will scan
1794 the context for sections without notes (note that it does not scan
1795 for rests; it scans for the absence of notes. This is so that
1796 single-staff polyphony with rests in one of the parts does not
1797 throw off the @code{Page_turn_engraver}). When it finds a
1798 sufficiently long section without notes, the
1799 @code{Page_turn_engraver} will insert an @code{\allowPageTurn} at
1800 the final bar line in that section, unless there is a @q{special}
1801 bar line (such as a double bar), in which case the
1802 @code{\allowPageTurn} will be inserted at the final @q{special}
1803 bar line in the section.
1805 @funindex minimumPageTurnLength
1806 The @code{Page_turn_engraver} reads the context property
1807 @code{minimumPageTurnLength} to determine how long a note-free
1808 section must be before a page turn is considered. The default
1809 value for @code{minimumPageTurnLength} is
1810 @code{(ly:make-moment 1/1)}. If you want to disable page turns,
1811 set it to something @q{very large}.
1814 \new Staff \with @{ \consists "Page_turn_engraver" @}
1817 R1 | % a page turn will be allowed here
1819 \set Staff.minimumPageTurnLength = #(ly:make-moment 5/2)
1820 R1 | % a page turn will not be allowed here
1822 R1*2 | % a page turn will be allowed here
1827 @funindex minimumRepeatLengthForPageTurn
1829 When using volta repeats, the @code{Page_turn_engraver} will only allow
1830 a page turn during the repeat if there is enough time at the beginning
1831 and end of the repeat to turn the page back. If the repeat is too
1832 short then the @code{Page_turn_engraver} can be used to @emph{disable}
1833 page turns by setting an appropriate value for the context property
1834 @code{minimumRepeatLengthForPageTurn}. In this case the
1835 @code{Page_turn_engraver} will only allows turns in repeats whose
1836 duration is longer than the value specified.
1838 The page turning commands, @code{\pageTurn}, @code{\noPageTurn} and
1839 @code{\allowPageTurn}, may also be used at top-level, in top-level
1840 markups and between scores.
1845 @funindex \noPageTurn
1847 @funindex \allowPageTurn
1848 @code{\allowPageTurn}.
1853 @ref{paper variables for line breaking}.
1859 Use only one @code{Page_turn_engraver} per score. If there are
1860 more, they will interfere with each other.
1865 @ref{Vertical spacing}.
1871 @node Vertical spacing
1872 @section Vertical spacing
1874 @cindex vertical spacing
1875 @cindex spacing, vertical
1877 Vertical spacing is controlled by three things: the amount of
1878 space available (i.e., paper size and margins), the amount of
1879 space between systems, and the amount of space between staves
1883 * Flexible vertical spacing within systems::
1884 * Explicit staff and system positioning::
1885 * Vertical collision avoidance::
1889 @node Flexible vertical spacing within systems
1890 @subsection Flexible vertical spacing within systems
1892 @cindex distance between staves
1893 @cindex staff distance
1894 @cindex space between staves
1895 @cindex space inside systems
1897 Three separate mechanisms control the flexible vertical spacing
1898 within systems, one for each of the following categories:
1903 @emph{ungrouped staves},
1906 @emph{grouped staves} (staves within a staff-group such as
1907 @code{ChoirStaff}, etc.), and
1910 @emph{non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
1915 @c TODO: Clarify this. This almost implies that non-staff lines
1916 @c have NO effect on the spacing between staves. -mp
1918 The height of each system is determined in two steps. First, all
1919 of the staves are spaced according to the amount of space
1920 available. Then, the non-staff lines are distributed between the
1923 Note that the spacing mechanisms discussed in this section only
1924 control the vertical spacing of staves and non-staff lines within
1925 individual systems. The vertical spacing between separate
1926 systems, scores, markups, and margins is controlled by
1927 @code{\paper} variables, which are discussed in
1928 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables}.
1931 * Within-system spacing properties::
1932 * Spacing of ungrouped staves::
1933 * Spacing of grouped staves::
1934 * Spacing of non-staff lines::
1938 @node Within-system spacing properties
1939 @unnumberedsubsubsec Within-system spacing properties
1941 @funindex staff-affinity
1942 @funindex staffgroup-staff-spacing
1943 @funindex staff-staff-spacing
1944 @funindex nonstaff-unrelatedstaff-spacing
1945 @funindex nonstaff-relatedstaff-spacing
1946 @funindex nonstaff-nonstaff-spacing
1947 @funindex default-staff-staff-spacing
1948 @funindex minimum-Y-extent
1949 @funindex extra-offset
1950 @funindex self-alignment-X
1952 @funindex VerticalAxisGroup
1954 The within-system vertical spacing mechanisms are controlled by
1955 two sets of grob properties. The first set is associated with the
1956 @code{VerticalAxisGroup} grob, which is created by all staves and
1957 non-staff lines. The second set is associated with the
1958 @code{StaffGrouper} grob, which can be created by staff-groups,
1959 but only if explicitly called. These properties are described
1960 individually at the end of this section.
1962 The names of these properties (except for @code{staff-affinity})
1963 follow the format @code{@var{item1}-@var{item2}-spacing}, where
1964 @code{@var{item1}} and @code{@var{item2}} are the items to be
1965 spaced. Note that @code{@var{item2}} is not necessarily below
1966 @code{@var{item1}}; for example,
1967 @code{nonstaff-relatedstaff-spacing} will measure upwards from the
1968 non-staff line if @code{staff-affinity} is @code{UP}.
1970 Each distance is measured between the @emph{reference points} of
1971 the two items. The reference point for a staff is the vertical
1972 center of its @code{StaffSymbol} (i.e., the middle line if
1973 @code{line-count} is odd; the middle space if @code{line-count} is
1974 even). The reference points for individual non-staff lines are
1975 given in the following table:
1977 @multitable {Non-staff line} {Reference point}
1978 @headitem Non-staff line @tab Reference point
1979 @item @code{ChordNames} @tab baseline
1980 @item @code{NoteNames} @tab baseline
1981 @item @code{Lyrics} @tab baseline
1982 @item @code{Dynamics} @tab mid-height of @q{m}
1983 @item @code{FiguredBass} @tab highest point
1984 @item @code{FretBoards} @tab top line
1987 In the following image, horizontal lines indicate the positions
1988 of these reference points:
1990 @lilypond[quote,noragged-right,line-width=110\mm]
1991 #(define zero-space '((padding . -inf.0) (basic-distance . 0)))
1993 alignToZero = \with {
1994 \override VerticalAxisGroup.nonstaff-relatedstaff-spacing = #zero-space
1995 \override VerticalAxisGroup.nonstaff-nonstaff-spacing = #zero-space
1996 \override VerticalAxisGroup.staff-affinity = #DOWN
1997 \remove Text_engraver % avoid having two
1998 \consists Text_engraver
2000 lowerCaseChords = \with {
2001 chordNameLowercaseMinor = ##t
2004 #(define-music-function
2007 #{ s1*0^\markup { \upright {\typewriter #context } } #})
2010 \context { \Dynamics \alignToZero }
2011 \context { \FiguredBass \alignToZero }
2012 \context { \Lyrics \alignToZero }
2013 \context { \NoteNames \alignToZero }
2014 \context { \ChordNames \alignToZero \lowerCaseChords }
2015 \context { \FretBoards \alignToZero }
2018 \override DynamicText.self-alignment-X = #-1
2019 \override FretBoard.X-offset = #1.75
2020 \override InstrumentName.minimum-Y-extent = #'(-1 . 2)
2026 %% These contexts have reference points at the baseline:
2027 %% ChordNames, NoteNames, and Lyrics
2029 \new ChordNames { \chords { \labelContext "ChordNames" g1:m } }
2030 \new NoteNames { s1 |\labelContext "NoteNames" g1 | }
2031 \new Lyrics { \lyrics { \skip 1*2 | \labelContext "Lyrics" ghijk1 | } }
2032 \new RhythmicStaff \with { instrumentName = #"baseline " } s1*3
2035 %% The reference point for Dynamics is the midline of 'm' in the font
2037 \new Dynamics { \labelContext "Dynamics" s1\mp s\fp }
2038 \new RhythmicStaff \with { instrumentName = #"mid-height " } s1*3
2041 %% The reference point for FiguredBass is its highest point
2043 \new FiguredBass { \labelContext "FiguredBass" \figuremode { <6 5>1 } }
2044 \new RhythmicStaff \with { instrumentName = #"highest point " } s1
2047 %% The reference point for FretBoards is the top line
2048 \include "predefined-guitar-fretboards.ly"
2050 \new FretBoards { \labelContext "FretBoards" \chordmode { e1 } }
2051 \new RhythmicStaff \with { instrumentName = #"top line " } s1
2055 Each of the vertical spacing grob properties (except
2056 @code{staff-affinity}) uses the same alist structure as the
2057 @code{\paper} spacing variables discussed in
2058 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables}.
2060 for modifying alists are discussed in @ref{Modifying alists}.
2061 Grob properties should be adjusted with an @code{\override} inside
2062 a @code{\score} or @code{\layout} block, and not inside a
2063 @code{\paper} block.
2065 The following example demonstrates the two ways these alists can
2066 be modified. The first declaration updates one key-value
2067 individually, and the second completely re-defines the property:
2071 \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #10
2075 \override VerticalAxisGroup.default-staff-staff-spacing =
2076 #'((basic-distance . 10)
2077 (minimum-distance . 9)
2079 (stretchability . 10))
2083 To change any spacing settings globally, put them in the
2084 @code{\layout} block:
2090 \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #10
2095 Standard settings for the vertical spacing grob properties are
2096 listed in @rinternals{VerticalAxisGroup} and
2097 @rinternals{StaffGrouper}. Default overrides for specific types
2098 of non-staff lines are listed in the relevant context descriptions
2099 in @rinternals{Contexts}.
2102 @subsubheading Properties of the @code{VerticalAxisGroup} grob
2104 @code{VerticalAxisGroup} properties are typically adjusted with an
2105 @code{\override} at the @code{Staff} level (or equivalent).
2108 @item staff-staff-spacing
2110 Used to determine the distance between the current staff and the
2111 staff just below it in the same system, even if one or more
2112 non-staff lines (such as @code{Lyrics}) are placed between the two
2113 staves. Does not apply to the bottom staff of a system.
2115 Initially, the @code{staff-staff-spacing} of a
2116 @code{VerticalAxisGroup} is a Scheme function that applies the
2117 properties of the @code{StaffGrouper} if the staff is part of a
2118 group, or the @code{default-staff-staff-spacing} of the staff
2119 otherwise. This allows staves to be spaced differently when they
2120 are grouped. For uniform spacing regardless of grouping, this
2121 function may be replaced by a flexible-spacing alist, using the
2122 complete-redefinition form of override shown above.
2124 @item default-staff-staff-spacing
2125 A flexible-spacing alist defining the @code{staff-staff-spacing} used for
2126 ungrouped staves, unless @code{staff-staff-spacing} has been explicitly
2127 set with an @code{\override}.
2129 @item staff-affinity
2130 The direction of the staff to use for spacing the current
2131 non-staff line. Choices are @code{UP}, @code{DOWN}, and
2132 @code{CENTER}. If @code{CENTER}, the non-staff line will be
2133 placed equidistant between the two nearest staves on either side,
2134 unless collisions or other spacing constraints prevent this.
2135 Adjacent non-staff lines should have non-increasing
2136 @code{staff-affinity} from top to bottom, e.g., a non-staff line
2137 set to @code{UP} should not immediately follow one that is set to
2138 @code{DOWN}. Non-staff lines at the top of a system should use
2139 @code{DOWN}; those at the bottom should use @code{UP}. Setting
2140 @code{staff-affinity} for a staff causes it to be treated as a
2141 non-staff line. Setting @code{staff-affinity} to @code{#f} causes
2142 a non-staff line to be treated as a staff. Setting
2143 @code{staff-affinity} to @code{UP}, @code{CENTER}, or @code{DOWN}
2144 causes a staff to be spaced as a non-staff line.
2146 @item nonstaff-relatedstaff-spacing
2147 The distance between the current non-staff line and the nearest
2148 staff in the direction of @code{staff-affinity}, if there are no
2149 non-staff lines between the two, and @code{staff-affinity} is
2150 either @code{UP} or @code{DOWN}. If @code{staff-affinity} is
2151 @code{CENTER}, then @code{nonstaff-relatedstaff-spacing} is used
2152 for the nearest staves on @emph{both} sides, even if other
2153 non-staff lines appear between the current one and either of the
2154 staves. This means that the placement of a non-staff line depends
2155 on both the surrounding staves and the surrounding non-staff lines.
2156 Setting the @code{stretchability} of one of these types of spacing to
2157 a small value will make that spacing dominate. Setting the
2158 @code{stretchability} to a large value will make that spacing have
2161 @item nonstaff-nonstaff-spacing
2162 The distance between the current non-staff line and the next
2163 non-staff line in the direction of @code{staff-affinity}, if both
2164 are on the same side of the related staff, and
2165 @code{staff-affinity} is either @code{UP} or @code{DOWN}.
2167 @item nonstaff-unrelatedstaff-spacing
2168 The distance between the current non-staff line and the staff in
2169 the opposite direction from @code{staff-affinity}, if there are no
2170 other non-staff lines between the two, and @code{staff-affinity}
2171 is either @code{UP} or @code{DOWN}. This can be used, for
2172 example, to require a minimum amount of padding between a
2173 @code{Lyrics} line and the staff to which it does not belong.
2177 @subsubheading Properties of the @code{StaffGrouper} grob
2179 @code{StaffGrouper} properties are typically adjusted with an
2180 @code{\override} at the @code{StaffGroup} level (or equivalent).
2183 @item staff-staff-spacing
2184 The distance between consecutive staves within the current
2185 staff-group. The @code{staff-staff-spacing} property of an
2186 individual staff's @code{VerticalAxisGroup} grob can be
2187 overriden with different spacing settings for that staff.
2189 @item staffgroup-staff-spacing
2190 The distance between the last staff of the current staff-group and
2191 the staff just below it in the same system, even if one or more
2192 non-staff lines (such as @code{Lyrics}) exist between the two
2193 staves. Does not apply to the bottom staff of a system. The
2194 @code{staff-staff-spacing} property of an individual staff's
2195 @code{VerticalAxisGroup} grob can be overriden with different
2196 spacing settings for that staff.
2201 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables},
2202 @ref{Modifying alists}.
2205 @file{ly/engraver-init.ly},
2206 @file{scm/define-grobs.scm}.
2208 Internals Reference:
2209 @rinternals{Contexts},
2210 @rinternals{VerticalAxisGroup},
2211 @rinternals{StaffGrouper}.
2214 @node Spacing of ungrouped staves
2215 @unnumberedsubsubsec Spacing of ungrouped staves
2217 @emph{Staves} (such as @code{Staff}, @code{DrumStaff},
2218 @code{TabStaff}, etc.) are contexts that can contain one or more
2219 voice contexts, but cannot contain any other staves.
2221 The following properties affect the spacing of @emph{ungrouped}
2225 @item @code{VerticalAxisGroup} properties:
2227 @item @code{default-staff-staff-spacing}
2228 @item @code{staff-staff-spacing}
2232 These grob properties are described individually above; see
2233 @ref{Within-system spacing properties}.
2235 Additional properties are involved for staves that are part of a
2236 staff-group; see @ref{Spacing of grouped staves}.
2238 The following example shows how the @code{default-staff-staff-spacing}
2239 property can affect the spacing of ungrouped staves.
2240 The same overrides applied to @code{staff-staff-spacing} would
2241 have the same effect, but would also apply in cases where the staves
2242 are combined in a group or groups.
2244 @lilypond[verbatim,quote,staffsize=16]
2248 \override VerticalAxisGroup.default-staff-staff-spacing =
2249 #'((basic-distance . 8)
2250 (minimum-distance . 7)
2256 % The very low note here needs more room than 'basic-distance
2257 % can provide, so the distance between this staff and the next
2258 % is determined by 'padding.
2259 \new Staff { b,2 r | }
2261 % Here, 'basic-distance provides enough room, and there is no
2262 % need to compress the space (towards 'minimum-distance) to make
2263 % room for anything else on the page, so the distance between
2264 % this staff and the next is determined by 'basic-distance.
2265 \new Staff { \clef bass g2 r | }
2267 % By setting 'padding to a negative value, staves can be made to
2268 % collide. The lowest acceptable value for 'basic-distance is 0.
2270 \override VerticalAxisGroup.default-staff-staff-spacing =
2271 #'((basic-distance . 3.5)
2273 } { \clef bass g2 r | }
2274 \new Staff { \clef bass g2 r | }
2280 @file{scm/define-grobs.scm}.
2285 Internals Reference:
2286 @rinternals{VerticalAxisGroup}.
2289 @node Spacing of grouped staves
2290 @unnumberedsubsubsec Spacing of grouped staves
2292 In orchestral and other large scores, it is common to place staves
2293 in groups. The space between groups is typically larger than the
2294 space between staves of the same group.
2296 @emph{Staff-groups} (such as @code{StaffGroup}, @code{ChoirStaff},
2297 etc.) are contexts that can contain one or more staves
2300 The following properties affect the spacing of staves inside
2304 @item @code{VerticalAxisGroup} properties:
2306 @item @code{staff-staff-spacing}
2308 @item @code{StaffGrouper} properties:
2310 @item @code{staff-staff-spacing}
2311 @item @code{staffgroup-staff-spacing}
2315 These grob properties are described individually above; see
2316 @ref{Within-system spacing properties}.
2318 The following example shows how properties of the
2319 @code{StaffGrouper} grob can affect the spacing of grouped staves:
2321 @lilypond[verbatim,quote,staffsize=16]
2325 \override StaffGrouper.staff-staff-spacing.padding = #0
2326 \override StaffGrouper.staff-staff-spacing.basic-distance = #1
2331 \new PianoStaff \with {
2332 \override StaffGrouper.staffgroup-staff-spacing.basic-distance = #20
2347 @file{scm/define-grobs.scm}.
2352 Internals Reference:
2353 @rinternals{VerticalAxisGroup},
2354 @rinternals{StaffGrouper}.
2357 @node Spacing of non-staff lines
2358 @unnumberedsubsubsec Spacing of non-staff lines
2360 @emph{Non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
2361 etc.) are contexts whose layout objects are engraved like staves
2362 (i.e., in horizontal lines within systems). Specifically,
2363 non-staff lines are non-staff contexts that contain the
2364 @rinternals{Axis_group_engraver}.
2366 The following properties affect the spacing of non-staff lines:
2369 @item @code{VerticalAxisGroup} properties:
2371 @item @code{staff-affinity}
2372 @item @code{nonstaff-relatedstaff-spacing}
2373 @item @code{nonstaff-nonstaff-spacing}
2374 @item @code{nonstaff-unrelatedstaff-spacing}
2378 These grob properties are described individually above; see
2379 @ref{Within-system spacing properties}.
2381 The following example shows how the
2382 @code{nonstaff-nonstaff-spacing} property can affect the spacing
2383 of consecutive non-staff lines. Here, by setting the
2384 @code{stretchability} key to a very high value, the lyrics are
2385 able to stretch much more than usual:
2387 @lilypond[verbatim,quote,staffsize=16]
2391 \override VerticalAxisGroup.nonstaff-nonstaff-spacing.stretchability = #1000
2398 \override VerticalAxisGroup.staff-staff-spacing = #'((basic-distance . 30))
2401 \override VerticalAxisGroup.staff-affinity = #UP
2404 \override VerticalAxisGroup.staff-affinity = #CENTER
2405 } \lyricmode { center }
2407 \override VerticalAxisGroup.staff-affinity = #DOWN
2408 } \lyricmode { down }
2415 @file{ly/engraver-init.ly},
2416 @file{scm/define-grobs.scm}.
2421 @c @lsr{spacing,page-spacing.ly},
2422 @c @lsr{spacing,alignment-vertical-spacing.ly}.
2424 Internals Reference:
2425 @rinternals{Contexts},
2426 @rinternals{VerticalAxisGroup}.
2429 @node Explicit staff and system positioning
2430 @subsection Explicit staff and system positioning
2432 One way to understand the flexible vertical spacing mechanisms
2433 explained above is as a collection of settings that control the
2434 amount of vertical padding between staves and systems.
2436 It is possible to approach vertical spacing in a different way
2437 using @code{NonMusicalPaperColumn.line-break-system-details}.
2438 While the flexible vertical spacing mechanisms specify vertical
2439 padding, @code{NonMusicalPaperColumn.line-break-system-details}
2440 can specify exact vertical positions on the page.
2442 @code{NonMusicalPaperColumn.line-break-system-details} accepts
2443 an associative list of three different settings:
2446 @item @code{X-offset}
2447 @item @code{Y-offset}
2448 @item @code{alignment-distances}
2451 Grob overrides, including the overrides for @code{NonMusicalPaperColumn}
2452 below, can occur in any of three different places in an input file:
2455 @item in the middle of note entry directly
2456 @item in a @code{\context} block
2457 @item in the @code{\with} block
2460 When we override @code{NonMusicalPaperColumn}, we use the usual
2461 @code{\override} command in @code{\context} blocks and in the
2462 @code{\with} block. On the other hand, when we override
2463 @code{NonMusicalPaperColumn} in the middle of note entry,
2464 use the special @code{\overrideProperty} command. Here are some
2465 example @code{NonMusicalPaperColumn} overrides with the special
2466 @code{\overrideProperty} command:
2469 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2472 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2475 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2479 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2480 #'((alignment-distances . (15)))
2482 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2485 (alignment-distances . (15)))
2488 To understand how each of these different settings work, we begin
2489 by looking at an example that includes no overrides at all.
2491 @c \book { } is required in these examples to ensure the spacing
2492 @c overrides can be seen between systems. -np
2494 @lilypond[verbatim,quote,staffsize=16]
2495 \header { tagline = ##f }
2496 \paper { left-margin = 0\mm }
2506 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2509 \repeat unfold 15 { d'4 d' d' d' }
2516 This score isolates both line-breaking and page-breaking information in
2517 a dedicated voice. This technique of creating a breaks voice will help
2518 keep layout separate from music entry as our example becomes more
2519 complicated. Also see @ref{Breaks}.
2521 By using explicit @code{\break} commands, the music is divided into five
2522 measures per line. Vertical spacing is from LilyPond's own defaults but
2523 the vertical startpoint of each system is set explicitly using the
2524 @code{Y-offset} pair in the @code{line-break-system-details} attribute
2525 of the @code{NonMusicalPaperColumn} grob:
2527 @lilypond[verbatim,quote,staffsize=16]
2528 \header { tagline = ##f }
2529 \paper { left-margin = 0\mm }
2535 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2538 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2541 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2545 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2548 \repeat unfold 15 { d'4 d' d' d' }
2555 Note that @code{line-break-system-details} takes an associative list of
2556 potentially many values, but that we set only one value here. Note,
2557 too, that the @code{Y-offset} property here determines the exact vertical
2558 position on the page at which each new system will render.
2560 Now that we have set the vertical startpoint of each system
2561 explicitly, we can also set the vertical distances between staves
2562 within each system manually. We do this using the @code{alignment-distances}
2563 subproperty of @code{line-break-system-details}.
2565 @lilypond[verbatim,quote,staffsize=16]
2566 \header { tagline = ##f }
2567 \paper { left-margin = 0\mm }
2573 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2575 (alignment-distances . (10)))
2577 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2579 (alignment-distances . (15)))
2581 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2583 (alignment-distances . (20)))
2586 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2589 \repeat unfold 15 { d'4 d' d' d' }
2596 Note that here we assign two different values to the
2597 @code{line-break-system-details} attribute of the
2598 @code{NonMusicalPaperColumn} grob. Though the
2599 @code{line-break-system-details} attribute alist accepts many
2600 additional spacing parameters (including, for example, a corresponding
2601 @code{X-offset} pair), we need only set the @code{Y-offset} and
2602 @code{alignment-distances} pairs to control the vertical startpoint of
2603 every system and every staff. Finally, note that @code{alignment-distances}
2604 specifies the vertical positioning of staves but not of staff groups.
2606 @lilypond[verbatim,quote,staffsize=16]
2607 \header { tagline = ##f }
2608 \paper { left-margin = 0\mm }
2614 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2616 (alignment-distances . (30 10)))
2618 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2620 (alignment-distances . (10 10)))
2622 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2624 (alignment-distances . (10 30)))
2627 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2630 \new Staff { \repeat unfold 15 { d'4 d' d' d' } }
2631 \new Staff { \repeat unfold 15 { e'4 e' e' e' } }
2638 Some points to consider:
2641 @item When using @code{alignment-distances}, lyrics and other non-staff lines
2642 do not count as a staff.
2644 @item The units of the numbers passed to @code{X-offset},
2645 @code{Y-offset} and @code{alignment-distances} are interpreted as multiples
2646 of the distance between adjacent staff lines. Positive values move staves
2647 and lyrics up, negative values move staves and lyrics down.
2649 @item Because the @code{NonMusicalPaperColumn.line-break-system-details}
2650 settings given here allow the positioning of staves and systems anywhere
2651 on the page, it is possible to violate paper or margin boundaries or even
2652 to print staves or systems on top of one another. Reasonable values
2653 passed to these different settings will avoid this.
2661 @node Vertical collision avoidance
2662 @subsection Vertical collision avoidance
2664 @funindex outside-staff-priority
2665 @funindex outside-staff-padding
2666 @funindex outside-staff-horizontal-padding
2668 Intuitively, there are some objects in musical notation that belong
2669 to the staff and there are other objects that should be placed outside
2670 the staff. Objects belonging outside the staff include things such as
2671 rehearsal marks, text and dynamic markings (from now on, these will
2672 be called outside-staff objects). LilyPond's rule for the
2673 vertical placement of outside-staff objects is to place them as close
2674 to the staff as possible but not so close that they collide with
2677 LilyPond uses the @code{outside-staff-priority} property to determine
2678 whether a grob is an outside-staff object: if @code{outside-staff-priority}
2679 is a number, the grob is an outside-staff object. In addition,
2680 @code{outside-staff-priority} tells LilyPond in which order the objects
2683 First, LilyPond places all the objects that do not belong outside
2684 the staff. Then it sorts the outside-staff objects according to their
2685 @code{outside-staff-priority} (in increasing order). One by one, LilyPond
2686 takes the outside-staff objects and places them so that they do
2687 not collide with any objects that have already been placed. That
2688 is, if two outside-staff grobs are competing for the same space, the one
2689 with the lower @code{outside-staff-priority} will be placed closer to
2692 A listing of outside-staff-priorities may be found in
2693 @rlearning{The outside-staff-priority property}.
2695 @lilypond[quote,ragged-right,verbatim]
2699 \once \override TextScript.outside-staff-priority = #1
2700 c4_"Text"\pp % this time the text will be closer to the staff
2702 % by setting outside-staff-priority to a non-number,
2703 % we disable the automatic collision avoidance
2704 \once \override TextScript.outside-staff-priority = ##f
2705 \once \override DynamicLineSpanner.outside-staff-priority = ##f
2706 c4_"Text"\pp % now they will collide
2710 The vertical padding around outside-staff objects
2711 can be controlled with @code{outside-staff-padding}.
2713 @lilypond[quote,ragged-right,verbatim,staffsize=18]
2715 \once \override TextScript.outside-staff-padding = #0
2716 a'4-"outside-staff-padding = #0"
2717 \once \override TextScript.outside-staff-padding = #3
2718 d-"outside-staff-padding = #3"
2719 c-"default outside-staff-padding"
2720 b-"default outside-staff-padding"
2726 By default, outside-staff objects are placed so they avoid
2727 a horizontal collision with previously-positioned grobs. This
2728 can lead to situations in which objects are placed close to each
2730 As shown in the example below, setting @code{outside-staff-horizontal-padding}
2731 increases the horizontal spacing required, and in this case moves the text up
2732 to prevent it from getting too close to the ledger lines.
2734 @lilypond[quote,ragged-right,verbatim]
2738 \once \override TextScript.outside-staff-horizontal-padding = #1
2748 @node Horizontal spacing
2749 @section Horizontal spacing
2751 @cindex horizontal spacing
2752 @cindex spacing, horizontal
2755 * Horizontal spacing overview::
2756 * New spacing section::
2757 * Changing horizontal spacing::
2759 * Proportional notation::
2763 @node Horizontal spacing overview
2764 @subsection Horizontal spacing overview
2766 The spacing engine translates differences in durations into stretchable
2767 distances (@q{springs}) of differing lengths. Longer durations get
2768 more space, shorter durations get less. The shortest durations get a
2769 fixed amount of space (which is controlled by
2770 @code{shortest-duration-space} in the @rinternals{SpacingSpanner}
2771 object). The longer the duration, the more space it gets: doubling a
2772 duration adds @code{spacing-increment} of space to the note.
2774 For example, the following piece contains lots of half, quarter, and
2775 8th notes; the eighth note is followed by 1 note head width (NHW).
2776 The quarter note is followed by 2 NHW, the half by 3 NHW, etc.
2778 @lilypond[quote,verbatim]
2786 Normally, @code{spacing-increment} is set to 1.2 staff space, which is
2787 approximately the width of a note head, and
2788 @code{shortest-duration-space} is set to 2.0, meaning that the
2789 shortest note gets 2.4 staff space (2.0 times the
2790 @code{spacing-increment}) of horizontal space. This space is counted
2791 from the left edge of the symbol, so the shortest notes are generally
2792 followed by one NHW of space.
2794 If one would follow the above procedure exactly, then adding a single
2795 32nd note to a score that uses 8th and 16th notes, would widen up the
2796 entire score a lot. The shortest note is no longer a 16th, but a 32nd,
2797 thus adding 1 NHW to every note. To prevent this, the shortest
2798 duration for spacing is not the shortest note in the score, but rather
2799 the one which occurs most frequently.
2802 The most common shortest duration is determined as follows: in every
2803 measure, the shortest duration is determined. The most common shortest
2804 duration is taken as the basis for the spacing, with the stipulation
2805 that this shortest duration should always be equal to or shorter than
2808 These durations may also be customized. If you set the
2809 @code{common-shortest-duration} in @rinternals{SpacingSpanner}, then
2810 this sets the base duration for spacing. The maximum duration for this
2811 base (normally an 8th), is set through @code{base-shortest-duration}.
2813 @funindex common-shortest-duration
2814 @funindex base-shortest-duration
2815 @funindex stem-spacing-correction
2818 Notes that are even shorter than the common shortest note are
2819 followed by a space that is proportional to their duration relative to
2820 the common shortest note. So if we were to add only a few 16th notes
2821 to the example above, they would be followed by half a NHW:
2823 @lilypond[quote,verbatim]
2824 \relative { c''2 c4. c8 | c4. c16[ c] c4. c8 | c8 c c4 c c }
2827 As explained in the @emph{Essay on automated music engraving}, stem
2828 directions will influence spacing (see @ressay{Optical spacing}) and can
2829 be adjusted using the @code{stem-spacing-correction} property of the
2830 @rinternals{NoteSpacing} object (which are generated for every
2831 @rinternals{Voice} context).
2833 The @code{StaffSpacing} object (generated in @rinternals{Staff} context)
2834 contains the same property for controlling the stem/bar line spacing.
2836 The following example shows this; once with the default settings and
2837 once with an exaggerated adjustment:
2839 @lilypond[quote,ragged-right]
2843 \override Staff.NoteSpacing.stem-spacing-correction = #1.5
2844 \override Staff.StaffSpacing.stem-spacing-correction = #1.5
2850 Proportional notation is supported; see @ref{Proportional notation}.
2853 Essay on automated music engraving:
2854 @ressay{Optical spacing}.
2859 Internals Reference:
2860 @rinternals{SpacingSpanner},
2861 @rinternals{NoteSpacing},
2862 @rinternals{StaffSpacing},
2863 @rinternals{NonMusicalPaperColumn}.
2866 There is no convenient mechanism to manually override spacing. The
2867 following work-around may be used to insert extra space into a score,
2868 adjusting the padding value as necessary.
2871 \override Score.NonMusicalPaperColumn.padding = #10
2874 No work-around exists for decreasing the amount of space.
2877 @node New spacing section
2878 @subsection New spacing section
2880 @funindex \newSpacingSection
2881 @cindex new spacing section
2882 @cindex spacing section, new
2883 @cindex notes, spacing horizontally
2885 New sections with different spacing parameters can be started with the
2886 @code{newSpacingSection} command. This is useful for sections with
2887 different notions of @q{long} and @q{short} notes. The
2888 @code{\newSpacingSection} command creates a new @code{SpacingSpanner}
2889 object at that musical moment.
2891 In the following example the time signature change introduces a new
2892 section, and the 16ths notes are automatically spaced slightly wider
2895 @lilypond[verbatim,quote]
2899 c8 c c4 c16[ c c8] c4
2906 If the automatic spacing adjustments do not give the required spacing,
2907 manual @code{\override}s may be applied to its properties. These must
2908 be applied at the same musical moment as the @code{\newSpacingSection}
2909 command itself and will then affect the spacing of all the following
2910 music until the properties are changed in a new spacing section, for
2913 @lilypond[verbatim,quote]
2918 \override Score.SpacingSpanner.spacing-increment = #2
2921 \revert Score.SpacingSpanner.spacing-increment
2931 Internals Reference:
2932 @rinternals{SpacingSpanner}.
2935 @node Changing horizontal spacing
2936 @subsection Changing horizontal spacing
2938 Horizontal spacing may be altered with the
2939 @code{base-shortest-duration} property. Here
2940 we compare the same music; once without altering
2941 the property, and then altered. Larger values
2942 of @code{ly:make-moment} will produce smaller
2943 music. Note that @code{ly:make-moment} constructs
2944 a duration, so @code{1 4} is a longer duration
2947 @lilypond[verbatim,line-width=12\cm]
2950 g'4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2951 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2952 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2953 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2958 @lilypond[verbatim,line-width=12\cm]
2961 g'4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2962 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2963 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2964 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2969 \override SpacingSpanner.base-shortest-duration = #(ly:make-moment 1/16)
2978 By default, spacing in tuplets depends on various non-duration
2979 factors (such as accidentals, clef changes, etc). To disregard
2980 such symbols and force uniform equal-duration spacing, use
2981 @code{Score.SpacingSpanner.uniform-stretching}. This
2982 property can only be changed at the beginning of a score,
2984 @lilypond[quote,ragged-right,verbatim]
2988 \tuplet 5/4 { c8 c c c c } c8 c c c
2991 c8 c c c \tuplet 5/4 { c8 c c c c }
2997 \override SpacingSpanner.uniform-stretching = ##t
3003 When @code{strict-note-spacing} is set, notes are spaced without
3004 regard for clefs, bar lines, and grace notes,
3006 @lilypond[quote,ragged-right,fragment,verbatim]
3007 \override Score.SpacingSpanner.strict-note-spacing = ##t
3008 \new Staff \relative {
3009 c''8[ c \clef alto c \grace { c16 c } c8 c c] c32[ c] }
3018 @subsection Line width
3021 @cindex breaking pages
3024 @funindex line-width
3025 @funindex ragged-right
3026 @funindex ragged-last
3028 @c Although line-width can be set in \layout, it should be set in paper
3029 @c block, to get page layout right.
3030 @c Setting indent in \paper block makes not much sense, but it works.
3032 @c Bit verbose and vague, use examples?
3033 The most basic settings influencing the spacing are @code{indent} and
3034 @code{line-width}. They are set in the @code{\layout} block. They
3035 control the indentation of the first line of music, and the lengths of
3038 If @code{ragged-right} is set to true in the @code{\layout} block, then
3039 systems ends at their natural horizontal length, instead of being spread
3040 horizontally to fill the whole line. This is useful for
3041 short fragments, and for checking how tight the natural spacing is.
3042 The normal default setting is false, but if the score has only one
3043 system the default value is true.
3046 @cindex vertical spacing
3048 The option @code{ragged-last} is similar to @code{ragged-right}, but
3049 only affects the last line of the piece. No restrictions are put on
3050 that line. The result is similar to formatting text paragraphs. In a
3051 paragraph, the last line simply takes its natural horizontal length.
3052 @c Note that for text there are several options for the last line.
3053 @c While Knuth TeX uses natural length, lead typesetters use the same
3054 @c stretch as the previous line. eTeX uses \lastlinefit to
3055 @c interpolate between both these solutions.
3070 @node Proportional notation
3071 @subsection Proportional notation
3073 LilyPond supports proportional notation, a type of horizontal spacing
3074 in which each note consumes an amount of horizontal space exactly
3075 equivalent to its rhythmic duration. This type of proportional spacing
3076 is comparable to horizontal spacing on top of graph paper. Some late
3077 20th- and early 21st-century scores use proportional notation to
3078 clarify complex rhythmic relationships or to facilitate the placement
3079 of timelines or other graphics directly in the score.
3081 LilyPond supports five different settings for proportional notation,
3082 which may be used together or alone:
3085 @item @code{proportionalNotationDuration}
3086 @item @code{uniform-stretching}
3087 @item @code{strict-note-spacing}
3088 @item @code{\remove "Separating_line_group_engraver"}
3089 @item @code{\override PaperColumn.used = ##t}
3092 In the examples that follow, we explore these five different
3093 proportional notation settings and examine how these settings interact.
3095 We start with the following one-measure example, which uses classical
3096 spacing with ragged-right turned on.
3098 @c The initial pitch is not necessary as long as RhythmicStaff is
3099 @c not preceded by other material in the score, but we don't want
3101 @lilypond[quote,verbatim,ragged-right]
3104 \new RhythmicStaff {
3105 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3111 Notice that the half note which begins the measure takes up far less
3112 than half of the horizontal space of the measure. Likewise, the
3113 sixteenth notes and sixteenth-note quintuplets (or twentieth notes)
3114 which end the measure together take up far more than half the
3115 horizontal space of the measure.
3117 In classical engraving, this spacing may be exactly what we want
3118 because we can borrow horizontal space from the half note and conserve
3119 horizontal space across the measure as a whole.
3121 On the other hand, if we want to insert a measured timeline or other
3122 graphic above or below our score, we need proportional notation. We
3123 turn proportional notation on with the proportionalNotationDuration
3126 @lilypond[quote,verbatim,ragged-right]
3129 \new RhythmicStaff {
3130 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3136 proportionalNotationDuration = #(ly:make-moment 1/20)
3142 The half note at the beginning of the measure and the faster notes in
3143 the second half of the measure now occupy equal amounts of horizontal
3144 space. We could place a measured timeline or graphic above or below
3147 The @code{proportionalNotationDuration} setting is a context setting
3148 that lives in @code{Score}. Remember that context settings can appear
3149 in one of three locations within our input file -- in a @code{\with}
3150 block, in a @code{\context} block, or directly in music entry preceded
3151 by the @code{\set} command. As with all context settings, users can
3152 pick which of the three different locations they would like to
3153 set @code{proportionalNotationDuration} in to.
3155 The @code{proportionalNotationDuration} setting takes a single argument,
3156 which is the reference duration against that all music will be spaced.
3157 The LilyPond Scheme function @code{make-moment} takes two arguments
3158 -- a numerator and denominator which together express some fraction of
3159 a whole note. The call @code{(ly:make-moment 1/20)} therefore produces
3160 a reference duration of a twentieth note. Values such as
3161 @code{(ly:make-moment 1/16)}, @code{(ly:make-moment 1/8)}, and
3162 @code{(ly:make-moment 3/97)} are all possible as well.
3164 How do we select the right reference duration to pass to
3165 @code{proportionalNotationDuration}? Usually by a process of trial
3166 and error, beginning with a duration close to the fastest (or smallest)
3167 duration in the piece. Smaller reference durations space music loosely;
3168 larger reference durations space music tightly.
3170 @lilypond[quote,verbatim,ragged-right]
3173 \new RhythmicStaff {
3174 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3180 proportionalNotationDuration = #(ly:make-moment 1/8)
3187 \new RhythmicStaff {
3188 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3194 proportionalNotationDuration = #(ly:make-moment 1/16)
3201 \new RhythmicStaff {
3202 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3208 proportionalNotationDuration = #(ly:make-moment 1/32)
3214 Note that too large a reference duration -- such as the eighth note,
3215 above -- spaces music too tightly and can cause note head collisions.
3216 Also that proportional notation in general takes up more horizontal
3217 space than classical spacing. Proportional spacing provides rhythmic
3218 clarity at the expense of horizontal space.
3220 Next we examine how to optimally space overlapping tuplets.
3222 We start by examining what happens to our original example, with
3223 classical spacing, when we add a second staff with a different type of
3226 @lilypond[quote,verbatim,ragged-right]
3229 \new RhythmicStaff {
3230 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3232 \new RhythmicStaff {
3233 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3239 The spacing is bad because the evenly spaced notes of the bottom staff
3240 do not stretch uniformly. Classical engravings include very few complex
3241 triplets and so classical engraving rules can generate this type of
3242 result. Setting @code{proportionalNotationDuration} fixes this.
3244 @lilypond[quote,verbatim,ragged-right]
3247 \new RhythmicStaff {
3248 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3250 \new RhythmicStaff {
3251 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3257 proportionalNotationDuration = #(ly:make-moment 1/20)
3263 But if we look very carefully we can see that notes of the second half
3264 of the 9-tuplet space ever so slightly more widely than the notes
3265 of the first half of the 9-tuplet. To ensure uniform stretching, we
3266 turn on @code{uniform-stretching}, which is a property of
3267 @code{SpacingSpanner}.
3269 @lilypond[quote,verbatim,ragged-right]
3272 \new RhythmicStaff {
3273 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3275 \new RhythmicStaff {
3276 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3282 proportionalNotationDuration = #(ly:make-moment 1/20)
3283 \override SpacingSpanner.uniform-stretching = ##t
3289 Our two-staff example now spaces exactly, our rhythmic
3290 relationships are visually clear, and we can include a measured
3291 timeline or graphic if we want.
3293 Note that the LilyPond's proportional notation package expects
3294 that all proportional scores set the SpacingSpanner's
3295 'uniform-stretching attribute to ##t. Setting
3296 proportionalNotationDuration without also setting the
3297 SpacingSpanner's 'uniform-stretching attribute to ##t will, for
3298 example, cause Skips to consume an incorrect amount of horizontal
3301 The SpacingSpanner is an abstract grob that lives in the Score
3302 context. As with our settings of proportionalNotationDuration,
3303 overrides to the SpacingSpanner can occur in any of three
3304 different places in our input file – in the Score \with block, in
3305 a Score \context block, or in note entry directly.
3307 There is by default only one @code{SpacingSpanner} per @code{Score}. This
3308 means that, by default, @code{uniform-stretching} is either turned on for the
3309 entire score or turned off for the entire score. We can, however,
3310 override this behavior and turn on different spacing features at
3311 different places in the score. We do this with the command
3312 @code{\newSpacingSection}. See @ref{New spacing section}, for more info.
3314 Next we examine the effects of the @code{Separating_line_group_engraver} and
3315 see why proportional scores frequently remove this engraver. The following
3316 example shows that there is a small amount of @qq{prefatory} space
3317 just before the first note in each system.
3319 @lilypond[quote,verbatim,ragged-right]
3332 The amount of this prefatory space is the same whether after a time
3333 signature, a key signature or a clef. @code{Separating_line_group_engraver}
3334 is responsible for this space. Removing @code{Separating_line_group_engraver}
3335 reduces this space to zero.
3337 @lilypond[quote,verbatim,ragged-right]
3343 \remove "Separating_line_group_engraver"
3351 non-musical elements like time signatures, key signatures, clefs and
3352 accidentals are problematic in proportional notation. None of these
3353 elements has rhythmic duration. But all of these elements consume
3354 horizontal space. Different proportional scores approach these
3355 problems differently.
3357 It may be possible to avoid spacing problems with key signatures
3358 simply by not having any. This is a valid option since most
3359 proportional scores are contemporary music. The same may be true
3360 of time signatures, especially for those scores
3361 that include a measured timeline or other graphic. But these scores
3362 are exceptional and most proportional scores include at least some
3363 time signatures. Clefs and accidentals are even more essential.
3365 So what strategies exist for spacing non-musical elements in a
3366 proportional context? One good option is the @code{strict-note-spacing}
3367 property of @code{SpacingSpanner}. Compare the two scores below:
3369 @lilypond[quote,verbatim,ragged-right]
3371 \set Score.proportionalNotationDuration = #(ly:make-moment 1/16)
3372 c''8 8 8 \clef alto d'2 2
3376 \set Score.proportionalNotationDuration = #(ly:make-moment 1/16)
3377 \override Score.SpacingSpanner.strict-note-spacing = ##t
3378 c''8 8 8 \clef alto d'2 2
3382 Both scores are proportional, but the spacing in the first score
3383 is too loose because of the clef change. The spacing of the second
3384 score remains strict, however, because strict-note-spacing is
3385 turned on. Turning on strict-note-spacing causes the width of
3386 time signatures, key signatures, clefs and accidentals to play no
3387 part in the spacing algorithm.
3389 In addition to the settings given here, there are other settings
3390 that frequently appear in proportional scores. These include:
3393 @item @code{\override SpacingSpanner.strict-grace-spacing = ##t}
3394 @item @code{\set tupletFullLength = ##t}
3395 @item @code{\override Beam.breakable = ##t}
3396 @item @code{\override Glissando.breakable = ##t}
3397 @item @code{\override TextSpanner.breakable = ##t}
3398 @item @code{\remove "Forbid_line_break_engraver" in the Voice context}
3401 These settings space grace notes strictly, extend tuplet brackets to
3402 mark both rhythmic start- and stop-points, and allow spanning elements
3403 to break across systems and pages. See the respective parts of the manual
3404 for these related settings.
3408 @ref{New spacing section}.
3414 @node Fitting music onto fewer pages
3415 @section Fitting music onto fewer pages
3417 Sometimes you can end up with one or two staves on a second
3418 (or third, or fourth@dots{}) page. This is annoying, especially
3419 if you look at previous pages and it looks like there is plenty
3420 of room left on those.
3422 When investigating layout issues, @code{annotate-spacing} is an
3423 invaluable tool. This command prints the values of various layout
3424 spacing variables; for more details see the following section,
3425 @ref{Displaying spacing}.
3428 * Displaying spacing::
3429 * Changing spacing::
3433 @node Displaying spacing
3434 @subsection Displaying spacing
3436 @funindex annotate-spacing
3437 @cindex spacing, display of layout
3439 To graphically display the dimensions of vertical layout variables
3440 that may be altered for page formatting, set
3441 @code{annotate-spacing} in the @code{\paper} block:
3443 @lilypond[verbatim,quote,papersize=a6landscape]
3446 \paper { annotate-spacing = ##t }
3452 All layout dimensions are displayed in staff-spaces, regardless
3453 of the units specified in the @code{\paper} or @code{\layout} block.
3454 In the above example, @code{paper-height} has a value of 59.75
3455 @code{staff-spaces}, and the @code{staff-size} is 20 points (the
3456 default value). Note that:
3458 @multitable {1 staff-space} {staff-size)/4 * (25.4/72.27) mm}
3461 @tab = (25.4/72.27) mm
3464 @tab = (@code{staff-size})/4 pts
3466 @tab = (@code{staff-size})/4 * (25.4/72.27) mm
3471 In this case, one @code{staff-space} is approximately equal to
3472 1.757mm. Thus the @code{paper-height} measurement of 59.75
3473 @code{staff-spaces} is equivalent to 105 millimeters, the height
3474 of @code{a6} paper in landscape orientation. The pairs
3475 (@var{a},@var{b}) are intervals, where @var{a} is the lower
3476 edge and @var{b} the upper edge of the interval.
3480 @ref{Setting the staff size}.
3486 @node Changing spacing
3487 @subsection Changing spacing
3489 The output of @code{annotate-spacing} reveals vertical dimensions
3490 in great detail. For details about modifying margins and other
3491 layout variables, see @ref{Page layout}.
3493 Other than margins, there are a few other options to save space:
3497 Force systems to move as close together as possible (to fit as
3498 many systems as possible onto a page) while being spaced so that
3499 there is no blank space at the bottom of the page.
3503 system-system-spacing = #'((basic-distance . 0.1) (padding . 0))
3504 ragged-last-bottom = ##f
3510 Force the number of systems. This can help in two ways. Just
3511 setting a value, even the same value as the number of systems
3512 being typeset by default, will sometimes cause more systems to
3513 be fitted onto each page, as an estimation step is then bypassed,
3514 giving a more accurate fit to each page. Also, forcing an actual
3515 reduction in the number of systems may save a further page. For
3516 example, if the default layout has 11 systems, the following
3517 assignment will force a layout with 10 systems.
3526 Force the number of pages. For example, the following
3527 assignment will force a layout with 2 pages.
3536 Avoid (or reduce) objects that increase the vertical size of a
3537 system. For example, volta brackets for alternative repeat endings
3538 require extra space. If these endings are spread over two systems,
3539 they take up more space than if they were on the same system.
3540 As another example, dynamics that @q{stick out} of a system
3541 can be moved closer to the staff:
3543 @lilypond[verbatim,quote]
3546 e4 c g-\tweak X-offset #-2.7 \f c
3551 Alter the horizontal spacing via @code{SpacingSpanner}. For more
3552 details, see @ref{Changing horizontal spacing}. The following
3553 example illustrates the default spacing:
3555 @lilypond[verbatim,quote]
3568 The next example modifies @code{common-shortest-duration} from a
3569 value of @code{1/4} to @code{1/2}. The quarter note is the most
3570 common and shortest duration in this example, so by making this
3571 duration longer, a @q{squeezing} effect occurs:
3573 @lilypond[verbatim,quote]
3585 \override SpacingSpanner.common-shortest-duration =
3586 #(ly:make-moment 1/2)
3593 The @code{common-shortest-duration} property cannot be modified
3594 dynamically, so it must always be placed in a @code{\context}
3595 block so that it applies to the whole score.
3602 @ref{Changing horizontal spacing}.