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:
233 @item set-default-paper-size
236 #(set-default-paper-size "quarto")
239 which must always be placed at the toplevel scope, and
245 #(set-paper-size "tabloid")
249 which must always be placed in a @code{\paper} block.
252 If the @code{set-default-paper-size} function is used in the toplevel
253 scope, it must come before any @code{\paper} block.
254 @code{set-default-paper-size} sets the paper size for all pages,
255 whereas @code{set-paper-size} only sets the paper size for the pages
256 that the @code{\paper} block applies to. For example, if the
257 @code{\paper} block is at the top of the file, then it will apply the
258 paper size to all pages. If the @code{\paper} block is inside a
259 @code{\book}, then the paper size will only apply to that book.
261 When the @code{set-paper-size} function is used, it must be
262 placed @emph{before} any other functions used within the same
263 @code{\paper} block. See @ref{Automatic scaling to paper size}.
265 Paper sizes are defined in @file{scm/paper.scm}, and while it is
266 possible to add custom sizes, they will be overwritten on subsequent
267 software updates. The available paper sizes are listed in
268 @ref{Predefined paper sizes}.
270 @c An appendix entry exists for paper sizes but is not auto-generated
272 The following command can be used in the file to add a custom paper size
273 which can then be used with @code{set-default-paper-size} or
274 @code{set-paper-size} as appropriate,
277 #(set! paper-alist (cons '("my size" . (cons (* 15 in) (* 3 in))) paper-alist))
280 #(set-paper-size "my size")
284 The units @code{in} (inches), @code{cm} (centimeters) and @code{mm}
285 (millimeters) can all be used.
287 @cindex paper size, orientation
288 @cindex page, orientation
289 @cindex paper size, landscape
291 If the symbol @code{'landscape} is added to the paper size function,
292 pages will be rotated by 90 degrees, and wider line widths will be set
296 #(set-default-paper-size "a6" 'landscape)
299 Swapping the paper dimensions @emph{without} having the print rotated
300 (like when printing to postcard size, or creating graphics for inclusion
301 rather than a standalone document) can be achieved by appending
302 @samp{landscape} to the name of the paper size itself:
305 #(set-default-paper-size "a6landscape")
308 When the paper size ends with an explicit @samp{landscape} or
309 @samp{portrait}, the presence of a @code{'landscape} symbol @emph{only}
310 affects print orientation, not the paper dimensions used for layout.
314 @ref{Automatic scaling to paper size},
315 @ref{Predefined paper sizes}.
318 @file{scm/paper.scm}.
321 @node Automatic scaling to paper size
322 @unnumberedsubsubsec Automatic scaling to paper size
324 If the paper size is changed with one of the scheme functions
325 (@code{set-default-paper-size} or @code{set-paper-size}), the
326 values of several @code{\paper} variables are automatically scaled
327 to the new size. To bypass the automatic scaling for a particular
328 variable, set the variable after setting the paper size. Note
329 that the automatic scaling is not triggered by setting the
330 @code{paper-height} or @code{paper-width} variables, even though
331 @code{paper-width} can influence other values (this is separate
332 from scaling and is discussed below). The
333 @code{set-default-paper-size} and @code{set-paper-size} functions
334 are described in @ref{Setting the paper size}.
336 The vertical dimensions affected by automatic scaling are
337 @code{top-margin} and @code{bottom-margin} (see
338 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables}).
340 dimensions affected by automatic scaling are @code{left-margin},
341 @code{right-margin}, @code{inner-margin}, @code{outer-margin},
342 @code{binding-offset}, @code{indent}, and @code{short-indent} (see
343 @ref{Horizontal spacing paper variables,,Horizontal spacing @code{@bs{}paper} variables}).
345 The default values for these dimensions are set in
346 @file{ly/paper-defaults-init.ly}, using internal variables named
347 @code{top-margin-default}, @code{bottom-margin-default}, etc.
348 These are the values that result at the default paper size
349 @code{a4}. For reference, with @code{a4} paper the
350 @code{paper-height} is @code{297\mm} and the @code{paper-width} is
355 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables},
356 @ref{Horizontal spacing paper variables,,Horizontal spacing @code{@bs{}paper} variables}.
359 @file{ly/paper-defaults-init.ly},
360 @file{scm/paper.scm}.
363 @node Fixed vertical spacing paper variables
364 @subsection Fixed vertical spacing @code{@bs{}paper} variables
366 @warning{Some @code{@bs{}paper} dimensions are automatically
367 scaled to the paper size, which may lead to unexpected behavior.
368 See @ref{Automatic scaling to paper size}.}
370 Default values (before scaling) are defined in
371 @file{ly/paper-defaults-init.ly}.
375 @funindex paper-height
377 The height of the page, unset by default. Note that the automatic
378 scaling of some vertical dimensions is not affected by this.
383 The margin between the top of the page and the top of the
384 printable area. If the paper size is modified, this dimension's
385 default value is scaled accordingly.
388 @funindex bottom-margin
390 The margin between the bottom of the printable area and the bottom
391 of the page. If the paper size is modified, this dimension's
392 default value is scaled accordingly.
395 @funindex ragged-bottom
397 If set to true, systems will not spread vertically down the page.
398 This does not affect the last page. This should be set to true
399 for pieces that have only two or three systems per page, for
400 example orchestral scores.
402 @item ragged-last-bottom
403 @funindex ragged-last-bottom
405 If set to false, systems will spread vertically down the last
406 page. Pieces that amply fill two pages or more should have this
407 set to false. It also affects the last page of book parts, i.e.
408 parts of a book created with @code{\bookpart} blocks.
414 @ref{Automatic scaling to paper size}.
417 @file{ly/paper-defaults-init.ly}.
423 The titles (from the @code{\header} block) are treated as a
424 system, so @code{ragged-bottom} and @code{ragged-last-bottom} will
425 add space between the titles and the first system of the score.
427 Explicitly defined paper-sizes will override any user-defined top or
428 bottom margin settings.
431 @node Flexible vertical spacing paper variables
432 @subsection Flexible vertical spacing @code{@bs{}paper} variables
434 In most cases, it is preferable for the vertical distances between
435 certain items (such as margins, titles, systems, and separate
436 scores) to be flexible, so that they stretch and compress nicely
437 according to each situation. A number of @code{\paper} variables
438 (listed below) are available to fine-tune the stretching behavior
441 Note that the @code{\paper} variables discussed in this section do
442 not control the spacing of staves within individual systems.
443 Within-system spacing is controlled by grob properties, with
444 settings typically entered inside a @code{\score} or
445 @code{\layout} block, and not inside a @code{\paper} block. See
446 @ref{Flexible vertical spacing within systems}.
449 * Structure of flexible vertical spacing alists::
450 * List of flexible vertical spacing paper variables::
454 @node Structure of flexible vertical spacing alists
455 @unnumberedsubsubsec Structure of flexible vertical spacing alists
457 Each of the flexible vertical spacing @code{\paper} variables is
458 an alist (association list) containing four @emph{keys}:
463 @code{basic-distance} -- the vertical distance, measured in
464 staff-spaces, between the @emph{reference points} of the two
465 items, when no collisions would result, and no stretching or
466 compressing is in effect. The reference point of a (title or
467 top-level) markup is its highest point, and the reference point of
468 a system is the vertical center of the nearest @code{StaffSymbol}
469 -- even if a non-staff line (such as a @code{Lyrics} context) is
470 in the way. Values for @code{basic-distance} that are less than
471 either @code{padding} or @code{minimum-distance} are not
472 meaningful, since the resulting distance will never be less than
473 either @code{padding} or @code{minimum-distance}.
476 @code{minimum-distance} -- the smallest allowable vertical
477 distance, measured in staff-spaces, between the reference points
478 of the two items, when compressing is in effect. Values for
479 @code{minimum-distance} that are less than @code{padding} are not
480 meaningful, since the resulting distance will never be less than
483 @c TODO: explain skylines somewhere and xref to it from here.
486 @code{padding} -- the minimum required amount of unobstructed
487 vertical whitespace between the bounding boxes (or skylines) of
488 the two items, measured in staff-spaces.
491 @code{stretchability} -- a unitless measure of the dimension's
492 relative propensity to stretch. If zero, the distance will not
493 stretch (unless collisions would result). When positive, the
494 significance of a particular dimension's @code{stretchability}
495 value lies only in its relation to the @code{stretchability}
496 values of the other dimensions. For example, if one dimension has
497 twice the @code{stretchability} of another, it will stretch twice
498 as easily. Values should be non-negative and finite. The value
499 @code{+inf.0} triggers a @code{programming_error} and is ignored,
500 but @code{1.0e7} can be used for an almost infinitely stretchable
501 spring. If unset, the default value is set to
502 @code{basic-distance}. Note that the dimension's propensity to
503 @emph{compress} cannot be directly set by the user and is equal to
504 (@code{basic-distance}@tie{}@minus{}@tie{}@code{minimum-distance}).
508 If a page has a ragged bottom, the resulting distance is the
514 @code{basic-distance},
517 @code{minimum-distance}, and
520 @code{padding} plus the smallest distance necessary to eliminate
525 For multi-page scores with a ragged bottom on the last page, the last
526 page uses the same spacing as the preceding page, provided there is
527 enough space for that.
529 Specific methods for modifying alists are discussed in
530 @ref{Modifying alists}. The following example demonstrates the
531 two ways these alists can be modified. The first declaration
532 updates one key-value individually, and the second completely
533 redefines the variable:
537 system-system-spacing #'basic-distance = #8
538 score-system-spacing =
539 #'((basic-distance . 12)
540 (minimum-distance . 6)
542 (stretchability . 12))
547 @node List of flexible vertical spacing paper variables
548 @unnumberedsubsubsec List of flexible vertical spacing @code{@bs{}paper} variables
550 The names of these variables follow the format
551 @code{@var{upper}-@var{lower}-spacing}, where @code{@var{upper}}
552 and @code{@var{lower}} are the items to be spaced. Each distance
553 is measured between the reference points of the two items (see the
554 description of the alist structure above). Note that in these
555 variable names, the term @q{@code{markup}} refers to both
556 @emph{title markups} (@code{bookTitleMarkup} or
557 @code{scoreTitleMarkup}) and @emph{top-level markups} (see
558 @ref{File structure}). All distances are measured in
561 Default settings are defined in @file{ly/paper-defaults-init.ly}.
563 @c TODO: Where do headers/footers fit in? -mp
566 @item markup-system-spacing
567 @funindex markup-system-spacing
569 the distance between a (title or top-level) markup and the system
572 @item score-markup-spacing
573 @funindex score-markup-spacing
575 the distance between the last system of a score and the (title or
576 top-level) markup that follows it.
578 @item score-system-spacing
579 @funindex score-system-spacing
581 the distance between the last system of a score and the first
582 system of the score that follows it, when no (title or top-level)
583 markup exists between them.
585 @item system-system-spacing
586 @funindex system-system-spacing
588 the distance between two systems in the same score.
590 @item markup-markup-spacing
591 @funindex markup-markup-spacing
593 the distance between two (title or top-level) markups.
595 @item last-bottom-spacing
596 @funindex last-bottom-spacing
598 the distance from the last system or top-level markup on a page to
599 the bottom of the printable area (i.e. the top of the bottom
602 @item top-system-spacing
603 @funindex top-system-spacing
605 the distance from the top of the printable area (i.e. the bottom
606 of the top margin) to the first system on a page, when there is no
607 (title or top-level) markup between the two.
609 @item top-markup-spacing
610 @funindex top-markup-spacing
612 the distance from the top of the printable area (i.e. the bottom
613 of the top margin) to the first (title or top-level) markup on a
614 page, when there is no system between the two.
619 @ref{Flexible vertical spacing within systems}.
622 @file{ly/paper-defaults-init.ly}.
628 @node Horizontal spacing paper variables
629 @subsection Horizontal spacing @code{@bs{}paper} variables
631 @warning{Some @code{@bs{}paper} dimensions are automatically
632 scaled to the paper size, which may lead to unexpected behavior.
633 See @ref{Automatic scaling to paper size}.}
636 * paper variables for widths and margins::
637 * paper variables for two-sided mode::
638 * paper variables for shifts and indents::
642 @node paper variables for widths and margins
643 @unnumberedsubsubsec @code{@bs{}paper} variables for widths and margins
645 Default values (before scaling) that are not listed here are
646 defined in @file{ly/paper-defaults-init.ly}.
651 @funindex paper-width
653 The width of the page, unset by default. While @code{paper-width}
654 has no effect on the automatic scaling of some horizontal
655 dimensions, it does influence the @code{line-width} variable. If
656 both @code{paper-width} and @code{line-width} are set, then
657 @code{left-margin} and @code{right-margin} will also be updated.
658 Also see @code{check-consistency}.
663 The horizontal extent of the staff lines in unindented, non-ragged
665 @code{(paper-width@tie{}@minus{}@tie{}left-margin@tie{}@minus{}@tie{}right-margin)}
666 when unset. If @code{line-width} is set, and both
667 @code{left-margin} and @code{right-margin} are unset, then the
668 margins will be updated to center the systems on the page
669 automatically. Also see @code{check-consistency}. This variable
670 can also be set in a @code{\layout} block.
673 @funindex left-margin
675 The margin between the left edge of the page and the start of the
676 staff lines in unindented systems. If the paper size is modified,
677 this dimension's default value is scaled accordingly. If
678 @code{left-margin} is unset, and both @code{line-width} and
679 @code{right-margin} are set, then @code{left-margin} is set to
680 @code{(paper-width@tie{}@minus{}@tie{}line-width@tie{}@minus{}@tie{}right-margin)}.
681 If only @code{line-width} is set, then both margins are set to
682 @code{((paper-width@tie{}@minus{}@tie{}line-width)@tie{}/@tie{}2)},
683 and the systems are consequently centered on the page. Also see
684 @code{check-consistency}.
687 @funindex right-margin
689 The margin between the right edge of the page and the end of the
690 staff lines in non-ragged systems. If the paper size is modified,
691 this dimension's default value is scaled accordingly. If
692 @code{right-margin} is unset, and both @code{line-width} and
693 @code{left-margin} are set, then @code{right-margin} is set to
694 @code{(paper-width@tie{}@minus{}@tie{}line-width@tie{}@minus{}@tie{}left-margin)}.
695 If only @code{line-width} is set, then both margins are set to
696 @code{((paper-width@tie{}@minus{}@tie{}line-width)@tie{}/@tie{}2)},
697 and the systems are consequently centered on the page. Also see
698 @code{check-consistency}.
700 @item check-consistency
701 @funindex check-consistency
703 If set to true, print a warning if @code{left-margin},
704 @code{line-width}, and @code{right-margin} do not exactly add up
705 to @code{paper-width}, and replace each of these (except
706 @code{paper-width}) with its default value (scaled to the paper
707 size if necessary). If set to false, ignore any inconsistencies
708 and allow systems to run off the edge of the page.
711 @funindex ragged-right
713 If set to true, systems will not fill the line width. Instead,
714 systems end at their natural horizontal length. Default:
715 @code{#t} for scores with only one system, and @code{#f} for
716 scores with two or more systems. This variable can also be set in
717 a @code{\layout} block.
720 @funindex ragged-last
722 If set to true, the last system in the score will not fill the
723 line width. Instead the last system ends at its natural
724 horizontal length. Default: @code{#f}. This variable can also be
725 set in a @code{\layout} block.
731 @ref{Automatic scaling to paper size}.
734 @file{ly/paper-defaults-init.ly}.
737 Explicitly defined paper-sizes will override any user-defined left or
738 right margin settings.
741 @node paper variables for two-sided mode
742 @unnumberedsubsubsec @code{@bs{}paper} variables for two-sided mode
744 Default values (before scaling) are defined in
745 @file{ly/paper-defaults-init.ly}.
753 @cindex binding gutter
755 If set to true, use @code{inner-margin}, @code{outer-margin} and
756 @code{binding-offset} to determine margins depending on whether
757 the page number is odd or even. This overrides @code{left-margin}
758 and @code{right-margin}.
761 @funindex inner-margin
763 The margin all pages have at the inner side if they are part of a
764 book. If the paper size is modified, this dimension's default
765 value is scaled accordingly. Works only with @code{two-sided} set
769 @funindex outer-margin
771 The margin all pages have at the outer side if they are part of a
772 book. If the paper size is modified, this dimension's default
773 value is scaled accordingly. Works only with @code{two-sided} set
777 @funindex binding-offset
779 The amount @code{inner-margin} is increased to make sure nothing
780 will be hidden by the binding. If the paper size is modified,
781 this dimension's default value is scaled accordingly. Works only
782 with @code{two-sided} set to true.
788 @ref{Automatic scaling to paper size}.
791 @file{ly/paper-defaults-init.ly}.
794 @node paper variables for shifts and indents
795 @unnumberedsubsubsec @code{@bs{}paper} variables for shifts and indents
797 Default values (before scaling) that are not listed here are
798 defined in @file{ly/paper-defaults-init.ly}.
802 @item horizontal-shift
803 @funindex horizontal-shift
805 @c This default value is buried in the middle of page.scm. -mp
807 The amount that all systems (including titles and system
808 separators) are shifted to the right. Default: @code{0.0\mm}.
813 The level of indentation for the first system in a score. If the
814 paper size is modified, this dimension's default value is scaled
815 accordingly. This variable can also be set in a @code{\layout}
819 @funindex short-indent
821 The level of indentation for all systems in a score besides the
822 first system. If the paper size is modified, this dimension's
823 default value is scaled accordingly. This variable can also be
824 set in a @code{\layout} block.
830 @ref{Automatic scaling to paper size}.
833 @file{ly/paper-defaults-init.ly}.
839 @node Other paper variables
840 @subsection Other @code{@bs{}paper} variables
843 * paper variables for line breaking::
844 * paper variables for page breaking::
845 * paper variables for page numbering::
846 * Miscellaneous paper variables::
850 @node paper variables for line breaking
851 @unnumberedsubsubsec @code{@bs{}paper} variables for line breaking
855 @item max-systems-per-page
856 @funindex max-systems-per-page
858 The maximum number of systems that will be placed on a page. This
859 is currently supported only by the @code{ly:optimal-breaking} algorithm.
862 @item min-systems-per-page
863 @funindex min-systems-per-page
865 The minimum number of systems that will be placed on a page. This
866 may cause pages to be overfilled if it is made too large. This is
867 currently supported only by the @code{ly:optimal-breaking} algorithm.
870 @item systems-per-page
871 @funindex systems-per-page
873 The number of systems that should be placed on each page.
874 This is currently supported only by the @code{ly:optimal-breaking} algorithm.
878 @funindex system-count
880 The number of systems to be used for a score. Default: unset.
881 This variable can also be set in a @code{\layout} block.
890 @node paper variables for page breaking
891 @unnumberedsubsubsec @code{@bs{}paper} variables for page breaking
893 Default values not listed here are defined in
894 @file{ly/paper-defaults-init.ly}
899 @funindex page-breaking
901 The page-breaking algorithm to use. Choices are
902 @code{ly:minimal-breaking}, @code{ly:page-turn-breaking},
903 @code{ly:one-line-breaking} and @code{ly:optimal-breaking}
906 @item page-breaking-system-system-spacing
907 @funindex page-breaking-system-system-spacing
909 Tricks the page breaker into thinking that
910 @code{system-system-spacing} is set to something different than
911 it really is. For example, if
912 @code{page-breaking-system-system-spacing #'padding} is set to something
913 substantially larger than @code{system-system-spacing #'padding}, then the
914 page-breaker will put fewer systems on each page. Default: unset.
919 The number of pages to be used for a score, unset by default.
923 The following variables are effective only when @code{page-breaking}
924 is set to @code{ly:page-turn-breaking}. Page breaks are then chosen
925 to minimize the number of page turns. Since page turns are required
926 on moving from an odd-numbered page to an even-numbered one, a
927 layout in which the last page is odd-numbered will usually be
928 favoured. Places where page turns are preferred can be indicated
929 manually by inserting @code{\allowPageTurn} or automatically by
930 including the @code{Page_turn_engraver} (see @ref{Optimal page turning}).
932 If there are insufficient choices available for making suitable page
933 turns, LilyPond may insert a blank page either within a score, between
934 scores (if there are two or more scores), or by ending a score on an
935 even-numbered page. The values of the following three variables may
936 be increased to make these actions less likely.
938 The values are penalties, i.e. the higher the value the less likely
939 will be the associated action relative to other choices.
943 @item blank-page-penalty
944 @funindex blank-page-penalty
946 The penalty for having a blank page in the middle of a score. If
947 @code{blank-page-penalty} is large and @code{ly:page-turn-breaking} is
948 selected, then LilyPond will be less likely to insert a page in the
949 middle of a score. Instead, it will space out the music further to
950 fill the blank page and the following one. Default: 5.
952 @item blank-last-page-penalty
953 @funindex blank-last-page-penalty
955 The penalty for ending the score on an even-numbered page. If
956 @code{blank-last-page-penalty} is large and
957 @code{ly:page-turn-breaking} is selected, then LilyPond will be less
958 likely to produce a score in which the last page is even-numbered.
959 Instead, it will adjust the spacing in order to use one page more or
960 one page less. Default: 0.
962 @item blank-after-score-page-penalty
963 @funindex blank-after-score-page-penalty
965 The penalty for having a blank page after the end of one score and
966 before the next. By default, this is smaller than
967 @code{blank-page-penalty}, so that blank pages after scores are
968 inserted in preference to blank pages within a score. Default: 2.
976 @ref{Optimal page breaking},
977 @ref{Optimal page turning},
978 @ref{Minimal page breaking},
979 @ref{One-line page breaking}.
982 @file{ly/paper-defaults-init.ly}.
985 @node paper variables for page numbering
986 @unnumberedsubsubsec @code{@bs{}paper} variables for page numbering
988 Default values not listed here are defined in
989 @file{ly/paper-defaults-init.ly}
993 @cindex page numbers, auto-numbering
994 @item auto-first-page-number
995 @funindex auto-first-page-number
997 The page breaking algorithm is affected by the first page number
998 being odd or even. If set to true, the page breaking algorithm
999 will decide whether to start with an odd or even number. This
1000 will result in the first page number remaining as is or being
1001 increased by one. Default: @code{#f}.
1003 @cindex page numbers, specify the first
1004 @item first-page-number
1005 @funindex first-page-number
1007 The value of the page number on the first page.
1009 @item print-first-page-number
1010 @funindex print-first-page-number
1012 If set to true, a page number is printed on the first page.
1014 @cindex page numbers, suppress
1015 @item print-page-number
1016 @funindex print-page-number
1018 If set to false, page numbers are not printed.
1024 @file{ly/paper-defaults-init.ly}.
1027 Odd page numbers are always on the right. If you want the
1028 music to start on page 1 there must be a blank page on the back
1029 of the cover page so that page 1 is on the right hand side.
1032 @node Miscellaneous paper variables
1033 @unnumberedsubsubsec Miscellaneous @code{@bs{}paper} variables
1037 @item page-spacing-weight
1038 @funindex page-spacing-weight
1040 The relative importance of page (vertical) spacing and line
1041 (horizontal) spacing. High values will make page spacing more
1042 important. Default: @code{10}.
1044 @item print-all-headers
1045 @funindex print-all-headers
1047 If set to true, this will print all headers for each @code{\score}
1048 in the output. Normally only the @code{piece} and @code{opus}
1049 header variables are printed. Default: @code{#f}.
1051 @item system-separator-markup
1052 @funindex system-separator-markup
1054 A markup object that is inserted between systems, often used for
1055 orchestral scores. Default: unset. The @code{\slashSeparator}
1056 markup, defined in @file{ly/titling-init.ly}, is provided as a
1057 sensible default, for example:
1059 @lilypond[quote,verbatim,noragged-right,line-width=30\mm]
1060 #(set-default-paper-size "a8")
1064 system-separator-markup = \slashSeparator
1070 \relative c'' { c1 \break c1 \break c1 }
1079 @file{ly/titling-init.ly}.
1085 The default page header puts the page number and the @code{instrument}
1086 field from the @code{\header} block on a line.
1090 @section Score layout
1092 This section discusses score layout options for the @code{\layout}
1096 * The layout block::
1097 * Setting the staff size::
1101 @node The layout block
1102 @subsection The @code{@bs{}layout} block
1106 While the @code{\paper} block contains settings that relate to the
1107 page formatting of the whole document, the @code{\layout} block
1108 contains settings for score-specific layout. To set score layout
1109 options globally, enter them in a toplevel @code{\layout} block.
1110 To set layout options for an individual score, enter them in a
1111 @code{\layout} block inside the @code{\score} block, after the
1112 music. Settings that can appear in a @code{\layout} block
1116 @item the @code{layout-set-staff-size} scheme function,
1117 @item context modifications in @code{\context} blocks, and
1118 @item @code{\paper} variables that affect score layout.
1121 The @code{layout-set-staff-size} function is discussed in the next
1122 section, @ref{Setting the staff size}. Context modifications are
1123 discussed in a separate chapter; see
1124 @ref{Modifying context plug-ins} and
1125 @ref{Changing context default settings}. The @code{\paper}
1126 variables that can appear in a @code{\layout} block are:
1131 @code{line-width}, @code{ragged-right} and @code{ragged-last}
1132 (see @ref{paper variables for widths and margins,,@code{@bs{}paper} variables for widths and margins})
1135 @code{indent} and @code{short-indent}
1136 (see @ref{paper variables for shifts and indents,,@code{@bs{}paper} variables for shifts and indents})
1140 (see @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking})
1144 Here is an example @code{\layout} block:
1151 \override StaffGrouper.staff-staff-spacing.basic-distance = #8
1155 \override TextScript.padding = #1
1156 \override Glissando.thickness = #3
1161 Multiple @code{\layout} blocks can be entered as toplevel expressions.
1162 This can, for example, be useful if different settings are stored in
1163 separate files and included optionally. Internally, when
1164 a @code{\layout} block is evaluated, a copy of the current
1165 @code{\layout} configuration is made, then any changes defined within
1166 the block are applied and the result is saved as the new current
1167 configuration. From the user's perspective the @code{\layout} blocks
1168 are combined, but in conflicting situations (when the same property
1169 is changed in different blocks) the later definitions take precedence.
1171 For example, if this block:
1177 \override TextScript.color = #magenta
1178 \override Glissando.thickness = #1.5
1183 is placed after the one from the preceding example the @code{'padding}
1184 and @code{'color} overrides for @code{TextScript} are combined, but
1185 the later @code{'thickness} override for @code{Glissando} replaces
1186 (or hides) the earlier one.
1188 @code{\layout} blocks may be assigned to variables for reuse later,
1189 but the way this works is slightly but significantly different from
1190 writing them literally.
1192 If a variable is defined like this:
1195 layoutVariable = \layout @{
1198 \override NoteHead.font-size = #4
1203 it will hold the current @code{\layout} configuration with the
1204 @code{NoteHead.font-size} override added, but this combination
1205 is @emph{not} saved as the new current configuration. Be aware
1206 that the @q{current configuration} is read when the variable is
1207 defined and not when it is used, so the content of the variable
1208 is dependent on its position in the source.
1210 The variable can then be used inside another @code{\layout} block,
1218 \override NoteHead.color = #red
1223 A @code{\layout} block containing a variable, as in the example above,
1224 does @emph{not} copy the current configuration but instead uses the
1225 content of @code{\layoutVariable} as the base configuration for the
1226 further additions. This means that any changes defined between the
1227 definition and the use of the variable are lost.
1229 If @code{layoutVariable} is defined (or @code{\include}d) immediately
1230 before being used, its content is just the current configuration plus
1231 the overrides defined within it. So in the example above showing the
1232 use of @code{\layoutVariable} the final @code{\layout} block would
1236 TextScript.padding = #1
1237 TextScript.color = #magenta
1238 Glissando.thickness = #1.5
1239 NoteHead.font-size = #4
1240 NoteHead.color = #red
1243 plus the @code{indent} and the @code{StaffGrouper} overrides.
1245 But if the variable had already been defined before the first
1246 @code{\layout} block the current configuration would now contain
1250 NoteHead.font-size = #4 % (written in the variable definition)
1251 NoteHead.color = #red % (added after the use of the variable)
1254 If carefully planned, @code{\layout} variables can be a valuable tool
1255 to structure the layout design of sources, and also to reset the
1256 @code{\layout} configuration to a known state.
1260 @ref{Changing context default settings}.
1266 @node Setting the staff size
1267 @subsection Setting the staff size
1269 @cindex font size, setting
1270 @cindex staff size, setting
1271 @funindex layout file
1273 The default @strong{staff size} is set to 20 points.
1274 This may be changed in two ways:
1276 To set the staff size globally for all scores in a file (or
1277 in a @code{book} block, to be precise), use @code{set-global-staff-size}.
1280 #(set-global-staff-size 14)
1284 This sets the global default size to 14pt staff height and scales all
1287 To set the staff size individually for each score, use
1292 #(layout-set-staff-size 15)
1297 The Feta font provides musical symbols at eight different
1298 sizes. Each font is tuned for a different staff size: at a smaller size
1299 the font becomes heavier, to match the relatively heavier staff lines.
1300 The recommended font sizes are listed in the following table:
1303 @multitable @columnfractions .15 .2 .22 .2
1306 @tab @b{staff height (pt)}
1307 @tab @b{staff height (mm)}
1349 @c modern rental material?
1354 These fonts are available in any sizes. The context property
1355 @code{fontSize} and the layout property @code{staff-space} (in
1356 @rinternals{StaffSymbol}) can be used to tune the size for individual
1357 staves. The sizes of individual staves are relative to the global size.
1361 @ref{Selecting notation font size}.
1367 @code{layout-set-staff-size} does not change the distance between the
1377 * Optimal page breaking::
1378 * Optimal page turning::
1379 * Minimal page breaking::
1380 * One-line page breaking::
1382 * Using an extra voice for breaks::
1387 @subsection Line breaking
1390 @cindex breaking lines
1392 Line breaks are normally determined automatically. They are chosen
1393 so that lines look neither cramped nor loose, and consecutive
1394 lines have similar density.
1396 To manually force a line break at a bar line, use the
1397 @code{\break} command:
1399 @lilypond[quote,ragged-right,relative=2,verbatim]
1404 By default, a @code{\break} in the middle of a measure is ignored,
1405 and a warning is printed. To force a line break in the middle of
1406 a measure, add an invisible bar line with @w{@samp{\bar ""}}:
1408 @lilypond[quote,ragged-right,relative=2,verbatim]
1415 A @code{\break} occurring at a bar line is also ignored if the
1416 previous measure ends in the middle of a note, such as when a
1417 tuplet begins and ends in different measures. To allow
1418 @code{\break} commands to work in these situations, remove the
1419 @code{Forbid_line_break_engraver} from the @code{Voice} context.
1420 Note that manually forced line breaks have to be added in parallel
1423 @lilypond[quote,ragged-right,verbatim]
1425 \remove "Forbid_line_break_engraver"
1428 { c2. \tuplet 3/2 { c4 c c } c2. | }
1429 { s1 | \break s1 | }
1434 Similarly, line breaks are normally forbidden when beams cross bar
1435 lines. This behavior can be changed by setting
1436 @code{\override Beam.breakable = ##t}:
1438 @lilypond[quote,ragged-right,relative=2,verbatim]
1439 \override Beam.breakable = ##t
1444 The @code{\noBreak} command forbids a line break at the bar line
1445 where it is inserted.
1447 The most basic settings influencing line spacing are @code{indent}
1448 and @code{line-width}. They are set in the @code{\layout} block.
1449 They control the indentation of the first line of music, and the
1450 lengths of the lines.
1452 If @code{ragged-right} is set to true in the @code{\layout} block,
1453 then systems end at their natural horizontal length, instead of
1454 being spread horizontally to fill the whole line. This is useful
1455 for short fragments, and for checking how tight the natural
1458 @c TODO Check and add para on default for ragged-right
1460 The option @code{ragged-last} is similar to @code{ragged-right},
1461 but affects only the last line of the piece.
1473 @cindex regular line breaks
1474 @cindex four bar music.
1476 For line breaks at regular intervals use @code{\break} separated by
1477 skips and repeated with @code{\repeat}. For example, this would
1478 cause the following 28 measures (assuming 4/4 time) to be broken
1479 every 4 measures, and only there:
1484 s1 \noBreak s1 \noBreak
1485 s1 \noBreak s1 \break
1487 @{ @var{the actual music@dots{}} @}
1501 @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking}.
1506 Internals Reference:
1507 @rinternals{LineBreakEvent}.
1511 @subsection Page breaking
1513 The default page breaking may be overridden by inserting
1514 @code{\pageBreak} or @code{\noPageBreak} commands. These commands are
1515 analogous to @code{\break} and @code{\noBreak}. They should be
1516 inserted at a bar line. These commands force and forbid a page-break
1517 from happening. Of course, the @code{\pageBreak} command also forces
1520 The @code{\pageBreak} and @code{\noPageBreak} commands may also be
1521 inserted at top-level, between scores and top-level markups.
1523 There are also analogous settings to @code{ragged-right} and
1524 @code{ragged-last} which have the same effect on vertical spacing:
1525 @code{ragged-bottom} and @code{ragged-last-bottom}. If set to
1526 @code{#t} the systems on all pages or just the last page
1527 respectively will not be justified vertically. See
1528 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables}.
1530 Page breaks are computed by the @code{page-breaking} function. LilyPond
1531 provides three algorithms for computing page breaks,
1532 @code{ly:optimal-breaking}, @code{ly:page-turn-breaking} and
1533 @code{ly:minimal-breaking}. The default is @code{ly:optimal-breaking},
1534 but the value can be changed in the @code{\paper} block:
1538 page-breaking = #ly:page-turn-breaking
1544 When a book has many scores and pages, the page breaking problem may be
1545 difficult to solve, requiring large processing time and memory. To ease
1546 the page breaking process, @code{\bookpart} blocks are used to divide
1547 the book into several parts: the page breaking occurs separately on each
1548 part. Different page breaking functions may also be used in different
1554 subtitle = "Preface"
1557 %% In a part consisting mostly of text,
1558 %% ly:minimal-breaking may be preferred
1559 page-breaking = #ly:minimal-breaking
1561 \markup @{ @dots{} @}
1565 %% In this part, consisting of music, the default optimal
1566 %% page breaking function is used.
1568 subtitle = "First movement"
1570 \score @{ @dots{} @}
1577 @funindex \pageBreak
1579 @funindex \noPageBreak
1580 @code{\noPageBreak}.
1585 @ref{paper variables for page breaking,,@code{@bs{}paper} variables for page breaking}.
1591 @node Optimal page breaking
1592 @subsection Optimal page breaking
1594 @funindex ly:optimal-breaking
1596 The @code{ly:optimal-breaking} function is LilyPond's default method of
1597 determining page breaks. It attempts to find a page breaking that minimizes
1598 cramping and stretching, both horizontally and vertically. Unlike
1599 @code{ly:page-turn-breaking}, it has no concept of page turns.
1606 @node Optimal page turning
1607 @subsection Optimal page turning
1609 @funindex ly:page-turn-breaking
1611 Often it is necessary to find a page breaking configuration so that there is
1612 a rest at the end of every second page. This way, the musician can turn the
1613 page without having to miss notes. The @code{ly:page-turn-breaking} function
1614 attempts to find a page breaking minimizing cramping and stretching, but with
1615 the additional restriction that it is only allowed to introduce page turns
1616 in specified places.
1618 There are two steps to using this page breaking function. First, you
1619 must enable it in the @code{\paper} block, as explained in @ref{Page
1620 breaking}. Then you must tell the function where you would like to allow
1623 There are two ways to achieve the second step. First, you can specify each
1624 potential page turn manually, by inserting @code{\allowPageTurn} into your
1625 input file at the appropriate places.
1627 If this is too tedious, you can add a @code{Page_turn_engraver} to a Staff or
1628 Voice context. The @code{Page_turn_engraver} will scan the context for
1629 sections without notes (note that it does not scan for rests; it scans for
1630 the absence of notes. This is so that single-staff polyphony with rests in one
1631 of the parts does not throw off the @code{Page_turn_engraver}). When it finds
1632 a sufficiently long section without notes, the @code{Page_turn_engraver} will
1633 insert an @code{\allowPageTurn} at the final bar line in that section, unless
1634 there is a @q{special} bar line (such as a double bar), in which case the
1635 @code{\allowPageTurn} will be inserted at the final @q{special} bar line in
1638 @funindex minimumPageTurnLength
1639 The @code{Page_turn_engraver} reads the context property
1640 @code{minimumPageTurnLength} to determine how long a note-free section must
1641 be before a page turn is considered. The default value for
1642 @code{minimumPageTurnLength} is @code{(ly:make-moment 1/1)}. If you want
1643 to disable page turns, you can set it to something very large.
1646 \new Staff \with @{ \consists "Page_turn_engraver" @}
1649 R1 | % a page turn will be allowed here
1651 \set Staff.minimumPageTurnLength = #(ly:make-moment 5/2)
1652 R1 | % a page turn will not be allowed here
1654 R1*2 | % a page turn will be allowed here
1659 @funindex minimumRepeatLengthForPageTurn
1660 The @code{Page_turn_engraver} detects volta repeats. It will only allow a page
1661 turn during the repeat if there is enough time at the beginning and end of the
1662 repeat to turn the page back. The @code{Page_turn_engraver} can also disable
1663 page turns if the repeat is very short. If you set the context property
1664 @code{minimumRepeatLengthForPageTurn} then the @code{Page_turn_engraver} will
1665 only allow turns in repeats whose duration is longer than this value.
1667 The page turning commands, @code{\pageTurn}, @code{\noPageTurn} and
1668 @code{\allowPageTurn}, may also be used at top-level, between scores and
1674 @funindex \noPageTurn
1676 @funindex \allowPageTurn
1677 @code{\allowPageTurn}.
1682 @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking}.
1688 There should only be one @code{Page_turn_engraver} in a score. If there is more
1689 than one, they will interfere with each other.
1692 @node Minimal page breaking
1693 @subsection Minimal page breaking
1695 @funindex ly:minimal-breaking
1697 The @code{ly:minimal-breaking} function performs minimal computations to
1698 calculate the page breaking: it fills a page with as many systems as
1699 possible before moving to the next one. Thus, it may be preferred for
1700 scores with many pages, where the other page breaking functions could be
1701 too slow or memory demanding, or a lot of texts. It is enabled using:
1705 page-breaking = #ly:minimal-breaking
1713 @node One-line page breaking
1714 @subsection One-line page breaking
1716 @funindex ly:one-line-breaking
1718 The @code{ly:one-line-breaking} function is a special-purpose
1719 page breaking algorithm that puts each score on its own page,
1720 and on a single line. This page breaking function does not
1721 typeset titles or margins; only the score will be displayed.
1723 The page width will be adjusted so that
1724 the longest score fits on one line. In particular,
1725 @code{paper-width}, @code{line-width} and @code{indent}
1726 variables in the @code{\paper} block will be ignored, although
1727 @code{left-margin} and @code{right-margin} will
1728 still be honored. The height of the page will
1731 @node Explicit breaks
1732 @subsection Explicit breaks
1734 Lily sometimes rejects explicit @code{\break} and @code{\pageBreak}
1735 commands. There are two commands to override this behavior:
1738 \override NonMusicalPaperColumn.line-break-permission = ##f
1739 \override NonMusicalPaperColumn.page-break-permission = ##f
1742 When @code{line-break-permission} is overridden to false, Lily will insert
1743 line breaks at explicit @code{\break} commands and nowhere else. When
1744 @code{page-break-permission} is overridden to false, Lily will insert
1745 page breaks at explicit @code{\pageBreak} commands and nowhere else.
1747 @lilypond[quote,verbatim]
1754 music = \relative c'' { c8 c c c }
1758 \repeat unfold 2 { \music } \break
1759 \repeat unfold 4 { \music } \break
1760 \repeat unfold 6 { \music } \break
1761 \repeat unfold 8 { \music } \pageBreak
1762 \repeat unfold 8 { \music } \break
1763 \repeat unfold 6 { \music } \break
1764 \repeat unfold 4 { \music } \break
1765 \repeat unfold 2 { \music }
1770 \override NonMusicalPaperColumn.line-break-permission = ##f
1771 \override NonMusicalPaperColumn.page-break-permission = ##f
1782 @node Using an extra voice for breaks
1783 @subsection Using an extra voice for breaks
1785 Line- and page-breaking information usually appears within note entry directly.
1788 music = \relative c'' @{ c4 c c c @}
1792 \repeat unfold 2 @{ \music @} \break
1793 \repeat unfold 3 @{ \music @}
1798 This makes @code{\break} and @code{\pageBreak} commands easy to enter but mixes
1799 music entry with information that specifies how music should lay out
1800 on the page. You can keep music entry and line- and page-breaking
1801 information in two separate places by introducing an extra voice to
1802 contain the breaks. This extra voice
1803 contains only skips together with @code{\break}, @code{pageBreak} and other
1804 breaking layout information.
1806 @lilypond[quote,verbatim]
1807 music = \relative c'' { c4 c c c }
1809 \header { tagline = ##f }
1810 \paper { left-margin = 0\mm }
1821 \repeat unfold 2 { \music }
1822 \repeat unfold 3 { \music }
1823 \repeat unfold 6 { \music }
1824 \repeat unfold 5 { \music }
1831 This pattern becomes especially helpful when overriding
1832 @code{line-break-system-details} and the other useful but long properties of
1833 @code{NonMusicalPaperColumnGrob}, as explained in @ref{Vertical spacing}.
1835 @lilypond[quote,verbatim]
1836 music = \relative c'' { c4 c c c }
1838 \header { tagline = ##f }
1839 \paper { left-margin = 0\mm }
1844 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1848 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1852 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1856 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1861 \repeat unfold 2 { \music }
1862 \repeat unfold 3 { \music }
1863 \repeat unfold 6 { \music }
1864 \repeat unfold 5 { \music }
1873 @ref{Vertical spacing}.
1879 @node Vertical spacing
1880 @section Vertical spacing
1882 @cindex vertical spacing
1883 @cindex spacing, vertical
1885 Vertical spacing is controlled by three things: the amount of
1886 space available (i.e., paper size and margins), the amount of
1887 space between systems, and the amount of space between
1888 staves inside a system.
1891 * Flexible vertical spacing within systems::
1892 * Explicit staff and system positioning::
1893 * Vertical collision avoidance::
1897 @node Flexible vertical spacing within systems
1898 @subsection Flexible vertical spacing within systems
1900 @cindex distance between staves
1901 @cindex staff distance
1902 @cindex space between staves
1903 @cindex space inside systems
1905 Three separate mechanisms control the flexible vertical spacing
1906 within systems, one for each of the following categories:
1911 @emph{ungrouped staves},
1914 @emph{grouped staves} (staves within a staff-group such as
1915 @code{ChoirStaff}, etc.), and
1918 @emph{non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
1923 @c TODO: Clarify this. This almost implies that non-staff lines
1924 @c have NO effect on the spacing between staves. -mp
1926 The height of each system is determined in two steps. First, all
1927 of the staves are spaced according to the amount of space
1928 available. Then, the non-staff lines are distributed between the
1931 Note that the spacing mechanisms discussed in this section only
1932 control the vertical spacing of staves and non-staff lines within
1933 individual systems. The vertical spacing between separate
1934 systems, scores, markups, and margins is controlled by
1935 @code{\paper} variables, which are discussed in
1936 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables}.
1939 * Within-system spacing properties::
1940 * Spacing of ungrouped staves::
1941 * Spacing of grouped staves::
1942 * Spacing of non-staff lines::
1946 @node Within-system spacing properties
1947 @unnumberedsubsubsec Within-system spacing properties
1949 @funindex staff-affinity
1950 @funindex staffgroup-staff-spacing
1951 @funindex staff-staff-spacing
1952 @funindex nonstaff-unrelatedstaff-spacing
1953 @funindex nonstaff-relatedstaff-spacing
1954 @funindex nonstaff-nonstaff-spacing
1955 @funindex default-staff-staff-spacing
1956 @funindex minimum-Y-extent
1957 @funindex extra-offset
1958 @funindex self-alignment-X
1960 @funindex VerticalAxisGroup
1962 The within-system vertical spacing mechanisms are controlled by
1963 two sets of grob properties. The first set is associated with the
1964 @code{VerticalAxisGroup} grob, which is created by all staves and
1965 non-staff lines. The second set is associated with the
1966 @code{StaffGrouper} grob, which can be created by staff-groups,
1967 but only if explicitly called. These properties are described
1968 individually at the end of this section.
1970 The names of these properties (except for @code{staff-affinity})
1971 follow the format @code{@var{item1}-@var{item2}-spacing}, where
1972 @code{@var{item1}} and @code{@var{item2}} are the items to be
1973 spaced. Note that @code{@var{item2}} is not necessarily below
1974 @code{@var{item1}}; for example,
1975 @code{nonstaff-relatedstaff-spacing} will measure upwards from the
1976 non-staff line if @code{staff-affinity} is @code{UP}.
1978 Each distance is measured between the @emph{reference points} of
1979 the two items. The reference point for a staff is the vertical
1980 center of its @code{StaffSymbol} (i.e. the middle line if
1981 @code{line-count} is odd; the middle space if @code{line-count} is
1982 even). The reference points for individual non-staff lines are
1983 given in the following table:
1985 @multitable {Non-staff line} {Reference point}
1986 @headitem Non-staff line @tab Reference point
1987 @item @code{ChordNames} @tab baseline
1988 @item @code{NoteNames} @tab baseline
1989 @item @code{Lyrics} @tab baseline
1990 @item @code{Dynamics} @tab mid-height of @q{m}
1991 @item @code{FiguredBass} @tab highest point
1992 @item @code{FretBoards} @tab top line
1995 In the following image, horizontal lines indicate the positions
1996 of these reference points:
1998 @lilypond[quote,noragged-right,line-width=110\mm]
1999 #(define zero-space '((padding . -inf.0) (basic-distance . 0)))
2001 alignToZero = \with {
2002 \override VerticalAxisGroup.nonstaff-relatedstaff-spacing = #zero-space
2003 \override VerticalAxisGroup.nonstaff-nonstaff-spacing = #zero-space
2005 lowerCaseChords = \with {
2006 chordNameLowercaseMinor = ##t
2008 staffAffinityDown = \with {
2009 \override VerticalAxisGroup.staff-affinity = #DOWN
2012 #(define-music-function
2013 (parser location context)
2015 #{ s1*0^\markup { \typewriter #context } #})
2018 \context { \Dynamics \alignToZero }
2019 \context { \FiguredBass \alignToZero }
2020 \context { \Lyrics \alignToZero }
2021 \context { \NoteNames \alignToZero \staffAffinityDown }
2022 \context { \ChordNames \alignToZero
2025 \context { \FretBoards \alignToZero \staffAffinityDown }
2028 \override DynamicText.self-alignment-X = #-1
2029 \override FretBoard.X-offset = #1.75
2030 \override InstrumentName.minimum-Y-extent = #'(-2 . 2)
2031 \override InstrumentName.extra-offset = #'(0 . -0.5)
2032 \override TextScript.minimum-Y-extent = #'(-2 . 3)
2037 %% These contexts have reference points at the baseline:
2038 %% ChordNames, NoteNames, and Lyrics
2040 \new ChordNames { \chords { g1:m } }
2041 \new NoteNames { s1 | g1 | }
2042 \new RhythmicStaff {
2043 \set RhythmicStaff.instrumentName = #"baseline "
2045 \labelContext "ChordNames " s1 |
2046 \labelContext "NoteNames " s1 |
2047 \labelContext "Lyrics" s1 |
2049 \new Lyrics { \lyrics { \skip 1*2 | ghijk1 | } }
2052 %% The reference point for Dynamics is the midline of 'm' in the font
2054 \new RhythmicStaff {
2055 \set RhythmicStaff.instrumentName = #"mid-height "
2056 \labelContext "Dynamics" s1*3
2058 \new Dynamics { s1\mp s\fp }
2061 %% The reference point for FiguredBass is its highest point
2063 \new RhythmicStaff {
2064 \set RhythmicStaff.instrumentName = #"highest point "
2065 \labelContext "FiguredBass" s1
2067 \new FiguredBass { \figuremode { <6 5>1 } }
2070 %% The reference point for FretBoards is the top line
2071 \include "predefined-guitar-fretboards.ly"
2073 \new FretBoards { \chordmode { e1 } }
2074 \new RhythmicStaff {
2075 \set RhythmicStaff.instrumentName = #"top line "
2076 \labelContext "FretBoards " s1
2081 Each of the vertical spacing grob properties (except
2082 @code{staff-affinity}) uses the same alist structure as the
2083 @code{\paper} spacing variables discussed in
2084 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables}.
2086 for modifying alists are discussed in @ref{Modifying alists}.
2087 Grob properties should be adjusted with an @code{\override} inside
2088 a @code{\score} or @code{\layout} block, and not inside a
2089 @code{\paper} block.
2091 The following example demonstrates the two ways these alists can
2092 be modified. The first declaration updates one key-value
2093 individually, and the second completely re-defines the property:
2097 \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #10
2101 \override VerticalAxisGroup.default-staff-staff-spacing =
2102 #'((basic-distance . 10)
2103 (minimum-distance . 9)
2105 (stretchability . 10))
2109 To change any spacing settings globally, put them in the
2110 @code{\layout} block:
2116 \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #10
2121 Standard settings for the vertical spacing grob properties are
2122 listed in @rinternals{VerticalAxisGroup} and
2123 @rinternals{StaffGrouper}. Default overrides for specific types
2124 of non-staff lines are listed in the relevant context descriptions
2125 in @rinternals{Contexts}.
2128 @subsubheading Properties of the @code{VerticalAxisGroup} grob
2130 @code{VerticalAxisGroup} properties are typically adjusted with an
2131 @code{\override} at the @code{Staff} level (or equivalent).
2134 @item staff-staff-spacing
2136 Used to determine the distance between the current staff and the
2137 staff just below it in the same system, even if one or more
2138 non-staff lines (such as @code{Lyrics}) are placed between the two
2139 staves. Does not apply to the bottom staff of a system.
2141 Initially, the @code{staff-staff-spacing} of a
2142 @code{VerticalAxisGroup} is a Scheme function that applies the
2143 properties of the @code{StaffGrouper} if the staff is part of a
2144 group, or the @code{default-staff-staff-spacing} of the staff
2145 otherwise. This allows staves to be spaced differently when they
2146 are grouped. For uniform spacing regardless of grouping, this
2147 function may be replaced by a flexible-spacing alist, using the
2148 complete-redefinition form of override shown above.
2150 @item default-staff-staff-spacing
2151 A flexible-spacing alist defining the @code{staff-staff-spacing} used for
2152 ungrouped staves, unless @code{staff-staff-spacing} has been explicitly
2153 set with an @code{\override}.
2155 @item staff-affinity
2156 The direction of the staff to use for spacing the current
2157 non-staff line. Choices are @code{UP}, @code{DOWN}, and
2158 @code{CENTER}. If @code{CENTER}, the non-staff line will be
2159 placed equidistant between the two nearest staves on either side,
2160 unless collisions or other spacing constraints prevent this.
2161 Adjacent non-staff lines should have non-increasing
2162 @code{staff-affinity} from top to bottom, e.g. a non-staff line
2163 set to @code{UP} should not immediately follow one that is set to
2164 @code{DOWN}. Non-staff lines at the top of a system should use
2165 @code{DOWN}; those at the bottom should use @code{UP}. Setting
2166 @code{staff-affinity} for a staff causes it to be treated as a
2167 non-staff line. Setting @code{staff-affinity} to @code{#f} causes
2168 a non-staff line to be treated as a staff. Setting
2169 @code{staff-affinity} to @code{UP}, @code{CENTER}, or @code{DOWN}
2170 causes a staff to be spaced as a non-staff line.
2172 @item nonstaff-relatedstaff-spacing
2173 The distance between the current non-staff line and the nearest
2174 staff in the direction of @code{staff-affinity}, if there are no
2175 non-staff lines between the two, and @code{staff-affinity} is
2176 either @code{UP} or @code{DOWN}. If @code{staff-affinity} is
2177 @code{CENTER}, then @code{nonstaff-relatedstaff-spacing} is used
2178 for the nearest staves on @emph{both} sides, even if other
2179 non-staff lines appear between the current one and either of the
2180 staves. This means that the placement of a non-staff line depends
2181 on both the surrounding staves and the surrounding non-staff lines.
2182 Setting the @code{stretchability} of one of these types of spacing to
2183 a small value will make that spacing dominate. Setting the
2184 @code{stretchability} to a large value will make that spacing have
2187 @item nonstaff-nonstaff-spacing
2188 The distance between the current non-staff line and the next
2189 non-staff line in the direction of @code{staff-affinity}, if both
2190 are on the same side of the related staff, and
2191 @code{staff-affinity} is either @code{UP} or @code{DOWN}.
2193 @item nonstaff-unrelatedstaff-spacing
2194 The distance between the current non-staff line and the staff in
2195 the opposite direction from @code{staff-affinity}, if there are no
2196 other non-staff lines between the two, and @code{staff-affinity}
2197 is either @code{UP} or @code{DOWN}. This can be used, for
2198 example, to require a minimum amount of padding between a
2199 @code{Lyrics} line and the staff to which it does not belong.
2203 @subsubheading Properties of the @code{StaffGrouper} grob
2205 @code{StaffGrouper} properties are typically adjusted with an
2206 @code{\override} at the @code{StaffGroup} level (or equivalent).
2209 @item staff-staff-spacing
2210 The distance between consecutive staves within the current
2211 staff-group. The @code{staff-staff-spacing} property of an
2212 individual staff's @code{VerticalAxisGroup} grob can be
2213 overriden with different spacing settings for that staff.
2215 @item staffgroup-staff-spacing
2216 The distance between the last staff of the current staff-group and
2217 the staff just below it in the same system, even if one or more
2218 non-staff lines (such as @code{Lyrics}) exist between the two
2219 staves. Does not apply to the bottom staff of a system. The
2220 @code{staff-staff-spacing} property of an individual staff's
2221 @code{VerticalAxisGroup} grob can be overriden with different
2222 spacing settings for that staff.
2227 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables},
2228 @ref{Modifying alists}.
2231 @file{ly/engraver-init.ly},
2232 @file{scm/define-grobs.scm}.
2234 Internals Reference:
2235 @rinternals{Contexts},
2236 @rinternals{VerticalAxisGroup},
2237 @rinternals{StaffGrouper}.
2240 @node Spacing of ungrouped staves
2241 @unnumberedsubsubsec Spacing of ungrouped staves
2243 @emph{Staves} (such as @code{Staff}, @code{DrumStaff},
2244 @code{TabStaff}, etc.) are contexts that can contain one or more
2245 voice contexts, but cannot contain any other staves.
2247 The following properties affect the spacing of @emph{ungrouped}
2251 @item @code{VerticalAxisGroup} properties:
2253 @item @code{default-staff-staff-spacing}
2254 @item @code{staff-staff-spacing}
2258 These grob properties are described individually above; see
2259 @ref{Within-system spacing properties}.
2261 Additional properties are involved for staves that are part of a
2262 staff-group; see @ref{Spacing of grouped staves}.
2264 The following example shows how the @code{default-staff-staff-spacing}
2265 property can affect the spacing of ungrouped staves.
2266 The same overrides applied to @code{staff-staff-spacing} would
2267 have the same effect, but would also apply in cases where the staves
2268 are combined in a group or groups.
2270 @lilypond[verbatim,quote,staffsize=16]
2274 \override VerticalAxisGroup.default-staff-staff-spacing =
2275 #'((basic-distance . 8)
2276 (minimum-distance . 7)
2282 % The very low note here needs more room than 'basic-distance
2283 % can provide, so the distance between this staff and the next
2284 % is determined by 'padding.
2285 \new Staff { b,2 r | }
2287 % Here, 'basic-distance provides enough room, and there is no
2288 % need to compress the space (towards 'minimum-distance) to make
2289 % room for anything else on the page, so the distance between
2290 % this staff and the next is determined by 'basic-distance.
2291 \new Staff { \clef bass g2 r | }
2293 % By setting 'padding to a negative value, staves can be made to
2294 % collide. The lowest acceptable value for 'basic-distance is 0.
2296 \override VerticalAxisGroup.default-staff-staff-spacing =
2297 #'((basic-distance . 3.5)
2299 } { \clef bass g2 r | }
2300 \new Staff { \clef bass g2 r | }
2306 @file{scm/define-grobs.scm}.
2311 Internals Reference:
2312 @rinternals{VerticalAxisGroup}.
2315 @node Spacing of grouped staves
2316 @unnumberedsubsubsec Spacing of grouped staves
2318 In orchestral and other large scores, it is common to place staves
2319 in groups. The space between groups is typically larger than the
2320 space between staves of the same group.
2322 @emph{Staff-groups} (such as @code{StaffGroup}, @code{ChoirStaff},
2323 etc.) are contexts that can contain one or more staves
2326 The following properties affect the spacing of staves inside
2330 @item @code{VerticalAxisGroup} properties:
2332 @item @code{staff-staff-spacing}
2334 @item @code{StaffGrouper} properties:
2336 @item @code{staff-staff-spacing}
2337 @item @code{staffgroup-staff-spacing}
2341 These grob properties are described individually above; see
2342 @ref{Within-system spacing properties}.
2344 The following example shows how properties of the
2345 @code{StaffGrouper} grob can affect the spacing of grouped staves:
2347 @lilypond[verbatim,quote,staffsize=16]
2351 \override StaffGrouper.staff-staff-spacing.padding = #0
2352 \override StaffGrouper.staff-staff-spacing.basic-distance = #1
2357 \new PianoStaff \with {
2358 \override StaffGrouper.staffgroup-staff-spacing.basic-distance = #20
2373 @file{scm/define-grobs.scm}.
2378 Internals Reference:
2379 @rinternals{VerticalAxisGroup},
2380 @rinternals{StaffGrouper}.
2383 @node Spacing of non-staff lines
2384 @unnumberedsubsubsec Spacing of non-staff lines
2386 @emph{Non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
2387 etc.) are contexts whose layout objects are engraved like staves
2388 (i.e. in horizontal lines within systems). Specifically,
2389 non-staff lines are non-staff contexts that create the
2390 @code{VerticalAxisGroup} layout object.
2392 The following properties affect the spacing of non-staff lines:
2395 @item @code{VerticalAxisGroup} properties:
2397 @item @code{staff-affinity}
2398 @item @code{nonstaff-relatedstaff-spacing}
2399 @item @code{nonstaff-nonstaff-spacing}
2400 @item @code{nonstaff-unrelatedstaff-spacing}
2404 These grob properties are described individually above; see
2405 @ref{Within-system spacing properties}.
2407 The following example shows how the
2408 @code{nonstaff-nonstaff-spacing} property can affect the spacing
2409 of consecutive non-staff lines. Here, by setting the
2410 @code{stretchability} key to a very high value, the lyrics are
2411 able to stretch much more than usual:
2413 @lilypond[verbatim,quote,staffsize=16]
2417 \override VerticalAxisGroup.nonstaff-nonstaff-spacing.stretchability = #1000
2424 \override VerticalAxisGroup.staff-staff-spacing = #'((basic-distance . 30))
2427 \override VerticalAxisGroup.staff-affinity = #UP
2430 \override VerticalAxisGroup.staff-affinity = #CENTER
2431 } \lyricmode { center }
2433 \override VerticalAxisGroup.staff-affinity = #DOWN
2434 } \lyricmode { down }
2441 @file{ly/engraver-init.ly},
2442 @file{scm/define-grobs.scm}.
2447 @c @lsr{spacing,page-spacing.ly},
2448 @c @lsr{spacing,alignment-vertical-spacing.ly}.
2450 Internals Reference:
2451 @rinternals{Contexts},
2452 @rinternals{VerticalAxisGroup}.
2455 @node Explicit staff and system positioning
2456 @subsection Explicit staff and system positioning
2458 One way to understand the flexible vertical spacing mechanisms
2459 explained above is as a collection of settings that control the
2460 amount of vertical padding between staves and systems.
2462 It is possible to approach vertical spacing in a different way
2463 using @code{NonMusicalPaperColumn.line-break-system-details}.
2464 While the flexible vertical spacing mechanisms specify vertical
2465 padding, @code{NonMusicalPaperColumn.line-break-system-details}
2466 can specify exact vertical positions on the page.
2468 @code{NonMusicalPaperColumn.line-break-system-details} accepts
2469 an associative list of three different settings:
2472 @item @code{X-offset}
2473 @item @code{Y-offset}
2474 @item @code{alignment-distances}
2477 Grob overrides, including the overrides for @code{NonMusicalPaperColumn}
2478 below, can occur in any of three different places in an input file:
2481 @item in the middle of note entry directly
2482 @item in a @code{\context} block
2483 @item in the @code{\with} block
2486 When we override @code{NonMusicalPaperColumn}, we use the usual
2487 @code{\override} command in @code{\context} blocks and in the
2488 @code{\with} block. On the other hand, when we override
2489 @code{NonMusicalPaperColumn} in the middle of note entry,
2490 use the special @code{\overrideProperty} command. Here are some
2491 example @code{NonMusicalPaperColumn} overrides with the special
2492 @code{\overrideProperty} command:
2495 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2498 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2501 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2505 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2506 #'((alignment-distances . (15)))
2508 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2511 (alignment-distances . (15)))
2514 To understand how each of these different settings work, we begin
2515 by looking at an example that includes no overrides at all.
2517 @c \book { } is required in these examples to ensure the spacing
2518 @c overrides can be seen between systems. -np
2520 @lilypond[verbatim,quote,staffsize=16]
2521 \header { tagline = ##f }
2522 \paper { left-margin = 0\mm }
2532 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2535 \repeat unfold 15 { d'4 d' d' d' }
2542 This score isolates line- and page-breaking information in a dedicated
2543 voice. This technique of creating a breaks voice will help keep layout
2544 separate from music entry as our example becomes more complicated.
2545 See @ref{Using an extra voice for breaks}.
2547 Explicit @code{\breaks} evenly divide the music into six measures per
2548 line. Vertical spacing results from LilyPond's defaults. To set
2549 the vertical startpoint of each system explicitly, we can set
2550 the @code{Y-offset} pair in the @code{line-break-system-details}
2551 attribute of the @code{NonMusicalPaperColumn} grob:
2553 @lilypond[verbatim,quote,staffsize=16]
2554 \header { tagline = ##f }
2555 \paper { left-margin = 0\mm }
2561 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2564 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2567 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2571 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2574 \repeat unfold 15 { d'4 d' d' d' }
2581 Note that @code{line-break-system-details} takes an associative list of
2582 potentially many values, but that we set only one value here. Note,
2583 too, that the @code{Y-offset} property here determines the exact vertical
2584 position on the page at which each new system will render.
2586 Now that we have set the vertical startpoint of each system
2587 explicitly, we can also set the vertical distances between staves
2588 within each system manually. We do this using the @code{alignment-distances}
2589 subproperty of @code{line-break-system-details}.
2591 @lilypond[verbatim,quote,staffsize=16]
2592 \header { tagline = ##f }
2593 \paper { left-margin = 0\mm }
2599 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2601 (alignment-distances . (10)))
2603 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2605 (alignment-distances . (15)))
2607 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2609 (alignment-distances . (20)))
2612 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2615 \repeat unfold 15 { d'4 d' d' d' }
2622 Note that here we assign two different values to the
2623 @code{line-break-system-details} attribute of the
2624 @code{NonMusicalPaperColumn} grob. Though the
2625 @code{line-break-system-details} attribute alist accepts many
2626 additional spacing parameters (including, for example, a corresponding
2627 @code{X-offset} pair), we need only set the @code{Y-offset} and
2628 @code{alignment-distances} pairs to control the vertical startpoint of
2629 every system and every staff. Finally, note that @code{alignment-distances}
2630 specifies the vertical positioning of staves but not of staff groups.
2632 @lilypond[verbatim,quote,staffsize=16]
2633 \header { tagline = ##f }
2634 \paper { left-margin = 0\mm }
2640 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2642 (alignment-distances . (30 10)))
2644 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2646 (alignment-distances . (10 10)))
2648 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2650 (alignment-distances . (10 30)))
2653 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2656 \new Staff { \repeat unfold 15 { d'4 d' d' d' } }
2657 \new Staff { \repeat unfold 15 { e'4 e' e' e' } }
2664 Some points to consider:
2667 @item When using @code{alignment-distances}, lyrics and other non-staff lines
2668 do not count as a staff.
2670 @item The units of the numbers passed to @code{X-offset},
2671 @code{Y-offset} and @code{alignment-distances} are interpreted as multiples
2672 of the distance between adjacent staff lines. Positive values move staves
2673 and lyrics up, negative values move staves and lyrics down.
2675 @item Because the @code{NonMusicalPaperColumn.line-break-system-details}
2676 settings given here allow the positioning of staves and systems anywhere
2677 on the page, it is possible to violate paper or margin boundaries or even
2678 to print staves or systems on top of one another. Reasonable values
2679 passed to these different settings will avoid this.
2687 @node Vertical collision avoidance
2688 @subsection Vertical collision avoidance
2690 @funindex outside-staff-priority
2691 @funindex outside-staff-padding
2692 @funindex outside-staff-horizontal-padding
2694 Intuitively, there are some objects in musical notation that belong
2695 to the staff and there are other objects that should be placed outside
2696 the staff. Objects belonging outside the staff include things such as
2697 rehearsal marks, text and dynamic markings (from now on, these will
2698 be called outside-staff objects). LilyPond's rule for the
2699 vertical placement of outside-staff objects is to place them as close
2700 to the staff as possible but not so close that they collide with
2703 LilyPond uses the @code{outside-staff-priority} property to determine
2704 whether a grob is an outside-staff object: if @code{outside-staff-priority}
2705 is a number, the grob is an outside-staff object. In addition,
2706 @code{outside-staff-priority} tells LilyPond in which order the objects
2709 First, LilyPond places all the objects that do not belong outside
2710 the staff. Then it sorts the outside-staff objects according to their
2711 @code{outside-staff-priority} (in increasing order). One by one, LilyPond
2712 takes the outside-staff objects and places them so that they do
2713 not collide with any objects that have already been placed. That
2714 is, if two outside-staff grobs are competing for the same space, the one
2715 with the lower @code{outside-staff-priority} will be placed closer to
2718 @lilypond[quote,ragged-right,relative=2,verbatim]
2721 \once \override TextScript.outside-staff-priority = #1
2722 c4_"Text"\pp % this time the text will be closer to the staff
2724 % by setting outside-staff-priority to a non-number,
2725 % we disable the automatic collision avoidance
2726 \once \override TextScript.outside-staff-priority = ##f
2727 \once \override DynamicLineSpanner.outside-staff-priority = ##f
2728 c4_"Text"\pp % now they will collide
2731 The vertical padding around outside-staff objects
2732 can be controlled with @code{outside-staff-padding}.
2734 @lilypond[quote,ragged-right,relative=2,verbatim,staffsize=18]
2735 \once \override TextScript.outside-staff-padding = #0
2736 a4-"outside-staff-padding = #0"
2737 \once \override TextScript.outside-staff-padding = #3
2738 d-"outside-staff-padding = #3"
2739 c-"default outside-staff-padding"
2740 b-"default outside-staff-padding"
2745 By default, outside-staff objects are placed so they avoid
2746 a horizontal collision with previously-positioned grobs. This
2747 can lead to situations in which objects are placed close to each
2749 As shown in the example below, setting @code{outside-staff-horizontal-padding}
2750 increases the horizontal spacing required, and in this case moves the text up
2751 to prevent it from getting too close to the ledger lines.
2753 @lilypond[quote,ragged-right,relative=2,verbatim]
2756 \once \override TextScript.outside-staff-horizontal-padding = #1
2765 @node Horizontal spacing
2766 @section Horizontal spacing
2768 @cindex horizontal spacing
2769 @cindex spacing, horizontal
2772 * Horizontal spacing overview::
2773 * New spacing area::
2774 * Changing horizontal spacing::
2776 * Proportional notation::
2780 @node Horizontal spacing overview
2781 @subsection Horizontal spacing overview
2783 The spacing engine translates differences in durations into stretchable
2784 distances (@q{springs}) of differing lengths. Longer durations get
2785 more space, shorter durations get less. The shortest durations get a
2786 fixed amount of space (which is controlled by
2787 @code{shortest-duration-space} in the @rinternals{SpacingSpanner}
2788 object). The longer the duration, the more space it gets: doubling a
2789 duration adds a fixed amount (this amount is controlled by
2790 @code{spacing-increment}) of space to the note.
2792 For example, the following piece contains lots of half, quarter, and
2793 8th notes; the eighth note is followed by 1 note head width (NHW).
2794 The quarter note is followed by 2 NHW, the half by 3 NHW, etc.
2796 @lilypond[quote,verbatim,relative=1]
2802 Normally, @code{spacing-increment} is set to 1.2 staff space, which is
2803 approximately the width of a note head, and
2804 @code{shortest-duration-space} is set to 2.0, meaning that the
2805 shortest note gets 2.4 staff space (2.0 times the
2806 @code{spacing-increment}) of horizontal space. This space is counted
2807 from the left edge of the symbol, so the shortest notes are generally
2808 followed by one NHW of space.
2810 If one would follow the above procedure exactly, then adding a single
2811 32nd note to a score that uses 8th and 16th notes, would widen up the
2812 entire score a lot. The shortest note is no longer a 16th, but a 32nd,
2813 thus adding 1 NHW to every note. To prevent this, the shortest
2814 duration for spacing is not the shortest note in the score, but rather
2815 the one which occurs most frequently.
2818 The most common shortest duration is determined as follows: in every
2819 measure, the shortest duration is determined. The most common shortest
2820 duration is taken as the basis for the spacing, with the stipulation
2821 that this shortest duration should always be equal to or shorter than
2822 an 8th note. The shortest duration is printed when you run
2823 @code{lilypond} with the @option{--verbose} option.
2825 These durations may also be customized. If you set the
2826 @code{common-shortest-duration} in @rinternals{SpacingSpanner}, then
2827 this sets the base duration for spacing. The maximum duration for this
2828 base (normally an 8th), is set through @code{base-shortest-duration}.
2830 @funindex common-shortest-duration
2831 @funindex base-shortest-duration
2832 @funindex stem-spacing-correction
2835 Notes that are even shorter than the common shortest note are
2836 followed by a space that is proportional to their duration relative to
2837 the common shortest note. So if we were to add only a few 16th notes
2838 to the example above, they would be followed by half a NHW:
2840 @lilypond[quote,verbatim,relative=2]
2841 c2 c4. c8 | c4. c16[ c] c4. c8 | c8 c c4 c c
2845 In the @emph{Essay on automated music engraving}, it was explained
2846 that stem directions influence spacing (see
2847 @ressay{Optical spacing}). This is controlled with the
2848 @code{stem-spacing-correction} property in the
2849 @rinternals{NoteSpacing}, object. These are generated for every
2850 @rinternals{Voice} context. The @code{StaffSpacing} object
2851 (generated in @rinternals{Staff} context) contains the same
2852 property for controlling the stem/bar line spacing. The following
2853 example shows these corrections, once with default settings, and
2854 once with exaggerated corrections:
2856 @lilypond[quote,ragged-right]
2860 \override Staff.NoteSpacing.stem-spacing-correction = #1.5
2861 \override Staff.StaffSpacing.stem-spacing-correction = #1.5
2867 Proportional notation is supported; see @ref{Proportional notation}.
2870 Essay on automated music engraving:
2871 @ressay{Optical spacing}.
2876 Internals Reference:
2877 @rinternals{SpacingSpanner},
2878 @rinternals{NoteSpacing},
2879 @rinternals{StaffSpacing},
2880 @rinternals{NonMusicalPaperColumn}.
2883 There is no convenient mechanism to manually override spacing. The
2884 following work-around may be used to insert extra space into a score,
2885 adjusting the padding value as necessary.
2888 \override Score.NonMusicalPaperColumn.padding = #10
2891 No work-around exists for decreasing the amount of space.
2894 @node New spacing area
2895 @subsection New spacing area
2897 @funindex \newSpacingSection
2898 @cindex new spacing area
2899 @cindex spacing area, new
2900 @cindex notes, spacing horizontally
2902 New sections with different spacing parameters can be started with
2903 @code{newSpacingSection}. This is useful when there are
2904 sections with a different notions of long and short notes.
2906 In the following example, the time signature change introduces a new
2907 section, and hence the 16ths notes are automatically spaced slightly
2910 @lilypond[relative=1,verbatim,quote]
2913 c8 c c4 c16[ c c8] c4
2919 The @code{\newSpacingSection} command creates a new
2920 @code{SpacingSpanner} object at that musical moment.
2921 If the automatic spacing adjustments do not give the required spacing,
2922 manual @code{\override}s may be applied to its properties. These must
2923 be applied at the same musical moment as the @code{\newSpacingSection}
2924 command itself. They will then affect the spacing of all the following
2925 music until the properties are changed in a new spacing section, for
2928 @lilypond[relative=1,verbatim,quote]
2932 \override Score.SpacingSpanner.spacing-increment = #2
2935 \revert Score.SpacingSpanner.spacing-increment
2944 Internals Reference:
2945 @rinternals{SpacingSpanner}.
2948 @node Changing horizontal spacing
2949 @subsection Changing horizontal spacing
2951 Horizontal spacing may be altered with the
2952 @code{base-shortest-duration} property. Here
2953 we compare the same music; once without altering
2954 the property, and then altered. Larger values
2955 of @code{ly:make-moment} will produce smaller
2956 music. Note that @code{ly:make-moment} constructs
2957 a duration, so @code{1 4} is a longer duration
2960 @lilypond[verbatim,line-width=12\cm]
2963 g4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2964 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2965 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2966 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2971 @lilypond[verbatim,line-width=12\cm]
2974 g4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2975 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2976 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2977 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2982 \override SpacingSpanner.base-shortest-duration = #(ly:make-moment 1/16)
2991 By default, spacing in tuplets depends on various non-duration
2992 factors (such as accidentals, clef changes, etc). To disregard
2993 such symbols and force uniform equal-duration spacing, use
2994 @code{Score.SpacingSpanner.uniform-stretching}. This
2995 property can only be changed at the beginning of a score,
2997 @lilypond[quote,ragged-right,verbatim]
3001 \tuplet 5/4 { c8 c c c c } c8 c c c
3004 c8 c c c \tuplet 5/4 { c8 c c c c }
3010 \override SpacingSpanner.uniform-stretching = ##t
3016 When @code{strict-note-spacing} is set, notes are spaced without
3017 regard for clefs, bar lines, and grace notes,
3019 @lilypond[quote,ragged-right,relative=2,verbatim]
3020 \override Score.SpacingSpanner.strict-note-spacing = ##t
3021 \new Staff { c8[ c \clef alto c \grace { c16 c } c8 c c] c32[ c] }
3030 @subsection Line length
3033 @cindex breaking pages
3036 @funindex line-width
3037 @funindex ragged-right
3038 @funindex ragged-last
3040 @c Although line-width can be set in \layout, it should be set in paper
3041 @c block, to get page layout right.
3042 @c Setting indent in \paper block makes not much sense, but it works.
3044 @c Bit verbose and vague, use examples?
3045 The most basic settings influencing the spacing are @code{indent} and
3046 @code{line-width}. They are set in the @code{\layout} block. They
3047 control the indentation of the first line of music, and the lengths of
3050 If @code{ragged-right} is set to true in the @code{\layout} block, then
3051 systems ends at their natural horizontal length, instead of being spread
3052 horizontally to fill the whole line. This is useful for
3053 short fragments, and for checking how tight the natural spacing is.
3054 The normal default setting is false, but if the score has only one
3055 system the default value is true.
3058 @cindex vertical spacing
3060 The option @code{ragged-last} is similar to @code{ragged-right}, but
3061 only affects the last line of the piece. No restrictions are put on
3062 that line. The result is similar to formatting text paragraphs. In a
3063 paragraph, the last line simply takes its natural horizontal length.
3064 @c Note that for text there are several options for the last line.
3065 @c While Knuth TeX uses natural length, lead typesetters use the same
3066 @c stretch as the previous line. eTeX uses \lastlinefit to
3067 @c interpolate between both these solutions.
3082 @node Proportional notation
3083 @subsection Proportional notation
3085 LilyPond supports proportional notation, a type of horizontal spacing
3086 in which each note consumes an amount of horizontal space exactly
3087 equivalent to its rhythmic duration. This type of proportional spacing
3088 is comparable to horizontal spacing on top of graph paper. Some late
3089 20th- and early 21st-century scores use proportional notation to
3090 clarify complex rhythmic relationships or to facilitate the placement
3091 of timelines or other graphics directly in the score.
3093 LilyPond supports five different settings for proportional notation,
3094 which may be used together or alone:
3097 @item @code{proportionalNotationDuration}
3098 @item @code{uniform-stretching}
3099 @item @code{strict-note-spacing}
3100 @item @code{\remove "Separating_line_group_engraver"}
3101 @item @code{\override PaperColumn.used = ##t}
3104 In the examples that follow, we explore these five different
3105 proportional notation settings and examine how these settings interact.
3107 We start with the following one-measure example, which uses classical
3108 spacing with ragged-right turned on.
3110 @c The initial pitch is not necessary as long as RhythmicStaff is
3111 @c not preceded by other material in the score, but we don't want
3113 @lilypond[quote,verbatim,ragged-right]
3116 \new RhythmicStaff {
3117 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3123 Notice that the half note which begins the measure takes up far less
3124 than half of the horizontal space of the measure. Likewise, the
3125 sixteenth notes and sixteenth-note quintuplets (or twentieth notes)
3126 which end the measure together take up far more than half the
3127 horizontal space of the measure.
3129 In classical engraving, this spacing may be exactly what we want
3130 because we can borrow horizontal space from the half note and conserve
3131 horizontal space across the measure as a whole.
3133 On the other hand, if we want to insert a measured timeline or other
3134 graphic above or below our score, we need proportional notation. We
3135 turn proportional notation on with the proportionalNotationDuration
3138 @lilypond[quote,verbatim,ragged-right]
3141 \new RhythmicStaff {
3142 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3148 proportionalNotationDuration = #(ly:make-moment 1/20)
3154 The half note at the beginning of the measure and the faster notes in
3155 the second half of the measure now occupy equal amounts of horizontal
3156 space. We could place a measured timeline or graphic above or below
3159 The @code{proportionalNotationDuration} setting is a context setting
3160 that lives in @code{Score}. Remember that context settings can appear
3161 in one of three locations within our input file -- in a @code{\with}
3162 block, in a @code{\context} block, or directly in music entry preceded
3163 by the @code{\set} command. As with all context settings, users can
3164 pick which of the three different locations they would like to
3165 set @code{proportionalNotationDuration} in to.
3167 The @code{proportionalNotationDuration} setting takes a single argument,
3168 which is the reference duration against that all music will be spaced.
3169 The LilyPond Scheme function @code{make-moment} takes two arguments
3170 -- a numerator and denominator which together express some fraction of
3171 a whole note. The call @code{(ly:make-moment 1/20)} therefore produces
3172 a reference duration of a twentieth note. Values such as
3173 @code{(ly:make-moment 1/16)}, @code{(ly:make-moment 1/8)}, and
3174 @code{(ly:make-moment 3/97)} are all possible as well.
3176 How do we select the right reference duration to pass to
3177 @code{proportionalNotationDuration}? Usually by a process of trial
3178 and error, beginning with a duration close to the fastest (or smallest)
3179 duration in the piece. Smaller reference durations space music loosely;
3180 larger reference durations space music tightly.
3182 @lilypond[quote,verbatim,ragged-right]
3185 \new RhythmicStaff {
3186 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3192 proportionalNotationDuration = #(ly:make-moment 1/8)
3199 \new RhythmicStaff {
3200 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3206 proportionalNotationDuration = #(ly:make-moment 1/16)
3213 \new RhythmicStaff {
3214 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3220 proportionalNotationDuration = #(ly:make-moment 1/32)
3226 Note that too large a reference duration -- such as the eighth note,
3227 above -- spaces music too tightly and can cause note head collisions.
3228 Also that proportional notation in general takes up more horizontal
3229 space than classical spacing. Proportional spacing provides rhythmic
3230 clarity at the expense of horizontal space.
3232 Next we examine how to optimally space overlapping tuplets.
3234 We start by examining what happens to our original example, with
3235 classical spacing, when we add a second staff with a different type of
3238 @lilypond[quote,verbatim,ragged-right]
3241 \new RhythmicStaff {
3242 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3244 \new RhythmicStaff {
3245 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3251 The spacing is bad because the evenly spaced notes of the bottom staff
3252 do not stretch uniformly. Classical engravings include very few complex
3253 triplets and so classical engraving rules can generate this type of
3254 result. Setting @code{proportionalNotationDuration} fixes this.
3256 @lilypond[quote,verbatim,ragged-right]
3259 \new RhythmicStaff {
3260 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3262 \new RhythmicStaff {
3263 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3269 proportionalNotationDuration = #(ly:make-moment 1/20)
3275 But if we look very carefully we can see that notes of the second half
3276 of the 9-tuplet space ever so slightly more widely than the notes
3277 of the first half of the 9-tuplet. To ensure uniform stretching, we
3278 turn on @code{uniform-stretching}, which is a property of
3279 @code{SpacingSpanner}.
3281 @lilypond[quote,verbatim,ragged-right]
3284 \new RhythmicStaff {
3285 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3287 \new RhythmicStaff {
3288 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3294 proportionalNotationDuration = #(ly:make-moment 1/20)
3295 \override SpacingSpanner.uniform-stretching = ##t
3301 Our two-staff example now spaces exactly, our rhythmic
3302 relationships are visually clear, and we can include a measured
3303 timeline or graphic if we want.
3305 Note that the LilyPond's proportional notation package expects
3306 that all proportional scores set the SpacingSpanner's
3307 'uniform-stretching attribute to ##t. Setting
3308 proportionalNotationDuration without also setting the
3309 SpacingSpanner's 'uniform-stretching attribute to ##t will, for
3310 example, cause Skips to consume an incorrect amount of horizontal
3313 The SpacingSpanner is an abstract grob that lives in the Score
3314 context. As with our settings of proportionalNotationDuration,
3315 overrides to the SpacingSpanner can occur in any of three
3316 different places in our input file – in the Score \with block, in
3317 a Score \context block, or in note entry directly.
3319 There is by default only one @code{SpacingSpanner} per @code{Score}. This
3320 means that, by default, @code{uniform-stretching} is either turned on for the
3321 entire score or turned off for the entire score. We can, however,
3322 override this behavior and turn on different spacing features at
3323 different places in the score. We do this with the command
3324 @code{\newSpacingSection}. See @ref{New spacing area}, for more info.
3326 Next we examine the effects of the @code{Separating_line_group_engraver} and
3327 see why proportional scores frequently remove this engraver. The following
3328 example shows that there is a small amount of @qq{prefatory} space
3329 just before the first note in each system.
3331 @lilypond[quote,verbatim,ragged-right]
3344 The amount of this prefatory space is the same whether after a time
3345 signature, a key signature or a clef. @code{Separating_line_group_engraver}
3346 is responsible for this space. Removing @code{Separating_line_group_engraver}
3347 reduces this space to zero.
3349 @lilypond[quote,verbatim,ragged-right]
3355 \remove "Separating_line_group_engraver"
3363 non-musical elements like time signatures, key signatures, clefs and
3364 accidentals are problematic in proportional notation. None of these
3365 elements has rhythmic duration. But all of these elements consume
3366 horizontal space. Different proportional scores approach these
3367 problems differently.
3369 It may be possible to avoid spacing problems with key signatures
3370 simply by not having any. This is a valid option since most
3371 proportional scores are contemporary music. The same may be true
3372 of time signatures, especially for those scores
3373 that include a measured timeline or other graphic. But these scores
3374 are exceptional and most proportional scores include at least some
3375 time signatures. Clefs and accidentals are even more essential.
3377 So what strategies exist for spacing non-musical elements in a
3378 proportional context? One good option is the @code{strict-note-spacing}
3379 property of @code{SpacingSpanner}. Compare the two scores below:
3381 @lilypond[quote,verbatim,ragged-right]
3383 \set Score.proportionalNotationDuration = #(ly:make-moment 1/16)
3384 c''8 8 8 \clef alto d'2 2
3388 \set Score.proportionalNotationDuration = #(ly:make-moment 1/16)
3389 \override Score.SpacingSpanner.strict-note-spacing = ##t
3390 c''8 8 8 \clef alto d'2 2
3394 Both scores are proportional, but the spacing in the first score
3395 is too loose because of the clef change. The spacing of the second
3396 score remains strict, however, because strict-note-spacing is
3397 turned on. Turning on strict-note-spacing causes the width of
3398 time signatures, key signatures, clefs and accidentals to play no
3399 part in the spacing algorithm.
3401 In addition to the settings given here, there are other settings
3402 that frequently appear in proportional scores. These include:
3405 @item @code{\override SpacingSpanner.strict-grace-spacing = ##t}
3406 @item @code{\set tupletFullLength = ##t}
3407 @item @code{\override Beam.breakable = ##t}
3408 @item @code{\override Glissando.breakable = ##t}
3409 @item @code{\override TextSpanner.breakable = ##t}
3410 @item @code{\remove "Forbid_line_break_engraver" in the Voice context}
3413 These settings space grace notes strictly, extend tuplet brackets to
3414 mark both rhythmic start- and stop-points, and allow spanning elements
3415 to break across systems and pages. See the respective parts of the manual
3416 for these related settings.
3420 @ref{New spacing area}.
3426 @node Fitting music onto fewer pages
3427 @section Fitting music onto fewer pages
3429 Sometimes you can end up with one or two staves on a second
3430 (or third, or fourth@dots{}) page. This is annoying, especially
3431 if you look at previous pages and it looks like there is plenty
3432 of room left on those.
3434 When investigating layout issues, @code{annotate-spacing} is an
3435 invaluable tool. This command prints the values of various layout
3436 spacing variables; for more details see the following section,
3437 @ref{Displaying spacing}.
3440 * Displaying spacing::
3441 * Changing spacing::
3445 @node Displaying spacing
3446 @subsection Displaying spacing
3448 @funindex annotate-spacing
3449 @cindex spacing, display of layout
3451 To graphically display the dimensions of vertical layout variables
3452 that may be altered for page formatting, set
3453 @code{annotate-spacing} in the @code{\paper} block:
3455 @lilypond[verbatim,quote,papersize=a6landscape]
3458 \paper { annotate-spacing = ##t }
3464 All layout dimensions are displayed in staff-spaces, regardless
3465 of the units specified in the @code{\paper} or @code{\layout} block.
3466 In the above example, @code{paper-height} has a value of 59.75
3467 @code{staff-spaces}, and the @code{staff-size} is 20 points (the
3468 default value). Note that:
3470 @multitable {1 staff-space} {staff-size)/4 * (25.4/72.27) mm}
3473 @tab = (25.4/72.27) mm
3476 @tab = (@code{staff-size})/4 pts
3478 @tab = (@code{staff-size})/4 * (25.4/72.27) mm
3483 In this case, one @code{staff-space} is approximately equal to
3484 1.757mm. Thus the @code{paper-height} measurement of 59.75
3485 @code{staff-spaces} is equivalent to 105 millimeters, the height
3486 of @code{a6} paper in landscape orientation. The pairs
3487 (@var{a},@var{b}) are intervals, where @var{a} is the lower
3488 edge and @var{b} the upper edge of the interval.
3492 @ref{Setting the staff size}.
3498 @node Changing spacing
3499 @subsection Changing spacing
3501 The output of @code{annotate-spacing} reveals vertical dimensions
3502 in great detail. For details about modifying margins and other
3503 layout variables, see @ref{Page layout}.
3505 Other than margins, there are a few other options to save space:
3509 Force systems to move as close together as possible (to fit as
3510 many systems as possible onto a page) while being spaced so that
3511 there is no blank space at the bottom of the page.
3515 system-system-spacing = #'((basic-distance . 0.1) (padding . 0))
3516 ragged-last-bottom = ##f
3522 Force the number of systems. This can help in two ways. Just
3523 setting a value, even the same value as the number of systems
3524 being typeset by default, will sometimes cause more systems to
3525 be fitted onto each page, as an estimation step is then bypassed,
3526 giving a more accurate fit to each page. Also, forcing an actual
3527 reduction in the number of systems may save a further page. For
3528 example, if the default layout has 11 systems, the following
3529 assignment will force a layout with 10 systems.
3538 Force the number of pages. For example, the following
3539 assignment will force a layout with 2 pages.
3548 Avoid (or reduce) objects that increase the vertical size of a
3549 system. For example, volta repeats (or alternate repeats) require
3550 extra space. If these repeats are spread over two systems, they
3551 will take up more space than one system with the volta repeats and
3552 another system without. For example, dynamics that @q{stick out} of
3553 a system can be moved closer to the staff:
3555 @lilypond[verbatim,quote,relative=1]
3557 e4 c g-\tweak X-offset #-2.7 \f c
3561 Alter the horizontal spacing via @code{SpacingSpanner}. For more
3562 details, see @ref{Changing horizontal spacing}. The following
3563 example illustrates the default spacing:
3565 @lilypond[verbatim,quote]
3578 The next example modifies @code{common-shortest-duration} from a
3579 value of @code{1/4} to @code{1/2}. The quarter note is the most
3580 common and shortest duration in this example, so by making this
3581 duration longer, a @q{squeezing} effect occurs:
3583 @lilypond[verbatim,quote]
3595 \override SpacingSpanner.common-shortest-duration =
3596 #(ly:make-moment 1/2)
3603 The @code{common-shortest-duration} property cannot be modified
3604 dynamically, so it must always be placed in a @code{\context}
3605 block so that it applies to the whole score.
3612 @ref{Changing horizontal spacing}.