1 @c -*- coding: latin-1; mode: texinfo; -*-
2 @c This file is part of lilypond.tely
4 @c A menu is needed before every deeper *section nesting of @node's; run
5 @c M-x texinfo-all-menus-update
6 @c to automatically fill in these menus before saving changes
9 @chapter Basic notation
11 This chapter explains how to use all basic notation features.
15 * Easier music entry::
29 This section is about basic notation elements like notes, rests, and
30 related constructs, such as stems, tuplets and ties.
35 * Cautionary accidentals::
51 A note is printed by specifying its pitch and then its duration,
53 @lilypond[quote,verbatim,raggedright,fragment]
62 @cindex Note specification
64 @cindex entering notes
66 The most common syntax for pitch entry is used for standard notes and
67 @code{\chordmode} modes. In these modes, pitches may be designated by
68 names. The notes are specified by the letters @code{a} through
69 @code{g}. The octave is formed with notes ranging from @code{c}
70 to @code{b}. The pitch @code{c} is an octave below middle C and the
71 letters span the octave above that C
73 @lilypond[quote,fragment,verbatim]
75 a,4 b, c d e f g a b c' d' e' \clef treble f' g' a' b' c''
81 The optional octave specification takes the form of a series of
82 single quote (`@code{'}') characters or a series of comma
83 (`@code{,}') characters. Each @code{'} raises the pitch by one
84 octave; each @code{,} lowers the pitch by an octave
86 @lilypond[quote,raggedright,fragment,verbatim]
87 c' c'' es' g' as' gisis' ais'
90 @cindex note names, Dutch
92 A sharp is formed by adding @code{-is} to the end of a pitch name and
93 a flat is formed by adding @code{-es}. Double sharps and double flats
94 are obtained by adding @code{-isis} or @code{-eses}. These
95 names are the Dutch note names. In Dutch, @code{aes} is contracted to
96 @code{as}, but both forms are accepted. Similarly, both
97 @code{es} and @code{ees} are accepted
99 @lilypond[fragment,quote,raggedright,verbatim,relative=2]
107 In accordance with standard typsetting rules, a natural sign is printed
108 before a sharp or flat if a previous accidental needs to be
109 cancelled. To change this behaviour, use
110 @code{\set Staff.extraNatural = ##f}
112 @lilypond[fragment,quote,raggedright,verbatim,relative=2]
114 \set Staff.extraNatural = ##f
118 There are predefined sets of note names for various other languages.
119 To use them, include the language specific init file. For
120 example: @code{\include "english.ly"}. The available language files
121 and the note names they define are
126 Note Names sharp flat
127 nederlands.ly c d e f g a bes b -is -es
128 english.ly c d e f g a bf b -s/-sharp -f/-flat
130 deutsch.ly c d e f g a b h -is -es
131 norsk.ly c d e f g a b h -iss/-is -ess/-es
132 svenska.ly c d e f g a b h -iss -ess
133 italiano.ly do re mi fa sol la sib si -d -b
134 catalan.ly do re mi fa sol la sib si -d/-s -b
135 espanol.ly do re mi fa sol la sib si -s -b
141 Program reference: @internalsref{NoteEvent},
142 @internalsref{LedgerLineSpanner}, and @internalsref{NoteHead}.
146 @node Cautionary accidentals
147 @subsection Cautionary accidentals
149 Normally accidentals are printed automatically, but you may also
150 print them manually. A reminder accidental
151 @cindex reminder accidental
153 can be forced by adding an exclamation mark @code{!}
154 after the pitch. A cautionary accidental
155 @cindex cautionary accidental
156 @cindex parenthesized accidental
158 (i.e., an accidental within parentheses) can be obtained by adding the
159 question mark `@code{?}' after the pitch.
161 @lilypond[quote,raggedright,fragment,verbatim]
162 cis' cis' cis'! cis'?
168 The automatic production of accidentals can be tuned in many
169 ways. For more information, refer to @ref{Automatic accidentals}.
174 @subsection Micro tones
176 Half-flats and half-sharps are formed by adding @code{-eh} and
177 @code{-ih}; the following is a series of Cs with increasing pitches
179 @cindex quarter tones
180 @cindex semi-flats, semi-sharps
182 @lilypond[verbatim,raggedright,quote,relative=2,fragment]
183 { ceseh ceh cih cisih }
186 Micro tones are also exported to the MIDI file
191 There are no generally accepted standards for denoting three quarter
192 flats, so LilyPond's symbol does not conform to any standard.
198 A chord is formed by a enclosing a set of pitches in @code{<} and
199 @code{>}. A chord may be followed by a duration, and a set of
200 articulations, just like simple notes
202 @lilypond[verbatim,raggedright,fragment,quote,relative=1]
206 For more information about chords, see @ref{Chord names}.
217 Rests are entered like notes, with the note name @code{r}
219 @lilypond[fragment,quote,raggedright,verbatim]
223 Whole bar rests, centered in middle of the bar,
224 must be done with multi-measure rests. They are discussed in
225 @ref{Multi measure rests}.
228 A rest's vertical position may be explicitly specified by entering a
229 note with the @code{\rest} keyword appended, the rest will be placed at
230 the note's place. This makes manual formatting in polyphonic music
231 easier. Automatic rest collision formatting will leave these rests
234 @lilypond[fragment,quote,raggedright,verbatim]
240 Program reference: @internalsref{RestEvent}, and @internalsref{Rest}.
247 @cindex Invisible rest
252 An invisible rest (also called a `skip') can be entered like a note
253 with note name `@code{s}' or with @code{\skip @var{duration}}
255 @lilypond[fragment,quote,raggedright,verbatim,relative=2]
256 a4 a4 s4 a4 \skip 1 a4
259 The @code{s} syntax is only available in note mode and chord mode. In
260 other situations, for example, when entering lyrics, you should use
261 the @code{\skip} command
263 @lilypond[quote,raggedright,verbatim]
266 \new Lyrics \lyricmode { \skip 2 bla1 }
270 The skip command is merely an empty musical placeholder. It does not
271 produce any output, not even transparent output.
273 The @code{s} skip command does create @internalsref{Staff} and
274 @internalsref{Voice} when necessary, similar to note and rest
275 commands. For example, the following results in an empty staff.
277 @lilypond[quote,raggedright,verbatim]
281 The fragment @code{@{ \skip 4 @} } would produce an empty page.
285 Program reference: @internalsref{SkipEvent}, @internalsref{SkipMusic}.
290 @subsection Durations
294 @cindex @code{\longa}
295 @cindex @code{\breve}
296 @cindex @code{\maxima}
299 In Note, Chord, and Lyrics mode, durations are designated by numbers and
300 dots: durations are entered as their reciprocal values. For example, a
301 quarter note is entered using a @code{4} (since it is a 1/4 note), while
302 a half note is entered using a @code{2} (since it is a 1/2 note). For
303 notes longer than a whole you must use the variables @code{\longa} and
308 c'1 c'2 c'4 c'8 c'16 c'32 c'64 c'64
310 r1 r2 r4 r8 r16 r32 r64 r64
316 a\breve*1/2 \autoBeamOff
317 a1 a2 a4 a8 a16 a32 a64 a64
320 r\longa*1/4 r\breve *1/2
321 r1 r2 r4 r8 r16 r32 r64 r64
327 \remove "Clef_engraver"
328 \override StaffSymbol #'transparent = ##t
329 \override TimeSignature #'transparent = ##t
330 \override BarLine #'transparent = ##t
331 \consists "Pitch_squash_engraver"
337 If the duration is omitted then it is set to the previously entered
338 duration. The default for the first note is a quarter note.
340 @lilypond[quote,raggedright,verbatim,fragment]
341 { a a a2 a a4 a a1 a }
346 @node Augmentation dots
347 @subsection Augmentation dots
350 To obtain dotted note lenghts, simply add a dot (`@code{.}') to
351 the number. Double-dotted notes are produced in a similar way.
353 @lilypond[quote,raggedright,fragment,verbatim]
354 a'4 b' c''4. b'8 a'4. b'4.. c''8.
359 Dots are normally moved up to avoid staff lines, except in polyphonic
360 situations. The following commands may be used to force a particular
363 @cindex @code{\dotsUp}
365 @cindex @code{\dotsDown}
367 @cindex @code{\dotsNeutral}
372 Program reference: @internalsref{Dots}, and @internalsref{DotColumn}.
380 @cindex @code{\times}
382 Tuplets are made out of a music expression by multiplying all durations
385 @cindex @code{\times}
387 \times @var{fraction} @var{musicexpr}
391 The duration of @var{musicexpr} will be multiplied by the fraction.
392 The fraction's denominator will be printed over the notes, optionally
393 with a bracket. The most common tuplet is the triplet in which 3
394 notes have the length of 2, so the notes are 2/3 of their written
397 @lilypond[quote,raggedright,fragment,verbatim]
398 g'4 \times 2/3 {c'4 c' c'} d'4 d'4
401 The property @code{tupletSpannerDuration} specifies how long each
402 bracket should last. With this, you can make lots of tuplets while
403 typing @code{\times} only once, thus saving lots of typing. In the next
404 example, there are two triplets shown, while @code{\times} was only
407 @lilypond[quote,fragment,relative=1,raggedright,verbatim]
408 \set tupletSpannerDuration = #(ly:make-moment 1 4)
409 \times 2/3 { c'8 c c c c c }
412 The format of the number is determined by the property
413 @code{tupletNumberFormatFunction}. The default prints only the
414 denominator, but if it is set to the Scheme function
415 @code{fraction-tuplet-formatter}, @var{num}:@var{den} will be printed
418 @cindex @code{tupletNumberFormatFunction}
419 @cindex tuplet formatting
423 @cindex @code{\tupletUp}
425 @cindex @code{\tupletDown}
427 @cindex @code{\tupletNeutral}
428 @code{\tupletNeutral}.
432 User manual: @ref{Changing context properties on the fly} for the
436 Program reference: @internalsref{TupletBracket}, and @internalsref{TimeScaledMusic}.
438 Examples: @inputfileref{input/@/regression,tuplet@/-nest@/.ly}.
442 Nested tuplets are not formatted automatically. In this case, outer
443 tuplet brackets should be moved manually, which is demonstrated in
444 @inputfileref{input/@/regression,tuplet@/-nest@/.ly}.
447 @node Scaling durations
448 @subsection Scaling durations
450 You can alter the length of duration by a fraction @var{N/M}
451 appending `@code{*}@var{N/M}' (or `@code{*}@var{N}' if @var{M=1}). This
452 will not affect the appearance of the notes or rests produced.
454 In the following example, the first three notes take up exactly two
455 beats, but no triplet bracket is printed.
456 @lilypond[quote,raggedright,fragment,relative=2,verbatim]
458 a4*2/3 gis4*2/3 a4*2/3
466 This manual: @ref{Tuplets}
469 @node Easier music entry
470 @section Easier music entry
473 This section deals with tricks and features of the input language that
474 were added solely to help entering music and finding and correcting
475 mistakes. There are also external tools that make debugging easier.
476 See @ref{Point and click} for more information.
478 It is also possible to enter and edit music using other programs, such as
479 GUI interfaces or MIDI sequencers. Refer to the LilyPond
480 website for more information.
487 * Skipping corrected music::
488 * Automatic note splitting::
494 @node Relative octaves
495 @subsection Relative octaves
497 @cindex relative octave specification
499 Octaves are specified by adding @code{'} and @code{,} to pitch names.
500 When you copy existing music, it is easy to accidentally put a pitch
501 in the wrong octave and hard to find such an error. The relative
502 octave mode prevents these errors by making the mistakes much
503 larger: a single error puts the rest of the piece off by one octave
505 @cindex @code{\relative}
507 \relative @var{startpitch} @var{musicexpr}
514 \relative @var{musicexpr}
517 The octave of notes that appear in @var{musicexpr} are calculated as
518 follows: if no octave changing marks are used, the basic interval
519 between this and the last note is always taken to be a fourth or
520 less. This distance is determined without regarding alterations; a
521 @code{fisis} following a @code{ceses} will be put above the
522 @code{ceses}. In other words, a doubly-augmented fourth is considered
523 a smaller interval than a diminshed fifth, even though the fourth is
524 seven semitones while the fifth is only six semitones.
526 The octave changing marks @code{'} and @code{,} can be added to raise
527 or lower the pitch by an extra octave. Upon entering relative mode,
528 an absolute starting pitch can be specified that will act as the
529 predecessor of the first note of @var{musicexpr}. If no starting pitch
530 is specified, then middle C is used as a start.
532 Here is the relative mode shown in action
533 @lilypond[quote,fragment,raggedright,verbatim]
539 Octave changing marks are used for intervals greater than a fourth
540 @lilypond[quote,raggedright,fragment,verbatim]
546 If the preceding item is a chord, the first note of the chord is used
547 to determine the first note of the next chord
549 @lilypond[quote,raggedright,fragment,verbatim]
557 The pitch after the @code{\relative} contains a note name.
560 The relative conversion will not affect @code{\transpose},
561 @code{\chordmode} or @code{\relative} sections in its argument. To use
562 relative within transposed music, an additional @code{\relative} must
563 be placed inside @code{\transpose}.
566 @subsection Octave check
569 Octave checks make octave errors easier to correct: a note may be
570 followed by @code{=}@var{quotes} which indicates what its absolute
571 octave should be. In the following example,
573 \relative c'' @{ c='' b=' d,='' @}
577 @c take care with @code, adds confusing quotes.
578 the @code{d} will generate a warning, because a @code{d''} is expected
579 (because @code{b'} to @code{d''} is only a third), but a @code{d}' is
580 found. In the output, the octave is corrected to be a @code{d''} and
581 the next note is calculated relative to @code{d''} instead of @code{d'}.
585 There is also a syntax that is separate from the notes. The syntax
591 This checks that @var{pitch} (without quotes) yields @var{pitch} (with
592 quotes) in \relative mode. If not, a warning is printed, and the
595 In the example below, the first check passes without incident, since
596 the @code{e} (in relative mode) is within a fifth of @code{a'}. However,
597 the second check produces a warning, since the @code{e} is not within
598 a fifth of @code{b'}. The warning message is printed, and the octave
599 is adjusted so that the following notes are in the correct octave
611 The octave of a note following an octave check is determined with
612 respect to the note preceding it. In the next fragment, the last note
613 is a @code{a'}, above middle C. That means that the @code{\octave}
614 check passes successfully, so the check could be deleted without changing
615 the output of the piece.
617 @lilypond[quote,raggedright,verbatim,fragment]
626 @subsection Bar check
630 @cindex @code{barCheckSynchronize}
633 Bar checks help detect errors in the durations. A bar check is
634 entered using the bar symbol, `@code{|}'. Whenever it is encountered
635 during interpretation, it should fall on a measure boundary. If it
636 does not, a warning is printed. In the next example, the second bar
637 check will signal an error
639 \time 3/4 c2 e4 | g2 |
642 Bar checks can also be used in lyrics, for example
647 Twin -- kle | Twin -- kle
652 @cindex @code{skipTypesetting}
654 Failed bar checks are caused by entering incorrect
655 durations. Incorrect durations often completely garble up the score,
656 especially if the score is polyphonic, so a good place to start correcting
657 input is by scanning for failed bar checks and incorrect durations. To
658 speed up this process, the @code{skipTypesetting} feature may be
659 used. It is described in the next section.
662 @cindex @code{pipeSymbol}
664 It is also possible to redefine the meaning of @code{|}. This is done
665 by assigning a music expression to @code{pipeSymbol},
667 @lilypond[quote,raggedright,verbatim]
668 pipeSymbol = \bar "||"
674 @node Skipping corrected music
675 @subsection Skipping corrected music
677 The property @code{Score.skipTypesetting} can be used to switch on and
678 off typesetting completely during the interpretation phase. When
679 typesetting is switched off, the music is processed much more
680 quickly. This can be used to skip over the parts of a score that
681 have already been checked for errors
683 @lilypond[quote,fragment,raggedright,verbatim]
686 \set Score.skipTypesetting = ##t
688 \set Score.skipTypesetting = ##f
692 In polyphonic music, @code{Score.skipTypesetting} will affect all
693 voices and staves, saving even more time.
695 @node Automatic note splitting
696 @subsection Automatic note splitting
698 Long notes can be converted automatically to tied notes. This is done
699 by replacing the @internalsref{Note_heads_engraver} by the
700 @internalsref{Completion_heads_engraver}.
701 In the following examples, notes crossing the bar line are split and tied.
704 @lilypond[quote,fragment,verbatim,relative=1,linewidth=12\cm]
706 \remove "Note_heads_engraver"
707 \consists "Completion_heads_engraver"
709 c2. c8 d4 e f g a b c8 c2 b4 a g16 f4 e d c8. c2
713 This engraver splits all running notes at the bar line, and inserts
714 ties. One of its uses is to debug complex scores: if the measures are
715 not entirely filled, then the ties exactly show how much each measure
720 Not all durations (especially those containing tuplets) can be
721 represented exactly with normal notes and dots, but the engraver will
724 @code{Completion_heads_engraver} only affects notes; it does not split
730 Examples: @inputfileref{input/@/regression,completion@/-heads@/.ly}.
734 Program reference: @internalsref{Completion_heads_engraver}.
740 @section Staff notation
742 This section describes music notation that occurs on staff level,
743 such as key signatures, clefs and time signatures.
745 @cindex Staff notation
755 * System start delimiters::
760 @subsection Staff symbol
762 @cindex adjusting staff symbol
764 Notes, dynamic signs, etc., are grouped
765 with a set of horizontal lines, into a staff (plural `staves'). In our
766 system, these lines are drawn using a separate layout object called
769 The staff symbol may be tuned in the number, thickness and distannce
770 of lines, using properties. This is demonstrated in the example files
771 @inputfileref{input/@/test,staff@/-lines@/.ly},
772 @inputfileref{input/@/test,staff@/-size@/.ly}.
774 In addition, staves may be started and stopped at will. This is done
775 with @code{\startStaff} and @code{\stopStaff}.
777 @lilypond[verbatim,relative=2,fragment]
779 \override Staff.StaffSymbol #'line-count = 2
780 \stopStaff \startStaff
782 \revert Staff.StaffSymbol #'line-count
783 \stopStaff \startStaff
787 In combination with Frenched staves, this may be used to typeset ossia
788 sections. An example is in @inputfileref{input/@/test@/,ossia.ly},
793 @lilypondfile{ossia.ly}
795 @cindex staff lines, setting number of
796 @cindex staff lines, setting thickness of
797 @cindex thickness of staff lines, setting
798 @cindex number of staff lines, setting
802 Program reference: @internalsref{StaffSymbol}, @internalsref{StaffSpanEvent}.
804 Examples: @inputfileref{input/@/test,staff@/-lines@/.ly},
805 @inputfileref{input/@/test@/,ossia.ly},
806 @inputfileref{input/@/test,staff@/-size@/.ly}.
810 @subsection Key signature
811 @cindex Key signature
815 The key signature indicates the tonality in which a piece is played. It
816 is denoted by a set of alterations (flats or sharps) at the start of the
820 Setting or changing the key signature is done with the @code{\key}
823 @code{\key} @var{pitch} @var{type}
826 @cindex @code{\minor}
827 @cindex @code{\major}
828 @cindex @code{\minor}
829 @cindex @code{\ionian}
830 @cindex @code{\locrian}
831 @cindex @code{\aeolian}
832 @cindex @code{\mixolydian}
833 @cindex @code{\lydian}
834 @cindex @code{\phrygian}
835 @cindex @code{\dorian}
837 Here, @var{type} should be @code{\major} or @code{\minor} to get
838 @var{pitch}-major or @var{pitch}-minor, respectively.
839 The standard mode names @code{\ionian},
840 @code{\locrian}, @code{\aeolian}, @code{\mixolydian}, @code{\lydian},
841 @code{\phrygian}, and @code{\dorian} are also defined.
843 This command sets the context property
844 @internalsref{Staff}.@code{keySignature}. Non-standard key signatures
845 can be specified by setting this property directly.
847 A natural sign is printed to cancel any previous accidentals. This
848 can be suppressed by setting the @code{Staff.printKeyCancellation}
851 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
857 \set Staff.printKeyCancellation = ##f
865 Accidentals and key signatures often confuse new users, because
866 unaltered notes get natural signs depending on the key signature. For
867 more information, see @ref{More about pitches}.
871 Program reference: @internalsref{KeyChangeEvent},
872 @internalsref{KeyCancellation} and @internalsref{KeySignature}.
874 @cindex @code{keySignature}
881 The clef indicates which lines of the staff correspond to which
885 The clef can be set with the @code{\clef} command
886 @lilypond[quote,raggedright,fragment,verbatim]
887 { c''2 \clef alto g'2 }
890 Supported clef-names include
891 @c Moved standard clefs to the top /MB
895 @item treble, violin, G, G2
908 G clef on 1st line, so-called French violin clef
913 @cindex mezzosoprano clef
916 @cindex baritone clef
919 @cindex varbaritone clef
930 By adding @code{_8} or @code{^8} to the clef name, the clef is
931 transposed one octave down or up, respectively, and @code{_15} and
932 @code{^15} transposes by two octaves. The argument @var{clefname}
933 must be enclosed in quotes when it contains underscores or digits. For
937 @cindex choral tenor clef
938 @lilypond[quote,raggedright,verbatim,fragment,relative=1]
942 This command is equivalent to setting @code{clefGlyph},
943 @code{clefPosition} (which controls the Y position of the clef),
944 @code{middleCPosition} and @code{clefOctavation}. A clef is printed
945 when any of these properties are changed. The following example shows
946 possibilities when setting properties manually.
948 @lilypond[quote,raggedright,verbatim]
950 \set Staff.clefGlyph = #"clefs.F"
951 \set Staff.clefPosition = #2
953 \set Staff.clefGlyph = #"clefs.G"
955 \set Staff.clefGlyph = #"clefs.C"
957 \set Staff.clefOctavation = #7
959 \set Staff.clefOctavation = #0
960 \set Staff.clefPosition = #0
964 \set Staff.middleCPosition = #4
971 Program reference: @internalsref{Clef}.
978 @subsection Time signature
979 @cindex Time signature
983 Time signature indicates the metrum of a piece: a regular pattern of
984 strong and weak beats. It is denoted by a fraction at the start of the
988 The time signature is set or changed by the @code{\time}
990 @lilypond[quote,raggedright,fragment,verbatim]
991 \time 2/4 c'2 \time 3/4 c'2.
994 The symbol that is printed can be customized with the @code{style}
995 property. Setting it to @code{#'()} uses fraction style for 4/4 and
998 @lilypond[fragment,quote,raggedright,verbatim]
1001 \override Staff.TimeSignature #'style = #'()
1008 There are many more options for its layout. See @ref{Ancient time
1009 signatures} for more examples.
1012 This command sets the property @code{timeSignatureFraction},
1013 @code{beatLength} and @code{measureLength} in the @code{Timing}
1014 context, which is normally aliased to @internalsref{Score}. The
1015 property @code{measureLength} determines where bar lines should be
1016 inserted, and how automatic beams should be generated. Changing the
1017 value of @code{timeSignatureFraction} also causes the symbol to be
1020 More options are available through the Scheme function
1021 @code{set-time-signature}. In combination with the
1022 @internalsref{Measure_grouping_engraver}, it will create
1023 @internalsref{MeasureGrouping} signs. Such signs ease reading
1024 rhythmically complex modern music. In the following example, the 9/8
1025 measure is subdivided in 2, 2, 2 and 3. This is passed to
1026 @code{set-time-signature} as the third argument @code{(2 2 2 3)}
1028 @lilypond[quote,raggedright,verbatim]
1031 #(set-time-signature 9 8 '(2 2 2 3))
1032 g8[ g] d[ d] g[ g] a8[( bes g]) |
1033 #(set-time-signature 5 8 '(3 2))
1039 \consists "Measure_grouping_engraver"
1047 Program reference: @internalsref{TimeSignature}, and @internalsref{Timing_engraver}.
1052 Automatic beaming does not use the measure grouping specified with
1053 @code{set-time-signature}.
1055 @node Partial measures
1056 @subsection Partial measures
1059 @cindex partial measure
1060 @cindex measure, partial
1061 @cindex shorten measures
1062 @cindex @code{\partial}
1064 Partial measures, for example in upsteps, are entered using the
1065 @code{\partial} command
1066 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
1067 \partial 16*5 c16 cis d dis e | a2. c,4 | b2
1070 The syntax for this command is
1072 \partial @var{duration}
1074 This is internally translated into
1076 \set Timing.measurePosition = -@var{length of duration}
1079 The property @code{measurePosition} contains a rational number
1080 indicating how much of the measure has passed at this point.
1084 This command does not take into account grace notes at the start of
1085 the music. When a piece starts with graces notes in the pickup, then
1086 the @code{\partial} should follow the grace notes
1088 @lilypond[verbatim,quote,raggedright,relative,fragment]
1098 @node Unmetered music
1099 @subsection Unmetered music
1103 Bar lines and bar numbers are calculated automatically. For unmetered
1104 music (cadenzas, for example), this is not desirable. By setting
1105 @code{Score.timing} to false, this automatic timing can be switched
1106 off. Empty bar lines,
1113 indicate where line breaks can occur.
1117 @cindex @code{\cadenzaOn}
1119 @cindex @code{\cadenzaOff}
1126 @subsection Bar lines
1130 @cindex measure lines
1134 Bar lines delimit measures, but are also used to indicate repeats.
1135 Normally, they are inserted automatically. Line breaks may only
1136 happen on bar lines.
1138 Special types of bar lines can be forced with the @code{\bar} command
1140 @lilypond[quote,raggedright,relative=2,fragment,verbatim]
1144 The following bar types are available
1145 @lilypondfile[raggedright,quote]{bar-lines.ly}
1147 For allowing line breaks, there is a special command,
1151 This will insert an invisible bar line, and allow line breaks at this
1154 In scores with many staves, a @code{\bar} command in one staff is
1155 automatically applied to all staves. The resulting bar lines are
1156 connected between different staves of a @internalsref{StaffGroup}
1158 @lilypond[quote,raggedright,fragment,verbatim]
1160 \context StaffGroup <<
1166 \new Staff { \clef bass c4 g e g }
1168 \new Staff { \clef bass c2 c2 }
1173 The command @code{\bar }@var{bartype} is a short cut for doing
1174 @code{\set Timing.whichBar = }@var{bartype}. Whenever @code{whichBar}
1175 is set to a string, a bar line of that type is created.
1177 A bar line is created whenever the @code{whichBar} property is set.
1178 At the start of a measure it is set to the contents of
1179 @code{Timing.defaultBarType}. The contents of @code{repeatCommands} are used
1180 to override default measure bars.
1182 @cindex @code{whichBar}
1183 @cindex @code{repeatCommands}
1184 @cindex @code{defaultBarType}
1186 You are encouraged to use @code{\repeat} for repetitions. See
1193 In this manual: @ref{Repeats}, @ref{System start delimiters}.
1196 Program reference: @internalsref{BarLine} (created at
1197 @internalsref{Staff} level), @internalsref{SpanBar} (across staves).
1199 @cindex bar lines at start of system
1200 @cindex start of system
1204 Examples: @inputfileref{input/@/test,bar@/-lines@/.ly},
1208 @node System start delimiters
1209 @subsection System start delimiters
1211 Many scores consist of more than one staff. These staves can be
1212 joined in three different ways
1214 @item The group is started with a brace at the left, and bar lines are
1215 connected. This is done with the @internalsref{GrandStaff} context.
1217 @lilypond[verbatim,raggedright,quote]
1226 @item The group is started with a bracket, and bar lines are connected.
1227 This is done with the
1228 @internalsref{StaffGroup} context
1230 @lilypond[verbatim,raggedright,quote]
1239 @item The group is started with a vertical line. Bar lines are not
1240 connected. This is the default for the score.
1242 @lilypond[verbatim,raggedright,quote]
1251 @cindex Staff, multiple
1252 @cindex bracket, vertical
1253 @cindex brace, vertical
1260 The bar lines at the start of each system are
1261 @internalsref{SystemStartBar}, @internalsref{SystemStartBrace}, and
1262 @internalsref{SystemStartBracket}. Only one of these types is created
1263 in every context, and that type is determined by the property
1264 @code{systemStartDelimiter}.
1267 @node More than notes
1268 @section More than notes
1269 @c silly title; should change.
1271 This section deals with notation that affects more than one note.
1278 * Fingering instructions::
1288 A tie connects two adjacent note heads of the same pitch. The tie in
1289 effect extends the length of a note. Ties should not be confused with
1290 slurs, which indicate articulation, or phrasing slurs, which indicate
1291 musical phrasing. A tie is entered using the tilde symbol `@code{~}'
1293 @lilypond[quote,raggedright,fragment,verbatim]
1294 e' ~ e' <c' e' g'> ~ <c' e' g'>
1297 When a tie is applied to a chord, all note heads whose pitches match
1298 are connected. When no note heads match, no ties will be created.
1300 A tie is just a way of extending a note duration, similar to the
1301 augmentation dot. The following example shows two ways of notating
1302 exactly the same concept
1304 @lilypond[quote,fragment,raggedright]
1305 \time 3/4 c'2. c'2 ~ c'4
1309 Ties are used either when the note crosses a bar line, or when dots
1310 cannot be used to denote the rhythm. When using ties, larger note
1311 values should be aligned to subdivisions of the measure, eg.
1313 @lilypond[fragment,quote,raggedright]
1315 r8 c8 ~ c2 r4 | r8^"not" c2 ~ c8 r4
1319 If you need to tie a lot of notes over bars, it may be easier to use
1320 automatic note splitting (see @ref{Automatic note splitting}). This
1321 mechanism automatically splits long notes, and ties them across bar
1324 Ties are sometimes used to write out arpeggios. In this case, two tied
1325 notes need not be consecutive. This can be achieved by setting the
1326 @code{tieWaitForNote} property to true. For example,
1328 @lilypond[fragment,verbatim,relative=1,raggedright]
1329 \set tieWaitForNote = ##t
1330 \grace { c16[~ e~ g]~ } <c, e g>4
1337 @cindex @code{\tieUp}
1339 @cindex @code{\tieDown}
1341 @cindex @code{\tieNeutral}
1343 @cindex @code{\tieDotted}
1345 @cindex @code{\tieSolid}
1350 In this manual: @ref{Automatic note splitting}.
1352 Program reference: @internalsref{TieEvent}, @internalsref{Tie}.
1357 Switching staves when a tie is active will not produce a slanted tie.
1359 Formatting of ties is a difficult subject. The results are often not
1363 @node Automatic beams
1364 @subsection Automatic beams
1366 LilyPond inserts beams automatically
1368 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
1369 \time 2/4 c8 c c c \time 6/8 c c c c8. c16 c8
1372 When these automatic decisions are not good enough, beaming can be
1373 entered explicitly. It is also possible to define beaming patterns
1374 that differ from the defaults. See @ref{Setting automatic beam behavior}
1377 Individual notes may be marked with @code{\noBeam}, to prevent them
1380 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
1381 \time 2/4 c8 c\noBeam c c
1387 Program reference: @internalsref{Beam}.
1391 @subsection Manual beams
1392 @cindex beams, manual
1396 In some cases it may be necessary to override the automatic beaming
1397 algorithm. For example, the autobeamer will not put beams over rests
1398 or bar lines. Such beams are specified manually by marking the begin
1399 and end point with @code{[} and @code{]}
1401 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
1403 r4 r8[ g' a r8] r8 g[ | a] r8
1407 @cindex @code{stemLeftBeamCount}
1409 Normally, beaming patterns within a beam are determined automatically.
1410 If necessary, the properties @code{stemLeftBeamCount} and
1411 @code{stemRightBeamCount} can be used to override the defaults. If
1412 either property is set, its value will be used only once, and then it
1415 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
1420 \set stemLeftBeamCount = #1
1424 @cindex @code{stemRightBeamCount}
1427 The property @code{subdivideBeams} can be set in order to subdivide
1428 all 16th or shorter beams at beat positions, as defined by the
1429 @code{beatLength} property.
1432 @lilypond[fragment,quote,relative=2,verbatim]
1434 \set subdivideBeams = ##t
1436 \set Score.beatLength = #(ly:make-moment 1 8)
1439 @cindex @code{subdivideBeams}
1441 Normally, line breaks are forbidden when beams cross bar lines. This
1442 behavior can be changed by setting @code{allowBeamBreak}.
1444 @cindex @code{allowBeamBreak}
1445 @cindex beams and line breaks
1447 @cindex beams, kneed
1449 @cindex auto-knee-gap
1454 User manual: @ref{Changing context properties on the fly} for the
1460 @cindex Frenched staves
1461 Kneed beams are inserted automatically, when a large gap is detected
1462 between the note heads. This behavior can be tuned through the object.
1465 Automatically kneed cross-staff beams cannot be used together with
1466 hidden staves. See @ref{Hiding staves}.
1468 Beams do not avoid collisions with symbols around the notes, such as
1469 texts and accidentals.
1475 @subsection Grace notes
1477 @cindex @code{\grace}
1481 Grace notes are ornaments that are written out. The most common ones
1482 are acciaccatura, which should be played as very short. It is denoted
1483 by a slurred small note with a slashed stem. The appoggiatura is a
1484 grace note that takes a fixed fraction of the main note, and is
1485 denoted as a slurred note in small print without a slash. They
1486 are entered with the commands @code{\acciaccatura} and
1487 @code{\appoggiatura}, as demonstrated in the following example
1490 @cindex appoggiatura
1491 @cindex acciaccatura
1493 @lilypond[quote,raggedright,relative=2,verbatim,fragment]
1494 b4 \acciaccatura d8 c4 \appoggiatura e8 d4
1495 \acciaccatura { g16[ f] } e4
1498 Both are special forms of the @code{\grace} command. By prefixing this
1499 keyword to a music expression, a new one is formed, which will be
1500 printed in a smaller font and takes up no logical time in a measure.
1502 @lilypond[quote,raggedright,relative=2,verbatim,fragment]
1504 \grace { c16[ d16] } c2 c4
1508 Unlike @code{\acciaccatura} and @code{\appoggiatura}, the
1509 @code{\grace} command does not start a slur.
1511 Internally, timing for grace notes is done using a second, `grace'
1512 timing. Every point in time consists of two rational numbers: one
1513 denotes the logical time, one denotes the grace timing. The above
1514 example is shown here with timing tuples
1516 @lilypond[quote,raggedright]
1519 c4 \grace c16 c4 \grace {
1522 \new Lyrics \lyricmode {
1523 \override LyricText #'font-family = #'typewriter
1527 ( \fraction 1 4 , \fraction -1 16 ) } 16 }
1528 \markup { (\fraction 1 4 , 0 ) } 4
1530 \markup { (\fraction 2 4 , \fraction "-1" 8 ) } 16
1531 \markup { (\fraction 2 4 , \fraction "-1" 16 ) } 16
1533 \markup { ( \fraction 2 4 , 0 ) }
1539 The placement of grace notes is synchronized between different staves.
1540 In the following example, there are two sixteenth grace notes for
1541 every eighth grace note
1543 @lilypond[quote,raggedright,relative=2,verbatim,fragment]
1544 << \new Staff { e4 \grace { c16[ d e f] } e4 }
1545 \new Staff { c4 \grace { g8[ b] } c4 } >>
1550 If you want to end a note with a grace, use the @code{\afterGrace}
1551 command. It takes two arguments: the main note, and the grace notes
1552 following the main note.
1554 @lilypond[raggedright, verbatim,relative=2,fragment]
1555 c1 \afterGrace d1 { c16[ d] } c4
1558 This will put the grace notes after a ``space'' lasting 3/4 of the
1559 length of the main note. The fraction 3/4 can be changed by setting
1560 @code{afterGraceFraction}, ie.
1563 afterGraceFraction = #(cons 7 8)
1567 will put the grace note at 7/8 of the main note.
1570 The same effect can be achieved manually by doing
1573 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
1576 { s2 \grace { c16[ d] } } >>
1582 By adjusting the duration of the skip note (here it is a half-note),
1583 the space between the main-note and the grace is adjusted.
1588 A @code{\grace} section will introduce special typesetting settings,
1589 for example, to produce smaller type, and set directions. Hence, when
1590 introducing layout tweaks, they should be inside the grace section,
1592 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
1604 The overrides should also be reverted inside the grace section.
1606 The layout of grace sections can be changed throughout the music using
1607 the function @code{add-grace-property}. The following example
1608 undefines the Stem direction for this grace, so stems do not always
1613 #(add-grace-property 'Voice 'Stem 'direction '())
1619 Another option is to change the variables @code{startGraceMusic},
1620 @code{stopGraceMusic}, @code{startAcciaccaturaMusic},
1621 @code{stopAcciaccaturaMusic}, @code{startAppoggiaturaMusic},
1622 @code{stopAppoggiaturaMusic}. More information is in the file
1623 @file{ly/@/grace@/-init@/.ly}.
1628 Program reference: @internalsref{GraceMusic}.
1632 A score that starts with a @code{\grace} section needs an explicit
1633 @code{\context Voice} declaration, otherwise the main note and the grace
1634 note end up on different staves.
1636 Grace note synchronization can also lead to surprises. Staff notation,
1637 such as key signatures, bar lines, etc., are also synchronized. Take
1638 care when you mix staves with grace notes and staves without, for example,
1640 @lilypond[quote,raggedright,relative=2,verbatim,fragment]
1641 << \new Staff { e4 \bar "|:" \grace c16 d4 }
1642 \new Staff { c4 \bar "|:" d4 } >>
1646 This can be remedied by inserting grace skips, for the above example
1649 \new Staff @{ c4 \bar "|:" \grace s16 d4 @}
1652 Grace sections should only be used within sequential music
1653 expressions. Nesting or juxtaposing grace sections is not supported,
1654 and might produce crashes or other errors.
1657 @node Fingering instructions
1658 @subsection Fingering instructions
1662 Fingering instructions can be entered using
1664 @var{note}-@var{digit}
1666 For finger changes, use markup texts
1668 @lilypond[quote,verbatim,raggedright,fragment,relative=1]
1670 c^\markup { \finger "2-3" }
1673 @cindex finger change
1678 You can use the thumb-script to indicate that a note should be
1679 played with the thumb (e.g., in cello music)
1680 @lilypond[quote,verbatim,raggedright,fragment,relative=2]
1681 <a_\thumb a'-3>8 <b_\thumb b'-3>
1684 Fingerings for chords can also be added to individual notes
1685 of the chord by adding them after the pitches
1686 @lilypond[quote,verbatim,raggedright,fragment,relative=2]
1687 < c-1 e-2 g-3 b-5 >4
1691 In this case, setting @code{fingeringOrientations} will put fingerings next
1694 @lilypond[quote,verbatim,raggedright,fragment,relative=1]
1695 \set fingeringOrientations = #'(left down)
1696 <c-1 es-2 g-4 bes-5 > 4
1697 \set fingeringOrientations = #'(up right down)
1698 <c-1 es-2 g-4 bes-5 > 4
1701 Using this feature, it is also possible to put fingering instructions
1702 very close to note heads in monophonic music,
1704 @lilypond[verbatim,raggedright,quote,fragment]
1705 \set fingeringOrientations = #'(right)
1712 Program reference: @internalsref{FingerEvent}, and @internalsref{Fingering}.
1714 Examples: @inputfileref{input/@/regression,finger@/-chords@/.ly}.
1719 @node Expressive marks
1720 @section Expressive marks
1722 Expressive marks help musicians to bring more to the music than simple
1741 A slur indicates that notes are to be played bound or @emph{legato}.
1743 They are entered using parentheses
1744 @lilypond[quote,raggedright,relative=2,fragment,verbatim]
1745 f( g a) a8 b( a4 g2 f4)
1749 The direction of a slur can be set with the
1753 \override Slur #'direction = #UP
1754 \slurUp % shortcut for the previous line
1758 However, there is a convenient shorthand for forcing slur
1759 directions. By adding @code{_} or @code{^} before the opening
1760 parentheses, the direction is also set. For example,
1762 @lilypond[relative=2,raggedright,quote,verbatim,fragment]
1766 Some composers write two slurs when they want legato chords. This can
1767 be achieved in LilyPond by setting @code{doubleSlurs},
1769 @lilypond[verbatim,raggedright,relative,fragment,quote]
1770 \set doubleSlurs = ##t
1771 <c e>4 ( <d f> <c e> <d f> )
1774 Only one slur can be printed at once. If you need to print a long
1775 slur over a few small slurs, please see @ref{Phrasing slurs}.
1781 @cindex @code{\slurUp}
1783 @cindex @code{\slurDown}
1785 @cindex @code{\slurNeutral}
1786 @code{\slurNeutral},
1787 @cindex @code{\slurDashed}
1789 @cindex @code{\slurDotted}
1791 @cindex @code{\slurSolid}
1796 Program reference: @seeinternals{Slur}, and @internalsref{SlurEvent}.
1799 @node Phrasing slurs
1800 @subsection Phrasing slurs
1802 @cindex phrasing slurs
1803 @cindex phrasing marks
1805 A phrasing slur (or phrasing mark) connects chords and is used to
1806 indicate a musical sentence. It is written using @code{\(} and @code{\)}
1809 @lilypond[quote,raggedright,fragment,verbatim,relative=1]
1810 \time 6/4 c'\( d( e) f( e) d\)
1813 Typographically, the phrasing slur behaves almost exactly like a
1814 normal slur. However, they are treated as different objects. A
1815 @code{\slurUp} will have no effect on a phrasing slur; instead, use
1816 @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
1817 @code{\phrasingSlurNeutral}.
1819 The commands @code{\slurUp}, @code{\slurDown}, and @code{\slurNeutral}
1820 will only affect normal slurs and not phrasing slurs.
1822 You cannot have simultaneous phrasing slurs.
1826 @cindex @code{\phrasingSlurUp}
1827 @code{\phrasingSlurUp},
1828 @cindex @code{\phrasingSlurDown}
1829 @code{\phrasingSlurDown},
1830 @cindex @code{\phrasingSlurNeutral}
1831 @code{\phrasingSlurNeutral}.
1835 Program reference: see also @internalsref{PhrasingSlur}, and
1836 @internalsref{PhrasingSlurEvent}.
1840 Putting phrasing slurs over rests leads to spurious warnings.
1844 @subsection Articulations
1845 @cindex Articulations
1847 @cindex articulations
1851 A variety of symbols can appear above and below notes to indicate
1852 different characteristics of the performance. They are added to a note
1853 by adding a dash and the character signifying the
1854 articulation. They are demonstrated here
1856 @lilypondfile[quote,raggedright]{script-abbreviations.ly}
1858 The meanings of these shorthands can be changed. See
1859 @file{ly/@/script@/-init@/.ly} for examples.
1862 The script is automatically placed, but the direction can be forced as
1863 well. Like other pieces of LilyPond code, @code{_} will place them
1864 below the staff, and @code{^} will place them above.
1867 @lilypond[quote,raggedright,fragment,verbatim]
1871 Other symbols can be added using the syntax
1872 @var{note}@code{\}@var{name}. Again, they
1873 can be forced up or down using @code{^} and @code{_},
1876 @lilypond[quote,raggedright,verbatim,fragment,relative=2]
1877 c\fermata c^\fermata c_\fermata
1884 @cindex staccatissimo
1894 @cindex organ pedal marks
1903 @cindex prallmordent
1907 @cindex thumb marking
1912 Here is a chart showing all scripts available,
1914 @lilypondfile[raggedright,quote]{script-chart.ly}
1917 The vertical ordering of scripts is controlled with the
1918 @code{script-priority} property. The lower this number, the closer it
1919 will be put to the note. In this example, the
1920 @internalsref{TextScript} (the sharp symbol) first has the lowest
1921 priority, so it is put lowest in the first example. In the second, the
1922 prall trill (the @internalsref{Script}) has the lowest, so it is on the
1923 inside. When two objects have the same priority, the order in which
1924 they are entered decides which one comes first.
1927 @lilypond[verbatim,relative=3,raggedright,fragment,quote]
1928 \once \override TextScript #'script-priority = #-100
1929 a4^\prall^\markup { \sharp }
1931 \once \override Script #'script-priority = #-100
1932 a4^\prall^\markup { \sharp }
1940 Program reference: @internalsref{ScriptEvent}, and @internalsref{Script}.
1944 These signs appear in the printed output but have no effect on the
1945 MIDI rendering of the music.
1949 @subsection Dynamics
1962 @cindex @code{\ffff}
1972 Absolute dynamic marks are specified using a command after a note
1973 @code{c4\ff}. The available dynamic marks are @code{\ppp},
1974 @code{\pp}, @code{\p}, @code{\mp}, @code{\mf}, @code{\f}, @code{\ff},
1975 @code{\fff}, @code{\fff}, @code{\fp}, @code{\sf}, @code{\sff},
1976 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}
1978 @lilypond[quote,verbatim,raggedright,fragment,relative=2]
1979 c\ppp c\pp c \p c\mp c\mf c\f c\ff c\fff
1980 c2\fp c\sf c\sff c\sp c\spp c\sfz c\rfz
1989 A crescendo mark is started with @code{\<} and terminated with
1990 @code{\!} or an absolute dynamic. A decrescendo is started with
1991 @code{\>} and is also terminated with @code{\!} or an absolute
1992 dynamic. Because these marks are bound to notes, you must
1993 use spacer notes if multiple marks are needed during one note
1995 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
1997 << f1 { s4 s4\< s4\! \> s4\! } >>
1999 This may give rise to very short hairpins. Use @code{minimum-length}
2000 in @internalsref{Voice}.@internalsref{Hairpin} to lengthen them, for
2004 \override Staff.Hairpin #'minimum-length = #5
2007 You can also use a text saying @emph{cresc.} instead of hairpins. Here
2008 is an example how to do it
2010 @lilypond[quote,raggedright,fragment,relative=2,verbatim]
2024 You can also supply your own texts
2025 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
2026 \set crescendoText = \markup { \italic "cresc. poco" }
2027 \set crescendoSpanner = #'dashed-line
2033 To create new dynamic marks or text that should be aligned
2034 with dynamics, see @ref{New dynamic marks}.
2039 @cindex @code{\dynamicUp}
2041 @cindex @code{\dynamicDown}
2042 @code{\dynamicDown},
2043 @cindex @code{\dynamicNeutral}
2044 @code{\dynamicNeutral}.
2046 @cindex direction, of dynamics
2050 Program reference: @internalsref{CrescendoEvent},
2051 @internalsref{DecrescendoEvent}, and
2052 @internalsref{AbsoluteDynamicEvent}.
2054 Dynamics are @internalsref{DynamicText} and @internalsref{Hairpin}
2055 objects. Vertical positioning of these symbols is handled by the
2056 @internalsref{DynamicLineSpanner} object.
2059 @subsection Breath marks
2061 Breath marks are entered using @code{\breathe}
2064 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
2068 The glyph of the breath mark can be tuned by overriding the
2069 @code{text} property of the @code{BreathingSign} layout object with
2070 any markup text. For example,
2071 @lilypond[quote,raggedright,fragment,verbatim,relative=1]
2073 \override BreathingSign #'text
2074 = #(make-musicglyph-markup "scripts.rvarcomma")
2081 Program reference: @internalsref{BreathingSign},
2082 @internalsref{BreathingSignEvent}.
2084 Examples: @inputfileref{input/@/regression,breathing@/-sign@/.ly}.
2087 @node Running trills
2088 @subsection Running trills
2090 Long running trills are made with @code{\startTrillSpan} and
2091 @code{\stopTrillSpan},
2094 @lilypond[verbatim,raggedright,relative=2,quote,fragment]
2096 << { c1 \startTrillSpan }
2097 { s2. \grace { d16[\stopTrillSpan e] } } >>
2103 @code{\startTrillSpan},
2104 @cindex @code{\startTrillSpan}
2105 @code{\stopTrillSpan}.
2106 @cindex @code{\stopTrillSpan}
2110 Program reference: @internalsref{TrillSpanner},
2111 @internalsref{TrillSpanEvent}.
2117 @subsection Glissando
2120 @cindex @code{\glissando}
2122 A glissando is a smooth change in pitch. It is denoted by a line or a
2123 wavy line between two notes. It is requested by attaching
2124 @code{\glissando} to a note
2126 @lilypond[quote,raggedright,fragment,relative=2,verbatim]
2132 Program reference: @internalsref{Glissando}, and @internalsref{GlissandoEvent}.
2134 Example files: @file{input/@/regression/@/glissando@/.ly}.
2140 Printing text over the line (such as @emph{gliss.}) is not supported.
2144 @subsection Arpeggio
2147 @cindex broken chord
2148 @cindex @code{\arpeggio}
2150 You can specify an arpeggio sign (also known as broken chord) on a
2151 chord by attaching an @code{\arpeggio} to a chord
2154 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
2158 When an arpeggio crosses staves, you attach an arpeggio to the chords
2159 in both staves, and set
2160 @internalsref{PianoStaff}.@code{connectArpeggios}
2162 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
2163 \context PianoStaff <<
2164 \set PianoStaff.connectArpeggios = ##t
2165 \new Staff { <c' e g c>\arpeggio }
2166 \new Staff { \clef bass <c,, e g>\arpeggio }
2170 The direction of the arpeggio is sometimes denoted by adding an
2171 arrowhead to the wiggly line
2173 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
2182 A square bracket on the left indicates that the player should not
2183 arpeggiate the chord
2185 @c todo: ugh, lousy typography. Look for real example. --hwn
2187 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
2194 @cindex @code{\arpeggio}
2196 @cindex @code{\arpeggioUp}
2198 @cindex @code{\arpeggioDown}
2199 @code{\arpeggioDown},
2200 @cindex @code{\arpeggioNeutral}
2201 @code{\arpeggioNeutral},
2202 @cindex @code{\arpeggioBracket}
2203 @code{\arpeggioBracket}.
2207 Notation manual: @ref{Ties}, for writing out arpeggios.
2209 Program reference: @internalsref{ArpeggioEvent},
2210 @internalsref{Arpeggio}.
2216 It is not possible to mix connected arpeggios and unconnected
2217 arpeggios in one @internalsref{PianoStaff} at the same point in time.
2224 Polyphony in music refers to having more than one voice occuring in
2225 a piece of music. Polyphony in LilyPond refers to having more than
2226 one voice on the same staff.
2230 * Explicitly instantiating voices::
2231 * Collision Resolution::
2234 @node Basic polyphony
2235 @subsection Basic polyphony
2238 The easiest way to enter fragments with more than one voice on a staff
2239 is to enter each voice as a sequence (with @code{@{...@}}), and combine
2240 them simultaneously, separating the voices with @code{\\}
2244 @lilypond[quote,verbatim,fragment]
2245 \new Staff \relative c' {
2247 << { g4 f e | d2 e2 } \\
2248 { r8 e4 d c8 ~ | c b16 a b8 g ~ g2 } \\
2254 The separator causes @internalsref{Voice} contexts@footnote{Polyphonic
2255 voices are sometimes called ``layers'' in other notation packages}
2257 to be instantiated. They bear the names @code{"1"}, @code{"2"}, etc. In
2258 each of these contexts, vertical direction of slurs, stems, etc., is set
2261 These voices are all seperate from the voice that contains the notes just
2262 outside the @code{<< \\ >>} construct. This should be noted when making
2263 changes at the voice level. This also means that slurs and ties cannot go
2264 into or out of a @code{<< \\ >>} construct.
2265 Conversely, parallel voices from separate @code{<< \\ >>} constructs on the
2266 same staff are the the same voice.
2267 Here is the same example, with different noteheads for each voice.
2268 Note that the change to the note-head style in the main voice does not affect
2269 the inside of the @code{<< \\ >>} constructs. Also, the change to the second
2270 voice in the first @code{<< \\ >>} construct is effective in the second
2271 @code{<< \\ >>}, and the voice is tied accross the two constructs.
2273 @lilypond[quote,verbatim,fragment]
2274 \new Staff \relative c' {
2275 \override NoteHead #'style = #'cross
2279 { \override NoteHead #'style = #'triangle
2285 { c8 b16 a b8 g ~ g2 } \\
2286 { \override NoteHead #'style = #'slash s4 b4 c2 }
2291 Polyphony does not change the relationship of notes within a
2292 @code{\relative @{ @}} block. Each note is calculated relative
2293 to the note immediately preceding it.
2296 \relative @{ noteA << noteB \\ noteC >> noteD @}
2299 @code{noteC} is relative to @code{noteB}, not @code{noteA};
2300 @code{noteD} is relative to @code{noteC}, not @code{noteB} or
2303 @node Explicitly instantiating voices
2304 @subsection Explicitly instantiating voices
2306 @internalsref{Voice} contexts can also also be instantiated manually
2307 inside a @code{<< >>} block to create polyphonic music, using
2308 @code{\voiceOne}, up to @code{\voiceFour} to assign stem directions
2309 and a horizontal shift for each part.
2313 << \upper \\ \lower >>
2321 \context Voice = "1" @{ \voiceOne \upper @}
2322 \context Voice = "2" @{ \voiceTwo \lower @}
2326 @cindex @code{\voiceOne}
2327 @cindex @code{\voiceFour}
2329 The @code{\voiceXXX} commands set the direction of stems, slurs, ties,
2330 articulations, text annotations, augmentation dots of dotted
2331 notes, and fingerings. @code{\voiceOne} and @code{\voiceThree} make
2332 these objects point upwards, while @code{\voiceTwo} and @code{\voiceFour}
2333 make them point downwards.
2334 The command @code{\oneVoice} will revert back to the normal setting.
2335 @cindex @code{\oneVoice}
2337 An expression that appears directly inside a @code{<< >>} belongs to
2338 the main voice. This is useful when extra voices appear while the main
2339 voice is playing. Here is a more correct rendition of the example from
2340 the previous section. The crossed noteheads demonstrate that the main
2341 melody is now in a single voice context.
2343 @lilypond[quote,raggedright,verbatim]
2344 \new Staff \relative c' {
2345 \override NoteHead #'style = #'cross
2350 \context Voice="1" { \voiceTwo
2351 r8 e4 d c8 ~ | c8 b16 a b8 g ~ g2
2354 \new Voice { \voiceThree
2363 The correct definition of the voices allows the melody to be slurred.
2364 @lilypond[quote,raggedright,verbatim]
2365 \new Staff \relative c' {
2370 \context Voice="1" { \voiceTwo
2371 r8 e4 d c8 ~ | c8 b16 a b8 g ~ g2
2374 \new Voice { \voiceThree
2383 Avoiding the @code{\\} seperator also allows nesting polyphony
2384 constructs, which in some case might be a more natural way to typeset
2387 @lilypond[quote,raggedright,verbatim]
2388 \new Staff \relative c' {
2393 \context Voice="1" { \voiceTwo
2396 {c8 b16 a b8 g ~ g2}
2397 \new Voice { \voiceThree
2409 @node Collision Resolution
2410 @subsection Collision Resolution
2412 Normally, note heads with a different number of dots are not merged, but
2413 when the object property @code{merge-differently-dotted} is set in
2414 the @internalsref{NoteCollision} object, they are merged
2415 @lilypond[quote,verbatim,fragment,raggedright,relative=2]
2418 \override Staff.NoteCollision
2419 #'merge-differently-dotted = ##t
2421 } \\ { g8.[ f16] g8.[ f16] } >>
2424 Similarly, you can merge half note heads with eighth notes, by setting
2425 @code{merge-differently-headed}
2426 @lilypond[quote,raggedright,fragment,relative=2,verbatim]
2429 \override Staff.NoteCollision
2430 #'merge-differently-headed = ##t
2431 c8 c4. } \\ { c2 c2 } >>
2434 LilyPond also vertically shifts rests that are opposite of a stem,
2437 @lilypond[quote,raggedright,fragment,verbatim]
2438 \context Voice << c''4 \\ r4 >>
2446 @cindex @code{\oneVoice}
2448 @cindex @code{\voiceOne}
2450 @cindex @code{\voiceTwo}
2452 @cindex @code{\voiceThree}
2454 @cindex @code{\voiceFour}
2459 @cindex @code{\shiftOn}
2461 @cindex @code{\shiftOnn}
2463 @cindex @code{\shiftOnnn}
2465 @cindex @code{\shiftOff}
2466 @code{\shiftOff}: these commands specify in what chords of the current
2467 voice should be shifted. The outer voices (normally: voice one and
2468 two) have @code{\shiftOff}, while the inner voices (three and four)
2469 have @code{\shiftOn}. @code{\shiftOnn} and @code{\shiftOnnn} define
2470 further shift levels.
2473 When LilyPond cannot cope, the @code{force-hshift}
2474 property of the @internalsref{NoteColumn} object and pitched rests can
2475 be used to override typesetting decisions.
2477 @lilypond[quote,verbatim,raggedright]
2484 \once \override NoteColumn #'force-hshift = #1.7
2493 Program reference: the objects responsible for resolving collisions are
2494 @internalsref{NoteCollision} and @internalsref{RestCollision}.
2497 @inputfileref{input/@/regression,collision@/-dots@/.ly},
2498 @inputfileref{input/@/regression,collision@/-head-chords@/.ly},
2499 @inputfileref{input/@/regression,collision@/-heads@/.ly},
2500 @inputfileref{input/@/regression,collision@/-mesh@/.ly}, and
2501 @inputfileref{input/@/regression,collisions@/.ly}.
2507 When using @code{merge-differently-headed} with an upstem eighth or a
2508 shorter note, and a downstem half note, the eighth note gets the wrong
2511 There is no support for clusters where the same note occurs with
2512 different accidentals in the same chord. In this case, it is
2513 recommended to use enharmonic transcription, or to use special cluster
2514 notation (see @ref{Clusters}).
2521 Repetition is a central concept in music, and multiple notations exist
2527 * Repeats and MIDI::
2528 * Manual repeat commands::
2530 * Tremolo subdivisions::
2535 @subsection Repeat types
2538 @cindex @code{\repeat}
2540 The following types of repetition are supported
2544 Repeated music is fully written (played) out. This is useful when
2545 entering repetitious music. This is the only kind of repeat that
2546 is included in MIDI output.
2549 Repeats are not written out, but alternative endings (volte) are
2550 printed, left to right with brackets. This is the standard notation
2551 for repeats with alternatives. These are not played in MIDI output by default.
2555 Alternative endings are written stacked. This has limited use but may be
2556 used to typeset two lines of lyrics in songs with repeats, see
2557 @inputfileref{input,star-spangled-banner@/.ly}.
2562 Make tremolo beams. These are not played in MIDI output by default.
2565 Make beat or measure repeats. These look like percent signs. These
2566 are not played in MIDI output by default. Percent repeats must be
2567 declared within a Voice context.
2572 @subsection Repeat syntax
2575 LilyPond has one syntactic construct for specifying different types of
2576 repeats. The syntax is
2579 \repeat @var{variant} @var{repeatcount} @var{repeatbody}
2582 If you have alternative endings, you may add
2583 @cindex @code{\alternative}
2585 \alternative @{ @var{alternative1}
2587 @var{alternative3} @dots{} @}
2589 where each @var{alternative} is a music expression. If you do not
2590 give enough alternatives for all of the repeats, the first alternative
2591 is assumed to be played more than once.
2593 Standard repeats are used like this
2594 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
2596 \repeat volta 2 { c4 d e f }
2597 \repeat volta 2 { f e d c }
2600 With alternative endings
2601 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
2603 \repeat volta 2 {c4 d e f}
2604 \alternative { {d2 d} {f f,} }
2608 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
2611 \repeat volta 4 { e | c2 d2 | e2 f2 | }
2612 \alternative { { g4 g g } { a | a a a a | b2. } }
2616 It is possible to shorten volta brackets
2617 by setting @code{voltaSpannerDuration}. In the next example, the
2618 bracket only lasts one measure, which is a duration of 3/4.
2622 @lilypond[verbatim,raggedright,quote]
2626 \set Staff.voltaSpannerDuration = #(ly:make-moment 3 4)
2627 \repeat "volta" 5 { d d d }
2628 \alternative { { e e e f f f }
2638 Brackets for the repeat are normally only printed over the topmost
2639 staff. This can be adjusted by setting the @code{voltaOnThisStaff}
2640 property; see @inputfileref{input/@/regression,volta@/-multi@/-staff@/.ly}.
2643 @c @inputfileref{input/@/regression,volta@/-chord@/-names@/.ly}.
2648 A nested repeat like
2657 is ambiguous, since it is is not clear to which @code{\repeat} the
2658 @code{\alternative} belongs. This ambiguity is resolved by always
2659 having the @code{\alternative} belong to the inner @code{\repeat}.
2660 For clarity, it is advisable to use braces in such situations.
2665 Timing information is not remembered at the start of an alternative,
2666 so after a repeat timing information must be reset by hand, for
2667 example by setting @code{Score.measurePosition} or entering
2668 @code{\partial}. Similarly, slurs or ties are also not repeated.
2673 @node Repeats and MIDI
2674 @subsection Repeats and MIDI
2676 @cindex expanding repeats
2678 With a little bit of tweaking, all types of repeats can be present
2679 in the MIDI output. This is achieved by applying the
2680 @code{\unfoldrepeats} music function. This functions changes all
2681 repeats to unfold repeats.
2683 @lilypond[quote,verbatim,fragment,linewidth=8.0\cm]
2685 \repeat tremolo 8 {c'32 e' }
2686 \repeat percent 2 { c''8 d'' }
2687 \repeat volta 2 {c'4 d' e' f'}
2696 When creating a score file using @code{\unfoldrepeats} for midi, then
2697 it is necessary to make two @code{\score} blocks. One for MIDI (with
2698 unfolded repeats) and one for notation (with volta, tremolo, and
2699 percent repeats). For example,
2707 \unfoldrepeats @var{..music..}
2712 @node Manual repeat commands
2713 @subsection Manual repeat commands
2715 @cindex @code{repeatCommands}
2717 The property @code{repeatCommands} can be used to control the layout of
2718 repeats. Its value is a Scheme list of repeat commands.
2721 @item @code{start-repeat}
2722 Print a @code{|:} bar line.
2724 @item @code{end-repeat}
2725 Print a @code{:|} bar line.
2727 @item @code{(volta @var{text})}
2728 Print a volta bracket saying @var{text}: The text can be specified as
2729 a text string or as a markup text, see @ref{Text markup}. Do not
2730 forget to change the font, as the default number font does not contain
2731 alphabetic characters;
2733 @item @code{(volta #f)}
2734 Stop a running volta bracket.
2737 @lilypond[quote,raggedright,verbatim,fragment,relative=2]
2739 \set Score.repeatCommands = #'((volta "93") end-repeat)
2741 \set Score.repeatCommands = #'((volta #f))
2749 Program reference: @internalsref{VoltaBracket}, @internalsref{RepeatedMusic},
2750 @internalsref{VoltaRepeatedMusic},
2751 @internalsref{UnfoldedRepeatedMusic}, and
2752 @internalsref{FoldedRepeatedMusic}.
2754 @node Tremolo repeats
2755 @subsection Tremolo repeats
2756 @cindex tremolo beams
2758 To place tremolo marks between notes, use @code{\repeat} with tremolo
2760 @lilypond[quote,verbatim,raggedright]
2761 \new Voice \relative c' {
2762 \repeat "tremolo" 8 { c16 d16 }
2763 \repeat "tremolo" 4 { c16 d16 }
2764 \repeat "tremolo" 2 { c16 d16 }
2768 Tremolo marks can also be put on a single note. In this case, the
2769 note should not be surrounded by braces.
2770 @lilypond[quote,verbatim,raggedright]
2771 \repeat "tremolo" 4 c'16
2774 Similar output is obtained using the tremolo subdivision, described in
2775 @ref{Tremolo subdivisions}.
2779 In this manual: @ref{Tremolo subdivisions}, @ref{Repeats}.
2781 Program reference: tremolo beams are @internalsref{Beam} objects. Single stem
2782 tremolos are @internalsref{StemTremolo} objects. The music expression is
2783 @internalsref{TremoloEvent}.
2785 Example files: @inputfileref{input/@/regression,chord@/-tremolo@/.ly},
2786 @inputfileref{input/@/regression,stem@/-tremolo@/.ly}.
2788 @node Tremolo subdivisions
2789 @subsection Tremolo subdivisions
2790 @cindex tremolo marks
2791 @cindex @code{tremoloFlags}
2793 Tremolo marks can be printed on a single note by adding
2794 `@code{:}[@var{number}]' after the note. The number indicates the
2795 duration of the subdivision, and it must be at least 8. A
2796 @var{length} value of 8 gives one line across the note stem. If the
2797 length is omitted, the last value (stored in @code{tremoloFlags}) is
2800 @lilypond[quote,raggedright,verbatim,fragment]
2801 c'2:8 c':32 | c': c': |
2804 @c [TODO: stok is te kort bij 32en]
2805 @c somebody want to translate that into English?
2806 @c `Stem is too short for 32nds' (wl)
2810 Tremolos entered in this way do not carry over into the MIDI output.
2814 In this manual: @ref{Tremolo repeats}.
2816 Elsewhere: @internalsref{StemTremolo}, @internalsref{TremoloEvent}.
2818 @node Measure repeats
2819 @subsection Measure repeats
2821 @cindex percent repeats
2822 @cindex measure repeats
2824 In the @code{percent} style, a note pattern can be repeated. It is
2825 printed once, and then the pattern is replaced with a special sign.
2826 Patterns of one and two measures are replaced by percent-like signs,
2827 patterns that divide the measure length are replaced by slashes.
2828 Percent repeats must be declared within a @code{Voice} context.
2830 @lilypond[quote,verbatim,raggedright]
2831 \new Voice \relative c' {
2832 \repeat "percent" 4 { c4 }
2833 \repeat "percent" 2 { c2 es2 f4 fis4 g4 c4 }
2839 Program reference: @internalsref{RepeatSlash}, @internalsref{PercentRepeat},
2840 @internalsref{PercentRepeatedMusic}, and
2841 @internalsref{DoublePercentRepeat}.