1 @c -*- coding: utf-8; mode: texinfo; -*-
4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. For details, see the Contributors'
8 Guide, node Updating translation committishes..
16 Negative numbers are allowed:
17 > Are you sure? The following works well
19 > first-page-number = -2
21 > and prints page number -1 on the second page, for example.
25 http://code.google.com/p/lilypond/issues/detail?id=68
31 @chapter Spacing issues
33 The global paper layout is determined by three factors: the page layout, the
34 line breaks, and the spacing. These all influence each other. The
35 choice of spacing determines how densely each system of music is set.
36 This influences where line breaks are chosen, and thus ultimately, how
37 many pages a piece of music takes.
39 Globally speaking, this procedure happens in four steps: first,
40 flexible distances (@q{springs}) are chosen, based on durations. All
41 possible line breaking combinations are tried, and a @q{badness} score
42 is calculated for each. Then the height of each possible system is
43 estimated. Finally, a page breaking and line breaking combination is chosen
44 so that neither the horizontal nor the vertical spacing is too cramped
47 Two types of blocks can contain layout settings:
48 @code{\paper @{@dots{}@}} and @code{\layout @{@dots{}@}}. The
49 @code{\paper} block contains page layout settings that are expected
50 to be the same for all scores in a book or bookpart, such as the
51 paper height, or whether to print page numbers, etc. See
52 @ref{Page layout}. The @code{\layout} block contains score layout
53 settings, such as the number of systems to use, or the space
54 between staff-groups, etc. See @ref{Score layout}.
61 * Horizontal spacing::
62 * Fitting music onto fewer pages::
69 This section discusses page layout options for the @code{\paper}
74 * Paper size and automatic scaling::
75 * Fixed vertical spacing paper variables::
76 * Flexible vertical spacing paper variables::
77 * Horizontal spacing paper variables::
78 * Other paper variables::
83 @subsection The @code{@bs{}paper} block
85 @code{\paper} blocks may be placed in three different places to form
86 a descending hierarchy of @code{\paper} blocks:
91 At the top of the input file, before all @code{\book},
92 @code{\bookpart}, and @code{\score} blocks.
95 Within a @code{\book} block but outside all the @code{\bookpart} and
96 @code{\score} blocks within that book.
99 Within a @code{\bookpart} block but outside all @code{\score} blocks
100 within that bookpart.
104 A @code{\paper} block cannot be placed within a @code{\score} block.
106 The values of the fields filter down this hierarchy, with the values
107 set higher in the hierarchy persisting unless they are over-ridden
108 by a value set lower in the hierarchy.
110 Several @code{\paper} blocks can appear at each of the levels, for
111 example as parts of several @code{\include}d files. If so, the
112 fields at each level are merged, with values encountered last taking
113 precedence if duplicated fields appear.
115 Settings that can appear in a @code{\paper} block include:
120 the @code{set-paper-size} scheme function,
123 @code{\paper} variables used for customizing page layout, and
126 markup definitions used for customizing the layout of headers,
131 The @code{set-paper-size} function is discussed in the next
132 section, @ref{Paper size and automatic scaling}. The
133 @code{\paper} variables that deal with page layout are discussed
134 in later sections. The markup definitions that deal with headers,
135 footers, and titles are discussed in
136 @ref{Custom titles headers and footers}.
138 Most @code{\paper} variables will only work in a @code{\paper}
139 block. The few that will also work in a @code{\layout} block are
140 listed in @ref{The layout block,,The @code{@bs{}layout} block}.
142 Except when specified otherwise, all @code{\paper} variables that
143 correspond to distances on the page are measured in millimeters,
144 unless a different unit is specified by the user. For example,
145 the following declaration sets @code{top-margin} to ten
154 To set it to @code{0.5} inches, use the @code{\in} unit suffix:
162 The available unit suffixes are @code{\mm}, @code{\cm},
163 @code{\in}, and @code{\pt}. These units are simple values for
164 converting from millimeters; they are defined in
165 @file{ly/paper-defaults-init.ly}. For the sake of clarity, when
166 using millimeters, the @code{\mm} is typically included in the
167 code, even though it is not technically necessary.
169 It is also possible to define @code{\paper} values using Scheme.
170 The Scheme equivalent of the above example is:
174 #(define top-margin (* 0.5 in))
180 @ref{Paper size and automatic scaling},
181 @ref{Custom titles headers and footers},
182 @ref{The layout block,,The @code{@bs{}layout} block}.
185 @file{ly/paper-defaults-init.ly}.
188 @node Paper size and automatic scaling
189 @subsection Paper size and automatic scaling
197 * Setting the paper size::
198 * Automatic scaling to paper size::
202 @node Setting the paper size
203 @unnumberedsubsubsec Setting the paper size
205 @q{A4} is the default value when no explicit paper size is set. However,
206 there are two functions that can be used to change it:
209 @item set-default-paper-size
212 #(set-default-paper-size "quarto")
215 which must always be placed at the toplevel scope, and
221 #(set-paper-size "tabloid")
225 which must always be placed in a @code{\paper} block.
228 If the @code{set-default-paper-size} function is used in the toplevel
229 scope, it must come before any @code{\paper} block.
230 @code{set-default-paper-size} sets the paper size for all pages,
231 whereas @code{set-paper-size} only sets the paper size for the pages
232 that the @code{\paper} block applies to. For example, if the
233 @code{\paper} block is at the top of the file, then it will apply the
234 paper size to all pages. If the @code{\paper} block is inside a
235 @code{\book}, then the paper size will only apply to that book.
237 When the @code{set-paper-size} function is used, it must be
238 placed @emph{before} any other functions used within the same
239 @code{\paper} block. See @ref{Automatic scaling to paper size}.
241 Paper sizes are defined in @file{scm/paper.scm}, and while it is
242 possible to add custom sizes, they will be overwritten on subsequent
243 software updates. The available paper sizes are listed in
244 @ref{Predefined paper sizes}.
246 @c An appendix entry exists for paper sizes but is not auto-generated
248 The following command can be used in the file to add a custom paper size
249 which can then be used with @code{set-default-paper-size} or
250 @code{set-paper-size} as appropriate,
253 #(set! paper-alist (cons '("my size" . (cons (* 15 in) (* 3 in))) paper-alist))
256 #(set-paper-size "my size")
260 The units @code{in} (inches), @code{cm} (centimeters) and @code{mm}
261 (millimeters) can all be used.
263 @cindex paper size, orientation
264 @cindex page, orientation
265 @cindex paper size, landscape
267 If the symbol @code{'landscape} is added to the paper size function,
268 pages will be rotated by 90 degrees, and wider line widths will be set
272 #(set-default-paper-size "a6" 'landscape)
275 Swapping the paper dimensions @emph{without} having the print rotated
276 (like when printing to postcard size, or creating graphics for inclusion
277 rather than a standalone document) can be achieved by appending
278 @samp{landscape} to the name of the paper size itself:
281 #(set-default-paper-size "a6landscape")
284 When the paper size ends with an explicit @samp{landscape} or
285 @samp{portrait}, the presence of a @code{'landscape} symbol @emph{only}
286 affects print orientation, not the paper dimensions used for layout.
290 @ref{Automatic scaling to paper size},
291 @ref{Predefined paper sizes}.
294 @file{scm/paper.scm}.
297 @node Automatic scaling to paper size
298 @unnumberedsubsubsec Automatic scaling to paper size
300 If the paper size is changed with one of the scheme functions
301 (@code{set-default-paper-size} or @code{set-paper-size}), the
302 values of several @code{\paper} variables are automatically scaled
303 to the new size. To bypass the automatic scaling for a particular
304 variable, set the variable after setting the paper size. Note
305 that the automatic scaling is not triggered by setting the
306 @code{paper-height} or @code{paper-width} variables, even though
307 @code{paper-width} can influence other values (this is separate
308 from scaling and is discussed below). The
309 @code{set-default-paper-size} and @code{set-paper-size} functions
310 are described in @ref{Setting the paper size}.
312 The vertical dimensions affected by automatic scaling are
313 @code{top-margin} and @code{bottom-margin} (see
314 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables}).
316 dimensions affected by automatic scaling are @code{left-margin},
317 @code{right-margin}, @code{inner-margin}, @code{outer-margin},
318 @code{binding-offset}, @code{indent}, and @code{short-indent} (see
319 @ref{Horizontal spacing paper variables,,Horizontal spacing @code{@bs{}paper} variables}).
321 The default values for these dimensions are set in
322 @file{ly/paper-defaults-init.ly}, using internal variables named
323 @code{top-margin-default}, @code{bottom-margin-default}, etc.
324 These are the values that result at the default paper size
325 @code{a4}. For reference, with @code{a4} paper the
326 @code{paper-height} is @code{297\mm} and the @code{paper-width} is
331 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables},
332 @ref{Horizontal spacing paper variables,,Horizontal spacing @code{@bs{}paper} variables}.
335 @file{ly/paper-defaults-init.ly},
336 @file{scm/paper.scm}.
339 @node Fixed vertical spacing paper variables
340 @subsection Fixed vertical spacing @code{@bs{}paper} variables
342 @warning{Some @code{@bs{}paper} dimensions are automatically
343 scaled to the paper size, which may lead to unexpected behavior.
344 See @ref{Automatic scaling to paper size}.}
346 Default values (before scaling) are defined in
347 @file{ly/paper-defaults-init.ly}.
351 @funindex paper-height
353 The height of the page, unset by default. Note that the automatic
354 scaling of some vertical dimensions is not affected by this.
359 The margin between the top of the page and the top of the
360 printable area. If the paper size is modified, this dimension's
361 default value is scaled accordingly.
364 @funindex bottom-margin
366 The margin between the bottom of the printable area and the bottom
367 of the page. If the paper size is modified, this dimension's
368 default value is scaled accordingly.
371 @funindex ragged-bottom
373 If this is set to true,
374 systems will be set at their natural spacing, neither compressed
375 nor stretched vertically to fit the page.
377 @item ragged-last-bottom
378 @funindex ragged-last-bottom
380 If this is set to false, then the last page,
381 and the last page in each section created with a @code{\bookpart} block,
382 will be vertically justified in the same way as the earlier pages.
388 @ref{Automatic scaling to paper size}.
391 @file{ly/paper-defaults-init.ly}.
397 The titles (from the @code{\header} block) are treated as a
398 system, so @code{ragged-bottom} and @code{ragged-last-bottom} will
399 add space between the titles and the first system of the score.
401 Explicitly defined paper-sizes will override any user-defined top or
402 bottom margin settings.
405 @node Flexible vertical spacing paper variables
406 @subsection Flexible vertical spacing @code{@bs{}paper} variables
408 In most cases, it is preferable for the vertical distances between
409 certain items (such as margins, titles, systems, and separate
410 scores) to be flexible, so that they stretch and compress nicely
411 according to each situation. A number of @code{\paper} variables
412 (listed below) are available to fine-tune the stretching behavior
415 Note that the @code{\paper} variables discussed in this section do
416 not control the spacing of staves within individual systems.
417 Within-system spacing is controlled by grob properties, with
418 settings typically entered inside a @code{\score} or
419 @code{\layout} block, and not inside a @code{\paper} block. See
420 @ref{Flexible vertical spacing within systems}.
423 * Structure of flexible vertical spacing alists::
424 * List of flexible vertical spacing paper variables::
428 @node Structure of flexible vertical spacing alists
429 @unnumberedsubsubsec Structure of flexible vertical spacing alists
431 Each of the flexible vertical spacing @code{\paper} variables is
432 an alist (association list) containing four @emph{keys}:
437 @code{basic-distance} -- the vertical distance, measured in
438 staff-spaces, between the @emph{reference points} of the two
439 items, when no collisions would result, and no stretching or
440 compressing is in effect. The reference point of a (title or
441 top-level) markup is its highest point, and the reference point of
442 a system is the vertical center of the nearest @code{StaffSymbol}
443 -- even if a non-staff line (such as a @code{Lyrics} context) is
444 in the way. Values for @code{basic-distance} that are less than
445 either @code{padding} or @code{minimum-distance} are not
446 meaningful, since the resulting distance will never be less than
447 either @code{padding} or @code{minimum-distance}.
450 @code{minimum-distance} -- the smallest allowable vertical
451 distance, measured in staff-spaces, between the reference points
452 of the two items, when compressing is in effect. Values for
453 @code{minimum-distance} that are less than @code{padding} are not
454 meaningful, since the resulting distance will never be less than
457 @c TODO: explain skylines somewhere and xref to it from here.
460 @code{padding} -- the minimum required amount of unobstructed
461 vertical whitespace between the bounding boxes (or skylines) of
462 the two items, measured in staff-spaces.
465 @code{stretchability} -- a unitless measure of the dimension's
466 relative propensity to stretch. If zero, the distance will not
467 stretch (unless collisions would result). When positive, the
468 significance of a particular dimension's @code{stretchability}
469 value lies only in its relation to the @code{stretchability}
470 values of the other dimensions. For example, if one dimension has
471 twice the @code{stretchability} of another, it will stretch twice
472 as easily. Values should be non-negative and finite. The value
473 @code{+inf.0} triggers a @code{programming_error} and is ignored,
474 but @code{1.0e7} can be used for an almost infinitely stretchable
475 spring. If unset, the default value is set to
476 @code{basic-distance}. Note that the dimension's propensity to
477 @emph{compress} cannot be directly set by the user and is equal to
478 (@code{basic-distance}@tie{}@minus{}@tie{}@code{minimum-distance}).
482 If a page has a ragged bottom, the resulting distance is the
488 @code{basic-distance},
491 @code{minimum-distance}, and
494 @code{padding} plus the smallest distance necessary to eliminate
499 For multi-page scores with a ragged bottom on the last page, the last
500 page uses the same spacing as the preceding page, provided there is
501 enough space for that.
503 Specific methods for modifying alists are discussed in
504 @ref{Modifying alists}. The following example demonstrates the
505 two ways these alists can be modified. The first declaration
506 updates one key-value individually, and the second completely
507 redefines the variable:
511 system-system-spacing #'basic-distance = #8
512 score-system-spacing =
513 #'((basic-distance . 12)
514 (minimum-distance . 6)
516 (stretchability . 12))
521 @node List of flexible vertical spacing paper variables
522 @unnumberedsubsubsec List of flexible vertical spacing @code{@bs{}paper} variables
524 The names of these variables follow the format
525 @code{@var{upper}-@var{lower}-spacing}, where @code{@var{upper}}
526 and @code{@var{lower}} are the items to be spaced. Each distance
527 is measured between the reference points of the two items (see the
528 description of the alist structure above). Note that in these
529 variable names, the term @q{@code{markup}} refers to both
530 @emph{title markups} (@code{bookTitleMarkup} or
531 @code{scoreTitleMarkup}) and @emph{top-level markups} (see
532 @ref{File structure}). All distances are measured in
535 Default settings are defined in @file{ly/paper-defaults-init.ly}.
537 @c TODO: Where do headers/footers fit in? -mp
540 @item markup-system-spacing
541 @funindex markup-system-spacing
543 the distance between a (title or top-level) markup and the system
546 @item score-markup-spacing
547 @funindex score-markup-spacing
549 the distance between the last system of a score and the (title or
550 top-level) markup that follows it.
552 @item score-system-spacing
553 @funindex score-system-spacing
555 the distance between the last system of a score and the first
556 system of the score that follows it, when no (title or top-level)
557 markup exists between them.
559 @item system-system-spacing
560 @funindex system-system-spacing
562 the distance between two systems in the same score.
564 @item markup-markup-spacing
565 @funindex markup-markup-spacing
567 the distance between two (title or top-level) markups.
569 @item last-bottom-spacing
570 @funindex last-bottom-spacing
572 the distance from the last system or top-level markup on a page to
573 the bottom of the printable area (i.e. the top of the bottom
576 @item top-system-spacing
577 @funindex top-system-spacing
579 the distance from the top of the printable area (i.e. the bottom
580 of the top margin) to the first system on a page, when there is no
581 (title or top-level) markup between the two.
583 @item top-markup-spacing
584 @funindex top-markup-spacing
586 the distance from the top of the printable area (i.e. the bottom
587 of the top margin) to the first (title or top-level) markup on a
588 page, when there is no system between the two.
593 @ref{Flexible vertical spacing within systems}.
596 @file{ly/paper-defaults-init.ly}.
602 @node Horizontal spacing paper variables
603 @subsection Horizontal spacing @code{@bs{}paper} variables
605 @warning{Some @code{@bs{}paper} dimensions are automatically
606 scaled to the paper size, which may lead to unexpected behavior.
607 See @ref{Automatic scaling to paper size}.}
610 * paper variables for widths and margins::
611 * paper variables for two-sided mode::
612 * paper variables for shifts and indents::
616 @node paper variables for widths and margins
617 @unnumberedsubsubsec @code{@bs{}paper} variables for widths and margins
619 Default values (before scaling) that are not listed here are
620 defined in @file{ly/paper-defaults-init.ly}.
625 @funindex paper-width
627 The width of the page, unset by default. While @code{paper-width}
628 has no effect on the automatic scaling of some horizontal
629 dimensions, it does influence the @code{line-width} variable. If
630 both @code{paper-width} and @code{line-width} are set, then
631 @code{left-margin} and @code{right-margin} will also be updated.
632 Also see @code{check-consistency}.
637 The horizontal extent of the staff lines in unindented, non-ragged
639 @code{(paper-width@tie{}@minus{}@tie{}left-margin@tie{}@minus{}@tie{}right-margin)}
640 when unset. If @code{line-width} is set, and both
641 @code{left-margin} and @code{right-margin} are unset, then the
642 margins will be updated to center the systems on the page
643 automatically. Also see @code{check-consistency}. This variable
644 can also be set in a @code{\layout} block.
647 @funindex left-margin
649 The margin between the left edge of the page and the start of the
650 staff lines in unindented systems. If the paper size is modified,
651 this dimension's default value is scaled accordingly. If
652 @code{left-margin} is unset, and both @code{line-width} and
653 @code{right-margin} are set, then @code{left-margin} is set to
654 @code{(paper-width@tie{}@minus{}@tie{}line-width@tie{}@minus{}@tie{}right-margin)}.
655 If only @code{line-width} is set, then both margins are set to
656 @code{((paper-width@tie{}@minus{}@tie{}line-width)@tie{}/@tie{}2)},
657 and the systems are consequently centered on the page. Also see
658 @code{check-consistency}.
661 @funindex right-margin
663 The margin between the right edge of the page and the end of the
664 staff lines in non-ragged systems. If the paper size is modified,
665 this dimension's default value is scaled accordingly. If
666 @code{right-margin} is unset, and both @code{line-width} and
667 @code{left-margin} are set, then @code{right-margin} is set to
668 @code{(paper-width@tie{}@minus{}@tie{}line-width@tie{}@minus{}@tie{}left-margin)}.
669 If only @code{line-width} is set, then both margins are set to
670 @code{((paper-width@tie{}@minus{}@tie{}line-width)@tie{}/@tie{}2)},
671 and the systems are consequently centered on the page. Also see
672 @code{check-consistency}.
674 @item check-consistency
675 @funindex check-consistency
677 If set to true, print a warning if @code{left-margin},
678 @code{line-width}, and @code{right-margin} do not exactly add up
679 to @code{paper-width}, and replace each of these (except
680 @code{paper-width}) with its default value (scaled to the paper
681 size if necessary). If set to false, ignore any inconsistencies
682 and allow systems to run off the edge of the page.
685 @funindex ragged-right
687 If set to true, systems will not fill the line width. Instead,
688 systems end at their natural horizontal length. Default:
689 @code{#t} for scores with only one system, and @code{#f} for
690 scores with two or more systems. This variable can also be set in
691 a @code{\layout} block.
694 @funindex ragged-last
696 If set to true, the last system in the score will not fill the
697 line width. Instead the last system ends at its natural
698 horizontal length. Default: @code{#f}. This variable can also be
699 set in a @code{\layout} block.
705 @ref{Automatic scaling to paper size}.
708 @file{ly/paper-defaults-init.ly}.
711 Explicitly defined paper-sizes will override any user-defined left or
712 right margin settings.
715 @node paper variables for two-sided mode
716 @unnumberedsubsubsec @code{@bs{}paper} variables for two-sided mode
718 Default values (before scaling) are defined in
719 @file{ly/paper-defaults-init.ly}.
727 @cindex binding gutter
729 If set to true, use @code{inner-margin}, @code{outer-margin} and
730 @code{binding-offset} to determine margins depending on whether
731 the page number is odd or even. This overrides @code{left-margin}
732 and @code{right-margin}.
735 @funindex inner-margin
737 The margin all pages have at the inner side if they are part of a
738 book. If the paper size is modified, this dimension's default
739 value is scaled accordingly. Works only with @code{two-sided} set
743 @funindex outer-margin
745 The margin all pages have at the outer side if they are part of a
746 book. If the paper size is modified, this dimension's default
747 value is scaled accordingly. Works only with @code{two-sided} set
751 @funindex binding-offset
753 The amount @code{inner-margin} is increased to make sure nothing
754 will be hidden by the binding. If the paper size is modified,
755 this dimension's default value is scaled accordingly. Works only
756 with @code{two-sided} set to true.
762 @ref{Automatic scaling to paper size}.
765 @file{ly/paper-defaults-init.ly}.
768 @node paper variables for shifts and indents
769 @unnumberedsubsubsec @code{@bs{}paper} variables for shifts and indents
771 Default values (before scaling) that are not listed here are
772 defined in @file{ly/paper-defaults-init.ly}.
776 @item horizontal-shift
777 @funindex horizontal-shift
779 @c This default value is buried in the middle of page.scm. -mp
781 The amount that all systems (including titles and system
782 separators) are shifted to the right. Default: @code{0.0\mm}.
787 The level of indentation for the first system in a score. If the
788 paper size is modified, this dimension's default value is scaled
789 accordingly. This variable can also be set in a @code{\layout}
793 @funindex short-indent
795 The level of indentation for all systems in a score besides the
796 first system. If the paper size is modified, this dimension's
797 default value is scaled accordingly. This variable can also be
798 set in a @code{\layout} block.
804 @ref{Automatic scaling to paper size}.
807 @file{ly/paper-defaults-init.ly}.
813 @node Other paper variables
814 @subsection Other @code{@bs{}paper} variables
817 * paper variables for line breaking::
818 * paper variables for page breaking::
819 * paper variables for page numbering::
820 * Miscellaneous paper variables::
824 @node paper variables for line breaking
825 @unnumberedsubsubsec @code{@bs{}paper} variables for line breaking
829 @item max-systems-per-page
830 @funindex max-systems-per-page
832 The maximum number of systems that will be placed on a page. This
833 is currently supported only by the @code{ly:optimal-breaking} algorithm.
836 @item min-systems-per-page
837 @funindex min-systems-per-page
839 The minimum number of systems that will be placed on a page. This
840 may cause pages to be overfilled if it is made too large. This is
841 currently supported only by the @code{ly:optimal-breaking} algorithm.
844 @item systems-per-page
845 @funindex systems-per-page
847 The number of systems that should be placed on each page.
848 This is currently supported only by the @code{ly:optimal-breaking} algorithm.
852 @funindex system-count
854 The number of systems to be used for a score. Default: unset.
855 This variable can also be set in a @code{\layout} block.
864 @node paper variables for page breaking
865 @unnumberedsubsubsec @code{@bs{}paper} variables for page breaking
867 Default values not listed here are defined in
868 @file{ly/paper-defaults-init.ly}
873 @funindex page-breaking
875 The page-breaking algorithm to use. Choices are
876 @code{ly:minimal-breaking}, @code{ly:page-turn-breaking},
877 @code{ly:one-line-breaking} and @code{ly:optimal-breaking}
880 @item page-breaking-system-system-spacing
881 @funindex page-breaking-system-system-spacing
883 Tricks the page breaker into thinking that
884 @code{system-system-spacing} is set to something different than
885 it really is. For example, if
886 @code{page-breaking-system-system-spacing #'padding} is set to something
887 substantially larger than @code{system-system-spacing #'padding}, then the
888 page-breaker will put fewer systems on each page. Default: unset.
893 The number of pages to be used for a score, unset by default.
897 The following variables are effective only when @code{page-breaking}
898 is set to @code{ly:page-turn-breaking}. Page breaks are then chosen
899 to minimize the number of page turns. Since page turns are required
900 on moving from an odd-numbered page to an even-numbered one, a
901 layout in which the last page is odd-numbered will usually be
902 favoured. Places where page turns are preferred can be indicated
903 manually by inserting @code{\allowPageTurn} or automatically by
904 including the @code{Page_turn_engraver} (see @ref{Optimal page turning}).
906 If there are insufficient choices available for making suitable page
907 turns, LilyPond may insert a blank page either within a score, between
908 scores (if there are two or more scores), or by ending a score on an
909 even-numbered page. The values of the following three variables may
910 be increased to make these actions less likely.
912 The values are penalties, i.e. the higher the value the less likely
913 will be the associated action relative to other choices.
917 @item blank-page-penalty
918 @funindex blank-page-penalty
920 The penalty for having a blank page in the middle of a score. If
921 @code{blank-page-penalty} is large and @code{ly:page-turn-breaking} is
922 selected, then LilyPond will be less likely to insert a page in the
923 middle of a score. Instead, it will space out the music further to
924 fill the blank page and the following one. Default: 5.
926 @item blank-last-page-penalty
927 @funindex blank-last-page-penalty
929 The penalty for ending the score on an even-numbered page. If
930 @code{blank-last-page-penalty} is large and
931 @code{ly:page-turn-breaking} is selected, then LilyPond will be less
932 likely to produce a score in which the last page is even-numbered.
933 Instead, it will adjust the spacing in order to use one page more or
934 one page less. Default: 0.
936 @item blank-after-score-page-penalty
937 @funindex blank-after-score-page-penalty
939 The penalty for having a blank page after the end of one score and
940 before the next. By default, this is smaller than
941 @code{blank-page-penalty}, so that blank pages after scores are
942 inserted in preference to blank pages within a score. Default: 2.
950 @ref{Optimal page breaking},
951 @ref{Optimal page turning},
952 @ref{Minimal page breaking},
953 @ref{One-line page breaking}.
956 @file{ly/paper-defaults-init.ly}.
959 @node paper variables for page numbering
960 @unnumberedsubsubsec @code{@bs{}paper} variables for page numbering
962 Default values not listed here are defined in
963 @file{ly/paper-defaults-init.ly}
967 @cindex page numbers, auto-numbering
968 @item auto-first-page-number
969 @funindex auto-first-page-number
971 The page breaking algorithm is affected by the first page number
972 being odd or even. If set to true, the page breaking algorithm
973 will decide whether to start with an odd or even number. This
974 will result in the first page number remaining as is or being
975 increased by one. Default: @code{#f}.
977 @cindex page numbers, specify the first
978 @item first-page-number
979 @funindex first-page-number
981 The value of the page number on the first page.
983 @item print-first-page-number
984 @funindex print-first-page-number
986 If set to true, a page number is printed on the first page.
988 @cindex page numbers, suppress
989 @item print-page-number
990 @funindex print-page-number
992 If set to false, page numbers are not printed.
998 @file{ly/paper-defaults-init.ly}.
1001 Odd page numbers are always on the right. If you want the
1002 music to start on page 1 there must be a blank page on the back
1003 of the cover page so that page 1 is on the right hand side.
1006 @node Miscellaneous paper variables
1007 @unnumberedsubsubsec Miscellaneous @code{@bs{}paper} variables
1011 @item page-spacing-weight
1012 @funindex page-spacing-weight
1014 The relative importance of page (vertical) spacing and line
1015 (horizontal) spacing. High values will make page spacing more
1016 important. Default: @code{10}.
1018 @item print-all-headers
1019 @funindex print-all-headers
1021 If set to true, this will print all headers for each @code{\score}
1022 in the output. Normally only the @code{piece} and @code{opus}
1023 header variables are printed. Default: @code{#f}.
1025 @item system-separator-markup
1026 @funindex system-separator-markup
1028 A markup object that is inserted between systems, often used for
1029 orchestral scores. Default: unset. The @code{\slashSeparator}
1030 markup, defined in @file{ly/titling-init.ly}, is provided as a
1031 sensible default, for example:
1033 @lilypond[quote,verbatim,noragged-right,line-width=30\mm]
1034 #(set-default-paper-size "a8")
1038 system-separator-markup = \slashSeparator
1044 \relative c'' { c1 \break c1 \break c1 }
1053 @file{ly/titling-init.ly}.
1059 The default page header puts the page number and the @code{instrument}
1060 field from the @code{\header} block on a line.
1064 @section Score layout
1066 This section discusses score layout options for the @code{\layout}
1070 * The layout block::
1071 * Setting the staff size::
1075 @node The layout block
1076 @subsection The @code{@bs{}layout} block
1080 While the @code{\paper} block contains settings that relate to the
1081 page formatting of the whole document, the @code{\layout} block
1082 contains settings for score-specific layout. To set score layout
1083 options globally, enter them in a toplevel @code{\layout} block.
1084 To set layout options for an individual score, enter them in a
1085 @code{\layout} block inside the @code{\score} block, after the
1086 music. Settings that can appear in a @code{\layout} block
1090 @item the @code{layout-set-staff-size} scheme function,
1091 @item context modifications in @code{\context} blocks, and
1092 @item @code{\paper} variables that affect score layout.
1095 The @code{layout-set-staff-size} function is discussed in the next
1096 section, @ref{Setting the staff size}. Context modifications are
1097 discussed in a separate chapter; see
1098 @ref{Modifying context plug-ins} and
1099 @ref{Changing context default settings}. The @code{\paper}
1100 variables that can appear in a @code{\layout} block are:
1105 @code{line-width}, @code{ragged-right} and @code{ragged-last}
1106 (see @ref{paper variables for widths and margins,,@code{@bs{}paper} variables for widths and margins})
1109 @code{indent} and @code{short-indent}
1110 (see @ref{paper variables for shifts and indents,,@code{@bs{}paper} variables for shifts and indents})
1114 (see @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking})
1118 Here is an example @code{\layout} block:
1125 \override StaffGrouper.staff-staff-spacing.basic-distance = #8
1129 \override TextScript.padding = #1
1130 \override Glissando.thickness = #3
1135 Multiple @code{\layout} blocks can be entered as toplevel expressions.
1136 This can, for example, be useful if different settings are stored in
1137 separate files and included optionally. Internally, when
1138 a @code{\layout} block is evaluated, a copy of the current
1139 @code{\layout} configuration is made, then any changes defined within
1140 the block are applied and the result is saved as the new current
1141 configuration. From the user's perspective the @code{\layout} blocks
1142 are combined, but in conflicting situations (when the same property
1143 is changed in different blocks) the later definitions take precedence.
1145 For example, if this block:
1151 \override TextScript.color = #magenta
1152 \override Glissando.thickness = #1.5
1157 is placed after the one from the preceding example the @code{'padding}
1158 and @code{'color} overrides for @code{TextScript} are combined, but
1159 the later @code{'thickness} override for @code{Glissando} replaces
1160 (or hides) the earlier one.
1162 @code{\layout} blocks may be assigned to variables for reuse later,
1163 but the way this works is slightly but significantly different from
1164 writing them literally.
1166 If a variable is defined like this:
1169 layoutVariable = \layout @{
1172 \override NoteHead.font-size = #4
1177 it will hold the current @code{\layout} configuration with the
1178 @code{NoteHead.font-size} override added, but this combination
1179 is @emph{not} saved as the new current configuration. Be aware
1180 that the @q{current configuration} is read when the variable is
1181 defined and not when it is used, so the content of the variable
1182 is dependent on its position in the source.
1184 The variable can then be used inside another @code{\layout} block,
1192 \override NoteHead.color = #red
1197 A @code{\layout} block containing a variable, as in the example above,
1198 does @emph{not} copy the current configuration but instead uses the
1199 content of @code{\layoutVariable} as the base configuration for the
1200 further additions. This means that any changes defined between the
1201 definition and the use of the variable are lost.
1203 If @code{layoutVariable} is defined (or @code{\include}d) immediately
1204 before being used, its content is just the current configuration plus
1205 the overrides defined within it. So in the example above showing the
1206 use of @code{\layoutVariable} the final @code{\layout} block would
1210 TextScript.padding = #1
1211 TextScript.color = #magenta
1212 Glissando.thickness = #1.5
1213 NoteHead.font-size = #4
1214 NoteHead.color = #red
1217 plus the @code{indent} and the @code{StaffGrouper} overrides.
1219 But if the variable had already been defined before the first
1220 @code{\layout} block the current configuration would now contain
1224 NoteHead.font-size = #4 % (written in the variable definition)
1225 NoteHead.color = #red % (added after the use of the variable)
1228 If carefully planned, @code{\layout} variables can be a valuable tool
1229 to structure the layout design of sources, and also to reset the
1230 @code{\layout} configuration to a known state.
1234 @ref{Changing context default settings}.
1240 @node Setting the staff size
1241 @subsection Setting the staff size
1243 @cindex font size, setting
1244 @cindex staff size, setting
1245 @funindex layout file
1246 @funindex magnification->font-size
1248 @funindex set-global-staff-size
1249 @funindex layout-set-staff-size
1251 The default @strong{staff size} is 20 points, which corresponds to
1252 a staff height of 7.03mm (one point is equal to 100/7227 of an
1253 inch, or 2540/7227 mm). The staff size may be changed in three
1259 To set the staff size globally for all scores in a file (or in a
1260 @code{\book} block, to be precise), use
1261 @code{set-global-staff-size}:
1264 #(set-global-staff-size 14)
1268 The above example sets the global default staff size to 14pt
1269 (4.92mm) and scales all fonts accordingly.
1272 To set the staff size for a single score within a book, use
1273 @code{layout-set-staff-size} inside that score's @code{\layout}
1280 #(layout-set-staff-size 14)
1286 To set the staff size for a single staff within a system, set the
1287 staff's font-size and staff-space using units relative to the
1288 score's default staff size. Using relative units prevents the
1289 proportion of staff sizes from being altered if the default staff
1290 size is modified with @code{set-global-staff-size} or
1291 @code{layout-set-staff-size}.
1293 For example, traditionally engraved chamber music scores with
1294 piano often used 7mm piano staves while the other staves were up
1295 to 5/7 as large (if space allowed), or down to 3/5 as large (if
1296 space was cramped). To achieve the 5/7 proportion, use:
1302 fontSize = #(magnification->font-size 5/7)
1303 \override StaffSymbol.staff-space = #5/7
1305 \new PianoStaff @{ @dots{} @}
1310 If you happen to know which @code{fontSize} you wish to use, you
1311 could use the following form:
1318 \override StaffSymbol.staff-space = #(magstep -3)
1320 \new PianoStaff @{ @dots{} @}
1325 To emulate the look of traditional engraving, it is best to avoid
1326 reducing the thickness of the staff lines.
1331 @subheading Automatic font weight at different sizes
1333 The Feta font provides musical symbols at eight different
1334 sizes. Each font is tuned for a different staff size: at a smaller size
1335 the font becomes heavier, to match the relatively heavier staff lines.
1336 The recommended font sizes are listed in the following table:
1338 @multitable @columnfractions .15 .2 .22 .2
1339 @item @b{font name} @tab @b{staff height (pt)} @tab @b{staff height (mm)} @tab @b{use}
1340 @item feta11 @tab 11.22 @tab 3.9 @tab pocket scores
1341 @item feta13 @tab 12.60 @tab 4.4 @tab
1342 @item feta14 @tab 14.14 @tab 5.0 @tab
1343 @item feta16 @tab 15.87 @tab 5.6 @tab
1344 @item feta18 @tab 17.82 @tab 6.3 @tab song books
1345 @item feta20 @tab 20 @tab 7.0 @tab standard parts
1346 @item feta23 @tab 22.45 @tab 7.9 @tab
1347 @item feta26 @tab 25.2 @tab 8.9 @tab @c modern rental material?
1352 @ref{Selecting notation font size}.
1358 @code{layout-set-staff-size} does not change the distance between the
1368 * Optimal page breaking::
1369 * Optimal page turning::
1370 * Minimal page breaking::
1371 * One-line page breaking::
1373 * Using an extra voice for breaks::
1378 @subsection Line breaking
1381 @cindex breaking lines
1383 Line breaks are normally determined automatically. They are chosen
1384 so that lines look neither cramped nor loose, and consecutive
1385 lines have similar density.
1387 To manually force a line break at a bar line, use the
1388 @code{\break} command:
1390 @lilypond[quote,ragged-right,relative=2,verbatim]
1395 By default, a @code{\break} in the middle of a measure is ignored,
1396 and a warning is printed. To force a line break in the middle of
1397 a measure, add an invisible bar line with @w{@samp{\bar ""}}:
1399 @lilypond[quote,ragged-right,relative=2,verbatim]
1406 A @code{\break} occurring at a bar line is also ignored if the
1407 previous measure ends in the middle of a note, such as when a
1408 tuplet begins and ends in different measures. To allow
1409 @code{\break} commands to work in these situations, remove the
1410 @code{Forbid_line_break_engraver} from the @code{Voice} context.
1411 Note that manually forced line breaks have to be added in parallel
1414 @lilypond[quote,ragged-right,verbatim]
1416 \remove "Forbid_line_break_engraver"
1419 { c2. \tuplet 3/2 { c4 c c } c2. | }
1420 { s1 | \break s1 | }
1425 Similarly, line breaks are normally forbidden when beams cross bar
1426 lines. This behavior can be changed by setting
1427 @code{\override Beam.breakable = ##t}:
1429 @lilypond[quote,ragged-right,relative=2,verbatim]
1430 \override Beam.breakable = ##t
1435 The @code{\noBreak} command forbids a line break at the bar line
1436 where it is inserted.
1438 The most basic settings influencing line spacing are @code{indent}
1439 and @code{line-width}. They are set in the @code{\layout} block.
1440 They control the indentation of the first line of music, and the
1441 lengths of the lines.
1443 If @code{ragged-right} is set to true in the @code{\layout} block,
1444 then systems end at their natural horizontal length, instead of
1445 being spread horizontally to fill the whole line. This is useful
1446 for short fragments, and for checking how tight the natural
1449 @c TODO Check and add para on default for ragged-right
1451 The option @code{ragged-last} is similar to @code{ragged-right},
1452 but affects only the last line of the piece.
1464 @cindex regular line breaks
1465 @cindex four bar music.
1467 For line breaks at regular intervals use @code{\break} separated by
1468 skips and repeated with @code{\repeat}. For example, this would
1469 cause the following 28 measures (assuming 4/4 time) to be broken
1470 every 4 measures, and only there:
1475 s1 \noBreak s1 \noBreak
1476 s1 \noBreak s1 \break
1478 @{ @var{the actual music@dots{}} @}
1492 @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking}.
1497 Internals Reference:
1498 @rinternals{LineBreakEvent}.
1502 @subsection Page breaking
1504 The default page breaking may be overridden by inserting
1505 @code{\pageBreak} or @code{\noPageBreak} commands. These commands are
1506 analogous to @code{\break} and @code{\noBreak}. They should be
1507 inserted at a bar line. These commands force and forbid a page-break
1508 from happening. Of course, the @code{\pageBreak} command also forces
1511 The @code{\pageBreak} and @code{\noPageBreak} commands may also be
1512 inserted at top-level, between scores and top-level markups.
1514 There are also analogous settings to @code{ragged-right} and
1515 @code{ragged-last} which have the same effect on vertical spacing.
1516 If @code{ragged-bottom} is set to @code{#t} the systems will not
1517 be justified vertically. When @code{ragged-last-bottom} is set
1518 to @code{#t}, as it is by default, empty space is allowed at the
1519 bottom of the final page (or the final page in each
1520 @code{\bookpart}). See
1521 @ref{Fixed vertical spacing paper variables,,Fixed vertical spacing @code{@bs{}paper} variables}.
1523 Page breaks are computed by the @code{page-breaking} function. LilyPond
1524 provides three algorithms for computing page breaks,
1525 @code{ly:optimal-breaking}, @code{ly:page-turn-breaking} and
1526 @code{ly:minimal-breaking}. The default is @code{ly:optimal-breaking},
1527 but the value can be changed in the @code{\paper} block:
1531 page-breaking = #ly:page-turn-breaking
1537 When a book has many scores and pages, the page breaking problem may be
1538 difficult to solve, requiring large processing time and memory. To ease
1539 the page breaking process, @code{\bookpart} blocks are used to divide
1540 the book into several parts: the page breaking occurs separately on each
1541 part. Different page breaking functions may also be used in different
1547 subtitle = "Preface"
1550 %% In a part consisting mostly of text,
1551 %% ly:minimal-breaking may be preferred
1552 page-breaking = #ly:minimal-breaking
1554 \markup @{ @dots{} @}
1558 %% In this part, consisting of music, the default optimal
1559 %% page breaking function is used.
1561 subtitle = "First movement"
1563 \score @{ @dots{} @}
1570 @funindex \pageBreak
1572 @funindex \noPageBreak
1573 @code{\noPageBreak}.
1578 @ref{paper variables for page breaking,,@code{@bs{}paper} variables for page breaking}.
1584 @node Optimal page breaking
1585 @subsection Optimal page breaking
1587 @funindex ly:optimal-breaking
1589 The @code{ly:optimal-breaking} function is LilyPond's default method of
1590 determining page breaks. It attempts to find a page breaking that minimizes
1591 cramping and stretching, both horizontally and vertically. Unlike
1592 @code{ly:page-turn-breaking}, it has no concept of page turns.
1599 @node Optimal page turning
1600 @subsection Optimal page turning
1602 @funindex ly:page-turn-breaking
1604 Often it is necessary to find a page breaking configuration so that there is
1605 a rest at the end of every second page. This way, the musician can turn the
1606 page without having to miss notes. The @code{ly:page-turn-breaking} function
1607 attempts to find a page breaking minimizing cramping and stretching, but with
1608 the additional restriction that it is only allowed to introduce page turns
1609 in specified places.
1611 There are two steps to using this page breaking function. First, you
1612 must enable it in the @code{\paper} block, as explained in @ref{Page
1613 breaking}. Then you must tell the function where you would like to allow
1616 There are two ways to achieve the second step. First, you can specify each
1617 potential page turn manually, by inserting @code{\allowPageTurn} into your
1618 input file at the appropriate places.
1620 If this is too tedious, you can add a @code{Page_turn_engraver} to a Staff or
1621 Voice context. The @code{Page_turn_engraver} will scan the context for
1622 sections without notes (note that it does not scan for rests; it scans for
1623 the absence of notes. This is so that single-staff polyphony with rests in one
1624 of the parts does not throw off the @code{Page_turn_engraver}). When it finds
1625 a sufficiently long section without notes, the @code{Page_turn_engraver} will
1626 insert an @code{\allowPageTurn} at the final bar line in that section, unless
1627 there is a @q{special} bar line (such as a double bar), in which case the
1628 @code{\allowPageTurn} will be inserted at the final @q{special} bar line in
1631 @funindex minimumPageTurnLength
1632 The @code{Page_turn_engraver} reads the context property
1633 @code{minimumPageTurnLength} to determine how long a note-free section must
1634 be before a page turn is considered. The default value for
1635 @code{minimumPageTurnLength} is @code{(ly:make-moment 1/1)}. If you want
1636 to disable page turns, you can set it to something very large.
1639 \new Staff \with @{ \consists "Page_turn_engraver" @}
1642 R1 | % a page turn will be allowed here
1644 \set Staff.minimumPageTurnLength = #(ly:make-moment 5/2)
1645 R1 | % a page turn will not be allowed here
1647 R1*2 | % a page turn will be allowed here
1652 @funindex minimumRepeatLengthForPageTurn
1653 The @code{Page_turn_engraver} detects volta repeats. It will only allow a page
1654 turn during the repeat if there is enough time at the beginning and end of the
1655 repeat to turn the page back. The @code{Page_turn_engraver} can also disable
1656 page turns if the repeat is very short. If you set the context property
1657 @code{minimumRepeatLengthForPageTurn} then the @code{Page_turn_engraver} will
1658 only allow turns in repeats whose duration is longer than this value.
1660 The page turning commands, @code{\pageTurn}, @code{\noPageTurn} and
1661 @code{\allowPageTurn}, may also be used at top-level, between scores and
1667 @funindex \noPageTurn
1669 @funindex \allowPageTurn
1670 @code{\allowPageTurn}.
1675 @ref{paper variables for line breaking,,@code{@bs{}paper} variables for line breaking}.
1681 There should only be one @code{Page_turn_engraver} in a score. If there is more
1682 than one, they will interfere with each other.
1685 @node Minimal page breaking
1686 @subsection Minimal page breaking
1688 @funindex ly:minimal-breaking
1690 The @code{ly:minimal-breaking} function performs minimal computations to
1691 calculate the page breaking: it fills a page with as many systems as
1692 possible before moving to the next one. Thus, it may be preferred for
1693 scores with many pages, where the other page breaking functions could be
1694 too slow or memory demanding, or a lot of texts. It is enabled using:
1698 page-breaking = #ly:minimal-breaking
1706 @node One-line page breaking
1707 @subsection One-line page breaking
1709 @funindex ly:one-line-breaking
1711 The @code{ly:one-line-breaking} function is a special-purpose
1712 page breaking algorithm that puts each score on its own page,
1713 and on a single line. This page breaking function does not
1714 typeset titles or margins; only the score will be displayed.
1716 The page width will be adjusted so that
1717 the longest score fits on one line. In particular,
1718 @code{paper-width}, @code{line-width} and @code{indent}
1719 variables in the @code{\paper} block will be ignored, although
1720 @code{left-margin} and @code{right-margin} will
1721 still be honored. The height of the page will
1724 @node Explicit breaks
1725 @subsection Explicit breaks
1727 Lily sometimes rejects explicit @code{\break} and @code{\pageBreak}
1728 commands. There are two commands to override this behavior:
1731 \override NonMusicalPaperColumn.line-break-permission = ##f
1732 \override NonMusicalPaperColumn.page-break-permission = ##f
1735 When @code{line-break-permission} is overridden to false, Lily will insert
1736 line breaks at explicit @code{\break} commands and nowhere else. When
1737 @code{page-break-permission} is overridden to false, Lily will insert
1738 page breaks at explicit @code{\pageBreak} commands and nowhere else.
1740 @lilypond[quote,verbatim]
1747 music = \relative c'' { c8 c c c }
1751 \repeat unfold 2 { \music } \break
1752 \repeat unfold 4 { \music } \break
1753 \repeat unfold 6 { \music } \break
1754 \repeat unfold 8 { \music } \pageBreak
1755 \repeat unfold 8 { \music } \break
1756 \repeat unfold 6 { \music } \break
1757 \repeat unfold 4 { \music } \break
1758 \repeat unfold 2 { \music }
1763 \override NonMusicalPaperColumn.line-break-permission = ##f
1764 \override NonMusicalPaperColumn.page-break-permission = ##f
1775 @node Using an extra voice for breaks
1776 @subsection Using an extra voice for breaks
1778 Line- and page-breaking information usually appears within note entry directly.
1781 music = \relative c'' @{ c4 c c c @}
1785 \repeat unfold 2 @{ \music @} \break
1786 \repeat unfold 3 @{ \music @}
1791 This makes @code{\break} and @code{\pageBreak} commands easy to enter but mixes
1792 music entry with information that specifies how music should lay out
1793 on the page. You can keep music entry and line- and page-breaking
1794 information in two separate places by introducing an extra voice to
1795 contain the breaks. This extra voice
1796 contains only skips together with @code{\break}, @code{pageBreak} and other
1797 breaking layout information.
1799 @lilypond[quote,verbatim]
1800 music = \relative c'' { c4 c c c }
1802 \header { tagline = ##f }
1803 \paper { left-margin = 0\mm }
1814 \repeat unfold 2 { \music }
1815 \repeat unfold 3 { \music }
1816 \repeat unfold 6 { \music }
1817 \repeat unfold 5 { \music }
1824 This pattern becomes especially helpful when overriding
1825 @code{line-break-system-details} and the other useful but long properties of
1826 @code{NonMusicalPaperColumnGrob}, as explained in @ref{Vertical spacing}.
1828 @lilypond[quote,verbatim]
1829 music = \relative c'' { c4 c c c }
1831 \header { tagline = ##f }
1832 \paper { left-margin = 0\mm }
1837 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1841 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1845 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1849 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
1854 \repeat unfold 2 { \music }
1855 \repeat unfold 3 { \music }
1856 \repeat unfold 6 { \music }
1857 \repeat unfold 5 { \music }
1866 @ref{Vertical spacing}.
1872 @node Vertical spacing
1873 @section Vertical spacing
1875 @cindex vertical spacing
1876 @cindex spacing, vertical
1878 Vertical spacing is controlled by three things: the amount of
1879 space available (i.e., paper size and margins), the amount of
1880 space between systems, and the amount of space between
1881 staves inside a system.
1884 * Flexible vertical spacing within systems::
1885 * Explicit staff and system positioning::
1886 * Vertical collision avoidance::
1890 @node Flexible vertical spacing within systems
1891 @subsection Flexible vertical spacing within systems
1893 @cindex distance between staves
1894 @cindex staff distance
1895 @cindex space between staves
1896 @cindex space inside systems
1898 Three separate mechanisms control the flexible vertical spacing
1899 within systems, one for each of the following categories:
1904 @emph{ungrouped staves},
1907 @emph{grouped staves} (staves within a staff-group such as
1908 @code{ChoirStaff}, etc.), and
1911 @emph{non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
1916 @c TODO: Clarify this. This almost implies that non-staff lines
1917 @c have NO effect on the spacing between staves. -mp
1919 The height of each system is determined in two steps. First, all
1920 of the staves are spaced according to the amount of space
1921 available. Then, the non-staff lines are distributed between the
1924 Note that the spacing mechanisms discussed in this section only
1925 control the vertical spacing of staves and non-staff lines within
1926 individual systems. The vertical spacing between separate
1927 systems, scores, markups, and margins is controlled by
1928 @code{\paper} variables, which are discussed in
1929 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables}.
1932 * Within-system spacing properties::
1933 * Spacing of ungrouped staves::
1934 * Spacing of grouped staves::
1935 * Spacing of non-staff lines::
1939 @node Within-system spacing properties
1940 @unnumberedsubsubsec Within-system spacing properties
1942 @funindex staff-affinity
1943 @funindex staffgroup-staff-spacing
1944 @funindex staff-staff-spacing
1945 @funindex nonstaff-unrelatedstaff-spacing
1946 @funindex nonstaff-relatedstaff-spacing
1947 @funindex nonstaff-nonstaff-spacing
1948 @funindex default-staff-staff-spacing
1949 @funindex minimum-Y-extent
1950 @funindex extra-offset
1951 @funindex self-alignment-X
1953 @funindex VerticalAxisGroup
1955 The within-system vertical spacing mechanisms are controlled by
1956 two sets of grob properties. The first set is associated with the
1957 @code{VerticalAxisGroup} grob, which is created by all staves and
1958 non-staff lines. The second set is associated with the
1959 @code{StaffGrouper} grob, which can be created by staff-groups,
1960 but only if explicitly called. These properties are described
1961 individually at the end of this section.
1963 The names of these properties (except for @code{staff-affinity})
1964 follow the format @code{@var{item1}-@var{item2}-spacing}, where
1965 @code{@var{item1}} and @code{@var{item2}} are the items to be
1966 spaced. Note that @code{@var{item2}} is not necessarily below
1967 @code{@var{item1}}; for example,
1968 @code{nonstaff-relatedstaff-spacing} will measure upwards from the
1969 non-staff line if @code{staff-affinity} is @code{UP}.
1971 Each distance is measured between the @emph{reference points} of
1972 the two items. The reference point for a staff is the vertical
1973 center of its @code{StaffSymbol} (i.e. the middle line if
1974 @code{line-count} is odd; the middle space if @code{line-count} is
1975 even). The reference points for individual non-staff lines are
1976 given in the following table:
1978 @multitable {Non-staff line} {Reference point}
1979 @headitem Non-staff line @tab Reference point
1980 @item @code{ChordNames} @tab baseline
1981 @item @code{NoteNames} @tab baseline
1982 @item @code{Lyrics} @tab baseline
1983 @item @code{Dynamics} @tab mid-height of @q{m}
1984 @item @code{FiguredBass} @tab highest point
1985 @item @code{FretBoards} @tab top line
1988 In the following image, horizontal lines indicate the positions
1989 of these reference points:
1991 @lilypond[quote,noragged-right,line-width=110\mm]
1992 #(define zero-space '((padding . -inf.0) (basic-distance . 0)))
1994 alignToZero = \with {
1995 \override VerticalAxisGroup.nonstaff-relatedstaff-spacing = #zero-space
1996 \override VerticalAxisGroup.nonstaff-nonstaff-spacing = #zero-space
1997 \override VerticalAxisGroup.staff-affinity = #DOWN
1998 \remove Text_engraver % avoid having two
1999 \consists Text_engraver
2001 lowerCaseChords = \with {
2002 chordNameLowercaseMinor = ##t
2005 #(define-music-function
2006 (parser location context)
2008 #{ s1*0^\markup { \upright {\typewriter #context } } #})
2011 \context { \Dynamics \alignToZero }
2012 \context { \FiguredBass \alignToZero }
2013 \context { \Lyrics \alignToZero }
2014 \context { \NoteNames \alignToZero }
2015 \context { \ChordNames \alignToZero \lowerCaseChords }
2016 \context { \FretBoards \alignToZero }
2019 \override DynamicText.self-alignment-X = #-1
2020 \override FretBoard.X-offset = #1.75
2021 \override InstrumentName.minimum-Y-extent = #'(-1 . 2)
2027 %% These contexts have reference points at the baseline:
2028 %% ChordNames, NoteNames, and Lyrics
2030 \new ChordNames { \chords { \labelContext "ChordNames" g1:m } }
2031 \new NoteNames { s1 |\labelContext "NoteNames" g1 | }
2032 \new Lyrics { \lyrics { \skip 1*2 | \labelContext "Lyrics" ghijk1 | } }
2033 \new RhythmicStaff \with { instrumentName = #"baseline " } s1*3
2036 %% The reference point for Dynamics is the midline of 'm' in the font
2038 \new Dynamics { \labelContext "Dynamics" s1\mp s\fp }
2039 \new RhythmicStaff \with { instrumentName = #"mid-height " } s1*3
2042 %% The reference point for FiguredBass is its highest point
2044 \new FiguredBass { \labelContext "FiguredBass" \figuremode { <6 5>1 } }
2045 \new RhythmicStaff \with { instrumentName = #"highest point " } s1
2048 %% The reference point for FretBoards is the top line
2049 \include "predefined-guitar-fretboards.ly"
2051 \new FretBoards { \labelContext "FretBoards" \chordmode { e1 } }
2052 \new RhythmicStaff \with { instrumentName = #"top line " } s1
2056 Each of the vertical spacing grob properties (except
2057 @code{staff-affinity}) uses the same alist structure as the
2058 @code{\paper} spacing variables discussed in
2059 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables}.
2061 for modifying alists are discussed in @ref{Modifying alists}.
2062 Grob properties should be adjusted with an @code{\override} inside
2063 a @code{\score} or @code{\layout} block, and not inside a
2064 @code{\paper} block.
2066 The following example demonstrates the two ways these alists can
2067 be modified. The first declaration updates one key-value
2068 individually, and the second completely re-defines the property:
2072 \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #10
2076 \override VerticalAxisGroup.default-staff-staff-spacing =
2077 #'((basic-distance . 10)
2078 (minimum-distance . 9)
2080 (stretchability . 10))
2084 To change any spacing settings globally, put them in the
2085 @code{\layout} block:
2091 \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #10
2096 Standard settings for the vertical spacing grob properties are
2097 listed in @rinternals{VerticalAxisGroup} and
2098 @rinternals{StaffGrouper}. Default overrides for specific types
2099 of non-staff lines are listed in the relevant context descriptions
2100 in @rinternals{Contexts}.
2103 @subsubheading Properties of the @code{VerticalAxisGroup} grob
2105 @code{VerticalAxisGroup} properties are typically adjusted with an
2106 @code{\override} at the @code{Staff} level (or equivalent).
2109 @item staff-staff-spacing
2111 Used to determine the distance between the current staff and the
2112 staff just below it in the same system, even if one or more
2113 non-staff lines (such as @code{Lyrics}) are placed between the two
2114 staves. Does not apply to the bottom staff of a system.
2116 Initially, the @code{staff-staff-spacing} of a
2117 @code{VerticalAxisGroup} is a Scheme function that applies the
2118 properties of the @code{StaffGrouper} if the staff is part of a
2119 group, or the @code{default-staff-staff-spacing} of the staff
2120 otherwise. This allows staves to be spaced differently when they
2121 are grouped. For uniform spacing regardless of grouping, this
2122 function may be replaced by a flexible-spacing alist, using the
2123 complete-redefinition form of override shown above.
2125 @item default-staff-staff-spacing
2126 A flexible-spacing alist defining the @code{staff-staff-spacing} used for
2127 ungrouped staves, unless @code{staff-staff-spacing} has been explicitly
2128 set with an @code{\override}.
2130 @item staff-affinity
2131 The direction of the staff to use for spacing the current
2132 non-staff line. Choices are @code{UP}, @code{DOWN}, and
2133 @code{CENTER}. If @code{CENTER}, the non-staff line will be
2134 placed equidistant between the two nearest staves on either side,
2135 unless collisions or other spacing constraints prevent this.
2136 Adjacent non-staff lines should have non-increasing
2137 @code{staff-affinity} from top to bottom, e.g. a non-staff line
2138 set to @code{UP} should not immediately follow one that is set to
2139 @code{DOWN}. Non-staff lines at the top of a system should use
2140 @code{DOWN}; those at the bottom should use @code{UP}. Setting
2141 @code{staff-affinity} for a staff causes it to be treated as a
2142 non-staff line. Setting @code{staff-affinity} to @code{#f} causes
2143 a non-staff line to be treated as a staff. Setting
2144 @code{staff-affinity} to @code{UP}, @code{CENTER}, or @code{DOWN}
2145 causes a staff to be spaced as a non-staff line.
2147 @item nonstaff-relatedstaff-spacing
2148 The distance between the current non-staff line and the nearest
2149 staff in the direction of @code{staff-affinity}, if there are no
2150 non-staff lines between the two, and @code{staff-affinity} is
2151 either @code{UP} or @code{DOWN}. If @code{staff-affinity} is
2152 @code{CENTER}, then @code{nonstaff-relatedstaff-spacing} is used
2153 for the nearest staves on @emph{both} sides, even if other
2154 non-staff lines appear between the current one and either of the
2155 staves. This means that the placement of a non-staff line depends
2156 on both the surrounding staves and the surrounding non-staff lines.
2157 Setting the @code{stretchability} of one of these types of spacing to
2158 a small value will make that spacing dominate. Setting the
2159 @code{stretchability} to a large value will make that spacing have
2162 @item nonstaff-nonstaff-spacing
2163 The distance between the current non-staff line and the next
2164 non-staff line in the direction of @code{staff-affinity}, if both
2165 are on the same side of the related staff, and
2166 @code{staff-affinity} is either @code{UP} or @code{DOWN}.
2168 @item nonstaff-unrelatedstaff-spacing
2169 The distance between the current non-staff line and the staff in
2170 the opposite direction from @code{staff-affinity}, if there are no
2171 other non-staff lines between the two, and @code{staff-affinity}
2172 is either @code{UP} or @code{DOWN}. This can be used, for
2173 example, to require a minimum amount of padding between a
2174 @code{Lyrics} line and the staff to which it does not belong.
2178 @subsubheading Properties of the @code{StaffGrouper} grob
2180 @code{StaffGrouper} properties are typically adjusted with an
2181 @code{\override} at the @code{StaffGroup} level (or equivalent).
2184 @item staff-staff-spacing
2185 The distance between consecutive staves within the current
2186 staff-group. The @code{staff-staff-spacing} property of an
2187 individual staff's @code{VerticalAxisGroup} grob can be
2188 overriden with different spacing settings for that staff.
2190 @item staffgroup-staff-spacing
2191 The distance between the last staff of the current staff-group and
2192 the staff just below it in the same system, even if one or more
2193 non-staff lines (such as @code{Lyrics}) exist between the two
2194 staves. Does not apply to the bottom staff of a system. The
2195 @code{staff-staff-spacing} property of an individual staff's
2196 @code{VerticalAxisGroup} grob can be overriden with different
2197 spacing settings for that staff.
2202 @ref{Flexible vertical spacing paper variables,,Flexible vertical spacing @code{@bs{}paper} variables},
2203 @ref{Modifying alists}.
2206 @file{ly/engraver-init.ly},
2207 @file{scm/define-grobs.scm}.
2209 Internals Reference:
2210 @rinternals{Contexts},
2211 @rinternals{VerticalAxisGroup},
2212 @rinternals{StaffGrouper}.
2215 @node Spacing of ungrouped staves
2216 @unnumberedsubsubsec Spacing of ungrouped staves
2218 @emph{Staves} (such as @code{Staff}, @code{DrumStaff},
2219 @code{TabStaff}, etc.) are contexts that can contain one or more
2220 voice contexts, but cannot contain any other staves.
2222 The following properties affect the spacing of @emph{ungrouped}
2226 @item @code{VerticalAxisGroup} properties:
2228 @item @code{default-staff-staff-spacing}
2229 @item @code{staff-staff-spacing}
2233 These grob properties are described individually above; see
2234 @ref{Within-system spacing properties}.
2236 Additional properties are involved for staves that are part of a
2237 staff-group; see @ref{Spacing of grouped staves}.
2239 The following example shows how the @code{default-staff-staff-spacing}
2240 property can affect the spacing of ungrouped staves.
2241 The same overrides applied to @code{staff-staff-spacing} would
2242 have the same effect, but would also apply in cases where the staves
2243 are combined in a group or groups.
2245 @lilypond[verbatim,quote,staffsize=16]
2249 \override VerticalAxisGroup.default-staff-staff-spacing =
2250 #'((basic-distance . 8)
2251 (minimum-distance . 7)
2257 % The very low note here needs more room than 'basic-distance
2258 % can provide, so the distance between this staff and the next
2259 % is determined by 'padding.
2260 \new Staff { b,2 r | }
2262 % Here, 'basic-distance provides enough room, and there is no
2263 % need to compress the space (towards 'minimum-distance) to make
2264 % room for anything else on the page, so the distance between
2265 % this staff and the next is determined by 'basic-distance.
2266 \new Staff { \clef bass g2 r | }
2268 % By setting 'padding to a negative value, staves can be made to
2269 % collide. The lowest acceptable value for 'basic-distance is 0.
2271 \override VerticalAxisGroup.default-staff-staff-spacing =
2272 #'((basic-distance . 3.5)
2274 } { \clef bass g2 r | }
2275 \new Staff { \clef bass g2 r | }
2281 @file{scm/define-grobs.scm}.
2286 Internals Reference:
2287 @rinternals{VerticalAxisGroup}.
2290 @node Spacing of grouped staves
2291 @unnumberedsubsubsec Spacing of grouped staves
2293 In orchestral and other large scores, it is common to place staves
2294 in groups. The space between groups is typically larger than the
2295 space between staves of the same group.
2297 @emph{Staff-groups} (such as @code{StaffGroup}, @code{ChoirStaff},
2298 etc.) are contexts that can contain one or more staves
2301 The following properties affect the spacing of staves inside
2305 @item @code{VerticalAxisGroup} properties:
2307 @item @code{staff-staff-spacing}
2309 @item @code{StaffGrouper} properties:
2311 @item @code{staff-staff-spacing}
2312 @item @code{staffgroup-staff-spacing}
2316 These grob properties are described individually above; see
2317 @ref{Within-system spacing properties}.
2319 The following example shows how properties of the
2320 @code{StaffGrouper} grob can affect the spacing of grouped staves:
2322 @lilypond[verbatim,quote,staffsize=16]
2326 \override StaffGrouper.staff-staff-spacing.padding = #0
2327 \override StaffGrouper.staff-staff-spacing.basic-distance = #1
2332 \new PianoStaff \with {
2333 \override StaffGrouper.staffgroup-staff-spacing.basic-distance = #20
2348 @file{scm/define-grobs.scm}.
2353 Internals Reference:
2354 @rinternals{VerticalAxisGroup},
2355 @rinternals{StaffGrouper}.
2358 @node Spacing of non-staff lines
2359 @unnumberedsubsubsec Spacing of non-staff lines
2361 @emph{Non-staff lines} (such as @code{Lyrics}, @code{ChordNames},
2362 etc.) are contexts whose layout objects are engraved like staves
2363 (i.e. in horizontal lines within systems). Specifically,
2364 non-staff lines are non-staff contexts that create the
2365 @code{VerticalAxisGroup} layout object.
2367 The following properties affect the spacing of non-staff lines:
2370 @item @code{VerticalAxisGroup} properties:
2372 @item @code{staff-affinity}
2373 @item @code{nonstaff-relatedstaff-spacing}
2374 @item @code{nonstaff-nonstaff-spacing}
2375 @item @code{nonstaff-unrelatedstaff-spacing}
2379 These grob properties are described individually above; see
2380 @ref{Within-system spacing properties}.
2382 The following example shows how the
2383 @code{nonstaff-nonstaff-spacing} property can affect the spacing
2384 of consecutive non-staff lines. Here, by setting the
2385 @code{stretchability} key to a very high value, the lyrics are
2386 able to stretch much more than usual:
2388 @lilypond[verbatim,quote,staffsize=16]
2392 \override VerticalAxisGroup.nonstaff-nonstaff-spacing.stretchability = #1000
2399 \override VerticalAxisGroup.staff-staff-spacing = #'((basic-distance . 30))
2402 \override VerticalAxisGroup.staff-affinity = #UP
2405 \override VerticalAxisGroup.staff-affinity = #CENTER
2406 } \lyricmode { center }
2408 \override VerticalAxisGroup.staff-affinity = #DOWN
2409 } \lyricmode { down }
2416 @file{ly/engraver-init.ly},
2417 @file{scm/define-grobs.scm}.
2422 @c @lsr{spacing,page-spacing.ly},
2423 @c @lsr{spacing,alignment-vertical-spacing.ly}.
2425 Internals Reference:
2426 @rinternals{Contexts},
2427 @rinternals{VerticalAxisGroup}.
2430 @node Explicit staff and system positioning
2431 @subsection Explicit staff and system positioning
2433 One way to understand the flexible vertical spacing mechanisms
2434 explained above is as a collection of settings that control the
2435 amount of vertical padding between staves and systems.
2437 It is possible to approach vertical spacing in a different way
2438 using @code{NonMusicalPaperColumn.line-break-system-details}.
2439 While the flexible vertical spacing mechanisms specify vertical
2440 padding, @code{NonMusicalPaperColumn.line-break-system-details}
2441 can specify exact vertical positions on the page.
2443 @code{NonMusicalPaperColumn.line-break-system-details} accepts
2444 an associative list of three different settings:
2447 @item @code{X-offset}
2448 @item @code{Y-offset}
2449 @item @code{alignment-distances}
2452 Grob overrides, including the overrides for @code{NonMusicalPaperColumn}
2453 below, can occur in any of three different places in an input file:
2456 @item in the middle of note entry directly
2457 @item in a @code{\context} block
2458 @item in the @code{\with} block
2461 When we override @code{NonMusicalPaperColumn}, we use the usual
2462 @code{\override} command in @code{\context} blocks and in the
2463 @code{\with} block. On the other hand, when we override
2464 @code{NonMusicalPaperColumn} in the middle of note entry,
2465 use the special @code{\overrideProperty} command. Here are some
2466 example @code{NonMusicalPaperColumn} overrides with the special
2467 @code{\overrideProperty} command:
2470 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2473 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2476 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2480 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2481 #'((alignment-distances . (15)))
2483 \overrideProperty NonMusicalPaperColumn.line-break-system-details
2486 (alignment-distances . (15)))
2489 To understand how each of these different settings work, we begin
2490 by looking at an example that includes no overrides at all.
2492 @c \book { } is required in these examples to ensure the spacing
2493 @c overrides can be seen between systems. -np
2495 @lilypond[verbatim,quote,staffsize=16]
2496 \header { tagline = ##f }
2497 \paper { left-margin = 0\mm }
2507 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2510 \repeat unfold 15 { d'4 d' d' d' }
2517 This score isolates line- and page-breaking information in a dedicated
2518 voice. This technique of creating a breaks voice will help keep layout
2519 separate from music entry as our example becomes more complicated.
2520 See @ref{Using an extra voice for breaks}.
2522 Explicit @code{\breaks} evenly divide the music into six measures per
2523 line. Vertical spacing results from LilyPond's defaults. To set
2524 the vertical startpoint of each system explicitly, we can set
2525 the @code{Y-offset} pair in the @code{line-break-system-details}
2526 attribute of the @code{NonMusicalPaperColumn} grob:
2528 @lilypond[verbatim,quote,staffsize=16]
2529 \header { tagline = ##f }
2530 \paper { left-margin = 0\mm }
2536 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2539 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2542 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2546 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2549 \repeat unfold 15 { d'4 d' d' d' }
2556 Note that @code{line-break-system-details} takes an associative list of
2557 potentially many values, but that we set only one value here. Note,
2558 too, that the @code{Y-offset} property here determines the exact vertical
2559 position on the page at which each new system will render.
2561 Now that we have set the vertical startpoint of each system
2562 explicitly, we can also set the vertical distances between staves
2563 within each system manually. We do this using the @code{alignment-distances}
2564 subproperty of @code{line-break-system-details}.
2566 @lilypond[verbatim,quote,staffsize=16]
2567 \header { tagline = ##f }
2568 \paper { left-margin = 0\mm }
2574 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2576 (alignment-distances . (10)))
2578 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2580 (alignment-distances . (15)))
2582 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2584 (alignment-distances . (20)))
2587 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2590 \repeat unfold 15 { d'4 d' d' d' }
2597 Note that here we assign two different values to the
2598 @code{line-break-system-details} attribute of the
2599 @code{NonMusicalPaperColumn} grob. Though the
2600 @code{line-break-system-details} attribute alist accepts many
2601 additional spacing parameters (including, for example, a corresponding
2602 @code{X-offset} pair), we need only set the @code{Y-offset} and
2603 @code{alignment-distances} pairs to control the vertical startpoint of
2604 every system and every staff. Finally, note that @code{alignment-distances}
2605 specifies the vertical positioning of staves but not of staff groups.
2607 @lilypond[verbatim,quote,staffsize=16]
2608 \header { tagline = ##f }
2609 \paper { left-margin = 0\mm }
2615 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2617 (alignment-distances . (30 10)))
2619 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2621 (alignment-distances . (10 10)))
2623 \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details
2625 (alignment-distances . (10 30)))
2628 \new Voice { \repeat unfold 15 { c'4 c' c' c' } }
2631 \new Staff { \repeat unfold 15 { d'4 d' d' d' } }
2632 \new Staff { \repeat unfold 15 { e'4 e' e' e' } }
2639 Some points to consider:
2642 @item When using @code{alignment-distances}, lyrics and other non-staff lines
2643 do not count as a staff.
2645 @item The units of the numbers passed to @code{X-offset},
2646 @code{Y-offset} and @code{alignment-distances} are interpreted as multiples
2647 of the distance between adjacent staff lines. Positive values move staves
2648 and lyrics up, negative values move staves and lyrics down.
2650 @item Because the @code{NonMusicalPaperColumn.line-break-system-details}
2651 settings given here allow the positioning of staves and systems anywhere
2652 on the page, it is possible to violate paper or margin boundaries or even
2653 to print staves or systems on top of one another. Reasonable values
2654 passed to these different settings will avoid this.
2662 @node Vertical collision avoidance
2663 @subsection Vertical collision avoidance
2665 @funindex outside-staff-priority
2666 @funindex outside-staff-padding
2667 @funindex outside-staff-horizontal-padding
2669 Intuitively, there are some objects in musical notation that belong
2670 to the staff and there are other objects that should be placed outside
2671 the staff. Objects belonging outside the staff include things such as
2672 rehearsal marks, text and dynamic markings (from now on, these will
2673 be called outside-staff objects). LilyPond's rule for the
2674 vertical placement of outside-staff objects is to place them as close
2675 to the staff as possible but not so close that they collide with
2678 LilyPond uses the @code{outside-staff-priority} property to determine
2679 whether a grob is an outside-staff object: if @code{outside-staff-priority}
2680 is a number, the grob is an outside-staff object. In addition,
2681 @code{outside-staff-priority} tells LilyPond in which order the objects
2684 First, LilyPond places all the objects that do not belong outside
2685 the staff. Then it sorts the outside-staff objects according to their
2686 @code{outside-staff-priority} (in increasing order). One by one, LilyPond
2687 takes the outside-staff objects and places them so that they do
2688 not collide with any objects that have already been placed. That
2689 is, if two outside-staff grobs are competing for the same space, the one
2690 with the lower @code{outside-staff-priority} will be placed closer to
2693 @lilypond[quote,ragged-right,relative=2,verbatim]
2696 \once \override TextScript.outside-staff-priority = #1
2697 c4_"Text"\pp % this time the text will be closer to the staff
2699 % by setting outside-staff-priority to a non-number,
2700 % we disable the automatic collision avoidance
2701 \once \override TextScript.outside-staff-priority = ##f
2702 \once \override DynamicLineSpanner.outside-staff-priority = ##f
2703 c4_"Text"\pp % now they will collide
2706 The vertical padding around outside-staff objects
2707 can be controlled with @code{outside-staff-padding}.
2709 @lilypond[quote,ragged-right,relative=2,verbatim,staffsize=18]
2710 \once \override TextScript.outside-staff-padding = #0
2711 a4-"outside-staff-padding = #0"
2712 \once \override TextScript.outside-staff-padding = #3
2713 d-"outside-staff-padding = #3"
2714 c-"default outside-staff-padding"
2715 b-"default outside-staff-padding"
2720 By default, outside-staff objects are placed so they avoid
2721 a horizontal collision with previously-positioned grobs. This
2722 can lead to situations in which objects are placed close to each
2724 As shown in the example below, setting @code{outside-staff-horizontal-padding}
2725 increases the horizontal spacing required, and in this case moves the text up
2726 to prevent it from getting too close to the ledger lines.
2728 @lilypond[quote,ragged-right,relative=2,verbatim]
2731 \once \override TextScript.outside-staff-horizontal-padding = #1
2740 @node Horizontal spacing
2741 @section Horizontal spacing
2743 @cindex horizontal spacing
2744 @cindex spacing, horizontal
2747 * Horizontal spacing overview::
2748 * New spacing area::
2749 * Changing horizontal spacing::
2751 * Proportional notation::
2755 @node Horizontal spacing overview
2756 @subsection Horizontal spacing overview
2758 The spacing engine translates differences in durations into stretchable
2759 distances (@q{springs}) of differing lengths. Longer durations get
2760 more space, shorter durations get less. The shortest durations get a
2761 fixed amount of space (which is controlled by
2762 @code{shortest-duration-space} in the @rinternals{SpacingSpanner}
2763 object). The longer the duration, the more space it gets: doubling a
2764 duration adds @code{spacing-increment} of space to the note.
2766 For example, the following piece contains lots of half, quarter, and
2767 8th notes; the eighth note is followed by 1 note head width (NHW).
2768 The quarter note is followed by 2 NHW, the half by 3 NHW, etc.
2770 @lilypond[quote,verbatim,relative=1]
2776 Normally, @code{spacing-increment} is set to 1.2 staff space, which is
2777 approximately the width of a note head, and
2778 @code{shortest-duration-space} is set to 2.0, meaning that the
2779 shortest note gets 2.4 staff space (2.0 times the
2780 @code{spacing-increment}) of horizontal space. This space is counted
2781 from the left edge of the symbol, so the shortest notes are generally
2782 followed by one NHW of space.
2784 If one would follow the above procedure exactly, then adding a single
2785 32nd note to a score that uses 8th and 16th notes, would widen up the
2786 entire score a lot. The shortest note is no longer a 16th, but a 32nd,
2787 thus adding 1 NHW to every note. To prevent this, the shortest
2788 duration for spacing is not the shortest note in the score, but rather
2789 the one which occurs most frequently.
2792 The most common shortest duration is determined as follows: in every
2793 measure, the shortest duration is determined. The most common shortest
2794 duration is taken as the basis for the spacing, with the stipulation
2795 that this shortest duration should always be equal to or shorter than
2796 an 8th note. The shortest duration is printed when you run
2797 @code{lilypond} with the @option{--verbose} option.
2799 These durations may also be customized. If you set the
2800 @code{common-shortest-duration} in @rinternals{SpacingSpanner}, then
2801 this sets the base duration for spacing. The maximum duration for this
2802 base (normally an 8th), is set through @code{base-shortest-duration}.
2804 @funindex common-shortest-duration
2805 @funindex base-shortest-duration
2806 @funindex stem-spacing-correction
2809 Notes that are even shorter than the common shortest note are
2810 followed by a space that is proportional to their duration relative to
2811 the common shortest note. So if we were to add only a few 16th notes
2812 to the example above, they would be followed by half a NHW:
2814 @lilypond[quote,verbatim,relative=2]
2815 c2 c4. c8 | c4. c16[ c] c4. c8 | c8 c c4 c c
2819 In the @emph{Essay on automated music engraving}, it was explained
2820 that stem directions influence spacing (see
2821 @ressay{Optical spacing}). This is controlled with the
2822 @code{stem-spacing-correction} property in the
2823 @rinternals{NoteSpacing}, object. These are generated for every
2824 @rinternals{Voice} context. The @code{StaffSpacing} object
2825 (generated in @rinternals{Staff} context) contains the same
2826 property for controlling the stem/bar line spacing. The following
2827 example shows these corrections, once with default settings, and
2828 once with exaggerated corrections:
2830 @lilypond[quote,ragged-right]
2834 \override Staff.NoteSpacing.stem-spacing-correction = #1.5
2835 \override Staff.StaffSpacing.stem-spacing-correction = #1.5
2841 Proportional notation is supported; see @ref{Proportional notation}.
2844 Essay on automated music engraving:
2845 @ressay{Optical spacing}.
2850 Internals Reference:
2851 @rinternals{SpacingSpanner},
2852 @rinternals{NoteSpacing},
2853 @rinternals{StaffSpacing},
2854 @rinternals{NonMusicalPaperColumn}.
2857 There is no convenient mechanism to manually override spacing. The
2858 following work-around may be used to insert extra space into a score,
2859 adjusting the padding value as necessary.
2862 \override Score.NonMusicalPaperColumn.padding = #10
2865 No work-around exists for decreasing the amount of space.
2868 @node New spacing area
2869 @subsection New spacing area
2871 @funindex \newSpacingSection
2872 @cindex new spacing area
2873 @cindex spacing area, new
2874 @cindex notes, spacing horizontally
2876 New sections with different spacing parameters can be started with
2877 @code{newSpacingSection}. This is useful when there are
2878 sections with a different notions of long and short notes.
2880 In the following example, the time signature change introduces a new
2881 section, and hence the 16ths notes are automatically spaced slightly
2884 @lilypond[relative=1,verbatim,quote]
2887 c8 c c4 c16[ c c8] c4
2893 The @code{\newSpacingSection} command creates a new
2894 @code{SpacingSpanner} object at that musical moment.
2895 If the automatic spacing adjustments do not give the required spacing,
2896 manual @code{\override}s may be applied to its properties. These must
2897 be applied at the same musical moment as the @code{\newSpacingSection}
2898 command itself. They will then affect the spacing of all the following
2899 music until the properties are changed in a new spacing section, for
2902 @lilypond[relative=1,verbatim,quote]
2906 \override Score.SpacingSpanner.spacing-increment = #2
2909 \revert Score.SpacingSpanner.spacing-increment
2918 Internals Reference:
2919 @rinternals{SpacingSpanner}.
2922 @node Changing horizontal spacing
2923 @subsection Changing horizontal spacing
2925 Horizontal spacing may be altered with the
2926 @code{base-shortest-duration} property. Here
2927 we compare the same music; once without altering
2928 the property, and then altered. Larger values
2929 of @code{ly:make-moment} will produce smaller
2930 music. Note that @code{ly:make-moment} constructs
2931 a duration, so @code{1 4} is a longer duration
2934 @lilypond[verbatim,line-width=12\cm]
2937 g4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2938 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2939 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2940 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2945 @lilypond[verbatim,line-width=12\cm]
2948 g4 e e2 | f4 d d2 | c4 d e f | g4 g g2 |
2949 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2950 d4 d d d | d4 e f2 | e4 e e e | e4 f g2 |
2951 g4 e e2 | f4 d d2 | c4 e g g | c,1 |
2956 \override SpacingSpanner.base-shortest-duration = #(ly:make-moment 1/16)
2965 By default, spacing in tuplets depends on various non-duration
2966 factors (such as accidentals, clef changes, etc). To disregard
2967 such symbols and force uniform equal-duration spacing, use
2968 @code{Score.SpacingSpanner.uniform-stretching}. This
2969 property can only be changed at the beginning of a score,
2971 @lilypond[quote,ragged-right,verbatim]
2975 \tuplet 5/4 { c8 c c c c } c8 c c c
2978 c8 c c c \tuplet 5/4 { c8 c c c c }
2984 \override SpacingSpanner.uniform-stretching = ##t
2990 When @code{strict-note-spacing} is set, notes are spaced without
2991 regard for clefs, bar lines, and grace notes,
2993 @lilypond[quote,ragged-right,relative=2,verbatim]
2994 \override Score.SpacingSpanner.strict-note-spacing = ##t
2995 \new Staff { c8[ c \clef alto c \grace { c16 c } c8 c c] c32[ c] }
3004 @subsection Line length
3007 @cindex breaking pages
3010 @funindex line-width
3011 @funindex ragged-right
3012 @funindex ragged-last
3014 @c Although line-width can be set in \layout, it should be set in paper
3015 @c block, to get page layout right.
3016 @c Setting indent in \paper block makes not much sense, but it works.
3018 @c Bit verbose and vague, use examples?
3019 The most basic settings influencing the spacing are @code{indent} and
3020 @code{line-width}. They are set in the @code{\layout} block. They
3021 control the indentation of the first line of music, and the lengths of
3024 If @code{ragged-right} is set to true in the @code{\layout} block, then
3025 systems ends at their natural horizontal length, instead of being spread
3026 horizontally to fill the whole line. This is useful for
3027 short fragments, and for checking how tight the natural spacing is.
3028 The normal default setting is false, but if the score has only one
3029 system the default value is true.
3032 @cindex vertical spacing
3034 The option @code{ragged-last} is similar to @code{ragged-right}, but
3035 only affects the last line of the piece. No restrictions are put on
3036 that line. The result is similar to formatting text paragraphs. In a
3037 paragraph, the last line simply takes its natural horizontal length.
3038 @c Note that for text there are several options for the last line.
3039 @c While Knuth TeX uses natural length, lead typesetters use the same
3040 @c stretch as the previous line. eTeX uses \lastlinefit to
3041 @c interpolate between both these solutions.
3056 @node Proportional notation
3057 @subsection Proportional notation
3059 LilyPond supports proportional notation, a type of horizontal spacing
3060 in which each note consumes an amount of horizontal space exactly
3061 equivalent to its rhythmic duration. This type of proportional spacing
3062 is comparable to horizontal spacing on top of graph paper. Some late
3063 20th- and early 21st-century scores use proportional notation to
3064 clarify complex rhythmic relationships or to facilitate the placement
3065 of timelines or other graphics directly in the score.
3067 LilyPond supports five different settings for proportional notation,
3068 which may be used together or alone:
3071 @item @code{proportionalNotationDuration}
3072 @item @code{uniform-stretching}
3073 @item @code{strict-note-spacing}
3074 @item @code{\remove "Separating_line_group_engraver"}
3075 @item @code{\override PaperColumn.used = ##t}
3078 In the examples that follow, we explore these five different
3079 proportional notation settings and examine how these settings interact.
3081 We start with the following one-measure example, which uses classical
3082 spacing with ragged-right turned on.
3084 @c The initial pitch is not necessary as long as RhythmicStaff is
3085 @c not preceded by other material in the score, but we don't want
3087 @lilypond[quote,verbatim,ragged-right]
3090 \new RhythmicStaff {
3091 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3097 Notice that the half note which begins the measure takes up far less
3098 than half of the horizontal space of the measure. Likewise, the
3099 sixteenth notes and sixteenth-note quintuplets (or twentieth notes)
3100 which end the measure together take up far more than half the
3101 horizontal space of the measure.
3103 In classical engraving, this spacing may be exactly what we want
3104 because we can borrow horizontal space from the half note and conserve
3105 horizontal space across the measure as a whole.
3107 On the other hand, if we want to insert a measured timeline or other
3108 graphic above or below our score, we need proportional notation. We
3109 turn proportional notation on with the proportionalNotationDuration
3112 @lilypond[quote,verbatim,ragged-right]
3115 \new RhythmicStaff {
3116 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3122 proportionalNotationDuration = #(ly:make-moment 1/20)
3128 The half note at the beginning of the measure and the faster notes in
3129 the second half of the measure now occupy equal amounts of horizontal
3130 space. We could place a measured timeline or graphic above or below
3133 The @code{proportionalNotationDuration} setting is a context setting
3134 that lives in @code{Score}. Remember that context settings can appear
3135 in one of three locations within our input file -- in a @code{\with}
3136 block, in a @code{\context} block, or directly in music entry preceded
3137 by the @code{\set} command. As with all context settings, users can
3138 pick which of the three different locations they would like to
3139 set @code{proportionalNotationDuration} in to.
3141 The @code{proportionalNotationDuration} setting takes a single argument,
3142 which is the reference duration against that all music will be spaced.
3143 The LilyPond Scheme function @code{make-moment} takes two arguments
3144 -- a numerator and denominator which together express some fraction of
3145 a whole note. The call @code{(ly:make-moment 1/20)} therefore produces
3146 a reference duration of a twentieth note. Values such as
3147 @code{(ly:make-moment 1/16)}, @code{(ly:make-moment 1/8)}, and
3148 @code{(ly:make-moment 3/97)} are all possible as well.
3150 How do we select the right reference duration to pass to
3151 @code{proportionalNotationDuration}? Usually by a process of trial
3152 and error, beginning with a duration close to the fastest (or smallest)
3153 duration in the piece. Smaller reference durations space music loosely;
3154 larger reference durations space music tightly.
3156 @lilypond[quote,verbatim,ragged-right]
3159 \new RhythmicStaff {
3160 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3166 proportionalNotationDuration = #(ly:make-moment 1/8)
3173 \new RhythmicStaff {
3174 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3180 proportionalNotationDuration = #(ly:make-moment 1/16)
3187 \new RhythmicStaff {
3188 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3194 proportionalNotationDuration = #(ly:make-moment 1/32)
3200 Note that too large a reference duration -- such as the eighth note,
3201 above -- spaces music too tightly and can cause note head collisions.
3202 Also that proportional notation in general takes up more horizontal
3203 space than classical spacing. Proportional spacing provides rhythmic
3204 clarity at the expense of horizontal space.
3206 Next we examine how to optimally space overlapping tuplets.
3208 We start by examining what happens to our original example, with
3209 classical spacing, when we add a second staff with a different type of
3212 @lilypond[quote,verbatim,ragged-right]
3215 \new RhythmicStaff {
3216 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3218 \new RhythmicStaff {
3219 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3225 The spacing is bad because the evenly spaced notes of the bottom staff
3226 do not stretch uniformly. Classical engravings include very few complex
3227 triplets and so classical engraving rules can generate this type of
3228 result. Setting @code{proportionalNotationDuration} fixes this.
3230 @lilypond[quote,verbatim,ragged-right]
3233 \new RhythmicStaff {
3234 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3236 \new RhythmicStaff {
3237 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3243 proportionalNotationDuration = #(ly:make-moment 1/20)
3249 But if we look very carefully we can see that notes of the second half
3250 of the 9-tuplet space ever so slightly more widely than the notes
3251 of the first half of the 9-tuplet. To ensure uniform stretching, we
3252 turn on @code{uniform-stretching}, which is a property of
3253 @code{SpacingSpanner}.
3255 @lilypond[quote,verbatim,ragged-right]
3258 \new RhythmicStaff {
3259 c2 16 16 16 16 \tuplet 5/4 { 16 16 16 16 16 }
3261 \new RhythmicStaff {
3262 \tuplet 9/8 { c8 8 8 8 8 8 8 8 8 }
3268 proportionalNotationDuration = #(ly:make-moment 1/20)
3269 \override SpacingSpanner.uniform-stretching = ##t
3275 Our two-staff example now spaces exactly, our rhythmic
3276 relationships are visually clear, and we can include a measured
3277 timeline or graphic if we want.
3279 Note that the LilyPond's proportional notation package expects
3280 that all proportional scores set the SpacingSpanner's
3281 'uniform-stretching attribute to ##t. Setting
3282 proportionalNotationDuration without also setting the
3283 SpacingSpanner's 'uniform-stretching attribute to ##t will, for
3284 example, cause Skips to consume an incorrect amount of horizontal
3287 The SpacingSpanner is an abstract grob that lives in the Score
3288 context. As with our settings of proportionalNotationDuration,
3289 overrides to the SpacingSpanner can occur in any of three
3290 different places in our input file – in the Score \with block, in
3291 a Score \context block, or in note entry directly.
3293 There is by default only one @code{SpacingSpanner} per @code{Score}. This
3294 means that, by default, @code{uniform-stretching} is either turned on for the
3295 entire score or turned off for the entire score. We can, however,
3296 override this behavior and turn on different spacing features at
3297 different places in the score. We do this with the command
3298 @code{\newSpacingSection}. See @ref{New spacing area}, for more info.
3300 Next we examine the effects of the @code{Separating_line_group_engraver} and
3301 see why proportional scores frequently remove this engraver. The following
3302 example shows that there is a small amount of @qq{prefatory} space
3303 just before the first note in each system.
3305 @lilypond[quote,verbatim,ragged-right]
3318 The amount of this prefatory space is the same whether after a time
3319 signature, a key signature or a clef. @code{Separating_line_group_engraver}
3320 is responsible for this space. Removing @code{Separating_line_group_engraver}
3321 reduces this space to zero.
3323 @lilypond[quote,verbatim,ragged-right]
3329 \remove "Separating_line_group_engraver"
3337 non-musical elements like time signatures, key signatures, clefs and
3338 accidentals are problematic in proportional notation. None of these
3339 elements has rhythmic duration. But all of these elements consume
3340 horizontal space. Different proportional scores approach these
3341 problems differently.
3343 It may be possible to avoid spacing problems with key signatures
3344 simply by not having any. This is a valid option since most
3345 proportional scores are contemporary music. The same may be true
3346 of time signatures, especially for those scores
3347 that include a measured timeline or other graphic. But these scores
3348 are exceptional and most proportional scores include at least some
3349 time signatures. Clefs and accidentals are even more essential.
3351 So what strategies exist for spacing non-musical elements in a
3352 proportional context? One good option is the @code{strict-note-spacing}
3353 property of @code{SpacingSpanner}. Compare the two scores below:
3355 @lilypond[quote,verbatim,ragged-right]
3357 \set Score.proportionalNotationDuration = #(ly:make-moment 1/16)
3358 c''8 8 8 \clef alto d'2 2
3362 \set Score.proportionalNotationDuration = #(ly:make-moment 1/16)
3363 \override Score.SpacingSpanner.strict-note-spacing = ##t
3364 c''8 8 8 \clef alto d'2 2
3368 Both scores are proportional, but the spacing in the first score
3369 is too loose because of the clef change. The spacing of the second
3370 score remains strict, however, because strict-note-spacing is
3371 turned on. Turning on strict-note-spacing causes the width of
3372 time signatures, key signatures, clefs and accidentals to play no
3373 part in the spacing algorithm.
3375 In addition to the settings given here, there are other settings
3376 that frequently appear in proportional scores. These include:
3379 @item @code{\override SpacingSpanner.strict-grace-spacing = ##t}
3380 @item @code{\set tupletFullLength = ##t}
3381 @item @code{\override Beam.breakable = ##t}
3382 @item @code{\override Glissando.breakable = ##t}
3383 @item @code{\override TextSpanner.breakable = ##t}
3384 @item @code{\remove "Forbid_line_break_engraver" in the Voice context}
3387 These settings space grace notes strictly, extend tuplet brackets to
3388 mark both rhythmic start- and stop-points, and allow spanning elements
3389 to break across systems and pages. See the respective parts of the manual
3390 for these related settings.
3394 @ref{New spacing area}.
3400 @node Fitting music onto fewer pages
3401 @section Fitting music onto fewer pages
3403 Sometimes you can end up with one or two staves on a second
3404 (or third, or fourth@dots{}) page. This is annoying, especially
3405 if you look at previous pages and it looks like there is plenty
3406 of room left on those.
3408 When investigating layout issues, @code{annotate-spacing} is an
3409 invaluable tool. This command prints the values of various layout
3410 spacing variables; for more details see the following section,
3411 @ref{Displaying spacing}.
3414 * Displaying spacing::
3415 * Changing spacing::
3419 @node Displaying spacing
3420 @subsection Displaying spacing
3422 @funindex annotate-spacing
3423 @cindex spacing, display of layout
3425 To graphically display the dimensions of vertical layout variables
3426 that may be altered for page formatting, set
3427 @code{annotate-spacing} in the @code{\paper} block:
3429 @lilypond[verbatim,quote,papersize=a6landscape]
3432 \paper { annotate-spacing = ##t }
3438 All layout dimensions are displayed in staff-spaces, regardless
3439 of the units specified in the @code{\paper} or @code{\layout} block.
3440 In the above example, @code{paper-height} has a value of 59.75
3441 @code{staff-spaces}, and the @code{staff-size} is 20 points (the
3442 default value). Note that:
3444 @multitable {1 staff-space} {staff-size)/4 * (25.4/72.27) mm}
3447 @tab = (25.4/72.27) mm
3450 @tab = (@code{staff-size})/4 pts
3452 @tab = (@code{staff-size})/4 * (25.4/72.27) mm
3457 In this case, one @code{staff-space} is approximately equal to
3458 1.757mm. Thus the @code{paper-height} measurement of 59.75
3459 @code{staff-spaces} is equivalent to 105 millimeters, the height
3460 of @code{a6} paper in landscape orientation. The pairs
3461 (@var{a},@var{b}) are intervals, where @var{a} is the lower
3462 edge and @var{b} the upper edge of the interval.
3466 @ref{Setting the staff size}.
3472 @node Changing spacing
3473 @subsection Changing spacing
3475 The output of @code{annotate-spacing} reveals vertical dimensions
3476 in great detail. For details about modifying margins and other
3477 layout variables, see @ref{Page layout}.
3479 Other than margins, there are a few other options to save space:
3483 Force systems to move as close together as possible (to fit as
3484 many systems as possible onto a page) while being spaced so that
3485 there is no blank space at the bottom of the page.
3489 system-system-spacing = #'((basic-distance . 0.1) (padding . 0))
3490 ragged-last-bottom = ##f
3496 Force the number of systems. This can help in two ways. Just
3497 setting a value, even the same value as the number of systems
3498 being typeset by default, will sometimes cause more systems to
3499 be fitted onto each page, as an estimation step is then bypassed,
3500 giving a more accurate fit to each page. Also, forcing an actual
3501 reduction in the number of systems may save a further page. For
3502 example, if the default layout has 11 systems, the following
3503 assignment will force a layout with 10 systems.
3512 Force the number of pages. For example, the following
3513 assignment will force a layout with 2 pages.
3522 Avoid (or reduce) objects that increase the vertical size of a
3523 system. For example, volta repeats (or alternate repeats) require
3524 extra space. If these repeats are spread over two systems, they
3525 will take up more space than one system with the volta repeats and
3526 another system without. For example, dynamics that @q{stick out} of
3527 a system can be moved closer to the staff:
3529 @lilypond[verbatim,quote,relative=1]
3531 e4 c g-\tweak X-offset #-2.7 \f c
3535 Alter the horizontal spacing via @code{SpacingSpanner}. For more
3536 details, see @ref{Changing horizontal spacing}. The following
3537 example illustrates the default spacing:
3539 @lilypond[verbatim,quote]
3552 The next example modifies @code{common-shortest-duration} from a
3553 value of @code{1/4} to @code{1/2}. The quarter note is the most
3554 common and shortest duration in this example, so by making this
3555 duration longer, a @q{squeezing} effect occurs:
3557 @lilypond[verbatim,quote]
3569 \override SpacingSpanner.common-shortest-duration =
3570 #(ly:make-moment 1/2)
3577 The @code{common-shortest-duration} property cannot be modified
3578 dynamically, so it must always be placed in a @code{\context}
3579 block so that it applies to the whole score.
3586 @ref{Changing horizontal spacing}.