1 @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. See TRANSLATION for details.
14 @lilypondfile[quote]{rhythms-headword.ly}
16 This section discusses rhythms, rests, durations, beaming and bars.
21 * Displaying rhythms::
24 * Special rhythmic concerns::
29 @subsection Writing rhythms
39 @unnumberedsubsubsec Durations
41 @cindex durations, of notes
42 @cindex note durations
43 @cindex length of notes
53 Durations are designated by numbers and dots. Durations are entered
54 as their reciprocal values. For example, a quarter note is entered
55 using a @code{4} (since it is a 1/4 note), and a half note is entered
56 using a @code{2} (since it is a 1/2 note). For notes longer than a
57 whole you must use the @code{\longa} (a double breve) and
58 @code{\breve} commands. Durations as short as 128th notes may be
59 specified. Shorter values are possible, but only as beamed notes.
61 @c Two 64th notes are needed to obtain beams
62 @lilypond[quote,verbatim,relative=2]
65 c4 c8 c16 c32 c64 c128 c128
68 Here are the same durations with automatic beaming turned off.
70 @c not strictly "writing rhythms"; more of a "displaying" thing,
71 @c but it's ok here. -gp
72 @lilypond[quote,verbatim,relative=2]
76 c4 c8 c16 c32 c64 c128 c128
79 A note with the duration of a quadruple breve may be entered with
80 @code{\maxima}, but this is supported only within ancient music
81 notation. For details, see @ref{Ancient notation}.
83 @cindex duration, default
84 @cindex default note duration
85 @cindex note duration, default
87 If the duration is omitted, it is set to the previously
88 entered duration. The default for the first note is a quarter
91 @lilypond[quote,verbatim,relative=2]
97 @cindex notes, double-dotted
98 @cindex double-dotted notes
102 To obtain dotted note lengths, place a dot (@code{.}) after the
103 duration. Double-dotted notes are specified by appending two
106 @lilypond[quote,verbatim,relative=2]
107 a4 b c4. b8 a4. b4.. c8.
110 Some durations cannot be represented with just binary durations
111 and dots; they can be represented only by tying two or more
112 notes together. For details, see @ref{Ties}.
114 For ways of specifying durations for the syllables of lyrics and
115 ways of aligning lyrics to notes, see @ref{Vocal music}.
117 Optionally, notes can be spaced strictly proportionately to their
118 duration. For details of this and other settings which control
119 proportional notation, see @ref{Proportional notation}.
125 @funindex \dotsNeutral
126 @funindex dotsNeutral
128 Dots are normally moved up to avoid staff lines, except in
129 polyphonic situations. Dots may be manually placed above or below
130 the staff; see @ref{Direction and placement}.
148 @rglos{Duration names notes and rests}.
151 @ref{Automatic beams},
154 @ref{Writing rhythms},
157 @ref{Ancient notation},
158 @ref{Proportional notation}.
165 @rinternals{DotColumn}.
170 @c Deliberately duplicated in Durations and Rests. -gp
171 There is no fundamental limit to rest durations (both in terms of
172 longest and shortest), but the number of glyphs is limited:
173 rests from 128th to maxima (8 x whole) may be printed.
177 @unnumberedsubsubsec Tuplets
185 Tuplets are made from a music expression by multiplying all the
186 durations with a fraction:
189 \times @var{fraction} @{ @var{music} @}
193 The duration of @var{music} will be multiplied by the
194 fraction. The fraction's denominator will be printed over or
195 under the notes, optionally with a bracket. The most common
196 tuplet is the triplet in which 3 notes have the duration of 2, so
197 the notes are 2/3 of their written length.
199 @lilypond[quote,verbatim,relative=2]
200 a2 \times 2/3 { b4 b b }
201 c4 c \times 2/3 { b4 a g }
204 @cindex tuplet bracket placement
208 @funindex \tupletDown
210 @funindex \tupletNeutral
211 @funindex tupletNeutral
213 Tuplet brackets may be manually placed above or below the staff;
214 see @ref{Direction and placement}.
216 Tuplets may be nested:
218 @lilypond[quote,verbatim,relative=2]
220 c4 \times 4/5 { f8 e f \times 2/3 { e[ f g] } } f4 |
223 Modifying nested tuplets which begin at the same musical moment
224 must be done with @code{\tweak}.
226 To modify the duration of notes without printing a tuplet bracket,
227 see @ref{Scaling durations}.
233 @code{\tupletNeutral}.
239 @cindex tuplet formatting
240 @cindex triplet formatting
242 @funindex tupletNumberFormatFunction
243 @funindex tupletSpannerDuration
245 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
246 {entering-several-tuplets-using-only-one--times-command.ly}
248 @cindex Tuplet number changes
250 @funindex TupletNumber
252 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
253 {changing-the-tuplet-number.ly}
255 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
256 {non-default-tuplet-numbers.ly}
258 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
259 {permitting-line-breaks-within-beamed-tuplets.ly}
269 @rlearning{Tweaking methods}.
272 @ref{Time administration},
273 @ref{Scaling durations},
274 @ref{The tweak command},
275 @ref{Polymetric notation}.
281 @rinternals{TupletBracket},
282 @rinternals{TupletNumber},
283 @rinternals{TimeScaledMusic}.
286 @cindex grace notes within tuplet brackets
289 When the first note on a staff is a grace note followed by a
290 tuplet the grace note must be placed before the @code{\times}
291 command to avoid errors. Anywhere else, grace notes may be
292 placed within tuplet brackets.
295 @node Scaling durations
296 @unnumberedsubsubsec Scaling durations
298 @cindex scaling durations
299 @cindex durations, scaling
301 You can alter the duration of single notes, rests or chords by a
302 fraction @code{N/M} by appending @code{*N/M} (or @code{*N} if @code{M}
303 is 1) to the duration. This will not affect the appearance of the
304 notes or rests produced, but the altered duration will be used in
305 calculating the position within the measure and setting the duration
306 in the MIDI output. Multiplying factors may be combined such as
309 In the following example, the first three notes take up exactly
310 two beats, but no triplet bracket is printed.
312 @lilypond[quote,relative=2,verbatim]
314 % Alter durations to triplets
315 a4*2/3 gis4*2/3 a4*2/3
318 % Double the duration of chord
320 % Duration of quarter, appears like sixteenth
324 The duration of skip or spacing notes may also be modified by
325 a multiplier. This is useful for skipping many measures, e.g.,
328 @cindex compressing music
329 @cindex expanding music
331 @funindex \scaleDurations
332 @funindex scaleDurations
334 Longer stretches of music may be compressed by a fraction in the
335 same way, as if every note, chord or rest had the fraction as a
336 multiplier. This leaves the appearance of the music unchanged but
337 the internal duration of the notes will be multiplied by the
338 fraction @emph{num}/@emph{den}. The spaces around the dot are
339 required. Here is an example showing how music can be compressed
342 @lilypond[quote,relative=2,verbatim]
346 % Scale music by *2/3
347 \scaleDurations #'(2 . 3) {
351 \scaleDurations #'(2 . 1) {
356 One application of this command is in polymetric
357 notation, see @ref{Polymetric notation}.
363 @ref{Invisible rests},
364 @ref{Polymetric notation}.
371 @unnumberedsubsubsec Ties
377 A tie connects two adjacent note heads of the same pitch. The tie
378 in effect extends the duration of a note.
380 @warning{Ties should not be confused with @emph{slurs}, which
381 indicate articulation, or @emph{phrasing slurs}, which indicate
382 musical phrasing. A tie is just a way of extending a note
383 duration, similar to the augmentation dot.}
385 A tie is entered using the tilde symbol (@code{~}).
387 @lilypond[quote,verbatim,relative=2]
391 Ties are used either when the note crosses a bar line, or when
392 dots cannot be used to denote the rhythm. Ties should also be
393 used when note values cross larger subdivisions of the measure:
395 @lilypond[verbatim,quote]
402 If you need to tie many notes across bar lines, it may be
403 easier to use automatic note splitting, see @ref{Automatic note
404 splitting}. This mechanism automatically splits long notes, and
405 ties them across bar lines.
407 @cindex ties and chords
408 @cindex chords and ties
410 When a tie is applied to a chord, all note heads whose pitches
411 match are connected. When no note heads match, no ties will be
412 created. Chords may be partially tied by placing the tie inside
415 @lilypond[quote,verbatim,relative=1]
417 <c~ e g~ b> <c e g b>
420 @cindex repeating ties
421 @cindex ties, repeating
422 @cindex volta brackets and ties
423 @cindex ties and volta brackets
428 When a second alternative of a repeat starts with a tied note, you
429 have to specify the repeated tie as follows:
431 @lilypond[quote,relative=2,verbatim]
432 \repeat volta 2 { c g <c e>2 ~ }
434 % First alternative: following note is tied normally
436 % Second alternative: following note has a repeated tie
437 { <c e>2\repeatTie d4 c } }
440 @cindex laissez vibrer
441 @cindex ties, laissez vibrer
443 @funindex \laissezVibrer
444 @funindex laissezVibrer
446 @notation{L.v.}@: ties (@notation{laissez vibrer}) indicate that
447 notes must not be damped at the end. It is used in notation for
448 piano, harp and other string and percussion instruments. They can
449 be entered as follows:
451 @lilypond[quote,verbatim,relative=1]
452 <c f g>1\laissezVibrer
455 @cindex ties, placement
461 @funindex \tieNeutral
464 Ties may be manually placed above or below the staff; see
465 @ref{Direction and placement}.
467 @cindex ties, appearance
480 Ties may be made dashed, dotted, or a combination of solid and
483 @lilypond[quote, verbatim, relative=1]
496 Custom dash patterns can be specified:
498 @lilypond[quote, verbatim, relative=1]
499 \tieDashPattern #0.3 #0.75
501 \tieDashPattern #0.7 #1.5
507 Dash pattern definitions for ties have the same structure as
508 dash pattern definitions for slurs.
509 For more information about complex dash patterns,
510 see the snippets under @ref{Slurs}.
518 @code{\tieDashPattern},
519 @code{\tieHalfDashed},
520 @code{\tieHalfSolid},
527 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
528 {using-ties-with-arpeggios.ly}
530 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
531 {engraving-ties-manually.ly}
537 @rglos{laissez vibrer}.
541 @ref{Automatic note splitting}.
547 @rinternals{LaissezVibrerTie},
548 @rinternals{LaissezVibrerTieColumn},
549 @rinternals{TieColumn},
555 Switching staves when a tie is active will not produce a slanted
558 Changing clefs or octavations during a tie is not really
559 well-defined. In these cases, a slur may be preferable.
564 @subsection Writing rests
566 Rests are entered as part of the music in music expressions.
571 * Full measure rests::
575 @unnumberedsubsubsec Rests
578 @cindex rest, entering durations
593 Rests are entered like notes with the note name @code{r}.
594 Durations longer than a whole rest use the predefined
597 @c \time 16/1 is used to avoid spurious bar lines
598 @c and long tracts of empty measures
599 @lilypond[fragment,quote,verbatim]
601 % These two lines are just to prettify this example
603 \override Staff.TimeSignature #'stencil = ##f
604 % Print a maxima rest, equal to four breves
606 % Print a longa rest, equal to two breves
610 r1 r2 r4 r8 r16 r32 r64 r128
614 @cindex rest, multi-measure
615 @cindex rest, whole-measure
617 Whole measure rests, centered in the middle of the measure, must be
618 entered as multi-measure rests. They can be used for a single
619 measure as well as many measures and are discussed in @ref{Full
622 @cindex rest, specifying vertical position
624 To explicitly specify a rest's vertical position, write a note
625 followed by @code{\rest}. A rest of the duration of the note will
626 be placed at the staff position where the note would appear. This
627 allows for precise manual formatting of polyphonic music, since the
628 automatic rest collision formatter will not move these rests.
630 @lilypond[quote,verbatim,relative=2]
636 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
647 @ref{Full measure rests}.
658 @c Deliberately duplicated in Durations and Rests. -gp
659 There is no fundamental limit to rest durations (both in terms of
660 longest and shortest), but the number of glyphs is limited: there
661 are rests from 128th to maxima (8 x whole).
664 @node Invisible rests
665 @unnumberedsubsubsec Invisible rests
668 @cindex invisible rest
669 @cindex rest, invisible
677 An invisible rest (also called a @q{spacer rest}) can be entered
678 like a note with the note name@tie{}@code{s}:
680 @lilypond[verbatim,quote,relative=2]
687 Spacer rests are available only in note mode and chord mode. In
688 other situations, for example, when entering lyrics, @code{\skip}
689 is used to skip a musical moment. @code{\skip} requires an
692 @lilypond[quote,verbatim,relative=2]
705 A spacer rest implicitly causes @code{Staff} and @code{Voice}
706 contexts to be created if none exist, just like notes and rests
709 @lilypond[quote,verbatim,fragment]
713 @code{\skip} simply skips musical time; it creates no output of
716 @lilypond[quote,verbatim,fragment]
717 % This is valid input, but does nothing
718 \skip 1 \skip1 \skip 1
724 @rlearning{Visibility and color of objects}.
728 @ref{Visibility of objects}.
734 @rinternals{SkipMusic}.
737 @node Full measure rests
738 @unnumberedsubsubsec Full measure rests
740 @cindex multi-measure rests
741 @cindex full-measure rests
742 @cindex rest, multi-measure
743 @cindex rest, full-measure
744 @cindex whole rest for a full measure
745 @cindex rest, whole for a full measure
749 Rests for one or more full measures are entered like notes with
750 the note name uppercase @code{R}:
752 @lilypond[quote,verbatim,relative=2]
753 % Rest measures contracted to single measure
754 \compressFullBarRests
761 The duration of full-measure rests is identical to the duration
762 notation used for notes. The duration in a multi-measure rest must
763 always be an integral number of measure-lengths, so augmentation dots
764 or fractions must often be used:
766 @lilypond[quote,fragment,verbatim]
767 \compressFullBarRests
773 R1*13/8 | R1*13/8*12 |
778 A full-measure rest is printed as either a whole or breve rest,
779 centered in the measure, depending on the time signature.
781 @lilypond[quote,verbatim,fragment]
790 @cindex multi-measure rest, expanding
791 @cindex multi-measure rest, contracting
793 @funindex \expandFullBarRests
794 @funindex expandFullBarRests
795 @funindex \compressFullBarRests
796 @funindex compressFullBarRests
798 By default a multi-measure rest is expanded in the printed score to
799 show all the rest measures explicitly. Alternatively, a multi-measure
800 rest can be shown as a single measure containing a multi-measure rest
801 symbol, with the number of measures of rest printed above the measure:
803 @lilypond[quote,fragment,verbatim]
805 \time 3/4 r2. | R2.*2 |
808 % Rest measures contracted to single measure
809 \compressFullBarRests
811 % Rest measures expanded
818 @cindex text on multi-measure rest
819 @cindex multi-measure rest, attaching text
820 @cindex script on multi-measure rest
821 @cindex multi-measure rest, script
822 @cindex fermata on multi-measure rest
823 @cindex multi-measure rest, attaching fermata
824 @cindex markup on multi-measure rest
825 @cindex multi-measure rest with markup
827 @funindex \fermataMarkup
828 @funindex fermataMarkup
829 @funindex MultiMeasureRestText
831 Markups can be added to multi-measure rests.
832 The predefined command @code{\fermataMarkup}
833 is provided for adding fermatas.
835 @lilypond[quote,verbatim,fragment]
836 \compressFullBarRests
838 R2.*10^\markup { \italic "ad lib." }
843 Markups attached to a multi-measure rest are
844 objects of type @code{MultiMeasureRestText}, not
845 @code{TextScript}. Overrides must be directed to the correct
846 object, or they will be ignored. See the following example.
849 @lilypond[quote,verbatim,fragment]
850 % This fails, as the wrong object name is specified
851 \override TextScript #'padding = #5
853 % This is correct and works
854 \override MultiMeasureRestText #'padding = #5
858 When a multi-measure rest immediately follows a @code{\partial}
859 setting, resulting bar-check warnings may not be displayed.
862 @funindex \textLengthOn
863 @funindex textLengthOn
864 @funindex \textLengthOff
865 @funindex textLenthOff
866 @funindex \fermataMarkup
867 @funindex fermataMarkup
868 @funindex \compressFullBarRests
869 @funindex compressFullBarRests
870 @funindex \expandFullBarRests
871 @funindex expandFullBarRests
874 @code{\textLengthOn},
875 @code{\textLengthOff},
876 @code{\fermataMarkup},
877 @code{\compressFullBarRests},
878 @code{\expandFullBarRests}.
886 @cindex kirchenpausen
888 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
889 {changing-form-of-multi-measure-rests.ly}
891 @cindex multi-measure rests, positioning
892 @cindex positioning multi-measure rests
894 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
895 {positioning-multi-measure-rests.ly}
897 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
898 {multi-measure-rest-markup.ly}
903 @rglos{multi-measure rest}.
908 @ref{Formatting text},
915 @rinternals{MultiMeasureRest},
916 @rinternals{MultiMeasureRestNumber},
917 @rinternals{MultiMeasureRestText}.
920 @cindex fingerings and multi-measure rests
921 @cindex multi-measure rests and fingerings
925 If an attempt is made to use fingerings (e.g.,
926 @code{R1*10-4}) to put numbers over multi-measure rests, the
927 fingering numeral (4) may collide with the bar counter
930 @cindex condensing rests
931 @cindex rest, condensing ordinary
933 There is no way to automatically condense multiple ordinary rests
934 into a single multi-measure rest.
936 @cindex rest, collisions of
938 Multi-measure rests do not take part in rest collisions.
940 @node Displaying rhythms
941 @subsection Displaying rhythms
947 * Polymetric notation::
948 * Automatic note splitting::
949 * Showing melody rhythms::
953 @unnumberedsubsubsec Time signature
955 @cindex time signature
961 The time signature is set as follows:
963 @lilypond[quote,verbatim,relative=2]
968 @cindex time signature, visibility of
970 Time signatures are printed at the beginning of a piece
971 and whenever the time signature changes. If a change takes place
972 at the end of a line a warning time signature sign is printed
973 there. This default behavior may be changed, see
974 @ref{Visibility of objects}.
976 @lilypond[quote,verbatim,relative=2]
986 @cindex time signature style
989 @funindex \numericTimeSignature
990 @funindex numericTimeSignature
991 @funindex \defaultTimeSignature
992 @funindex defaultTimeSignature
994 The time signature symbol that is used in 2/2 and 4/4 time can be
995 changed to a numeric style:
997 @lilypond[quote,verbatim,relative=2]
1001 % Change to numeric style
1002 \numericTimeSignature
1005 % Revert to default style
1006 \defaultTimeSignature
1012 Mensural time signatures are covered in
1013 @ref{Mensural time signatures}.
1017 @code{\numericTimeSignature},
1018 @code{\defaultTimeSignature}.
1024 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
1025 {changing-the-time-signature-without-affecting-the-beaming.ly}
1027 @cindex compound time signatures
1028 @cindex time signature, compound
1030 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1031 {compound-time-signatures.ly}
1033 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1034 {time-signature-printing-only-the-numerator-as-a-number-instead-of-the-fraction.ly}
1039 @rglos{time signature}
1042 @ref{Mensural time signatures},
1043 @ref{Time administration}.
1048 Internals Reference:
1049 @rinternals{TimeSignature},
1050 @rinternals{Timing_translator}.
1054 @unnumberedsubsubsec Upbeats
1058 @cindex partial measure
1059 @cindex measure, partial
1060 @cindex pickup measure
1061 @cindex measure, change length
1063 @funindex measurePosition
1067 Partial or pick-up measures, such as an anacrusis or upbeat, are
1068 entered using the @code{\partial} command, with the syntax
1071 \partial @var{duration}
1075 where @code{duration} is the rhythmic length of the interval
1076 before the start of the first complete measure:
1078 @lilypond[quote,verbatim,relative=2]
1083 The partial measure can be any duration less than a full measure:
1085 @lilypond[quote,verbatim,relative=2]
1086 \partial 8*3 c8 d e |
1090 Internally, @code{\partial} is translated into
1093 \set Timing.measurePosition = -@var{duration}
1097 The property @code{measurePosition} contains a rational number
1098 indicating how much of the measure has passed at this point. Note
1099 that this is set to a negative number by the @code{\partial}
1100 command: i.e., @code{\partial 4} is internally translated to
1101 @code{-4}, meaning @qq{there is a quarter note left in the measure.}
1115 @rinternals{Timing_translator}.
1120 The @code{\partial} command is intended to be used only at the
1121 beginning of a piece. If you use it after the beginning, some
1122 odd warnings may occur.
1124 @node Unmetered music
1125 @unnumberedsubsubsec Unmetered music
1127 @cindex bar lines, turning off
1128 @cindex bar numbering, turning off
1130 @cindex unmetered music
1132 @funindex \cadenzaOn
1134 @funindex \cadenzaOff
1135 @funindex cadenzaOff
1137 Bar lines and bar numbers are calculated automatically. For
1138 unmetered music (some cadenzas, for example), this is not desirable.
1139 To turn off automatic calculation of bar lines and bar numbers,
1140 use the command @code{\cadenzaOn}, and use @code{\cadenzaOff}
1141 to turn them on again.
1143 @lilypond[verbatim,relative=2,fragment]
1152 Bar numbering is resumed at the end of the cadenza as if the
1153 cadenza were not there:
1155 @lilypond[verbatim,relative=2,fragment]
1156 % Show all bar numbers
1157 \override Score.BarNumber #'break-visibility = #all-visible
1178 @ref{Visibility of objects}.
1184 @cindex cadenza line breaks
1185 @cindex cadenza page breaks
1186 @cindex unmetered music, line breaks
1187 @cindex unmetered music, page breaks
1188 @cindex breaks in unmetered music
1189 @cindex line breaks in cadenzas
1190 @cindex page breaks in cadenzas
1191 @cindex line breaks in unmetered music
1192 @cindex page breaks in unmetered music
1196 LilyPond will insert line breaks and page breaks only at a
1197 bar line. Unless the unmetered music ends before the end of the
1198 staff line, you will need to insert invisible bar lines with
1205 to indicate where breaks can occur.
1208 @node Polymetric notation
1209 @unnumberedsubsubsec Polymetric notation
1211 @c This section necessarily uses \set
1212 @c This is acceptable -td
1214 @cindex double time signatures
1215 @cindex signatures, polymetric
1216 @cindex time signatures, polymetric
1217 @cindex time signatures, double
1218 @cindex polymetric signatures
1219 @cindex meter, polymetric
1221 @funindex timeSignatureFraction
1222 @funindex \scaleDurations
1223 @funindex scaleDurations
1227 Polymetric notation is supported, either explicitly or by modifying
1228 the visible time signature symbol and scaling the note durations.
1230 @strong{@i{Staves with different time signatures, equal measure lengths}}
1232 This notation can be created by setting a common time signature
1233 for each staff but replacing the symbol manually by setting
1234 @code{timeSignatureFraction} to the desired fraction and scaling
1235 the printed durations in each staff to the common time
1236 signature; see @ref{Time signature}. The scaling is done with
1237 @code{\scaleDurations}, which is used in a similar way to
1238 @code{\times}, but does not create a tuplet bracket; see
1239 @ref{Scaling durations}.
1241 @cindex beaming in polymetric music
1242 @cindex beaming in polymetric meter
1244 In this example, music with the time signatures of 3/4, 9/8, and
1245 10/8 are used in parallel. In the second staff, shown durations
1246 are multiplied by 2/3, as 2/3 * 9/8 = 3/4, and in the third
1247 staff, shown durations are multiplied by 3/5, as 3/5 * 10/8 = 3/4.
1248 It will often be necessary to insert beams manually, as the
1249 duration scaling affects the autobeaming rules.
1251 @lilypond[quote,verbatim,fragment]
1260 \set Staff.timeSignatureFraction = #'(9 . 8)
1261 \scaleDurations #'(2 . 3)
1262 \repeat unfold 6 { c8[ c c] }
1266 \set Staff.timeSignatureFraction = #'(10 . 8)
1267 \scaleDurations #'(3 . 5) {
1268 \repeat unfold 2 { c8[ c c] }
1269 \repeat unfold 2 { c8[ c] } |
1270 c4. c4. \times 2/3 { c8[ c c] } c4
1276 @strong{@i{Staves with different time signatures, unequal bar lengths}}
1278 Each staff can be given its own independent time signature by
1279 moving the @code{Timing_translator} and the
1280 @code{Default_bar_line_engraver} to the @code{Staff} context.
1282 @lilypond[quote,verbatim]
1286 \remove "Timing_translator"
1287 \remove "Default_bar_line_engraver"
1291 \consists "Timing_translator"
1292 \consists "Default_bar_line_engraver"
1296 % Now each staff has its own time signature.
1322 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
1323 {compound-time-signatures.ly}
1329 @rglos{polymetric time signature},
1333 @ref{Time signature},
1334 @ref{Scaling durations}.
1339 Internals Reference:
1340 @rinternals{TimeSignature},
1341 @rinternals{Timing_translator},
1342 @rinternals{Default_bar_line_engraver},
1348 When using different time signatures in parallel, notes
1349 at the same moment will be be placed at the same horizontal
1350 location. However, the bar lines in the different staves
1351 will cause the note spacing to be less regular in each of the
1352 individual staves than would be normal without the different
1355 @node Automatic note splitting
1356 @unnumberedsubsubsec Automatic note splitting
1358 @cindex notes, splitting
1359 @cindex splitting notes
1361 @funindex Note_heads_engraver
1362 @funindex Completion_heads_engraver
1364 Long notes which overrun bar lines can be converted automatically
1365 to tied notes. This is done by replacing the
1366 @code{Note_heads_engraver} with the
1367 @code{Completion_heads_engraver}. In the following
1368 example, notes crossing the bar lines are split and tied.
1370 @lilypond[quote,verbatim,relative=1]
1372 \remove "Note_heads_engraver"
1373 \consists "Completion_heads_engraver"
1376 { c2. c8 d4 e f g a b c8 c2 b4 a g16 f4 e d c8. c2 }
1379 This engraver splits all running notes at the bar line, and
1380 inserts ties. One of its uses is to debug complex scores: if the
1381 measures are not entirely filled, then the ties show exactly how
1382 much each measure is off.
1390 @rlearning{Engravers explained},
1391 @rlearning{Adding and removing engravers}.
1396 Internals Reference:
1397 @rinternals{Note_heads_engraver},
1398 @rinternals{Completion_heads_engraver},
1399 @rinternals{Forbid_line_break_engraver}.
1404 Not all durations (especially those containing tuplets) can be
1405 represented exactly with normal notes and dots, but the
1406 @code{Completion_heads_engraver} will not insert tuplets.
1408 The @code{Completion_heads_engraver} only affects notes; it does not
1412 @node Showing melody rhythms
1413 @unnumberedsubsubsec Showing melody rhythms
1415 @cindex melody rhythms, showing
1416 @cindex rhythms, showing melody
1418 Sometimes you might want to show only the rhythm of a melody. This
1419 can be done with the rhythmic staff. All pitches of notes on such a
1420 staff are squashed, and the staff itself has a single line
1422 @lilypond[quote,relative=1,verbatim]
1424 \new RhythmicStaff {
1425 \new Voice = "myRhythm" {
1433 \lyricsto "myRhythm" {
1441 @cindex guitar chord charts
1442 @cindex strumming rhythms, showing
1443 @cindex guitar strumming rhythms, showing
1445 @funindex Pitch_squash_engraver
1446 @funindex \improvisationOn
1447 @funindex improvisationOn
1448 @funindex \improvisationOff
1449 @funindex improvisationOff
1451 Guitar chord charts often show the strumming rhythms. This can
1452 be done with the @code{Pitch_squash_engraver} and
1453 @code{\improvisationOn}.
1456 @lilypond[quote,verbatim]
1465 \consists Pitch_squash_engraver
1478 @code{\improvisationOn},
1479 @code{\improvisationOff}.
1485 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
1486 {guitar-strum-rhythms.ly}
1493 Internals Reference:
1494 @rinternals{RhythmicStaff},
1495 @rinternals{Pitch_squash_engraver}.
1503 * Setting automatic beam behavior::
1508 @node Automatic beams
1509 @unnumberedsubsubsec Automatic beams
1511 By default, beams are inserted automatically:
1513 @cindex beams, manual
1514 @cindex manual beams
1515 @cindex beams, setting rules for
1516 @cindex beams, custom rules for
1518 @funindex \autoBeamOn
1519 @funindex autoBeamOn
1520 @funindex \autoBeamOff
1521 @funindex autoBeamOff
1523 @lilypond[quote,verbatim,relative=2]
1525 \time 6/8 c c c c8. c16 c8
1528 If these automatic decisions are not satisfactory, beaming can be
1529 entered explicitly; see @ref{Manual beams}. Beams @emph{must} be
1530 entered manually if beams are to be extended over rests.
1532 If automatic beaming is not required, it may be turned off with
1533 @code{\autoBeamOff} and on with @code{\autoBeamOn}:
1535 @lilypond[quote,relative=1,verbatim]
1536 c4 c8 c8. c16 c8. c16 c8
1543 @cindex melismata, beams
1544 @cindex beams and melismata
1546 @warning{If beams are used to indicate melismata in songs, then
1547 automatic beaming should be switched off with @code{\autoBeamOff}
1548 and the beams indicated manually.}
1550 Beaming patterns that differ from the automatic defaults can be
1551 created; see @ref{Setting automatic beam behavior}.
1555 @code{\autoBeamOff},
1562 @cindex line breaks and beams
1563 @cindex beams and line breaks
1567 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
1568 {beams-across-line-breaks.ly}
1570 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
1571 {changing-beam-knee-gap.ly}
1577 @ref{Setting automatic beam behavior}.
1580 @file{scm/@/auto@/-beam@/.scm}.
1585 Internals Reference:
1591 Beams can collide with note heads and accidentals in other voices.
1594 @node Setting automatic beam behavior
1595 @unnumberedsubsubsec Setting automatic beam behavior
1598 @cindex automatic beams, tuning
1599 @cindex tuning automatic beaming
1600 @cindex automatic beam generation
1602 @cindex lyrics and beaming
1604 @funindex autoBeaming
1605 @funindex beamSettings
1606 @funindex measureLength
1607 @funindex beatLength
1613 The placement of automatic beams is determined by the time signature.
1614 Three types of rules are used for determining the end of automatic
1615 beams: @emph{default} rules
1616 for the time signature, @emph{explicit} rules for the beam in the time
1617 signature, and the @emph{beatLength} for the time signature.
1619 The following rules, in order of priority, apply when determining
1620 the appearance of beams:
1624 @item If a manual beam is specified with @code{[..]} set the beam
1625 as specified, otherwise
1627 @item if @code{\autoBeamOff} is in force do not beam, otherwise
1629 @item if an explicit beam-ending rule is defined for the beam type
1630 in the time signature, use it to determine the valid
1631 places where beams may end, otherwise
1633 @item if a default beam-ending rule is defined in the time signature,
1634 use it to group notes with beams, otherwise
1636 @item use the value of @code{beatLength} to group notes with beams
1640 @i{@strong{Modifying the grouping of beats}}
1642 By default @code{beatLength} is
1643 derived from the time signature set by the @code{\time} command.
1644 The @code{beatLength} is set to be one over the denominator
1645 of the time signature.
1647 @code{beatLength} is a @i{moment},
1648 a unit of musical duration. A quantity of type @i{moment} is
1649 created by the scheme function @code{ly:make-moment}. For more
1650 information about this function, see @ref{Time administration}.
1652 Autobeam and beam subdivide settings are stored in the
1653 @code{beamSettings} property. Default values of @code{beamSettings}
1654 are determined in @file{scm/@/beam@/-settings@/.scm}. Entries in
1655 @code{beamSettings} are indexed by time signature and
1658 Time signature should be a scheme pair , e.g. @code{#'(4 . 4)}.
1660 Rule type should be @code{#'end} for beam ending and @code{#'subdivide} for
1663 The ending and subdivision rules consist of a scheme alist
1664 (or list of pairs) that
1665 indicates the beam type and the grouping to be applied to that
1669 #'((beam-type1 . grouping-1)
1670 (beam-type2 . grouping-2)
1671 (beam-type3 . grouping-3))
1674 Beam type is either a scheme pair indicating the duration
1675 of the beam, e.g. @code{(1 . 16)}, or @code{*} to indicate a
1676 default rule, which applies to all beams if no explicit rule is
1679 Grouping is a scheme list indicating the grouping to be applied to
1680 the beam. For default rules (where beam type is
1681 @code{*}, the grouping is in units of @code{beatLength}.
1682 For explicit rules, the grouping is in units of the beam type.
1684 Beam settings are changed with
1685 @code{\overrideBeamSettings} and @code{\revertBeamSettings}.
1687 @lilypond[quote,relative=2,verbatim]
1690 \overrideBeamSettings #'Score #'(5 . 16) #'end #'((* . (2 3)))
1692 \overrideBeamSettings #'Score #'(5 . 16) #'end #'((* . (3 2)))
1696 Beam setting changes can be limited to specific contexts. If no
1697 setting is included in a lower-level context, the setting of the
1698 enclosing context will apply.
1700 @lilypond[quote, verbatim,relative=1]
1705 \overrideBeamSettings #'Staff #'(7 . 8) #'end #'((* . (2 3 2)))
1712 \overrideBeamSettings #'Voice #'(7 . 8) #'end #'((* . (1 3 3)))
1719 When multiple voices are used the @code{Staff} context must be
1720 specified if the beaming is to be applied to all voices in the
1723 @lilypond[quote,verbatim,relative=2]
1726 % Context Voice specified -- does not work correctly
1727 % Because of autogenerated voices, all beating will
1728 % be at beatLength (1 . 8)
1729 \overrideBeamSettings #'Voice #'(7 . 8) #'end #'((* . (3 1 1 2)))
1730 << {a8 a a a16 a a a a8 a} \\ {f4. f8 f f f} >>
1732 % Works correctly with context Staff specified
1733 \overrideBeamSettings #'Staff #'(7 . 8) #'end #'((* . (3 1 1 2)))
1734 << {a8 a a a16 a a a a8 a} \\ {f4. f8 f f f} >>
1737 @funindex revertBeamSettings
1739 Beam settings can be reverted to get back to default behavior. This
1740 is accomplished by using @code{\revertBeamSettings}. The arguments
1741 are the same as for @code{\overrideBeamSettings}, except no value
1742 for @var{grouping} is given:
1745 \revertBeamSettings context time-signature rule-type
1749 @lilypond[quote,verbatim,relative=2]
1751 \repeat unfold 16 {a16}
1752 % set default rule for (1 1 1 1) grouping
1753 \overrideBeamSettings #'Score #'(4 . 4) #'end #'((* . (1 1 1 1)))
1754 \repeat unfold 16 {a16}
1755 % revert the new rule
1756 \revertBeamSettings #'Score #'(4 . 4) #'end
1757 \repeat unfold 16 {a16}
1762 @cindex beams, subdividing
1764 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
1765 {sub-dividing-beams.ly}
1767 @cindex measure groupings
1768 @cindex beats, grouping
1769 @cindex grouping beats
1770 @cindex measure sub-grouping
1772 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
1773 {conducting-signs,-measure-grouping-signs.ly}
1775 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
1776 {beam-endings-in-score-context.ly}
1778 @cindex beam, last in score
1779 @cindex beam, last in polyphonic voice
1783 If a score ends while an automatic beam has not been ended and is
1784 still accepting notes, this last beam will not be typeset at all.
1785 The same holds for polyphonic voices, entered with @code{<<
1786 @dots{} \\ @dots{} >>}. If a polyphonic voice ends while an
1787 automatic beam is still accepting notes, it is not typeset.
1796 @unnumberedsubsubsec Manual beams
1798 @cindex beams, manual
1799 @cindex manual beams
1804 In some cases it may be necessary to override the automatic
1805 beaming algorithm. For example, the autobeamer will not put beams
1806 over rests or bar lines, and in choral scores the beaming is
1807 often set to follow the meter of the lyrics rather than the
1808 notes. Such beams can be specified manually by
1809 marking the begin and end point with @code{[} and @code{]}
1811 @lilypond[quote,relative=1,verbatim]
1813 r4 r8[ g' a r8] r8 g[ | a] r8
1821 Individual notes may be marked with @code{\noBeam} to prevent them
1824 @lilypond[quote,verbatim,relative=2]
1825 \time 2/4 c8 c\noBeam c c
1828 @funindex stemLeftBeamCount
1829 @funindex stemRightBeamCount
1831 Even more strict manual control with the beams can be achieved by
1832 setting the properties @code{stemLeftBeamCount} and
1833 @code{stemRightBeamCount}. They specify the number of beams to
1834 draw on the left and right side, respectively, of the next note.
1835 If either property is set, its value will be used only once, and
1836 then it is erased. In this example, the last @code{f} is printed
1837 with only one beam on the left side, i.e., the eighth-note beam of
1838 the group as a whole.
1840 @lilypond[quote,relative=2,verbatim]
1843 \set stemLeftBeamCount = #2
1844 \set stemRightBeamCount = #1
1846 \set stemLeftBeamCount = #1
1853 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
1854 {flat-flags-and-beam-nibs.ly}
1856 @node Feathered beams
1857 @unnumberedsubsubsec Feathered beams
1859 @cindex beams, feathered
1860 @cindex feathered beams
1862 @funindex \featherDurations
1863 @funindex featherDurations
1864 @funindex grow-direction
1866 Feathered beams are used to indicate that a small group of notes
1867 should be played at an increasing (or decreasing) tempo, without
1868 changing the overall tempo of the piece. The extent of the
1869 feathered beam must be indicated manually using @code{[} and
1870 @code{]}, and the beam feathering is turned on by specifying a
1871 direction to the @code{Beam} property @code{grow-direction}.
1873 If the placement of the notes and the sound in the MIDI output is to
1874 reflect the ritardando or accelerando indicated by the feathered beam
1875 the notes must be grouped as a music expression delimited by braces
1876 and preceded by a @code{featherDurations} command which specifies
1877 the ratio between the durations of the first and last notes in the
1880 The square brackets show the extent of the beam and the braces show
1881 which notes are to have their durations modified. Normally these
1882 would delimit the same group of notes, but this is not required: the
1883 two commands are independent.
1885 In the following example the eight 16th notes occupy exactly the
1886 same time as a half note, but the first note is one half as long
1887 as the last one, with the intermediate notes gradually
1888 lengthening. The first four 32nd notes gradually speed up, while
1889 the last four 32nd notes are at a constant tempo.
1891 @lilypond[relative=1,verbatim,quote]
1892 \override Beam #'grow-direction = #LEFT
1893 \featherDurations #(ly:make-moment 2 1)
1894 { c16[ c c c c c c c] }
1895 \override Beam #'grow-direction = #RIGHT
1896 \featherDurations #(ly:make-moment 2 3)
1898 % revert to non-feathered beams
1899 \override Beam #'grow-direction = #'()
1904 The spacing in the printed output represents the
1905 note durations only approximately, but the MIDI output is exact.
1909 The @code{\featherDurations} command only works with very short
1910 music snippets, and when numbers in the fraction are small.
1925 * Bar and bar number checks::
1930 @unnumberedsubsubsec Bar lines
1933 @cindex measure lines
1934 @cindex closing bar lines
1935 @cindex bar lines, closing
1936 @cindex double bar lines
1937 @cindex bar lines, double
1943 Bar lines delimit measures, and are also used to indicate
1944 repeats. Normally, simple bar lines are automatically inserted
1945 into the printed output at places based on the current time
1948 The simple bar lines inserted automatically can be changed to
1949 other types with the @code{\bar} command. For example, a closing
1950 double bar line is usually placed at the end of a piece:
1952 @lilypond[quote,relative=1,verbatim]
1956 It is not invalid if the final note in a measure does not
1957 end on the automatically entered bar line: the note is assumed
1958 to carry over into the next measure. But if a long sequence
1959 of such carry-over measures appears the music can appear compressed
1960 or even flowing off the page. This is because automatic line
1961 breaks happen only at the end of complete measures, i.e., where
1962 all notes end before the end of a measure.
1964 @warning{An incorrect duration can cause line breaks to be
1965 inhibited, leading to a line of highly compressed music or
1966 music which flows off the page.}
1969 @cindex bar lines, invisible
1970 @cindex measure lines, invisible
1972 Line breaks are also permitted at manually inserted bar lines
1973 even within incomplete measures. To allow a line break without
1974 printing a bar line, use
1981 This will insert an invisible bar line and allow (but not
1982 force) a line break to occur at this point. The bar number
1983 counter is not increased. To force a line break see
1984 @ref{Line breaking}.
1986 @cindex manual bar lines
1987 @cindex manual measure lines
1988 @cindex bar lines, manual
1989 @cindex measure lines, manual
1991 This and other special bar lines may be inserted manually at any
1992 point. When they coincide with the end of a measure they replace the
1993 simple bar line which would have been inserted there automatically.
1994 When they do not coincide with the end of a measure the specified bar
1995 line is inserted at that point in the printed output. Such insertions
1996 do not affect the calculation and placement of subsequent automatic
1999 Two types of simple bar lines and five types of double bar lines are available
2000 for manual insertion:
2002 @lilypond[quote,relative=1,verbatim]
2014 together with dotted and dashed bar lines:
2016 @lilypond[quote,relative=1,verbatim]
2023 and five types of repeat bar line:
2025 @lilypond[quote,relative=1,verbatim]
2034 Additionally, a bar line can be printed as a simple tick:
2035 @lilypond[quote,relative=1,verbatim]
2038 However, as such ticks are typically used in Gregorian chant, it is preferable
2039 to use @code{\divisioMinima} there instead, described in the section
2040 @ref{Divisiones} in Gregorian chant.
2045 Although the bar line types signifying repeats may be inserted
2046 manually they do not in themselves cause LilyPond to recognize
2047 a repeated section. Such repeated sections are better entered
2048 using the various repeat commands (see @ref{Repeats}), which
2049 automatically print the appropriate bar lines.
2051 In addition, you can specify @code{"||:"}, which is equivalent to
2052 @code{"|:"} except at line breaks, where it gives a double bar
2053 line at the end of the line and a start repeat at the beginning of
2056 @lilypond[quote,relative=2,verbatim]
2064 In scores with many staves, a @code{\bar} command in one staff is
2065 automatically applied to all staves. The resulting bar lines are
2066 connected between different staves of a @code{StaffGroup},
2067 @code{PianoStaff}, or @code{GrandStaff}.
2069 @lilypond[quote,fragment,verbatim]
2077 \new Staff { \clef bass c4 g e g }
2079 \new Staff { \clef bass c2 c2 }
2084 @cindex default bar lines, changing
2085 @cindex bar lines, default, changing
2090 @funindex defaultBarType
2095 The command @code{\bar }@var{bartype} is a shortcut for
2096 @code{\set Timing.whichBar = }@var{bartype}. A bar line is
2097 created whenever the @code{whichBar} property is
2100 The default bar type used for automatically inserted bar lines is
2101 @code{"|"}. This may be changed at any time
2102 with @code{\set Timing.defaultBarType = }@var{bartype}.
2107 @ref{Line breaking},
2109 @ref{Grouping staves}.
2114 Internals Reference:
2115 @rinternals{BarLine} (created at @code{Staff} level),
2116 @rinternals{SpanBar} (across staves),
2117 @rinternals{Timing_translator} (for Timing properties).
2121 @unnumberedsubsubsec Bar numbers
2124 @cindex measure numbers
2125 @cindex numbers, bar
2126 @cindex numbers, measure
2128 @funindex currentBarNumber
2130 Bar numbers are typeset by default at the start of every line except
2131 the first line. The number itself is stored in the
2132 @code{currentBarNumber} property, which is normally updated
2133 automatically for every measure. It may also be set manually:
2135 @lilypond[verbatim,quote,fragment,relative=1]
2138 \set Score.currentBarNumber = #50
2142 @cindex bar numbers, regular spacing
2144 @funindex barNumberVisibility
2147 Bar numbers can be typeset at regular intervals instead of just at
2148 the beginning of every line. To do this the default behavior
2149 must be overridden to permit bar numbers to be printed at places
2150 other than the start of a line. This is controlled by the
2151 @code{break-visibility} property of @code{BarNumber}. This takes
2152 three values which may be set to @code{#t} or @code{#f} to specify
2153 whether the corresponding bar number is visible or not. The order
2154 of the three values is @code{end of line visible}, @code{middle of
2155 line visible}, @code{beginning of line visible}. In the following
2156 example bar numbers are printed at all possible places:
2158 @lilypond[verbatim,quote,relative=1]
2159 \override Score.BarNumber #'break-visibility = #'#(#t #t #t)
2160 \set Score.currentBarNumber = #11
2161 % Permit first bar number to be printed
2171 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
2172 {printing-the-bar-number-for-the-first-measure.ly}
2174 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
2175 {printing-bar-numbers-at-regular-intervals.ly}
2177 @cindex measure number, format
2178 @cindex bar number, format
2180 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
2181 {printing-bar-numbers-inside-boxes-or-circles.ly}
2183 @cindex bar number alignment
2185 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
2186 {aligning-bar-numbers.ly}
2188 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
2189 {removing-bar-numbers-from-a-score.ly}
2196 Internals Reference:
2197 @rinternals{BarNumber}.
2200 @cindex bar number collision
2201 @cindex collision, bar number
2205 Bar numbers may collide with the top of the @code{StaffGroup} bracket,
2206 if there is one. To solve this, the @code{padding} property of
2207 @code{BarNumber} can be used to position the number correctly. See
2208 @rinternals{StaffGroup} and @rinternals{BarNumber} for more.
2212 @node Bar and bar number checks
2213 @unnumberedsubsubsec Bar and bar number checks
2216 @cindex bar number check
2217 @cindex measure check
2218 @cindex measure number check
2220 @funindex barCheckSynchronize
2223 Bar checks help detect errors in the entered durations. A bar check
2224 may be entered using the bar symbol, @code{|}, at any place where a
2225 bar line is expected to fall. If bar check lines are encountered at
2226 other places, a list of warnings is printed in the log file, showing
2227 the line numbers and lines in which the bar checks failed. In the
2228 next example, the second bar check will signal an error.
2231 \time 3/4 c2 e4 | g2 |
2234 Bar checks can also be used in lyrics, for example
2239 Twin -- kle | Twin -- kle |
2243 An incorrect duration can result in a completely garbled score,
2244 especially if the score is polyphonic, so a good place to start
2245 correcting input is by scanning for failed bar checks and
2246 incorrect durations.
2248 If successive bar checks are off by the same musical interval,
2249 only the first warning message is displayed. This allows the
2250 warning to focus on the source of the timing error.
2254 @funindex pipeSymbol
2256 It is also possible to redefine the action taken when a bar check
2257 or pipe symbol, @code{|}, is encountered in the input, so that
2258 it does something other than a bar check. This is done by
2259 assigning a music expression to @code{pipeSymbol}.
2260 In the following example @code{|} is set to insert a double bar
2261 line wherever it appears in the input, rather than checking
2264 @lilypond[quote,verbatim]
2265 pipeSymbol = \bar "||"
2274 @funindex \barNumberCheck
2275 @funindex barNumberCheck
2277 When copying large pieces of music, it can be helpful to check that
2278 the LilyPond bar number corresponds to the original that you are
2279 entering from. This can be checked with @code{\barNumberCheck}, for
2283 \barNumberCheck #123
2287 will print a warning if the @code{currentBarNumber} is not 123
2288 when it is processed.
2296 @node Rehearsal marks
2297 @unnumberedsubsubsec Rehearsal marks
2299 @cindex rehearsal marks
2300 @cindex mark, rehearsal
2305 To print a rehearsal mark, use the @code{\mark} command.
2307 @lilypond[quote,verbatim,relative=2]
2316 The letter@tie{}@q{I} is skipped in accordance with engraving
2317 traditions. If you wish to include the letter @q{I}, then use
2320 \set Score.markFormatter = #format-mark-alphabet
2323 The mark is incremented automatically if you use @code{\mark
2324 \default}, but you can also use an integer argument to set the
2325 mark manually. The value to use is stored in the property
2326 @code{rehearsalMark}.
2328 @cindex rehearsal mark format
2329 @cindex rehearsal mark style
2330 @cindex style, rehearsal mark
2331 @cindex format, rehearsal mark
2332 @cindex mark, rehearsal, style
2333 @cindex mark, rehearsal, format
2334 @cindex rehearsal mark, manual
2335 @cindex mark, rehearsal, manual
2336 @cindex custom rehearsal mark
2337 @cindex manual rehearsal mark
2339 The style is defined by the property @code{markFormatter}. It is
2340 a function taking the current mark (an integer) and the current
2341 context as argument. It should return a markup object. In the
2342 following example, @code{markFormatter} is set to a pre-defined
2343 procedure. After a few measures, it is set to a procedure that
2344 produces a boxed number.
2346 @lilypond[quote,verbatim,relative=2]
2347 \set Score.markFormatter = #format-mark-numbers
2350 \set Score.markFormatter = #format-mark-box-numbers
2352 \set Score.markFormatter = #format-mark-circle-numbers
2354 \set Score.markFormatter = #format-mark-circle-letters
2358 The file @file{scm/@/translation@/-functions@/.scm} contains the
2359 definitions of @code{format-mark-numbers} (the default format),
2360 @code{format-mark-box-numbers}, @code{format-mark-letters} and
2361 @code{format-mark-box-letters}. These can be used as inspiration
2362 for other formatting functions.
2364 You may use @code{format-mark-barnumbers},
2365 @code{format-mark-box-barnumbers}, and
2366 @code{format-mark-circle-barnumbers} to get bar numbers instead of
2367 incremented numbers or letters.
2369 Other styles of rehearsal mark can be specified manually:
2376 Note that @code{Score.markFormatter} does not affect marks specified
2377 in this manner. However, it is possible to apply a @code{\markup} to the
2381 \mark \markup@{ \box A1 @}
2386 @cindex D.S. al Fine
2388 @cindex music glyphs
2389 @cindex glyphs, music
2391 @funindex \musicglyph
2392 @funindex musicglyph
2394 Music glyphs (such as the segno sign) may be printed inside a
2397 @lilypond[quote,verbatim,relative=1]
2398 c1 \mark \markup { \musicglyph #"scripts.segno" }
2399 c1 \mark \markup { \musicglyph #"scripts.coda" }
2400 c1 \mark \markup { \musicglyph #"scripts.ufermata" }
2405 See @ref{The Feta font}, for a list of symbols which may be
2406 printed with @code{\musicglyph}.
2408 For common tweaks to the positioning of rehearsal marks, see
2409 @ref{Formatting text}.
2414 @ref{The Feta font},
2415 @ref{Formatting text}.
2418 @file{scm/@/translation@/-functions@/.scm} contains
2419 the definition of @code{format-mark-numbers} and
2420 @code{format-mark-letters}. They can be used as inspiration for
2421 other formatting functions.
2426 Internals Reference:
2427 @rinternals{RehearsalMark}.
2430 @node Special rhythmic concerns
2431 @subsection Special rhythmic concerns
2436 * Aligning to cadenzas::
2437 * Time administration::
2441 @unnumberedsubsubsec Grace notes
2445 @cindex appoggiatura
2446 @cindex acciaccatura
2451 Grace notes are ornaments that are written out. Grace notes
2452 are printed in a smaller font and take up no logical time
2455 @lilypond[quote,relative=2,verbatim]
2457 \grace { c16[ d16] } c2
2460 LilyPond also supports two special types of grace notes, the
2461 @emph{acciaccatura} -- an unmeasured grace note indicated by a slurred
2462 small note with a slashed stem -- and the @emph{appoggiatura}, which
2463 takes a fixed fraction of the main note and appears in small print
2466 @lilypond[quote,relative=2,verbatim]
2470 \acciaccatura { g16[ f] } e4
2473 The placement of grace notes is synchronized between different
2474 staves. In the following example, there are two sixteenth grace
2475 notes for every eighth grace note
2477 @lilypond[quote,relative=2,verbatim]
2478 << \new Staff { e2 \grace { c16[ d e f] } e2 }
2479 \new Staff { c2 \grace { g8[ b] } c2 } >>
2482 @cindex grace notes, following
2484 @funindex \afterGrace
2485 @funindex afterGrace
2487 If you want to end a note with a grace, use the @code{\afterGrace}
2488 command. It takes two arguments: the main note, and the grace
2489 notes following the main note.
2491 @lilypond[quote,verbatim,relative=2]
2492 c1 \afterGrace d1 { c16[ d] } c1
2495 This will put the grace notes after a space lasting 3/4 of the
2496 length of the main note. The default fraction 3/4 can be changed by
2497 setting @code{afterGraceFraction}. The following example shows
2498 the results from setting the space at the default, at 15/16, and
2499 finally at 1/2 of the main note.
2501 @lilypond[quote,verbatim,relative=2]
2504 c1 \afterGrace d1 { c16[ d] } c1
2507 #(define afterGraceFraction (cons 15 16))
2508 c1 \afterGrace d1 { c16[ d] } c1
2511 #(define afterGraceFraction (cons 1 2))
2512 c1 \afterGrace d1 { c16[ d] } c1
2517 The space between the main note and the grace note may also be
2518 specified using spacers. The following example places the grace
2519 note after a space lasting 7/8 of the main note.
2521 @lilypond[quote,verbatim,relative=2]
2524 { s2 s4. \grace { c16[ d] } } >>
2529 @cindex tweaking grace notes
2530 @cindex grace notes, tweaking
2531 @cindex grace notes, changing layout settings
2533 A @code{\grace} music expression will introduce special
2534 typesetting settings, for example, to produce smaller type, and
2535 set directions. Hence, when introducing layout tweaks to
2536 override the special settings, they should be placed inside
2537 the grace expression. The overrides should also be reverted
2538 inside the grace expression. Here, the grace note's default stem
2539 direction is overridden and then reverted.
2541 @lilypond[quote,verbatim,relative=2]
2553 @cindex stem, with slash
2558 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
2559 {using-grace-note-slashes-with-normal-heads.ly}
2561 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
2562 {tweaking-grace-layout-within-music.ly}
2564 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
2565 {redefining-grace-note-global-defaults.ly}
2567 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
2568 {positioning-grace-notes-with-floating-space.ly}
2573 @rglos{grace notes},
2574 @rglos{acciaccatura},
2575 @rglos{appoggiatura}.
2578 @file{ly/@/grace@/-init@/.ly}.
2583 Internals Reference:
2584 @rinternals{GraceMusic}.
2589 @cindex acciaccatura, multi-note
2590 @cindex multi-note acciaccatura
2591 @cindex grace-note synchronization
2593 A multi-note beamed @i{acciaccatura} is printed without a slash,
2594 and looks exactly the same as a multi-note beamed
2597 @c TODO Add link to LSR snippet to add slash when available
2599 Grace note synchronization can also lead to surprises. Staff
2600 notation, such as key signatures, bar lines, etc., are also
2601 synchronized. Take care when you mix staves with grace notes and
2602 staves without, for example,
2604 @lilypond[quote,relative=2,verbatim]
2606 \new Staff { e4 \bar "|:" \grace c16 d2. }
2607 \new Staff { c4 \bar "|:" d2. }
2612 This can be remedied by inserting grace skips of the corresponding
2613 durations in the other staves. For the above example
2615 @lilypond[quote,relative=2,verbatim]
2617 \new Staff { e4 \bar "|:" \grace c16 d2. }
2618 \new Staff { c4 \bar "|:" \grace s16 d2. }
2622 Grace sections should only be used within sequential music
2623 expressions. Nesting or juxtaposing grace sections is not
2624 supported, and might produce crashes or other errors.
2626 @node Aligning to cadenzas
2627 @unnumberedsubsubsec Aligning to cadenzas
2630 @cindex cadenza, aligning to
2631 @cindex aligning to cadenza
2633 In an orchestral context, cadenzas present a special problem: when
2634 constructing a score that includes a measured cadenza or other solo
2635 passage, all other instruments should skip just as many notes as the
2636 length of the cadenza, otherwise they will start too soon or too late.
2638 One solution to this problem is to use the functions
2639 @code{mmrest-of-length} and @code{skip-of-length}. These Scheme
2640 functions take a defined piece of music as an argument and generate a
2641 multi-measure rest or @code{\skip} exactly as long as the piece.
2643 @lilypond[verbatim,quote]
2644 MyCadenza = \relative c' {
2655 #(ly:export (mmrest-of-length MyCadenza))
2657 #(ly:export (skip-of-length MyCadenza))
2672 @node Time administration
2673 @unnumberedsubsubsec Time administration
2675 @cindex time administration
2676 @cindex timing (within the score)
2677 @cindex music, unmetered
2678 @cindex unmetered music
2680 @funindex currentBarNumber
2681 @funindex measurePosition
2682 @funindex measureLength
2684 Time is administered by the @code{Timing_translator}, which by
2685 default is to be found in the @code{Score} context. An alias,
2686 @code{Timing}, is added to the context in which the
2687 @code{Timing_translator} is placed.
2689 The following properties of @code{Timing} are used
2690 to keep track of timing within the score.
2693 @cindex measure number
2696 @item currentBarNumber
2697 The current measure number. For an example showing the
2698 use of this property see @ref{Bar numbers}.
2701 The length of the measures in the current time signature. For a
2702 4/4 time this is@tie{}1, and for 6/8 it is 3/4. Its value
2703 determines when bar lines are inserted and how automatic beams
2704 should be generated.
2706 @item measurePosition
2707 The point within the measure where we currently are. This
2708 quantity is reset by subtracting @code{measureLength} whenever
2709 @code{measureLength} is reached or exceeded. When that happens,
2710 @code{currentBarNumber} is incremented.
2713 If set to true, the above variables are updated for every time
2714 step. When set to false, the engraver stays in the current
2715 measure indefinitely.
2719 Timing can be changed by setting any of these variables
2720 explicitly. In the next example, the default 4/4 time
2721 signature is printed, but @code{measureLength} is set to 5/4.
2722 At 4/8 through the third measure, the @code{measurePosition} is
2723 advanced by 1/8 to 5/8, shortening that bar by 1/8.
2724 The next bar line then falls at 9/8 rather than 5/4.
2726 @lilypond[quote,verbatim,relative=1]
2727 \set Score.measureLength = #(ly:make-moment 5 4)
2731 \set Score.measurePosition = #(ly:make-moment 5 8)
2737 As the example illustrates, @code{ly:make-moment n m} constructs a
2738 duration of n/m of a whole note. For example,
2739 @code{ly:make-moment 1 8} is an eighth note duration and
2740 @code{ly:make-moment 7 16} is the duration of seven sixteenths
2747 @ref{Unmetered music}.
2752 Internals Reference:
2753 @rinternals{Timing_translator},