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 Notation manual
11 This chapter describes all the different types of notation supported
12 by LilyPond. It is intended as a reference for users that are already
13 somewhat familiar with LilyPond.
17 * Easier music entry::
31 * Contemporary notation::
36 @c FIXME: Note entry vs Music entry at top level menu is confusing.
42 This section is about basic notation elements notes, rests and
43 related constructs, such as stems, tuplets and ties.
48 * Chromatic alterations::
63 A note is printed by specifying its pitch and then its duration
64 @footnote{Notes constitute the most basic elements of LilyPond input,
65 but they do not form valid input on their own without a @code{\score}
66 block. However, for the sake of brevity and simplicity we will
67 generally omit @code{\score} blocks and @code{\paper} declarations in
70 @lilypond[quote,fragment,verbatim]
79 @cindex Note specification
81 @cindex entering notes
83 The most common syntax for pitch entry is used in @code{\chords} and
84 @code{\notes} mode. In these modes, pitches may be designated by
85 names. The notes are specified by the letters @code{a} through
86 @code{g}, while the octave is formed with notes ranging from @code{c}
87 to @code{b}. The pitch @code{c} is an octave below middle C and the
88 letters span the octave above that C
90 @lilypond[quote,fragment,verbatim]
92 a,4 b, c d e f g a b c' d' e' \clef treble f' g' a' b' c''
95 @cindex note names, Dutch
97 A sharp is formed by adding @code{-is} to the end of a pitch name and
98 a flat is formed by adding @code{-es}. Double sharps and double flats
99 are obtained by adding @code{-isis} or @code{-eses}. These
100 names are the Dutch note names. In Dutch, @code{aes} is contracted to
101 @code{as}, but both forms are accepted. Similarly, both
102 @code{es} and @code{ees} are accepted.
104 Half-flats and half-sharps are formed by adding @code{-eh} and
105 @code{-ih}; the following is a series of Cs with increasing pitches
107 @cindex quarter tones
108 @cindex semi-flats, semi-sharps
110 @lilypond[quote,verbatim,relative=3]
122 There are predefined sets of note names for various other languages.
123 To use them, include the language specific init file. For
124 example: @code{\include "english.ly"}. The available language files
125 and the note names they define are
130 Note Names sharp flat
131 nederlands.ly c d e f g a bes b -is -es
132 english.ly c d e f g a bf b -s/-sharp -f/-flat
134 deutsch.ly c d e f g a b h -is -es
135 norsk.ly c d e f g a b h -iss/-is -ess/-es
136 svenska.ly c d e f g a b h -iss -ess
137 italiano.ly do re mi fa sol la sib si -d -b
138 catalan.ly do re mi fa sol la sib si -d/-s -b
139 espanol.ly do re mi fa sol la sib si -s -b
148 The optional octave specification takes the form of a series of
149 single quote (`@code{'}') characters or a series of comma
150 (`@code{,}') characters. Each @code{'} raises the pitch by one
151 octave; each @code{,} lowers the pitch by an octave
153 @lilypond[quote,fragment,verbatim]
154 c' c'' es' g' as' gisis' ais'
160 Notes can be hidden and unhidden with the following commands
162 @cindex @code{\hideNotes}
164 @cindex @code{\unHideNotes}
170 Program reference: @internalsref{NoteEvent}, and @internalsref{NoteHead}.
172 @node Chromatic alterations
173 @subsection Chromatic alterations
175 Normally accidentals are printed automatically, but you may also
176 print them manually. A reminder accidental
177 @cindex reminder accidental
179 can be forced by adding an exclamation mark @code{!}
180 after the pitch. A cautionary accidental
181 @cindex cautionary accidental
182 @cindex parenthesized accidental
183 (i.e. an accidental within parentheses) can be obtained by adding the
184 question mark `@code{?}' after the pitch
186 @lilypond[quote,fragment,verbatim]
187 cis' cis' cis'! cis'?
193 The automatic production of accidentals can be tuned in many
194 ways. For more information, refer to @ref{Accidentals}.
199 There are no generally accepted standards for denoting three quarter
200 flats, so LilyPond's symbol does not conform to any standard.
205 A chord is formed by a enclosing a set of pitches in @code{<} and
206 @code{>}. A chord may be followed by a duration, and a set of
207 articulations, just like simple notes.
209 @lilypond[quote,relative=1]
220 Rests are entered like notes, with the note name @code{r}
222 @lilypond[quote,raggedright,verbatim]
226 Whole bar rests, centered in middle of the bar,
227 must be done with multi-measure rests. They are discussed in
228 @ref{Multi measure rests}.
231 A rest's vertical position may be explicitly specified by entering a
232 note with the @code{\rest} keyword appended. This makes manual
233 formatting in polyphonic music easier. Rest collision testing will
234 leave these rests alone
236 @lilypond[quote,raggedright,verbatim]
242 Program reference: @internalsref{RestEvent}, and @internalsref{Rest}.
249 @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[quote,raggedright,verbatim]
259 The @code{s} syntax is only available in note mode and chord mode. In
260 other situations, you should use the @code{\skip} command
262 @lilypond[quote,raggedright,verbatim]
265 { \time 4/8 \skip 2 \time 4/4 }
266 \notes\relative c'' { a2 a1 }
271 The skip command is merely an empty musical placeholder. It does not
272 produce any output, not even transparent output.
274 The @code{s} skip command does create @internalsref{Staff} and
275 @internalsref{Voice} when necessary, similar to note and rest
276 commands. For example, the following results in an empty staff.
278 @lilypond[quote,raggedright,verbatim]
279 \score { \notes { s4 } }
282 The same fragment using @code{\skip} results in an empty page.
286 Program reference: @internalsref{SkipEvent}, @internalsref{SkipMusic}.
291 @subsection Durations
297 In Note, Chord, and Lyrics mode, durations are designated by numbers
298 and dots: durations are entered as their reciprocal values. For example,
299 a quarter note is entered using a @code{4} (since it is a 1/4 note), while
300 a half note is entered using a @code{2} (since it is a 1/2 note). For notes
301 longer than a whole you must use variables
305 c'1 c'2 c'4 c'8 c'16 c'32 c'64 c'64
307 r1 r2 r4 r8 r16 r32 r64 r64
312 \notes \relative c'' {
313 a\breve*1/2 \autoBeamOff
314 a1 a2 a4 a8 a16 a32 a64 a64
315 r\longa*1/4 r\breve *1/2
316 r1 r2 r4 r8 r16 r32 r64 r64
322 \remove "Clef_engraver"
323 \override StaffSymbol #'transparent = ##t
324 \override TimeSignature #'transparent = ##t
325 \override BarLine #'transparent = ##t
326 \consists "Pitch_squash_engraver"
333 If the duration is omitted then it is set to the previously entered
334 duration. The default for the first note is a quarter note. The duration
335 can be followed by dots (`@code{.}') in order to obtain dotted note
339 @lilypond[quote,fragment,verbatim]
340 a' b' c''8 b' a'4 a'4. b'4.. c'8.
345 You can alter the length of duration by a fraction @var{N/M}
346 appending `@code{*}@var{N/M}' (or `@code{*}@var{N}' if @var{M=1}). This
347 will not affect the appearance of the notes or rests produced.
349 In the following example, the first three notes take up exactly two
350 beats, but no triplet bracket is printed.
351 @lilypond[quote,fragment,relative=3,verbatim]
353 a4*2/3 gis4*2/3 a4*2/3
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{\dotsBoth}
372 This manual: @ref{Tuplets}
374 Program reference: @internalsref{Dots}, and @internalsref{DotColumn}.
379 Whenever a note is found, a @internalsref{Stem} object is created
380 automatically. For whole notes and rests, they are also created but
385 @cindex @code{\stemUp}
387 @cindex @code{\stemDown}
389 @cindex @code{\stemBoth}
400 A tie connects two adjacent note heads of the same pitch. The tie in
401 effect extends the length of a note. Ties should not be confused with
402 slurs, which indicate articulation, or phrasing slurs, which indicate
403 musical phrasing. A tie is entered using the tilde symbol `@code{~}'
405 @lilypond[quote,fragment,verbatim]
406 e' ~ e' <c' e' g'> ~ <c' e' g'>
409 When a tie is applied to a chord, all note heads whose pitches match
410 are connected. When no note heads match, no ties will be created.
412 In its meaning a tie is just a way of extending a note duration, similar
413 to the augmentation dot; in the following example there are two ways of
414 notating exactly the same concept
416 @lilypond[quote,fragment,raggedright]
417 \time 3/4 c'2. c'2 ~ c'4
419 If you need to tie a lot of notes over bars, it may be easier to use automatic
420 note splitting (see @ref{Automatic note splitting}).
425 @cindex @code{\tieUp}
427 @cindex @code{\tieDown}
429 @cindex @code{\tieBoth}
431 @cindex @code{\tieDotted}
433 @cindex @code{\tieSolid}
438 In this manual: @ref{Automatic note splitting}.
440 Program reference: @internalsref{TieEvent}, @internalsref{Tie}.
442 For tying only a subset of the note heads of a pair of chords, see
443 @inputfileref{input/regression,tie-chord-partial.ly}.
448 Switching staves when a tie is active will not produce a slanted tie.
450 Formatting of ties is a difficult subject. The results are often not
460 @cindex @code{\times}
462 Tuplets are made out of a music expression by multiplying all durations
465 @cindex @code{\times}
467 \times @var{fraction} @var{musicexpr}
471 The duration of @var{musicexpr} will be multiplied by the fraction.
472 The fraction's denominator will be printed over the notes, optionally
473 with a bracket. The most common tuplet is the triplet in which 3
474 notes have the length of 2, so the notes are 2/3 of their written
477 @lilypond[quote,fragment,verbatim]
478 g'4 \times 2/3 {c'4 c' c'} d'4 d'4
481 The property @code{tupletSpannerDuration} specifies how long each
482 bracket should last. With this, you can make lots of tuplets while
483 typing @code{\times} only once, saving lots of typing. In the next
484 example, there are two triplets shown, while @code{\times} was only
487 @lilypond[quote,fragment,relative=1,raggedright,verbatim]
488 \set tupletSpannerDuration = #(ly:make-moment 1 4)
489 \times 2/3 { c'8 c c c c c }
492 The format of the number is determined by the property
493 @code{tupletNumberFormatFunction}. The default prints only the
494 denominator, but if it is set to the Scheme function
495 @code{fraction-tuplet-formatter}, @var{num}:@var{den} will be printed
499 @cindex @code{tupletNumberFormatFunction}
500 @cindex tuplet formatting
505 @cindex @code{\tupletUp}
507 @cindex @code{\tupletDown}
509 @cindex @code{\tupletBoth}
514 Program reference: @internalsref{TupletBracket}, and @internalsref{TimeScaledMusic}.
516 Examples: @inputfileref{input/regression,tuplet-nest.ly}.
520 Nested tuplets are not formatted automatically. In this case, outer
521 tuplet brackets should be moved manually, which is demonstrated in
522 @inputfileref{input/regression,tuplet-nest.ly}.
526 @node Easier music entry
527 @section Easier music entry
530 This section deals with tricks and features of the input language that
531 were added solely to help entering music, finding and correcting
532 mistakes. There are also external tools that make debugging easier.
533 See @ref{Point and click} for more information.
535 It is also possible to enter and edit music using other programs. For
536 example, GUI interfaces, or MIDI sequencers. Refer to the LilyPond
537 website for more information.
544 * Skipping corrected music::
545 * Automatic note splitting::
551 @node Relative octaves
552 @subsection Relative octaves
554 @cindex relative octave specification
556 Octaves are specified by adding @code{'} and @code{,} to pitch names.
557 When you copy existing music, it is easy to accidentally put a pitch
558 in the wrong octave and hard to find such an error. The relative
559 octave mode prevents these errors: a single error puts the rest of the
560 piece off by one octave
562 @cindex @code{\relative}
564 \relative @var{startpitch} @var{musicexpr}
567 The octave of notes that appear in @var{musicexpr} are calculated as
568 follows: If no octave changing marks are used, the basic interval
569 between this and the last note is always taken to be a fourth or
570 less. This distance is determined without regarding alterations; a
571 @code{fisis} following a @code{ceses} will be put above the
574 The octave changing marks @code{'} and @code{,} can be added to raise
575 or lower the pitch by an extra octave. Upon entering relative mode,
576 an absolute starting pitch must be specified that will act as the
577 predecessor of the first note of @var{musicexpr}.
579 Here is the relative mode shown in action
580 @lilypond[quote,fragment,raggedright,verbatim]
586 Octave changing marks are used for intervals greater than a fourth
587 @lilypond[quote,fragment,verbatim]
593 If the preceding item is a chord, the first note of the chord is used
594 to determine the first note of the next chord
596 @lilypond[quote,fragment,verbatim]
603 @cindex @code{\notes}
605 The pitch after the @code{\relative} contains a note name. To parse
606 the note name as a pitch, it must surrounded by @code{\notes}
608 The relative conversion will not affect @code{\transpose},
609 @code{\chords} or @code{\relative} sections in its argument. If you
610 want to use relative within transposed music, you must place an
611 additional @code{\relative} inside the @code{\transpose}.
614 @subsection Octave check
617 Octave checks make octave errors easier to correct: a note may be
618 followed by @code{=}@var{quotes} which indicates what its absolute
619 octave should be. In the following example,
621 \relative c'' @{ c='' b=' d,='' @}
625 @c take care with @code, adds confusing quotes.
626 the d will generate a warning, because a d'' is expected, but a d' is
627 found. In the output, the octave is corrected for this and the
632 There is also a syntax that is separate from the notes.
637 This checks that @var{pitch} (without octave) yields @var{pitch} (with
638 octave) in \relative mode. If not, a warning is printed, and the
639 octave is corrected, for example, the first check is passed
640 successfully. The second check fails with an error message. The
641 octave is adjusted so the following notes are in the correct octave
652 The octave of a note following an octave check is determined with
653 respect to the note preceding it. In the next fragment, the last note
654 is a @code{a'}, above middle C. Hence, the @code{\octave} check may
655 be deleted without changing the meaning of the piece.
657 @lilypond[quote,verbatim,fragment]
666 @subsection Bar check
670 @cindex @code{barCheckSynchronize}
673 Bar checks help detect errors in the durations. A bar check is
674 entered using the bar symbol, `@code{|}'. Whenever it is encountered
675 during interpretation, it should fall on a measure boundary. If it
676 does not, a warning is printed. In the next example, the second bar
677 check will signal an error
679 \time 3/4 c2 e4 | g2 |
682 Bar checks can also be used in lyrics, for example
687 Twin -- kle | Twin -- kle
692 @cindex skipTypesetting
694 Failed bar checks are caused by entering incorrect
695 durations. Incorrect durations often completely garble up the score,
696 especially if it is polyphonic, so you should start correcting the
697 score by scanning for failed bar checks and incorrect durations. To
698 speed up this process, you can use @code{skipTypesetting}, described
701 It is also possible to redefine the meaning of @code{|}. This is done
702 by assigning a music expression to @code{pipeSymbol},
705 pipeSymbol = \bar "||"
708 \notes { c'2 c'2 | c'2 c'2 | }
713 @node Skipping corrected music
714 @subsection Skipping corrected music
716 The property @code{Score.skipTypesetting} can be used to switch on and
717 off typesetting completely during the interpretation phase. When
718 typesetting is switched off, the music is processed much more quickly.
719 This can be used to skip over the parts of a score that have already
720 been checked for errors
722 @lilypond[quote,fragment,raggedright,verbatim]
725 \set Score.skipTypesetting = ##t
727 \set Score.skipTypesetting = ##f
731 @node Automatic note splitting
732 @subsection Automatic note splitting
734 Long notes can be converted automatically to tied notes. This is done
735 by replacing the @internalsref{Note_heads_engraver} by the
736 @internalsref{Completion_heads_engraver}.
737 In the following examples, notes crossing the bar line are split and tied.
740 @lilypond[quote,fragment,verbatim,relative=1,raggedright]
742 \remove "Note_heads_engraver"
743 \consists "Completion_heads_engraver"
745 c2. c8 d4 e f g a b c8 c2 b4 a g16 f4 e d c8. c2
749 This engraver splits all running notes at the bar line, and inserts
750 ties. One of its uses is to debug complex scores: if the measures are
751 not entirely filled, then the ties exactly show how much each measure
756 Not all durations (especially those containing tuplets) can be
757 represented exactly; the engraver will not insert tuplets.
761 Examples: @inputfileref{input/regression,completion-heads.ly}.
763 Program reference: @internalsref{Completion_heads_engraver}.
767 @section Staff notation
769 This section describes music notation that occurs on staff level,
770 such as keys, clefs and time signatures.
772 @cindex Staff notation
786 @subsection Staff symbol
788 @cindex adjusting staff symbol
790 Notes, dynamic signs, etc. are grouped
791 with a set of horizontal lines, into a staff (plural `staves'). In our
792 system, these lines are drawn using a separate layout object called
796 @cindex staff lines, setting number of
797 @cindex staff lines, setting thickness of
798 @cindex thickness of staff lines, setting
799 @cindex number of staff lines, setting
803 Program reference: @internalsref{StaffSymbol}.
805 Examples: @inputfileref{input/test,staff-lines.ly},
806 @inputfileref{input/test,staff-size.ly}.
810 If a staff is ended halfway a piece, the staff symbol may not end
811 exactly on the bar line.
815 @subsection Key signature
816 @cindex Key signature
820 The key signature indicates the scale in which a piece is played. It
821 is denoted by a set of alterations (flats or sharps) at the start of
825 Setting or changing the key signature is done with the @code{\key}
828 @code{\key} @var{pitch} @var{type}
831 @cindex @code{\minor}
832 @cindex @code{\major}
833 @cindex @code{\minor}
834 @cindex @code{\ionian}
835 @cindex @code{\locrian}
836 @cindex @code{\aeolian}
837 @cindex @code{\mixolydian}
838 @cindex @code{\lydian}
839 @cindex @code{\phrygian}
840 @cindex @code{\dorian}
842 Here, @var{type} should be @code{\major} or @code{\minor} to get
843 @var{pitch}-major or @var{pitch}-minor, respectively.
844 The standard mode names @code{\ionian},
845 @code{\locrian}, @code{\aeolian}, @code{\mixolydian}, @code{\lydian},
846 @code{\phrygian}, and @code{\dorian} are also defined.
848 This command sets the context property
849 @internalsref{Staff}.@code{keySignature}. Non-standard key signatures
850 can be specified by setting this property directly.
852 Accidentals and key signatures often confuse new users, because
853 unaltered notes get natural signs depending on the key signature. For
854 more information, see @ref{More about pitches}.
858 The ordering of a key cancellation is wrong when it is combined with
859 repeat bar lines. The cancellation is also printed after a line break.
863 Program reference: @internalsref{KeyChangeEvent}, and @internalsref{KeySignature}.
865 @cindex @code{keySignature}
872 The clef indicates which lines of the staff correspond to which
876 The clef can be set or changed with the @code{\clef} command
877 @lilypond[quote,fragment,verbatim]
878 \key f\major c''2 \clef alto g'2
881 Supported clef-names include
882 @c Moved standard clefs to the top /MB
886 @item treble, violin, G, G2
899 G clef on 1st line, so-called French violin clef
904 @cindex mezzosoprano clef
907 @cindex baritone clef
910 @cindex varbaritone clef
921 By adding @code{_8} or @code{^8} to the clef name, the clef is
922 transposed one octave down or up, respectively, and @code{_15} and
923 @code{^15} transposes by two octaves. The argument @var{clefname}
924 must be enclosed in quotes when it contains underscores or digits. For
928 @cindex choral tenor clef
929 @lilypond[quote,verbatim,fragment,relative=1]
933 This command is equivalent to setting @code{clefGlyph},
934 @code{clefPosition} (which controls the Y position of the clef),
935 @code{centralCPosition} and @code{clefOctavation}. A clef is printed
936 when any of these properties are changed.
940 Program reference: the object for this symbol is @internalsref{Clef}.
944 @node Ottava brackets
945 @subsection Ottava brackets
947 ``Ottava'' brackets introduce an extra transposition of an octave for
948 the staff. They are created by invoking the function
949 @code{set-octavation}
955 @lilypond[quote,verbatim,fragment]
965 The @code{set-octavation} function also takes -1 (for 8va bassa) and 2
966 (for 15ma) as arguments. Internally the function sets the properties
967 @code{ottavation} (e.g. to @code{"8va"}) and
968 @code{centralCPosition}. For overriding the text of the bracket, set
969 @code{ottavation} after invoking @code{set-octavation}, i.e.,
973 \set Staff.ottavation = #"8"
978 Program reference: @internalsref{OttavaBracket}.
980 Examples: @inputfileref{input/regression,ottava.ly},
981 @inputfileref{input/regression,ottava-broken.ly}.
985 @code{set-octavation} will get confused when clef changes happen
986 during an octavation bracket.
989 @subsection Time signature
990 @cindex Time signature
994 Time signature indicates the metrum of a piece: a regular pattern of
995 strong and weak beats. It is denoted by a fraction at the start of the
999 The time signature is set or changed by the @code{\time}
1001 @lilypond[quote,fragment,verbatim]
1002 \time 2/4 c'2 \time 3/4 c'2.
1005 The symbol that is printed can be customized with the @code{style}
1006 property. Setting it to @code{#'()} uses fraction style for 4/4 and
1007 2/2 time. There are many more options for its layout. See
1008 @inputfileref{input/test,time.ly} for more examples.
1011 This command sets the property @code{timeSignatureFraction},
1012 @code{beatLength} and @code{measureLength} in the @code{Timing}
1013 context, which is normally aliased to @internalsref{Score}. The
1014 property @code{measureLength} determines where bar lines should be
1015 inserted, and how automatic beams should be generated. Changing the
1016 value of @code{timeSignatureFraction} also causes the symbol to be
1019 More options are available through the Scheme function
1020 @code{set-time-signature}. In combination with the
1021 @internalsref{Measure_grouping_engraver}, it will create
1022 @internalsref{MeasureGrouping} signs. Such signs ease reading
1023 rhythmically complex modern music. In the following example, the 9/8
1024 measure is subdivided in 2, 2, 2 and 3. This is passed to
1025 @code{set-time-signature} as the third argument @code{(2 2 2 3)}
1027 @lilypond[quote,raggedright,verbatim]
1029 \notes \relative c'' {
1030 #(set-time-signature 9 8 '(2 2 2 3))
1031 g8[ g] d[ d] g[ g] a8[( bes g]) |
1032 #(set-time-signature 5 8 '(3 2))
1038 \consists "Measure_grouping_engraver"
1046 Program reference: @internalsref{TimeSignature}, and @internalsref{Timing_engraver}.
1051 Automatic beaming does not use the measure grouping specified with
1052 @code{set-time-signature}.
1054 @node Partial measures
1055 @subsection Partial measures
1058 @cindex partial measure
1059 @cindex measure, partial
1060 @cindex shorten measures
1061 @cindex @code{\partial}
1063 Partial measures, for example in upsteps, are entered using the
1064 @code{\partial} command
1065 @lilypond[quote,fragment,verbatim,relative=2]
1066 \partial 16*5 c16 cis d dis e | a2. c,4 | b2
1069 The syntax for this command is
1071 \partial @var{duration}
1073 This is internally translated into
1075 \set Timing.measurePosition = -@var{length of duration}
1078 The property @code{measurePosition} contains a rational number
1079 indicating how much of the measure has passed at this point.
1081 @node Unmetered music
1082 @subsection Unmetered music
1084 Bar lines and bar numbers are calculated automatically. For unmetered
1085 music (e.g. cadenzas), this is not desirable. By setting
1086 @code{Score.timing} to false, this automatic timing can be switched
1087 off. Empty bar lines,
1094 indicate where line breaks can occur.
1100 @cindex @code{\cadenzaOn}
1102 @cindex @code{\cadenzaOff}
1106 @subsection Bar lines
1110 @cindex measure lines
1114 Bar lines delimit measures, but are also used to indicate repeats.
1115 Normally, they are inserted automatically. Line breaks may only
1116 happen on bar lines.
1118 Special types of bar lines can be forced with the @code{\bar} command
1120 @lilypond[quote,relative=2,fragment,verbatim]
1124 The following bar types are available
1125 @lilypond[quote,fragment,relative=1,raggedright,verbatim]
1138 For allowing line breaks, there is a special command,
1142 This will insert an invisible bar line, and allow line breaks at this
1145 In scores with many staves, a @code{\bar} command in one staff is
1146 automatically applied to all staves. The resulting bar lines are
1147 connected between different staves of a @internalsref{StaffGroup}
1149 @lilypond[quote,fragment,verbatim]
1151 \context StaffGroup <<
1157 \new Staff { \clef bass c4 g e g }
1159 \new Staff { \clef bass c2 c2 }
1163 A bar line is created whenever the @code{whichBar} property is set.
1164 At the start of a measure it is set to the contents of
1165 @code{defaultBarType}. The contents of @code{repeatCommands} are used
1166 to override default measure bars.
1168 The command @code{\bar }@var{bartype} is a short cut for doing
1169 @code{\set Timing.whichBar = }@var{bartype}. Whenever @code{whichBar}
1170 is set to a string, a bar line of that type is created.
1173 @cindex repeatCommands
1174 @cindex defaultBarType
1176 You are encouraged to use @code{\repeat} for repetitions. See
1183 In this manual: @ref{Repeats}.
1186 Program reference: the bar line objects that are created at
1187 @internalsref{Staff} level are called @internalsref{BarLine}, the bar
1188 lines that span staves are @internalsref{SpanBar} objects.
1190 @cindex bar lines at start of system
1191 @cindex start of system
1193 The bar lines at the start of each system are
1194 @internalsref{SystemStartBar}, @internalsref{SystemStartBrace}, and
1195 @internalsref{SystemStartBracket}. Only one of these types is created
1196 in every context, and that type is determined by the property
1197 @code{systemStartDelimiter}.
1199 Examples: @inputfileref{input/test,bar-lines.ly},
1205 The easiest way to enter fragments with more than one voice on a staff
1206 is to split chords using the separator @code{\\}. You can use it for
1207 small, short-lived voices or for single chords
1209 @lilypond[quote,verbatim,fragment]
1210 \context Staff \relative c'' {
1211 c4 << { f d e } \\ { b c2 } >>
1212 c4 << g' \\ b, \\ f' \\ d >>
1216 The separator causes @internalsref{Voice} contexts@footnote{Polyphonic
1217 voices are sometimes called "layers" other notation packages}
1219 to be instantiated. They bear the names @code{"1"}, @code{"2"}, etc. In
1220 each of these contexts, vertical direction of slurs, stems, etc. is set
1223 @cindex @code{\voiceOne}
1224 @cindex @code{\voiceFour}
1226 This can also be done by instantiating @internalsref{Voice} contexts
1227 by hand, and using @code{\voiceOne}, up to @code{\voiceFour} to assign
1228 a stem directions and horizontal shift for each part
1231 @lilypond[quote,raggedright,verbatim]
1234 \new Voice { \voiceOne cis2 b }
1235 \new Voice { \voiceThree b4 ais ~ ais4 gis4 }
1236 \new Voice { \voiceTwo fis4~ fis4 f ~ f } >>
1240 The command @code{\oneVoice} will revert back to the normal setting.
1241 @cindex @code{\oneVoice}
1244 Normally, note heads with a different number of dots are not merged, but
1245 when the object property @code{merge-differently-dotted} is set in
1246 the @internalsref{NoteCollision} object, they are merged
1247 @lilypond[quote,verbatim,fragment,raggedright,relative=2]
1250 \override Staff.NoteCollision
1251 #'merge-differently-dotted = ##t
1253 } \\ { g8.[ f16] g8.[ f16] } >>
1256 Similarly, you can merge half note heads with eighth notes, by setting
1257 @code{merge-differently-headed}
1258 @lilypond[quote,fragment,relative=2,verbatim]
1261 \override Staff.NoteCollision
1262 #'merge-differently-headed = ##t
1263 c8 c4. } \\ { c2 c2 } >>
1266 LilyPond also vertically shifts rests that are opposite of a stem
1269 @lilypond[quote,raggedright,fragment,verbatim]
1270 \context Voice << c''4 \\ r4 >>
1278 @cindex @code{\oneVoice}
1280 @cindex @code{\voiceOne}
1282 @cindex @code{\voiceTwo}
1284 @cindex @code{\voiceThree}
1286 @cindex @code{\voiceFour}
1290 The following commands specify in what chords of the current voice
1291 should be shifted: the outer voice has @code{\shiftOff}, and the inner
1292 voices have @code{\shiftOn}, @code{\shiftOnn}, etc.
1295 @cindex @code{\shiftOn}
1297 @cindex @code{\shiftOnn}
1299 @cindex @code{\shiftOnnn}
1301 @cindex @code{\shiftOff}
1308 Program reference: the objects responsible for resolving collisions are
1309 @internalsref{NoteCollision} and @internalsref{RestCollision}.
1311 Examples: See also example files
1312 @inputfileref{input/regression,collision-dots.ly},
1313 @inputfileref{input/regression,collision-head-chords.ly},
1314 @inputfileref{input/regression,collision-heads.ly},
1315 @inputfileref{input/regression,collision-mesh.ly}, and
1316 @inputfileref{input/regression,collisions.ly}.
1321 Resolving collisions is a intricate subject, and only a few situations
1322 are handled. When LilyPond cannot cope, the @code{force-hshift}
1323 property of the @internalsref{NoteColumn} object and pitched rests can
1324 be used to override typesetting decisions.
1326 When using @code{merge-differently-headed} with an upstem eighth or a
1327 shorter note, and a downstem half note, the eighth note gets the wrong
1330 There is no support for clusters where the same note occurs with
1331 different accidentals in the same chord. In this case, it is
1332 recommended to use enharmonic transcription, or to use special cluster
1333 notation (see @ref{Clusters}).
1338 Beams are used to group short notes into chunks that are aligned with
1339 the metrum. They are inserted automatically
1341 @lilypond[quote,fragment,verbatim,relative=2]
1342 \time 2/4 c8 c c c \time 6/8 c c c c8. c16 c8
1345 When these automatic decisions are not good enough, beaming can be
1346 entered explicitly. It is also possible to define beaming patterns
1347 that differ from the defaults.
1349 Individual notes may be marked with @code{\noBeam}, to prevent them
1352 @lilypond[quote,fragment,verbatim,relative=2]
1353 \time 2/4 c8 c\noBeam c c
1359 Program reference: @internalsref{Beam}.
1362 @cindex Automatic beams
1365 * Setting automatic beam behavior::
1369 @subsection Manual beams
1370 @cindex beams, manual
1374 In some cases it may be necessary to override the automatic beaming
1375 algorithm. For example, the autobeamer will not put beams over rests
1376 or bar lines. Such beams are specified by manually: the begin and end
1377 point are marked with @code{[} and @code{]}
1379 @lilypond[quote,fragment,relative=1,verbatim]
1381 r4 r8[ g' a r8] r8 g[ | a] r8
1385 @cindex @code{stemLeftBeamCount}
1387 Normally, beaming patterns within a beam are determined automatically.
1388 If necessary, the properties @code{stemLeftBeamCount} and
1389 @code{stemRightBeamCount} can be used to override the defaults. If
1390 either property is set, its value will be used only once, and then it
1393 @lilypond[quote,fragment,relative=1,verbatim]
1396 f8[ r16 \set stemLeftBeamCount = #1 f g a]
1399 @cindex @code{stemRightBeamCount}
1402 The property @code{subdivideBeams} can be set in order to subdivide
1403 all 16th or shorter beams at beat positions, as defined by the
1404 @code{beatLength} property.
1407 @lilypond[quote,relative=2,verbatim,noindent]
1409 \set subdivideBeams = ##t
1411 \set Score.beatLength = #(ly:make-moment 1 8)
1414 @cindex subdivideBeams
1416 Kneed beams are inserted automatically, when a large gap is detected
1417 between the note heads. This behavior can be tuned through the object
1418 property @code{auto-knee-gap}.
1420 Normally, line breaks are forbidden when beams cross bar lines. This
1421 behavior can be changed by setting @code{allowBeamBreak}.
1423 @cindex @code{allowBeamBreak}
1424 @cindex beams and line breaks
1426 @cindex beams, kneed
1428 @cindex auto-knee-gap
1434 @cindex Frenched staves
1436 Automatically kneed cross-staff beams cannot be used together with
1439 Beams do not avoid collisions with symbols around the notes, such as
1440 texts and accidentals.
1444 @node Setting automatic beam behavior
1445 @subsection Setting automatic beam behavior
1447 @cindex @code{autoBeamSettings}
1448 @cindex @code{(end * * * *)}
1449 @cindex @code{(begin * * * *)}
1450 @cindex automatic beams, tuning
1451 @cindex tuning automatic beaming
1453 @c [TODO: use \applycontext]
1455 In normal time signatures, automatic beams can start on any note but can
1456 only end in a few positions within the measure: beams can end on a beat,
1457 or at durations specified by the properties in
1458 @code{autoBeamSettings}. The defaults for @code{autoBeamSettings}
1459 are defined in @file{scm/auto-beam.scm}.
1461 The value of @code{autoBeamSettings} is changed with two functions,
1463 #(override-auto-beam-setting
1464 '(@var{be} @var{p} @var{q} @var{n} @var{m}) @var{a} @var{b}
1466 #(revert-auto-beam-setting '(@var{be} @var{p} @var{q} @var{n} @var{m}))
1468 Here, @var{be} is the symbol @code{begin} or @code{end}, and
1469 @var{context} is an optional context (default: @code{'Voice}). It
1470 determines whether the rule applies to begin or end-points. The
1471 quantity @var{p}/@var{q} refers to the length of the beamed notes (and
1472 `@code{* *}' designates notes of any length), @var{n}/@var{M} refers
1473 to a time signature (wildcards `@code{* *}' may be entered to
1474 designate all time signatures), @var{a}/@var{b} is a duration. By
1475 default, this command changes settings for the current voice. It is
1476 also possible to adjust settings at higher contexts, by adding a
1477 @var{context} argument.
1479 For example, if automatic beams should end on every quarter note, use
1482 #(override-auto-beam-setting '(end * * * *) 1 4 'Staff)
1484 Since the duration of a quarter note is 1/4 of a whole note, it is
1485 entered as @code{(ly:make-moment 1 4)}.
1487 The same syntax can be used to specify beam starting points. In this
1488 example, automatic beams can only end on a dotted quarter note
1490 #(override-auto-beam-setting '(end * * * *) 3 8)
1492 In 4/4 time signature, this means that automatic beams could end only on
1493 3/8 and on the fourth beat of the measure (after 3/4, that is 2 times
1494 3/8, has passed within the measure).
1496 Rules can also be restricted to specific time signatures. A rule that
1497 should only be applied in @var{N}/@var{M} time signature is formed by
1498 replacing the second asterisks by @var{N} and @var{M}. For example, a
1499 rule for 6/8 time exclusively looks like
1501 #(override-auto-beam-setting '(begin * * 6 8) @dots{})
1504 If a rule should be to applied only to certain types of beams, use the
1505 first pair of asterisks. Beams are classified according to the
1506 shortest note they contain. For a beam ending rule that only applies
1507 to beams with 32nd notes (and no shorter notes), use @code{(end 1 32 *
1510 @cindex automatic beam generation
1512 @cindex @code{autoBeaming}
1515 If beams are used to indicate melismata in songs, then automatic
1516 beaming should be switched off. This is done by setting
1517 @code{autoBeaming} to @code{#f}.
1521 @cindex @code{\autoBeamOff}
1522 @code{\autoBeamOff},
1523 @cindex @code{\autoBeamOn}
1529 If a score ends while an automatic beam has not been ended and is
1530 still accepting notes, this last beam will not be typeset at all. The
1531 same holds polyphonic voices, entered with @code{<< @dots{} \\ @dots{}
1532 >>}. If a polyphonic voice ends while an automatic beam is still
1533 accepting notes, it is not typeset.
1535 The rules for ending a beam depend on the shortest note in a beam.
1536 So, while it is possible to have different ending rules for eight
1537 beams and sixteenth beams, a beam that contains both eight and
1538 sixteenth notes will use the rules for the sixteenth beam.
1540 In the example below, the autobeamer makes eight beams and sixteenth
1541 end at 3 eights; the third beam can only be corrected by specifying
1544 @lilypond[quote,raggedright,fragment,relative=1]
1545 #(override-auto-beam-setting '(end * * * *) 3 8)
1546 % rather show case where it goes wrong
1547 %\time 12/8 c'8 c c c16 c c c c c c[ c c c] c8[ c] c4
1548 \time 12/8 c'8 c c c16 c c c c c c c c c c8 c c4
1550 It is not possible to specify beaming parameters that act differently in
1551 different parts of a measure. This means that it is not possible to use
1552 automatic beaming in irregular meters such as @code{5/8}.
1555 @section Accidentals
1558 This section describes how to change the way that accidentals are
1559 inserted automatically before the running notes.
1561 Common rules for typesetting accidentals have been canned in a
1562 function. This function is called as follows
1564 @cindex @code{set-accidental-style}
1566 #(set-accidental-style 'modern 'Voice)
1569 The function takes two arguments: a symbol that denotes the style (in
1570 the example, @code{modern}), and another symbol that denotes the
1571 context name (in this example, @code{Voice}). If no context name is
1572 supplied, @code{Staff} is the default.
1574 The following styles are supported
1577 This is the default typesetting behavior. It should correspond
1578 to 18th century common practice: Accidentals are
1579 remembered to the end of the measure in which they occur and
1580 only on their own octave.
1584 The normal behavior is to remember the accidentals on
1585 Staff-level. This variable, however, typesets accidentals
1586 individually for each voice. Apart from that, the rule is similar to
1589 This leads to some weird and often unwanted results
1590 because accidentals from one voice do not get canceled in other
1592 @lilypond[quote,raggedright,relative=1,fragment,verbatim]
1594 #(set-accidental-style 'voice)
1600 Hence you should only use @code{voice} if the voices
1601 are to be read solely by individual musicians. If the staff is to be
1602 used by one musician (e.g. a conductor) then you use
1603 @code{modern} or @code{modern-cautionary}
1607 @cindex @code{modern} style accidentals
1608 This rule corresponds to the common practice in the 20th
1610 This rule prints the same accidentals as @code{default}, but temporary
1611 accidentals also are canceled in other octaves. Furthermore,
1612 in the same octave, they also get canceled in the following
1615 @lilypond[quote,raggedright,fragment,verbatim]
1616 #(set-accidental-style 'modern)
1617 cis' c'' cis'2 | c'' c'
1620 @item @code{modern-cautionary}
1621 @cindex @code{modern-cautionary}
1622 This rule is similar to @code{modern}, but the
1623 ``extra'' accidentals (the ones not typeset by
1624 @code{default}) are typeset as cautionary accidentals.
1625 They are printed in reduced size or with parentheses
1626 @lilypond[quote,raggedright,fragment,verbatim]
1627 #(set-accidental-style 'modern-cautionary)
1628 cis' c'' cis'2 | c'' c'
1631 @cindex @code{modern-voice}
1633 This rule is used for multivoice accidentals to be read both by musicians
1634 playing one voice and musicians playing all voices. Accidentals are
1635 typeset for each voice, but they @emph{are} canceled across voices in
1636 the same @internalsref{Staff}.
1638 @cindex @code{modern-voice-cautionary}
1639 @item modern-voice-cautionary
1640 This rule is the same as @code{modern-voice}, but with the extra
1641 accidentals (the ones not typeset by @code{voice}) typeset
1642 as cautionaries. Even though all accidentals typeset by
1643 @code{default} @emph{are} typeset by this variable then
1644 some of them are typeset as cautionaries.
1647 @cindex @code{piano} accidentals
1648 This rule reflects 20th century practice for piano notation. Very similar to
1649 @code{modern} but accidentals also get canceled
1650 across the staves in the same @internalsref{GrandStaff} or
1651 @internalsref{PianoStaff}.
1653 @item piano-cautionary
1654 @cindex @code{#(set-accidental-style 'piano-cautionary)}
1655 As @code{#(set-accidental-style 'piano)' , str)} but with the extra accidentals
1656 typeset as cautionaries.
1659 @cindex @code{no-reset} accidental style
1661 This is the same as @code{default} but with accidentals lasting
1662 ``forever'' and not only until the next measure
1663 @lilypond[quote,raggedright,fragment,verbatim,relative=1]
1664 #(set-accidental-style 'no-reset)
1669 This is sort of the opposite of @code{no-reset}: Accidentals
1670 are not remembered at all---and hence all accidentals are
1671 typeset relative to the key signature, regardless of what was
1674 @lilypond[quote,raggedright,fragment,verbatim,relative=1]
1675 #(set-accidental-style 'forget)
1676 \key d\major c4 c cis cis d d dis dis
1683 Program reference: @internalsref{Accidental_engraver},
1684 @internalsref{Accidental}, and @internalsref{AccidentalPlacement}.
1689 Simultaneous notes are considered to be entered in sequential
1690 mode. This means that in a chord the accidentals are typeset as if the
1691 notes in the chord happened once at a time - in the order in which
1692 they appear in the input file.
1694 This is only a problem when accidentals in a chord depend on each
1695 other. This problem can be solved by manually inserting @code{!} and
1696 @code{?} for the problematic notes.
1698 In the default scheme, accidentals only depend on other
1699 accidentals with the same pitch on the same staff, so no conflicts are
1702 @node Expressive marks
1703 @section Expressive marks
1706 @c todo: should change ordering
1707 @c where to put text spanners, metronome marks,
1716 * Analysis brackets::
1718 * Fingering instructions::
1729 A slur indicates that notes are to be played bound or @emph{legato}.
1732 They are entered using parentheses
1733 @lilypond[quote,relative=2,fragment,verbatim]
1734 f( g)( a) a8 b( a4 g2 f4)
1739 @c TODO: should explain that ^( and _( set directions
1740 @c should set attachments with ^ and _ ?
1742 Slurs avoid crossing stems, and are generally attached to note heads.
1743 However, in some situations with beams, slurs may be attached to stem
1744 ends. If you want to override this layout you can do this through the
1745 object property @code{attachment} of @internalsref{Slur}. Its value
1746 is a pair of symbols, specifying the attachment type of the left and
1749 @lilypond[quote,fragment,relative=1,verbatim]
1751 \override Stem #'length = #5.5
1753 \override Slur #'attachment = #'(stem . stem)
1757 If a slur would strike through a stem or beam, the slur will be moved
1758 away upward or downward. If this happens, attaching the slur to the
1759 stems might look better
1761 @lilypond[quote,fragment,relative=1,verbatim]
1764 \override Slur #'attachment = #'(stem . stem)
1771 @cindex @code{\slurUp}
1773 @cindex @code{\slurDown}
1775 @cindex @code{\slurBoth}
1777 @cindex @code{\slurDotted}
1779 @cindex @code{\slurSolid}
1784 Program reference: @seeinternals{Slur}, and @internalsref{SlurEvent}.
1789 Producing nice slurs is a difficult problem, and LilyPond
1790 uses a simple, empiric method to produce slurs. In some cases, its
1794 @cindex Adjusting slurs
1796 @node Phrasing slurs
1797 @subsection Phrasing slurs
1799 @cindex phrasing slurs
1800 @cindex phrasing marks
1802 A phrasing slur (or phrasing mark) connects chords and is used to
1803 indicate a musical sentence. It is started using @code{\(} and @code{\)}
1806 @lilypond[quote,fragment,verbatim,relative=1]
1807 \time 6/4 c'\( d( e) f( e) d\)
1810 Typographically, the phrasing slur behaves almost exactly like a
1811 normal slur. However, they are treated as different objects. A
1812 @code{\slurUp} will have no effect on a phrasing slur; instead, you
1813 should use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
1814 @code{\phrasingSlurBoth}.
1816 The commands @code{\slurUp}, @code{\slurDown}, and @code{\slurBoth}
1817 will only affect normal slurs and not phrasing slurs.
1821 @cindex @code{\phrasingSlurUp}
1822 @code{\phrasingSlurUp},
1823 @cindex @code{\phrasingSlurDown}
1824 @code{\phrasingSlurDown},
1825 @cindex @code{\phrasingSlurBoth}
1826 @code{\phrasingSlurBoth}.
1830 Program reference: see also @internalsref{PhrasingSlur}, and
1831 @internalsref{PhrasingSlurEvent}.
1835 Phrasing slurs have the same limitations in their formatting as normal
1836 slurs. Putting phrasing slurs over rests leads to spurious warnings.
1839 @subsection Breath marks
1841 Breath marks are entered using @code{\breathe}
1844 @lilypond[quote,fragment,relative=1,verbatim]
1848 The glyph of the breath mark can be tuned by overriding the
1849 @code{text} property of the @code{BreathingSign} layout object with
1850 any markup text. For example,
1851 @lilypond[quote,fragment,verbatim,relative=1]
1853 \override BreathingSign #'text
1854 = #(make-musicglyph-markup "scripts-rvarcomma")
1861 Program reference: @internalsref{BreathingSign},
1862 @internalsref{BreathingSignEvent}.
1864 Examples: @inputfileref{input/regression,breathing-sign.ly}.
1867 @node Metronome marks
1868 @subsection Metronome marks
1871 @cindex beats per minute
1872 @cindex metronome marking
1874 Metronome settings can be entered as follows
1876 \tempo @var{duration} = @var{per-minute}
1879 In the MIDI output, they are interpreted as a tempo change, and in the
1880 paper output, a metronome marking is printed
1881 @cindex @code{\tempo}
1882 @lilypond[quote,fragment,verbatim]
1888 Program reference: @internalsref{MetronomeChangeEvent}.
1893 @subsection Text spanners
1894 @cindex Text spanners
1896 Some performance indications, e.g. @i{rallentando} or @i{accelerando},
1897 are written as texts, and extended over many measures with dotted
1898 lines. You can create such texts using text spanners: attach
1899 @code{\startTextSpan} and @code{\stopTextSpan} to the
1900 start and ending note of the spanner.
1902 The string to be printed, as well as the style, is set through object
1905 @lilypond[quote,fragment,relative=1,verbatim]
1908 \override TextSpanner #'direction = #-1
1909 \override TextSpanner #'edge-text = #'("rall " . "")
1910 c2\startTextSpan b c\stopTextSpan a
1917 Internals @internalsref{TextSpanEvent},
1918 @internalsref{TextSpanner}.
1920 Examples: @inputfileref{input/regression,text-spanner.ly}.
1923 @node Analysis brackets
1924 @subsection Analysis brackets
1926 @cindex phrasing brackets
1927 @cindex musicological analysis
1928 @cindex note grouping bracket
1930 Brackets are used in musical analysis to indicate structure in musical
1931 pieces. LilyPond supports a simple form of nested horizontal brackets.
1932 To use this, add the @internalsref{Horizontal_bracket_engraver} to
1933 @internalsref{Staff} context. A bracket is started with
1934 @code{\startGroup} and closed with @code{\stopGroup}
1936 @lilypond[quote,raggedright,verbatim]
1938 \notes \relative c'' {
1939 c4\startGroup\startGroup
1942 c4\stopGroup\stopGroup
1946 \Staff \consists "Horizontal_bracket_engraver"
1952 Program reference: @internalsref{HorizontalBracket},
1953 @internalsref{NoteGroupingEvent}.
1955 Examples: @inputfileref{input/regression,note-group-bracket.ly}.
1959 @subsection Articulations
1960 @cindex Articulations
1962 @cindex articulations
1966 A variety of symbols can appear above and below notes to indicate
1967 different characteristics of the performance. They are added to a note
1968 by adding a dash and the character signifying the
1969 articulation. They are demonstrated here
1971 @lilypondfile[quote,raggedright]{script-abbreviations.ly}
1973 The meanings of these shorthands can be changed. See
1974 @file{ly/script-init.ly} for examples.
1977 The script is automatically placed, but if you need to force
1978 directions, you can use @code{_} to force them down, or @code{^} to
1980 @lilypond[quote,fragment,verbatim]
1984 Other symbols can be added using the syntax
1985 @var{note}@code{\}@var{name}, e.g. @code{c4\fermata}. Again, they
1986 can be forced up or down using @code{^} and @code{_},
1989 @lilypond[quote,verbatim,fragment,relative=3]
1990 c\fermata c^\fermata c_\fermata
1997 @cindex staccatissimo
2006 @cindex organ pedal marks
2015 @cindex prallmordent
2019 @cindex thumb marking
2024 @lilypondfile[quote,raggedright]{script-chart.ly}
2028 @cindex @code{\scriptUp}
2030 @cindex @code{\scriptDown}
2032 @cindex @code{\scriptBoth}
2037 Program reference: @internalsref{ScriptEvent}, and @internalsref{Script}.
2041 These note ornaments appear in the printed output but have no
2042 effect on the MIDI rendering of the music.
2045 @node Fingering instructions
2046 @subsection Fingering instructions
2050 Fingering instructions can be entered using
2052 @var{note}-@var{digit}
2054 For finger changes, use markup texts
2056 @lilypond[quote,verbatim,raggedright,fragment]
2057 c'4-1 c'4-2 c'4-3 c'4-4
2058 c'^\markup { \finger "2-3" }
2061 @cindex finger change
2066 You can use the thumb-script to indicate that a note should be
2067 played with the thumb (e.g. in cello music)
2069 @lilypond[quote,verbatim,raggedright,fragment]
2070 <a' a''-3>8_\thumb <b' b''-3>_\thumb
2073 Fingerings for chords can also be added to individual notes
2074 of the chord by adding them after the pitches
2075 @lilypond[quote,verbatim,raggedright,fragment,relative=2]
2076 < c-1 e-2 g-3 b-5 >4
2080 iIn this case, setting @code{fingeringOrientations} will put fingerings next
2083 @lilypond[quote,verbatim,raggedright,fragment,relative=1]
2084 \set fingeringOrientations = #'(left down)
2085 <c-1 es-2 g-4 bes-5 > 4
2086 \set fingeringOrientations = #'(up right down)
2087 <c-1 es-2 g-4 bes-5 > 4
2088 \set fingeringOrientations = #'(right)
2092 The last note demonstrates how fingering instructions can be put close
2093 to note heads in monophonic music, using this feature.
2097 Program reference: @internalsref{FingerEvent}, and @internalsref{Fingering}.
2099 Examples: @inputfileref{input/regression,finger-chords.ly}.
2102 @subsection Text scripts
2103 @cindex Text scripts
2105 @cindex text items, non-empty
2106 @cindex non-empty texts
2108 It is possible to place arbitrary strings of text or markup text (see
2109 @ref{Text markup}) above or below notes by using a string
2110 @code{c^"text"}. By default, these indications do not influence the
2111 note spacing, but by using the command @code{\fatText}, the widths
2112 will be taken into account
2114 @lilypond[quote,fragment,raggedright,verbatim]
2116 c4^"longtext" \fatText c4_"longlongtext" c4
2120 It is possible to use @TeX{} commands in the strings, but this should
2121 be avoided because the exact dimensions of the string can then no
2126 @cindex @code{\fatText}
2128 @cindex @code{\emptyText}
2133 In this manual: @ref{Text markup}.
2135 Program reference: @internalsref{TextScriptEvent}, @internalsref{TextScript}.
2141 @subsection Grace notes
2144 @c should have blurb about accaciatura / appogiatura
2146 @cindex @code{\grace}
2150 Grace notes are ornaments that are written out. The most common ones
2151 are acciaccatura, which should be played as very short. It is denoted
2152 by a slurred small note with a slashed stem. The appoggiatura is a
2153 grace note that takes a fixed fraction of the main note, is and
2154 denoted as a slurred note in small print without a slash.
2155 They are entered with the commands @code{\acciaccatura} and
2156 @code{\appoggiatura}, as demonstrated in the following example
2159 @cindex appoggiatura
2160 @cindex acciaccatura
2162 @lilypond[quote,relative=2,verbatim,fragment]
2163 b4 \acciaccatura d8 c4 \appoggiatura e8 d4
2164 \acciaccatura { g16[ f] } e4
2167 Both are special forms of the @code{\grace} command. By prefixing this
2168 keyword to a music expression, a new one is formed, which will be
2169 printed in a smaller font and takes up no logical time in a measure.
2171 @lilypond[quote,relative=2,verbatim,fragment]
2173 \grace { c16[ d16] } c2 c4
2177 Unlike @code{\acciaccatura} and @code{\appoggiatura}, the
2178 @code{\grace} command does not start a slur.
2180 Internally, timing for grace notes is done using a second, `grace'
2181 time. Every point in time consists of two rational numbers: one
2182 denotes the logical time, one denotes the grace timing. The above
2183 example is shown here with timing tuples
2185 @lilypond[quote,raggedright]
2188 c4 \grace c16 c4 \grace {
2191 \new Lyrics \lyrics {
2194 ( \fraction 1 4 , \fraction -1 16 ) } 16 }
2195 \markup { (\fraction 1 4 , 0 ) } 4
2197 \markup { (\fraction 2 4 , \fraction "-1" 8 ) } 16
2198 \markup { (\fraction 2 4 , \fraction "-1" 16 ) } 16
2200 \markup { ( \fraction 2 4 , 0 ) }
2206 The placement of grace notes is synchronized between different staves.
2207 In the following example, there are two sixteenth graces notes for
2208 every eighth grace note
2210 @lilypond[quote,relative=2,verbatim,fragment]
2211 << \new Staff { e4 \grace { c16[ d e f] } e4 }
2212 \new Staff { c'4 \grace { g8[ b] } c4 } >>
2217 If you want to end a note with a grace, the standard trick is to put
2218 the grace notes after a ``space note''
2220 @lilypond[quote,fragment,verbatim,relative=2]
2223 { s2 \grace { c16[ d] } } >>
2229 By adjusting the duration of the skip note (here it is a half-note),
2230 the space between the main-note and the grace is adjusted.
2233 A @code{\grace} section will introduce special typesetting settings,
2234 for example, to produce smaller type, and set directions. Hence, when
2235 introducing layout tweaks, they should be inside the grace section,
2237 @lilypond[quote,fragment,verbatim,relative=2]
2240 \override Stem #'direction = #-1
2242 \revert Stem #'direction
2249 The overrides should also be reverted inside the grace section.
2251 If the layout of grace sections must be changed throughout the music,
2252 then this can be accomplished through the function
2253 @code{add-grace-property}. The following example undefines the Stem
2254 direction for this grace, so stems do not always point up.
2258 #(add-grace-property 'Voice 'Stem 'direction '())
2264 Another option is to change the variables @code{startGraceMusic},
2265 @code{stopGraceMusic}, @code{startAccacciaturaMusic},
2266 @code{stopAccacciaturaMusic}, @code{startAppoggiaturaMusic},
2267 @code{stopAppoggiaturaMusic}. More information is in the file
2268 @file{ly/grace-init.ly}.
2273 Program reference: @internalsref{GraceMusic}.
2277 A score that starts with an @code{\grace} section needs an explicit
2278 @code{\context Voice} declaration, otherwise the main note and grace
2279 note end up on different staves.
2281 Grace note synchronization can also lead to surprises. Staff notation,
2282 such as key signatures, bar lines, etc. are also synchronized. Take
2283 care when you mix staves with grace notes and staves without, for example,
2285 @lilypond[quote,relative=2,verbatim,fragment]
2286 << \new Staff { e4 \bar "|:" \grace c16 d4 }
2287 \new Staff { c4 \bar "|:" d4 } >>
2291 This can be remedied by inserting grace skips, for the above example
2294 \new Staff @{ c4 \bar "|:" \grace s16 d4 @} >>
2297 Grace sections should only be used within sequential music
2298 expressions. Nesting or juxtaposing grace sections is not supported,
2299 and might produce crashes or other errors.
2303 @subsection Glissando
2306 @cindex @code{\glissando}
2308 A glissando is a smooth change in pitch. It is denoted by a line or a
2309 wavy line between two notes.
2312 A glissando line can be requested by attaching a @code{\glissando} to
2315 @lilypond[quote,fragment,relative=1,verbatim]
2321 Program reference: @internalsref{Glissando}, and @internalsref{GlissandoEvent}.
2323 Example files: @file{input/regression,glissando.ly}
2329 Printing text over the line (such as @emph{gliss.}) is not supported.
2333 @subsection Dynamics
2346 @cindex @code{\ffff}
2356 Absolute dynamic marks are specified using a command after a note
2357 @code{c4\ff}. The available dynamic marks are @code{\ppp},
2358 @code{\pp}, @code{\p}, @code{\mp}, @code{\mf}, @code{\f}, @code{\ff},
2359 @code{\fff}, @code{\fff}, @code{\fp}, @code{\sf}, @code{\sff},
2360 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}
2362 @lilypond[quote,verbatim,raggedright,fragment,relative=1]
2363 c'\ppp c\pp c \p c\mp c\mf c\f c\ff c\fff
2373 A crescendo mark is started with @code{\<} and terminated with
2374 @code{\!}. A decrescendo is started with @code{\>} and also terminated
2375 with @code{\!}. Because these marks are bound to notes, if you must
2376 use spacer notes if multiple marks during one note are needed
2378 @lilypond[quote,fragment,verbatim]
2379 c''\< c''\! d''\> e''\!
2380 << f''1 { s4 s4\< s4\! \> s4\! } >>
2382 This may give rise to very short hairpins. Use @code{minimum-length}
2383 in @internalsref{Voice}.@internalsref{Hairpin} to lengthen them, for
2387 \override Staff.Hairpin #'minimum-length = #5
2390 You can also use a text saying @emph{cresc.} instead of hairpins. Here
2391 is an example how to do it
2393 @lilypond[quote,fragment,relative=2,verbatim]
2403 You can also supply your own texts
2404 @lilypond[quote,fragment,relative=1,verbatim]
2406 \set crescendoText = \markup { \italic "cresc. poco" }
2407 \set crescendoSpanner = #'dashed-line
2417 @cindex @code{\dynamicUp}
2419 @cindex @code{\dynamicDown}
2420 @code{\dynamicDown},
2421 @cindex @code{\dynamicBoth}
2422 @code{\dynamicBoth}.
2424 @cindex direction, of dynamics
2428 Program reference: @internalsref{CrescendoEvent},
2429 @internalsref{DecrescendoEvent}, and
2430 @internalsref{AbsoluteDynamicEvent}.
2432 Dynamics @internalsref{DynamicText} and @internalsref{Hairpin}
2433 objects. Vertical positioning of these symbols is handled by the
2434 @internalsref{DynamicLineSpanner} object.
2442 @cindex @code{\repeat}
2445 Repetition is a central concept in music, and multiple notations exist
2446 for repetitions. In LilyPond, most of these notations can be captured
2447 in a uniform syntax. One of the advantages is that they can be
2448 rendered in MIDI accurately.
2450 The following types of repetition are supported
2454 Repeated music is fully written (played) out. Useful for MIDI
2455 output, and entering repetitive music.
2458 This is the normal notation: Repeats are not written out, but
2459 alternative endings (volte) are printed, left to right.
2463 Alternative endings are written stacked. This has limited use but may be
2464 used to typeset two lines of lyrics in songs with repeats, see
2465 @inputfileref{input,star-spangled-banner.ly}.
2473 Make beat or measure repeats. These look like percent signs.
2479 * Repeats and MIDI::
2480 * Manual repeat commands::
2482 * Tremolo subdivisions::
2487 @subsection Repeat syntax
2490 LilyPond has one syntactic construct for specifying different types of
2491 repeats. The syntax is
2494 \repeat @var{variant} @var{repeatcount} @var{repeatbody}
2497 If you have alternative endings, you may add
2498 @cindex @code{\alternative}
2500 \alternative @code{@{} @var{alternative1}
2502 @var{alternative3} @dots{} @code{@}}
2504 where each @var{alternative} is a music expression. If you do not
2505 give enough alternatives for all of the repeats, the first alternative
2506 is assumed to be played more than once.
2508 Normal notation repeats are used like this
2509 @lilypond[quote,fragment,verbatim,relative=2]
2511 \repeat volta 2 { c4 d e f }
2512 \repeat volta 2 { f e d c }
2515 With alternative endings
2516 @lilypond[quote,fragment,verbatim,relative=2]
2518 \repeat volta 2 {c4 d e f}
2519 \alternative { {d2 d} {f f,} }
2523 @lilypond[quote,fragment,verbatim,relative=2]
2526 \repeat volta 4 { e | c2 d2 | e2 f2 | }
2527 \alternative { { g4 g g } { a | a a a a | b2. } }
2533 A nested repeat like
2542 is ambiguous, since it is is not clear to which @code{\repeat} the
2543 @code{\alternative} belongs. This ambiguity is resolved by always
2544 having the @code{\alternative} belong to the inner @code{\repeat}.
2545 For clarity, it is advisable to use braces in such situations.
2548 @node Repeats and MIDI
2549 @subsection Repeats and MIDI
2551 @cindex expanding repeats
2553 For instructions on how to expand repeats for MIDI output, see the
2554 example file @inputfileref{input/test,unfold-all-repeats.ly}.
2559 Timing information is not remembered at the start of an alternative,
2560 so after a repeat timing information must be reset by hand, for
2561 example by setting @code{Score.measurePosition} or entering
2562 @code{\partial}. Similarly, slurs or ties are also not repeated.
2565 @node Manual repeat commands
2566 @subsection Manual repeat commands
2568 @cindex @code{repeatCommands}
2570 The property @code{repeatCommands} can be used to control the layout of
2571 repeats. Its value is a Scheme list of repeat commands, where each repeat
2575 @item the symbol @code{start-repeat},
2576 which prints a @code{|:} bar line,
2577 @item the symbol @code{end-repeat},
2578 which prints a @code{:|} bar line,
2579 @item the list @code{(volta @var{text})},
2580 which prints a volta bracket saying @var{text}: The text can be specified as
2581 a text string or as a markup text, see @ref{Text markup}. Do not
2582 forget to change the font, as the default number font does not contain
2583 alphabetic characters. Or,
2584 @item the list @code{(volta #f)}, which
2585 stops a running volta bracket
2588 @lilypond[quote,verbatim,fragment,relative=2]
2590 \set Score.repeatCommands = #'((volta "93") end-repeat)
2592 \set Score.repeatCommands = #'((volta #f))
2599 Program reference: @internalsref{VoltaBracket}, @internalsref{RepeatedMusic},
2600 @internalsref{VoltaRepeatedMusic},
2601 @internalsref{UnfoldedRepeatedMusic}, and
2602 @internalsref{FoldedRepeatedMusic}.
2604 @node Tremolo repeats
2605 @subsection Tremolo repeats
2606 @cindex tremolo beams
2608 To place tremolo marks between notes, use @code{\repeat} with tremolo
2610 @lilypond[quote,verbatim,raggedright]
2612 \context Voice \notes\relative c' {
2613 \repeat "tremolo" 8 { c16 d16 }
2614 \repeat "tremolo" 4 { c16 d16 }
2615 \repeat "tremolo" 2 { c16 d16 }
2620 Tremolo marks can also be put on a single note. In this case, the
2621 note should not be surrounded by braces.
2622 @lilypond[quote,verbatim,raggedright]
2623 \repeat "tremolo" 4 c'16
2626 A similar mechanism is the tremolo subdivision, described in
2627 @ref{Tremolo subdivisions}.
2631 In this manual: @ref{Tremolo subdivisions}, @ref{Repeats}.
2633 Program reference: tremolo beams are @internalsref{Beam} objects. Single stem
2634 tremolos are @internalsref{StemTremolo} objects. The music expression is
2635 @internalsref{TremoloEvent}.
2637 Example files: @inputfileref{input/regression,chord-tremolo.ly},
2638 @inputfileref{input/regression,stem-tremolo.ly}.
2640 @node Tremolo subdivisions
2641 @subsection Tremolo subdivisions
2642 @cindex tremolo marks
2643 @cindex @code{tremoloFlags}
2645 Tremolo marks can be printed on a single note by adding
2646 `@code{:}[@var{length}]' after the note. The length must be at least
2647 8. A @var{length} value of 8 gives one line across the note stem. If
2648 the length is omitted, the last value (stored in @code{tremoloFlags})
2651 @lilypond[quote,verbatim,fragment]
2652 c'2:8 c':32 | c': c': |
2655 @c [TODO : stok is te kort bij 32en]
2659 Tremolos entered in this way do not carry over into the MIDI output.
2663 In this manual: @ref{Tremolo repeats}.
2665 Elsewhere: @internalsref{StemTremolo}, @internalsref{TremoloEvent}.
2667 @node Measure repeats
2668 @subsection Measure repeats
2670 @cindex percent repeats
2671 @cindex measure repeats
2673 In the @code{percent} style, a note pattern can be repeated. It is
2674 printed once, and then the pattern is replaced with a special sign.
2675 Patterns of a one and two measures are replaced by percent-like signs,
2676 patterns that divide the measure length are replaced by slashes
2678 @lilypond[quote,verbatim,raggedright]
2679 \repeat "percent" 4 { c'4 }
2680 \repeat "percent" 2 { c'2 es'2 f'4 fis'4 g'4 c''4 }
2685 Program reference: @internalsref{RepeatSlash}, @internalsref{PercentRepeat},
2686 @internalsref{PercentRepeatedMusic}, and
2687 @internalsref{DoublePercentRepeat}.
2691 @node Rhythmic music
2692 @section Rhythmic music
2696 * Showing melody rhythms::
2697 * Entering percussion::
2698 * Percussion staves::
2702 @node Showing melody rhythms
2703 @subsection Showing melody rhythms
2705 Sometimes you might want to show only the rhythm of a melody. This
2706 can be done with the rhythmic staff. All pitches of notes on such a
2707 staff are squashed, and the staff itself has a single line
2709 @lilypond[quote,fragment,relative=1,verbatim]
2710 \context RhythmicStaff {
2712 c4 e8 f g2 | r4 g r2 | g1:32 | r1 |
2718 Program reference: @internalsref{RhythmicStaff}.
2720 Examples: @inputfileref{input/regression,rhythmic-staff.ly}.
2723 @node Entering percussion
2724 @subsection Entering percussion
2730 Percussion notes may be entered in @code{\drums} mode, which is
2731 similar to @code{notes}. Each piece of percussion has a full name and
2732 an abbreviated name, and both be used in input files
2735 hihat hh bassdrum bd
2737 @lilypond[quote,raggedright]
2738 \new DrumStaff \drums { hihat hh bassdrum bd }
2741 The complete list of drum names is in the init file
2742 @file{ly/drumpitch-init.ly}.
2743 @c TODO: properly document this.
2747 Program reference: @internalsref{DrumNoteEvent}.
2749 @node Percussion staves
2750 @subsection Percussion staves
2754 A percussion part for more than one instrument typically uses a
2755 multiline staff where each position in the staff refers to one piece
2759 To typeset the music, the notes must be interpreted in a
2760 @internalsref{DrumStaff} and @internalsref{DrumVoice} contexts
2763 @lilypond[quote,raggedright,verbatim]
2764 up = \drums { crashcymbal4 hihat8 halfopenhihat hh hh hh openhihat }
2765 down = \drums { bassdrum4 snare8 bd r bd sn4 }
2768 \new DrumVoice { \voiceOne \up }
2769 \new DrumVoice { \voiceTwo \down }
2774 The above example shows verbose polyphonic notation. The short
2775 polyphonic notation, described in @ref{Polyphony}, can also be used if
2776 the @internalsref{DrumVoices} are instantiated by hand first. For example,
2778 @lilypond[quote,fragment,verbatim]
2780 \context DrumVoice = "1" { s1 *2 }
2781 \context DrumVoice = "2" { s1 *2 }
2785 { \repeat unfold 16 hh16 }
2794 There are also other layout possibilities. To use these, set the
2795 property @code{drumStyleTable} in context @internalsref{DrumVoice}.
2796 The following variables have been predefined
2800 is the default. It typesets a typical drum kit on a five-line staff
2802 @lilypond[quote,noindent]
2803 nam = \lyrics { cymc cyms cymr hh hhc hho hhho hhp cb hc
2804 bd sn ss tomh tommh tomml toml tomfh tomfl }
2805 mus = \drums { cymc cyms cymr hh | hhc hho hhho hhp | \break cb hc
2806 bd sn ss tomh tommh tomml toml tomfh tomfl s16 }
2808 << \new DrumStaff\with {
2809 \remove Bar_engraver
2810 \remove Time_signature_engraver
2811 \override Stem #'transparent = ##t
2812 \override Stem #'Y-extent-callback = ##f
2813 minimumVerticalExtent = #'(-4.0 . 5.0)
2815 \context Lyrics \nam
2818 %% need to do this, because of indented @itemize
2821 \override LyricText #'font-family = #'typewriter
2822 \override BarNumber #'transparent =##T
2826 The drum scheme supports six different toms. When there fewer toms, simply
2827 select the toms that produce the desired result, i.e. to get toms on
2828 the three middle lines you use @code{tommh}, @code{tomml} and
2831 @item timbales-style
2832 to typeset timbales on a two line staff
2834 @lilypond[quote,raggedright]
2835 nam = \lyrics { timh ssh timl ssl cb }
2836 mus = \drums { timh ssh timl ssl cb s16 }
2839 \context DrumStaff \with {
2840 \remove Bar_engraver
2841 \remove Time_signature_engraver
2842 \override Stem #'transparent = ##t
2843 \override Stem #'Y-extent-callback = ##f
2844 \override StaffSymbol #'line-count = #2
2845 \override StaffSymbol #'staff-space = #2
2846 minimumVerticalExtent = #'(-3.0 . 4.0)
2847 drumStyleTable = #timbales-style
2850 \override LyricText #'font-family = #'typewriter
2857 to typeset congas on a two line staff
2859 @lilypond[quote,raggedright]
2860 nam = \lyrics { cgh cgho cghm ssh cgl cglo cglm ssl }
2861 mus = \drums { cgh cgho cghm ssh cgl cglo cglm ssl s16 }
2864 \context DrumStaff\with {
2865 \remove Bar_engraver
2866 \remove Time_signature_engraver
2867 drumStyleTable = #congas-style
2868 \override StaffSymbol #'line-count = #2
2870 %% this sucks; it will lengthen stems.
2871 \override StaffSymbol #'staff-space = #2
2872 \override Stem #'transparent = ##t
2873 \override Stem #'Y-extent-callback = ##f
2876 \override LyricText #'font-family = #'typewriter
2882 to typeset bongos on a two line staff
2884 @lilypond[quote,raggedright]
2885 nam = \lyrics { boh boho bohm ssh bol bolo bolm ssl }
2886 mus = \drums { boh boho bohm ssh bol bolo bolm ssl s16 }
2889 \context DrumStaff\with {
2890 \remove Bar_engraver
2891 \remove Time_signature_engraver
2892 \override StaffSymbol #'line-count = #2
2893 drumStyleTable = #bongos-style
2895 %% this sucks; it will lengthen stems.
2896 \override StaffSymbol #'staff-space = #2
2897 \override Stem #'transparent = ##t
2898 \override Stem #'Y-extent-callback = ##f
2901 \override LyricText #'font-family = #'typewriter
2907 @item percussion-style
2908 to typeset all kinds of simple percussion on one line staves
2909 @lilypond[quote,raggedright]
2910 nam = \lyrics { tri trio trim gui guis guil cb cl tamb cab mar hc }
2911 mus = \drums { tri trio trim gui guis guil cb cl tamb cab mar hc s16 }
2914 \context DrumStaff\with{
2915 \remove Bar_engraver
2916 drumStyleTable = #percussion-style
2917 \override StaffSymbol #'line-count = #1
2918 \remove Time_signature_engraver
2919 \override Stem #'transparent = ##t
2920 \override Stem #'Y-extent-callback = ##f
2924 \override LyricText #'font-family = #'typewriter
2931 If you do not like any of the predefined lists you can define your own
2932 list at the top of your file
2934 @lilypond[quote,raggedright,verbatim]
2936 (bassdrum default #f -1)
2937 (snare default #f 0)
2939 (pedalhihat xcircle "stopped" 2)
2940 (lowtom diamond #f 3)))
2941 up = \drums { hh8 hh hh hh hhp4 hhp }
2942 down = \drums { bd4 sn bd toml8 toml }
2945 \set DrumStaff.drumStyleTable
2946 = #(alist->hash-table mydrums)
2947 \new DrumVoice { \voiceOne \up }
2948 \new DrumVoice { \voiceTwo \down }
2956 Init files: @file{ly/drumpitch-init.ly}.
2958 Program reference: @internalsref{DrumStaff}, @internalsref{DrumVoice}.
2962 Because general MIDI does not contain rim shots, the sidestick is used
2963 for this purpose instead.
2966 @section Piano music
2968 Piano staves are two normal staves coupled with a brace. The staves
2969 are largely independent, but sometimes voices can cross between the
2970 two staves. The same notation is also used for harps and other key
2971 instruments. The @internalsref{PianoStaff} is especially built to
2972 handle this cross-staffing behavior. In this section we discuss the
2973 @internalsref{PianoStaff} and some other pianistic peculiarities.
2977 * Automatic staff changes::
2978 * Manual staff switches::
2981 * Staff switch lines::
2986 There is no support for putting chords across staves. You can get
2987 this result by increasing the length of the stem in the lower stave so
2988 it reaches the stem in the upper stave, or vice versa. An example is
2989 included with the distribution as
2990 @inputfileref{input/test,stem-cross-staff.ly}.
2992 Dynamics are not centered, but kludges do exist. See
2993 @inputfileref{input/template,piano-dynamics.ly}.
2995 @cindex cross staff stem
2996 @cindex stem, cross staff
2997 @cindex distance between staves in piano music
2999 The distance between the two staves is normally fixed across the
3000 entire score. It is possible to tune this per system, but it does
3001 require arcane command incantations. See
3002 @inputfileref{input/test,piano-staff-distance.ly}.
3005 @node Automatic staff changes
3006 @subsection Automatic staff changes
3007 @cindex Automatic staff changes
3009 Voices can switch automatically between the top and the bottom
3010 staff. The syntax for this is
3014 \autochange \context Voice @{ @dots{}@var{music}@dots{} @}
3019 The two staves of the piano staff must be named @code{up} and
3022 A @code{\relative} section that is outside of @code{\autochange} has
3023 no effect on the pitches of @var{music}, so, if necessary, put
3024 @code{\relative} inside @code{\autochange} like
3028 \autochange \relative @dots{} \new Voice @dots{}
3033 The autochanger switches on basis of pitch (middle C is the turning
3034 point), and it looks ahead skipping over rests to switch in
3035 advance. Here is a practical example
3037 @lilypond[quote,verbatim,raggedright]
3038 \score { \notes \context PianoStaff <<
3039 \context Staff = "up" {
3040 \autochange \new Voice \relative c' {
3041 g4 a b c d r4 a g } }
3042 \context Staff = "down" {
3049 In this example, spacer rests are used to prevent the bottom staff from
3050 terminating too soon.
3055 In this manual: @ref{Manual staff switches}.
3057 Program reference: @internalsref{AutoChangeMusic}.
3063 The staff switches often do not end up in optimal places. For high
3064 quality output, staff switches should be specified manually.
3067 @code{\autochange} cannot be inside @code{\times}.
3069 Internally, the @code{\partcombine} interprets both arguments as
3070 @code{Voice}s named @code{one} and @code{two}, and then decides when
3071 the parts can be combined. Consequently, if the arguments switch to
3072 differently named @internalsref{Voice} contexts, the events in those
3076 @node Manual staff switches
3077 @subsection Manual staff switches
3079 @cindex manual staff switches
3080 @cindex staff switch, manual
3082 Voices can be switched between staves manually, using the following command
3084 \change Staff = @var{staffname} @var{music}
3088 The string @var{staffname} is the name of the staff. It switches the
3089 current voice from its current staff to the Staff called
3090 @var{staffname}. Typically @var{staffname} is @code{"up"} or
3091 @code{"down"}. The @context{Staff} referred to must already exist, so
3092 usually the setup for a score will start with a setup of the staves,
3096 \context Staff = up @{
3097 \skip 1 * 10 %@emph{ keep staff alive}
3099 \context Staff = down @{
3100 \skip 1 * 10 %@emph{idem}
3106 and the @context{Voice} is inserted afterwards
3109 \context Staff = down
3110 \new Voice @{ @dots{} \change Staff = up @dots{} @}
3118 Pianos have pedals that alter the way sound are produced. Generally, a
3119 piano has three pedals, sustain, una corda, and sostenuto.
3122 Piano pedal instruction can be expressed by attaching
3123 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
3124 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
3127 @lilypond[quote,fragment,verbatim]
3128 c'4\sustainDown c'4\sustainUp
3131 What is printed can be modified by setting @code{pedal@var{X}Strings},
3132 where @var{X} is one of the pedal types: @code{Sustain},
3133 @code{Sostenuto} or @code{UnaCorda}. Refer to
3134 @internalsref{SustainPedal} in the program reference for more
3137 Pedals can also be indicated by a sequence of brackets, by setting the
3138 @code{pedalSustainStyle} property to @code{bracket} objects
3140 @lilypond[quote,fragment,verbatim,relative=2]
3141 \set Staff.pedalSustainStyle = #'bracket
3143 b\sustainUp\sustainDown
3144 b g \sustainUp a \sustainDown \bar "|."
3147 A third style of pedal notation is a mixture of text and brackets,
3148 obtained by setting the @code{pedalSustainStyle} style property to
3151 @lilypond[quote,fragment,verbatim,relative=2]
3152 \set Staff.pedalSustainStyle = #'mixed
3154 b\sustainUp\sustainDown
3155 b g \sustainUp a \sustainDown \bar "|."
3158 The default `*Ped.' style for sustain and damper pedals corresponds to
3159 style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
3162 @lilypond[quote,fragment,verbatim,relative=2]
3163 c\sostenutoDown d e c, f g a\sostenutoUp
3166 For fine-tuning of the appearance of a pedal bracket, the properties
3167 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
3168 @code{PianoPedalBracket} objects (see
3169 @internalsref{PianoPedalBracket} in the Program reference) can be modified. For example, the
3170 bracket may be extended to the end of the note head
3172 @lilypond[quote,fragment,verbatim,relative=2]
3173 \override Staff.PianoPedalBracket
3174 #'shorten-pair = #'(0 . -1.0)
3175 c\sostenutoDown d e c, f g a\sostenutoUp
3179 @subsection Arpeggio
3182 @cindex broken arpeggio
3183 @cindex @code{\arpeggio}
3185 You can specify an arpeggio sign on a chord by attaching an
3186 @code{\arpeggio} to a chord
3189 @lilypond[quote,fragment,relative=1,verbatim]
3193 When an arpeggio crosses staves, you attach an arpeggio to the chords
3194 in both staves, and set
3195 @internalsref{PianoStaff}.@code{connectArpeggios}
3197 @lilypond[quote,fragment,relative=1,verbatim]
3198 \context PianoStaff <<
3199 \set PianoStaff.connectArpeggios = ##t
3200 \new Staff { <c' e g c>\arpeggio }
3201 \new Staff { \clef bass <c,, e g>\arpeggio }
3205 The direction of the arpeggio is sometimes denoted by adding an
3206 arrowhead to the wiggly line
3208 @lilypond[quote,fragment,relative=1,verbatim]
3217 A square bracket on the left indicates that the player should not
3218 arpeggiate the chord
3220 @lilypond[quote,fragment,relative=1,verbatim]
3227 @cindex @code{\arpeggio}
3229 @cindex @code{\arpeggioUp}
3231 @cindex @code{\arpeggioDown}
3233 @cindex @code{\arpeggioBoth}
3234 @code{\arpeggioBoth},
3235 @cindex @code{\arpeggioBracket}
3236 @code{\arpeggioBracket}.
3240 Program reference: @internalsref{ArpeggioEvent} music expressions lead to
3241 @internalsref{Arpeggio} objects. Cross staff arpeggios are
3242 @internalsref{PianoStaff}.@internalsref{Arpeggio}.
3246 It is not possible to mix connected arpeggios and unconnected
3247 arpeggios in one @internalsref{PianoStaff} at the same time.
3249 @node Staff switch lines
3250 @subsection Staff switch lines
3253 @cindex follow voice
3254 @cindex staff switching
3257 @cindex @code{followVoice}
3259 Whenever a voice switches to another staff a line connecting the notes
3260 can be printed automatically. This is enabled if the property
3261 @code{PianoStaff.followVoice} is set to true
3263 @lilypond[quote,fragment,relative=1,verbatim]
3264 \context PianoStaff <<
3265 \set PianoStaff.followVoice = ##t
3266 \context Staff \context Voice {
3271 \context Staff=two { \clef bass \skip 1*2 }
3277 The associated object is @internalsref{VoiceFollower}.
3281 @cindex @code{\showStaffSwitch}
3282 @code{\showStaffSwitch},
3283 @cindex @code{\hideStaffSwitch}
3284 @code{\hideStaffSwitch}.
3288 @section Vocal music
3290 This section discusses how to enter and print lyrics.
3294 * The Lyrics context::
3299 @node Entering lyrics
3300 @subsection Entering lyrics
3304 @cindex @code{\lyrics}
3307 Lyrics are entered in a special input mode. This mode is is introduced
3308 by the keyword @code{\lyrics}. In this mode you can enter lyrics, with
3309 punctuation and accents without any hassle. Syllables are entered like
3310 notes, but with pitches replaced by text. For example,
3312 \lyrics @{ Twin-4 kle4 twin- kle litt- le star2 @}
3315 A word in Lyrics mode begins with: an alphabetic character, @code{_},
3316 @code{?}, @code{!}, @code{:}, @code{'}, the control characters @code{^A}
3317 through @code{^F}, @code{^Q} through @code{^W}, @code{^Y}, @code{^^},
3318 any 8-bit character with ASCII code over 127, or a two-character
3319 combination of a backslash followed by one of @code{`}, @code{'},
3320 @code{"}, or @code{^}.
3322 Subsequent characters of a word can be any character that is not a digit
3323 and not white space. One important consequence of this is that a word
3324 can end with @code{@}}. The following example is usually a bug. The
3325 syllable includes a @code{@}}, and hence the opening brace is not balanced
3327 \lyrics @{ twinkle@}
3330 @cindex @code{\property}, in @code{\lyrics}
3331 Similarly, a period following a alphabetic sequence, is included in
3332 the resulting string. As a consequence, spaces must be inserted around
3335 \override Score . LyricText #'font-shape = #'italic
3339 @cindex spaces, in lyrics
3340 @cindex quotes, in lyrics
3342 Any @code{_} character which appears in an unquoted word is converted
3343 to a space. This provides a mechanism for introducing spaces into words
3344 without using quotes. Quoted words can also be used in Lyrics mode to
3345 specify words that cannot be written with the above rules
3348 \lyrics @{ He said: "\"Let" my peo ple "go\"" @}
3350 However, at least for english texts, you should use
3352 \lyrics @{ He said: ``Let my peo ple go'' @}
3354 to get the correct shape of the starting and ending quote.
3358 Centered hyphens are entered as `@code{-}@code{-}' between syllables.
3359 The hyphen will have variable length depending on the space between
3360 the syllables and it will be centered between the syllables.
3365 When a lyric is sung over many notes (this is called a melisma), this is
3366 indicated with a horizontal line centered between a syllable and the
3367 next one. Such a line is called an extender line, and it is entered as
3372 Program reference: events @internalsref{LyricEvent},
3373 @internalsref{HyphenEvent}, and @internalsref{ExtenderEvent}. Objects
3374 @internalsref{LyricHyphen}, @internalsref{LyricExtender} and
3375 @internalsref{LyricText}.
3377 Examples: @inputfileref{input/test,lyric-hyphen-retain.ly}.
3381 The definition of lyrics mode is too complex.
3385 @node The Lyrics context
3386 @subsection The Lyrics context
3389 @c TODO: document \newlyrics
3391 Lyrics are printed by interpreting them in a @internalsref{Lyrics} context
3393 \context Lyrics \lyrics @dots{}
3396 @cindex automatic syllable durations
3397 @cindex @code{\lyricsto}
3398 @cindex lyrics and melodies
3400 This will place the lyrics according to the durations that were
3401 entered. The lyrics can also be aligned under a given melody
3402 automatically. In this case, it is no longer necessary to enter the
3403 correct duration for each syllable. This is achieved by combining the
3404 melody and the lyrics with the @code{\lyricsto} expression
3406 \lyricsto @var{name} \new Lyrics \lyrics @dots{}
3409 This aligns the lyrics to the
3411 notes of the @internalsref{Voice} context called @var{name}, which has
3412 to exist. Therefore, normally the @code{Voice} is specified first, and
3413 then the lyrics are specified with @code{\lyricsto}.
3415 For different or more complex orderings, the best way is to setup the
3416 hierarchy of staves and lyrics first, e.g.
3418 \context ChoirStaff \notes <<
3419 \context Lyrics = sopranoLyrics @{ s1 @}
3420 \context Voice = soprano @{ @emph{music} @}
3421 \context Lyrics = tenorLyrics @{ s1 @}
3422 \context Voice = tenor @{ @emph{music} @}
3425 and then combine the appropriate melodies and lyric lines
3427 \lyricsto "soprano" \context Lyrics = sopranoLyrics
3432 The final input would resemble
3435 << \context ChoirStaff \notes << @emph{setup the music} >>
3436 \lyricsto "soprano" @emph{etc}
3437 \lyricsto "alto" @emph{etc}
3443 The @code{\lyricsto} command detects melismata: it only puts one
3444 syllable under a tied or slurred group of notes. If you want to force
3445 an unslurred group of notes to be a melisma, insert @code{\melisma}
3446 after the first note of the group, and @code{\melismaEnd} after the
3449 @lilypond[quote,relative=2,raggedright,fragment,verbatim]
3451 \context Voice = "lala" {
3459 \lyricsto "lala" \new Lyrics \lyrics {
3465 In addition, notes are considered a melisma if they are manually
3466 beamed, and automatic beaming (see @ref{Setting automatic beam
3467 behavior}) is switched off. The criteria for deciding melismata can
3468 be tuned with the property @code{melismaBusyProperties}. See
3469 @internalsref{Melisma_translator} in the program reference for more
3472 Lyrics can also be entered without @code{\lyricsto}. In this case the
3473 durations of each syllable must be entered explicitly, for example,
3480 Alignment to a melody can be specified with the @code{associatedVoice}
3484 \set associatedVoice = #"melody"
3487 Here is an example demonstrating manual lyric durations,
3489 @lilypond[relative=1,verbatim,fragment]
3490 << \context Voice = melody {
3494 \new Lyrics \lyrics {
3495 \set associatedVoice = #"melody"
3503 When multiple stanzas are put on the same melody, it can happen that
3504 two stanzas have melismata in different locations. This can be
3505 remedied by switching off melismata for one
3506 @internalsref{Lyrics}. This is achieved by setting
3507 the @code{ignoreMelismata} property to @code{#t}. An example is shown
3508 in @inputfileref{input/regression,lyric-combine-new.ly}.
3511 @cindex choral score
3513 A complete example of a SATB score setup is in the file
3514 @inputfileref{input/template,satb.ly}.
3519 @code{\melisma}, @code{\melismaEnd}
3520 @cindex @code{\melismaEnd}
3521 @cindex @code{\melisma}
3525 Program reference: Music expressions: @internalsref{LyricCombineMusic},
3526 Contexts: @internalsref{Lyrics}, @internalsref{Melisma_translator}.
3528 Examples: @inputfileref{input/template,satb.ly},
3529 @inputfileref{input/regression,lyric-combine-new.ly}.
3533 Melismata are not detected automatically, and extender lines must be
3537 For proper processing of extender lines, the
3538 @internalsref{Lyrics} and @internalsref{Voice} should be
3539 linked. This can be achieved either by using @code{\lyricsto} or by
3540 setting corresponding names for both contexts. The latter is explained
3541 in @ref{More stanzas}.
3543 @c TODO: document \new Staff << Voice \lyricsto >> bug
3546 @subsection More stanzas
3548 @cindex phrasing, in lyrics
3551 The lyrics should be aligned with the note heads of the melody. To
3552 achieve this, each line of lyrics should be marked to correspond with
3553 the melodic line. This is done automatically when @code{\lyricsto},
3554 but it can also be done manually.
3556 To this end, give the @internalsref{Voice} context an identity
3558 \context Voice = duet @{
3563 Then set the @internalsref{Lyrics} contexts to names starting with
3564 that identity followed by a dash. In the preceding example, the
3565 @internalsref{Voice} identity is @code{duet}, so the identities of the
3566 @internalsref{Lyrics}s are marked @code{duet-1} and @code{duet-2}
3568 \context Lyrics = "duet-1" @{
3569 Hi, my name is Bert. @}
3570 \context Lyrics = "duet-2" @{
3571 Ooooo, ch\'e -- ri, je t'aime. @}
3574 The complete example is shown here
3575 @lilypond[quote,raggedright,verbatim]
3578 \notes \relative c'' \context Voice = duet {
3582 \lyricsto "duet" \new Lyrics \lyrics {
3583 \set vocalName = "Bert"
3584 Hi, my name is Bert. }
3585 \lyricsto "duet" \new Lyrics \lyrics {
3586 \set vocalName = "Ernie"
3587 Ooooo, ch\'e -- ri, je t'aime. }
3593 @cindex stanza number
3594 @cindex singer's names
3595 @cindex name of singer
3597 Stanza numbers can be added by setting @code{stanza}, e.g.
3599 @lilypond[quote,verbatim,relative=2]
3601 \context Voice = duet {
3602 \time 3/4 g2 e4 a2 f4 g2. }
3603 \lyricsto "duet" \new Lyrics \lyrics {
3605 Hi, my name is Bert. }
3609 This example also demonstrates how names of the singers can be added
3610 using @code{vocalName} analogous to instrument annotations for staves.
3611 A short version may be entered as @code{vocNam}.
3613 To make empty spaces in lyrics, use @code{\skip}.
3618 Program reference: Layout objects @internalsref{LyricText} and
3619 @internalsref{VocalName}. Music expressions
3620 @internalsref{LyricEvent}.
3626 Input for lyrics introduces a syntactical ambiguity
3633 is interpreted as assigning a string identifier @code{\foo} such that
3634 it contains @code{"bar"}. However, it could also be interpreted as
3635 making or a music identifier @code{\foo} containing the syllable
3636 `bar'. The force the latter interpretation, use
3646 The term @emph{ambitus} denotes a range of pitches for a given voice
3647 in a part of music. It also may denote the pitch range that a musical
3648 instrument is capable of playing. Ambituses are printed on vocal
3649 parts, so singers can easily determine if it meets his or her
3652 It denoted at the beginning of a piece near the initial clef. The
3653 range is graphically specified by two note heads, that represent the
3654 minimum and maximum pitch. To print such ambituses, add the
3655 @internalsref{Ambitus_engraver} to the @internalsref{Voice} context,
3662 \consists Ambitus_engraver
3667 This results in the following output
3669 @lilypond[quote,raggedright]
3672 \notes \relative c' <<
3683 \consists Ambitus_engraver
3689 If you have multiple voices in a single staff, and you want a single
3690 ambitus per staff rather than per each voice, add the
3691 @internalsref{Ambitus_engraver} to the @internalsref{Staff} context
3692 rather than to the @internalsref{Voice} context.
3694 It is possible to tune individual ambituses for multiple voices on a
3695 single staff, for example by erasing or shifting them horizontally. An
3696 example is in @inputfileref{input/test,ambitus-mixed.ly}.
3700 Program reference: @internalsref{Ambitus}.
3702 Examples: @inputfileref{input/regression,ambitus.ly},
3703 @inputfileref{input/test,ambitus-mixed.ly}.
3707 There is no collision handling in the case of multiple per-voice
3713 Tablature notation is used for notating music for plucked string
3714 instruments. It notates pitches not by using note heads, but by
3715 indicating on which string and fret a note must be played. LilyPond
3716 offers limited support for tablature.
3719 * Tablatures basic::
3720 * Non-guitar tablatures::
3723 @node Tablatures basic
3724 @subsection Tablatures basic
3725 @cindex Tablatures basic
3727 The string number associated to a note is given as a backslash
3728 followed by a number, e.g. @code{c4\3} for a C quarter on the third
3729 string. By default, string 1 is the highest one, and the tuning
3730 defaults to the standard guitar tuning (with 6 strings). The notes
3731 are printed as tablature, by using @internalsref{TabStaff} and
3732 @internalsref{TabVoice} contexts
3734 @lilypond[quote,fragment,verbatim]
3735 \notes \context TabStaff {
3743 When no string is specified, the first string that does not give a
3744 fret number less than @code{minimumFret} is selected. The default
3745 value for @code{minimumFret} is 0
3750 \set TabStaff.minimumFret = #8
3753 @lilypond[quote,noindent,raggedright]
3757 \set TabStaff.minimumFret = #8
3761 \context StaffGroup <<
3762 \context Staff { \clef "G_8" \frag }
3763 \context TabStaff { \frag }
3770 Program reference: @internalsref{TabStaff}, @internalsref{TabVoice}, and
3771 @internalsref{StringNumberEvent}.
3775 Chords are not handled in a special way, and hence the automatic
3776 string selector may easily select the same string to two notes in a
3780 @node Non-guitar tablatures
3781 @subsection Non-guitar tablatures
3782 @cindex Non-guitar tablatures
3784 You can change the number of strings, by setting the number of lines
3785 in the @internalsref{TabStaff}.
3787 You can change the tuning of the strings. A string tuning is given as
3788 a Scheme list with one integer number for each string, the number
3789 being the pitch (measured in semitones relative to middle C) of an
3790 open string. The numbers specified for @code{stringTuning} are the
3791 numbers of semitones to subtract or add, starting the specified pitch
3792 by default middle C, in string order. Thus, the notes are e, a, d, and
3795 @lilypond[quote,fragment,verbatim]
3796 \context TabStaff <<
3797 \set TabStaff.stringTunings = #'(-5 -10 -15 -20)
3800 a,4 c' a e' e c' a e'
3807 No guitar special effects have been implemented.
3811 Program reference: @internalsref{Tab_note_heads_engraver}.
3815 @section Chord names
3818 LilyPond has support for both printing chord names. Chords may be
3819 entered in musical chord notation, i.e. @code{< .. >}, but they can
3820 also be entered by name. Internally, the chords are represented as a
3821 set of pitches, so they can be transposed
3824 @lilypond[quote,verbatim,raggedright]
3825 twoWays = \notes \transpose c c' {
3835 << \context ChordNames \twoWays
3836 \context Voice \twoWays >> }
3839 This example also shows that the chord printing routines do not try to
3840 be intelligent. The last chord (@code{f bes d}) is not interpreted as
3846 * Printing chord names::
3851 @subsection Chords mode
3854 Chord mode is a mode where you can input sets of pitches using common
3855 names. It is introduced by the keyword @code{\chords}.
3856 In chords mode, a chord is entered by the root, which is entered
3858 @lilypond[quote,fragment,verbatim,relative=2]
3859 \chords { es4. d8 c2 }
3864 Other chords may be entered by suffixing a colon, and introducing a
3865 modifier, and optionally, a number
3867 @lilypond[quote,fragment,verbatim]
3868 \chords { e1:m e1:7 e1:m7 }
3870 The first number following the root is taken to be the `type' of the
3871 chord, thirds are added to the root until it reaches the specified
3873 @lilypond[quote,fragment,verbatim]
3874 \chords { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 }
3877 @cindex root of chord
3878 @cindex additions, in chords
3879 @cindex removals, in chords
3881 More complex chords may also be constructed adding separate steps
3882 to a chord. Additions are added after the number following
3883 the colon, and are separated by dots
3885 @lilypond[quote,verbatim,fragment]
3886 \chords { c:5.6 c:3.7.8 c:3.6.13 }
3888 Chord steps can be altered by suffixing a @code{-} or @code{+} sign
3890 @lilypond[quote,verbatim,fragment]
3891 \chords { c:7+ c:5+.3- c:3-.5-.7- }
3893 Removals are specified similarly, and are introduced by a caret. They
3894 must come after the additions
3895 @lilypond[quote,verbatim,fragment]
3896 \chords { c^3 c:7^5 c:9^3.5 }
3899 Modifiers can be used to change pitches. The following modifiers are
3903 is the minor chord. This modifier lowers the 3rd and (if present) the 7th step.
3905 is the diminished chord. This modifier lowers the 3rd, 5th and (if present)
3908 is the augmented chord. This modifier raises the 5th step.
3910 is the major 7th chord. This modifier raises the 7th step if present.
3912 is the suspended 4th or 2nd. This modifier removes the 3rd
3913 step. Append either @code{2} or @code{4} to add the 2nd or 4th step to
3916 Modifiers can be mixed with additions
3917 @lilypond[quote,verbatim,fragment]
3918 \chords { c:sus4 c:7sus4 c:dim7 c:m6 }
3921 @cindex modifiers, in chords.
3928 Since an unaltered 11 does not sound good when combined with an
3929 unaltered 3, the 11 is removed in this case (unless it is added
3932 @lilypond[quote,fragment,verbatim]
3933 \chords { c:13 c:13.11 c:m13 }
3938 An inversion (putting one pitch of the chord on the bottom), as well
3939 as bass notes, can be specified by appending
3940 @code{/}@var{pitch} to the chord
3941 @lilypond[quote,fragment,verbatim]
3942 \chords { c1 c/g c/f }
3946 A bass note can be added instead of transposed out of the chord,
3947 by using @code{/+}@var{pitch}.
3949 @lilypond[quote,fragment,verbatim]
3950 \chords { c1 c/+g c/+f }
3953 Chords is a mode similar to @code{\lyrics}, @code{\notes} etc. Most
3954 of the commands continue to work, for example, @code{r} and
3955 @code{\skip} can be used to insert rests and spaces, and property
3956 commands may be used to change various settings.
3962 Each step can only be present in a chord once. The following
3963 simply produces the augmented chord, since @code{5+} is interpreted
3966 @lilypond[quote,verbatim,fragment]
3967 \chords { c:5.5-.5+ }
3971 @node Printing chord names
3972 @subsection Printing chord names
3974 @cindex printing chord names
3978 For displaying printed chord names, use the @internalsref{ChordNames} context.
3979 The chords may be entered either using the notation
3980 described above, or directly using @code{<} and @code{>}
3982 @lilypond[quote,verbatim,raggedright]
3984 \chords {a1 b c} <d' f' a'> <e' g' b'>
3988 \context ChordNames \scheme
3989 \context Staff \scheme
3994 You can make the chord changes stand out by setting
3995 @internalsref{ChordNames}.@code{chordChanges} to true. This will only
3996 display chord names when there is a change in the chords scheme and at
3997 the start of a new line
3999 @lilypond[quote,verbatim,linewidth=9\cm]
4001 c1:m c:m \break c:m c:m d
4005 \context ChordNames {
4006 \set chordChanges = ##t
4008 \context Staff \transpose c c' \scheme
4013 The default chord name layout is a system for Jazz music, proposed by
4014 Klaus Ignatzek (see @ref{Literature list}). It can be tuned through the
4015 following properties
4018 @cindex chordNameExceptions
4019 @item chordNameExceptions
4020 This is a list that contains the chords that have special formatting.
4022 @inputfileref{input/regression,chord-name-exceptions.ly}.
4023 @cindex exceptions, chord names.
4026 @cindex majorSevenSymbol
4027 @item majorSevenSymbol
4028 This property contains the markup object used for the 7th step, when
4029 it is major. Predefined options are @code{whiteTriangleMarkup} and
4030 @code{blackTriangleMarkup}. See
4031 @inputfileref{input/regression,chord-name-major7.ly} for an example.
4033 @cindex chordNameSeparator
4034 @item chordNameSeparator
4035 Different parts of a chord name are normally separated by a
4036 slash. By setting @code{chordNameSeparator}, you can specify other
4038 @lilypond[quote,fragment,verbatim]
4039 \context ChordNames \chords {
4041 \set chordNameSeparator
4042 = \markup { \typewriter "|" }
4047 @cindex chordRootNamer
4048 @item chordRootNamer
4049 The root of a chord is usually printed as a letter with an optional
4050 alteration. The transformation from pitch to letter is done by this
4051 function. Special note names (for example, the German ``H'' for a
4052 B-chord) can be produced by storing a new function in this property.
4054 The predefined variables @code{\germanChords},
4055 @code{\semiGermanChords} set these variables.
4058 @cindex chordNoteNamer
4059 @item chordNoteNamer
4060 The default is to print single pitch, e.g. the bass note, using the
4061 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
4062 to a specialized function to change this behavior. For example, the
4063 base can be printed in lower case.
4068 There are also two other chord name schemes implemented: an alternate
4069 Jazz chord notation, and a systematic scheme called Banter chords. The
4070 alternate jazz notation is also shown on the chart in @ref{Chord name
4071 chart}. Turning on these styles is described in the input file
4072 @inputfileref{input/test,chord-names-jazz.ly}.
4076 @cindex chords, jazz
4081 @cindex @code{\germanChords}
4082 @code{\germanChords},
4083 @cindex @code{\semiGermanChords}
4084 @code{\semiGermanChords}.
4091 Examples: @inputfileref{input/regression,chord-name-major7.ly},
4092 @inputfileref{input/regression,chord-name-exceptions.ly},
4093 @inputfileref{input/test,chord-names-jazz.ly},
4094 @inputfileref{input/test,chord-names-german.ly}.
4096 Init files: @file{scm/chords-ignatzek.scm}, and @file{scm/chord-entry.scm}.
4101 Chord names are determined solely from the list of pitches. Chord
4102 inversions are not identified, and neither are added bass notes. This
4103 may result in strange chord names when chords are entered with the
4104 @code{< .. >} syntax.
4109 @node Orchestral music
4110 @section Orchestral music
4112 @cindex Writing parts
4114 Orchestral music involves some special notation, both in the full
4115 score and the individual parts. This section explains how to tackle
4116 some common problems in orchestral music.
4121 * Multiple staff contexts::
4124 * Instrument names::
4126 * Instrument transpositions::
4127 * Multi measure rests::
4128 * Automatic part combining::
4130 * Different editions from one source::
4131 * Quoting other voices::
4134 @node Multiple staff contexts
4135 @subsection Multiple staff contexts
4137 Polyphonic scores consist of many staves. These staves can be
4138 constructed in three different ways
4140 @item The group is started with a brace at the left, and bar lines are
4141 connected. This is done with the @internalsref{GrandStaff} context.
4143 @item The group is started with a bracket, and bar lines are connected. This is done with the
4144 @internalsref{StaffGroup} context
4147 @item The group is started with a vertical line. Bar lines are not
4148 connected. This is the default for the score.
4152 @cindex Staff, multiple
4153 @cindex bracket, vertical
4154 @cindex brace, vertical
4161 @node Rehearsal marks
4162 @subsection Rehearsal marks
4163 @cindex Rehearsal marks
4165 @cindex @code{\mark}
4167 To print a rehearsal mark, use the @code{\mark} command
4168 @lilypond[quote,fragment,verbatim]
4179 (The letter I is skipped in accordance with engraving traditions.)
4181 The mark is incremented automatically if you use @code{\mark
4182 \default}, but you can also use an integer argument to set the mark
4183 manually. The value to use is stored in the property
4184 @code{rehearsalMark}.
4186 The style is defined by the property @code{markFormatter}. It is a
4187 function taking the current mark (an integer) and the current context
4188 as argument. It should return a markup object. In the following
4189 example, @code{markFormatter} is set to a canned procedure. After a
4190 few measures, it is set to function that produces a boxed number.
4192 @lilypond[quote,verbatim,fragment,relative=2]
4193 \set Score.markFormatter = #format-mark-numbers
4196 \set Score.markFormatter
4197 = #(lambda (mark context)
4198 (make-bold-markup (make-box-markup (number->string mark))))
4203 The file @file{scm/translation-functions.scm} contains the definitions
4204 of @code{format-mark-numbers} (the default format) and
4205 @code{format-mark-letters}. They can be used as inspiration for other
4206 formatting functions.
4209 @cindex coda on bar line
4210 @cindex segno on bar line
4211 @cindex fermata on bar line
4212 @cindex bar lines, symbols on
4214 The @code{\mark} command can also be used to put signs like coda,
4215 segno and fermatas on a bar line. Use @code{\markup} to
4216 to access the appropriate symbol
4218 @lilypond[quote,fragment,verbatim,relative=2]
4219 c1 \mark \markup { \musicglyph #"scripts-ufermata" }
4223 In the case of a line break, marks must also be printed at the end of
4224 the line, and not at the beginning. Use the following to force that
4227 \override Score.RehearsalMark
4228 #'break-visibility = #begin-of-line-invisible
4234 @cindex bar lines, putting symbols on
4238 Program reference: @internalsref{MarkEvent}, @internalsref{RehearsalMark}.
4240 Init files: @file{scm/translation-functions.scm} contains the
4241 definition of @code{format-mark-numbers} and
4242 @code{format-mark-letters}. They can be used as inspiration for other
4243 formatting functions.
4245 Examples: @inputfileref{input/regression,rehearsal-mark-letter.ly},
4246 @inputfileref{input/regression,rehearsal-mark-number.ly}.
4250 @subsection Bar numbers
4254 @cindex measure numbers
4255 @cindex currentBarNumber
4257 Bar numbers are printed by default at the start of the line. The
4258 number itself is stored in the
4259 @code{currentBarNumber} property,
4260 which is normally updated automatically for every measure.
4262 Bar numbers can be typeset at regular intervals instead of at the
4263 beginning of each line. This is illustrated in the following example,
4264 whose source is available as
4265 @inputfileref{input/test,bar-number-regular-interval.ly}
4267 @lilypondfile[quote]{bar-number-regular-interval.ly}
4271 Program reference: @internalsref{BarNumber}.
4273 Examples: @inputfileref{input/test,bar-number-every-five-reset.ly},
4274 and @inputfileref{input/test,bar-number-regular-interval.ly}.
4278 Bar numbers can collide with the @internalsref{StaffGroup} bracket, if
4279 there is one at the top. To solve this, the
4280 @code{padding} property of @internalsref{BarNumber} can be
4281 used to position the number correctly.
4283 @node Instrument names
4284 @subsection Instrument names
4286 In an orchestral score, instrument names are printed left side of the
4289 This can be achieved by setting @internalsref{Staff}.@code{instrument}
4290 and @internalsref{Staff}.@code{instr}. This will print a string before
4291 the start of the staff. For the first start, @code{instrument} is
4292 used, for the next ones @code{instr} is used.
4294 @lilypond[quote,verbatim,raggedright,relative=1]
4295 \set Staff.instrument = "Ploink "
4296 \set Staff.instr = "Plk "
4302 You can also use markup texts to construct more complicated instrument
4305 @lilypond[quote,fragment,verbatim,raggedright]
4307 \set Staff.instrument = \markup {
4308 \column < "Clarinetti" { "in B"
4309 \smaller \flat } > }
4316 Program reference: @internalsref{InstrumentName}.
4320 When you put a name on a grand staff or piano staff the width of the
4321 brace is not taken into account. You must add extra spaces to the end of
4322 the name to avoid a collision.
4325 @subsection Transpose
4327 @cindex transposition of pitches
4328 @cindex @code{\transpose}
4330 A music expression can be transposed with @code{\transpose}. The
4333 \transpose @var{from} @var{to} @var{musicexpr}
4336 This means that @var{musicexpr} is transposed by the interval between
4337 the pitches @var{from} and @var{to}: any note with pitch @code{from}
4338 is changed to @code{to}.
4341 For example, consider a piece written in the key of D major. If
4342 this piece is a little too low for its performer, it can be
4343 transposed up to E major with
4345 \transpose d e @dots{}
4348 Consider a part written for violin (a C instrument). If
4349 this part is to be played on the A clarinet, the following
4350 transposition will produce the appropriate part
4353 \transpose a c @dots{}
4356 Since @var{from} and @var{to} are pitches, so @code{\transpose} must be
4357 inside a @code{\notes} section. @code{\transpose} distinguishes
4358 between enharmonic pitches: both @code{\transpose c cis} or
4359 @code{\transpose c des} will transpose up half a tone. The first
4360 version will print sharps and the second version will print flats
4362 @lilypond[quote,raggedright,verbatim]
4363 mus =\notes { \key d \major cis d fis g }
4364 \score { \notes \context Staff {
4367 \transpose c g' \mus
4368 \transpose c f' \mus
4375 Program reference: @internalsref{TransposedMusic}, and
4376 @internalsref{UntransposableMusic}.
4380 If you want to use both @code{\transpose} and @code{\relative},
4381 you must put @code{\transpose} outside of @code{\relative}, since
4382 @code{\relative} will have no effect music that appears inside a
4385 @node Instrument transpositions
4386 @subsection Instrument transpositions
4388 The key of a transposing instrument can also be specified. This
4389 applies to many wind instruments, for example, clarinets (B-flat, A and
4390 E-flat), horn (F) and trumpet (B-flat, C, D and E-flat).
4393 The transposition is entered after the keyword @code{\transposition}
4396 \transposition bes %% B-flat clarinet
4399 This command sets the property @code{instrumentTuning}. The value of
4400 this property is used for MIDI output and quotations. It does not
4401 affect how notes are printed in the current staff.
4403 @cindex transposition, MIDI
4404 @cindex transposition, instrument
4407 @node Multi measure rests
4408 @subsection Multi measure rests
4409 @cindex multi measure rests
4410 @cindex Rests, multi measure
4414 Multi measure rests are entered using `@code{R}'. It is specifically
4415 meant for full bar rests and for entering parts: the rest can expand
4416 to fill a score with rests, or it can be printed as a single
4417 multimeasure rest. This expansion is controlled by the property
4418 @code{Score.skipBars}. If this is set to true, empty measures will not
4419 be expanded, and the appropriate number is added automatically
4421 @lilypond[quote,fragment,verbatim]
4422 \time 4/4 r1 | R1 | R1*2
4423 \set Score.skipBars = ##t R1*17 R1*4
4426 The @code{1} in @code{R1} is similar to the duration notation used for
4427 notes. Hence, for time signatures other than 4/4, you must enter other
4428 durations. This can be done with augmentation dots or fractions
4430 @lilypond[quote,fragment,verbatim]
4431 \set Score.skipBars = ##t
4439 An @code{R} spanning a single measure is printed as either a whole rest
4440 or a breve, centered in the measure regardless of the time signature.
4442 @cindex text on multi-measure rest
4443 @cindex script on multi-measure rest
4444 @cindex fermata on multi-measure rest
4446 Texts can be added to multi-measure rests by using the
4447 @var{note}-@code{markup} syntax (see @ref{Text markup}). In this case, the number is
4448 replaced. If you need both texts and the number, you must add the
4449 number by hand. A variable (@code{\fermataMarkup}) is provided for
4453 @lilypond[quote,verbatim,fragment]
4455 R2._\markup { "Ad lib" }
4459 If you want to have a text on the left end of a multi-measure rest,
4460 attach the text to a zero-length skip note, i.e.
4468 @cindex whole rests for a full measure
4472 Program reference: @internalsref{MultiMeasureRestEvent},
4473 @internalsref{MultiMeasureTextEvent},
4474 @internalsref{MultiMeasureRestMusicGroup}, and
4475 @internalsref{MultiMeasureRest}.
4477 The layout object @internalsref{MultiMeasureRestNumber} is for the
4478 default number, and @internalsref{MultiMeasureRestText} for user
4483 It is not possible to use fingerings (e.g. @code{R1-4}) to put numbers
4484 over multi-measure rests.
4486 @cindex condensing rests
4488 There is no way to automatically condense multiple rests into a single
4489 multimeasure rest. Multi measure rests do not take part in rest
4492 Be careful when entering multimeasure rests followed by whole
4493 notes. The following will enter two notes lasting four measures each
4497 When @code{skipBars} is set, the result will look OK, but the bar
4498 numbering will be off.
4500 @node Automatic part combining
4501 @subsection Automatic part combining
4502 @cindex automatic part combining
4503 @cindex part combiner
4506 Automatic part combining is used to merge two parts of music onto a
4507 staff. It is aimed at typesetting orchestral scores. When the two
4508 parts are identical for a period of time, only one is shown. In
4509 places where the two parts differ, they are typeset as separate
4510 voices, and stem directions are set automatically. Also, solo and
4511 @emph{a due} parts are identified and can be marked.
4513 The syntax for part combining is
4516 \partcombine @var{musicexpr1} @var{musicexpr2}
4519 The music expressions will be interpreted as @internalsref{Voice}
4520 contexts. If using relative octaves, @code{\relative} should be
4521 specified for both music expressions, i.e.
4524 \partcombine \relative @dots{} @var{musicexpr1}
4525 \relative @dots{} @var{musicexpr2}
4529 A @code{\relative} section that is outside of @code{\partcombine} has
4530 no effect on the pitches of @var{musicexpr1} and @var{musicexpr2}.
4533 The following example demonstrates the basic functionality of the part
4534 combiner: putting parts on one staff, and setting stem directions and
4537 @lilypond[quote,verbatim,raggedright,fragment]
4538 \new Staff \partcombine
4539 \relative g' { g g a( b) c c r r }
4540 \relative g' { g g r4 r e e g g }
4543 The first @code{g} appears only once, although it was
4544 specified twice (once in each part). Stem, slur and tie directions are
4545 set automatically, depending whether there is a solo or unisono. The
4546 first part (with context called @code{one}) always gets up stems, and
4547 `solo', while the second (called @code{two}) always gets down stems and
4550 If you just want the merging parts, and not the textual markings, you
4551 may set the property @code{soloADue} to false
4553 @lilypond[quote,verbatim,raggedright,fragment,relative=2]
4555 \set Staff.soloADue = ##f
4557 \relative g' { g a( b) r }
4558 \relative g' { g r4 r f }
4564 Program reference: @internalsref{PartCombineMusic},
4565 @internalsref{SoloOneEvent}, and
4566 @internalsref{SoloTwoEvent}, and
4567 @internalsref{UnisonoEvent}.
4571 In @code{soloADue} mode, when the two voices play the same notes on and
4572 off, the part combiner may typeset @code{a2} more than once in a
4575 @code{\partcombine} cannot be inside @code{\times}.
4577 @code{\partcombine} cannot be inside @code{\relative}.
4579 Internally, the @code{\partcombine} interprets both arguments as
4580 @code{Voice}s named @code{one} and @code{two}, and then decides when
4581 the parts can be combined. Consequently, if the arguments switch to
4582 differently named @internalsref{Voice} contexts, the events in those
4586 @subsection Hiding staves
4588 @cindex Frenched scores
4589 @cindex Hiding staves
4591 In orchestral scores, staff lines that only have rests are usually
4592 removed. This saves some space. This style is called `French Score'.
4593 For @internalsref{Lyrics},
4594 @internalsref{ChordNames} and @internalsref{FiguredBass}, this is
4595 switched on by default. When these line of these contexts turn out
4596 empty after the line-breaking process, they are removed.
4598 For normal staves, a specialized @internalsref{Staff} context is
4599 available, which does the same: staves containing nothing (or only
4600 multi measure rests) are removed. The context definition is stored in
4601 @code{\RemoveEmptyStaffContext} variable. Observe how the second staff
4602 in this example disappears in the second line
4605 @lilypond[quote,verbatim]
4607 \notes \relative c' <<
4608 \new Staff { e4 f g a \break c1 }
4609 \new Staff { c4 d e f \break R1 }
4613 \context { \RemoveEmptyStaffContext }
4618 The first page shows all staves in full. If empty staves should be
4619 removed from the first page too, set @code{remove-first} to false in
4620 @internalsref{RemoveEmptyVerticalGroup}.
4622 Another application is making ossia sections, i.e. alternative
4623 melodies on a separate piece of staff, with help of a Frenched
4624 staff. See @inputfileref{input/test,ossia.ly} for an example.
4627 @node Different editions from one source
4628 @subsection Different editions from one source
4630 The @code{\tag} command marks music expressions with a name. These
4631 tagged expressions can be filtered out later. With this mechanism it
4632 is possible to make different versions of the same music source.
4634 In the following example, we see two versions of a piece of music, one
4635 for the full score, and one with cue notes for the instrumental part
4651 The same can be applied to articulations, texts, etc.: they are
4654 -\tag #@var{your-tag}
4656 to an articulation, for example,
4661 This defines a note with a conditional fingering indication.
4663 By applying the @code{remove-tag} function, tagged expressions can be
4664 filtered. For example,
4668 \applymusic #(remove-tag 'score) @var{the music}
4669 \applymusic #(remove-tag 'part) @var{the music}
4674 @lilypondfile[quote]{tag-filter.ly}
4676 The argument of the @code{\tag} command should be a symbol, or a list
4677 of symbols, for example,
4679 \tag #'(original-part transposed-part) @dots{}
4684 Examples: @inputfileref{input/regression,tag-filter.ly}.
4687 @node Quoting other voices
4688 @subsection Quoting other voices
4690 With quotations, fragments of other parts can be inserted into a part
4691 directly. Before a part can be quoted, it must be marked especially as
4692 quotable. This is done with code @code{\addquote} command. The
4693 quotation may then be done with @code{\quote}
4696 \addquote @var{name} @var{music}
4697 \quote @var{name} @var{duration}
4702 Here, @var{name} is an identifying string. The @var{music} is any kind
4703 of music. This is an example of @code{\addquote}
4706 \addquote clarinet \notes\relative c' {
4711 During a part, a piece of music can be quoted with the @code{\quote}
4718 This would cite 3 quarter notes (a dotted half note) of the previously
4719 added clarinet voice.
4721 Quotations take into account the transposition both source and target
4722 instruments, if they are specified using the @code{\transposition} command.
4724 @lilypond[quote,raggedright,verbatim]
4725 \addquote clarinet \notes\relative c' {
4731 e'8 f'8 \quote clarinet 2
4737 Only the contents of the first @internalsref{Voice} occurring in an
4738 @code{\addquote} command will be considered for quotation, so
4739 @var{music} can not contain @code{\new} and @code{\context Voice}
4740 statements that would switch to a different Voice.
4745 In this manual: @ref{Instrument transpositions}.
4747 Examples: @inputfileref{input/regression,quote.ly}
4748 @inputfileref{input/regression,quote-transposition.ly}
4750 Program reference: @internalsref{QuoteMusic}.
4752 @node Ancient notation
4753 @section Ancient notation
4755 @cindex Vaticana, Editio
4756 @cindex Medicaea, Editio
4761 Support for ancient notation includes features for mensural notation
4762 and Gregorian Chant notation. There is also limited support for
4763 figured bass notation.
4765 Many graphical objects provide a @code{style} property, see
4766 @ref{Ancient note heads}, @ref{Ancient accidentals}, @ref{Ancient
4767 rests}, @ref{Ancient clefs}, @ref{Ancient flags} and @ref{Ancient time
4768 signatures}. By manipulating such a grob property, the typographical
4769 appearance of the affected graphical objects can be accommodated for a
4770 specific notation flavor without need for introducing any new
4773 Other aspects of ancient notation can not that easily be expressed as
4774 in terms of just changing a style property of a graphical object.
4775 Therefore, some notational concepts are introduced specifically for
4776 ancient notation, see @ref{Custodes}, @ref{Divisiones},
4777 @ref{Ligatures}, and @ref{Figured bass}.
4781 * Ancient note heads::
4782 * Ancient accidentals::
4786 * Ancient time signatures::
4791 * Vaticana style contexts::
4794 If this all is way too much of documentation for you, and you just
4795 want to dive into typesetting without worrying too much about the
4796 details on how to customize a context, you may have a look at the
4797 predefined contexts (see @ref{Vaticana style contexts}). Use them to
4798 set up predefined style-specific voice and staff contexts, and
4799 directly go ahead with the note entry.
4803 Ligatures need special spacing that has not yet been implemented. As
4804 a result, there is too much space between ligatures most of the time,
4805 and line breaking often is unsatisfactory. Also, lyrics do not
4806 correctly align with ligatures.
4808 Accidentals must not be printed within a ligature, but instead need to
4809 be collected and printed in front of it.
4811 Augmentum dots within ligatures are not handled correctly.
4814 @node Ancient note heads
4815 @subsection Ancient note heads
4820 For ancient notation, a note head style other than the @code{default}
4821 style may be chosen. This is accomplished by setting the @code{style}
4822 property of the NoteHead object to the desired value (@code{baroque},
4823 @code{neo_mensural} or @code{mensural}). The @code{baroque} style
4824 differs from the @code{default} style only in using a square shape for
4825 @code{\breve} note heads. The @code{neo_mensural} style differs from
4826 the @code{baroque} style in that it uses rhomboidal heads for whole
4827 notes and all smaller durations. Stems are centered on the note
4828 heads. This style is in particular useful when transcribing mensural
4829 music, e.g. for the incipit. The @code{mensural} style finally
4830 produces note heads that mimic the look of note heads in historic
4831 printings of the 16th century.
4833 The following example demonstrates the @code{neo_mensural} style
4835 @lilypond[quote,fragment,raggedright,verbatim]
4836 \override NoteHead #'style = #'neo_mensural
4837 a'\longa a'\breve a'1 a'2 a'4 a'8 a'16
4840 When typesetting a piece in Gregorian Chant notation, a Gregorian
4841 ligature engraver will automatically select the proper note heads,
4842 such there is no need to explicitly set the note head style. Still,
4843 the note head style can be set e.g. to @code{vaticana_punctum} to
4844 produce punctum neumes. Similarly, a mensural ligature engraver is
4845 used to automatically assemble mensural ligatures. See
4846 @ref{Ligatures} for how ligature engravers work.
4851 @ref{Percussion staves} use note head styles of their own that are
4852 frequently used in contemporary music notation.
4854 Examples: @inputfileref{input/regression,note-head-style.ly} gives an
4855 overview over all available note head styles.
4858 @node Ancient accidentals
4859 @subsection Ancient accidentals
4864 Use the @code{style} property of grob @internalsref{Accidental} to
4865 select ancient accidentals. Supported styles are
4866 @code{mensural}, @code{vaticana}, @code{hufnagel} and @code{medicaea}.
4868 @lilypond[quote,raggedright,staffsize=26]
4876 { " " \musicglyph #"accidentals-vaticana-1"
4877 " " \musicglyph #"accidentals-vaticana0" }
4881 { " " \musicglyph #"accidentals-medicaea-1" }
4885 { " " \musicglyph #"accidentals-hufnagel-1" }
4889 { " " \musicglyph #"accidentals-mensural-1"
4890 " " \musicglyph #"accidentals-mensural1" }
4899 \remove "Bar_number_engraver"
4903 \remove "Clef_engraver"
4904 \remove "Key_engraver"
4905 \remove "Time_signature_engraver"
4906 \remove "Staff_symbol_engraver"
4907 minimumVerticalExtent = ##f
4913 As shown, not all accidentals are supported by each style. When
4914 trying to access an unsupported accidental, LilyPond will switch to a
4915 different style, as demonstrated in
4916 @inputfileref{input/test,ancient-accidentals.ly}.
4918 Similarly to local accidentals, the style of the key signature can be
4919 controlled by the @code{style} property of the
4920 @internalsref{KeySignature} grob.
4924 In this manual: @ref{Pitches}, @ref{Chromatic alterations} and
4925 @ref{Accidentals} give a general introduction into the use of
4926 accidentals. @ref{Key signature} gives a general introduction into
4927 the use of key signatures.
4929 Program reference: @internalsref{KeySignature}.
4931 Examples: @inputfileref{input/test,ancient-accidentals.ly}.
4934 @subsection Ancient rests
4939 Use the @code{style} property of grob @internalsref{Rest} to select
4940 ancient accidentals. Supported styles are @code{classical},
4941 @code{neo_mensural} and @code{mensural}. @code{classical} differs
4942 from the @code{default} style only in that the quarter rest looks like
4943 a horizontally mirrored 8th rest. The @code{neo_mensural} style suits
4944 well for e.g. the incipit of a transcribed mensural piece of music.
4945 The @code{mensural} style finally mimics the appearance of rests as
4946 in historic prints of the 16th century.
4948 The following example demonstrates the @code{neo_mensural} style
4950 @lilypond[quote,fragment,raggedright,verbatim]
4951 \override Rest #'style = #'neo_mensural
4952 r\longa r\breve r1 r2 r4 r8 r16
4955 There are no 32th and 64th rests specifically for the mensural or
4956 neo-mensural style. Instead, the rests from the default style will be
4957 taken. See @inputfileref{input/test,rests.ly} for a chart of all
4960 There are no rests in Gregorian Chant notation; instead, it uses
4965 In this manual: @ref{Rests} gives a general introduction into the use of rests.
4969 @subsection Ancient clefs
4974 LilyPond supports a variety of clefs, many of them ancient.
4976 The following table shows all ancient clefs that are supported via the
4977 @code{\clef} command. Some of the clefs use the same glyph, but
4978 differ only with respect to the line they are printed on. In such
4979 cases, a trailing number in the name is used to enumerate these clefs.
4980 Still, you can manually force a clef glyph to be typeset on an
4981 arbitrary line, as described in @ref{Clef}. The note printed to the
4982 right side of each clef in the example column denotes the @code{c'}
4983 with respect to that clef.
4985 @multitable @columnfractions .3 .3 .3 .1
4989 @b{Description} @tab
4990 @b{Supported Clefs} @tab
4994 @code{clefs-neo_mensural_c} @tab
4995 modern style mensural C clef @tab
4996 @code{neo_mensural_c1}, @code{neo_mensural_c2},
4997 @code{neo_mensural_c3}, @code{neo_mensural_c4} @tab
4998 @lilypond[quote,relative=1,notime]
4999 \override Staff.TimeSignature #'transparent = ##t
5000 \clef "neo_mensural_c2" c
5004 @code{clefs-petrucci_c1}
5005 @code{clefs-petrucci_c2}
5006 @code{clefs-petrucci_c3}
5007 @code{clefs-petrucci_c4}
5008 @code{clefs-petrucci_c5}
5011 petrucci style mensural C clefs, for use on different staff lines
5012 (the examples shows the 2nd staff line C clef).
5022 @lilypond[quote,relative=1,notime]
5023 \override Staff.TimeSignature #'transparent = ##t
5024 \clef "petrucci_c2" c
5028 @code{clefs-petrucci_f} @tab
5029 petrucci style mensural F clef @tab
5030 @code{petrucci_f} @tab
5031 @lilypond[quote,relative=1,notime]
5032 \override Staff.TimeSignature #'transparent = ##t
5033 \clef "petrucci_f" c
5037 @code{clefs-petrucci_g} @tab
5038 petrucci style mensural G clef @tab
5039 @code{petrucci_g} @tab
5040 @lilypond[quote,relative=1,notime]
5041 \override Staff.TimeSignature #'transparent = ##t
5042 \clef "petrucci_g" c
5046 @code{clefs-mensural_c} @tab
5047 historic style mensural C clef @tab
5048 @code{mensural_c1}, @code{mensural_c2}, @code{mensural_c3},
5049 @code{mensural_c4} @tab
5050 @lilypond[quote,relative=1,notime]
5051 \override Staff.TimeSignature #'transparent = ##t
5052 \clef "mensural_c2" c
5056 @code{clefs-mensural_f} @tab
5057 historic style mensural F clef @tab
5058 @code{mensural_f} @tab
5059 @lilypond[quote,relative=1,notime]
5060 \override Staff.TimeSignature #'transparent = ##t
5061 \clef "mensural_f" c
5065 @code{clefs-mensural_g} @tab
5066 historic style mensural G clef @tab
5067 @code{mensural_g} @tab
5068 @lilypond[quote,relative=1,notime]
5069 \override Staff.TimeSignature #'transparent = ##t
5070 \clef "mensural_g" c
5074 @code{clefs-vaticana_do} @tab
5075 Editio Vaticana style do clef @tab
5076 @code{vaticana_do1}, @code{vaticana_do2}, @code{vaticana_do3} @tab
5077 @lilypond[quote,relative=1,notime]
5078 \override Staff.StaffSymbol #'line-count = #4
5079 \override Staff.TimeSignature #'transparent = ##t
5080 \clef "vaticana_do2" c
5084 @code{clefs-vaticana_fa} @tab
5085 Editio Vaticana style fa clef @tab
5086 @code{vaticana_fa1}, @code{vaticana_fa2} @tab
5087 @lilypond[quote,relative=1,notime]
5088 \override Staff.StaffSymbol #'line-count = #4
5089 \override Staff.TimeSignature #'transparent = ##t
5090 \clef "vaticana_fa2" c
5094 @code{clefs-medicaea_do} @tab
5095 Editio Medicaea style do clef @tab
5096 @code{medicaea_do1}, @code{medicaea_do2}, @code{medicaea_do3} @tab
5097 @lilypond[quote,relative=1,notime]
5098 \override Staff.StaffSymbol #'line-count = #4
5099 \override Staff.TimeSignature #'transparent = ##t
5100 \clef "medicaea_do2" c
5104 @code{clefs-medicaea_fa} @tab
5105 Editio Medicaea style fa clef @tab
5106 @code{medicaea_fa1}, @code{medicaea_fa2} @tab
5107 @lilypond[quote,relative=1,notime]
5108 \override Staff.StaffSymbol #'line-count = #4
5109 \override Staff.TimeSignature #'transparent = ##t
5110 \clef "medicaea_fa2" c
5114 @code{clefs-hufnagel_do} @tab
5115 historic style hufnagel do clef @tab
5116 @code{hufnagel_do1}, @code{hufnagel_do2}, @code{hufnagel_do3} @tab
5117 @lilypond[quote,relative=1,notime]
5118 \override Staff.StaffSymbol #'line-count = #4
5119 \override Staff.TimeSignature #'transparent = ##t
5120 \clef "hufnagel_do2" c
5124 @code{clefs-hufnagel_fa} @tab
5125 historic style hufnagel fa clef @tab
5126 @code{hufnagel_fa1}, @code{hufnagel_fa2} @tab
5127 @lilypond[quote,relative=1,notime]
5128 \override Staff.StaffSymbol #'line-count = #4
5129 \override Staff.TimeSignature #'transparent = ##t
5130 \clef "hufnagel_fa2" c
5134 @code{clefs-hufnagel_do_fa} @tab
5135 historic style hufnagel combined do/fa clef @tab
5136 @code{hufnagel_do_fa} @tab
5137 @lilypond[quote,relative=1,notime]
5138 \override Staff.TimeSignature #'transparent = ##t
5139 \clef "hufnagel_do_fa" c
5146 @emph{Modern style} means ``as is typeset in contemporary editions of
5147 transcribed mensural music''.
5149 @emph{Petrucci style} means ``inspired by printings published by the
5150 famous engraver Petrucci (1466-1539)''.
5152 @emph{Historic style} means ``as was typeset or written in historic
5153 editions (other than those of Petrucci)''.
5155 @emph{Editio XXX style} means ``as is/was printed in Editio XXX''.
5157 Petrucci used C clefs with differently balanced left-side vertical
5158 beams, depending on which staff line it is printed.
5162 In this manual: see @ref{Clef}.
5166 The mensural g clef is mapped to the Petrucci g clef, until a new
5167 mensural g clef is implemented.
5172 @subsection Ancient flags
5177 Use the @code{flag-style} property of grob @internalsref{Stem} to
5178 select ancient flags. Besides the @code{default} flag style,
5179 only @code{mensural} style is supported
5181 @lilypond[quote,fragment,raggedright,verbatim]
5182 \override Stem #'flag-style = #'mensural
5183 \override Stem #'thickness = #1.0
5184 \override NoteHead #'style = #'mensural
5186 c'8 d'8 e'8 f'8 c'16 d'16 e'16 f'16 c'32 d'32 e'32 f'32 s8
5187 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
5190 Note that the innermost flare of each mensural flag always is
5191 vertically aligned with a staff line. If you do not like this
5192 behavior, you can set the @code{adjust-if-on-staffline} property of
5193 grob @internalsref{Stem} to @code{##f}. Then, the vertical position
5194 of the end of each flare is different between notes on staff lines and
5195 notes between staff lines
5197 @lilypond[quote,fragment,raggedright]
5198 \override Stem #'flag-style = #'mensural
5199 \override Stem #'thickness = #1.0
5200 \override Stem #'adjust-if-on-staffline = ##f
5201 \override NoteHead #'style = #'mensural
5203 c'8 d'8 e'8 f'8 c'16 d'16 e'16 f'16 c'32 d'32 e'32 f'32 s8
5204 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
5207 There is no particular flag style for neo-mensural notation. Hence,
5208 when typesetting e.g. the incipit of a transcribed piece of mensural
5209 music, the default flag style should be used. There are no flags in
5210 Gregorian Chant notation.
5213 @node Ancient time signatures
5214 @subsection Ancient time signatures
5216 @cindex time signatures
5219 There is limited support for mensural time signatures. The
5220 glyphs are hard-wired to particular time fractions. In other words,
5221 to get a particular mensural signature glyph with the @code{\time n/m}
5222 command, @code{n} and @code{m} have to be chosen according to the
5228 \set Score.timing = ##f
5229 \set Score.barAlways = ##t
5230 s_\markup { "$\\backslash$time 4/4" }
5231 ^\markup { " " \musicglyph #"timesig-neo_mensural4/4" }
5233 s_\markup { "$\\backslash$time 2/2" }
5234 ^\markup { " " \musicglyph #"timesig-neo_mensural2/2" }
5236 s_\markup { "$\\backslash$time 6/4" }
5237 ^\markup { " " \musicglyph #"timesig-neo_mensural6/4" }
5239 s_\markup { "$\\backslash$time 6/8" }
5240 ^\markup { " " \musicglyph #"timesig-neo_mensural6/8" }
5242 s_\markup { "$\\backslash$time 3/2" }
5243 ^\markup { " " \musicglyph #"timesig-neo_mensural3/2" }
5245 s_\markup { "$\\backslash$time 3/4" }
5246 ^\markup { " " \musicglyph #"timesig-neo_mensural3/4" }
5248 s_\markup { "$\\backslash$time 9/4" }
5249 ^\markup { " " \musicglyph #"timesig-neo_mensural9/4" }
5251 s_\markup { "$\\backslash$time 9/8" }
5252 ^\markup { " " \musicglyph #"timesig-neo_mensural9/8" }
5254 s_\markup { "$\\backslash$time 4/8" }
5255 ^\markup { " " \musicglyph #"timesig-neo_mensural4/8" }
5257 s_\markup { "$\\backslash$time 2/4" }
5258 ^\markup { " " \musicglyph #"timesig-neo_mensural2/4" }
5266 \remove Staff_symbol_engraver
5267 \remove Clef_engraver
5268 \remove Time_signature_engraver
5274 Use the @code{style} property of grob @internalsref{TimeSignature} to
5275 select ancient time signatures. Supported styles are
5276 @code{neo_mensural} and @code{mensural}. The above table uses the
5277 @code{neo_mensural} style. This style is appropriate e.g. for the
5278 incipit of transcriptions of mensural pieces. The @code{mensural}
5279 style mimics the look of historical printings of the 16th century.
5281 @inputfileref{input/test,time.ly} gives an overview over all available
5282 ancient and modern styles.
5286 Program reference: @ref{Time signature} gives a general introduction into the use of time
5291 Mensural signature glyphs are mapped to time fractions in a hard-wired
5292 way. This mapping is sensible, but still arbitrary: given a mensural
5293 time signature, the time fraction represents a modern meter that
5294 usually will be a good choice when transcribing a mensural piece of
5295 music. For a particular piece of mensural music, however, the mapping
5296 may be unsatisfactory. In particular, the mapping assumes a fixed
5297 transcription of durations (e.g. brevis = half note in 2/2, i.e. 4:1).
5298 Some glyphs (such as the alternate glyph for 6/8 meter) are not at all
5299 accessible through the @code{\time} command.
5301 Mensural time signatures are supported typographically, but not yet
5302 musically. The internal representation of durations is
5303 based on a purely binary system; a ternary division such as 1 brevis =
5304 3 semibrevis (tempus perfectum) or 1 semibrevis = 3 minima (cum
5305 prolatione maiori) is not correctly handled: event times in ternary
5306 modes will be badly computed, resulting e.g. in horizontally
5307 misaligned note heads, and bar checks are likely to erroneously fail.
5309 The syntax and semantics of the @code{\time} command for mensural
5310 music is subject to change.
5313 @subsection Custodes
5318 A @emph{custos} (plural: @emph{custodes}; Latin word for `guard') is a
5319 symbol that appears at the end of a staff. It anticipates the pitch
5320 of the first note(s) of the following line and thus helps the player
5321 or singer to manage line breaks during performance, thus enhancing
5322 readability of a score.
5324 Custodes were frequently used in music notation until the 17th
5325 century. Nowadays, they have survived only in a few particular forms
5326 of musical notation such as contemporary editions of Gregorian chant
5327 like the @emph{editio vaticana}. There are different custos glyphs
5328 used in different flavors of notational style.
5330 For typesetting custodes, just put a @internalsref{Custos_engraver} into the
5331 @internalsref{Staff} context when declaring the @code{\paper} block,
5332 as shown in the following example
5338 \consists Custos_engraver
5339 Custos \override #'style = #'mensural
5344 The result looks like this
5346 @lilypond[quote,raggedright]
5350 \override Staff.Custos #'style = #'mensural
5357 \consists Custos_engraver
5363 The custos glyph is selected by the @code{style} property. The styles
5364 supported are @code{vaticana}, @code{medicaea}, @code{hufnagel} and
5365 @code{mensural}. They are demonstrated in the following fragment
5369 \new Lyrics \lyrics {
5373 { " " \musicglyph #"custodes-vaticana-u0" }
5377 { " " \musicglyph #"custodes-medicaea-u0" }
5382 { " " \musicglyph #"custodes-hufnagel-u0" }
5387 { " " \musicglyph #"custodes-mensural-u0" }
5399 Program reference: @internalsref{Custos}.
5401 Examples: @inputfileref{input/regression,custos.ly}.
5405 @subsection Divisiones
5411 A @emph{divisio} (plural: @emph{divisiones}; Latin word for
5412 `division') is a staff context symbol that is used to structure
5413 Gregorian music into phrases and sections. The musical meaning of
5414 @emph{divisio minima}, @emph{divisio maior} and @emph{divisio maxima}
5415 can be characterized as short, medium and long pause, somewhat like
5416 @ref{Breath marks}. The @emph{finalis} sign not only marks the end of
5417 a chant, but is also frequently used within a single
5418 antiphonal/responsorial chant to mark the end of each section.
5421 To use divisiones, include the file @code{gregorian-init.ly}. It
5422 contains definitions that you can apply by just inserting
5423 @code{\divisioMinima}, @code{\divisioMaior}, @code{\divisioMaxima},
5424 and @code{\finalis} at proper places in the input. Some editions use
5425 @emph{virgula} or @emph{caesura} instead of divisio minima.
5426 Therefore, @code{gregorian-init.ly} also defines @code{\virgula} and
5429 @lilypondfile[quote,raggedright]{divisiones.ly}
5433 @cindex @code{\virgula}
5435 @cindex @code{\caesura}
5437 @cindex @code{\divisioMinima}
5438 @code{\divisioMinima},
5439 @cindex @code{\divisioMaior}
5440 @code{\divisioMaior},
5441 @cindex @code{\divisioMaxima}
5442 @code{\divisioMaxima},
5443 @cindex @code{\finalis}
5448 In this manual: @ref{Breath marks}.
5450 Program reference: @internalsref{BreathingSign}, @internalsref{BreathingSignEvent}.
5452 Examples: @inputfileref{input/test,divisiones.ly}.
5455 @subsection Ligatures
5459 @c TODO: Should double check if I recalled things correctly when I wrote
5460 @c down the following paragraph by heart.
5462 A ligature is a coherent graphical symbol that represents at least two
5463 distinct notes. Ligatures originally appeared in the manuscripts of
5464 Gregorian chant notation roughly since the 9th century to denote
5465 ascending or descending sequences of notes.
5467 Ligatures are entered by enclosing them in @code{\[} and @code{\]}.
5468 Some ligature styles may need additional input syntax specific for
5469 this particular type of ligature. By default, the
5470 @internalsref{LigatureBracket} engraver just puts a square bracket
5473 @lilypond[quote,raggedright,verbatim]
5475 \notes \transpose c c' {
5483 To select a specific style of ligatures, a proper ligature engraver
5484 has to be added to the @internalsref{Voice} context, as explained in
5485 the following subsections. Only white mensural ligatures
5486 are supported with certain limitations.
5489 * White mensural ligatures::
5490 * Gregorian square neumes ligatures::
5493 @node White mensural ligatures
5494 @subsubsection White mensural ligatures
5496 @cindex Mensural ligatures
5497 @cindex White mensural ligatures
5499 There is limited support for white mensural ligatures.
5501 To engrave white mensural ligatures, in the paper block the
5502 @internalsref{Mensural_ligature_engraver} has to be put into the
5503 @internalsref{Voice} context, and remove the
5504 @internalsref{Ligature_bracket_engraver}
5510 \remove Ligature_bracket_engraver
5511 \consists Mensural_ligature_engraver
5516 There is no additional input language to describe the shape of a
5517 white mensural ligature. The shape is rather determined solely from
5518 the pitch and duration of the enclosed notes. While this approach may
5519 take a new user a while to get accustomed, it has the great advantage
5520 that the full musical information of the ligature is known internally.
5521 This is not only required for correct MIDI output, but also allows for
5522 automatic transcription of the ligatures.
5527 \set Score.timing = ##f
5528 \set Score.defaultBarType = "empty"
5529 \override NoteHead #'style = #'neo_mensural
5530 \override Staff.TimeSignature #'style = #'neo_mensural
5532 \[ g\longa c\breve a\breve f\breve d'\longa \]
5534 \[ e1 f1 a\breve g\longa \]
5536 @lilypond[quote,raggedright]
5538 \notes \transpose c c' {
5539 \set Score.timing = ##f
5540 \set Score.defaultBarType = "empty"
5541 \override NoteHead #'style = #'neo_mensural
5542 \override Staff.TimeSignature #'style = #'neo_mensural
5544 \[ g\longa c\breve a\breve f\breve d'\longa \]
5546 \[ e1 f1 a\breve g\longa \]
5551 \remove Ligature_bracket_engraver
5552 \consists Mensural_ligature_engraver
5558 Without replacing @internalsref{Ligature_bracket_engraver} with
5559 @internalsref{Mensural_ligature_engraver}, the same music transcribes
5562 @lilypond[quote,raggedright]
5564 \notes \transpose c c' {
5565 \set Score.timing = ##f
5566 \set Score.defaultBarType = "empty"
5567 \override NoteHead #'style = #'neo_mensural
5568 \override Staff.TimeSignature #'style = #'neo_mensural
5570 \[ g\longa c\breve a\breve f\breve d'\longa \]
5572 \[ e1 f1 a\breve g\longa \]
5579 The implementation is experimental; it may output strange warnings or
5580 even crash in some cases or produce weird results on more complex
5583 @node Gregorian square neumes ligatures
5584 @subsubsection Gregorian square neumes ligatures
5586 @cindex Square neumes ligatures
5587 @cindex Gregorian square neumes ligatures
5589 Gregorian square neumes notation (following the style of the Editio
5590 Vaticana) is under heavy development, but not yet really usable for
5591 production purposes. Core ligatures can already be typeset, but
5592 essential issues for serious typesetting are still under development,
5593 such as (among others) horizontal alignment of multiple ligatures,
5594 lyrics alignment and proper accidentals handling. Still, this section
5595 gives a sneak preview of what Gregorian chant may look like once it
5598 The following table contains the extended neumes table of the 2nd
5599 volume of the Antiphonale Romanum (@emph{Liber Hymnarius}), published
5600 1983 by the monks of Solesmes.
5602 @multitable @columnfractions .4 .2 .2 .2
5605 @b{Neuma aut@*Neumarum Elementa} @tab
5606 @b{Figurae@*Rectae} @tab
5607 @b{Figurae@*Liquescentes Auctae} @tab
5608 @b{Figurae@*Liquescentes Deminutae}
5610 @c TODO: \paper block is identical in all of the below examples.
5611 @c Therefore, it should somehow be included rather than duplicated all
5614 @c why not make identifiers in ly/engraver-init.ly? --hwn
5616 @c Because it's just used to typeset plain notes without
5617 @c a staff for demonstration purposes rather than something
5618 @c special of Gregorian chant notation. --jr
5623 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.5\cm]
5624 \include "gregorian-init.ly"
5626 \notes \transpose c c' {
5629 \noBreak s^\markup {"a"} \noBreak
5631 % Punctum Inclinatum
5633 \noBreak s^\markup {"b"}
5639 \remove "Bar_number_engraver"
5643 \remove "Clef_engraver"
5644 \remove "Key_engraver"
5645 \override StaffSymbol #'transparent = ##t
5646 \remove "Time_signature_engraver"
5647 \remove "Bar_engraver"
5648 minimumVerticalExtent = ##f
5652 \remove Ligature_bracket_engraver
5653 \consists Vaticana_ligature_engraver
5654 \override NoteHead #'style = #'vaticana_punctum
5655 \override Stem #'transparent = ##t
5661 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=2.5\cm]
5662 \include "gregorian-init.ly"
5664 \notes \transpose c c' {
5665 % Punctum Auctum Ascendens
5666 \[ \auctum \ascendens b \]
5667 \noBreak s^\markup {"c"} \noBreak
5669 % Punctum Auctum Descendens
5670 \[ \auctum \descendens b \]
5671 \noBreak s^\markup {"d"} \noBreak
5673 % Punctum Inclinatum Auctum
5674 \[ \inclinatum \auctum b \]
5675 \noBreak s^\markup {"e"}
5681 \remove "Bar_number_engraver"
5685 \remove "Clef_engraver"
5686 \remove "Key_engraver"
5687 \override StaffSymbol #'transparent = ##t
5688 \remove "Time_signature_engraver"
5689 \remove "Bar_engraver"
5690 minimumVerticalExtent = ##f
5694 \remove Ligature_bracket_engraver
5695 \consists Vaticana_ligature_engraver
5696 \override NoteHead #'style = #'vaticana_punctum
5697 \override Stem #'transparent = ##t
5703 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5704 \include "gregorian-init.ly"
5706 \notes \transpose c c' {
5707 % Punctum Inclinatum Parvum
5708 \[ \inclinatum \deminutum b \]
5709 \noBreak s^\markup {"f"}
5715 \remove "Bar_number_engraver"
5719 \remove "Clef_engraver"
5720 \remove "Key_engraver"
5721 \override StaffSymbol #'transparent = ##t
5722 \remove "Time_signature_engraver"
5723 \remove "Bar_engraver"
5724 minimumVerticalExtent = ##f
5728 \remove Ligature_bracket_engraver
5729 \consists Vaticana_ligature_engraver
5730 \override NoteHead #'style = #'vaticana_punctum
5731 \override Stem #'transparent = ##t
5740 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5741 \include "gregorian-init.ly"
5743 \notes \transpose c c' {
5746 \noBreak s^\markup {"g"}
5752 \remove "Bar_number_engraver"
5756 \remove "Clef_engraver"
5757 \remove "Key_engraver"
5758 \override StaffSymbol #'transparent = ##t
5759 \remove "Time_signature_engraver"
5760 \remove "Bar_engraver"
5761 minimumVerticalExtent = ##f
5765 \remove Ligature_bracket_engraver
5766 \consists Vaticana_ligature_engraver
5767 \override NoteHead #'style = #'vaticana_punctum
5768 \override Stem #'transparent = ##t
5777 @code{3. Apostropha vel Stropha}
5779 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5780 \include "gregorian-init.ly"
5782 \notes \transpose c c' {
5785 \noBreak s^\markup {"h"}
5791 \remove "Bar_number_engraver"
5795 \remove "Clef_engraver"
5796 \remove "Key_engraver"
5797 \override StaffSymbol #'transparent = ##t
5798 \remove "Time_signature_engraver"
5799 \remove "Bar_engraver"
5800 minimumVerticalExtent = ##f
5804 \remove Ligature_bracket_engraver
5805 \consists Vaticana_ligature_engraver
5806 \override NoteHead #'style = #'vaticana_punctum
5807 \override Stem #'transparent = ##t
5813 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5814 \include "gregorian-init.ly"
5816 \notes \transpose c c' {
5818 \[ \stropha \auctum b \]
5819 \noBreak s^\markup {"i"}
5825 \remove "Bar_number_engraver"
5829 \remove "Clef_engraver"
5830 \remove "Key_engraver"
5831 \override StaffSymbol #'transparent = ##t
5832 \remove "Time_signature_engraver"
5833 \remove "Bar_engraver"
5834 minimumVerticalExtent = ##f
5838 \remove Ligature_bracket_engraver
5839 \consists Vaticana_ligature_engraver
5840 \override NoteHead #'style = #'vaticana_punctum
5841 \override Stem #'transparent = ##t
5851 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5852 \include "gregorian-init.ly"
5854 \notes \transpose c c' {
5857 \noBreak s^\markup {"j"}
5863 \remove "Bar_number_engraver"
5867 \remove "Clef_engraver"
5868 \remove "Key_engraver"
5869 \override StaffSymbol #'transparent = ##t
5870 \remove "Time_signature_engraver"
5871 \remove "Bar_engraver"
5872 minimumVerticalExtent = ##f
5876 \remove Ligature_bracket_engraver
5877 \consists Vaticana_ligature_engraver
5878 \override NoteHead #'style = #'vaticana_punctum
5879 \override Stem #'transparent = ##t
5888 @code{5. Clivis vel Flexa}
5890 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5891 \include "gregorian-init.ly"
5893 \notes \transpose c c' {
5902 \remove "Bar_number_engraver"
5906 \remove "Clef_engraver"
5907 \remove "Key_engraver"
5908 \override StaffSymbol #'transparent = ##t
5909 \remove "Time_signature_engraver"
5910 \remove "Bar_engraver"
5911 minimumVerticalExtent = ##f
5915 \remove Ligature_bracket_engraver
5916 \consists Vaticana_ligature_engraver
5917 \override NoteHead #'style = #'vaticana_punctum
5918 \override Stem #'transparent = ##t
5924 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=2.0\cm]
5925 \include "gregorian-init.ly"
5927 \notes \transpose c c' {
5928 % Clivis Aucta Descendens
5929 \[ b \flexa \auctum \descendens g \]
5930 \noBreak s^\markup {"l"} \noBreak
5932 % Clivis Aucta Ascendens
5933 \[ b \flexa \auctum \ascendens g \]
5934 \noBreak s^\markup {"m"}
5940 \remove "Bar_number_engraver"
5944 \remove "Clef_engraver"
5945 \remove "Key_engraver"
5946 \override StaffSymbol #'transparent = ##t
5947 \remove "Time_signature_engraver"
5948 \remove "Bar_engraver"
5949 minimumVerticalExtent = ##f
5953 \remove Ligature_bracket_engraver
5954 \consists Vaticana_ligature_engraver
5955 \override NoteHead #'style = #'vaticana_punctum
5956 \override Stem #'transparent = ##t
5962 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5963 \include "gregorian-init.ly"
5965 \notes \transpose c c' {
5967 \[ b \flexa \deminutum g \]
5974 \remove "Bar_number_engraver"
5978 \remove "Clef_engraver"
5979 \remove "Key_engraver"
5980 \override StaffSymbol #'transparent = ##t
5981 \remove "Time_signature_engraver"
5982 \remove "Bar_engraver"
5983 minimumVerticalExtent = ##f
5987 \remove Ligature_bracket_engraver
5988 \consists Vaticana_ligature_engraver
5989 \override NoteHead #'style = #'vaticana_punctum
5990 \override Stem #'transparent = ##t
5997 @code{6. Podatus vel Pes}
5999 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6000 \include "gregorian-init.ly"
6002 \notes \transpose c c' {
6011 \remove "Bar_number_engraver"
6015 \remove "Clef_engraver"
6016 \remove "Key_engraver"
6017 \override StaffSymbol #'transparent = ##t
6018 \remove "Time_signature_engraver"
6019 \remove "Bar_engraver"
6020 minimumVerticalExtent = ##f
6024 \remove Ligature_bracket_engraver
6025 \consists Vaticana_ligature_engraver
6026 \override NoteHead #'style = #'vaticana_punctum
6027 \override Stem #'transparent = ##t
6033 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=2.0\cm]
6034 \include "gregorian-init.ly"
6036 \notes \transpose c c' {
6037 % Pes Auctus Descendens
6038 \[ g \pes \auctum \descendens b \]
6039 \noBreak s^\markup {"p"} \noBreak
6041 % Pes Auctus Ascendens
6042 \[ g \pes \auctum \ascendens b \]
6043 \noBreak s^\markup {"q"}
6049 \remove "Bar_number_engraver"
6053 \remove "Clef_engraver"
6054 \remove "Key_engraver"
6055 \override StaffSymbol #'transparent = ##t
6056 \remove "Time_signature_engraver"
6057 \remove "Bar_engraver"
6058 minimumVerticalExtent = ##f
6062 \remove Ligature_bracket_engraver
6063 \consists Vaticana_ligature_engraver
6064 \override NoteHead #'style = #'vaticana_punctum
6065 \override Stem #'transparent = ##t
6071 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6072 \include "gregorian-init.ly"
6074 \notes \transpose c c' {
6076 \[ g \pes \deminutum b \]
6083 \remove "Bar_number_engraver"
6087 \remove "Clef_engraver"
6088 \remove "Key_engraver"
6089 \override StaffSymbol #'transparent = ##t
6090 \remove "Time_signature_engraver"
6091 \remove "Bar_engraver"
6092 minimumVerticalExtent = ##f
6096 \remove Ligature_bracket_engraver
6097 \consists Vaticana_ligature_engraver
6098 \override NoteHead #'style = #'vaticana_punctum
6099 \override Stem #'transparent = ##t
6106 @code{7. Pes Quassus}
6108 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6109 \include "gregorian-init.ly"
6111 \notes \transpose c c' {
6113 \[ \oriscus g \pes \virga b \]
6120 \remove "Bar_number_engraver"
6124 \remove "Clef_engraver"
6125 \remove "Key_engraver"
6126 \override StaffSymbol #'transparent = ##t
6127 \remove "Time_signature_engraver"
6128 \remove "Bar_engraver"
6129 minimumVerticalExtent = ##f
6133 \remove Ligature_bracket_engraver
6134 \consists Vaticana_ligature_engraver
6135 \override NoteHead #'style = #'vaticana_punctum
6136 \override Stem #'transparent = ##t
6142 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6143 \include "gregorian-init.ly"
6145 \notes \transpose c c' {
6146 % Pes Quassus Auctus Descendens
6147 \[ \oriscus g \pes \auctum \descendens b \]
6154 \remove "Bar_number_engraver"
6158 \remove "Clef_engraver"
6159 \remove "Key_engraver"
6160 \override StaffSymbol #'transparent = ##t
6161 \remove "Time_signature_engraver"
6162 \remove "Bar_engraver"
6163 minimumVerticalExtent = ##f
6167 \remove Ligature_bracket_engraver
6168 \consists Vaticana_ligature_engraver
6169 \override NoteHead #'style = #'vaticana_punctum
6170 \override Stem #'transparent = ##t
6178 @code{8. Quilisma Pes}
6180 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6181 \include "gregorian-init.ly"
6183 \notes \transpose c c' {
6185 \[ \quilisma g \pes b \]
6192 \remove "Bar_number_engraver"
6196 \remove "Clef_engraver"
6197 \remove "Key_engraver"
6198 \override StaffSymbol #'transparent = ##t
6199 \remove "Time_signature_engraver"
6200 \remove "Bar_engraver"
6201 minimumVerticalExtent = ##f
6205 \remove Ligature_bracket_engraver
6206 \consists Vaticana_ligature_engraver
6207 \override NoteHead #'style = #'vaticana_punctum
6208 \override Stem #'transparent = ##t
6214 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6215 \include "gregorian-init.ly"
6217 \notes \transpose c c' {
6218 % Quilisma Pes Auctus Descendens
6219 \[ \quilisma g \pes \auctum \descendens b \]
6226 \remove "Bar_number_engraver"
6230 \remove "Clef_engraver"
6231 \remove "Key_engraver"
6232 \override StaffSymbol #'transparent = ##t
6233 \remove "Time_signature_engraver"
6234 \remove "Bar_engraver"
6235 minimumVerticalExtent = ##f
6239 \remove Ligature_bracket_engraver
6240 \consists Vaticana_ligature_engraver
6241 \override NoteHead #'style = #'vaticana_punctum
6242 \override Stem #'transparent = ##t
6250 @code{9. Podatus Initio Debilis}
6252 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6253 \include "gregorian-init.ly"
6255 \notes \transpose c c' {
6256 % Pes Initio Debilis
6257 \[ \deminutum g \pes b \]
6264 \remove "Bar_number_engraver"
6268 \remove "Clef_engraver"
6269 \remove "Key_engraver"
6270 \override StaffSymbol #'transparent = ##t
6271 \remove "Time_signature_engraver"
6272 \remove "Bar_engraver"
6273 minimumVerticalExtent = ##f
6277 \remove Ligature_bracket_engraver
6278 \consists Vaticana_ligature_engraver
6279 \override NoteHead #'style = #'vaticana_punctum
6280 \override Stem #'transparent = ##t
6286 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6287 \include "gregorian-init.ly"
6289 \notes \transpose c c' {
6290 % Pes Auctus Descendens Initio Debilis
6291 \[ \deminutum g \pes \auctum \descendens b \]
6298 \remove "Bar_number_engraver"
6302 \remove "Clef_engraver"
6303 \remove "Key_engraver"
6304 \override StaffSymbol #'transparent = ##t
6305 \remove "Time_signature_engraver"
6306 \remove "Bar_engraver"
6307 minimumVerticalExtent = ##f
6311 \remove Ligature_bracket_engraver
6312 \consists Vaticana_ligature_engraver
6313 \override NoteHead #'style = #'vaticana_punctum
6314 \override Stem #'transparent = ##t
6324 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6325 \include "gregorian-init.ly"
6327 \notes \transpose c c' {
6329 \[ a \pes b \flexa g \]
6336 \remove "Bar_number_engraver"
6340 \remove "Clef_engraver"
6341 \remove "Key_engraver"
6342 \override StaffSymbol #'transparent = ##t
6343 \remove "Time_signature_engraver"
6344 \remove "Bar_engraver"
6345 minimumVerticalExtent = ##f
6349 \remove Ligature_bracket_engraver
6350 \consists Vaticana_ligature_engraver
6351 \override NoteHead #'style = #'vaticana_punctum
6352 \override Stem #'transparent = ##t
6358 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6359 \include "gregorian-init.ly"
6361 \notes \transpose c c' {
6362 % Torculus Auctus Descendens
6363 \[ a \pes b \flexa \auctum \descendens g \]
6370 \remove "Bar_number_engraver"
6374 \remove "Clef_engraver"
6375 \remove "Key_engraver"
6376 \override StaffSymbol #'transparent = ##t
6377 \remove "Time_signature_engraver"
6378 \remove "Bar_engraver"
6379 minimumVerticalExtent = ##f
6383 \remove Ligature_bracket_engraver
6384 \consists Vaticana_ligature_engraver
6385 \override NoteHead #'style = #'vaticana_punctum
6386 \override Stem #'transparent = ##t
6392 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6393 \include "gregorian-init.ly"
6395 \notes \transpose c c' {
6396 % Torculus Deminutus
6397 \[ a \pes b \flexa \deminutum g \]
6404 \remove "Bar_number_engraver"
6408 \remove "Clef_engraver"
6409 \remove "Key_engraver"
6410 \override StaffSymbol #'transparent = ##t
6411 \remove "Time_signature_engraver"
6412 \remove "Bar_engraver"
6413 minimumVerticalExtent = ##f
6417 \remove Ligature_bracket_engraver
6418 \consists Vaticana_ligature_engraver
6419 \override NoteHead #'style = #'vaticana_punctum
6420 \override Stem #'transparent = ##t
6427 @code{11. Torculus Initio Debilis}
6429 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6430 \include "gregorian-init.ly"
6432 \notes \transpose c c' {
6433 % Torculus Initio Debilis
6434 \[ \deminutum a \pes b \flexa g \]
6441 \remove "Bar_number_engraver"
6445 \remove "Clef_engraver"
6446 \remove "Key_engraver"
6447 \override StaffSymbol #'transparent = ##t
6448 \remove "Time_signature_engraver"
6449 \remove "Bar_engraver"
6450 minimumVerticalExtent = ##f
6454 \remove Ligature_bracket_engraver
6455 \consists Vaticana_ligature_engraver
6456 \override NoteHead #'style = #'vaticana_punctum
6457 \override Stem #'transparent = ##t
6463 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6464 \include "gregorian-init.ly"
6466 \notes \transpose c c' {
6467 % Torculus Auctus Descendens Initio Debilis
6468 \[ \deminutum a \pes b \flexa \auctum \descendens g \]
6475 \remove "Bar_number_engraver"
6479 \remove "Clef_engraver"
6480 \remove "Key_engraver"
6481 \override StaffSymbol #'transparent = ##t
6482 \remove "Time_signature_engraver"
6483 \remove "Bar_engraver"
6484 minimumVerticalExtent = ##f
6488 \remove Ligature_bracket_engraver
6489 \consists Vaticana_ligature_engraver
6490 \override NoteHead #'style = #'vaticana_punctum
6491 \override Stem #'transparent = ##t
6497 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6498 \include "gregorian-init.ly"
6500 \notes \transpose c c' {
6501 % Torculus Deminutus Initio Debilis
6502 \[ \deminutum a \pes b \flexa \deminutum g \]
6509 \remove "Bar_number_engraver"
6513 \remove "Clef_engraver"
6514 \remove "Key_engraver"
6515 \override StaffSymbol #'transparent = ##t
6516 \remove "Time_signature_engraver"
6517 \remove "Bar_engraver"
6518 minimumVerticalExtent = ##f
6522 \remove Ligature_bracket_engraver
6523 \consists Vaticana_ligature_engraver
6524 \override NoteHead #'style = #'vaticana_punctum
6525 \override Stem #'transparent = ##t
6532 @code{12. Porrectus}
6534 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6535 \include "gregorian-init.ly"
6537 \notes \transpose c c' {
6539 \[ a \flexa g \pes b \]
6546 \remove "Bar_number_engraver"
6550 \remove "Clef_engraver"
6551 \remove "Key_engraver"
6552 \override StaffSymbol #'transparent = ##t
6553 \remove "Time_signature_engraver"
6554 \remove "Bar_engraver"
6555 minimumVerticalExtent = ##f
6559 \remove Ligature_bracket_engraver
6560 \consists Vaticana_ligature_engraver
6561 \override NoteHead #'style = #'vaticana_punctum
6562 \override Stem #'transparent = ##t
6568 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6569 \include "gregorian-init.ly"
6571 \notes \transpose c c' {
6572 % Porrectus Auctus Descendens
6573 \[ a \flexa g \pes \auctum \descendens b \]
6580 \remove "Bar_number_engraver"
6584 \remove "Clef_engraver"
6585 \remove "Key_engraver"
6586 \override StaffSymbol #'transparent = ##t
6587 \remove "Time_signature_engraver"
6588 \remove "Bar_engraver"
6589 minimumVerticalExtent = ##f
6593 \remove Ligature_bracket_engraver
6594 \consists Vaticana_ligature_engraver
6595 \override NoteHead #'style = #'vaticana_punctum
6596 \override Stem #'transparent = ##t
6602 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6603 \include "gregorian-init.ly"
6605 \notes \transpose c c' {
6606 % Porrectus Deminutus
6607 \[ a \flexa g \pes \deminutum b \]
6614 \remove "Bar_number_engraver"
6618 \remove "Clef_engraver"
6619 \remove "Key_engraver"
6620 \override StaffSymbol #'transparent = ##t
6621 \remove "Time_signature_engraver"
6622 \remove "Bar_engraver"
6623 minimumVerticalExtent = ##f
6627 \remove Ligature_bracket_engraver
6628 \consists Vaticana_ligature_engraver
6629 \override NoteHead #'style = #'vaticana_punctum
6630 \override Stem #'transparent = ##t
6639 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6640 \include "gregorian-init.ly"
6642 \notes \transpose c c' {
6644 \[ \virga b \inclinatum a \inclinatum g \]
6651 \remove "Bar_number_engraver"
6655 \remove "Clef_engraver"
6656 \remove "Key_engraver"
6657 \override StaffSymbol #'transparent = ##t
6658 \remove "Time_signature_engraver"
6659 \remove "Bar_engraver"
6660 minimumVerticalExtent = ##f
6664 \remove Ligature_bracket_engraver
6665 \consists Vaticana_ligature_engraver
6666 \override NoteHead #'style = #'vaticana_punctum
6667 \override Stem #'transparent = ##t
6673 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6674 \include "gregorian-init.ly"
6676 \notes \transpose c c' {
6678 \[ \virga b \inclinatum a \inclinatum \auctum g \]
6685 \remove "Bar_number_engraver"
6689 \remove "Clef_engraver"
6690 \remove "Key_engraver"
6691 \override StaffSymbol #'transparent = ##t
6692 \remove "Time_signature_engraver"
6693 \remove "Bar_engraver"
6694 minimumVerticalExtent = ##f
6698 \remove Ligature_bracket_engraver
6699 \consists Vaticana_ligature_engraver
6700 \override NoteHead #'style = #'vaticana_punctum
6701 \override Stem #'transparent = ##t
6707 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6708 \include "gregorian-init.ly"
6710 \notes \transpose c c' {
6711 % Climacus Deminutus
6712 \[ \virga b \inclinatum a \inclinatum \deminutum g \]
6719 \remove "Bar_number_engraver"
6723 \remove "Clef_engraver"
6724 \remove "Key_engraver"
6725 \override StaffSymbol #'transparent = ##t
6726 \remove "Time_signature_engraver"
6727 \remove "Bar_engraver"
6728 minimumVerticalExtent = ##f
6732 \remove Ligature_bracket_engraver
6733 \consists Vaticana_ligature_engraver
6734 \override NoteHead #'style = #'vaticana_punctum
6735 \override Stem #'transparent = ##t
6742 @code{14. Scandicus}
6744 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6745 \include "gregorian-init.ly"
6747 \notes \transpose c c' {
6749 \[ g \pes a \virga b \]
6756 \remove "Bar_number_engraver"
6760 \remove "Clef_engraver"
6761 \remove "Key_engraver"
6762 \override StaffSymbol #'transparent = ##t
6763 \remove "Time_signature_engraver"
6764 \remove "Bar_engraver"
6765 minimumVerticalExtent = ##f
6769 \remove Ligature_bracket_engraver
6770 \consists Vaticana_ligature_engraver
6771 \override NoteHead #'style = #'vaticana_punctum
6772 \override Stem #'transparent = ##t
6778 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6779 \include "gregorian-init.ly"
6781 \notes \transpose c c' {
6782 % Scandicus Auctus Descendens
6783 \[ g \pes a \pes \auctum \descendens b \]
6790 \remove "Bar_number_engraver"
6794 \remove "Clef_engraver"
6795 \remove "Key_engraver"
6796 \override StaffSymbol #'transparent = ##t
6797 \remove "Time_signature_engraver"
6798 \remove "Bar_engraver"
6799 minimumVerticalExtent = ##f
6803 \remove Ligature_bracket_engraver
6804 \consists Vaticana_ligature_engraver
6805 \override NoteHead #'style = #'vaticana_punctum
6806 \override Stem #'transparent = ##t
6812 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6813 \include "gregorian-init.ly"
6815 \notes \transpose c c' {
6816 % Scandicus Deminutus
6817 \[ g \pes a \pes \deminutum b \]
6824 \remove "Bar_number_engraver"
6828 \remove "Clef_engraver"
6829 \remove "Key_engraver"
6830 \override StaffSymbol #'transparent = ##t
6831 \remove "Time_signature_engraver"
6832 \remove "Bar_engraver"
6833 minimumVerticalExtent = ##f
6837 \remove Ligature_bracket_engraver
6838 \consists Vaticana_ligature_engraver
6839 \override NoteHead #'style = #'vaticana_punctum
6840 \override Stem #'transparent = ##t
6849 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6850 \include "gregorian-init.ly"
6852 \notes \transpose c c' {
6854 \[ g \oriscus a \pes \virga b \]
6861 \remove "Bar_number_engraver"
6865 \remove "Clef_engraver"
6866 \remove "Key_engraver"
6867 \override StaffSymbol #'transparent = ##t
6868 \remove "Time_signature_engraver"
6869 \remove "Bar_engraver"
6870 minimumVerticalExtent = ##f
6874 \remove Ligature_bracket_engraver
6875 \consists Vaticana_ligature_engraver
6876 \override NoteHead #'style = #'vaticana_punctum
6877 \override Stem #'transparent = ##t
6883 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6884 \include "gregorian-init.ly"
6886 \notes \transpose c c' {
6887 % Salicus Auctus Descendens
6888 \[ g \oriscus a \pes \auctum \descendens b \]
6895 \remove "Bar_number_engraver"
6899 \remove "Clef_engraver"
6900 \remove "Key_engraver"
6901 \override StaffSymbol #'transparent = ##t
6902 \remove "Time_signature_engraver"
6903 \remove "Bar_engraver"
6904 minimumVerticalExtent = ##f
6908 \remove Ligature_bracket_engraver
6909 \consists Vaticana_ligature_engraver
6910 \override NoteHead #'style = #'vaticana_punctum
6911 \override Stem #'transparent = ##t
6921 @lilypond[quote,noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6922 \include "gregorian-init.ly"
6924 \notes \transpose c c' {
6926 \[ \stropha b \stropha b \stropha a \]
6933 \remove "Bar_number_engraver"
6937 \remove "Clef_engraver"
6938 \remove "Key_engraver"
6939 \override StaffSymbol #'transparent = ##t
6940 \remove "Time_signature_engraver"
6941 \remove "Bar_engraver"
6942 minimumVerticalExtent = ##f
6946 \remove Ligature_bracket_engraver
6947 \consists Vaticana_ligature_engraver
6948 \override NoteHead #'style = #'vaticana_punctum
6949 \override Stem #'transparent = ##t
6960 Unlike most other neumes notation systems, the input language for
6961 neumes does not necessarily reflect directly the typographical
6962 appearance, but is designed to solely focuse on musical meaning. For
6963 example, @code{\[ a \pes b \flexa g \]} produces a Torculus consisting
6964 of three Punctum heads, while @code{\[ a \flexa g \pes b \]} produces
6965 a Porrectus with a curved flexa shape and only a single Punctum head.
6966 There is no command to explicitly typeset the curved flexa shape; the
6967 decision of when to typeset a curved flexa shape is purely taken from
6968 the musical input. The idea of this approach is to separate the
6969 musical aspects of the input from the notation style of the output.
6970 This way, the same input can be reused to typeset the same music in a
6971 different style of Gregorian chant notation.
6973 The following table shows the code fragments that produce the
6974 ligatures in the above neumes table. The letter in the first column
6975 in each line of the below table indicates to which ligature in the
6976 above table it refers. The second column gives the name of the
6977 ligature. The third column shows the code fragment that produces this
6978 ligature, using @code{g}, @code{a} and @code{b} as example pitches.
6980 @multitable @columnfractions .1 .4 .5
6994 Punctum Inclinatum @tab
6995 @code{\[ \inclinatum b \]}
6999 Punctum Auctum Ascendens @tab
7000 @code{\[ \auctum \ascendens b \]}
7004 Punctum Auctum Descendens @tab
7005 @code{\[ \auctum \descendens b \]}
7009 Punctum Inclinatum Auctum @tab
7010 @code{\[ \inclinatum \auctum b \]}
7014 Punctum Inclinatum Parvum @tab
7015 @code{\[ \inclinatum \deminutum b \]}
7020 @code{\[ \virga b \]}
7025 @code{\[ \stropha b \]}
7030 @code{\[ \stropha \auctum b \]}
7035 @code{\[ \oriscus b \]}
7039 Clivis vel Flexa @tab
7040 @code{\[ b \flexa g \]}
7044 Clivis Aucta Descendens @tab
7045 @code{\[ b \flexa \auctum \descendens g \]}
7049 Clivis Aucta Ascendens @tab
7050 @code{\[ b \flexa \auctum \ascendens g \]}
7055 @code{\[ b \flexa \deminutum g \]}
7059 Podatus vel Pes @tab
7060 @code{\[ g \pes b \]}
7064 Pes Auctus Descendens @tab
7065 @code{\[ g \pes \auctum \descendens b \]}
7069 Pes Auctus Ascendens @tab
7070 @code{\[ g \pes \auctum \ascendens b \]}
7075 @code{\[ g \pes \deminutum b \]}
7080 @code{\[ \oriscus g \pes \virga b \]}
7084 Pes Quassus Auctus Descendens @tab
7085 @code{\[ \oriscus g \pes \auctum \descendens b \]}
7090 @code{\[ \quilisma g \pes b \]}
7094 Quilisma Pes Auctus Descendens @tab
7095 @code{\[ \quilisma g \pes \auctum \descendens b \]}
7099 Pes Initio Debilis @tab
7100 @code{\[ \deminutum g \pes b \]}
7104 Pes Auctus Descendens Initio Debilis @tab
7105 @code{\[ \deminutum g \pes \auctum \descendens b \]}
7110 @code{\[ a \pes b \flexa g \]}
7114 Torculus Auctus Descendens @tab
7115 @code{\[ a \pes b \flexa \auctum \descendens g \]}
7119 Torculus Deminutus @tab
7120 @code{\[ a \pes b \flexa \deminutum g \]}
7124 Torculus Initio Debilis @tab
7125 @code{\[ \deminutum a \pes b \flexa g \]}
7129 Torculus Auctus Descendens Initio Debilis @tab
7130 @code{\[ \deminutum a \pes b \flexa \auctum \descendens g \]}
7134 Torculus Deminutus Initio Debilis @tab
7135 @code{\[ \deminutum a \pes b \flexa \deminutum g \]}
7140 @code{\[ a \flexa g \pes b \]}
7144 Porrectus Auctus Descendens @tab
7145 @code{\[ a \flexa g \pes \auctum \descendens b \]}
7149 Porrectus Deminutus @tab
7150 @code{\[ a \flexa g \pes \deminutum b \]}
7155 @code{\[ \virga b \inclinatum a \inclinatum g \]}
7159 Climacus Auctus @tab
7160 @code{\[ \virga b \inclinatum a \inclinatum \auctum g \]}
7164 Climacus Deminutus @tab
7165 @code{\[ \virga b \inclinatum a \inclinatum \deminutum g \]}
7170 @code{\[ g \pes a \virga b \]}
7174 Scandicus Auctus Descendens @tab
7175 @code{\[ g \pes a \pes \auctum \descendens b \]}
7179 Scandicus Deminutus @tab
7180 @code{\[ g \pes a \pes \deminutum b \]}
7185 @code{\[ g \oriscus a \pes \virga b \]}
7189 Salicus Auctus Descendens @tab
7190 @code{\[ g \oriscus a \pes \auctum \descendens b \]}
7195 @code{\[ \stropha b \stropha b \stropha a \]}
7201 The following head prefixes are supported
7203 @cindex @code{\virga}
7205 @cindex @code{\stropha}
7207 @cindex @code{\inclinatum}
7209 @cindex @code{\auctum}
7211 @cindex @code{\descendens}
7213 @cindex @code{\ascendens}
7215 @cindex @code{\oriscus}
7217 @cindex @code{\quilisma}
7219 @cindex @code{\deminutum}
7222 Head prefixes can be accumulated, though restrictions apply. For
7223 example, either @code{\descendens} or @code{\ascendens} can be applied
7224 to a head, but not both to the same head.
7227 @cindex @code{\flexa}
7228 Two adjacent heads can be tied together with the @code{\pes} and
7229 @code{\flexa} infix commands for a rising and falling line of melody,
7234 @node Vaticana style contexts
7235 @subsection Vaticana style contexts
7237 @cindex VaticanaVoiceContext
7238 @cindex VaticanaStaffContext
7240 The predefined @code{VaticanaVoiceContext} and
7241 @code{VaticanaStaffContext} can be used to easily engrave a piece of
7242 Gregorian Chant in the style of the Editio Vaticana. These contexts
7243 initialize all relevant context properties and grob properties to
7244 proper values. With these contexts, you can immediately go ahead
7245 entering the chant, as the following short excerpt demonstrates
7247 @lilypond[quote,raggedright,verbatim,noindent]
7248 \include "gregorian-init.ly"
7251 \context VaticanaVoice = "cantus" {
7252 \override Score.BarNumber #'transparent = ##t
7254 \[ c'\melisma c' \flexa a \]
7255 \[ a \flexa \deminutum g\melismaEnd \]
7257 \[ f\melisma \pes a c' c' \pes d'\melismaEnd \]
7258 c' \divisioMinima \break
7259 \[ c'\melisma c' \flexa a \]
7260 \[ a \flexa \deminutum g\melismaEnd \] f \divisioMinima
7263 \lyricsto "cantus" \new Lyrics \lyrics {
7264 San- ctus, San- ctus, San- ctus
7271 @subsection Figured bass
7273 @cindex Basso continuo
7275 @c TODO: musicological blurb about FB
7278 LilyPond has limited support for figured bass
7280 @lilypond[quote,verbatim,fragment]
7282 \context Voice \notes { \clef bass dis4 c d ais }
7283 \context FiguredBass \figures {
7284 < 6 >4 < 7 >8 < 6+ [_!] >
7290 The support for figured bass consists of two parts: there is an input
7291 mode, introduced by @code{\figures}, where you can enter bass figures
7292 as numbers, and there is a context called @internalsref{FiguredBass} that
7293 takes care of making @internalsref{BassFigure} objects.
7295 In figures input mode, a group of bass figures is delimited by
7296 @code{<} and @code{>}. The duration is entered after the @code{>>}
7300 @lilypond[quote,fragment]
7301 \context FiguredBass
7305 Accidentals are added when you append @code{-}, @code{!} and @code{+}
7311 @lilypond[quote,fragment]
7312 \context FiguredBass
7313 \figures { <4- 6+ 7!> }
7316 Spaces or dashes may be inserted by using @code{_}. Brackets are
7317 introduced with @code{[} and @code{]}
7322 @lilypond[quote,fragment]
7323 \context FiguredBass
7324 \figures { < [4 6] 8 [_! 12]> }
7327 Although the support for figured bass may superficially resemble chord
7328 support, it works much simpler. The @code{\figures} mode simply
7329 stores the numbers , and @internalsref{FiguredBass} context prints
7330 them as entered. There is no conversion to pitches, and no
7331 realizations of the bass are played in the MIDI file.
7333 Internally, the code produces markup texts. You can use any of the
7334 markup text properties to override formatting. For example, the
7335 vertical spacing of the figures may be set with @code{baseline-skip}.
7339 Program reference: @internalsref{BassFigureEvent} music, @internalsref{BassFigure} object,
7340 and @internalsref{FiguredBass} context.
7344 Slash notation for alterations is not supported.
7346 @node Contemporary notation
7347 @section Contemporary notation
7349 In the 20th century, composers have greatly expanded the musical
7350 vocabulary. With this expansion, many innovations in musical notation
7351 have been tried. The book by Stone (1980) gives a comprehensive
7352 overview (see @ref{Literature list}). In general, the use of new,
7353 innovative notation makes a piece harder to understand and perform and
7354 its use should therefore be avoided if possible. For this reason,
7355 support for contemporary notation in LilyPond is limited.
7364 @subsection Clusters
7368 A cluster indicates a continuous range of pitches to be played. They
7369 can be denoted as the envelope of a set of notes. They are entered by
7370 applying the function @code{notes-to-clusters} to a sequence of
7373 @lilypond[quote,relative=2,verbatim]
7374 \applymusic #notes-to-clusters { <c e > <b f'> }
7377 The following example (from
7378 @inputfileref{input/regression,cluster.ly}) shows what the result
7381 @lilypondfile[quote]{cluster.ly}
7383 Ordinary notes and clusters can be put together in the same staff,
7384 even simultaneously. In such a case no attempt is made to
7385 automatically avoid collisions between ordinary notes and clusters.
7389 Program reference: @internalsref{ClusterSpanner},
7390 @internalsref{ClusterSpannerBeacon},
7391 @internalsref{Cluster_spanner_engraver}, and
7392 @internalsref{ClusterNoteEvent}.
7394 Examples: @inputfileref{input/regression,cluster.ly}.
7398 Music expressions like @code{<< @{ g8 e8 @} a4 >>} are not printed
7399 accurately. Use @code{<g a>8 <e a>8} instead.
7404 @subsection Fermatas
7410 Contemporary music notation frequently uses special fermata symbols to
7411 indicate fermatas of differing lengths. The following fermatas are
7414 @lilypond[quote,raggedright]
7437 \context Lyrics \lyrics {
7438 \override LyricText #'font-family = #'typewriter
7439 "shortfermata" "fermata" "longfermata" "verylongfermata"
7445 See @ref{Articulations} for general instructions how to apply scripts
7446 such as fermatas to a @code{\notes@{@}} block.
7449 @node Special notation
7450 @section Special notation
7454 * Easy Notation note heads::
7458 @subsection Balloon help
7460 Elements of notation can be marked and named with the help of a square
7461 balloon. The primary purpose of this feature is to explain notation.
7463 The following example demonstrates its use.
7465 @lilypond[quote,verbatim,fragment,raggedright,relative=2]
7468 #(add-balloon-text 'NoteHead "heads, or tails?"
7474 The function @code{add-balloon-text} takes the name of a grob, the
7475 label to print and where to put the label relative to the object. In
7476 the above example, the text ``heads or tails?'' ends 3 spaces below
7480 @cindex notation, explaining
7484 Program reference: @internalsref{text-balloon-interface}.
7486 Examples: @inputfileref{input/regression,balloon.ly}.
7488 @node Easy Notation note heads
7489 @subsection Easy Notation note heads
7491 @cindex easy notation
7494 The `easy play' note head includes a name inside the head. It is
7495 used in music for beginners
7497 @lilypond[quote,raggedright,verbatim,staffsize=26]
7502 The command @code{\setEasyHeads} overrides settings for the
7503 @internalsref{NoteHead} object. To make the letters readable, it has
7504 to be printed in a large font size. To print with a larger font, see
7505 @ref{Setting global staff size}.
7510 If you view the result with Xdvi, staff lines may show through the
7511 letters. Printing the PostScript file obtained does produce the
7516 @cindex \setEasyHeads
7517 @code{\setEasyHeads}
7523 Entered music can also be converted to MIDI output. The performance
7524 is intended for proof-hearing the music for errors.
7526 Ties, dynamics and tempo changes are interpreted. Dynamic marks,
7527 crescendi and decrescendi translate into MIDI volume levels. Dynamic
7528 marks translate to a fixed fraction of the available MIDI volume
7529 range, crescendi and decrescendi make the volume vary linearly between
7530 their two extremities. The fractions can be adjusted by
7531 @code{dynamicAbsoluteVolumeFunction} in @internalsref{Voice} context.
7532 For each type of MIDI instrument, a volume range can be defined. This
7533 gives a basic equalizer control, which can enhance the quality of
7534 the MIDI output remarkably. The equalizer can be controlled by
7535 setting @code{instrumentEqualizer}.
7539 Many musically interesting effects, such as swing, articulation,
7540 slurring, etc., are not translated to MIDI.
7542 The MIDI output allocates a channel for each Staff, and one for global
7543 settings. Hence, the MIDI file should not have more than 15 staves
7544 (or 14 if you do not use drums). Other staves will remain silent.
7549 * MIDI instrument names::
7554 @subsection MIDI block
7558 The MIDI block is analogous to the paper block, but it is somewhat
7559 simpler. The @code{\midi} block can contain
7563 @item a @code{\tempo} definition, and
7564 @item context definitions.
7567 A number followed by a period is interpreted as a real number, so
7568 for setting the tempo for dotted notes, an extra space should be
7569 inserted, for example
7572 \midi @{ \tempo 4 . = 120 @}
7576 @cindex context definition
7578 Context definitions follow precisely the same syntax as within the
7579 \paper block. Translation modules for sound are called performers.
7580 The contexts for MIDI output are defined in @file{ly/performer-init.ly}.
7583 @node MIDI instrument names
7584 @subsection MIDI instrument names
7586 @cindex instrument names
7587 @cindex @code{Staff.midiInstrument}
7589 The MIDI instrument name is set by the @code{Staff.midiInstrument}
7590 property. The instrument name should be chosen from the list in
7591 @ref{MIDI instruments}.
7595 If the selected string does not exactly match, the default is used,
7596 which is the Grand Piano.