1 @c -*- coding: utf-8; mode: texinfo; -*-
4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. For details, see the Contributors'
8 Guide, node Updating translation committishes..
16 Negative numbers are allowed:
17 > Are you sure? The following works well
19 > first-page-number = -2
21 > and prints page number -1 on the second page, for example.
24 In 5.2.1 the @refbugs (line 495 in spacing.itely on master) it
27 "@code{layout-set-staff-size} does not change the distance between
31 Could we add a sentence:
32 "Use instead the pair fontSize = #@var{N}
33 \override StaffSymbol.staff-space = #(magstep
35 inside the Staff context to change the size of the font and the
37 staff lines accordingly."
39 Actually I found, that the @internalsref{StaffSymbol} at line 481
40 sends to an incomplete
41 documentation. The property staff-space is not explained here. I
42 thought Y-extent might be of
43 help, but it is in turn explained by x-space which again is
44 missing from the list. Who has the
45 knowledge to fix this?
49 http://code.google.com/p/lilypond/issues/detail?id=68
55 @chapter Spacing issues
57 The global paper layout is determined by three factors: the page layout, the
58 line breaks, and the spacing. These all influence each other. The
59 choice of spacing determines how densely each system of music is set.
60 This influences where line breaks are chosen, and thus ultimately, how
61 many pages a piece of music takes.
63 Globally speaking, this procedure happens in four steps: first,
64 flexible distances (@q{springs}) are chosen, based on durations. All
65 possible line breaking combinations are tried, and a @q{badness} score
66 is calculated for each. Then the height of each possible system is
67 estimated. Finally, a page breaking and line breaking combination is chosen
68 so that neither the horizontal nor the vertical spacing is too cramped
71 Two types of blocks can contain layout settings:
72 @code{\paper @{@dots{}@}} and @code{\layout @{@dots{}@}}. The
73 @code{\paper} block contains page layout settings that are expected
74 to be the same for all scores in a book or bookpart, such as the
75 paper height, or whether to print page numbers, etc. See
76 @ref{Page layout}. The @code{\layout} block contains score layout
77 settings, such as the number of systems to use, or the space
78 between staff-groups, etc. See @ref{Score layout}.
85 * Horizontal spacing::
86 * Fitting music onto fewer pages::
93 This section discusses page layout options for the @code{\paper}
98 * Paper size and automatic scaling::
99 * Fixed vertical spacing paper variables::
100 * Flexible vertical spacing paper variables::
101 * Horizontal spacing paper variables::
102 * Other paper variables::
106 @node The paper block
107 @subsection The @code{@bs{}paper} block
109 @code{\paper} blocks may be placed in three different places to form
110 a descending hierarchy of @code{\paper} blocks:
115 At the top of the input file, before all @code{\book},
116 @code{\bookpart}, and @code{\score} blocks.
119 Within a @code{\book} block but outside all the @code{\bookpart} and
120 @code{\score} blocks within that book.
123 Within a @code{\bookpart} block but outside all @code{\score} blocks
124 within that bookpart.
128 A @code{\paper} block cannot be placed within a @code{\score} block.
130 The values of the fields filter down this hierarchy, with the values
131 set higher in the hierarchy persisting unless they are over-ridden
132 by a value set lower in the hierarchy.
134 Several @code{\paper} blocks can appear at each of the levels, for
135 example as parts of several @code{\include}d files. If so, the
136 fields at each level are merged, with values encountered last taking
137 precedence if duplicated fields appear.
139 Settings that can appear in a @code{\paper} block include:
144 the @code{set-paper-size} scheme function,
147 @code{\paper} variables used for customizing page layout, and
150 markup definitions used for customizing the layout of headers,
155 The @code{set-paper-size} function is discussed in the next
156 section, @ref{Paper size and automatic scaling}. The
157 @code{\paper} variables that deal with page layout are discussed
158 in later sections. The markup definitions that deal with headers,
159 footers, and titles are discussed in
160 @ref{Custom titles headers and footers}.
162 Most @code{\paper} variables will only work in a @code{\paper}
163 block. The few that will also work in a @code{\layout} block are
164 listed in @ref{The layout block,,The @code{@bs{}layout} block}.
166 Except when specified otherwise, all @code{\paper} variables that
167 correspond to distances on the page are measured in millimeters,
168 unless a different unit is specified by the user. For example,
169 the following declaration sets @code{top-margin} to ten
178 To set it to @code{0.5} inches, use the @code{\in} unit suffix:
186 The available unit suffixes are @code{\mm}, @code{\cm},
187 @code{\in}, and @code{\pt}. These units are simple values for
188 converting from millimeters; they are defined in
189 @file{ly/paper-defaults-init.ly}. For the sake of clarity, when
190 using millimeters, the @code{\mm} is typically included in the
191 code, even though it is not technically necessary.
193 It is also possible to define @code{\paper} values using Scheme.
194 The Scheme equivalent of the above example is:
198 #(define top-margin (* 0.5 in))
204 @ref{Paper size and automatic scaling},
205 @ref{Custom titles headers and footers},
206 @ref{The layout block,,The @code{@bs{}layout} block}.
209 @file{ly/paper-defaults-init.ly}.
212 @node Paper size and automatic scaling
213 @subsection Paper size and automatic scaling
221 * Setting the paper size::
222 * Automatic scaling to paper size::
226 @node Setting the paper size
227 @unnumberedsubsubsec Setting the paper size
229 @q{A4} is the default value when no explicit paper size is set. However,
230 there are two functions that can be used to change it
231 @code{set-default-paper-size},
234 #(set-default-paper-size "quarto")
237 which must always be placed at the toplevel scope. and
238 @code{set-paper-size},
242 #(set-paper-size "tabloid")
246 which must always be placed in a @code{\paper} block.
248 If the @code{set-default-paper-size} function is used in the toplevel
249 scope, it must come before the any @code{\paper} block.
250 @code{set-default-paper-size} sets the paper size for all pages,
251 whereas @code{set-paper-size} only sets the paper size for the pages
252 that the @code{\paper} block applies to. For example, if the
253 @code{\paper} block is at the top of the file, then it will apply the
254 paper size to all pages. If the @code{\paper} block is inside a
255 @code{\book}, then the paper size will only apply to that book.
257 When the @code{set-paper-size} function is used, it must be
258 placed @emph{before} any other functions used within the same
259 @code{\paper} block. See @ref{Automatic scaling to paper size}.
261 Paper sizes are defined in @file{scm/paper.scm}, and while it is
262 possible to add custom sizes, they will be overwritten on subsequent
263 software updates. The available paper sizes are listed in
264 @ref{Predefined paper sizes}.
266 @c An appendix entry exists for paper sizes but is not auto-generated
268 The following command can be used in the file to add a custom paper size
269 which can then be used with @code{set-default-paper-size} or
270 @code{set-paper-size} as appropriate,
273 #(set! paper-alist (cons '("my size" . (cons (* 15 in) (* 3 in))) paper-alist))
276 #(set-paper-size "my size")
280 The units @code{in} (inches), @code{cm} (centimeters) and @code{mm}
281 (millimeters) can all be used.
283 @cindex paper size, orientation
284 @cindex page, orientation
285 @cindex paper size, landscape
287 If the symbol @code{'landscape} is added to the paper size function,
288 pages will be rotated by 90 degrees, and wider line widths will be set
292 #(set-default-paper-size "a6" 'landscape)
295 Swapping the paper dimensions @emph{without} having the print rotated
296 (like when printing to postcard size, or creating graphics for inclusion
297 rather than a standalone document) can be achieved by appending
298 @samp{landscape} to the name of the paper size itself:
301 #(set-default-paper-size "a6landscape")
304 When the paper size ends with an explicit @samp{landscape} or
305 @samp{portrait}, the presence of a @code{'landscape} symbol @emph{only}
306 affects print orientation, not the paper dimensions used for layout.
310 @ref{Automatic scaling to paper size},
311 @ref{Predefined paper sizes}.
314 @file{scm/paper.scm}.
317 @node Automatic scaling to paper size
318 @unnumberedsubsubsec Automatic scaling to paper size
320 If the paper size is changed with one of the scheme functions
321 (@code{set-default-paper-size} or @code{set-paper-size}), the
322 values of several @code{\paper} variables are automatically scaled
323 to the new size. To bypass the automatic scaling for a particular
324 variable, set the variable after setting the paper size. Note
325 that the automatic scaling is not triggered by setting the
326 @code{paper-height} or @code{paper-width} variables, even though
327 @code{paper-width} can influence other values (this is separate
328 from scaling and is discussed below). The
329 @code{set-default-paper-size} and @code{set-paper-size} functions
330 are described in @ref{Setting the paper size}.
332 The vertical dimensions affected by automatic scaling are
333 @code{top-margin} and @code{bottom-margin} (see
334 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables}).
336 dimensions affected by automatic scaling are @code{left-margin},
337 @code{right-margin}, @code{inner-margin}, @code{outer-margin},
338 @code{binding-offset}, @code{indent}, and @code{short-indent} (see
339 @ref{Horizontal spacing paper variables,,Horizontal spacing @code{@bs{}paper} variables}).
341 The default values for these dimensions are set in
342 @file{ly/paper-defaults-init.ly}, using internal variables named
343 @code{top-margin-default}, @code{bottom-margin-default}, etc.
344 These are the values that result at the default paper size
345 @code{a4}. For reference, with @code{a4} paper the
346 @code{paper-height} is @code{297\mm} and the @code{paper-width} is
351 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables},
352 @ref{Horizontal spacing paper variables,,Horizontal spacing @code{@bs{}paper} variables}.
355 @file{ly/paper-defaults-init.ly},
356 @file{scm/paper.scm}.
359 @node Fixed vertical spacing paper variables
360 @subsection Fixed vertical spacing @code{@bs{}paper} variables
362 @warning{Some @code{@bs{}paper} dimensions are automatically
363 scaled to the paper size, which may lead to unexpected behavior.
364 See @ref{Automatic scaling to paper size}.}
366 Default values (before scaling) are defined in
367 @file{ly/paper-defaults-init.ly}.
371 @funindex paper-height
373 The height of the page, unset by default. Note that the automatic
374 scaling of some vertical dimensions is not affected by this.
379 The margin between the top of the page and the top of the
380 printable area. If the paper size is modified, this dimension's
381 default value is scaled accordingly.
384 @funindex bottom-margin
386 The margin between the bottom of the printable area and the bottom
387 of the page. If the paper size is modified, this dimension's
388 default value is scaled accordingly.
391 @funindex ragged-bottom
393 If set to true, systems will not spread vertically down the page.
394 This does not affect the last page. This should be set to true
395 for pieces that have only two or three systems per page, for
396 example orchestral scores.
398 @item ragged-last-bottom
399 @funindex ragged-last-bottom
401 If set to false, systems will spread vertically down the last
402 page. Pieces that amply fill two pages or more should have this
403 set to false. It also affects the last page of book parts, i.e.
404 parts of a book created with @code{\bookpart} blocks.
410 @ref{Automatic scaling to paper size}.
413 @file{ly/paper-defaults-init.ly}.
419 The titles (from the @code{\header} block) are treated as a
420 system, so @code{ragged-bottom} and @code{ragged-last-bottom} will
421 add space between the titles and the first system of the score.
423 Explicitly defined paper-sizes will override any user-defined top or
424 bottom margin settings.
427 @node Flexible vertical spacing paper variables
428 @subsection Flexible vertical spacing @code{@bs{}paper} variables
430 In most cases, it is preferable for the vertical distances between
431 certain items (such as margins, titles, systems, and separate
432 scores) to be flexible, so that they stretch and compress nicely
433 according to each situation. A number of @code{\paper} variables
434 (listed below) are available to fine-tune the stretching behavior
437 Note that the @code{\paper} variables discussed in this section do
438 not control the spacing of staves within individual systems.
439 Within-system spacing is controlled by grob properties, with
440 settings typically entered inside a @code{\score} or
441 @code{\layout} block, and not inside a @code{\paper} block. See
442 @ref{Flexible vertical spacing within systems}.
445 * Structure of flexible vertical spacing alists::
446 * List of flexible vertical spacing paper variables::
450 @node Structure of flexible vertical spacing alists
451 @unnumberedsubsubsec Structure of flexible vertical spacing alists
453 Each of the flexible vertical spacing @code{\paper} variables is
454 an alist (association list) containing four @emph{keys}:
459 @code{basic-distance} -- the vertical distance, measured in
460 staff-spaces, between the @emph{reference points} of the two
461 items, when no collisions would result, and no stretching or
462 compressing is in effect. The reference point of a (title or
463 top-level) markup is its highest point, and the reference point of
464 a system is the vertical center of the nearest @code{StaffSymbol}
465 -- even if a non-staff line (such as a @code{Lyrics} context) is
466 in the way. Values for @code{basic-distance} that are less than
467 either @code{padding} or @code{minimum-distance} are not
468 meaningful, since the resulting distance will never be less than
469 either @code{padding} or @code{minimum-distance}.
472 @code{minimum-distance} -- the smallest allowable vertical
473 distance, measured in staff-spaces, between the reference points
474 of the two items, when compressing is in effect. Values for
475 @code{minimum-distance} that are less than @code{padding} are not
476 meaningful, since the resulting distance will never be less than
479 @c TODO: explain skylines somewhere and xref to it from here.
482 @code{padding} -- the minimum required amount of unobstructed
483 vertical whitespace between the bounding boxes (or skylines) of
484 the two items, measured in staff-spaces.
487 @code{stretchability} -- a unitless measure of the dimension's
488 relative propensity to stretch. If zero, the distance will not
489 stretch (unless collisions would result). When positive, the
490 significance of a particular dimension's @code{stretchability}
491 value lies only in its relation to the @code{stretchability}
492 values of the other dimensions. For example, if one dimension has
493 twice the @code{stretchability} of another, it will stretch twice
494 as easily. Values should be non-negative and finite. The value
495 @code{+inf.0} triggers a @code{programming_error} and is ignored,
496 but @code{1.0e7} can be used for an almost infinitely stretchable
497 spring. If unset, the default value is set to
498 @code{basic-distance}. Note that the dimension's propensity to
499 @emph{compress} cannot be directly set by the user and is equal to
500 (@code{basic-distance}@tie{}@minus{}@tie{}@code{minimum-distance}).
504 If a page has a ragged bottom, the resulting distance is the
510 @code{basic-distance},
513 @code{minimum-distance}, and
516 @code{padding} plus the smallest distance necessary to eliminate
521 For multi-page scores with a ragged bottom on the last page, the last
522 page uses the same spacing as the preceding page, provided there is
523 enough space for that.
525 Specific methods for modifying alists are discussed in
526 @ref{Modifying alists}. The following example demonstrates the
527 two ways these alists can be modified. The first declaration
528 updates one key-value individually, and the second completely
529 redefines the variable:
533 system-system-spacing #'basic-distance = #8
534 score-system-spacing =
535 #'((basic-distance . 12)
536 (minimum-distance . 6)
538 (stretchability . 12))
543 @node List of flexible vertical spacing paper variables
544 @unnumberedsubsubsec List of flexible vertical spacing @code{@bs{}paper} variables
546 The names of these variables follow the format
547 @code{@var{upper}-@var{lower}-spacing}, where @code{@var{upper}}
548 and @code{@var{lower}} are the items to be spaced. Each distance
549 is measured between the reference points of the two items (see the
550 description of the alist structure above). Note that in these
551 variable names, the term @q{@code{markup}} refers to both
552 @emph{title markups} (@code{bookTitleMarkup} or
553 @code{scoreTitleMarkup}) and @emph{top-level markups} (see
554 @ref{File structure}). All distances are measured in
557 Default settings are defined in @file{ly/paper-defaults-init.ly}.
559 @c TODO: Where do headers/footers fit in? -mp
562 @item markup-system-spacing
563 @funindex markup-system-spacing
565 the distance between a (title or top-level) markup and the system
568 @item score-markup-spacing
569 @funindex score-markup-spacing
571 the distance between the last system of a score and the (title or
572 top-level) markup that follows it.
574 @item score-system-spacing
575 @funindex score-system-spacing
577 the distance between the last system of a score and the first
578 system of the score that follows it, when no (title or top-level)
579 markup exists between them.
581 @item system-system-spacing
582 @funindex system-system-spacing
584 the distance between two systems in the same score.
586 @item markup-markup-spacing
587 @funindex markup-markup-spacing
589 the distance between two (title or top-level) markups.
591 @item last-bottom-spacing
592 @funindex last-bottom-spacing
594 the distance from the last system or top-level markup on a page to
595 the bottom of the printable area (i.e. the top of the bottom
598 @item top-system-spacing
599 @funindex top-system-spacing
601 the distance from the top of the printable area (i.e. the bottom
602 of the top margin) to the first system on a page, when there is no
603 (title or top-level) markup between the two.
605 @item top-markup-spacing
606 @funindex top-markup-spacing
608 the distance from the top of the printable area (i.e. the bottom
609 of the top margin) to the first (title or top-level) markup on a
610 page, when there is no system between the two.
615 @ref{Flexible vertical spacing within systems}.
618 @file{ly/paper-defaults-init.ly}.
624 @node Horizontal spacing paper variables
625 @subsection Horizontal spacing @code{@bs{}paper} variables
627 @warning{Some @code{@bs{}paper} dimensions are automatically
628 scaled to the paper size, which may lead to unexpected behavior.
629 See @ref{Automatic scaling to paper size}.}
632 * paper variables for widths and margins::
633 * paper variables for two-sided mode::
634 * paper variables for shifts and indents::
638 @node paper variables for widths and margins
639 @unnumberedsubsubsec @code{@bs{}paper} variables for widths and margins
641 Default values (before scaling) that are not listed here are
642 defined in @file{ly/paper-defaults-init.ly}.
647 @funindex paper-width
649 The width of the page, unset by default. While @code{paper-width}
650 has no effect on the automatic scaling of some horizontal
651 dimensions, it does influence the @code{line-width} variable. If
652 both @code{paper-width} and @code{line-width} are set, then
653 @code{left-margin} and @code{right-margin} will also be updated.
654 Also see @code{check-consistency}.
659 The horizontal extent of the staff lines in unindented, non-ragged
661 @code{(paper-width@tie{}@minus{}@tie{}left-margin@tie{}@minus{}@tie{}right-margin)}
662 when unset. If @code{line-width} is set, and both
663 @code{left-margin} and @code{right-margin} are unset, then the
664 margins will be updated to center the systems on the page
665 automatically. Also see @code{check-consistency}. This variable
666 can also be set in a @code{\layout} block.
669 @funindex left-margin
671 The margin between the left edge of the page and the start of the
672 staff lines in unindented systems. If the paper size is modified,
673 this dimension's default value is scaled accordingly. If
674 @code{left-margin} is unset, and both @code{line-width} and
675 @code{right-margin} are set, then @code{left-margin} is set to
676 @code{(paper-width@tie{}@minus{}@tie{}line-width@tie{}@minus{}@tie{}right-margin)}.
677 If only @code{line-width} is set, then both margins are set to
678 @code{((paper-width@tie{}@minus{}@tie{}line-width)@tie{}/@tie{}2)},
679 and the systems are consequently centered on the page. Also see
680 @code{check-consistency}.
683 @funindex right-margin
685 The margin between the right edge of the page and the end of the
686 staff lines in non-ragged systems. If the paper size is modified,
687 this dimension's default value is scaled accordingly. If
688 @code{right-margin} is unset, and both @code{line-width} and
689 @code{left-margin} are set, then @code{right-margin} is set to
690 @code{(paper-width@tie{}@minus{}@tie{}line-width@tie{}@minus{}@tie{}left-margin)}.
691 If only @code{line-width} is set, then both margins are set to
692 @code{((paper-width@tie{}@minus{}@tie{}line-width)@tie{}/@tie{}2)},
693 and the systems are consequently centered on the page. Also see
694 @code{check-consistency}.
696 @item check-consistency
697 @funindex check-consistency
699 If set to true, print a warning if @code{left-margin},
700 @code{line-width}, and @code{right-margin} do not exactly add up
701 to @code{paper-width}, and replace each of these (except
702 @code{paper-width}) with its default value (scaled to the paper
703 size if necessary). If set to false, ignore any inconsistencies
704 and allow systems to run off the edge of the page.
707 @funindex ragged-right
709 If set to true, systems will not fill the line width. Instead,
710 systems end at their natural horizontal length. Default:
711 @code{#t} for scores with only one system, and @code{#f} for
712 scores with two or more systems. This variable can also be set in
713 a @code{\layout} block.
716 @funindex ragged-last
718 If set to true, the last system in the score will not fill the
719 line width. Instead the last system ends at its natural
720 horizontal length. Default: @code{#f}. This variable can also be
721 set in a @code{\layout} block.
727 @ref{Automatic scaling to paper size}.
730 @file{ly/paper-defaults-init.ly}.
733 Explicitly defined paper-sizes will override any user-defined left or
734 right margin settings.
737 @node paper variables for two-sided mode
738 @unnumberedsubsubsec @code{@bs{}paper} variables for two-sided mode
740 Default values (before scaling) are defined in
741 @file{ly/paper-defaults-init.ly}.
749 @cindex binding gutter
751 If set to true, use @code{inner-margin}, @code{outer-margin} and
752 @code{binding-offset} to determine margins depending on whether
753 the page number is odd or even. This overrides @code{left-margin}
754 and @code{right-margin}.
757 @funindex inner-margin
759 The margin all pages have at the inner side if they are part of a
760 book. If the paper size is modified, this dimension's default
761 value is scaled accordingly. Works only with @code{two-sided} set
765 @funindex outer-margin
767 The margin all pages have at the outer side if they are part of a
768 book. If the paper size is modified, this dimension's default
769 value is scaled accordingly. Works only with @code{two-sided} set
773 @funindex binding-offset
775 The amount @code{inner-margin} is increased to make sure nothing
776 will be hidden by the binding. If the paper size is modified,
777 this dimension's default value is scaled accordingly. Works only
778 with @code{two-sided} set to true.
784 @ref{Automatic scaling to paper size}.
787 @file{ly/paper-defaults-init.ly}.
790 @node paper variables for shifts and indents
791 @unnumberedsubsubsec @code{@bs{}paper} variables for shifts and indents
793 Default values (before scaling) that are not listed here are
794 defined in @file{ly/paper-defaults-init.ly}.
798 @item horizontal-shift
799 @funindex horizontal-shift
801 @c This default value is buried in the middle of page.scm. -mp
803 The amount that all systems (including titles and system
804 separators) are shifted to the right. Default: @code{0.0\mm}.
809 The level of indentation for the first system in a score. If the
810 paper size is modified, this dimension's default value is scaled
811 accordingly. This variable can also be set in a @code{\layout}
815 @funindex short-indent
817 The level of indentation for all systems in a score besides the
818 first system. If the paper size is modified, this dimension's
819 default value is scaled accordingly. This variable can also be
820 set in a @code{\layout} block.
826 @ref{Automatic scaling to paper size}.
829 @file{ly/paper-defaults-init.ly}.
835 @node Other paper variables
836 @subsection Other @code{@bs{}paper} variables
839 * paper variables for line breaking::
840 * paper variables for page breaking::
841 * paper variables for page numbering::
842 * Miscellaneous paper variables::
846 @node paper variables for line breaking
847 @unnumberedsubsubsec @code{@bs{}paper} variables for line breaking
851 @item max-systems-per-page
852 @funindex max-systems-per-page
854 The maximum number of systems that will be placed on a page. This
855 is currently supported only by the @code{ly:optimal-breaking} algorithm.
858 @item min-systems-per-page
859 @funindex min-systems-per-page
861 The minimum number of systems that will be placed on a page. This
862 may cause pages to be overfilled if it is made too large. This is
863 currently supported only by the @code{ly:optimal-breaking} algorithm.
866 @item systems-per-page
867 @funindex systems-per-page
869 The number of systems that should be placed on each page.
870 This is currently supported only by the @code{ly:optimal-breaking} algorithm.
874 @funindex system-count
876 The number of systems to be used for a score. Default: unset.
877 This variable can also be set in a @code{\layout} block.
886 @node paper variables for page breaking
887 @unnumberedsubsubsec @code{@bs{}paper} variables for page breaking
889 Default values not listed here are defined in
890 @file{ly/paper-defaults-init.ly}
895 @funindex page-breaking
897 The page-breaking algorithm to use. Choices are
898 @code{ly:minimal-breaking}, @code{ly:page-turn-breaking},
899 @code{ly:one-line-breaking} and @code{ly:optimal-breaking}
902 @item page-breaking-system-system-spacing
903 @funindex page-breaking-system-system-spacing
905 Tricks the page breaker into thinking that
906 @code{system-system-spacing} is set to something different than
907 it really is. For example, if
908 @code{page-breaking-system-system-spacing #'padding} is set to something
909 substantially larger than @code{system-system-spacing #'padding}, then the
910 page-breaker will put fewer systems on each page. Default: unset.
915 The number of pages to be used for a score, unset by default.
919 The following variables are effective only when @code{page-breaking}
920 is set to @code{ly:page-turn-breaking}. Page breaks are then chosen
921 to minimize the number of page turns. Since page turns are required
922 on moving from an odd-numbered page to an even-numbered one, a
923 layout in which the last page is odd-numbered will usually be
924 favoured. Places where page turns are preferred can be indicated
925 manually by inserting @code{\allowPageTurn} or automatically by
926 including the @code{Page_turn_engraver} (see @ref{Optimal page turning}).
928 If there are insufficient choices available for making suitable page
929 turns, LilyPond may insert a blank page either within a score, between
930 scores (if there are two or more scores), or by ending a score on an
931 even-numbered page. The values of the following three variables may
932 be increased to make these actions less likely.
934 The values are penalties, i.e. the higher the value the less likely
935 will be the associated action relative to other choices.
939 @item blank-page-penalty
940 @funindex blank-page-penalty
942 The penalty for having a blank page in the middle of a score. If
943 @code{blank-page-penalty} is large and @code{ly:page-turn-breaking} is
944 selected, then LilyPond will be less likely to insert a page in the
945 middle of a score. Instead, it will space out the music further to
946 fill the blank page and the following one. Default: 5.
948 @item blank-last-page-penalty
949 @funindex blank-last-page-penalty
951 The penalty for ending the score on an even-numbered page. If
952 @code{blank-last-page-penalty} is large and
953 @code{ly:page-turn-breaking} is selected, then LilyPond will be less
954 likely to produce a score in which the last page is even-numbered.
955 Instead, it will adjust the spacing in order to use one page more or
956 one page less. Default: 0.
958 @item blank-after-score-page-penalty
959 @funindex blank-after-score-page-penalty
961 The penalty for having a blank page after the end of one score and
962 before the next. By default, this is smaller than
963 @code{blank-page-penalty}, so that blank pages after scores are
964 inserted in preference to blank pages within a score. Default: 2.
972 @ref{Optimal page breaking},
973 @ref{Optimal page turning},
974 @ref{Minimal page breaking},
975 @ref{One-line page breaking}.
978 @file{ly/paper-defaults-init.ly}.
981 @node paper variables for page numbering
982 @unnumberedsubsubsec @code{@bs{}paper} variables for page numbering
984 Default values not listed here are defined in
985 @file{ly/paper-defaults-init.ly}
989 @cindex page numbers, auto-numbering
990 @item auto-first-page-number
991 @funindex auto-first-page-number
993 The page breaking algorithm is affected by the first page number
994 being odd or even. If set to true, the page breaking algorithm
995 will decide whether to start with an odd or even number. This
996 will result in the first page number remaining as is or being
997 increased by one. Default: @code{#f}.
999 @cindex page numbers, specify the first
1000 @item first-page-number
1001 @funindex first-page-number
1003 The value of the page number on the first page.
1005 @item print-first-page-number
1006 @funindex print-first-page-number
1008 If set to true, a page number is printed on the first page.
1010 @cindex page numbers, suppress
1011 @item print-page-number
1012 @funindex print-page-number
1014 If set to false, page numbers are not printed.
1020 @file{ly/paper-defaults-init.ly}.
1023 Odd page numbers are always on the right. If you want the
1024 music to start on page 1 there must be a blank page on the back
1025 of the cover page so that page 1 is on the right hand side.
1028 @node Miscellaneous paper variables
1029 @unnumberedsubsubsec Miscellaneous @code{@bs{}paper} variables
1033 @item page-spacing-weight
1034 @funindex page-spacing-weight
1036 The relative importance of page (vertical) spacing and line
1037 (horizontal) spacing. High values will make page spacing more
1038 important. Default: @code{10}.
1040 @item print-all-headers
1041 @funindex print-all-headers
1043 If set to true, this will print all headers for each @code{\score}
1044 in the output. Normally only the @code{piece} and @code{opus}
1045 header variables are printed. Default: @code{#f}.
1047 @item system-separator-markup
1048 @funindex system-separator-markup
1050 A markup object that is inserted between systems, often used for
1051 orchestral scores. Default: unset. The @code{\slashSeparator}
1052 markup, defined in @file{ly/titling-init.ly}, is provided as a
1053 sensible default, for example:
1055 @lilypond[quote,verbatim,noragged-right,line-width=30\mm]
1056 #(set-default-paper-size "a8")
1060 system-separator-markup = \slashSeparator
1066 \relative c'' { c1 \break c1 \break c1 }
1075 @file{ly/titling-init.ly}.
1081 The default page header puts the page number and the @code{instrument}
1082 field from the @code{\header} block on a line.
1086 @section Score layout
1088 This section discusses score layout options for the @code{\layout}
1092 * The layout block::
1093 * Setting the staff size::
1097 @node The layout block
1098 @subsection The @code{@bs{}layout} block
1102 While the @code{\paper} block contains settings that relate to the
1103 page formatting of the whole document, the @code{\layout} block
1104 contains settings for score-specific layout. To set score layout
1105 options globally, enter them in a toplevel @code{\layout} block.
1106 To set layout options for an individual score, enter them in a
1107 @code{\layout} block inside the @code{\score} block, after the
1108 music. Settings that can appear in a @code{\layout} block
1112 @item the @code{layout-set-staff-size} scheme function,
1113 @item context modifications in @code{\context} blocks, and
1114 @item @code{\paper} variables that affect score layout.
1117 The @code{layout-set-staff-size} function is discussed in the next
1118 section, @ref{Setting the staff size}. Context modifications are
1119 discussed in a separate chapter; see
1120 @ref{Modifying context plug-ins} and
1121 @ref{Changing context default settings}. The @code{\paper}
1122 variables that can appear in a @code{\layout} block are:
1127 @code{line-width}, @code{ragged-right} and @code{ragged-last}
1128 (see @ref{paper variables for widths and margins,,@code{@bs{}paper} variables for widths and margins})
1131 @code{indent} and @code{short-indent}
1132 (see @ref{paper variables for shifts and indents,,@code{@bs{}paper} variables for shifts and indents})
1136 (see @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking})
1140 Here is an example @code{\layout} block:
1147 \override StaffGrouper.staff-staff-spacing.basic-distance = #8
1151 \override TextScript.padding = #1
1152 \override Glissando.thickness = #3
1157 Multiple @code{\layout} blocks can be entered as toplevel expressions.
1158 This can, for example, be useful if different settings are stored in
1159 separate files and included optionally. Internally, when
1160 a @code{\layout} block is evaluated, a copy of the current
1161 @code{\layout} configuration is made, then any changes defined within
1162 the block are applied and the result is saved as the new current
1163 configuration. From the user's perspective the @code{\layout} blocks
1164 are combined, but in conflicting situations (when the same property
1165 is changed in different blocks) the later definitions take precedence.
1167 For example, if this block:
1173 \override TextScript.color = #magenta
1174 \override Glissando.thickness = #1.5
1179 is placed after the one from the preceding example the @code{'padding}
1180 and @code{'color} overrides for @code{TextScript} are combined, but
1181 the later @code{'thickness} override for @code{Glissando} replaces
1182 (or hides) the earlier one.
1184 @code{\layout} blocks may be assigned to variables for reuse later,
1185 but the way this works is slightly but significantly different from
1186 writing them literally.
1188 If a variable is defined like this:
1191 layoutVariable = \layout @{
1194 \override NoteHead.font-size = #4
1199 it will hold the current @code{\layout} configuration with the
1200 @code{NoteHead.font-size} override added, but this combination
1201 is @emph{not} saved as the new current configuration. Be aware
1202 that the @q{current configuration} is read when the variable is
1203 defined and not when it is used, so the content of the variable
1204 is dependent on its position in the source.
1206 The variable can then be used inside another @code{\layout} block,
1214 \override NoteHead.color = #red
1219 A @code{\layout} block containing a variable, as in the example above,
1220 does @emph{not} copy the current configuration but instead uses the
1221 content of @code{\layoutVariable} as the base configuration for the
1222 further additions. This means that any changes defined between the
1223 definition and the use of the variable are lost.
1225 If @code{layoutVariable} is defined (or @code{\include}d) immediately
1226 before being used, its content is just the current configuration plus
1227 the overrides defined within it. So in the example above showing the
1228 use of @code{\layoutVariable} the final @code{\layout} block would
1232 TextScript.padding = #1
1233 TextScript.color = #magenta
1234 Glissando.thickness = #1.5
1235 NoteHead.font-size = #4
1236 NoteHead.color = #red
1239 plus the @code{indent} and the @code{StaffGrouper} overrides.
1241 But if the variable had already been defined before the first
1242 @code{\layout} block the current configuration would now contain
1246 NoteHead.font-size = #4 % (written in the variable definition)
1247 NoteHead.color = #red % (added after the use of the variable)
1250 If carefully planned, @code{\layout} variables can be a valuable tool
1251 to structure the layout design of sources, and also to reset the
1252 @code{\layout} configuration to a known state.
1256 @ref{Changing context default settings}.
1262 @node Setting the staff size
1263 @subsection Setting the staff size
1265 @cindex font size, setting
1266 @cindex staff size, setting
1267 @funindex layout file
1269 The default @strong{staff size} is set to 20 points.
1270 This may be changed in two ways:
1272 To set the staff size globally for all scores in a file (or
1273 in a @code{book} block, to be precise), use @code{set-global-staff-size}.
1276 #(set-global-staff-size 14)
1280 This sets the global default size to 14pt staff height and scales all
1283 To set the staff size individually for each score, use
1288 #(layout-set-staff-size 15)
1293 The Feta font provides musical symbols at eight different
1294 sizes. Each font is tuned for a different staff size: at a smaller size
1295 the font becomes heavier, to match the relatively heavier staff lines.
1296 The recommended font sizes are listed in the following table:
1299 @multitable @columnfractions .15 .2 .22 .2
1302 @tab @b{staff height (pt)}
1303 @tab @b{staff height (mm)}
1345 @c modern rental material?
1350 These fonts are available in any sizes. The context property
1351 @code{fontSize} and the layout property @code{staff-space} (in
1352 @rinternals{StaffSymbol}) can be used to tune the size for individual
1353 staves. The sizes of individual staves are relative to the global size.
1357 @ref{Selecting notation font size}.
1363 @code{layout-set-staff-size} does not change the distance between the
1373 * Optimal page breaking::
1374 * Optimal page turning::
1375 * Minimal page breaking::
1376 * One-line page breaking::
1378 * Using an extra voice for breaks::
1383 @subsection Line breaking
1386 @cindex breaking lines
1388 Line breaks are normally determined automatically. They are chosen
1389 so that lines look neither cramped nor loose, and consecutive
1390 lines have similar density.
1392 To manually force a line break at a bar line, use the
1393 @code{\break} command:
1395 @lilypond[quote,ragged-right,relative=2,verbatim]
1400 By default, a @code{\break} in the middle of a measure is ignored,
1401 and a warning is printed. To force a line break in the middle of
1402 a measure, add an invisible bar line with @w{@samp{\bar ""}}:
1404 @lilypond[quote,ragged-right,relative=2,verbatim]
1411 A @code{\break} occurring at a bar line is also ignored if the
1412 previous measure ends in the middle of a note, such as when a
1413 tuplet begins and ends in different measures. To allow
1414 @code{\break} commands to work in these situations, remove the
1415 @code{Forbid_line_break_engraver} from the @code{Voice} context.
1416 Note that manually forced line breaks have to be added in parallel
1419 @lilypond[quote,ragged-right,verbatim]
1421 \remove "Forbid_line_break_engraver"
1424 { c2. \tuplet 3/2 { c4 c c } c2. | }
1425 { s1 | \break s1 | }
1430 Similarly, line breaks are normally forbidden when beams cross bar
1431 lines. This behavior can be changed by setting
1432 @code{\override Beam.breakable = ##t}:
1434 @lilypond[quote,ragged-right,relative=2,verbatim]
1435 \override Beam.breakable = ##t
1440 The @code{\noBreak} command forbids a line break at the bar line
1441 where it is inserted.
1443 The most basic settings influencing line spacing are @code{indent}
1444 and @code{line-width}. They are set in the @code{\layout} block.
1445 They control the indentation of the first line of music, and the
1446 lengths of the lines.
1448 If @code{ragged-right} is set to true in the @code{\layout} block,
1449 then systems end at their natural horizontal length, instead of
1450 being spread horizontally to fill the whole line. This is useful
1451 for short fragments, and for checking how tight the natural
1454 @c TODO Check and add para on default for ragged-right
1456 The option @code{ragged-last} is similar to @code{ragged-right},
1457 but affects only the last line of the piece.
1469 @cindex regular line breaks
1470 @cindex four bar music.
1472 For line breaks at regular intervals use @code{\break} separated by
1473 skips and repeated with @code{\repeat}. For example, this would
1474 cause the following 28 measures (assuming 4/4 time) to be broken
1475 every 4 measures, and only there:
1480 s1 \noBreak s1 \noBreak
1481 s1 \noBreak s1 \break
1483 @{ @var{the actual music@dots{}} @}
1497 @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking}.
1502 Internals Reference:
1503 @rinternals{LineBreakEvent}.
1507 @subsection Page breaking
1509 The default page breaking may be overridden by inserting
1510 @code{\pageBreak} or @code{\noPageBreak} commands. These commands are
1511 analogous to @code{\break} and @code{\noBreak}. They should be
1512 inserted at a bar line. These commands force and forbid a page-break
1513 from happening. Of course, the @code{\pageBreak} command also forces
1516 The @code{\pageBreak} and @code{\noPageBreak} commands may also be
1517 inserted at top-level, between scores and top-level markups.
1519 There are also analogous settings to @code{ragged-right} and
1520 @code{ragged-last} which have the same effect on vertical spacing:
1521 @code{ragged-bottom} and @code{ragged-last-bottom}. If set to
1522 @code{#t} the systems on all pages or just the last page
1523 respectively will not be justified vertically. See
1524 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables}.
1526 Page breaks are computed by the @code{page-breaking} function. LilyPond
1527 provides three algorithms for computing page breaks,
1528 @code{ly:optimal-breaking}, @code{ly:page-turn-breaking} and
1529 @code{ly:minimal-breaking}. The default is @code{ly:optimal-breaking},
1530 but the value can be changed in the @code{\paper} block:
1534 page-breaking = #ly:page-turn-breaking
1540 When a book has many scores and pages, the page breaking problem may be
1541 difficult to solve, requiring large processing time and memory. To ease
1542 the page breaking process, @code{\bookpart} blocks are used to divide
1543 the book into several parts: the page breaking occurs separately on each
1544 part. Different page breaking functions may also be used in different
1550 subtitle = "Preface"
1553 %% In a part consisting mostly of text,
1554 %% ly:minimal-breaking may be preferred
1555 page-breaking = #ly:minimal-breaking
1557 \markup @{ @dots{} @}
1561 %% In this part, consisting of music, the default optimal
1562 %% page breaking function is used.
1564 subtitle = "First movement"
1566 \score @{ @dots{} @}
1573 @funindex \pageBreak
1575 @funindex \noPageBreak
1576 @code{\noPageBreak}.
1581 @ref{paper variables for page breaking,,@code{@bs{}paper} variables for page breaking}.
1587 @node Optimal page breaking
1588 @subsection Optimal page breaking
1590 @funindex ly:optimal-breaking
1592 The @code{ly:optimal-breaking} function is LilyPond's default method of
1593 determining page breaks. It attempts to find a page breaking that minimizes
1594 cramping and stretching, both horizontally and vertically. Unlike
1595 @code{ly:page-turn-breaking}, it has no concept of page turns.
1602 @node Optimal page turning
1603 @subsection Optimal page turning
1605 @funindex ly:page-turn-breaking
1607 Often it is necessary to find a page breaking configuration so that there is
1608 a rest at the end of every second page. This way, the musician can turn the
1609 page without having to miss notes. The @code{ly:page-turn-breaking} function
1610 attempts to find a page breaking minimizing cramping and stretching, but with
1611 the additional restriction that it is only allowed to introduce page turns
1612 in specified places.
1614 There are two steps to using this page breaking function. First, you
1615 must enable it in the @code{\paper} block, as explained in @ref{Page
1616 breaking}. Then you must tell the function where you would like to allow
1619 There are two ways to achieve the second step. First, you can specify each
1620 potential page turn manually, by inserting @code{\allowPageTurn} into your
1621 input file at the appropriate places.
1623 If this is too tedious, you can add a @code{Page_turn_engraver} to a Staff or
1624 Voice context. The @code{Page_turn_engraver} will scan the context for
1625 sections without notes (note that it does not scan for rests; it scans for
1626 the absence of notes. This is so that single-staff polyphony with rests in one
1627 of the parts does not throw off the @code{Page_turn_engraver}). When it finds
1628 a sufficiently long section without notes, the @code{Page_turn_engraver} will
1629 insert an @code{\allowPageTurn} at the final bar line in that section, unless
1630 there is a @q{special} bar line (such as a double bar), in which case the
1631 @code{\allowPageTurn} will be inserted at the final @q{special} bar line in
1634 @funindex minimumPageTurnLength
1635 The @code{Page_turn_engraver} reads the context property
1636 @code{minimumPageTurnLength} to determine how long a note-free section must
1637 be before a page turn is considered. The default value for
1638 @code{minimumPageTurnLength} is @code{(ly:make-moment 1/1)}. If you want
1639 to disable page turns, you can set it to something very large.
1642 \new Staff \with @{ \consists "Page_turn_engraver" @}
1645 R1 | % a page turn will be allowed here
1647 \set Staff.minimumPageTurnLength = #(ly:make-moment 5/2)
1648 R1 | % a page turn will not be allowed here
1650 R1*2 | % a page turn will be allowed here
1655 @funindex minimumRepeatLengthForPageTurn
1656 The @code{Page_turn_engraver} detects volta repeats. It will only allow a page
1657 turn during the repeat if there is enough time at the beginning and end of the
1658 repeat to turn the page back. The @code{Page_turn_engraver} can also disable
1659 page turns if the repeat is very short. If you set the context property
1660 @code{minimumRepeatLengthForPageTurn} then the @code{Page_turn_engraver} will
1661 only allow turns in repeats whose duration is longer than this value.
1663 The page turning commands, @code{\pageTurn}, @code{\noPageTurn} and
1664 @code{\allowPageTurn}, may also be used at top-level, between scores and
1670 @funindex \noPageTurn
1672 @funindex \allowPageTurn
1673 @code{\allowPageTurn}.
1678 @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking}.
1684 There should only be one @code{Page_turn_engraver} in a score. If there is more
1685 than one, they will interfere with each other.
1688 @node Minimal page breaking
1689 @subsection Minimal page breaking
1691 @funindex ly:minimal-breaking
1693 The @code{ly:minimal-breaking} function performs minimal computations to
1694 calculate the page breaking: it fills a page with as many systems as
1695 possible before moving to the next one. Thus, it may be preferred for
1696 scores with many pages, where the other page breaking functions could be
1697 too slow or memory demanding, or a lot of texts. It is enabled using:
1701 page-breaking = #ly:minimal-breaking
1709 @node One-line page breaking
1710 @subsection One-line page breaking
1712 @funindex ly:one-line-breaking
1714 The @code{ly:one-line-breaking} function is a special-purpose
1715 page breaking algorithm that puts each score on its own page,
1716 and on a single line. This page breaking function does not
1717 typeset titles or margins; only the score will be displayed.
1719 The page width will be adjusted so that
1720 the longest score fits on one line. In particular,
1721 @code{paper-width}, @code{line-width} and @code{indent}
1722 variables in the @code{\paper} block will be ignored, although
1723 @code{left-margin} and @code{right-margin} will
1724 still be honored. The height of the page will
1727 @node Explicit breaks
1728 @subsection Explicit breaks
1730 Lily sometimes rejects explicit @code{\break} and @code{\pageBreak}
1731 commands. There are two commands to override this behavior:
1734 \override NonMusicalPaperColumn.line-break-permission = ##f
1735 \override NonMusicalPaperColumn.page-break-permission = ##f
1738 When @code{line-break-permission} is overridden to false, Lily will insert
1739 line breaks at explicit @code{\break} commands and nowhere else. When
1740 @code{page-break-permission} is overridden to false, Lily will insert
1741 page breaks at explicit @code{\pageBreak} commands and nowhere else.
1743 @lilypond[quote,verbatim]
1750 music = \relative c'' { c8 c c c }
1754 \repeat unfold 2 { \music } \break
1755 \repeat unfold 4 { \music } \break
1756 \repeat unfold 6 { \music } \break
1757 \repeat unfold 8 { \music } \pageBreak
1758 \repeat unfold 8 { \music } \break
1759 \repeat unfold 6 { \music } \break
1760 \repeat unfold 4 { \music } \break
1761 \repeat unfold 2 { \music }
1766 \override NonMusicalPaperColumn.line-break-permission = ##f
1767 \override NonMusicalPaperColumn.page-break-permission = ##f
1778 @node Using an extra voice for breaks
1779 @subsection Using an extra voice for breaks
1781 Line- and page-breaking information usually appears within note entry directly.
1784 music = \relative c'' @{ c4 c c c @}
1788 \repeat unfold 2 @{ \music @} \break
1789 \repeat unfold 3 @{ \music @}
1794 This makes @code{\break} and @code{\pageBreak} commands easy to enter but mixes
1795 music entry with information that specifies how music should lay out
1796 on the page. You can keep music entry and line- and page-breaking
1797 information in two separate places by introducing an extra voice to
1798 contain the breaks. This extra voice
1799 contains only skips together with @code{\break}, @code{pageBreak} and other
1800 breaking layout information.
1802 @lilypond[quote,verbatim]
1803 music = \relative c'' { c4 c c c }
1805 \header { tagline = ##f }
1806 \paper { left-margin = 0\mm }
1817 \repeat unfold 2 { \music }
1818 \repeat unfold 3 { \music }
1819 \repeat unfold 6 { \music }
1820 \repeat unfold 5 { \music }
1827 This pattern becomes especially helpful when overriding
1828 @code{line-break-system-details} and the other useful but long properties of
1829 @code{NonMusicalPaperColumnGrob}, as explained in @ref{Vertical spacing}.
1831 @lilypond[quote,verbatim]
1832 music = \relative c'' { c4 c c c }
1834 \header { tagline = ##f }
1835 \paper { left-margin = 0\mm }
1840 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1844 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1848 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1852 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1857 \repeat unfold 2 { \music }
1858 \repeat unfold 3 { \music }
1859 \repeat unfold 6 { \music }
1860 \repeat unfold 5 { \music }
1869 @ref{Vertical spacing}.
1875 @node Vertical spacing
1876 @section Vertical spacing
1878 @cindex vertical spacing
1879 @cindex spacing, vertical
1881 Vertical spacing is controlled by three things: the amount of
1882 space available (i.e., paper size and margins), the amount of
1883 space between systems, and the amount of space between
1884 staves inside a system.
1887 * Flexible vertical spacing within systems::
1888 * Explicit staff and system positioning::
1889 * Vertical collision avoidance::
1893 @node Flexible vertical spacing within systems
1894 @subsection Flexible vertical spacing within systems
1896 @cindex distance between staves
1897 @cindex staff distance
1898 @cindex space between staves
1899 @cindex space inside systems
1901 Three separate mechanisms control the flexible vertical spacing
1902 within systems, one for each of the following categories:
1907 @emph{ungrouped staves},
1910 @emph{grouped staves} (staves within a staff-group such as
1911 @code{ChoirStaff}, etc.), and
1914 @emph{non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
1919 @c TODO: Clarify this. This almost implies that non-staff lines
1920 @c have NO effect on the spacing between staves. -mp
1922 The height of each system is determined in two steps. First, all
1923 of the staves are spaced according to the amount of space
1924 available. Then, the non-staff lines are distributed between the
1927 Note that the spacing mechanisms discussed in this section only
1928 control the vertical spacing of staves and non-staff lines within
1929 individual systems. The vertical spacing between separate
1930 systems, scores, markups, and margins is controlled by
1931 @code{\paper} variables, which are discussed in
1932 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables}.
1935 * Within-system spacing properties::
1936 * Spacing of ungrouped staves::
1937 * Spacing of grouped staves::
1938 * Spacing of non-staff lines::
1942 @node Within-system spacing properties
1943 @unnumberedsubsubsec Within-system spacing properties
1945 @funindex staff-affinity
1946 @funindex staffgroup-staff-spacing
1947 @funindex staff-staff-spacing
1948 @funindex nonstaff-unrelatedstaff-spacing
1949 @funindex nonstaff-relatedstaff-spacing
1950 @funindex nonstaff-nonstaff-spacing
1951 @funindex default-staff-staff-spacing
1952 @funindex minimum-Y-extent
1953 @funindex extra-offset
1954 @funindex self-alignment-X
1956 @funindex VerticalAxisGroup
1958 The within-system vertical spacing mechanisms are controlled by
1959 two sets of grob properties. The first set is associated with the
1960 @code{VerticalAxisGroup} grob, which is created by all staves and
1961 non-staff lines. The second set is associated with the
1962 @code{StaffGrouper} grob, which can be created by staff-groups,
1963 but only if explicitly called. These properties are described
1964 individually at the end of this section.
1966 The names of these properties (except for @code{staff-affinity})
1967 follow the format @code{@var{item1}-@var{item2}-spacing}, where
1968 @code{@var{item1}} and @code{@var{item2}} are the items to be
1969 spaced. Note that @code{@var{item2}} is not necessarily below
1970 @code{@var{item1}}; for example,
1971 @code{nonstaff-relatedstaff-spacing} will measure upwards from the
1972 non-staff line if @code{staff-affinity} is @code{UP}.
1974 Each distance is measured between the @emph{reference points} of
1975 the two items. The reference point for a staff is the vertical
1976 center of its @code{StaffSymbol} (i.e. the middle line if
1977 @code{line-count} is odd; the middle space if @code{line-count} is
1978 even). The reference points for individual non-staff lines are
1979 given in the following table:
1981 @multitable {Non-staff line} {Reference point}
1982 @headitem Non-staff line @tab Reference point
1983 @item @code{ChordNames} @tab baseline
1984 @item @code{NoteNames} @tab baseline
1985 @item @code{Lyrics} @tab baseline
1986 @item @code{Dynamics} @tab mid-height of @q{m}
1987 @item @code{FiguredBass} @tab highest point
1988 @item @code{FretBoards} @tab top line
1991 In the following image, horizontal lines indicate the positions
1992 of these reference points:
1994 @lilypond[quote,noragged-right,line-width=110\mm]
1995 #(define zero-space '((padding . -inf.0) (basic-distance . 0)))
1997 alignToZero = \with {
1998 \override VerticalAxisGroup.nonstaff-relatedstaff-spacing = #zero-space
1999 \override VerticalAxisGroup.nonstaff-nonstaff-spacing = #zero-space
2001 lowerCaseChords = \with {
2002 chordNameLowercaseMinor = ##t
2004 staffAffinityDown = \with {
2005 \override VerticalAxisGroup.staff-affinity = #DOWN
2008 #(define-music-function
2009 (parser location context)
2011 #{ s1*0^\markup { \typewriter #context } #})
2014 \context { \Dynamics \alignToZero }
2015 \context { \FiguredBass \alignToZero }
2016 \context { \Lyrics \alignToZero }
2017 \context { \NoteNames \alignToZero \staffAffinityDown }
2018 \context { \ChordNames \alignToZero
2021 \context { \FretBoards \alignToZero \staffAffinityDown }
2024 \override DynamicText.self-alignment-X = #-1
2025 \override FretBoard.X-offset = #1.75
2026 \override InstrumentName.minimum-Y-extent = #'(-2 . 2)
2027 \override InstrumentName.extra-offset = #'(0 . -0.5)
2028 \override TextScript.minimum-Y-extent = #'(-2 . 3)
2033 %% These contexts have reference points at the baseline:
2034 %% ChordNames, NoteNames, and Lyrics
2036 \new ChordNames { \chords { g1:m } }
2037 \new NoteNames { s1 | g1 | }
2038 \new RhythmicStaff {
2039 \set RhythmicStaff.instrumentName = #"baseline "
2041 \labelContext "ChordNames " s1 |
2042 \labelContext "NoteNames " s1 |
2043 \labelContext "Lyrics" s1 |
2045 \new Lyrics { \lyrics { \skip 1*2 | ghijk1 | } }
2048 %% The reference point for Dynamics is the midline of 'm' in the font
2050 \new RhythmicStaff {
2051 \set RhythmicStaff.instrumentName = #"mid-height "
2052 \labelContext "Dynamics" s1*3
2054 \new Dynamics { s1\mp s\fp }
2057 %% The reference point for FiguredBass is its highest point
2059 \new RhythmicStaff {
2060 \set RhythmicStaff.instrumentName = #"highest point "
2061 \labelContext "FiguredBass" s1
2063 \new FiguredBass { \figuremode { <6 5>1 } }
2066 %% The reference point for FretBoards is the top line
2067 \include "predefined-guitar-fretboards.ly"
2069 \new FretBoards { \chordmode { e1 } }
2070 \new RhythmicStaff {
2071 \set RhythmicStaff.instrumentName = #"top line "
2072 \labelContext "FretBoards " s1
2077 Each of the vertical spacing grob properties (except
2078 @code{staff-affinity}) uses the same alist structure as the
2079 @code{\paper} spacing variables discussed in
2080 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables}.
2082 for modifying alists are discussed in @ref{Modifying alists}.
2083 Grob properties should be adjusted with an @code{\override} inside
2084 a @code{\score} or @code{\layout} block, and not inside a
2085 @code{\paper} block.
2087 The following example demonstrates the two ways these alists can
2088 be modified. The first declaration updates one key-value
2089 individually, and the second completely re-defines the property:
2093 \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #10
2097 \override VerticalAxisGroup.default-staff-staff-spacing =
2098 #'((basic-distance . 10)
2099 (minimum-distance . 9)
2101 (stretchability . 10))
2105 To change any spacing settings globally, put them in the
2106 @code{\layout} block:
2112 \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #10
2117 Standard settings for the vertical spacing grob properties are
2118 listed in @rinternals{VerticalAxisGroup} and
2119 @rinternals{StaffGrouper}. Default overrides for specific types
2120 of non-staff lines are listed in the relevant context descriptions
2121 in @rinternals{Contexts}.
2124 @subsubheading Properties of the @code{VerticalAxisGroup} grob
2126 @code{VerticalAxisGroup} properties are typically adjusted with an
2127 @code{\override} at the @code{Staff} level (or equivalent).
2130 @item staff-staff-spacing
2132 Used to determine the distance between the current staff and the
2133 staff just below it in the same system, even if one or more
2134 non-staff lines (such as @code{Lyrics}) are placed between the two
2135 staves. Does not apply to the bottom staff of a system.
2137 Initially, the @code{staff-staff-spacing} of a
2138 @code{VerticalAxisGroup} is a Scheme function that applies the
2139 properties of the @code{StaffGrouper} if the staff is part of a
2140 group, or the @code{default-staff-staff-spacing} of the staff
2141 otherwise. This allows staves to be spaced differently when they
2142 are grouped. For uniform spacing regardless of grouping, this
2143 function may be replaced by a flexible-spacing alist, using the
2144 complete-redefinition form of override shown above.
2146 @item default-staff-staff-spacing
2147 A flexible-spacing alist defining the @code{staff-staff-spacing} used for
2148 ungrouped staves, unless @code{staff-staff-spacing} has been explicitly
2149 set with an @code{\override}.
2151 @item staff-affinity
2152 The direction of the staff to use for spacing the current
2153 non-staff line. Choices are @code{UP}, @code{DOWN}, and
2154 @code{CENTER}. If @code{CENTER}, the non-staff line will be
2155 placed equidistant between the two nearest staves on either side,
2156 unless collisions or other spacing constraints prevent this.
2157 Adjacent non-staff lines should have non-increasing
2158 @code{staff-affinity} from top to bottom, e.g. a non-staff line
2159 set to @code{UP} should not immediately follow one that is set to
2160 @code{DOWN}. Non-staff lines at the top of a system should use
2161 @code{DOWN}; those at the bottom should use @code{UP}. Setting
2162 @code{staff-affinity} for a staff causes it to be treated as a
2163 non-staff line. Setting @code{staff-affinity} to @code{#f} causes
2164 a non-staff line to be treated as a staff. Setting
2165 @code{staff-affinity} to @code{UP}, @code{CENTER}, or @code{DOWN}
2166 causes a staff to be spaced as a non-staff line.
2168 @item nonstaff-relatedstaff-spacing
2169 The distance between the current non-staff line and the nearest
2170 staff in the direction of @code{staff-affinity}, if there are no
2171 non-staff lines between the two, and @code{staff-affinity} is
2172 either @code{UP} or @code{DOWN}. If @code{staff-affinity} is
2173 @code{CENTER}, then @code{nonstaff-relatedstaff-spacing} is used
2174 for the nearest staves on @emph{both} sides, even if other
2175 non-staff lines appear between the current one and either of the
2176 staves. This means that the placement of a non-staff line depends
2177 on both the surrounding staves and the surrounding non-staff lines.
2178 Setting the @code{stretchability} of one of these types of spacing to
2179 a small value will make that spacing dominate. Setting the
2180 @code{stretchability} to a large value will make that spacing have
2183 @item nonstaff-nonstaff-spacing
2184 The distance between the current non-staff line and the next
2185 non-staff line in the direction of @code{staff-affinity}, if both
2186 are on the same side of the related staff, and
2187 @code{staff-affinity} is either @code{UP} or @code{DOWN}.
2189 @item nonstaff-unrelatedstaff-spacing
2190 The distance between the current non-staff line and the staff in
2191 the opposite direction from @code{staff-affinity}, if there are no
2192 other non-staff lines between the two, and @code{staff-affinity}
2193 is either @code{UP} or @code{DOWN}. This can be used, for
2194 example, to require a minimum amount of padding between a
2195 @code{Lyrics} line and the staff to which it does not belong.
2199 @subsubheading Properties of the @code{StaffGrouper} grob
2201 @code{StaffGrouper} properties are typically adjusted with an
2202 @code{\override} at the @code{StaffGroup} level (or equivalent).
2205 @item staff-staff-spacing
2206 The distance between consecutive staves within the current
2207 staff-group. The @code{staff-staff-spacing} property of an
2208 individual staff's @code{VerticalAxisGroup} grob can be
2209 overriden with different spacing settings for that staff.
2211 @item staffgroup-staff-spacing
2212 The distance between the last staff of the current staff-group and
2213 the staff just below it in the same system, even if one or more
2214 non-staff lines (such as @code{Lyrics}) exist between the two
2215 staves. Does not apply to the bottom staff of a system. The
2216 @code{staff-staff-spacing} property of an individual staff's
2217 @code{VerticalAxisGroup} grob can be overriden with different
2218 spacing settings for that staff.
2223 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables},
2224 @ref{Modifying alists}.
2227 @file{ly/engraver-init.ly},
2228 @file{scm/define-grobs.scm}.
2230 Internals Reference:
2231 @rinternals{Contexts},
2232 @rinternals{VerticalAxisGroup},
2233 @rinternals{StaffGrouper}.
2236 @node Spacing of ungrouped staves
2237 @unnumberedsubsubsec Spacing of ungrouped staves
2239 @emph{Staves} (such as @code{Staff}, @code{DrumStaff},
2240 @code{TabStaff}, etc.) are contexts that can contain one or more
2241 voice contexts, but cannot contain any other staves.
2243 The following properties affect the spacing of @emph{ungrouped}
2247 @item @code{VerticalAxisGroup} properties:
2249 @item @code{default-staff-staff-spacing}
2250 @item @code{staff-staff-spacing}
2254 These grob properties are described individually above; see
2255 @ref{Within-system spacing properties}.
2257 Additional properties are involved for staves that are part of a
2258 staff-group; see @ref{Spacing of grouped staves}.
2260 The following example shows how the @code{default-staff-staff-spacing}
2261 property can affect the spacing of ungrouped staves.
2262 The same overrides applied to @code{staff-staff-spacing} would
2263 have the same effect, but would also apply in cases where the staves
2264 are combined in a group or groups.
2266 @lilypond[verbatim,quote,staffsize=16]
2270 \override VerticalAxisGroup.default-staff-staff-spacing =
2271 #'((basic-distance . 8)
2272 (minimum-distance . 7)
2278 % The very low note here needs more room than 'basic-distance
2279 % can provide, so the distance between this staff and the next
2280 % is determined by 'padding.
2281 \new Staff { b,2 r | }
2283 % Here, 'basic-distance provides enough room, and there is no
2284 % need to compress the space (towards 'minimum-distance) to make
2285 % room for anything else on the page, so the distance between
2286 % this staff and the next is determined by 'basic-distance.
2287 \new Staff { \clef bass g2 r | }
2289 % By setting 'padding to a negative value, staves can be made to
2290 % collide. The lowest acceptable value for 'basic-distance is 0.
2292 \override VerticalAxisGroup.default-staff-staff-spacing =
2293 #'((basic-distance . 3.5)
2295 } { \clef bass g2 r | }
2296 \new Staff { \clef bass g2 r | }
2302 @file{scm/define-grobs.scm}.
2307 Internals Reference:
2308 @rinternals{VerticalAxisGroup}.
2311 @node Spacing of grouped staves
2312 @unnumberedsubsubsec Spacing of grouped staves
2314 In orchestral and other large scores, it is common to place staves
2315 in groups. The space between groups is typically larger than the
2316 space between staves of the same group.
2318 @emph{Staff-groups} (such as @code{StaffGroup}, @code{ChoirStaff},
2319 etc.) are contexts that can contain one or more staves
2322 The following properties affect the spacing of staves inside
2326 @item @code{VerticalAxisGroup} properties:
2328 @item @code{staff-staff-spacing}
2330 @item @code{StaffGrouper} properties:
2332 @item @code{staff-staff-spacing}
2333 @item @code{staffgroup-staff-spacing}
2337 These grob properties are described individually above; see
2338 @ref{Within-system spacing properties}.
2340 The following example shows how properties of the
2341 @code{StaffGrouper} grob can affect the spacing of grouped staves:
2343 @lilypond[verbatim,quote,staffsize=16]
2347 \override StaffGrouper.staff-staff-spacing.padding = #0
2348 \override StaffGrouper.staff-staff-spacing.basic-distance = #1
2353 \new PianoStaff \with {
2354 \override StaffGrouper.staffgroup-staff-spacing.basic-distance = #20
2369 @file{scm/define-grobs.scm}.
2374 Internals Reference:
2375 @rinternals{VerticalAxisGroup},
2376 @rinternals{StaffGrouper}.
2379 @node Spacing of non-staff lines
2380 @unnumberedsubsubsec Spacing of non-staff lines
2382 @emph{Non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
2383 etc.) are contexts whose layout objects are engraved like staves
2384 (i.e. in horizontal lines within systems). Specifically,
2385 non-staff lines are non-staff contexts that create the
2386 @code{VerticalAxisGroup} layout object.
2388 The following properties affect the spacing of non-staff lines:
2391 @item @code{VerticalAxisGroup} properties:
2393 @item @code{staff-affinity}
2394 @item @code{nonstaff-relatedstaff-spacing}
2395 @item @code{nonstaff-nonstaff-spacing}
2396 @item @code{nonstaff-unrelatedstaff-spacing}
2400 These grob properties are described individually above; see
2401 @ref{Within-system spacing properties}.
2403 The following example shows how the
2404 @code{nonstaff-nonstaff-spacing} property can affect the spacing
2405 of consecutive non-staff lines. Here, by setting the
2406 @code{stretchability} key to a very high value, the lyrics are
2407 able to stretch much more than usual:
2409 @lilypond[verbatim,quote,staffsize=16]
2413 \override VerticalAxisGroup.nonstaff-nonstaff-spacing.stretchability = #1000
2420 \override VerticalAxisGroup.staff-staff-spacing = #'((basic-distance . 30))
2423 \override VerticalAxisGroup.staff-affinity = #UP
2426 \override VerticalAxisGroup.staff-affinity = #CENTER
2427 } \lyricmode { center }
2429 \override VerticalAxisGroup.staff-affinity = #DOWN
2430 } \lyricmode { down }
2437 @file{ly/engraver-init.ly},
2438 @file{scm/define-grobs.scm}.
2443 @c @lsr{spacing,page-spacing.ly},
2444 @c @lsr{spacing,alignment-vertical-spacing.ly}.
2446 Internals Reference:
2447 @rinternals{Contexts},
2448 @rinternals{VerticalAxisGroup}.
2451 @node Explicit staff and system positioning
2452 @subsection Explicit staff and system positioning
2454 One way to understand the flexible vertical spacing mechanisms
2455 explained above is as a collection of settings that control the
2456 amount of vertical padding between staves and systems.
2458 It is possible to approach vertical spacing in a different way
2459 using @code{NonMusicalPaperColumn.line-break-system-details}.
2460 While the flexible vertical spacing mechanisms specify vertical
2461 padding, @code{NonMusicalPaperColumn.line-break-system-details}
2462 can specify exact vertical positions on the page.
2464 @code{NonMusicalPaperColumn.line-break-system-details} accepts
2465 an associative list of three different settings:
2468 @item @code{X-offset}
2469 @item @code{Y-offset}
2470 @item @code{alignment-distances}
2473 Grob overrides, including the overrides for @code{NonMusicalPaperColumn}
2474 below, can occur in any of three different places in an input file:
2477 @item in the middle of note entry directly
2478 @item in a @code{\context} block
2479 @item in the @code{\with} block
2482 When we override @code{NonMusicalPaperColumn}, we use the usual
2483 @code{\override} command in @code{\context} blocks and in the
2484 @code{\with} block. On the other hand, when we override
2485 @code{NonMusicalPaperColumn} in the middle of note entry,
2486 use the special @code{\overrideProperty} command. Here are some
2487 example @code{NonMusicalPaperColumn} overrides with the special
2488 @code{\overrideProperty} command:
2491 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2494 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2497 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2501 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2502 #'((alignment-distances . (15)))
2504 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2507 (alignment-distances . (15)))
2510 To understand how each of these different settings work, we begin
2511 by looking at an example that includes no overrides at all.
2513 @c \book { } is required in these examples to ensure the spacing
2514 @c overrides can be seen between systems. -np
2516 @lilypond[verbatim,quote,staffsize=16]
2517 \header { tagline = ##f }
2518 \paper { left-margin = 0\mm }
2528 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2531 \repeat unfold 15 { d'4 d' d' d' }
2538 This score isolates line- and page-breaking information in a dedicated
2539 voice. This technique of creating a breaks voice will help keep layout
2540 separate from music entry as our example becomes more complicated.
2541 See @ref{Using an extra voice for breaks}.
2543 Explicit @code{\breaks} evenly divide the music into six measures per
2544 line. Vertical spacing results from LilyPond's defaults. To set
2545 the vertical startpoint of each system explicitly, we can set
2546 the @code{Y-offset} pair in the @code{line-break-system-details}
2547 attribute of the @code{NonMusicalPaperColumn} grob:
2549 @lilypond[verbatim,quote,staffsize=16]
2550 \header { tagline = ##f }
2551 \paper { left-margin = 0\mm }
2557 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2560 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2563 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2567 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2570 \repeat unfold 15 { d'4 d' d' d' }
2577 Note that @code{line-break-system-details} takes an associative list of
2578 potentially many values, but that we set only one value here. Note,
2579 too, that the @code{Y-offset} property here determines the exact vertical
2580 position on the page at which each new system will render.
2582 Now that we have set the vertical startpoint of each system
2583 explicitly, we can also set the vertical distances between staves
2584 within each system manually. We do this using the @code{alignment-distances}
2585 subproperty of @code{line-break-system-details}.
2587 @lilypond[verbatim,quote,staffsize=16]
2588 \header { tagline = ##f }
2589 \paper { left-margin = 0\mm }
2595 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2597 (alignment-distances . (10)))
2599 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2601 (alignment-distances . (15)))
2603 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2605 (alignment-distances . (20)))
2608 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2611 \repeat unfold 15 { d'4 d' d' d' }
2618 Note that here we assign two different values to the
2619 @code{line-break-system-details} attribute of the
2620 @code{NonMusicalPaperColumn} grob. Though the
2621 @code{line-break-system-details} attribute alist accepts many
2622 additional spacing parameters (including, for example, a corresponding
2623 @code{X-offset} pair), we need only set the @code{Y-offset} and
2624 @code{alignment-distances} pairs to control the vertical startpoint of
2625 every system and every staff. Finally, note that @code{alignment-distances}
2626 specifies the vertical positioning of staves but not of staff groups.
2628 @lilypond[verbatim,quote,staffsize=16]
2629 \header { tagline = ##f }
2630 \paper { left-margin = 0\mm }
2636 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2638 (alignment-distances . (30 10)))
2640 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2642 (alignment-distances . (10 10)))
2644 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2646 (alignment-distances . (10 30)))
2649 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2652 \new Staff { \repeat unfold 15 { d'4 d' d' d' } }
2653 \new Staff { \repeat unfold 15 { e'4 e' e' e' } }
2660 Some points to consider:
2663 @item When using @code{alignment-distances}, lyrics and other non-staff lines
2664 do not count as a staff.
2666 @item The units of the numbers passed to @code{X-offset},
2667 @code{Y-offset} and @code{alignment-distances} are interpreted as multiples
2668 of the distance between adjacent staff lines. Positive values move staves
2669 and lyrics up, negative values move staves and lyrics down.
2671 @item Because the @code{NonMusicalPaperColumn.line-break-system-details}
2672 settings given here allow the positioning of staves and systems anywhere
2673 on the page, it is possible to violate paper or margin boundaries or even
2674 to print staves or systems on top of one another. Reasonable values
2675 passed to these different settings will avoid this.
2683 @node Vertical collision avoidance
2684 @subsection Vertical collision avoidance
2686 @funindex outside-staff-priority
2687 @funindex outside-staff-padding
2688 @funindex outside-staff-horizontal-padding
2690 Intuitively, there are some objects in musical notation that belong
2691 to the staff and there are other objects that should be placed outside
2692 the staff. Objects belonging outside the staff include things such as
2693 rehearsal marks, text and dynamic markings (from now on, these will
2694 be called outside-staff objects). LilyPond's rule for the
2695 vertical placement of outside-staff objects is to place them as close
2696 to the staff as possible but not so close that they collide with
2699 LilyPond uses the @code{outside-staff-priority} property to determine
2700 whether a grob is an outside-staff object: if @code{outside-staff-priority}
2701 is a number, the grob is an outside-staff object. In addition,
2702 @code{outside-staff-priority} tells LilyPond in which order the objects
2705 First, LilyPond places all the objects that do not belong outside
2706 the staff. Then it sorts the outside-staff objects according to their
2707 @code{outside-staff-priority} (in increasing order). One by one, LilyPond
2708 takes the outside-staff objects and places them so that they do
2709 not collide with any objects that have already been placed. That
2710 is, if two outside-staff grobs are competing for the same space, the one
2711 with the lower @code{outside-staff-priority} will be placed closer to
2714 @lilypond[quote,ragged-right,relative=2,verbatim]
2717 \once \override TextScript.outside-staff-priority = #1
2718 c4_"Text"\pp % this time the text will be closer to the staff
2720 % by setting outside-staff-priority to a non-number,
2721 % we disable the automatic collision avoidance
2722 \once \override TextScript.outside-staff-priority = ##f
2723 \once \override DynamicLineSpanner.outside-staff-priority = ##f
2724 c4_"Text"\pp % now they will collide
2727 The vertical padding around outside-staff objects
2728 can be controlled with @code{outside-staff-padding}.
2730 @lilypond[quote,ragged-right,relative=2,verbatim,staffsize=18]
2731 \once \override TextScript.outside-staff-padding = #0
2732 a4-"outside-staff-padding = #0"
2733 \once \override TextScript.outside-staff-padding = #3
2734 d-"outside-staff-padding = #3"
2735 c-"default outside-staff-padding"
2736 b-"default outside-staff-padding"
2741 By default, outside-staff objects are placed so they avoid
2742 a horizontal collision with previously-positioned grobs. This
2743 can lead to situations in which objects are placed close to each
2745 As shown in the example below, setting @code{outside-staff-horizontal-padding}
2746 increases the horizontal spacing required, and in this case moves the text up
2747 to prevent it from getting too close to the ledger lines.
2749 @lilypond[quote,ragged-right,relative=2,verbatim]
2752 \once \override TextScript.outside-staff-horizontal-padding = #1
2761 @node Horizontal spacing
2762 @section Horizontal spacing
2764 @cindex horizontal spacing
2765 @cindex spacing, horizontal
2768 * Horizontal spacing overview::
2769 * New spacing area::
2770 * Changing horizontal spacing::
2772 * Proportional notation::
2776 @node Horizontal spacing overview
2777 @subsection Horizontal spacing overview
2779 The spacing engine translates differences in durations into stretchable
2780 distances (@q{springs}) of differing lengths. Longer durations get
2781 more space, shorter durations get less. The shortest durations get a
2782 fixed amount of space (which is controlled by
2783 @code{shortest-duration-space} in the @rinternals{SpacingSpanner}
2784 object). The longer the duration, the more space it gets: doubling a
2785 duration adds a fixed amount (this amount is controlled by
2786 @code{spacing-increment}) of space to the note.
2788 For example, the following piece contains lots of half, quarter, and
2789 8th notes; the eighth note is followed by 1 note head width (NHW).
2790 The quarter note is followed by 2 NHW, the half by 3 NHW, etc.
2792 @lilypond[quote,verbatim,relative=1]
2798 Normally, @code{spacing-increment} is set to 1.2 staff space, which is
2799 approximately the width of a note head, and
2800 @code{shortest-duration-space} is set to 2.0, meaning that the
2801 shortest note gets 2.4 staff space (2.0 times the
2802 @code{spacing-increment}) of horizontal space. This space is counted
2803 from the left edge of the symbol, so the shortest notes are generally
2804 followed by one NHW of space.
2806 If one would follow the above procedure exactly, then adding a single
2807 32nd note to a score that uses 8th and 16th notes, would widen up the
2808 entire score a lot. The shortest note is no longer a 16th, but a 32nd,
2809 thus adding 1 NHW to every note. To prevent this, the shortest
2810 duration for spacing is not the shortest note in the score, but rather
2811 the one which occurs most frequently.
2814 The most common shortest duration is determined as follows: in every
2815 measure, the shortest duration is determined. The most common shortest
2816 duration is taken as the basis for the spacing, with the stipulation
2817 that this shortest duration should always be equal to or shorter than
2818 an 8th note. The shortest duration is printed when you run
2819 @code{lilypond} with the @option{--verbose} option.
2821 These durations may also be customized. If you set the
2822 @code{common-shortest-duration} in @rinternals{SpacingSpanner}, then
2823 this sets the base duration for spacing. The maximum duration for this
2824 base (normally an 8th), is set through @code{base-shortest-duration}.
2826 @funindex common-shortest-duration
2827 @funindex base-shortest-duration
2828 @funindex stem-spacing-correction
2831 Notes that are even shorter than the common shortest note are
2832 followed by a space that is proportional to their duration relative to
2833 the common shortest note. So if we were to add only a few 16th notes
2834 to the example above, they would be followed by half a NHW:
2836 @lilypond[quote,verbatim,relative=2]
2837 c2 c4. c8 | c4. c16[ c] c4. c8 | c8 c c4 c c
2841 In the @emph{Essay on automated music engraving}, it was explained
2842 that stem directions influence spacing (see
2843 @ressay{Optical spacing}). This is controlled with the
2844 @code{stem-spacing-correction} property in the
2845 @rinternals{NoteSpacing}, object. These are generated for every
2846 @rinternals{Voice} context. The @code{StaffSpacing} object
2847 (generated in @rinternals{Staff} context) contains the same
2848 property for controlling the stem/bar line spacing. The following
2849 example shows these corrections, once with default settings, and
2850 once with exaggerated corrections:
2852 @lilypond[quote,ragged-right]
2856 \override Staff.NoteSpacing.stem-spacing-correction = #1.5
2857 \override Staff.StaffSpacing.stem-spacing-correction = #1.5
2863 Proportional notation is supported; see @ref{Proportional notation}.
2866 Essay on automated music engraving:
2867 @ressay{Optical spacing}.
2872 Internals Reference:
2873 @rinternals{SpacingSpanner},
2874 @rinternals{NoteSpacing},
2875 @rinternals{StaffSpacing},
2876 @rinternals{NonMusicalPaperColumn}.
2879 There is no convenient mechanism to manually override spacing. The
2880 following work-around may be used to insert extra space into a score,
2881 adjusting the padding value as necessary.
2884 \override Score.NonMusicalPaperColumn.padding = #10
2887 No work-around exists for decreasing the amount of space.
2890 @node New spacing area
2891 @subsection New spacing area
2893 @funindex \newSpacingSection
2894 @cindex new spacing area
2895 @cindex spacing area, new
2896 @cindex notes, spacing horizontally
2898 New sections with different spacing parameters can be started with
2899 @code{newSpacingSection}. This is useful when there are
2900 sections with a different notions of long and short notes.
2902 In the following example, the time signature change introduces a new
2903 section, and hence the 16ths notes are automatically spaced slightly
2906 @lilypond[relative=1,verbatim,quote]
2909 c8 c c4 c16[ c c8] c4
2915 The @code{\newSpacingSection} command creates a new
2916 @code{SpacingSpanner} object at that musical moment.
2917 If the automatic spacing adjustments do not give the required spacing,
2918 manual @code{\override}s may be applied to its properties. These must
2919 be applied at the same musical moment as the @code{\newSpacingSection}
2920 command itself. They will then affect the spacing of all the following
2921 music until the properties are changed in a new spacing section, for
2924 @lilypond[relative=1,verbatim,quote]
2928 \override Score.SpacingSpanner.spacing-increment = #2
2931 \revert Score.SpacingSpanner.spacing-increment
2940 Internals Reference:
2941 @rinternals{SpacingSpanner}.
2944 @node Changing horizontal spacing
2945 @subsection Changing horizontal spacing
2947 Horizontal spacing may be altered with the
2948 @code{base-shortest-duration} property. Here
2949 we compare the same music; once without altering
2950 the property, and then altered. Larger values
2951 of @code{ly:make-moment} will produce smaller
2952 music. Note that @code{ly:make-moment} constructs
2953 a duration, so @code{1 4} is a longer duration
2956 @lilypond[verbatim,line-width=12\cm]
2959 g4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2960 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2961 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2962 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2967 @lilypond[verbatim,line-width=12\cm]
2970 g4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2971 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2972 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2973 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2978 \override SpacingSpanner.base-shortest-duration = #(ly:make-moment 1/16)
2987 By default, spacing in tuplets depends on various non-duration
2988 factors (such as accidentals, clef changes, etc). To disregard
2989 such symbols and force uniform equal-duration spacing, use
2990 @code{Score.SpacingSpanner.uniform-stretching}. This
2991 property can only be changed at the beginning of a score,
2993 @lilypond[quote,ragged-right,verbatim]
2997 \tuplet 5/4 { c8 c c c c } c8 c c c
3000 c8 c c c \tuplet 5/4 { c8 c c c c }
3006 \override SpacingSpanner.uniform-stretching = ##t
3012 When @code{strict-note-spacing} is set, notes are spaced without
3013 regard for clefs, bar lines, and grace notes,
3015 @lilypond[quote,ragged-right,relative=2,verbatim]
3016 \override Score.SpacingSpanner.strict-note-spacing = ##t
3017 \new Staff { c8[ c \clef alto c \grace { c16 c } c8 c c] c32[ c] }
3026 @subsection Line length
3029 @cindex breaking pages
3032 @funindex line-width
3033 @funindex ragged-right
3034 @funindex ragged-last
3036 @c Although line-width can be set in \layout, it should be set in paper
3037 @c block, to get page layout right.
3038 @c Setting indent in \paper block makes not much sense, but it works.
3040 @c Bit verbose and vague, use examples?
3041 The most basic settings influencing the spacing are @code{indent} and
3042 @code{line-width}. They are set in the @code{\layout} block. They
3043 control the indentation of the first line of music, and the lengths of
3046 If @code{ragged-right} is set to true in the @code{\layout} block, then
3047 systems ends at their natural horizontal length, instead of being spread
3048 horizontally to fill the whole line. This is useful for
3049 short fragments, and for checking how tight the natural spacing is.
3050 The normal default setting is false, but if the score has only one
3051 system the default value is true.
3054 @cindex vertical spacing
3056 The option @code{ragged-last} is similar to @code{ragged-right}, but
3057 only affects the last line of the piece. No restrictions are put on
3058 that line. The result is similar to formatting text paragraphs. In a
3059 paragraph, the last line simply takes its natural horizontal length.
3060 @c Note that for text there are several options for the last line.
3061 @c While Knuth TeX uses natural length, lead typesetters use the same
3062 @c stretch as the previous line. eTeX uses \lastlinefit to
3063 @c interpolate between both these solutions.
3078 @node Proportional notation
3079 @subsection Proportional notation
3081 LilyPond supports proportional notation, a type of horizontal spacing
3082 in which each note consumes an amount of horizontal space exactly
3083 equivalent to its rhythmic duration. This type of proportional spacing
3084 is comparable to horizontal spacing on top of graph paper. Some late
3085 20th- and early 21st-century scores use proportional notation to
3086 clarify complex rhythmic relationships or to facilitate the placement
3087 of timelines or other graphics directly in the score.
3089 LilyPond supports five different settings for proportional notation,
3090 which may be used together or alone:
3093 @item @code{proportionalNotationDuration}
3094 @item @code{uniform-stretching}
3095 @item @code{strict-note-spacing}
3096 @item @code{\remove "Separating_line_group_engraver"}
3097 @item @code{\override PaperColumn.used = ##t}
3100 In the examples that follow, we explore these five different
3101 proportional notation settings and examine how these settings interact.
3103 We start with the following one-measure example, which uses classical
3104 spacing with ragged-right turned on.
3106 @c The initial pitch is not necessary as long as RhythmicStaff is
3107 @c not preceded by other material in the score, but we don't want
3109 @lilypond[quote,verbatim,ragged-right]
3112 \new RhythmicStaff {
3113 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3119 Notice that the half note which begins the measure takes up far less
3120 than half of the horizontal space of the measure. Likewise, the
3121 sixteenth notes and sixteenth-note quintuplets (or twentieth notes)
3122 which end the measure together take up far more than half the
3123 horizontal space of the measure.
3125 In classical engraving, this spacing may be exactly what we want
3126 because we can borrow horizontal space from the half note and conserve
3127 horizontal space across the measure as a whole.
3129 On the other hand, if we want to insert a measured timeline or other
3130 graphic above or below our score, we need proportional notation. We
3131 turn proportional notation on with the proportionalNotationDuration
3134 @lilypond[quote,verbatim,ragged-right]
3137 \new RhythmicStaff {
3138 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3144 proportionalNotationDuration = #(ly:make-moment 1/20)
3150 The half note at the beginning of the measure and the faster notes in
3151 the second half of the measure now occupy equal amounts of horizontal
3152 space. We could place a measured timeline or graphic above or below
3155 The @code{proportionalNotationDuration} setting is a context setting
3156 that lives in @code{Score}. Remember that context settings can appear
3157 in one of three locations within our input file -- in a @code{\with}
3158 block, in a @code{\context} block, or directly in music entry preceded
3159 by the @code{\set} command. As with all context settings, users can
3160 pick which of the three different locations they would like to
3161 set @code{proportionalNotationDuration} in to.
3163 The @code{proportionalNotationDuration} setting takes a single argument,
3164 which is the reference duration against that all music will be spaced.
3165 The LilyPond Scheme function @code{make-moment} takes two arguments
3166 -- a numerator and denominator which together express some fraction of
3167 a whole note. The call @code{(ly:make-moment 1/20)} therefore produces
3168 a reference duration of a twentieth note. Values such as
3169 @code{(ly:make-moment 1/16)}, @code{(ly:make-moment 1/8)}, and
3170 @code{(ly:make-moment 3/97)} are all possible as well.
3172 How do we select the right reference duration to pass to
3173 @code{proportionalNotationDuration}? Usually by a process of trial
3174 and error, beginning with a duration close to the fastest (or smallest)
3175 duration in the piece. Smaller reference durations space music loosely;
3176 larger reference durations space music tightly.
3178 @lilypond[quote,verbatim,ragged-right]
3181 \new RhythmicStaff {
3182 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3188 proportionalNotationDuration = #(ly:make-moment 1/8)
3195 \new RhythmicStaff {
3196 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3202 proportionalNotationDuration = #(ly:make-moment 1/16)
3209 \new RhythmicStaff {
3210 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3216 proportionalNotationDuration = #(ly:make-moment 1/32)
3222 Note that too large a reference duration -- such as the eighth note,
3223 above -- spaces music too tightly and can cause note head collisions.
3224 Also that proportional notation in general takes up more horizontal
3225 space than classical spacing. Proportional spacing provides rhythmic
3226 clarity at the expense of horizontal space.
3228 Next we examine how to optimally space overlapping tuplets.
3230 We start by examining what happens to our original example, with
3231 classical spacing, when we add a second staff with a different type of
3234 @lilypond[quote,verbatim,ragged-right]
3237 \new RhythmicStaff {
3238 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3240 \new RhythmicStaff {
3241 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3247 The spacing is bad because the evenly spaced notes of the bottom staff
3248 do not stretch uniformly. Classical engravings include very few complex
3249 triplets and so classical engraving rules can generate this type of
3250 result. Setting @code{proportionalNotationDuration} fixes this.
3252 @lilypond[quote,verbatim,ragged-right]
3255 \new RhythmicStaff {
3256 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3258 \new RhythmicStaff {
3259 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3265 proportionalNotationDuration = #(ly:make-moment 1/20)
3271 But if we look very carefully we can see that notes of the second half
3272 of the 9-tuplet space ever so slightly more widely than the notes
3273 of the first half of the 9-tuplet. To ensure uniform stretching, we
3274 turn on @code{uniform-stretching}, which is a property of
3275 @code{SpacingSpanner}.
3277 @lilypond[quote,verbatim,ragged-right]
3280 \new RhythmicStaff {
3281 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3283 \new RhythmicStaff {
3284 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3290 proportionalNotationDuration = #(ly:make-moment 1/20)
3291 \override SpacingSpanner.uniform-stretching = ##t
3297 Our two-staff example now spaces exactly, our rhythmic
3298 relationships are visually clear, and we can include a measured
3299 timeline or graphic if we want.
3301 Note that the LilyPond's proportional notation package expects
3302 that all proportional scores set the SpacingSpanner's
3303 'uniform-stretching attribute to ##t. Setting
3304 proportionalNotationDuration without also setting the
3305 SpacingSpanner's 'uniform-stretching attribute to ##t will, for
3306 example, cause Skips to consume an incorrect amount of horizontal
3309 The SpacingSpanner is an abstract grob that lives in the Score
3310 context. As with our settings of proportionalNotationDuration,
3311 overrides to the SpacingSpanner can occur in any of three
3312 different places in our input file – in the Score \with block, in
3313 a Score \context block, or in note entry directly.
3315 There is by default only one @code{SpacingSpanner} per @code{Score}. This
3316 means that, by default, @code{uniform-stretching} is either turned on for the
3317 entire score or turned off for the entire score. We can, however,
3318 override this behavior and turn on different spacing features at
3319 different places in the score. We do this with the command
3320 @code{\newSpacingSection}. See @ref{New spacing area}, for more info.
3322 Next we examine the effects of the @code{Separating_line_group_engraver} and
3323 see why proportional scores frequently remove this engraver. The following
3324 example shows that there is a small amount of @qq{prefatory} space
3325 just before the first note in each system.
3327 @lilypond[quote,verbatim,ragged-right]
3340 The amount of this prefatory space is the same whether after a time
3341 signature, a key signature or a clef. @code{Separating_line_group_engraver}
3342 is responsible for this space. Removing @code{Separating_line_group_engraver}
3343 reduces this space to zero.
3345 @lilypond[quote,verbatim,ragged-right]
3351 \remove "Separating_line_group_engraver"
3359 non-musical elements like time signatures, key signatures, clefs and
3360 accidentals are problematic in proportional notation. None of these
3361 elements has rhythmic duration. But all of these elements consume
3362 horizontal space. Different proportional scores approach these
3363 problems differently.
3365 It may be possible to avoid spacing problems with key signatures
3366 simply by not having any. This is a valid option since most
3367 proportional scores are contemporary music. The same may be true
3368 of time signatures, especially for those scores
3369 that include a measured timeline or other graphic. But these scores
3370 are exceptional and most proportional scores include at least some
3371 time signatures. Clefs and accidentals are even more essential.
3373 So what strategies exist for spacing non-musical elements in a
3374 proportional context? One good option is the @code{strict-note-spacing}
3375 property of @code{SpacingSpanner}. Compare the two scores below:
3377 @lilypond[quote,verbatim,ragged-right]
3379 \set Score.proportionalNotationDuration = #(ly:make-moment 1/16)
3380 c''8 8 8 \clef alto d'2 2
3384 \set Score.proportionalNotationDuration = #(ly:make-moment 1/16)
3385 \override Score.SpacingSpanner.strict-note-spacing = ##t
3386 c''8 8 8 \clef alto d'2 2
3390 Both scores are proportional, but the spacing in the first score
3391 is too loose because of the clef change. The spacing of the second
3392 score remains strict, however, because strict-note-spacing is
3393 turned on. Turning on strict-note-spacing causes the width of
3394 time signatures, key signatures, clefs and accidentals to play no
3395 part in the spacing algorithm.
3397 In addition to the settings given here, there are other settings
3398 that frequently appear in proportional scores. These include:
3401 @item @code{\override SpacingSpanner.strict-grace-spacing = ##t}
3402 @item @code{\set tupletFullLength = ##t}
3403 @item @code{\override Beam.breakable = ##t}
3404 @item @code{\override Glissando.breakable = ##t}
3405 @item @code{\override TextSpanner.breakable = ##t}
3406 @item @code{\remove "Forbid_line_break_engraver" in the Voice context}
3409 These settings space grace notes strictly, extend tuplet brackets to
3410 mark both rhythmic start- and stop-points, and allow spanning elements
3411 to break across systems and pages. See the respective parts of the manual
3412 for these related settings.
3416 @ref{New spacing area}.
3422 @node Fitting music onto fewer pages
3423 @section Fitting music onto fewer pages
3425 Sometimes you can end up with one or two staves on a second
3426 (or third, or fourth@dots{}) page. This is annoying, especially
3427 if you look at previous pages and it looks like there is plenty
3428 of room left on those.
3430 When investigating layout issues, @code{annotate-spacing} is an
3431 invaluable tool. This command prints the values of various layout
3432 spacing variables; for more details see the following section,
3433 @ref{Displaying spacing}.
3436 * Displaying spacing::
3437 * Changing spacing::
3441 @node Displaying spacing
3442 @subsection Displaying spacing
3444 @funindex annotate-spacing
3445 @cindex spacing, display of layout
3447 To graphically display the dimensions of vertical layout variables
3448 that may be altered for page formatting, set
3449 @code{annotate-spacing} in the @code{\paper} block:
3451 @lilypond[verbatim,quote,papersize=a6landscape]
3454 \paper { annotate-spacing = ##t }
3460 All layout dimensions are displayed in staff-spaces, regardless
3461 of the units specified in the @code{\paper} or @code{\layout} block.
3462 In the above example, @code{paper-height} has a value of 59.75
3463 @code{staff-spaces}, and the @code{staff-size} is 20 points (the
3464 default value). Note that:
3466 @multitable {1 staff-space} {staff-size)/4 * (25.4/72.27) mm}
3469 @tab = (25.4/72.27) mm
3472 @tab = (@code{staff-size})/4 pts
3474 @tab = (@code{staff-size})/4 * (25.4/72.27) mm
3479 In this case, one @code{staff-space} is approximately equal to
3480 1.757mm. Thus the @code{paper-height} measurement of 59.75
3481 @code{staff-spaces} is equivalent to 105 millimeters, the height
3482 of @code{a6} paper in landscape orientation. The pairs
3483 (@var{a},@var{b}) are intervals, where @var{a} is the lower
3484 edge and @var{b} the upper edge of the interval.
3488 @ref{Setting the staff size}.
3494 @node Changing spacing
3495 @subsection Changing spacing
3497 The output of @code{annotate-spacing} reveals vertical dimensions
3498 in great detail. For details about modifying margins and other
3499 layout variables, see @ref{Page layout}.
3501 Other than margins, there are a few other options to save space:
3505 Force systems to move as close together as possible (to fit as
3506 many systems as possible onto a page) while being spaced so that
3507 there is no blank space at the bottom of the page.
3511 system-system-spacing = #'((basic-distance . 0.1) (padding . 0))
3512 ragged-last-bottom = ##f
3518 Force the number of systems. This can help in two ways. Just
3519 setting a value, even the same value as the number of systems
3520 being typeset by default, will sometimes cause more systems to
3521 be fitted onto each page, as an estimation step is then bypassed,
3522 giving a more accurate fit to each page. Also, forcing an actual
3523 reduction in the number of systems may save a further page. For
3524 example, if the default layout has 11 systems, the following
3525 assignment will force a layout with 10 systems.
3534 Force the number of pages. For example, the following
3535 assignment will force a layout with 2 pages.
3544 Avoid (or reduce) objects that increase the vertical size of a
3545 system. For example, volta repeats (or alternate repeats) require
3546 extra space. If these repeats are spread over two systems, they
3547 will take up more space than one system with the volta repeats and
3548 another system without. For example, dynamics that @q{stick out} of
3549 a system can be moved closer to the staff:
3551 @lilypond[verbatim,quote,relative=1]
3553 e4 c g-\tweak X-offset #-2.7 \f c
3557 Alter the horizontal spacing via @code{SpacingSpanner}. For more
3558 details, see @ref{Changing horizontal spacing}. The following
3559 example illustrates the default spacing:
3561 @lilypond[verbatim,quote]
3574 The next example modifies @code{common-shortest-duration} from a
3575 value of @code{1/4} to @code{1/2}. The quarter note is the most
3576 common and shortest duration in this example, so by making this
3577 duration longer, a @q{squeezing} effect occurs:
3579 @lilypond[verbatim,quote]
3591 \override SpacingSpanner.common-shortest-duration =
3592 #(ly:make-moment 1/2)
3599 The @code{common-shortest-duration} property cannot be modified
3600 dynamically, so it must always be placed in a @code{\context}
3601 block so that it applies to the whole score.
3608 @ref{Changing horizontal spacing}.