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
71 @lilypond[fragment,verbatim]
81 @cindex Note specification
83 @cindex entering notes
85 The most common syntax for pitch entry is used in @code{\chords} and
86 @code{\notes} mode. In these modes, pitches may be designated by
87 names. The notes are specified by the letters @code{a} through
88 @code{g}, while the octave is formed with notes ranging from @code{c}
89 to @code{b}. The pitch @code{c} is an octave below middle C and the
90 letters span the octave above that C
93 @lilypond[fragment,verbatim]
95 a,4 b, c d e f g a b c' d' e' \clef treble f' g' a' b' c''
99 @cindex note names, Dutch
101 A sharp is formed by adding @code{-is} to the end of a pitch name and
102 a flat is formed by adding @code{-es}. Double sharps and double flats
103 are obtained by adding @code{-isis} or @code{-eses}. These
104 names are the Dutch note names. In Dutch, @code{aes} is contracted to
105 @code{as}, but both forms are accepted. Similarly, both
106 @code{es} and @code{ees} are accepted.
108 Half-flats and half-sharps are formed by adding @code{-eh} and
109 @code{-ih}; the following is a series of Cs with increasing pitches
111 @cindex quarter tones
112 @cindex semi-flats, semi-sharps
115 @lilypond[verbatim,relative=3]
128 There are predefined sets of note names for various other languages.
129 To use them, include the language specific init file. For
130 example: @code{\include "english.ly"}. The available language files
131 and the note names they define are
136 Note Names sharp flat
137 nederlands.ly c d e f g a bes b -is -es
138 english.ly c d e f g a bf b -s/-sharp -f/-flat
140 deutsch.ly c d e f g a b h -is -es
141 norsk.ly c d e f g a b h -iss/-is -ess/-es
142 svenska.ly c d e f g a b h -iss -ess
143 italiano.ly do re mi fa sol la sib si -d -b
144 catalan.ly do re mi fa sol la sib si -d/-s -b
145 espanol.ly do re mi fa sol la sib si -s -b
154 The optional octave specification takes the form of a series of
155 single quote (`@code{'}') characters or a series of comma
156 (`@code{,}') characters. Each @code{'} raises the pitch by one
157 octave; each @code{,} lowers the pitch by an octave
160 @lilypond[fragment,verbatim]
161 c' c'' es' g' as' gisis' ais'
168 Notes can be hidden and unhidden with the following commands
170 @cindex @code{\hideNotes}
172 @cindex @code{\unHideNotes}
178 Program reference: @internalsref{NoteEvent}, and @internalsref{NoteHead}.
180 @node Chromatic alterations
181 @subsection Chromatic alterations
183 Normally accidentals are printed automatically, but you may also
184 print them manually. A reminder accidental
185 @cindex reminder accidental
187 can be forced by adding an exclamation mark @code{!}
188 after the pitch. A cautionary accidental
189 @cindex cautionary accidental
190 @cindex parenthesized accidental
191 (i.e. an accidental within parentheses) can be obtained by adding the
192 question mark `@code{?}' after the pitch
195 @lilypond[fragment,verbatim]
196 cis' cis' cis'! cis'?
203 The automatic production of accidentals can be tuned in many
204 ways. For more information, refer to @ref{Accidentals}.
209 There are no generally accepted standards for denoting three quarter
210 flats, so LilyPond's symbol does not conform to any standard.
215 A chord is formed by a enclosing a set of pitches in @code{<} and
216 @code{>}. A chord may be followed by a duration, and a set of
217 articulations, just like simple notes.
220 @lilypond[relative=1]
232 Rests are entered like notes, with the note name @code{r}
235 @lilypond[raggedright,verbatim]
240 Whole bar rests, centered in middle of the bar,
241 must be done with multi-measure rests. They are discussed in
242 @ref{Multi measure rests}.
245 A rest's vertical position may be explicitly specified by entering a
246 note with the @code{\rest} keyword appended. This makes manual
247 formatting in polyphonic music easier. Rest collision testing will
248 leave these rests alone
251 @lilypond[raggedright,verbatim]
258 Program reference: @internalsref{RestEvent}, and @internalsref{Rest}.
265 @cindex Invisible rest
268 An invisible rest (also called a `skip') can be entered like a note
269 with note name `@code{s}' or with @code{\skip @var{duration}}
272 @lilypond[raggedright,verbatim]
277 The @code{s} syntax is only available in note mode and chord mode. In
278 other situations, you should use the @code{\skip} command
281 @lilypond[raggedright,verbatim]
284 { \time 4/8 \skip 2 \time 4/4 }
285 \notes\relative c'' { a2 a1 }
291 The skip command is merely an empty musical placeholder. It does not
292 produce any output, not even transparent output.
294 The @code{s} skip command does create @internalsref{Staff} and
295 @internalsref{Voice} when necessary, similar to note and rest
296 commands. For example, the following results in an empty staff.
299 @lilypond[raggedright,verbatim]
300 \score { \notes { s4 } }
304 The same fragment using @code{\skip} results in an empty page.
308 Program reference: @internalsref{SkipEvent}, @internalsref{SkipMusic}.
313 @subsection Durations
319 In Note, Chord, and Lyrics mode, durations are designated by numbers
320 and dots: durations are entered as their reciprocal values. For example,
321 a quarter note is entered using a @code{4} (since it is a 1/4 note), while
322 a half note is entered using a @code{2} (since it is a 1/2 note). For notes
323 longer than a whole you must use variables
327 c'1 c'2 c'4 c'8 c'16 c'32 c'64 c'64
329 r1 r2 r4 r8 r16 r32 r64 r64
335 \notes \relative c'' {
336 a\breve*1/2 \autoBeamOff
337 a1 a2 a4 a8 a16 a32 a64 a64
338 r\longa*1/4 r\breve *1/2
339 r1 r2 r4 r8 r16 r32 r64 r64
345 \remove "Clef_engraver"
346 \override StaffSymbol #'transparent = ##t
347 \override TimeSignature #'transparent = ##t
348 \override BarLine #'transparent = ##t
349 \consists "Pitch_squash_engraver"
357 If the duration is omitted then it is set to the previously entered
358 duration. The default for the first note is a quarter note. The duration
359 can be followed by dots (`@code{.}') in order to obtain dotted note
364 @lilypond[fragment,verbatim]
365 a' b' c''8 b' a'4 a'4. b'4.. c'8.
371 You can alter the length of duration by a fraction @var{N/M}
372 appending `@code{*}@var{N/M}' (or `@code{*}@var{N}' if @var{M=1}). This
373 will not affect the appearance of the notes or rests produced.
375 In the following example, the first three notes take up exactly two
376 beats, but no triplet bracket is printed.
378 @lilypond[fragment,relative=3,verbatim]
380 a4*2/3 gis4*2/3 a4*2/3
387 Dots are normally moved up to avoid staff lines, except in polyphonic
388 situations. The following commands may be used to force a particular
391 @cindex @code{\dotsUp}
393 @cindex @code{\dotsDown}
395 @cindex @code{\dotsBoth}
400 This manual: @ref{Tuplets}
402 Program reference: @internalsref{Dots}, and @internalsref{DotColumn}.
407 Whenever a note is found, a @internalsref{Stem} object is created
408 automatically. For whole notes and rests, they are also created but
413 @cindex @code{\stemUp}
415 @cindex @code{\stemDown}
417 @cindex @code{\stemBoth}
428 A tie connects two adjacent note heads of the same pitch. The tie in
429 effect extends the length of a note. Ties should not be confused with
430 slurs, which indicate articulation, or phrasing slurs, which indicate
431 musical phrasing. A tie is entered using the tilde symbol `@code{~}'
434 @lilypond[fragment,verbatim]
435 e' ~ e' <c' e' g'> ~ <c' e' g'>
439 When a tie is applied to a chord, all note heads whose pitches match
440 are connected. When no note heads match, no ties will be created.
442 In its meaning a tie is just a way of extending a note duration, similar
443 to the augmentation dot; in the following example there are two ways of
444 notating exactly the same concept
447 @lilypond[fragment,raggedright]
448 \time 3/4 c'2. c'2 ~ c'4
451 If you need to tie a lot of notes over bars, it may be easier to use automatic
452 note splitting (see @ref{Automatic note splitting}).
457 @cindex @code{\tieUp}
459 @cindex @code{\tieDown}
461 @cindex @code{\tieBoth}
463 @cindex @code{\tieDotted}
465 @cindex @code{\tieSolid}
470 In this manual: @ref{Automatic note splitting}.
472 Program reference: @internalsref{TieEvent}, @internalsref{Tie}.
474 For tying only a subset of the note heads of a pair of chords, see
475 @inputfileref{input/regression,tie-chord-partial.ly}.
480 Switching staves when a tie is active will not produce a slanted tie.
482 Formatting of ties is a difficult subject. The results are often not
492 @cindex @code{\times}
494 Tuplets are made out of a music expression by multiplying all durations
497 @cindex @code{\times}
499 \times @var{fraction} @var{musicexpr}
503 The duration of @var{musicexpr} will be multiplied by the fraction.
504 The fraction's denominator will be printed over the notes, optionally
505 with a bracket. The most common tuplet is the triplet in which 3
506 notes have the length of 2, so the notes are 2/3 of their written
510 @lilypond[fragment,verbatim]
511 g'4 \times 2/3 {c'4 c' c'} d'4 d'4
515 The property @code{tupletSpannerDuration} specifies how long each
516 bracket should last. With this, you can make lots of tuplets while
517 typing @code{\times} only once, saving lots of typing. In the next
518 example, there are two triplets shown, while @code{\times} was only
522 @lilypond[fragment,relative=1,raggedright,verbatim]
523 \set tupletSpannerDuration = #(ly:make-moment 1 4)
524 \times 2/3 { c'8 c c c c c }
528 The format of the number is determined by the property
529 @code{tupletNumberFormatFunction}. The default prints only the
530 denominator, but if it is set to the Scheme function
531 @code{fraction-tuplet-formatter}, @var{num}:@var{den} will be printed
535 @cindex @code{tupletNumberFormatFunction}
536 @cindex tuplet formatting
541 @cindex @code{\tupletUp}
543 @cindex @code{\tupletDown}
545 @cindex @code{\tupletBoth}
550 Program reference: @internalsref{TupletBracket}, and @internalsref{TimeScaledMusic}.
552 Examples: @inputfileref{input/regression,tuplet-nest.ly}.
556 Nested tuplets are not formatted automatically. In this case, outer
557 tuplet brackets should be moved manually, which is demonstrated in
558 @inputfileref{input/regression,tuplet-nest.ly}.
562 @node Easier music entry
563 @section Easier music entry
566 This section deals with tricks and features of the input language that
567 were added solely to help entering music, finding and correcting
568 mistakes. There are also external tools that make debugging easier.
569 See @ref{Point and click} for more information.
571 It is also possible to enter and edit music using other programs. For
572 example, GUI interfaces, or MIDI sequencers. Refer to the LilyPond
573 website for more information.
580 * Skipping corrected music::
581 * Automatic note splitting::
587 @node Relative octaves
588 @subsection Relative octaves
590 @cindex relative octave specification
592 Octaves are specified by adding @code{'} and @code{,} to pitch names.
593 When you copy existing music, it is easy to accidentally put a pitch
594 in the wrong octave and hard to find such an error. The relative
595 octave mode prevents these errors: a single error puts the rest of the
596 piece off by one octave
598 @cindex @code{\relative}
600 \relative @var{startpitch} @var{musicexpr}
603 The octave of notes that appear in @var{musicexpr} are calculated as
604 follows: If no octave changing marks are used, the basic interval
605 between this and the last note is always taken to be a fourth or
606 less. This distance is determined without regarding alterations; a
607 @code{fisis} following a @code{ceses} will be put above the
610 The octave changing marks @code{'} and @code{,} can be added to raise
611 or lower the pitch by an extra octave. Upon entering relative mode,
612 an absolute starting pitch must be specified that will act as the
613 predecessor of the first note of @var{musicexpr}.
615 Here is the relative mode shown in action
617 @lilypond[fragment,raggedright,verbatim]
624 Octave changing marks are used for intervals greater than a fourth
626 @lilypond[fragment,verbatim]
633 If the preceding item is a chord, the first note of the chord is used
634 to determine the first note of the next chord
637 @lilypond[fragment,verbatim]
645 @cindex @code{\notes}
647 The pitch after the @code{\relative} contains a note name. To parse
648 the note name as a pitch, it must surrounded by @code{\notes}
650 The relative conversion will not affect @code{\transpose},
651 @code{\chords} or @code{\relative} sections in its argument. If you
652 want to use relative within transposed music, you must place an
653 additional @code{\relative} inside the @code{\transpose}.
656 @subsection Octave check
659 Octave checks make octave errors easier to correct: a note may be
660 followed by @code{=}@var{quotes} which indicates what its absolute
661 octave should be. In the following example,
663 \relative c'' @{ c='' b=' d,='' @}
667 @c take care with @code, adds confusing quotes.
668 the d will generate a warning, because a d'' is expected, but a d' is
669 found. In the output, the octave is corrected for this and the
674 There is also a syntax that is separate from the notes.
679 This checks that @var{pitch} (without octave) yields @var{pitch} (with
680 octave) in \relative mode. If not, a warning is printed, and the
681 octave is corrected, for example, the first check is passed
682 successfully. The second check fails with an error message. The
683 octave is adjusted so the following notes are in the correct octave
694 The octave of a note following an octave check is determined with
695 respect to the note preceding it. In the next fragment, the last note
696 is a @code{a'}, above middle C. Hence, the @code{\octave} check may
697 be deleted without changing the meaning of the piece.
700 @lilypond[verbatim,fragment]
710 @subsection Bar check
714 @cindex @code{barCheckSynchronize}
717 Bar checks help detect errors in the durations. A bar check is
718 entered using the bar symbol, `@code{|}'. Whenever it is encountered
719 during interpretation, it should fall on a measure boundary. If it
720 does not, a warning is printed. In the next example, the second bar
721 check will signal an error
723 \time 3/4 c2 e4 | g2 |
726 Bar checks can also be used in lyrics, for example
731 Twin -- kle | Twin -- kle
736 @cindex skipTypesetting
738 Failed bar checks are caused by entering incorrect
739 durations. Incorrect durations often completely garble up the score,
740 especially if it is polyphonic, so you should start correcting the
741 score by scanning for failed bar checks and incorrect durations. To
742 speed up this process, you can use @code{skipTypesetting}, described
745 @node Skipping corrected music
746 @subsection Skipping corrected music
748 The property @code{Score.skipTypesetting} can be used to switch on and
749 off typesetting completely during the interpretation phase. When
750 typesetting is switched off, the music is processed much more quickly.
751 This can be used to skip over the parts of a score that have already
752 been checked for errors
755 @lilypond[fragment,raggedright,verbatim]
757 \set Score.skipTypesetting = ##t
759 \set Score.skipTypesetting = ##f
764 @node Automatic note splitting
765 @subsection Automatic note splitting
767 Long notes can be converted automatically to tied notes. This is done
768 by replacing the @internalsref{Note_heads_engraver} by the
769 @internalsref{Completion_heads_engraver}.
770 In the following examples, notes crossing the bar line are split and tied.
774 @lilypond[noindent,verbatim,relative=2]
776 \remove "Note_heads_engraver"
777 \consists "Completion_heads_engraver"
779 c2. c8 d4 e f g a b c8 c2 b4 a g16 f4 e d c8. c2
784 This engraver splits all running notes at the bar line, and inserts
785 ties. One of its uses is to debug complex scores: if the measures are
786 not entirely filled, then the ties exactly show how much each measure
791 Not all durations (especially those containing tuplets) can be
792 represented exactly; the engraver will not insert tuplets.
796 Examples: @inputfileref{input/regression,completion-heads.ly}.
798 Program reference: @internalsref{Completion_heads_engraver}.
802 @section Staff notation
804 This section describes music notation that occurs on staff level,
805 such as keys, clefs and time signatures.
807 @cindex Staff notation
821 @subsection Staff symbol
823 @cindex adjusting staff symbol
825 Notes, dynamic signs, etc. are grouped
826 with a set of horizontal lines, into a staff (plural `staves'). In our
827 system, these lines are drawn using a separate layout object called
831 @cindex staff lines, setting number of
832 @cindex staff lines, setting thickness of
833 @cindex thickness of staff lines, setting
834 @cindex number of staff lines, setting
838 Program reference: @internalsref{StaffSymbol}.
840 Examples: @inputfileref{input/test,staff-lines.ly},
841 @inputfileref{input/test,staff-size.ly}.
845 If a staff is ended halfway a piece, the staff symbol may not end
846 exactly on the bar line.
850 @subsection Key signature
851 @cindex Key signature
855 The key signature indicates the scale in which a piece is played. It
856 is denoted by a set of alterations (flats or sharps) at the start of
860 Setting or changing the key signature is done with the @code{\key}
863 @code{\key} @var{pitch} @var{type}
866 @cindex @code{\minor}
867 @cindex @code{\major}
868 @cindex @code{\minor}
869 @cindex @code{\ionian}
870 @cindex @code{\locrian}
871 @cindex @code{\aeolian}
872 @cindex @code{\mixolydian}
873 @cindex @code{\lydian}
874 @cindex @code{\phrygian}
875 @cindex @code{\dorian}
877 Here, @var{type} should be @code{\major} or @code{\minor} to get
878 @var{pitch}-major or @var{pitch}-minor, respectively.
879 The standard mode names @code{\ionian},
880 @code{\locrian}, @code{\aeolian}, @code{\mixolydian}, @code{\lydian},
881 @code{\phrygian}, and @code{\dorian} are also defined.
883 This command sets the context property
884 @internalsref{Staff}.@code{keySignature}. Non-standard key signatures
885 can be specified by setting this property directly.
887 Accidentals and key signatures often confuse new users, because
888 unaltered notes get natural signs depending on the key signature. For
889 more information, see @ref{More about pitches}.
893 The ordering of a key cancellation is wrong when it is combined with
894 repeat bar lines. The cancellation is also printed after a line break.
898 Program reference: @internalsref{KeyChangeEvent}, and @internalsref{KeySignature}.
900 @cindex @code{keySignature}
907 The clef indicates which lines of the staff correspond to which
911 The clef can be set or changed with the @code{\clef} command
913 @lilypond[fragment,verbatim]
914 \key f\major c''2 \clef alto g'2
918 Supported clef-names include
919 @c Moved standard clefs to the top /MB
923 @item treble, violin, G, G2
936 G clef on 1st line, so-called French violin clef
941 @cindex mezzosoprano clef
944 @cindex baritone clef
947 @cindex varbaritone clef
958 By adding @code{_8} or @code{^8} to the clef name, the clef is
959 transposed one octave down or up, respectively, and @code{_15} and
960 @code{^15} transposes by two octaves. The argument @var{clefname}
961 must be enclosed in quotes when it contains underscores or digits. For
965 @cindex choral tenor clef
967 @lilypond[verbatim,fragment,relative=1]
972 This command is equivalent to setting @code{clefGlyph},
973 @code{clefPosition} (which controls the Y position of the clef),
974 @code{centralCPosition} and @code{clefOctavation}. A clef is printed
975 when any of these properties are changed.
979 Program reference: the object for this symbol is @internalsref{Clef}.
983 @node Ottava brackets
984 @subsection Ottava brackets
986 ``Ottava'' brackets introduce an extra transposition of an octave for
987 the staff. They are created by invoking the function
988 @code{set-octavation}
995 @lilypond[verbatim,fragment]
1006 The @code{set-octavation} function also takes -1 (for 8va bassa) and 2
1007 (for 15ma) as arguments. Internally the function sets the properties
1008 @code{ottavation} (e.g. to @code{"8va"}) and
1009 @code{centralCPosition}. For overriding the text of the bracket, set
1010 @code{ottavation} after invoking @code{set-octavation}, i.e.,
1014 \set Staff.ottavation = #"8"
1019 Program reference: @internalsref{OttavaBracket}.
1021 Examples: @inputfileref{input/regression,ottava.ly},
1022 @inputfileref{input/regression,ottava-broken.ly}.
1026 @code{set-octavation} will get confused when clef changes happen
1027 during an octavation bracket.
1029 @node Time signature
1030 @subsection Time signature
1031 @cindex Time signature
1033 @cindex @code{\time}
1035 Time signature indicates the metrum of a piece: a regular pattern of
1036 strong and weak beats. It is denoted by a fraction at the start of the
1040 The time signature is set or changed by the @code{\time}
1043 @lilypond[fragment,verbatim]
1044 \time 2/4 c'2 \time 3/4 c'2.
1048 The symbol that is printed can be customized with the @code{style}
1049 property. Setting it to @code{#'()} uses fraction style for 4/4 and
1050 2/2 time. There are many more options for its layout. See
1051 @inputfileref{input/test,time.ly} for more examples.
1054 This command sets the property @code{timeSignatureFraction},
1055 @code{beatLength} and @code{measureLength} in the @code{Timing}
1056 context, which is normally aliased to @internalsref{Score}. The
1057 property @code{measureLength} determines where bar lines should be
1058 inserted, and how automatic beams should be generated. Changing the
1059 value of @code{timeSignatureFraction} also causes the symbol to be
1062 More options are available through the Scheme function
1063 @code{set-time-signature}. In combination with the
1064 @internalsref{Measure_grouping_engraver}, it will create
1065 @internalsref{MeasureGrouping} signs. Such signs ease reading
1066 rhythmically complex modern music. In the following example, the 9/8
1067 measure is subdivided in 2, 2, 2 and 3. This is passed to
1068 @code{set-time-signature} as the third argument @code{(2 2 2 3)}
1071 @lilypond[raggedright,verbatim]
1073 \notes \relative c'' {
1074 #(set-time-signature 9 8 '(2 2 2 3))
1075 g8[ g] d[ d] g[ g] a8[( bes g]) |
1076 #(set-time-signature 5 8 '(3 2))
1082 \consists "Measure_grouping_engraver"
1091 Program reference: @internalsref{TimeSignature}, and @internalsref{Timing_engraver}.
1096 Automatic beaming does not use the measure grouping specified with
1097 @code{set-time-signature}.
1099 @node Partial measures
1100 @subsection Partial measures
1103 @cindex partial measure
1104 @cindex measure, partial
1105 @cindex shorten measures
1106 @cindex @code{\partial}
1108 Partial measures, for example in upsteps, are entered using the
1109 @code{\partial} command
1111 @lilypond[fragment,verbatim,relative=2]
1112 \partial 16*5 c16 cis d dis e | a2. c,4 | b2
1116 The syntax for this command is
1118 \partial @var{duration}
1120 This is internally translated into
1122 \set Timing.measurePosition = -@var{length of duration}
1125 The property @code{measurePosition} contains a rational number
1126 indicating how much of the measure has passed at this point.
1128 @node Unmetered music
1129 @subsection Unmetered music
1131 Bar lines and bar numbers are calculated automatically. For unmetered
1132 music (e.g. cadenzas), this is not desirable. By setting
1133 @code{Score.timing} to false, this automatic timing can be switched
1134 off. Empty bar lines,
1141 indicate where line breaks can occur.
1147 @cindex @code{\cadenzaOn}
1149 @cindex @code{\cadenzaOff}
1153 @subsection Bar lines
1157 @cindex measure lines
1161 Bar lines delimit measures, but are also used to indicate repeats.
1162 Normally, they are inserted automatically. Line breaks may only
1163 happen on bar lines.
1167 of bar lines can be forced with the @code{\bar} command
1170 @lilypond[relative=2,fragment,verbatim]
1175 The following bar types are available
1177 @lilypond[fragment,relative=1,raggedright,verbatim]
1191 For allowing line breaks, there is a special command,
1195 This will insert an invisible bar line, and allow line breaks at this
1198 In scores with many staves, a @code{\bar} command in one staff is
1199 automatically applied to all staves. The resulting bar lines are
1200 connected between different staves of a @internalsref{StaffGroup}
1203 @lilypond[fragment,verbatim]
1205 \context StaffGroup <<
1211 \new Staff { \clef bass c4 g e g }
1213 \new Staff { \clef bass c2 c2 }
1218 A bar line is created whenever the @code{whichBar} property is set.
1219 At the start of a measure it is set to the contents of
1220 @code{defaultBarType}. The contents of @code{repeatCommands} are used
1221 to override default measure bars.
1223 The command @code{\bar }@var{bartype} is a short cut for doing
1224 @code{\set Timing.whichBar = }@var{bartype}. Whenever @code{whichBar}
1225 is set to a string, a bar line of that type is created.
1228 @cindex repeatCommands
1229 @cindex defaultBarType
1231 You are encouraged to use @code{\repeat} for repetitions. See
1238 In this manual: @ref{Repeats}.
1241 Program reference: the bar line objects that are created at
1242 @internalsref{Staff} level are called @internalsref{BarLine}, the bar
1243 lines that span staves are @internalsref{SpanBar} objects.
1245 @cindex bar lines at start of system
1246 @cindex start of system
1248 The bar lines at the start of each system are
1249 @internalsref{SystemStartBar}, @internalsref{SystemStartBrace}, and
1250 @internalsref{SystemStartBracket}. Only one of these types is created
1251 in every context, and that type is determined by the property
1252 @code{systemStartDelimiter}.
1254 Examples: @inputfileref{input/test,bar-lines.ly},
1260 The easiest way to enter fragments with more than one voice on a staff
1261 is to split chords using the separator @code{\\}. You can use it for
1262 small, short-lived voices or for single chords
1265 @lilypond[verbatim,fragment]
1266 \context Staff \relative c'' {
1267 c4 << { f d e } \\ { b c2 } >>
1268 c4 << g' \\ b, \\ f' \\ d >>
1273 The separator causes @internalsref{Voice} contexts@footnote{Polyphonic
1274 voices are sometimes called "layers" other notation packages}
1276 to be instantiated. They bear the names @code{"1"}, @code{"2"}, etc. In
1277 each of these contexts, vertical direction of slurs, stems, etc. is set
1280 @cindex @code{\voiceOne}
1281 @cindex @code{\voiceFour}
1283 This can also be done by instantiating @internalsref{Voice} contexts
1284 by hand, and using @code{\voiceOne}, up to @code{\voiceFour} to assign
1285 a stem directions and horizontal shift for each part
1289 @lilypond[raggedright,verbatim]
1292 \new Voice { \voiceOne cis2 b }
1293 \new Voice { \voiceThree b4 ais ~ ais4 gis4 }
1294 \new Voice { \voiceTwo fis4~ fis4 f ~ f } >>
1299 The command @code{\oneVoice} will revert back to the normal setting.
1300 @cindex @code{\oneVoice}
1303 Normally, note heads with a different number of dots are not merged, but
1304 when the object property @code{merge-differently-dotted} is set in
1305 the @internalsref{NoteCollision} object, they are merged
1307 @lilypond[verbatim,fragment,raggedright]
1308 \relative c'' \context Voice << {
1310 \override Staff.NoteCollision
1311 #'merge-differently-dotted = ##t
1313 } \\ { g8.[ f16] g8.[ f16] } >>
1317 Similarly, you can merge half note heads with eighth notes, by setting
1318 @code{merge-differently-headed}
1320 @lilypond[fragment,relative=3,verbatim]
1323 \override Staff.NoteCollision
1324 #'merge-differently-headed = ##t
1325 c8 c4. } \\ { c2 c2 } >>
1329 LilyPond also vertically shifts rests that are opposite of a stem
1333 @lilypond[raggedright,fragment,verbatim]
1334 \context Voice << c''4 \\ r4 >>
1343 @cindex @code{\oneVoice}
1345 @cindex @code{\voiceOne}
1347 @cindex @code{\voiceTwo}
1349 @cindex @code{\voiceThree}
1351 @cindex @code{\voiceFour}
1355 The following commands specify in what chords of the current voice
1356 should be shifted: the outer voice has @code{\shiftOff}, and the inner
1357 voices have @code{\shiftOn}, @code{\shiftOnn}, etc.
1360 @cindex @code{\shiftOn}
1362 @cindex @code{\shiftOnn}
1364 @cindex @code{\shiftOnnn}
1366 @cindex @code{\shiftOff}
1373 Program reference: the objects responsible for resolving collisions are
1374 @internalsref{NoteCollision} and @internalsref{RestCollision}.
1376 Examples: See also example files
1377 @inputfileref{input/regression,collision-dots.ly},
1378 @inputfileref{input/regression,collision-head-chords.ly},
1379 @inputfileref{input/regression,collision-heads.ly},
1380 @inputfileref{input/regression,collision-mesh.ly}, and
1381 @inputfileref{input/regression,collisions.ly}.
1386 Resolving collisions is a intricate subject, and only a few situations
1387 are handled. When LilyPond cannot cope, the @code{force-hshift}
1388 property of the @internalsref{NoteColumn} object and pitched rests can
1389 be used to override typesetting decisions.
1391 When using @code{merge-differently-headed} with an upstem eighth or a
1392 shorter note, and a downstem half note, the eighth note gets the wrong
1395 There is no support for clusters where the same note occurs with
1396 different accidentals in the same chord. In this case, it is
1397 recommended to use enharmonic transcription, or to use special cluster
1398 notation (see @ref{Clusters}).
1403 Beams are used to group short notes into chunks that are aligned with
1404 the metrum. They are inserted automatically
1407 @lilypond[fragment,verbatim,relative=3]
1408 \time 2/4 c8 c c c \time 6/8 c c c c8. c16 c8
1412 When these automatic decisions are not good enough, beaming can be
1413 entered explicitly. It is also possible to define beaming patterns
1414 that differ from the defaults.
1416 Individual notes may be marked with @code{\noBeam}, to prevent them
1420 @lilypond[fragment,verbatim,relative=3]
1421 \time 2/4 c8 c\noBeam c c
1428 Program reference: @internalsref{Beam}.
1431 @cindex Automatic beams
1434 * Setting automatic beam behavior::
1438 @subsection Manual beams
1439 @cindex beams, manual
1443 In some cases it may be necessary to override the automatic beaming
1444 algorithm. For example, the autobeamer will not put beams over rests
1445 or bar lines. Such beams are specified by manually: the begin and end
1446 point are marked with @code{[} and @code{]}
1449 @lilypond[fragment,relative=1,verbatim]
1451 r4 r8[ g' a r8] r8 g[ | a] r8
1456 @cindex @code{stemLeftBeamCount}
1458 Normally, beaming patterns within a beam are determined automatically.
1459 If necessary, the properties @code{stemLeftBeamCount} and
1460 @code{stemRightBeamCount} can be used to override the defaults. If
1461 either property is set, its value will be used only once, and then it
1465 @lilypond[fragment,relative=1,verbatim]
1468 f8[ r16 \set stemLeftBeamCount = #1 f g a]
1472 @cindex @code{stemRightBeamCount}
1475 The property @code{subdivideBeams} can be set in order to subdivide
1476 all 16th or shorter beams at beat positions, as defined by the
1477 @code{beatLength} property.
1481 @lilypond[relative=2,verbatim,noindent]
1483 \set subdivideBeams = ##t
1485 \set Score.beatLength = #(ly:make-moment 1 8)
1489 @cindex subdivideBeams
1491 Kneed beams are inserted automatically, when a large gap is detected
1492 between the note heads. This behavior can be tuned through the object
1493 property @code{auto-knee-gap}.
1495 Normally, line breaks are forbidden when beams cross bar lines. This
1496 behavior can be changed by setting @code{allowBeamBreak}.
1498 @cindex @code{allowBeamBreak}
1499 @cindex beams and line breaks
1501 @cindex beams, kneed
1503 @cindex auto-knee-gap
1509 @cindex Frenched staves
1511 Automatically kneed cross-staff beams cannot be used together with
1517 @node Setting automatic beam behavior
1518 @subsection Setting automatic beam behavior
1520 @cindex @code{autoBeamSettings}
1521 @cindex @code{(end * * * *)}
1522 @cindex @code{(begin * * * *)}
1523 @cindex automatic beams, tuning
1524 @cindex tuning automatic beaming
1526 @c [TODO: use \applycontext]
1528 In normal time signatures, automatic beams can start on any note but can
1529 only end in a few positions within the measure: beams can end on a beat,
1530 or at durations specified by the properties in
1531 @code{autoBeamSettings}. The defaults for @code{autoBeamSettings}
1532 are defined in @file{scm/auto-beam.scm}.
1534 The value of @code{autoBeamSettings} is changed with two functions,
1536 #(override-auto-beam-setting
1537 '(@var{be} @var{p} @var{q} @var{n} @var{m}) @var{a} @var{b}
1539 #(revert-auto-beam-setting '(@var{be} @var{p} @var{q} @var{n} @var{m}))
1541 Here, @var{be} is the symbol @code{begin} or @code{end}, and
1542 @var{context} is an optional context (default: @code{'Voice}). It
1543 determines whether the rule applies to begin or end-points. The
1544 quantity @var{p}/@var{q} refers to the length of the beamed notes (and
1545 `@code{* *}' designates notes of any length), @var{n}/@var{M} refers
1546 to a time signature (wildcards `@code{* *}' may be entered to
1547 designate all time signatures), @var{a}/@var{b} is a duration. By
1548 default, this command changes settings for the current voice. It is
1549 also possible to adjust settings at higher contexts, by adding a
1550 @var{context} argument.
1552 For example, if automatic beams should end on every quarter note, use
1555 #(override-auto-beam-setting '(end * * * *) 1 4 'Staff)
1557 Since the duration of a quarter note is 1/4 of a whole note, it is
1558 entered as @code{(ly:make-moment 1 4)}.
1560 The same syntax can be used to specify beam starting points. In this
1561 example, automatic beams can only end on a dotted quarter note
1563 #(override-auto-beam-setting '(end * * * *) 3 8)
1565 In 4/4 time signature, this means that automatic beams could end only on
1566 3/8 and on the fourth beat of the measure (after 3/4, that is 2 times
1567 3/8, has passed within the measure).
1569 Rules can also be restricted to specific time signatures. A rule that
1570 should only be applied in @var{N}/@var{M} time signature is formed by
1571 replacing the second asterisks by @var{N} and @var{M}. For example, a
1572 rule for 6/8 time exclusively looks like
1574 #(override-auto-beam-setting '(begin * * 6 8) @dots{})
1577 If a rule should be to applied only to certain types of beams, use the
1578 first pair of asterisks. Beams are classified according to the
1579 shortest note they contain. For a beam ending rule that only applies
1580 to beams with 32nd notes (and no shorter notes), use @code{(end 1 32 *
1583 @cindex automatic beam generation
1585 @cindex @code{autoBeaming}
1588 If beams are used to indicate melismata in songs, then automatic
1589 beaming should be switched off. This is done by setting
1590 @code{autoBeaming} to @code{#f}.
1594 @cindex @code{\autoBeamOff}
1595 @code{\autoBeamOff},
1596 @cindex @code{\autoBeamOn}
1602 If a score ends while an automatic beam has not been ended and is
1603 still accepting notes, this last beam will not be typeset at all. The
1604 same holds polyphonic voices, entered with @code{<< @dots{} \\ @dots{}
1605 >>}. If a polyphonic voice ends while an automatic beam is still
1606 accepting notes, it is not typeset.
1608 The rules for ending a beam depend on the shortest note in a beam.
1609 So, while it is possible to have different ending rules for eight
1610 beams and sixteenth beams, a beam that contains both eight and
1611 sixteenth notes will use the rules for the sixteenth beam.
1613 In the example below, the autobeamer makes eight beams and sixteenth
1614 end at 3 eights; the third beam can only be corrected by specifying
1618 @lilypond[raggedright,fragment,relative=1]
1619 #(override-auto-beam-setting '(end * * * *) 3 8)
1620 % rather show case where it goes wrong
1621 %\time 12/8 c'8 c c c16 c c c c c c[ c c c] c8[ c] c4
1622 \time 12/8 c'8 c c c16 c c c c c c c c c c8 c c4
1625 It is not possible to specify beaming parameters that act differently in
1626 different parts of a measure. This means that it is not possible to use
1627 automatic beaming in irregular meters such as @code{5/8}.
1630 @section Accidentals
1633 This section describes how to change the way that accidentals are
1634 inserted automatically before the running notes.
1636 Common rules for typesetting accidentals have been canned in a
1637 function. This function is called as follows
1639 @cindex @code{set-accidental-style}
1641 #(set-accidental-style 'modern 'Voice)
1644 The function takes two arguments: a symbol that denotes the style (in
1645 the example, @code{modern}), and another symbol that denotes the
1646 context name (in this example, @code{Voice}). If no context name is
1647 supplied, @code{Staff} is the default.
1649 The following styles are supported
1652 This is the default typesetting behavior. It should correspond
1653 to 18th century common practice: Accidentals are
1654 remembered to the end of the measure in which they occur and
1655 only on their own octave.
1659 The normal behavior is to remember the accidentals on
1660 Staff-level. This variable, however, typesets accidentals
1661 individually for each voice. Apart from that, the rule is similar to
1664 This leads to some weird and often unwanted results
1665 because accidentals from one voice do not get canceled in other
1668 @lilypond[raggedright,relative=1,fragment,verbatim]
1670 #(set-accidental-style 'voice)
1677 Hence you should only use @code{voice} if the voices
1678 are to be read solely by individual musicians. If the staff is to be
1679 used by one musician (e.g. a conductor) then you use
1680 @code{modern} or @code{modern-cautionary}
1684 @cindex @code{modern} style accidentals
1685 This rule corresponds to the common practice in the 20th
1687 This rule prints the same accidentals as @code{default}, but temporary
1688 accidentals also are canceled in other octaves. Furthermore,
1689 in the same octave, they also get canceled in the following
1693 @lilypond[raggedright,fragment,verbatim]
1694 #(set-accidental-style 'modern)
1695 cis' c'' cis'2 | c'' c'
1699 @item @code{modern-cautionary}
1700 @cindex @code{modern-cautionary}
1701 This rule is similar to @code{modern}, but the
1702 ``extra'' accidentals (the ones not typeset by
1703 @code{default}) are typeset as cautionary accidentals.
1704 They are printed in reduced size or with parentheses
1706 @lilypond[raggedright,fragment,verbatim]
1707 #(set-accidental-style 'modern-cautionary)
1708 cis' c'' cis'2 | c'' c'
1712 @cindex @code{modern-voice}
1714 This rule is used for multivoice accidentals to be read both by musicians
1715 playing one voice and musicians playing all voices. Accidentals are
1716 typeset for each voice, but they @emph{are} canceled across voices in
1717 the same @internalsref{Staff}.
1719 @cindex @code{modern-voice-cautionary}
1720 @item modern-voice-cautionary
1721 This rule is the same as @code{modern-voice}, but with the extra
1722 accidentals (the ones not typeset by @code{voice}) typeset
1723 as cautionaries. Even though all accidentals typeset by
1724 @code{default} @emph{are} typeset by this variable then
1725 some of them are typeset as cautionaries.
1728 @cindex @code{piano} accidentals
1729 This rule reflects 20th century practice for piano notation. Very similar to
1730 @code{modern} but accidentals also get canceled
1731 across the staves in the same @internalsref{GrandStaff} or
1732 @internalsref{PianoStaff}.
1734 @item piano-cautionary
1735 @cindex @code{#(set-accidental-style 'piano-cautionary)}
1736 As @code{#(set-accidental-style 'piano)' , str)} but with the extra accidentals
1737 typeset as cautionaries.
1740 @cindex @code{no-reset} accidental style
1742 This is the same as @code{default} but with accidentals lasting
1743 ``forever'' and not only until the next measure
1745 @lilypond[raggedright,fragment,verbatim,relative=1]
1746 #(set-accidental-style 'no-reset)
1752 This is sort of the opposite of @code{no-reset}: Accidentals
1753 are not remembered at all---and hence all accidentals are
1754 typeset relative to the key signature, regardless of what was
1758 @lilypond[raggedright,fragment,verbatim,relative=1]
1759 #(set-accidental-style 'forget)
1760 \key d\major c4 c cis cis d d dis dis
1768 Program reference: @internalsref{Accidental_engraver},
1769 @internalsref{Accidental}, and @internalsref{AccidentalPlacement}.
1774 Simultaneous notes are considered to be entered in sequential
1775 mode. This means that in a chord the accidentals are typeset as if the
1776 notes in the chord happened once at a time - in the order in which
1777 they appear in the input file.
1779 This is only a problem when accidentals in a chord depend on each
1780 other. This problem can be solved by manually inserting @code{!} and
1781 @code{?} for the problematic notes.
1783 In the default scheme, accidentals only depend on other
1784 accidentals with the same pitch on the same staff, so no conflicts are
1787 @node Expressive marks
1788 @section Expressive marks
1791 @c todo: should change ordering
1792 @c where to put text spanners, metronome marks,
1801 * Analysis brackets::
1803 * Fingering instructions::
1814 A slur indicates that notes are to be played bound or @emph{legato}.
1817 They are entered using parentheses
1819 @lilypond[relative=2,fragment,verbatim]
1820 f( g)( a) a8 b( a4 g2 f4)
1826 @c TODO: should explain that ^( and _( set directions
1827 @c should set attachments with ^ and _ ?
1829 Slurs avoid crossing stems, and are generally attached to note heads.
1830 However, in some situations with beams, slurs may be attached to stem
1831 ends. If you want to override this layout you can do this through the
1832 object property @code{attachment} of @internalsref{Slur}. Its value
1833 is a pair of symbols, specifying the attachment type of the left and
1837 @lilypond[fragment,relative=1,verbatim]
1839 \override Stem #'length = #5.5
1841 \override Slur #'attachment = #'(stem . stem)
1846 If a slur would strike through a stem or beam, the slur will be moved
1847 away upward or downward. If this happens, attaching the slur to the
1848 stems might look better
1851 @lilypond[fragment,relative=1,verbatim]
1854 \override Slur #'attachment = #'(stem . stem)
1862 @cindex @code{\slurUp}
1864 @cindex @code{\slurDown}
1866 @cindex @code{\slurBoth}
1868 @cindex @code{\slurDotted}
1870 @cindex @code{\slurSolid}
1875 Program reference: @seeinternals{Slur}, and @internalsref{SlurEvent}.
1880 Producing nice slurs is a difficult problem, and LilyPond
1881 uses a simple, empiric method to produce slurs. In some cases, its
1885 @cindex Adjusting slurs
1887 @node Phrasing slurs
1888 @subsection Phrasing slurs
1890 @cindex phrasing slurs
1891 @cindex phrasing marks
1893 A phrasing slur (or phrasing mark) connects chords and is used to
1894 indicate a musical sentence. It is started using @code{\(} and @code{\)}
1898 @lilypond[fragment,verbatim,relative=1]
1899 \time 6/4 c'\( d( e) f( e) d\)
1903 Typographically, the phrasing slur behaves almost exactly like a
1904 normal slur. However, they are treated as different objects. A
1905 @code{\slurUp} will have no effect on a phrasing slur; instead, you
1906 should use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
1907 @code{\phrasingSlurBoth}.
1909 The commands @code{\slurUp}, @code{\slurDown}, and @code{\slurBoth}
1910 will only affect normal slurs and not phrasing slurs.
1914 @cindex @code{\phrasingSlurUp}
1915 @code{\phrasingSlurUp},
1916 @cindex @code{\phrasingSlurDown}
1917 @code{\phrasingSlurDown},
1918 @cindex @code{\phrasingSlurBoth}
1919 @code{\phrasingSlurBoth}.
1923 Program reference: see also @internalsref{PhrasingSlur}, and
1924 @internalsref{PhrasingSlurEvent}.
1928 Phrasing slurs have the same limitations in their formatting as normal
1929 slurs. Putting phrasing slurs over rests leads to spurious warnings.
1932 @subsection Breath marks
1934 Breath marks are entered using @code{\breathe}
1938 @lilypond[fragment,relative=1,verbatim]
1943 The glyph of the breath mark can be tuned by overriding the
1944 @code{text} property of the @code{BreathingSign} layout object with
1945 any markup text. For example,
1947 @lilypond[fragment,verbatim,relative=1]
1949 \override BreathingSign #'text
1950 = #(make-musicglyph-markup "scripts-rvarcomma")
1958 Program reference: @internalsref{BreathingSign},
1959 @internalsref{BreathingSignEvent}.
1961 Examples: @inputfileref{input/regression,breathing-sign.ly}.
1964 @node Metronome marks
1965 @subsection Metronome marks
1968 @cindex beats per minute
1969 @cindex metronome marking
1971 Metronome settings can be entered as follows
1973 \tempo @var{duration} = @var{per-minute}
1976 In the MIDI output, they are interpreted as a tempo change, and in the
1977 paper output, a metronome marking is printed
1978 @cindex @code{\tempo}
1980 @lilypond[fragment,verbatim]
1987 Program reference: @internalsref{MetronomeChangeEvent}.
1992 @subsection Text spanners
1993 @cindex Text spanners
1995 Some performance indications, e.g. @i{rallentando} or @i{accelerando},
1996 are written as texts, and extended over many measures with dotted
1997 lines. You can create such texts using text spanners: attach
1998 @code{\startTextSpan} and @code{\stopTextSpan} to the
1999 start and ending note of the spanner.
2001 The string to be printed, as well as the style, is set through object
2005 @lilypond[fragment,relative=1,verbatim]
2008 \override TextSpanner #'direction = #-1
2009 \override TextSpanner #'edge-text = #'("rall " . "")
2010 c2\startTextSpan b c\stopTextSpan a
2018 Internals @internalsref{TextSpanEvent},
2019 @internalsref{TextSpanner}.
2021 Examples: @inputfileref{input/regression,text-spanner.ly}.
2024 @node Analysis brackets
2025 @subsection Analysis brackets
2027 @cindex phrasing brackets
2028 @cindex musicological analysis
2029 @cindex note grouping bracket
2031 Brackets are used in musical analysis to indicate structure in musical
2032 pieces. LilyPond supports a simple form of nested horizontal brackets.
2033 To use this, add the @internalsref{Horizontal_bracket_engraver} to
2034 @internalsref{Staff} context. A bracket is started with
2035 @code{\startGroup} and closed with @code{\stopGroup}
2038 @lilypond[raggedright,verbatim]
2040 \notes \relative c'' {
2041 c4\startGroup\startGroup
2044 c4\stopGroup\stopGroup
2048 \StaffContext \consists "Horizontal_bracket_engraver"
2055 Program reference: @internalsref{HorizontalBracket},
2056 @internalsref{NoteGroupingEvent}.
2058 Examples: @inputfileref{input/regression,note-group-bracket.ly}.
2062 @subsection Articulations
2063 @cindex Articulations
2065 @cindex articulations
2069 A variety of symbols can appear above and below notes to indicate
2070 different characteristics of the performance. They are added to a note
2071 by adding a dash and the character signifying the
2072 articulation. They are demonstrated here
2075 @lilypondfile[]{script-abbreviations.ly}
2078 The meanings of these shorthands can be changed. See
2079 @file{ly/script-init.ly} for examples.
2082 The script is automatically placed, but if you need to force
2083 directions, you can use @code{_} to force them down, or @code{^} to
2086 @lilypond[fragment,verbatim]
2091 Other symbols can be added using the syntax
2092 @var{note}@code{\}@var{name}, e.g. @code{c4\fermata}. Again, they
2093 can be forced up or down using @code{^} and @code{_},
2097 @lilypond[verbatim,fragment,relative=3]
2098 c\fermata c^\fermata c_\fermata
2106 @cindex staccatissimo
2115 @cindex organ pedal marks
2124 @cindex prallmordent
2128 @cindex thumb marking
2134 @lilypondfile[]{script-chart.ly}
2139 @cindex @code{\scriptUp}
2141 @cindex @code{\scriptDown}
2143 @cindex @code{\scriptBoth}
2148 Program reference: @internalsref{ScriptEvent}, and @internalsref{Script}.
2152 These note ornaments appear in the printed output but have no
2153 effect on the MIDI rendering of the music.
2156 @node Fingering instructions
2157 @subsection Fingering instructions
2161 Fingering instructions can be entered using
2163 @var{note}-@var{digit}
2165 For finger changes, use markup texts
2168 @lilypond[verbatim,raggedright,fragment]
2169 c'4-1 c'4-2 c'4-3 c'4-4
2170 c'^\markup { \finger "2-3" }
2174 @cindex finger change
2179 You can use the thumb-script to indicate that a note should be
2180 played with the thumb (e.g. in cello music)
2183 @lilypond[verbatim,raggedright,fragment]
2184 <a' a''-3>8_\thumb <b' b''-3>_\thumb
2188 Fingerings for chords can also be added to individual notes
2189 of the chord by adding them after the pitches
2191 @lilypond[verbatim,raggedright,fragment,relative=2]
2192 < c-1 e-2 g-3 b-5 >4
2197 In this case, setting @code{fingeringOrientations} will put fingerings next
2201 @lilypond[verbatim,raggedright,fragment,relative=2]
2202 \set fingeringOrientations = #'(left down)
2203 <c-1 es-2 g-4 bes-5 > 4
2204 \set fingeringOrientations = #'(up right down)
2205 <c-1 es-2 g-4 bes-5 > 4
2206 \set fingeringOrientations = #'(right)
2211 The last note demonstrates how fingering instructions can be put close
2212 to note heads in monophonic music, using this feature.
2216 Program reference: @internalsref{FingerEvent}, and @internalsref{Fingering}.
2218 Examples: @inputfileref{input/regression,finger-chords.ly}.
2221 @subsection Text scripts
2222 @cindex Text scripts
2224 @cindex text items, non-empty
2225 @cindex non-empty texts
2227 It is possible to place arbitrary strings of text or markup text (see
2228 @ref{Text markup}) above or below notes by using a string
2229 @code{c^"text"}. By default, these indications do not influence the
2230 note spacing, but by using the command @code{\fatText}, the widths
2231 will be taken into account
2234 @lilypond[fragment,raggedright,verbatim]
2236 c4^"longtext" \fatText c4_"longlongtext" c4
2241 It is possible to use @TeX{} commands in the strings, but this should
2242 be avoided because the exact dimensions of the string can then no
2247 @cindex @code{\fatText}
2249 @cindex @code{\emptyText}
2254 In this manual: @ref{Text markup}.
2256 Program reference: @internalsref{TextScriptEvent}, @internalsref{TextScript}.
2262 @subsection Grace notes
2265 @c should have blurb about accaciatura / appogiatura
2267 @cindex @code{\grace}
2271 Grace notes are ornaments that are written out. The most common ones
2272 are acciaccatura, which should be played as very short. It is denoted
2273 by a slurred small note with a slashed stem. The appoggiatura is a
2274 grace note that takes a fixed fraction of the main note, is and
2275 denoted as a slurred note in small print without a slash.
2276 They are entered with the commands @code{\acciaccatura} and
2277 @code{\appoggiatura}, as demonstrated in the following example
2280 @cindex appoggiatura
2281 @cindex acciaccatura
2284 @lilypond[relative=3,verbatim,fragment]
2285 b4 \acciaccatura d8 c4 \appoggiatura e8 d4
2286 \acciaccatura { g16[ f] } e4
2290 Both are special forms of the @code{\grace} command. By prefixing this
2291 keyword to a music expression, a new one is formed, which will be
2292 printed in a smaller font and takes up no logical time in a measure.
2294 @lilypond[relative=3,verbatim,fragment]
2296 \grace { c16[ d16] } c2 c4
2301 Unlike @code{\acciaccatura} and @code{\appoggiatura}, the
2302 @code{\grace} command does not start a slur.
2304 Internally, timing for grace notes is done using a second, `grace'
2305 time. Every point in time consists of two rational numbers: one
2306 denotes the logical time, one denotes the grace timing. The above
2307 example is shown here with timing tuples
2310 @lilypond[raggedright]
2313 c4 \grace c16 c4 \grace {
2316 \new Lyrics \lyrics {
2319 ( \fraction 1 4 , \fraction -1 16 ) } 16 }
2320 \markup { (\fraction 1 4 , 0 ) } 4
2322 \markup { (\fraction 2 4 , \fraction "-1" 8 ) } 16
2323 \markup { (\fraction 2 4 , \fraction "-1" 16 ) } 16
2325 \markup { ( \fraction 2 4 , 0 ) }
2332 The placement of grace notes is synchronized between different staves.
2333 In the following example, there are two sixteenth graces notes for
2334 every eighth grace note
2337 @lilypond[relative=3,verbatim,fragment]
2338 << \new Staff { e4 \grace { c16[ d e f] } e4 }
2339 \new Staff { c'4 \grace { g8[ b] } c4 } >>
2345 If you want to end a note with a grace, the standard trick is to put
2346 the grace notes after a ``space note''
2349 @lilypond[fragment,verbatim,relative=3]
2352 { s2 \grace { c16[ d] } } >>
2359 By adjusting the duration of the skip note (here it is a half-note),
2360 the space between the main-note and the grace is adjusted.
2363 A @code{\grace} section will introduce special typesetting settings,
2364 for example, to produce smaller type, and set directions. Hence, when
2365 introducing layout tweaks, they should be inside the grace section,
2368 @lilypond[fragment,verbatim,relative=2]
2371 \override Stem #'direction = #-1
2373 \revert Stem #'direction
2381 The overrides should also be reverted inside the grace section.
2383 If the layout of grace sections must be changed throughout the music,
2384 then this can be accomplished through the function
2385 @code{add-grace-property}. The following example undefines the Stem
2386 direction for this grace, so stems do not always point up.
2390 #(add-grace-property "Voice" Stem direction '())
2396 Another option is to change the variables @code{startGraceMusic},
2397 @code{stopGraceMusic}, @code{startAccacciaturaMusic},
2398 @code{stopAccacciaturaMusic}, @code{startAppoggiaturaMusic},
2399 @code{stopAppoggiaturaMusic}. More information is in the file
2400 @file{ly/grace-init.ly}.
2405 Program reference: @internalsref{GraceMusic}.
2409 A score that starts with an @code{\grace} section needs an explicit
2410 @code{\context Voice} declaration, otherwise the main note and grace
2411 note end up on different staves.
2413 Grace note synchronization can also lead to surprises. Staff notation,
2414 such as key signatures, bar lines, etc. are also synchronized. Take
2415 care when you mix staves with grace notes and staves without, for example,
2418 @lilypond[relative=3,verbatim,fragment]
2419 << \new Staff { e4 \bar "|:" \grace c16 d4 }
2420 \new Staff { c4 \bar "|:" d4 } >>
2425 This can be remedied by inserting grace skips, for the above example
2428 \new Staff @{ c4 \bar "|:" \grace s16 d4 @} >>
2431 Grace sections should only be used within sequential music
2432 expressions. Nesting or juxtaposing grace sections is not supported,
2433 and might produce crashes or other errors.
2437 @subsection Glissando
2440 @cindex @code{\glissando}
2442 A glissando is a smooth change in pitch. It is denoted by a line or a
2443 wavy line between two notes.
2446 A glissando line can be requested by attaching a @code{\glissando} to
2450 @lilypond[fragment,relative=1,verbatim]
2457 Program reference: @internalsref{Glissando}, and @internalsref{GlissandoEvent}.
2459 Example files: @file{input/regression,glissando.ly}
2465 Printing text over the line (such as @emph{gliss.}) is not supported.
2469 @subsection Dynamics
2482 @cindex @code{\ffff}
2492 Absolute dynamic marks are specified using a command after a note
2493 @code{c4\ff}. The available dynamic marks are @code{\ppp},
2494 @code{\pp}, @code{\p}, @code{\mp}, @code{\mf}, @code{\f}, @code{\ff},
2495 @code{\fff}, @code{\fff}, @code{\fp}, @code{\sf}, @code{\sff},
2496 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}
2499 @lilypond[verbatim,raggedright,fragment,relative=1]
2500 c'\ppp c\pp c \p c\mp c\mf c\f c\ff c\fff
2511 A crescendo mark is started with @code{\<} and terminated with
2512 @code{\!}. A decrescendo is started with @code{\>} and also terminated
2513 with @code{\!}. Because these marks are bound to notes, if you must
2514 use spacer notes if multiple marks during one note are needed
2517 @lilypond[fragment,verbatim]
2518 c''\< c''\! d''\> e''\!
2519 << f''1 { s4 s4\< s4\! \> s4\! } >>
2522 This may give rise to very short hairpins. Use @code{minimum-length}
2523 in @internalsref{Voice}.@internalsref{Hairpin} to lengthen them, for
2527 \override Staff.Hairpin #'minimum-length = #5
2530 You can also use a text saying @emph{cresc.} instead of hairpins. Here
2531 is an example how to do it
2534 @lilypond[fragment,relative=3,verbatim]
2545 You can also supply your own texts
2547 @lilypond[fragment,relative=1,verbatim]
2549 \set crescendoText = \markup { \italic "cresc. poco" }
2550 \set crescendoSpanner = #'dashed-line
2561 @cindex @code{\dynamicUp}
2563 @cindex @code{\dynamicDown}
2564 @code{\dynamicDown},
2565 @cindex @code{\dynamicBoth}
2566 @code{\dynamicBoth}.
2568 @cindex direction, of dynamics
2572 Program reference: @internalsref{CrescendoEvent},
2573 @internalsref{DecrescendoEvent}, and
2574 @internalsref{AbsoluteDynamicEvent}.
2576 Dynamics @internalsref{DynamicText} and @internalsref{Hairpin}
2577 objects. Vertical positioning of these symbols is handled by the
2578 @internalsref{DynamicLineSpanner} object.
2586 @cindex @code{\repeat}
2589 Repetition is a central concept in music, and multiple notations exist
2590 for repetitions. In LilyPond, most of these notations can be captured
2591 in a uniform syntax. One of the advantages is that they can be
2592 rendered in MIDI accurately.
2594 The following types of repetition are supported
2598 Repeated music is fully written (played) out. Useful for MIDI
2599 output, and entering repetitive music.
2602 This is the normal notation: Repeats are not written out, but
2603 alternative endings (volte) are printed, left to right.
2607 Alternative endings are written stacked. This has limited use but may be
2608 used to typeset two lines of lyrics in songs with repeats, see
2609 @inputfileref{input,star-spangled-banner.ly}.
2617 Make beat or measure repeats. These look like percent signs.
2623 * Repeats and MIDI::
2624 * Manual repeat commands::
2626 * Tremolo subdivisions::
2631 @subsection Repeat syntax
2634 LilyPond has one syntactic construct for specifying different types of
2635 repeats. The syntax is
2638 \repeat @var{variant} @var{repeatcount} @var{repeatbody}
2641 If you have alternative endings, you may add
2642 @cindex @code{\alternative}
2644 \alternative @code{@{} @var{alternative1}
2646 @var{alternative3} @dots{} @code{@}}
2648 where each @var{alternative} is a music expression. If you do not
2649 give enough alternatives for all of the repeats, the first alternative
2650 is assumed to be played more than once.
2652 Normal notation repeats are used like this
2654 @lilypond[fragment,verbatim,relative=2]
2656 \repeat volta 2 { c4 d e f }
2657 \repeat volta 2 { f e d c }
2661 With alternative endings
2663 @lilypond[fragment,verbatim,relative=2]
2665 \repeat volta 2 {c4 d e f}
2666 \alternative { {d2 d} {f f,} }
2672 @lilypond[fragment,verbatim,relative=2]
2675 \repeat volta 4 { e | c2 d2 | e2 f2 | }
2676 \alternative { { g4 g g } { a | a a a a | b2. } }
2683 A nested repeat like
2692 is ambiguous, since it is is not clear to which @code{\repeat} the
2693 @code{\alternative} belongs. This ambiguity is resolved by always
2694 having the @code{\alternative} belong to the inner @code{\repeat}.
2695 For clarity, it is advisable to use braces in such situations.
2698 @node Repeats and MIDI
2699 @subsection Repeats and MIDI
2701 @cindex expanding repeats
2703 For instructions on how to expand repeats for MIDI output, see the
2704 example file @inputfileref{input/test,unfold-all-repeats.ly}.
2709 Timing information is not remembered at the start of an alternative,
2710 so after a repeat timing information must be reset by hand, for
2711 example by setting @code{Score.measurePosition} or entering
2712 @code{\partial}. Similarly, slurs or ties are also not repeated.
2715 @node Manual repeat commands
2716 @subsection Manual repeat commands
2718 @cindex @code{repeatCommands}
2720 The property @code{repeatCommands} can be used to control the layout of
2721 repeats. Its value is a Scheme list of repeat commands, where each repeat
2725 @item the symbol @code{start-repeat},
2726 which prints a @code{|:} bar line,
2727 @item the symbol @code{end-repeat},
2728 which prints a @code{:|} bar line,
2729 @item the list @code{(volta @var{text})},
2730 which prints a volta bracket saying @var{text}: The text can be specified as
2731 a text string or as a markup text, see @ref{Text markup}. Do not
2732 forget to change the font, as the default number font does not contain
2733 alphabetic characters. Or,
2734 @item the list @code{(volta #f)}, which
2735 stops a running volta bracket
2739 @lilypond[verbatim,fragment,relative=3]
2741 \set Score.repeatCommands = #'((volta "93") end-repeat)
2743 \set Score.repeatCommands = #'((volta #f))
2751 Program reference: @internalsref{VoltaBracket}, @internalsref{RepeatedMusic},
2752 @internalsref{VoltaRepeatedMusic},
2753 @internalsref{UnfoldedRepeatedMusic}, and
2754 @internalsref{FoldedRepeatedMusic}.
2756 @node Tremolo repeats
2757 @subsection Tremolo repeats
2758 @cindex tremolo beams
2760 To place tremolo marks between notes, use @code{\repeat} with tremolo
2763 @lilypond[verbatim,raggedright]
2765 \context Voice \notes\relative c' {
2766 \repeat "tremolo" 8 { c16 d16 }
2767 \repeat "tremolo" 4 { c16 d16 }
2768 \repeat "tremolo" 2 { c16 d16 }
2774 Tremolo marks can also be put on a single note. In this case, the
2775 note should not be surrounded by braces.
2777 @lilypond[verbatim,raggedright]
2778 \repeat "tremolo" 4 c'16
2782 A similar mechanism is the tremolo subdivision, described in
2783 @ref{Tremolo subdivisions}.
2787 In this manual: @ref{Tremolo subdivisions}, @ref{Repeats}.
2789 Program reference: tremolo beams are @internalsref{Beam} objects. Single stem
2790 tremolos are @internalsref{StemTremolo} objects. The music expression is
2791 @internalsref{TremoloEvent}.
2793 Example files: @inputfileref{input/regression,chord-tremolo.ly},
2794 @inputfileref{input/regression,stem-tremolo.ly}.
2796 @node Tremolo subdivisions
2797 @subsection Tremolo subdivisions
2798 @cindex tremolo marks
2799 @cindex @code{tremoloFlags}
2801 Tremolo marks can be printed on a single note by adding
2802 `@code{:}[@var{length}]' after the note. The length must be at least
2803 8. A @var{length} value of 8 gives one line across the note stem. If
2804 the length is omitted, the last value (stored in @code{tremoloFlags})
2808 @lilypond[verbatim,fragment]
2809 c'2:8 c':32 | c': c': |
2813 @c [TODO : stok is te kort bij 32en]
2817 Tremolos entered in this way do not carry over into the MIDI output.
2821 In this manual: @ref{Tremolo repeats}.
2823 Elsewhere: @internalsref{StemTremolo}, @internalsref{TremoloEvent}.
2825 @node Measure repeats
2826 @subsection Measure repeats
2828 @cindex percent repeats
2829 @cindex measure repeats
2831 In the @code{percent} style, a note pattern can be repeated. It is
2832 printed once, and then the pattern is replaced with a special sign.
2833 Patterns of a one and two measures are replaced by percent-like signs,
2834 patterns that divide the measure length are replaced by slashes
2837 @lilypond[verbatim,raggedright]
2838 \context Voice { \repeat "percent" 4 { c'4 }
2839 \repeat "percent" 2 { c'2 es'2 f'4 fis'4 g'4 c''4 }
2846 Program reference: @internalsref{RepeatSlash}, @internalsref{PercentRepeat},
2847 @internalsref{PercentRepeatedMusic}, and
2848 @internalsref{DoublePercentRepeat}.
2852 @node Rhythmic music
2853 @section Rhythmic music
2857 * Showing melody rhythms::
2858 * Entering percussion::
2859 * Percussion staves::
2863 @node Showing melody rhythms
2864 @subsection Showing melody rhythms
2866 Sometimes you might want to show only the rhythm of a melody. This
2867 can be done with the rhythmic staff. All pitches of notes on such a
2868 staff are squashed, and the staff itself has a single line
2871 @lilypond[fragment,relative=1,verbatim]
2872 \context RhythmicStaff {
2874 c4 e8 f g2 | r4 g r2 | g1:32 | r1 |
2881 Program reference: @internalsref{RhythmicStaff}.
2883 Examples: @inputfileref{input/regression,rhythmic-staff.ly}.
2886 @node Entering percussion
2887 @subsection Entering percussion
2893 Percussion notes may be entered in @code{\drums} mode, which is
2894 similar to @code{notes}. Each piece of percussion has a full name and
2895 an abbreviated name, and both be used in input files
2898 hihat hh bassdrum bd
2901 @lilypond[raggedright]
2902 \new DrumStaff \drums { hihat hh bassdrum bd
2907 The complete list of drum names is in the init file
2908 @file{ly/drumpitch-init.ly}.
2909 @c TODO: properly document this.
2913 Program reference: @internalsref{DrumNoteEvent}.
2915 @node Percussion staves
2916 @subsection Percussion staves
2920 A percussion part for more than one instrument typically uses a
2921 multiline staff where each position in the staff refers to one piece
2925 To typeset the music, the notes must be interpreted in a
2926 @internalsref{DrumStaff} and @internalsref{DrumVoice} contexts
2930 @lilypond[raggedright,verbatim]
2931 up = \drums { crashcymbal4 hihat8 halfopenhihat hh hh hh openhihat }
2932 down = \drums { bassdrum4 snare8 bd r bd sn4 }
2935 << \new DrumVoice { \voiceOne \up }
2936 \new DrumVoice { \voiceTwo \down }
2941 The above example shows verbose polyphonic notation. The short
2942 polyphonic notation, described in @ref{Polyphony}, can also be used if
2943 the @internalsref{DrumVoices} are instantiated by hand first. For example,
2946 @lilypond[fragment,verbatim]
2947 \drums \new DrumStaff <<
2948 \context DrumVoice = "1" { s1 *2 }
2949 \context DrumVoice = "2" { s1 *2 }
2953 { \repeat unfold 16 hh16 }
2963 There are also other layout possibilities. To use these, set the
2964 property @code{drumStyleTable} in context @internalsref{DrumVoice}.
2965 The following variables have been predefined
2969 is the default. It typesets a typical drum kit on a five-line staff
2973 nam = \lyrics { cymc cyms cymr hh hhc hho hhho hhp cb hc
2974 bd sn ss tomh tommh tomml toml tomfh tomfl }
2975 mus = \drums { cymc cyms cymr hh | hhc hho hhho hhp | \break cb hc
2976 bd sn ss tomh tommh tomml toml tomfh tomfl s16 }
2978 << \new DrumStaff\with {
2979 \remove Bar_engraver
2980 \remove Time_signature_engraver
2981 \override Stem #'transparent = ##t
2982 \override Stem #'Y-extent-callback = ##f
2983 minimumVerticalExtent = #'(-4.0 . 5.0)
2985 \context Lyrics \nam
2988 %% need to do this, because of indented @itemize
2990 \context { \ScoreContext
2991 \override LyricText #'font-family = #'typewriter
2992 \override BarNumber #'transparent =##T
2997 The drum scheme supports six different toms. When there fewer toms, simply
2998 select the toms that produce the desired result, i.e. to get toms on
2999 the three middle lines you use @code{tommh}, @code{tomml} and
3002 @item timbales-style
3003 to typeset timbales on a two line staff
3006 @lilypond[raggedright]
3007 nam = \lyrics { timh ssh timl ssl cb }
3008 mus = \drums { timh ssh timl ssl cb s16 }
3011 \context DrumStaff \with {
3012 \remove Bar_engraver
3013 \remove Time_signature_engraver
3014 \override Stem #'transparent = ##t
3015 \override Stem #'Y-extent-callback = ##f
3016 \override StaffSymbol #'line-count = #2
3017 \override StaffSymbol #'staff-space = #2
3018 minimumVerticalExtent = #'(-3.0 . 4.0)
3019 drumStyleTable = #timbales-style
3022 \override LyricText #'font-family = #'typewriter
3030 to typeset congas on a two line staff
3033 @lilypond[raggedright]
3034 nam = \lyrics { cgh cgho cghm ssh cgl cglo cglm ssl }
3035 mus = \drums { cgh cgho cghm ssh cgl cglo cglm ssl s16 }
3038 \context DrumStaff\with {
3039 \remove Bar_engraver
3040 \remove Time_signature_engraver
3041 drumStyleTable = #congas-style
3042 \override StaffSymbol #'line-count = #2
3044 %% this sucks; it will lengthen stems.
3045 \override StaffSymbol #'staff-space = #2
3046 \override Stem #'transparent = ##t
3047 \override Stem #'Y-extent-callback = ##f
3050 \override LyricText #'font-family = #'typewriter
3057 to typeset bongos on a two line staff
3060 @lilypond[raggedright]
3061 nam = \lyrics { boh boho bohm ssh bol bolo bolm ssl }
3062 mus = \drums { boh boho bohm ssh bol bolo bolm ssl s16 }
3065 \context DrumStaff\with {
3066 \remove Bar_engraver
3067 \remove Time_signature_engraver
3068 \override StaffSymbol #'line-count = #2
3069 drumStyleTable = #bongos-style
3071 %% this sucks; it will lengthen stems.
3072 \override StaffSymbol #'staff-space = #2
3073 \override Stem #'transparent = ##t
3074 \override Stem #'Y-extent-callback = ##f
3077 \override LyricText #'font-family = #'typewriter
3084 @item percussion-style
3085 to typeset all kinds of simple percussion on one line staves
3087 @lilypond[raggedright]
3088 nam = \lyrics { tri trio trim gui guis guil cb cl tamb cab mar hc }
3089 mus = \drums { tri trio trim gui guis guil cb cl tamb cab mar hc s16 }
3092 \context DrumStaff\with{
3093 \remove Bar_engraver
3094 drumStyleTable = #percussion-style
3095 \override StaffSymbol #'line-count = #1
3096 \remove Time_signature_engraver
3097 \override Stem #'transparent = ##t
3098 \override Stem #'Y-extent-callback = ##f
3102 \override LyricText #'font-family = #'typewriter
3110 If you do not like any of the predefined lists you can define your own
3111 list at the top of your file
3114 @lilypond[raggedright,verbatim]
3116 (bassdrum default #f -1)
3117 (snare default #f 0)
3119 (pedalhihat xcircle "stopped" 2)
3120 (lowtom diamond #f 3)
3122 up = \drums { hh8 hh hh hh hhp4 hhp }
3123 down = \drums { bd4 sn bd toml8 toml }
3126 \set DrumStaff.drumStyleTable
3127 = #(alist->hash-table mydrums)
3128 \new DrumVoice { \voiceOne \up }
3129 \new DrumVoice { \voiceTwo \down }
3138 Init files: @file{ly/drumpitch-init.ly}.
3140 Program reference: @internalsref{DrumStaff}, @internalsref{DrumVoice}.
3144 Because general MIDI does not contain rim shots, the sidestick is used
3145 for this purpose instead.
3148 @section Piano music
3150 Piano staves are two normal staves coupled with a brace. The staves
3151 are largely independent, but sometimes voices can cross between the
3152 two staves. The same notation is also used for harps and other key
3153 instruments. The @internalsref{PianoStaff} is especially built to
3154 handle this cross-staffing behavior. In this section we discuss the
3155 @internalsref{PianoStaff} and some other pianistic peculiarities.
3159 * Automatic staff changes::
3160 * Manual staff switches::
3163 * Staff switch lines::
3168 There is no support for putting chords across staves. You can get
3169 this result by increasing the length of the stem in the lower stave so
3170 it reaches the stem in the upper stave, or vice versa. An example is
3171 included with the distribution as
3172 @inputfileref{input/test,stem-cross-staff.ly}.
3174 Dynamics are not centered, but kludges do exist. See
3175 @inputfileref{input/template,piano-dynamics.ly}.
3177 @cindex cross staff stem
3178 @cindex stem, cross staff
3179 @cindex distance between staves in piano music
3181 The distance between the two staves is normally fixed across the
3182 entire score. It is possible to tune this per system, but it does
3183 require arcane command incantations. See
3184 @inputfileref{input/test,piano-staff-distance.ly}.
3187 @node Automatic staff changes
3188 @subsection Automatic staff changes
3189 @cindex Automatic staff changes
3191 Voices can switch automatically between the top and the bottom
3192 staff. The syntax for this is
3194 \autochange \context Voice @{ @dots{}@var{music}@dots{} @}
3196 The two staves of the piano staff must be named @code{up} and
3199 The autochanger switches on basis of pitch (middle C is the turning
3200 point), and it looks ahead skipping over rests to switch in
3201 advance. Here is a practical example
3204 @lilypond[verbatim,raggedright]
3205 \score { \notes \context PianoStaff <<
3206 \context Staff = "up" {
3207 \autochange \new Voice \relative c' {
3208 g4 a b c d r4 a g } }
3209 \context Staff = "down" {
3217 In this example, spacer rests are used to prevent the bottom staff from
3218 terminating too soon.
3223 In this manual: @ref{Manual staff switches}.
3225 Program reference: @internalsref{AutoChangeMusic}.
3231 The staff switches often do not end up in optimal places. For high
3232 quality output, staff switches should be specified manually.
3236 @node Manual staff switches
3237 @subsection Manual staff switches
3239 @cindex manual staff switches
3240 @cindex staff switch, manual
3242 Voices can be switched between staves manually, using the following command
3244 \change Staff = @var{staffname} @var{music}
3248 The string @var{staffname} is the name of the staff. It switches the
3249 current voice from its current staff to the Staff called
3250 @var{staffname}. Typically @var{staffname} is @code{"up"} or
3259 Pianos have pedals that alter the way sound are produced. Generally, a
3260 piano has three pedals, sustain, una corda, and sostenuto.
3263 Piano pedal instruction can be expressed by attaching
3264 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
3265 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
3269 @lilypond[fragment,verbatim]
3270 c'4\sustainDown c'4\sustainUp
3274 What is printed can be modified by setting @code{pedal@var{X}Strings},
3275 where @var{X} is one of the pedal types: @code{Sustain},
3276 @code{Sostenuto} or @code{UnaCorda}. Refer to
3277 @internalsref{SustainPedal} in the program reference for more
3280 Pedals can also be indicated by a sequence of brackets, by setting the
3281 @code{pedalSustainStyle} property to @code{bracket} objects
3284 @lilypond[fragment,verbatim,relative=3]
3285 \set Staff.pedalSustainStyle = #'bracket
3287 b\sustainUp\sustainDown
3288 b g \sustainUp a \sustainDown \bar "|."
3292 A third style of pedal notation is a mixture of text and brackets,
3293 obtained by setting the @code{pedalSustainStyle} style property to
3297 @lilypond[fragment,verbatim,relative=3]
3298 \set Staff.pedalSustainStyle = #'mixed
3300 b\sustainUp\sustainDown
3301 b g \sustainUp a \sustainDown \bar "|."
3305 The default `*Ped.' style for sustain and damper pedals corresponds to
3306 style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
3310 @lilypond[fragment,verbatim,relative=3]
3311 c\sostenutoDown d e c, f g a\sostenutoUp
3315 For fine-tuning of the appearance of a pedal bracket, the properties
3316 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
3317 @code{PianoPedalBracket} objects (see
3318 @internalsref{PianoPedalBracket} in the Program reference) can be modified. For example, the
3319 bracket may be extended to the end of the note head
3322 @lilypond[fragment,verbatim]
3323 \override Staff.PianoPedalBracket
3324 #'shorten-pair = #'(0 . -1.0)
3325 c\sostenutoDown d e c, f g a\sostenutoUp
3330 @subsection Arpeggio
3333 @cindex broken arpeggio
3334 @cindex @code{\arpeggio}
3336 You can specify an arpeggio sign on a chord by attaching an
3337 @code{\arpeggio} to a chord
3341 @lilypond[fragment,relative=1,verbatim]
3346 When an arpeggio crosses staves, you attach an arpeggio to the chords
3347 in both staves, and set
3348 @internalsref{PianoStaff}.@code{connectArpeggios}
3351 @lilypond[fragment,relative=1,verbatim]
3352 \context PianoStaff <<
3353 \set PianoStaff.connectArpeggios = ##t
3354 \new Staff { <c' e g c>\arpeggio }
3355 \new Staff { \clef bass <c,, e g>\arpeggio }
3360 The direction of the arpeggio is sometimes denoted by adding an
3361 arrowhead to the wiggly line
3364 @lilypond[fragment,relative=1,verbatim]
3374 A square bracket on the left indicates that the player should not
3375 arpeggiate the chord
3378 @lilypond[fragment,relative=1,verbatim]
3386 @cindex @code{\arpeggio}
3388 @cindex @code{\arpeggioUp}
3390 @cindex @code{\arpeggioDown}
3392 @cindex @code{\arpeggioBoth}
3393 @code{\arpeggioBoth},
3394 @cindex @code{\arpeggioBracket}
3395 @code{\arpeggioBracket}.
3399 Program reference: @internalsref{ArpeggioEvent} music expressions lead to
3400 @internalsref{Arpeggio} objects. Cross staff arpeggios are
3401 @internalsref{PianoStaff}.@internalsref{Arpeggio}.
3405 It is not possible to mix connected arpeggios and unconnected
3406 arpeggios in one @internalsref{PianoStaff} at the same time.
3408 @node Staff switch lines
3409 @subsection Staff switch lines
3412 @cindex follow voice
3413 @cindex staff switching
3416 @cindex @code{followVoice}
3418 Whenever a voice switches to another staff a line connecting the notes
3419 can be printed automatically. This is enabled if the property
3420 @code{PianoStaff.followVoice} is set to true
3423 @lilypond[fragment,relative=1,verbatim]
3424 \context PianoStaff <<
3425 \set PianoStaff.followVoice = ##t
3426 \context Staff \context Voice {
3431 \context Staff=two { \clef bass \skip 1*2 }
3438 The associated object is @internalsref{VoiceFollower}.
3442 @cindex @code{\showStaffSwitch}
3443 @code{\showStaffSwitch},
3444 @cindex @code{\hideStaffSwitch}
3445 @code{\hideStaffSwitch}.
3449 @section Vocal music
3451 This section discusses how to enter and print lyrics.
3455 * The Lyrics context::
3460 @node Entering lyrics
3461 @subsection Entering lyrics
3465 @cindex @code{\lyrics}
3468 Lyrics are entered in a special input mode. This mode is is introduced
3469 by the keyword @code{\lyrics}. In this mode you can enter lyrics, with
3470 punctuation and accents without any hassle. Syllables are entered like
3471 notes, but with pitches replaced by text. For example,
3473 \lyrics @{ Twin-4 kle4 twin- kle litt- le star2 @}
3476 A word in Lyrics mode begins with: an alphabetic character, @code{_},
3477 @code{?}, @code{!}, @code{:}, @code{'}, the control characters @code{^A}
3478 through @code{^F}, @code{^Q} through @code{^W}, @code{^Y}, @code{^^},
3479 any 8-bit character with ASCII code over 127, or a two-character
3480 combination of a backslash followed by one of @code{`}, @code{'},
3481 @code{"}, or @code{^}.
3483 Subsequent characters of a word can be any character that is not a digit
3484 and not white space. One important consequence of this is that a word
3485 can end with @code{@}}. The following example is usually a bug. The
3486 syllable includes a @code{@}}, and hence the opening brace is not balanced
3488 \lyrics @{ twinkle@}
3491 @cindex @code{\property}, in @code{\lyrics}
3492 Similarly, a period following a alphabetic sequence, is included in
3493 the resulting string. As a consequence, spaces must be inserted around
3496 \override Score . LyricText #'font-shape = #'italic
3500 @cindex spaces, in lyrics
3501 @cindex quotes, in lyrics
3503 Any @code{_} character which appears in an unquoted word is converted
3504 to a space. This provides a mechanism for introducing spaces into words
3505 without using quotes. Quoted words can also be used in Lyrics mode to
3506 specify words that cannot be written with the above rules
3509 \lyrics @{ He said: "\"Let" my peo ple "go\"" @}
3511 However, at least for english texts, you should use
3513 \lyrics @{ He said: ``Let my peo ple go'' @}
3515 to get the correct shape of the starting and ending quote.
3519 Centered hyphens are entered as `@code{-}@code{-}' between syllables.
3520 The hyphen will have variable length depending on the space between
3521 the syllables and it will be centered between the syllables.
3526 When a lyric is sung over many notes (this is called a melisma), this is
3527 indicated with a horizontal line centered between a syllable and the
3528 next one. Such a line is called an extender line, and it is entered as
3533 Program reference: events @internalsref{LyricEvent},
3534 @internalsref{HyphenEvent}, and @internalsref{ExtenderEvent}. Objects
3535 @internalsref{LyricHyphen}, @internalsref{LyricExtender} and
3536 @internalsref{LyricText}.
3538 Examples: @inputfileref{input/test,lyric-hyphen-retain.ly}.
3542 The definition of lyrics mode is too complex.
3546 @node The Lyrics context
3547 @subsection The Lyrics context
3549 Lyrics are printed by interpreting them in a @internalsref{Lyrics} context
3551 \context Lyrics \lyrics @dots{}
3554 @cindex automatic syllable durations
3555 @cindex @code{\lyricsto}
3556 @cindex lyrics and melodies
3558 This will place the lyrics according to the durations that were
3559 entered. The lyrics can also be aligned under a given melody
3560 automatically. In this case, it is no longer necessary to enter the
3561 correct duration for each syllable. This is achieved by combining the
3562 melody and the lyrics with the @code{\lyricsto} expression
3564 \lyricsto @var{name} \new Lyrics @dots{}
3567 This aligns the lyrics to the
3569 notes of the @internalsref{Voice} context called @var{name}, which has
3570 to exist. Therefore, normally the @code{Voice} is specified first, and
3571 then the lyrics are specified with @code{\lyricsto}.
3573 For different or more complex orderings, the best way is to setup the
3574 hierarchy of staves and lyrics first, e.g.
3576 \context ChoirStaff \notes <<
3577 \context Lyrics = sopranoLyrics @{ s1 @}
3578 \context Voice = soprano @{ @emph{music} @}
3579 \context Lyrics = tenorLyrics @{ s1 @}
3580 \context Voice = tenor @{ @emph{music} @}
3583 and then combine the appropriate melodies and lyric lines
3585 \lyricsto "soprano" \context Lyrics = sopranoLyrics
3590 The final input would resemble
3593 << \context ChoirStaff \notes << @emph{setup the music} >>
3594 \lyricsto "soprano" @emph{etc}
3595 \lyricsto "alto" @emph{etc}
3601 The @code{\lyricsto} command detects melismata: it only puts one
3602 syllable under a tied or slurred group of notes. If you want to force
3603 an unslurred group of notes to be a melisma, insert @code{\melisma}
3604 after the first note of the group, and @code{\melismaEnd} after the
3608 @lilypond[relative=2,raggedright,fragment,verbatim]
3609 << \context Voice = "lala" { \time 3/4
3615 \lyricsto "lala" \new Lyrics \lyrics {
3621 In addition, notes are considered a melisma if they are manually
3622 beamed, and automatic beaming (see @ref{Setting automatic beam
3623 behavior}) is switched off. The criteria for deciding melismata can
3624 be tuned with the property @code{melismaBusyProperties}. See
3625 @internalsref{Melisma_translator} in the program reference for more
3628 When multiple stanzas are put on the same melody, it can happen that
3629 two stanzas have melismata in different locations. This can be
3630 remedied by switching off melismata for one
3631 @internalsref{Lyrics}. This is achieved by setting
3632 the @code{ignoreMelismata} property to @code{#t}. An example is shown
3633 in @inputfileref{input/regression,lyric-combine-new.ly}.
3636 @cindex choral score
3638 A complete example of a SATB score setup is in the file
3639 @inputfileref{input/template,satb.ly}.
3644 @code{\melisma}, @code{\melismaEnd}
3645 @cindex @code{\melismaEnd}
3646 @cindex @code{\melisma}
3650 Program reference: Music expressions: @internalsref{LyricCombineMusic},
3651 Contexts: @internalsref{Lyrics}, @internalsref{Melisma_translator}.
3653 Examples: @inputfileref{input/template,satb.ly},
3654 @inputfileref{input/regression,lyric-combine-new.ly}.
3658 Melismata are not detected automatically, and extender lines must be
3662 For proper processing of extender lines, the
3663 @internalsref{Lyrics} and @internalsref{Voice} should be
3664 linked. This can be achieved either by using @code{\lyricsto} or by
3665 setting corresponding names for both contexts. The latter is explained
3666 in @ref{More stanzas}.
3669 @subsection More stanzas
3671 @cindex phrasing, in lyrics
3674 The lyrics should be aligned with the note heads of the melody. To
3675 achieve this, each line of lyrics should be marked to correspond with
3676 the melodic line. This is done automatically when @code{\lyricsto},
3677 but it can also be done manually.
3679 To this end, give the @internalsref{Voice} context an identity
3681 \context Voice = duet @{
3686 Then set the @internalsref{Lyrics} contexts to names starting with
3687 that identity followed by a dash. In the preceding example, the
3688 @internalsref{Voice} identity is @code{duet}, so the identities of the
3689 @internalsref{Lyrics}s are marked @code{duet-1} and @code{duet-2}
3691 \context Lyrics = "duet-1" @{
3692 Hi, my name is Bert. @}
3693 \context Lyrics = "duet-2" @{
3694 Ooooo, ch\'e -- ri, je t'aime. @}
3697 The complete example is shown here
3699 @lilypond[raggedright,verbatim]
3701 << \notes \relative c'' \context Voice = duet { \time 3/4
3703 \lyrics << \lyricsto "duet" \new Lyrics {
3704 \set vocalName = "Bert"
3705 Hi, my name is Bert. }
3706 \lyricsto "duet" \new Lyrics {
3707 \set vocalName = "Ernie"
3708 Ooooo, ch\'e -- ri, je t'aime.
3715 @cindex stanza number
3716 @cindex singer's names
3717 @cindex name of singer
3719 Stanza numbers can be added by setting @code{stanza}, e.g.
3722 @lilypond[verbatim,relative=3]
3723 << \context Voice = duet { \time 3/4
3725 \lyrics \lyricsto "duet" \new Lyrics {
3727 Hi, my name is Bert.
3733 This example also demonstrates how names of the singers can be added
3734 using @code{vocalName} analogous to instrument annotations for staves.
3735 A short version may be entered as @code{vocNam}.
3737 To make empty spaces in lyrics, use @code{\skip}.
3742 Program reference: Layout objects @internalsref{LyricText} and
3743 @internalsref{VocalName}. Music expressions
3744 @internalsref{LyricEvent}.
3750 Input for lyrics introduces a syntactical ambiguity
3757 is interpreted as assigning a string identifier @code{\foo} such that
3758 it contains @code{"bar"}. However, it could also be interpreted as
3759 making or a music identifier @code{\foo} containing the syllable
3760 `bar'. The force the latter interpretation, use
3770 The term @emph{ambitus} denotes a range of pitches for a given voice
3771 in a part of music. It also may denote the pitch range that a musical
3772 instrument is capable of playing. Ambituses are printed on vocal
3773 parts, so singers can easily determine if it meets his or her
3776 It denoted at the beginning of a piece near the initial clef. The
3777 range is graphically specified by two note heads, that represent the
3778 minimum and maximum pitch. To print such ambituses, add the
3779 @internalsref{Ambitus_engraver} to the @internalsref{Voice} context,
3786 \consists Ambitus_engraver
3791 This results in the following output
3794 @lilypond[raggedright]
3797 \notes \relative c' <<
3808 \consists Ambitus_engraver
3815 If you have multiple voices in a single staff, and you want a single
3816 ambitus per staff rather than per each voice, add the
3817 @internalsref{Ambitus_engraver} to the @internalsref{Staff} context
3818 rather than to the @internalsref{Voice} context.
3820 It is possible to tune individual ambituses for multiple voices on a
3821 single staff, for example by erasing or shifting them horizontally. An
3822 example is in @inputfileref{input/test,ambitus-mixed.ly}.
3826 Program reference: @internalsref{Ambitus}.
3828 Examples: @inputfileref{input/regression,ambitus.ly},
3829 @inputfileref{input/test,ambitus-mixed.ly}.
3833 There is no collision handling in the case of multiple per-voice
3839 Tablature notation is used for notating music for plucked string
3840 instruments. It notates pitches not by using note heads, but by
3841 indicating on which string and fret a note must be played. LilyPond
3842 offers limited support for tablature.
3845 * Tablatures basic::
3846 * Non-guitar tablatures::
3849 @node Tablatures basic
3850 @subsection Tablatures basic
3851 @cindex Tablatures basic
3853 The string number associated to a note is given as a backslash
3854 followed by a number, e.g. @code{c4\3} for a C quarter on the third
3855 string. By default, string 1 is the highest one, and the tuning
3856 defaults to the standard guitar tuning (with 6 strings). The notes
3857 are printed as tablature, by using @internalsref{TabStaff} and
3858 @internalsref{TabVoice} contexts
3861 @lilypond[fragment,verbatim]
3862 \notes \context TabStaff {
3871 When no string is specified, the first string that does not give a
3872 fret number less than @code{minimumFret} is selected. The default
3873 value for @code{minimumFret} is 0
3878 \set TabStaff.minimumFret = #8
3882 @lilypond[noindent,raggedright]
3886 \set TabStaff.minimumFret = #8
3890 \context StaffGroup <<
3891 \context Staff { \clef "G_8" \frag }
3892 \context TabStaff { \frag }
3900 Program reference: @internalsref{TabStaff}, @internalsref{TabVoice}, and
3901 @internalsref{StringNumberEvent}.
3905 Chords are not handled in a special way, and hence the automatic
3906 string selector may easily select the same string to two notes in a
3910 @node Non-guitar tablatures
3911 @subsection Non-guitar tablatures
3912 @cindex Non-guitar tablatures
3914 You can change the number of strings, by setting the number of lines
3915 in the @internalsref{TabStaff}.
3917 You can change the tuning of the strings. A string tuning is given as
3918 a Scheme list with one integer number for each string, the number
3919 being the pitch (measured in semitones relative to middle C) of an
3920 open string. The numbers specified for @code{stringTuning} are the
3921 numbers of semitones to subtract or add, starting the specified pitch
3922 by default middle C, in string order. Thus, the notes are e, a, d, and
3926 @lilypond[fragment,verbatim]
3927 \context TabStaff <<
3928 \set TabStaff.stringTunings = #'(-5 -10 -15 -20)
3931 a,4 c' a e' e c' a e'
3939 No guitar special effects have been implemented.
3943 Program reference: @internalsref{Tab_note_heads_engraver}.
3947 @section Chord names
3950 LilyPond has support for both printing chord names. Chords may be
3951 entered in musical chord notation, i.e. @code{< .. >}, but they can
3952 also be entered by name. Internally, the chords are represented as a
3953 set of pitches, so they can be transposed
3957 @lilypond[verbatim,raggedright]
3958 twoWays = \notes \transpose c c' {
3968 << \context ChordNames \twoWays
3969 \context Voice \twoWays >> }
3973 This example also shows that the chord printing routines do not try to
3974 be intelligent. The last chord (@code{f bes d}) is not interpreted as
3980 * Printing chord names::
3985 @subsection Chords mode
3988 Chord mode is a mode where you can input sets of pitches using common
3989 names. It is introduced by the keyword @code{\chords}.
3990 In chords mode, a chord is entered by the root, which is entered
3993 @lilypond[fragment,verbatim,relative=2]
3994 \chords { es4. d8 c2 }
4000 Other chords may be entered by suffixing a colon, and introducing a
4001 modifier, and optionally, a number
4004 @lilypond[fragment,verbatim]
4005 \chords { e1:m e1:7 e1:m7 }
4008 The first number following the root is taken to be the `type' of the
4009 chord, thirds are added to the root until it reaches the specified
4012 @lilypond[fragment,verbatim]
4013 \chords { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 }
4017 @cindex root of chord
4018 @cindex additions, in chords
4019 @cindex removals, in chords
4021 More complex chords may also be constructed adding separate steps
4022 to a chord. Additions are added after the number following
4023 the colon, and are separated by dots
4026 @lilypond[verbatim,fragment]
4027 \chords { c:5.6 c:3.7.8 c:3.6.13 }
4030 Chord steps can be altered by suffixing a @code{-} or @code{+} sign
4033 @lilypond[verbatim,fragment]
4034 \chords { c:7+ c:5+.3- c:3-.5-.7- }
4037 Removals are specified similarly, and are introduced by a caret. They
4038 must come after the additions
4040 @lilypond[verbatim,fragment]
4041 \chords { c^3 c:7^5 c:9^3.5 }
4045 Modifiers can be used to change pitches. The following modifiers are
4049 is the minor chord. This modifier lowers the 3rd and (if present) the 7th step.
4051 is the diminished chord. This modifier lowers the 3rd, 5th and (if present)
4054 is the augmented chord. This modifier raises the 5th step.
4056 is the major 7th chord. This modifier raises the 7th step if present.
4058 is the suspended 4th or 2nd. This modifier removes the 3rd
4059 step. Append either @code{2} or @code{4} to add the 2nd or 4th step to
4062 Modifiers can be mixed with additions
4064 @lilypond[verbatim,fragment]
4065 \chords { c:sus4 c:7sus4 c:dim7 c:m6 }
4069 @cindex modifiers, in chords.
4076 Since an unaltered 11 does not sound good when combined with an
4077 unaltered 13, the 11 is removed in this case (unless it is added
4081 @lilypond[fragment,verbatim]
4082 \chords { c:13 c:13.11 c:m13 }
4088 An inversion (putting one pitch of the chord on the bottom), as well
4089 as bass notes, can be specified by appending
4090 @code{/}@var{pitch} to the chord
4092 @lilypond[fragment,verbatim]
4093 \chords { c1 c/g c/f }
4098 A bass note can be added instead of transposed out of the chord,
4099 by using @code{/+}@var{pitch}.
4102 @lilypond[fragment,verbatim]
4103 \chords { c1 c/+g c/+f }
4107 Chords is a mode similar to @code{\lyrics}, @code{\notes} etc. Most
4108 of the commands continue to work, for example, @code{r} and
4109 @code{\skip} can be used to insert rests and spaces, and property
4110 commands may be used to change various settings.
4116 Each step can only be present in a chord once. The following
4117 simply produces the augmented chord, since @code{5+} is interpreted
4121 @lilypond[verbatim,fragment]
4122 \chords { c:5.5-.5+ }
4127 @node Printing chord names
4128 @subsection Printing chord names
4130 @cindex printing chord names
4134 For displaying printed chord names, use the @internalsref{ChordNames} context.
4135 The chords may be entered either using the notation
4136 described above, or directly using @code{<} and @code{>}
4139 @lilypond[verbatim,raggedright]
4141 \chords {a1 b c} <d' f' a'> <e' g' b'>
4145 \context ChordNames \scheme
4146 \context Staff \scheme
4152 You can make the chord changes stand out by setting
4153 @internalsref{ChordNames}.@code{chordChanges} to true. This will only
4154 display chord names when there is a change in the chords scheme and at
4155 the start of a new line
4158 @lilypond[verbatim,linewidth=9\cm]
4160 c1:m c:m \break c:m c:m d
4164 \context ChordNames {
4165 \set chordChanges = ##t
4167 \context Staff \transpose c c' \scheme
4173 The default chord name layout is a system for Jazz music, proposed by
4174 Klaus Ignatzek (see @ref{Literature list}). It can be tuned through the
4175 following properties
4178 @cindex chordNameExceptions
4179 @item chordNameExceptions
4180 This is a list that contains the chords that have special formatting.
4182 @inputfileref{input/regression,chord-name-exceptions.ly}.
4183 @cindex exceptions, chord names.
4186 @cindex majorSevenSymbol
4187 @item majorSevenSymbol
4188 This property contains the markup object used for the 7th step, when
4189 it is major. Predefined options are @code{whiteTriangleMarkup} and
4190 @code{blackTriangleMarkup}. See
4191 @inputfileref{input/regression,chord-name-major7.ly} for an example.
4193 @cindex chordNameSeparator
4194 @item chordNameSeparator
4195 Different parts of a chord name are normally separated by a
4196 slash. By setting @code{chordNameSeparator}, you can specify other
4199 @lilypond[fragment,verbatim]
4200 \context ChordNames \chords {
4202 \set chordNameSeparator
4203 = \markup { \typewriter "|" }
4209 @cindex chordRootNamer
4210 @item chordRootNamer
4211 The root of a chord is usually printed as a letter with an optional
4212 alteration. The transformation from pitch to letter is done by this
4213 function. Special note names (for example, the German ``H'' for a
4214 B-chord) can be produced by storing a new function in this property.
4216 The predefined variables @code{\germanChords},
4217 @code{\semiGermanChords} set these variables.
4220 @cindex chordNoteNamer
4221 @item chordNoteNamer
4222 The default is to print single pitch, e.g. the bass note, using the
4223 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
4224 to a specialized function to change this behavior. For example, the
4225 base can be printed in lower case.
4230 There are also two other chord name schemes implemented: an alternate
4231 Jazz chord notation, and a systematic scheme called Banter chords. The
4232 alternate jazz notation is also shown on the chart in @ref{Chord name
4233 chart}. Turning on these styles is described in the input file
4234 @inputfileref{input/test,chord-names-jazz.ly}.
4238 @cindex chords, jazz
4243 @cindex @code{\germanChords}
4244 @code{\germanChords},
4245 @cindex @code{\semiGermanChords}
4246 @code{\semiGermanChords}.
4253 Examples: @inputfileref{input/regression,chord-name-major7.ly},
4254 @inputfileref{input/regression,chord-name-exceptions.ly},
4255 @inputfileref{input/test,chord-names-jazz.ly},
4256 @inputfileref{input/test,chord-names-german.ly}.
4258 Init files: @file{scm/chords-ignatzek.scm}, and @file{scm/chord-entry.scm}.
4263 Chord names are determined solely from the list of pitches. Chord
4264 inversions are not identified, and neither are added bass notes. This
4265 may result in strange chord names when chords are entered with the
4266 @code{< .. >} syntax.
4271 @node Orchestral music
4272 @section Orchestral music
4274 @cindex Writing parts
4276 Orchestral music involves some special notation, both in the full
4277 score and the individual parts. This section explains how to tackle
4278 some common problems in orchestral music.
4283 * Multiple staff contexts::
4286 * Instrument names::
4288 * Instrument transpositions::
4289 * Multi measure rests::
4290 * Automatic part combining::
4292 * Different editions from one source::
4293 * Quoting other voices::
4296 @node Multiple staff contexts
4297 @subsection Multiple staff contexts
4299 Polyphonic scores consist of many staves. These staves can be
4300 constructed in three different ways
4302 @item The group is started with a brace at the left, and bar lines are
4303 connected. This is done with the @internalsref{GrandStaff} context.
4305 @item The group is started with a bracket, and bar lines are connected. This is done with the
4306 @internalsref{StaffGroup} context
4309 @item The group is started with a vertical line. Bar lines are not
4310 connected. This is the default for the score.
4314 @cindex Staff, multiple
4315 @cindex bracket, vertical
4316 @cindex brace, vertical
4323 @node Rehearsal marks
4324 @subsection Rehearsal marks
4325 @cindex Rehearsal marks
4327 @cindex @code{\mark}
4329 To print a rehearsal mark, use the @code{\mark} command
4331 @lilypond[fragment,verbatim]
4343 (The letter I is skipped in accordance with engraving traditions.)
4345 The mark is incremented automatically if you use @code{\mark
4346 \default}, but you can also use an integer argument to set the mark
4347 manually. The value to use is stored in the property
4348 @code{rehearsalMark}.
4350 The style is defined by the property @code{markFormatter}. It is a
4351 function taking the current mark (an integer) and the current context
4352 as argument. It should return a markup object. In the following
4353 example, @code{markFormatter} is set to a canned procedure. After a
4354 few measures, it is set to function that produces a boxed number.
4357 @lilypond[verbatim,fragment,relative=2]
4358 \set Score.markFormatter = #format-mark-numbers
4361 \set Score.markFormatter
4362 = #(lambda (mark context)
4363 (make-bold-markup (make-box-markup (number->string mark))))
4369 The file @file{scm/translation-functions.scm} contains the definitions
4370 of @code{format-mark-numbers} (the default format) and
4371 @code{format-mark-letters}. They can be used as inspiration for other
4372 formatting functions.
4375 @cindex coda on bar line
4376 @cindex segno on bar line
4377 @cindex fermata on bar line
4378 @cindex bar lines, symbols on
4380 The @code{\mark} command can also be used to put signs like coda,
4381 segno and fermatas on a bar line. Use @code{\markup} to
4382 to access the appropriate symbol
4385 @lilypond[fragment,verbatim,relative=2]
4386 c1 \mark \markup { \musicglyph #"scripts-ufermata" }
4391 In the case of a line break, marks must also be printed at the end of
4392 the line, and not at the beginning. Use the following to force that
4395 \override Score.RehearsalMark
4396 #'break-visibility = #begin-of-line-invisible
4402 @cindex bar lines, putting symbols on
4406 Program reference: @internalsref{MarkEvent}, @internalsref{RehearsalMark}.
4408 Init files: @file{scm/translation-functions.scm} contains the
4409 definition of @code{format-mark-numbers} and
4410 @code{format-mark-letters}. They can be used as inspiration for other
4411 formatting functions.
4413 Examples: @inputfileref{input/regression,rehearsal-mark-letter.ly},
4414 @inputfileref{input/regression,rehearsal-mark-number.ly}.
4418 @subsection Bar numbers
4422 @cindex measure numbers
4423 @cindex currentBarNumber
4425 Bar numbers are printed by default at the start of the line. The
4426 number itself is stored in the
4427 @code{currentBarNumber} property,
4428 which is normally updated automatically for every measure.
4430 Bar numbers can be typeset at regular intervals instead of at the
4431 beginning of each line. This is illustrated in the following example,
4432 whose source is available as
4433 @inputfileref{input/test,bar-number-regular-interval.ly}
4436 @lilypondfile[]{bar-number-regular-interval.ly}
4441 Program reference: @internalsref{BarNumber}.
4443 Examples: @inputfileref{input/test,bar-number-every-five-reset.ly},
4444 and @inputfileref{input/test,bar-number-regular-interval.ly}.
4448 Bar numbers can collide with the @internalsref{StaffGroup} bracket, if
4449 there is one at the top. To solve this, the
4450 @code{padding} property of @internalsref{BarNumber} can be
4451 used to position the number correctly.
4453 @node Instrument names
4454 @subsection Instrument names
4456 In an orchestral score, instrument names are printed left side of the
4459 This can be achieved by setting @internalsref{Staff}.@code{instrument}
4460 and @internalsref{Staff}.@code{instr}. This will print a string before
4461 the start of the staff. For the first start, @code{instrument} is
4462 used, for the next ones @code{instr} is used.
4465 @lilypond[verbatim,raggedright,relative=3]
4466 \set Staff.instrument = "Ploink "
4467 \set Staff.instr = "Plk "
4474 You can also use markup texts to construct more complicated instrument
4478 @lilypond[fragment,verbatim,raggedright]
4480 \set Staff.instrument = \markup {
4481 \column < "Clarinetti"
4494 Program reference: @internalsref{InstrumentName}.
4498 When you put a name on a grand staff or piano staff the width of the
4499 brace is not taken into account. You must add extra spaces to the end of
4500 the name to avoid a collision.
4503 @subsection Transpose
4505 @cindex transposition of pitches
4506 @cindex @code{\transpose}
4508 A music expression can be transposed with @code{\transpose}. The syntax
4511 \transpose @var{from} @var{to} @var{musicexpr}
4514 This means that @var{musicexpr} is transposed by the interval between
4515 the pitches @var{from} and @var{to}: any note with pitch @code{from}
4516 is changed to @code{to}.
4519 For example, consider a piece written in the key of D major. If
4520 this piece is a little too low for its performer, it can be
4521 transposed up to E major with
4523 \transpose d e @dots{}
4526 Consider a part written for violin (a C instrument). If
4527 this part is to be played on the A clarinet, the following
4528 transposition will produce the appropriate part
4531 \transpose a c @dots{}
4534 Since @var{from} and @var{to} are pitches, so @code{\transpose} must be
4535 inside a @code{\notes} section. @code{\transpose} distinguishes
4536 between enharmonic pitches: both @code{\transpose c cis} or
4537 @code{\transpose c des} will transpose up half a tone. The first
4538 version will print sharps and the second version will print flats
4541 @lilypond[raggedright,verbatim]
4542 mus =\notes { \key d \major cis d fis g }
4543 \score { \notes \context Staff {
4546 \transpose c g' \mus
4547 \transpose c f' \mus
4555 Program reference: @internalsref{TransposedMusic}, and
4556 @internalsref{UntransposableMusic}.
4560 If you want to use both @code{\transpose} and @code{\relative},
4561 you must put @code{\transpose} outside of @code{\relative}, since
4562 @code{\relative} will have no effect music that appears inside a
4565 @node Instrument transpositions
4566 @subsection Instrument transpositions
4568 The key of a transposing instrument can also be specified. This
4569 applies to many wind instruments, for example, clarinets (B-flat, A and
4570 E-flat), horn (F) and trumpet (B-flat, C, D and E-flat).
4573 The transposition is entered after the keyword @code{\transposition}
4576 \transposition bes %% B-flat clarinet
4579 This command sets the property @code{instrumentTuning}. The value of
4580 this property is used for MIDI output and quotations. It does not
4581 affect how notes are printed in the current staff.
4583 @cindex transposition, MIDI
4584 @cindex transposition, instrument
4587 @node Multi measure rests
4588 @subsection Multi measure rests
4589 @cindex multi measure rests
4590 @cindex Rests, multi measure
4594 Multi measure rests are entered using `@code{R}'. It is specifically
4595 meant for full bar rests and for entering parts: the rest can expand
4596 to fill a score with rests, or it can be printed as a single
4597 multimeasure rest. This expansion is controlled by the property
4598 @code{Score.skipBars}. If this is set to true, empty measures will not
4599 be expanded, and the appropriate number is added automatically
4602 @lilypond[fragment,verbatim]
4603 \time 4/4 r1 | R1 | R1*2
4604 \set Score.skipBars = ##t R1*17 R1*4
4608 The @code{1} in @code{R1} is similar to the duration notation used for
4609 notes. Hence, for time signatures other than 4/4, you must enter other
4610 durations. This can be done with augmentation dots or fractions
4613 @lilypond[fragment,verbatim]
4614 \set Score.skipBars = ##t
4623 An @code{R} spanning a single measure is printed as either a whole rest
4624 or a breve, centered in the measure regardless of the time signature.
4626 @cindex text on multi-measure rest
4627 @cindex script on multi-measure rest
4628 @cindex fermata on multi-measure rest
4630 Texts can be added to multi-measure rests by using the
4631 @var{note}-@code{markup} syntax (see @ref{Text markup}). In this case, the number is
4632 replaced. If you need both texts and the number, you must add the
4633 number by hand. A variable (@code{\fermataMarkup}) is provided for
4638 @lilypond[verbatim,fragment]
4640 R2._\markup { "Ad lib" }
4645 If you want to have a text on the left end of a multi-measure rest,
4646 attach the text to a zero-length skip note, i.e.
4654 @cindex whole rests for a full measure
4658 Program reference: @internalsref{MultiMeasureRestEvent},
4659 @internalsref{MultiMeasureTextEvent},
4660 @internalsref{MultiMeasureRestMusicGroup}, and
4661 @internalsref{MultiMeasureRest}.
4663 The layout object @internalsref{MultiMeasureRestNumber} is for the
4664 default number, and @internalsref{MultiMeasureRestText} for user
4669 It is not possible to use fingerings (e.g. @code{R1-4}) to put numbers
4670 over multi-measure rests.
4672 @cindex condensing rests
4674 There is no way to automatically condense multiple rests into a single
4675 multimeasure rest. Multi measure rests do not take part in rest
4678 Be careful when entering multimeasure rests followed by whole
4679 notes. The following will enter two notes lasting four measures each
4683 When @code{skipBars} is set, the result will look OK, but the bar
4684 numbering will be off.
4686 @node Automatic part combining
4687 @subsection Automatic part combining
4688 @cindex automatic part combining
4689 @cindex part combiner
4692 Automatic part combining is used to merge two parts of music onto a
4693 staff. It is aimed at typesetting orchestral scores. When the two
4694 parts are identical for a period of time, only one is shown. In
4695 places where the two parts differ, they are typeset as separate
4696 voices, and stem directions are set automatically. Also, solo and
4697 @emph{a due} parts are identified and can be marked.
4700 The syntax for part combining is
4703 \partcombine @var{musicexpr1} @var{musicexpr2}
4706 The music expressions will be interpreted as @internalsref{Voice} contexts.
4708 The following example demonstrates the basic functionality of the part
4709 combiner: putting parts on one staff, and setting stem directions and
4713 @lilypond[verbatim,raggedright,fragment,relative=2]
4714 \new Staff \partcombine
4724 The first @code{g} appears only once, although it was
4725 specified twice (once in each part). Stem, slur and tie directions are
4726 set automatically, depending whether there is a solo or unisono. The
4727 first part (with context called @code{one}) always gets up stems, and
4728 `solo', while the second (called @code{two}) always gets down stems and
4731 If you just want the merging parts, and not the textual markings, you
4732 may set the property @var{soloADue} to false
4735 @lilypond[verbatim,raggedright,fragment,relative=2]
4737 \set Staff.soloADue = ##f
4750 Program reference: @internalsref{PartCombineMusic},
4751 @internalsref{SoloOneEvent}, and
4752 @internalsref{SoloTwoEvent}, and
4753 @internalsref{UnisonoEvent}.
4757 In @code{soloADue} mode, when the two voices play the same notes on and
4758 off, the part combiner may typeset @code{a2} more than once in a
4761 @code{\partcombine} can not be inside @code{\times}.
4763 Internally, the @code{\partcombine} interprets both arguments as
4764 @code{Voice}s named @code{one} and @code{two}, and then decides when
4765 the parts can be combined. Consequently, if the arguments switch to
4766 differently named @internalsref{Voice} contexts, the events in those
4770 @subsection Hiding staves
4772 @cindex Frenched scores
4773 @cindex Hiding staves
4775 In orchestral scores, staff lines that only have rests are usually
4776 removed. This saves some space. This style is called `French Score'.
4777 For @internalsref{Lyrics},
4778 @internalsref{ChordNames} and @internalsref{FiguredBass}, this is
4779 switched on by default. When these line of these contexts turn out
4780 empty after the line-breaking process, they are removed.
4782 For normal staves, a specialized @internalsref{Staff} context is
4783 available, which does the same: staves containing nothing (or only
4784 multi measure rests) are removed. The context definition is stored in
4785 @code{\RemoveEmptyStaffContext} variable. Observe how the second staff
4786 in this example disappears in the second line
4792 \notes \relative c' <<
4793 \new Staff { e4 f g a \break c1 }
4794 \new Staff { c4 d e f \break R1 }
4798 \context { \RemoveEmptyStaffContext }
4804 The first page shows all staves in full. If empty staves should be
4805 removed from the first page too, set @code{remove-first} to false in
4806 @internalsref{RemoveEmptyVerticalGroup}.
4808 Another application is making ossia sections, i.e. alternative
4809 melodies on a separate piece of staff, with help of a Frenched
4810 staff. See @inputfileref{input/test,ossia.ly} for an example.
4813 @node Different editions from one source
4814 @subsection Different editions from one source
4816 The @code{\tag} command marks music expressions with a name. These
4817 tagged expressions can be filtered out later. With this mechanism it
4818 is possible to make different versions of the same music source.
4820 In the following example, we see two versions of a piece of music, one
4821 for the full score, and one with cue notes for the instrumental part
4837 The same can be applied to articulations, texts, etc.: they are
4840 -\tag #@var{your-tag}
4842 to an articulation, for example,
4847 This defines a note with a conditional fingering indication.
4849 By applying the @code{remove-tag} function, tagged expressions can be
4850 filtered. For example,
4854 \apply #(remove-tag 'score) @var{the music}
4855 \apply #(remove-tag 'part) @var{the music}
4861 @lilypondfile[]{tag-filter.ly}
4864 The argument of the @code{\tag} command should be a symbol, or a list
4865 of symbols, for example,
4867 \tag #'(original-part transposed-part) @dots{}
4872 Examples: @inputfileref{input/regression,tag-filter.ly}.
4875 @node Quoting other voices
4876 @subsection Quoting other voices
4878 With quotations, fragments of other parts can be inserted into a part
4879 directly. Before a part can be quoted, it must be marked especially as
4880 quotable. This is done with code @code{\addquote} command. The
4881 quotation may then be done with @code{\quote}
4884 \addquote @var{name} @var{music}
4885 \quote @var{name} @var{duration}
4890 Here, @var{name} is an identifying string. The @var{music} is any kind
4891 of music. This is an example of @code{\addquote}
4894 \addquote clarinet \notes\relative c' {
4899 During a part, a piece of music can be quoted with the @code{\quote}
4906 This would cite 3 quarter notes (a dotted half note) of the previously
4907 added clarinet voice.
4909 Quotations take into account the transposition both source and target
4910 instruments, if they are specified using the @code{\transposition} command.
4913 @lilypond[verbatim,fragment]
4914 \addquote clarinet \notes\relative c' {
4920 e'8 f'8 \quote clarinet 2
4927 Only the contents of the first @internalsref{Voice} occurring in an
4928 @code{\addquote} command will be considered for quotation, so
4929 @var{music} can not contain @code{\new} and @code{\context Voice}
4930 statements that would switch to a different Voice.
4935 In this manual: @ref{Instrument transpositions}.
4937 Examples: @inputfileref{input/regression,quote.ly}
4938 @inputfileref{input/regression,quote-transposition.ly}
4940 Program reference: @internalsref{QuoteMusic}.
4942 @node Ancient notation
4943 @section Ancient notation
4945 @cindex Vaticana, Editio
4946 @cindex Medicaea, Editio
4951 Support for ancient notation includes features for mensural notation
4952 and Gregorian Chant notation. There is also limited support for
4953 figured bass notation.
4955 Many graphical objects provide a @code{style} property, see
4956 @ref{Ancient note heads}, @ref{Ancient accidentals}, @ref{Ancient
4957 rests}, @ref{Ancient clefs}, @ref{Ancient flags} and @ref{Ancient time
4958 signatures}. By manipulating such a grob property, the typographical
4959 appearance of the affected graphical objects can be accommodated for a
4960 specific notation flavor without need for introducing any new
4963 Other aspects of ancient notation can not that easily be expressed as
4964 in terms of just changing a style property of a graphical object.
4965 Therefore, some notational concepts are introduced specifically for
4966 ancient notation, see @ref{Custodes}, @ref{Divisiones},
4967 @ref{Ligatures}, and @ref{Figured bass}.
4971 * Ancient note heads::
4972 * Ancient accidentals::
4976 * Ancient time signatures::
4981 * Vaticana style contexts::
4984 If this all is way too much of documentation for you, and you just
4985 want to dive into typesetting without worrying too much about the
4986 details on how to customize a context, you may have a look at the
4987 predefined contexts (see @ref{Vaticana style contexts}). Use them to
4988 set up predefined style-specific voice and staff contexts, and
4989 directly go ahead with the note entry.
4993 Ligatures need special spacing that has not yet been implemented. As
4994 a result, there is too much space between ligatures most of the time,
4995 and line breaking often is unsatisfactory. Also, lyrics do not
4996 correctly align with ligatures.
4998 Accidentals must not be printed within a ligature, but instead need to
4999 be collected and printed in front of it.
5001 Augmentum dots within ligatures are not handled correctly.
5004 @node Ancient note heads
5005 @subsection Ancient note heads
5010 For ancient notation, a note head style other than the @code{default}
5011 style may be chosen. This is accomplished by setting the @code{style}
5012 property of the NoteHead object to the desired value (@code{baroque},
5013 @code{neo_mensural} or @code{mensural}). The @code{baroque} style
5014 differs from the @code{default} style only in using a square shape for
5015 @code{\breve} note heads. The @code{neo_mensural} style differs from
5016 the @code{baroque} style in that it uses rhomboidal heads for whole
5017 notes and all smaller durations. Stems are centered on the note
5018 heads. This style is in particular useful when transcribing mensural
5019 music, e.g. for the incipit. The @code{mensural} style finally
5020 produces note heads that mimic the look of note heads in historic
5021 printings of the 16th century.
5023 The following example demonstrates the @code{neo_mensural} style
5026 @lilypond[fragment,raggedright,verbatim]
5027 \override NoteHead #'style = #'neo_mensural
5028 a'\longa a'\breve a'1 a'2 a'4 a'8 a'16
5032 When typesetting a piece in Gregorian Chant notation, a Gregorian
5033 ligature engraver will automatically select the proper note heads,
5034 such there is no need to explicitly set the note head style. Still,
5035 the note head style can be set e.g. to @code{vaticana_punctum} to
5036 produce punctum neumes. Similarly, a mensural ligature engraver is
5037 used to automatically assemble mensural ligatures. See
5038 @ref{Ligatures} for how ligature engravers work.
5043 @ref{Percussion staves} use note head styles of their own that are
5044 frequently used in contemporary music notation.
5046 Examples: @inputfileref{input/regression,note-head-style.ly} gives an
5047 overview over all available note head styles.
5050 @node Ancient accidentals
5051 @subsection Ancient accidentals
5056 Use the @code{style} property of grob @internalsref{Accidental} to
5057 select ancient accidentals. Supported styles are
5058 @code{mensural}, @code{vaticana}, @code{hufnagel} and @code{medicaea}.
5061 @lilypond[raggedright,staffsize=26]
5069 { " " \musicglyph #"accidentals-vaticana-1"
5070 " " \musicglyph #"accidentals-vaticana0" }
5074 { " " \musicglyph #"accidentals-medicaea-1" }
5078 { " " \musicglyph #"accidentals-hufnagel-1" }
5082 { " " \musicglyph #"accidentals-mensural-1"
5083 " " \musicglyph #"accidentals-mensural1" }
5092 \remove "Bar_number_engraver"
5096 \remove "Clef_engraver"
5097 \remove "Key_engraver"
5098 \remove "Time_signature_engraver"
5099 \remove "Staff_symbol_engraver"
5100 minimumVerticalExtent = ##f
5107 As shown, not all accidentals are supported by each style. When
5108 trying to access an unsupported accidental, LilyPond will switch to a
5109 different style, as demonstrated in
5110 @inputfileref{input/test,ancient-accidentals.ly}.
5112 Similarly to local accidentals, the style of the key signature can be
5113 controlled by the @code{style} property of the
5114 @internalsref{KeySignature} grob.
5118 In this manual: @ref{Pitches}, @ref{Chromatic alterations} and
5119 @ref{Accidentals} give a general introduction into the use of
5120 accidentals. @ref{Key signature} gives a general introduction into
5121 the use of key signatures.
5123 Program reference: @internalsref{KeySignature}.
5125 Examples: @inputfileref{input/test,ancient-accidentals.ly}.
5128 @subsection Ancient rests
5133 Use the @code{style} property of grob @internalsref{Rest} to select
5134 ancient accidentals. Supported styles are @code{classical},
5135 @code{neo_mensural} and @code{mensural}. @code{classical} differs
5136 from the @code{default} style only in that the quarter rest looks like
5137 a horizontally mirrored 8th rest. The @code{neo_mensural} style suits
5138 well for e.g. the incipit of a transcribed mensural piece of music.
5139 The @code{mensural} style finally mimics the appearance of rests as
5140 in historic prints of the 16th century.
5142 The following example demonstrates the @code{neo_mensural} style
5145 @lilypond[fragment,raggedright,verbatim]
5146 \override Rest #'style = #'neo_mensural
5147 r\longa r\breve r1 r2 r4 r8 r16
5151 There are no 32th and 64th rests specifically for the mensural or
5152 neo-mensural style. Instead, the rests from the default style will be
5153 taken. See @inputfileref{input/test,rests.ly} for a chart of all
5156 There are no rests in Gregorian Chant notation; instead, it uses
5161 In this manual: @ref{Rests} gives a general introduction into the use of rests.
5165 @subsection Ancient clefs
5170 LilyPond supports a variety of clefs, many of them ancient.
5172 The following table shows all ancient clefs that are supported via the
5173 @code{\clef} command. Some of the clefs use the same glyph, but
5174 differ only with respect to the line they are printed on. In such
5175 cases, a trailing number in the name is used to enumerate these clefs.
5176 Still, you can manually force a clef glyph to be typeset on an
5177 arbitrary line, as described in @ref{Clef}. The note printed to the
5178 right side of each clef in the example column denotes the @code{c'}
5179 with respect to that clef.
5181 @multitable @columnfractions .3 .3 .3 .1
5185 @b{Description} @tab
5186 @b{Supported Clefs} @tab
5190 @code{clefs-neo_mensural_c} @tab
5191 modern style mensural C clef @tab
5192 @code{neo_mensural_c1}, @code{neo_mensural_c2},
5193 @code{neo_mensural_c3}, @code{neo_mensural_c4} @tab
5195 @lilypond[relative=1,notime]
5196 \override Staff.TimeSignature #'transparent = ##t
5197 \clef "neo_mensural_c2" c
5202 @code{clefs-petrucci_c1}
5203 @code{clefs-petrucci_c2}
5204 @code{clefs-petrucci_c3}
5205 @code{clefs-petrucci_c4}
5206 @code{clefs-petrucci_c5}
5209 petrucci style mensural C clefs, for use on different staff lines
5210 (the examples shows the 2nd staff line C clef).
5221 @lilypond[relative=1,notime]
5222 \override Staff.TimeSignature #'transparent = ##t
5223 \clef "petrucci_c2" c
5228 @code{clefs-petrucci_f} @tab
5229 petrucci style mensural F clef @tab
5230 @code{petrucci_f} @tab
5232 @lilypond[relative=1,notime]
5233 \override Staff.TimeSignature #'transparent = ##t
5234 \clef "petrucci_f" c
5239 @code{clefs-petrucci_g} @tab
5240 petrucci style mensural G clef @tab
5241 @code{petrucci_g} @tab
5243 @lilypond[relative=1,notime]
5244 \override Staff.TimeSignature #'transparent = ##t
5245 \clef "petrucci_g" c
5250 @code{clefs-mensural_c} @tab
5251 historic style mensural C clef @tab
5252 @code{mensural_c1}, @code{mensural_c2}, @code{mensural_c3},
5253 @code{mensural_c4} @tab
5255 @lilypond[relative=1,notime]
5256 \override Staff.TimeSignature #'transparent = ##t
5257 \clef "mensural_c2" c
5262 @code{clefs-mensural_f} @tab
5263 historic style mensural F clef @tab
5264 @code{mensural_f} @tab
5266 @lilypond[relative=1,notime]
5267 \override Staff.TimeSignature #'transparent = ##t
5268 \clef "mensural_f" c
5273 @code{clefs-mensural_g} @tab
5274 historic style mensural G clef @tab
5275 @code{mensural_g} @tab
5277 @lilypond[relative=1,notime]
5278 \override Staff.TimeSignature #'transparent = ##t
5279 \clef "mensural_g" c
5284 @code{clefs-vaticana_do} @tab
5285 Editio Vaticana style do clef @tab
5286 @code{vaticana_do1}, @code{vaticana_do2}, @code{vaticana_do3} @tab
5288 @lilypond[relative=1,notime]
5289 \override Staff.StaffSymbol #'line-count = #4
5290 \override Staff.TimeSignature #'transparent = ##t
5291 \clef "vaticana_do2" c
5296 @code{clefs-vaticana_fa} @tab
5297 Editio Vaticana style fa clef @tab
5298 @code{vaticana_fa1}, @code{vaticana_fa2} @tab
5300 @lilypond[relative=1,notime]
5301 \override Staff.StaffSymbol #'line-count = #4
5302 \override Staff.TimeSignature #'transparent = ##t
5303 \clef "vaticana_fa2" c
5308 @code{clefs-medicaea_do} @tab
5309 Editio Medicaea style do clef @tab
5310 @code{medicaea_do1}, @code{medicaea_do2}, @code{medicaea_do3} @tab
5312 @lilypond[relative=1,notime]
5313 \override Staff.StaffSymbol #'line-count = #4
5314 \override Staff.TimeSignature #'transparent = ##t
5315 \clef "medicaea_do2" c
5320 @code{clefs-medicaea_fa} @tab
5321 Editio Medicaea style fa clef @tab
5322 @code{medicaea_fa1}, @code{medicaea_fa2} @tab
5324 @lilypond[relative=1,notime]
5325 \override Staff.StaffSymbol #'line-count = #4
5326 \override Staff.TimeSignature #'transparent = ##t
5327 \clef "medicaea_fa2" c
5332 @code{clefs-hufnagel_do} @tab
5333 historic style hufnagel do clef @tab
5334 @code{hufnagel_do1}, @code{hufnagel_do2}, @code{hufnagel_do3} @tab
5336 @lilypond[relative=1,notime]
5337 \override Staff.StaffSymbol #'line-count = #4
5338 \override Staff.TimeSignature #'transparent = ##t
5339 \clef "hufnagel_do2" c
5344 @code{clefs-hufnagel_fa} @tab
5345 historic style hufnagel fa clef @tab
5346 @code{hufnagel_fa1}, @code{hufnagel_fa2} @tab
5348 @lilypond[relative=1,notime]
5349 \override Staff.StaffSymbol #'line-count = #4
5350 \override Staff.TimeSignature #'transparent = ##t
5351 \clef "hufnagel_fa2" c
5356 @code{clefs-hufnagel_do_fa} @tab
5357 historic style hufnagel combined do/fa clef @tab
5358 @code{hufnagel_do_fa} @tab
5360 @lilypond[relative=1,notime]
5361 \override Staff.TimeSignature #'transparent = ##t
5362 \clef "hufnagel_do_fa" c
5370 @emph{Modern style} means ``as is typeset in contemporary editions of
5371 transcribed mensural music''.
5373 @emph{Petrucci style} means ``inspired by printings published by the
5374 famous engraver Petrucci (1466-1539)''.
5376 @emph{Historic style} means ``as was typeset or written in historic
5377 editions (other than those of Petrucci)''.
5379 @emph{Editio XXX style} means ``as is/was printed in Editio XXX''.
5381 Petrucci used C clefs with differently balanced left-side vertical
5382 beams, depending on which staff line it is printed.
5386 In this manual: see @ref{Clef}.
5390 The mensural g clef is mapped to the Petrucci g clef, until a new
5391 mensural g clef is implemented.
5396 @subsection Ancient flags
5401 Use the @code{flag-style} property of grob @internalsref{Stem} to
5402 select ancient flags. Besides the @code{default} flag style,
5403 only @code{mensural} style is supported
5406 @lilypond[fragment,raggedright,verbatim]
5407 \override Stem #'flag-style = #'mensural
5408 \override Stem #'thickness = #1.0
5409 \override NoteHead #'style = #'mensural
5411 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
5412 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
5416 Note that the innermost flare of each mensural flag always is
5417 vertically aligned with a staff line. If you do not like this
5418 behavior, you can set the @code{adjust-if-on-staffline} property of
5419 grob @internalsref{Stem} to @code{##f}. Then, the vertical position
5420 of the end of each flare is different between notes on staff lines and
5421 notes between staff lines
5424 @lilypond[fragment,raggedright]
5425 \override Stem #'flag-style = #'mensural
5426 \override Stem #'thickness = #1.0
5427 \override Stem #'adjust-if-on-staffline = ##f
5428 \override NoteHead #'style = #'mensural
5430 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
5431 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
5435 There is no particular flag style for neo-mensural notation. Hence,
5436 when typesetting e.g. the incipit of a transcribed piece of mensural
5437 music, the default flag style should be used. There are no flags in
5438 Gregorian Chant notation.
5441 @node Ancient time signatures
5442 @subsection Ancient time signatures
5444 @cindex time signatures
5447 There is limited support for mensural time signatures. The
5448 glyphs are hard-wired to particular time fractions. In other words,
5449 to get a particular mensural signature glyph with the @code{\time n/m}
5450 command, @code{n} and @code{m} have to be chosen according to the
5457 \set Score.timing = ##f
5458 \set Score.barAlways = ##t
5459 s_\markup { "$\\backslash$time 4/4" }
5460 ^\markup { " " \musicglyph #"timesig-neo_mensural4/4" }
5462 s_\markup { "$\\backslash$time 2/2" }
5463 ^\markup { " " \musicglyph #"timesig-neo_mensural2/2" }
5465 s_\markup { "$\\backslash$time 6/4" }
5466 ^\markup { " " \musicglyph #"timesig-neo_mensural6/4" }
5468 s_\markup { "$\\backslash$time 6/8" }
5469 ^\markup { " " \musicglyph #"timesig-neo_mensural6/8" }
5471 s_\markup { "$\\backslash$time 3/2" }
5472 ^\markup { " " \musicglyph #"timesig-neo_mensural3/2" }
5474 s_\markup { "$\\backslash$time 3/4" }
5475 ^\markup { " " \musicglyph #"timesig-neo_mensural3/4" }
5477 s_\markup { "$\\backslash$time 9/4" }
5478 ^\markup { " " \musicglyph #"timesig-neo_mensural9/4" }
5480 s_\markup { "$\\backslash$time 9/8" }
5481 ^\markup { " " \musicglyph #"timesig-neo_mensural9/8" }
5483 s_\markup { "$\\backslash$time 4/8" }
5484 ^\markup { " " \musicglyph #"timesig-neo_mensural4/8" }
5486 s_\markup { "$\\backslash$time 2/4" }
5487 ^\markup { " " \musicglyph #"timesig-neo_mensural2/4" }
5495 \remove Staff_symbol_engraver
5496 \remove Clef_engraver
5497 \remove Time_signature_engraver
5504 Use the @code{style} property of grob @internalsref{TimeSignature} to
5505 select ancient time signatures. Supported styles are
5506 @code{neo_mensural} and @code{mensural}. The above table uses the
5507 @code{neo_mensural} style. This style is appropriate e.g. for the
5508 incipit of transcriptions of mensural pieces. The @code{mensural}
5509 style mimics the look of historical printings of the 16th century.
5511 @inputfileref{input/test,time.ly} gives an overview over all available
5512 ancient and modern styles.
5516 Program reference: @ref{Time signature} gives a general introduction into the use of time
5521 Mensural signature glyphs are mapped to time fractions in a hard-wired
5522 way. This mapping is sensible, but still arbitrary: given a mensural
5523 time signature, the time fraction represents a modern meter that
5524 usually will be a good choice when transcribing a mensural piece of
5525 music. For a particular piece of mensural music, however, the mapping
5526 may be unsatisfactory. In particular, the mapping assumes a fixed
5527 transcription of durations (e.g. brevis = half note in 2/2, i.e. 4:1).
5528 Some glyphs (such as the alternate glyph for 6/8 meter) are not at all
5529 accessible through the @code{\time} command.
5531 Mensural time signatures are supported typographically, but not yet
5532 musically. The internal representation of durations is
5533 based on a purely binary system; a ternary division such as 1 brevis =
5534 3 semibrevis (tempus perfectum) or 1 semibrevis = 3 minima (cum
5535 prolatione maiori) is not correctly handled: event times in ternary
5536 modes will be badly computed, resulting e.g. in horizontally
5537 misaligned note heads, and bar checks are likely to erroneously fail.
5539 The syntax and semantics of the @code{\time} command for mensural
5540 music is subject to change.
5543 @subsection Custodes
5548 A @emph{custos} (plural: @emph{custodes}; Latin word for `guard') is a
5549 symbol that appears at the end of a staff. It anticipates the pitch
5550 of the first note(s) of the following line and thus helps the player
5551 or singer to manage line breaks during performance, thus enhancing
5552 readability of a score.
5554 Custodes were frequently used in music notation until the 17th
5555 century. Nowadays, they have survived only in a few particular forms
5556 of musical notation such as contemporary editions of Gregorian chant
5557 like the @emph{editio vaticana}. There are different custos glyphs
5558 used in different flavors of notational style.
5560 For typesetting custodes, just put a @internalsref{Custos_engraver} into the
5561 @internalsref{Staff} context when declaring the @code{\paper} block,
5562 as shown in the following example
5568 \consists Custos_engraver
5569 Custos \override #'style = #'mensural
5574 The result looks like this
5577 @lilypond[raggedright]
5581 \override Staff.Custos #'style = #'mensural
5588 \consists Custos_engraver
5595 The custos glyph is selected by the @code{style} property. The styles
5596 supported are @code{vaticana}, @code{medicaea}, @code{hufnagel} and
5597 @code{mensural}. They are demonstrated in the following fragment
5602 \new Lyrics \lyrics {
5606 { " " \musicglyph #"custodes-vaticana-u0" }
5610 { " " \musicglyph #"custodes-medicaea-u0" }
5615 { " " \musicglyph #"custodes-hufnagel-u0" }
5620 { " " \musicglyph #"custodes-mensural-u0" }
5633 Program reference: @internalsref{Custos}.
5635 Examples: @inputfileref{input/regression,custos.ly}.
5639 @subsection Divisiones
5645 A @emph{divisio} (plural: @emph{divisiones}; Latin word for
5646 `division') is a staff context symbol that is used to structure
5647 Gregorian music into phrases and sections. The musical meaning of
5648 @emph{divisio minima}, @emph{divisio maior} and @emph{divisio maxima}
5649 can be characterized as short, medium and long pause, somewhat like
5650 @ref{Breath marks}. The @emph{finalis} sign not only marks the end of
5651 a chant, but is also frequently used within a single
5652 antiphonal/responsorial chant to mark the end of each section.
5655 To use divisiones, include the file @code{gregorian-init.ly}. It
5656 contains definitions that you can apply by just inserting
5657 @code{\divisioMinima}, @code{\divisioMaior}, @code{\divisioMaxima},
5658 and @code{\finalis} at proper places in the input. Some editions use
5659 @emph{virgula} or @emph{caesura} instead of divisio minima.
5660 Therefore, @code{gregorian-init.ly} also defines @code{\virgula} and
5664 @lilypondfile[]{divisiones.ly}
5669 @cindex @code{\virgula}
5671 @cindex @code{\caesura}
5673 @cindex @code{\divisioMinima}
5674 @code{\divisioMinima},
5675 @cindex @code{\divisioMaior}
5676 @code{\divisioMaior},
5677 @cindex @code{\divisioMaxima}
5678 @code{\divisioMaxima},
5679 @cindex @code{\finalis}
5684 In this manual: @ref{Breath marks}.
5686 Program reference: @internalsref{BreathingSign}, @internalsref{BreathingSignEvent}.
5688 Examples: @inputfileref{input/test,divisiones.ly}.
5691 @subsection Ligatures
5695 @c TODO: Should double check if I recalled things correctly when I wrote
5696 @c down the following paragraph by heart.
5698 A ligature is a coherent graphical symbol that represents at least two
5699 distinct notes. Ligatures originally appeared in the manuscripts of
5700 Gregorian chant notation roughly since the 9th century to denote
5701 ascending or descending sequences of notes.
5703 Ligatures are entered by enclosing them in @code{\[} and @code{\]}.
5704 Some ligature styles may need additional input syntax specific for
5705 this particular type of ligature. By default, the
5706 @internalsref{LigatureBracket} engraver just puts a square bracket
5710 @lilypond[raggedright,verbatim]
5712 \notes \transpose c c' {
5721 To select a specific style of ligatures, a proper ligature engraver
5722 has to be added to the @internalsref{Voice} context, as explained in
5723 the following subsections. Only white mensural ligatures
5724 are supported with certain limitations.
5727 * White mensural ligatures::
5728 * Gregorian square neumes ligatures::
5731 @node White mensural ligatures
5732 @subsubsection White mensural ligatures
5734 @cindex Mensural ligatures
5735 @cindex White mensural ligatures
5737 There is limited support for white mensural ligatures.
5739 To engrave white mensural ligatures, in the paper block the
5740 @internalsref{Mensural_ligature_engraver} has to be put into the
5741 @internalsref{Voice} context, and remove the
5742 @internalsref{Ligature_bracket_engraver}
5748 \remove Ligature_bracket_engraver
5749 \consists Mensural_ligature_engraver
5754 There is no additional input language to describe the shape of a
5755 white mensural ligature. The shape is rather determined solely from
5756 the pitch and duration of the enclosed notes. While this approach may
5757 take a new user a while to get accustomed, it has the great advantage
5758 that the full musical information of the ligature is known internally.
5759 This is not only required for correct MIDI output, but also allows for
5760 automatic transcription of the ligatures.
5765 \set Score.timing = ##f
5766 \set Score.defaultBarType = "empty"
5767 \override NoteHead #'style = #'neo_mensural
5768 \override Staff.TimeSignature #'style = #'neo_mensural
5770 \[ g\longa c\breve a\breve f\breve d'\longa \]
5772 \[ e1 f1 a\breve g\longa \]
5775 @lilypond[raggedright]
5777 \notes \transpose c c' {
5778 \set Score.timing = ##f
5779 \set Score.defaultBarType = "empty"
5780 \override NoteHead #'style = #'neo_mensural
5781 \override Staff.TimeSignature #'style = #'neo_mensural
5783 \[ g\longa c\breve a\breve f\breve d'\longa \]
5785 \[ e1 f1 a\breve g\longa \]
5790 \remove Ligature_bracket_engraver
5791 \consists Mensural_ligature_engraver
5798 Without replacing @internalsref{Ligature_bracket_engraver} with
5799 @internalsref{Mensural_ligature_engraver}, the same music transcribes
5803 @lilypond[raggedright]
5805 \notes \transpose c c' {
5806 \set Score.timing = ##f
5807 \set Score.defaultBarType = "empty"
5808 \override NoteHead #'style = #'neo_mensural
5809 \override Staff.TimeSignature #'style = #'neo_mensural
5811 \[ g\longa c\breve a\breve f\breve d'\longa \]
5813 \[ e1 f1 a\breve g\longa \]
5821 The implementation is experimental; it may output strange warnings or
5822 even crash in some cases or produce weird results on more complex
5825 @node Gregorian square neumes ligatures
5826 @subsubsection Gregorian square neumes ligatures
5828 @cindex Square neumes ligatures
5829 @cindex Gregorian square neumes ligatures
5831 Gregorian square neumes notation (following the style of the Editio
5832 Vaticana) is under heavy development, but not yet really usable for
5833 production purposes. Core ligatures can already be typeset, but
5834 essential issues for serious typesetting are still under development,
5835 such as (among others) horizontal alignment of multiple ligatures,
5836 lyrics alignment and proper accidentals handling. Still, this section
5837 gives a sneak preview of what Gregorian chant may look like once it
5840 The following table contains the extended neumes table of the 2nd
5841 volume of the Antiphonale Romanum (@emph{Liber Hymnarius}), published
5842 1983 by the monks of Solesmes.
5844 @multitable @columnfractions .4 .2 .2 .2
5847 @b{Neuma aut@*Neumarum Elementa} @tab
5848 @b{Figurae@*Rectae} @tab
5849 @b{Figurae@*Liquescentes Auctae} @tab
5850 @b{Figurae@*Liquescentes Deminutae}
5852 @c TODO: \paper block is identical in all of the below examples.
5853 @c Therefore, it should somehow be included rather than duplicated all
5856 @c why not make identifiers in ly/engraver-init.ly? --hwn
5858 @c Because it's just used to typeset plain notes without
5859 @c a staff for demonstration purposes rather than something
5860 @c special of Gregorian chant notation. --jr
5866 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.5\cm]
5867 \include "gregorian-init.ly"
5869 \notes \transpose c c' {
5872 \noBreak s^\markup {"a"} \noBreak
5874 % Punctum Inclinatum
5876 \noBreak s^\markup {"b"}
5882 \remove "Bar_number_engraver"
5886 \remove "Clef_engraver"
5887 \remove "Key_engraver"
5888 \override StaffSymbol #'transparent = ##t
5889 \remove "Time_signature_engraver"
5890 \remove "Bar_engraver"
5891 minimumVerticalExtent = ##f
5895 \remove Ligature_bracket_engraver
5896 \consists Vaticana_ligature_engraver
5897 \override NoteHead #'style = #'vaticana_punctum
5898 \override Stem #'transparent = ##t
5906 @lilypond[noindent,staffsize=26,nofragment,linewidth=2.5\cm]
5907 \include "gregorian-init.ly"
5909 \notes \transpose c c' {
5910 % Punctum Auctum Ascendens
5911 \[ \auctum \ascendens b \]
5912 \noBreak s^\markup {"c"} \noBreak
5914 % Punctum Auctum Descendens
5915 \[ \auctum \descendens b \]
5916 \noBreak s^\markup {"d"} \noBreak
5918 % Punctum Inclinatum Auctum
5919 \[ \inclinatum \auctum b \]
5920 \noBreak s^\markup {"e"}
5926 \remove "Bar_number_engraver"
5930 \remove "Clef_engraver"
5931 \remove "Key_engraver"
5932 \override StaffSymbol #'transparent = ##t
5933 \remove "Time_signature_engraver"
5934 \remove "Bar_engraver"
5935 minimumVerticalExtent = ##f
5939 \remove Ligature_bracket_engraver
5940 \consists Vaticana_ligature_engraver
5941 \override NoteHead #'style = #'vaticana_punctum
5942 \override Stem #'transparent = ##t
5950 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5951 \include "gregorian-init.ly"
5953 \notes \transpose c c' {
5954 % Punctum Inclinatum Parvum
5955 \[ \inclinatum \deminutum b \]
5956 \noBreak s^\markup {"f"}
5962 \remove "Bar_number_engraver"
5966 \remove "Clef_engraver"
5967 \remove "Key_engraver"
5968 \override StaffSymbol #'transparent = ##t
5969 \remove "Time_signature_engraver"
5970 \remove "Bar_engraver"
5971 minimumVerticalExtent = ##f
5975 \remove Ligature_bracket_engraver
5976 \consists Vaticana_ligature_engraver
5977 \override NoteHead #'style = #'vaticana_punctum
5978 \override Stem #'transparent = ##t
5989 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5990 \include "gregorian-init.ly"
5992 \notes \transpose c c' {
5995 \noBreak s^\markup {"g"}
6001 \remove "Bar_number_engraver"
6005 \remove "Clef_engraver"
6006 \remove "Key_engraver"
6007 \override StaffSymbol #'transparent = ##t
6008 \remove "Time_signature_engraver"
6009 \remove "Bar_engraver"
6010 minimumVerticalExtent = ##f
6014 \remove Ligature_bracket_engraver
6015 \consists Vaticana_ligature_engraver
6016 \override NoteHead #'style = #'vaticana_punctum
6017 \override Stem #'transparent = ##t
6027 @code{3. Apostropha vel Stropha}
6030 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6031 \include "gregorian-init.ly"
6033 \notes \transpose c c' {
6036 \noBreak s^\markup {"h"}
6042 \remove "Bar_number_engraver"
6046 \remove "Clef_engraver"
6047 \remove "Key_engraver"
6048 \override StaffSymbol #'transparent = ##t
6049 \remove "Time_signature_engraver"
6050 \remove "Bar_engraver"
6051 minimumVerticalExtent = ##f
6055 \remove Ligature_bracket_engraver
6056 \consists Vaticana_ligature_engraver
6057 \override NoteHead #'style = #'vaticana_punctum
6058 \override Stem #'transparent = ##t
6066 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6067 \include "gregorian-init.ly"
6069 \notes \transpose c c' {
6071 \[ \stropha \auctum b \]
6072 \noBreak s^\markup {"i"}
6078 \remove "Bar_number_engraver"
6082 \remove "Clef_engraver"
6083 \remove "Key_engraver"
6084 \override StaffSymbol #'transparent = ##t
6085 \remove "Time_signature_engraver"
6086 \remove "Bar_engraver"
6087 minimumVerticalExtent = ##f
6091 \remove Ligature_bracket_engraver
6092 \consists Vaticana_ligature_engraver
6093 \override NoteHead #'style = #'vaticana_punctum
6094 \override Stem #'transparent = ##t
6106 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6107 \include "gregorian-init.ly"
6109 \notes \transpose c c' {
6112 \noBreak s^\markup {"j"}
6118 \remove "Bar_number_engraver"
6122 \remove "Clef_engraver"
6123 \remove "Key_engraver"
6124 \override StaffSymbol #'transparent = ##t
6125 \remove "Time_signature_engraver"
6126 \remove "Bar_engraver"
6127 minimumVerticalExtent = ##f
6131 \remove Ligature_bracket_engraver
6132 \consists Vaticana_ligature_engraver
6133 \override NoteHead #'style = #'vaticana_punctum
6134 \override Stem #'transparent = ##t
6144 @code{5. Clivis vel Flexa}
6147 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6148 \include "gregorian-init.ly"
6150 \notes \transpose c c' {
6159 \remove "Bar_number_engraver"
6163 \remove "Clef_engraver"
6164 \remove "Key_engraver"
6165 \override StaffSymbol #'transparent = ##t
6166 \remove "Time_signature_engraver"
6167 \remove "Bar_engraver"
6168 minimumVerticalExtent = ##f
6172 \remove Ligature_bracket_engraver
6173 \consists Vaticana_ligature_engraver
6174 \override NoteHead #'style = #'vaticana_punctum
6175 \override Stem #'transparent = ##t
6183 @lilypond[noindent,staffsize=26,nofragment,linewidth=2.0\cm]
6184 \include "gregorian-init.ly"
6186 \notes \transpose c c' {
6187 % Clivis Aucta Descendens
6188 \[ b \flexa \auctum \descendens g \]
6189 \noBreak s^\markup {"l"} \noBreak
6191 % Clivis Aucta Ascendens
6192 \[ b \flexa \auctum \ascendens g \]
6193 \noBreak s^\markup {"m"}
6199 \remove "Bar_number_engraver"
6203 \remove "Clef_engraver"
6204 \remove "Key_engraver"
6205 \override StaffSymbol #'transparent = ##t
6206 \remove "Time_signature_engraver"
6207 \remove "Bar_engraver"
6208 minimumVerticalExtent = ##f
6212 \remove Ligature_bracket_engraver
6213 \consists Vaticana_ligature_engraver
6214 \override NoteHead #'style = #'vaticana_punctum
6215 \override Stem #'transparent = ##t
6223 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6224 \include "gregorian-init.ly"
6226 \notes \transpose c c' {
6228 \[ b \flexa \deminutum g \]
6235 \remove "Bar_number_engraver"
6239 \remove "Clef_engraver"
6240 \remove "Key_engraver"
6241 \override StaffSymbol #'transparent = ##t
6242 \remove "Time_signature_engraver"
6243 \remove "Bar_engraver"
6244 minimumVerticalExtent = ##f
6248 \remove Ligature_bracket_engraver
6249 \consists Vaticana_ligature_engraver
6250 \override NoteHead #'style = #'vaticana_punctum
6251 \override Stem #'transparent = ##t
6259 @code{6. Podatus vel Pes}
6262 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6263 \include "gregorian-init.ly"
6265 \notes \transpose c c' {
6274 \remove "Bar_number_engraver"
6278 \remove "Clef_engraver"
6279 \remove "Key_engraver"
6280 \override StaffSymbol #'transparent = ##t
6281 \remove "Time_signature_engraver"
6282 \remove "Bar_engraver"
6283 minimumVerticalExtent = ##f
6287 \remove Ligature_bracket_engraver
6288 \consists Vaticana_ligature_engraver
6289 \override NoteHead #'style = #'vaticana_punctum
6290 \override Stem #'transparent = ##t
6298 @lilypond[noindent,staffsize=26,nofragment,linewidth=2.0\cm]
6299 \include "gregorian-init.ly"
6301 \notes \transpose c c' {
6302 % Pes Auctus Descendens
6303 \[ g \pes \auctum \descendens b \]
6304 \noBreak s^\markup {"p"} \noBreak
6306 % Pes Auctus Ascendens
6307 \[ g \pes \auctum \ascendens b \]
6308 \noBreak s^\markup {"q"}
6314 \remove "Bar_number_engraver"
6318 \remove "Clef_engraver"
6319 \remove "Key_engraver"
6320 \override StaffSymbol #'transparent = ##t
6321 \remove "Time_signature_engraver"
6322 \remove "Bar_engraver"
6323 minimumVerticalExtent = ##f
6327 \remove Ligature_bracket_engraver
6328 \consists Vaticana_ligature_engraver
6329 \override NoteHead #'style = #'vaticana_punctum
6330 \override Stem #'transparent = ##t
6338 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6339 \include "gregorian-init.ly"
6341 \notes \transpose c c' {
6343 \[ g \pes \deminutum b \]
6350 \remove "Bar_number_engraver"
6354 \remove "Clef_engraver"
6355 \remove "Key_engraver"
6356 \override StaffSymbol #'transparent = ##t
6357 \remove "Time_signature_engraver"
6358 \remove "Bar_engraver"
6359 minimumVerticalExtent = ##f
6363 \remove Ligature_bracket_engraver
6364 \consists Vaticana_ligature_engraver
6365 \override NoteHead #'style = #'vaticana_punctum
6366 \override Stem #'transparent = ##t
6374 @code{7. Pes Quassus}
6377 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6378 \include "gregorian-init.ly"
6380 \notes \transpose c c' {
6382 \[ \oriscus g \pes \virga b \]
6389 \remove "Bar_number_engraver"
6393 \remove "Clef_engraver"
6394 \remove "Key_engraver"
6395 \override StaffSymbol #'transparent = ##t
6396 \remove "Time_signature_engraver"
6397 \remove "Bar_engraver"
6398 minimumVerticalExtent = ##f
6402 \remove Ligature_bracket_engraver
6403 \consists Vaticana_ligature_engraver
6404 \override NoteHead #'style = #'vaticana_punctum
6405 \override Stem #'transparent = ##t
6413 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6414 \include "gregorian-init.ly"
6416 \notes \transpose c c' {
6417 % Pes Quassus Auctus Descendens
6418 \[ \oriscus g \pes \auctum \descendens b \]
6425 \remove "Bar_number_engraver"
6429 \remove "Clef_engraver"
6430 \remove "Key_engraver"
6431 \override StaffSymbol #'transparent = ##t
6432 \remove "Time_signature_engraver"
6433 \remove "Bar_engraver"
6434 minimumVerticalExtent = ##f
6438 \remove Ligature_bracket_engraver
6439 \consists Vaticana_ligature_engraver
6440 \override NoteHead #'style = #'vaticana_punctum
6441 \override Stem #'transparent = ##t
6450 @code{8. Quilisma Pes}
6453 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6454 \include "gregorian-init.ly"
6456 \notes \transpose c c' {
6458 \[ \quilisma g \pes b \]
6465 \remove "Bar_number_engraver"
6469 \remove "Clef_engraver"
6470 \remove "Key_engraver"
6471 \override StaffSymbol #'transparent = ##t
6472 \remove "Time_signature_engraver"
6473 \remove "Bar_engraver"
6474 minimumVerticalExtent = ##f
6478 \remove Ligature_bracket_engraver
6479 \consists Vaticana_ligature_engraver
6480 \override NoteHead #'style = #'vaticana_punctum
6481 \override Stem #'transparent = ##t
6489 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6490 \include "gregorian-init.ly"
6492 \notes \transpose c c' {
6493 % Quilisma Pes Auctus Descendens
6494 \[ \quilisma g \pes \auctum \descendens b \]
6501 \remove "Bar_number_engraver"
6505 \remove "Clef_engraver"
6506 \remove "Key_engraver"
6507 \override StaffSymbol #'transparent = ##t
6508 \remove "Time_signature_engraver"
6509 \remove "Bar_engraver"
6510 minimumVerticalExtent = ##f
6514 \remove Ligature_bracket_engraver
6515 \consists Vaticana_ligature_engraver
6516 \override NoteHead #'style = #'vaticana_punctum
6517 \override Stem #'transparent = ##t
6526 @code{9. Podatus Initio Debilis}
6529 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6530 \include "gregorian-init.ly"
6532 \notes \transpose c c' {
6533 % Pes Initio Debilis
6534 \[ \deminutum g \pes b \]
6541 \remove "Bar_number_engraver"
6545 \remove "Clef_engraver"
6546 \remove "Key_engraver"
6547 \override StaffSymbol #'transparent = ##t
6548 \remove "Time_signature_engraver"
6549 \remove "Bar_engraver"
6550 minimumVerticalExtent = ##f
6554 \remove Ligature_bracket_engraver
6555 \consists Vaticana_ligature_engraver
6556 \override NoteHead #'style = #'vaticana_punctum
6557 \override Stem #'transparent = ##t
6565 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6566 \include "gregorian-init.ly"
6568 \notes \transpose c c' {
6569 % Pes Auctus Descendens Initio Debilis
6570 \[ \deminutum g \pes \auctum \descendens b \]
6577 \remove "Bar_number_engraver"
6581 \remove "Clef_engraver"
6582 \remove "Key_engraver"
6583 \override StaffSymbol #'transparent = ##t
6584 \remove "Time_signature_engraver"
6585 \remove "Bar_engraver"
6586 minimumVerticalExtent = ##f
6590 \remove Ligature_bracket_engraver
6591 \consists Vaticana_ligature_engraver
6592 \override NoteHead #'style = #'vaticana_punctum
6593 \override Stem #'transparent = ##t
6605 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6606 \include "gregorian-init.ly"
6608 \notes \transpose c c' {
6610 \[ a \pes b \flexa g \]
6617 \remove "Bar_number_engraver"
6621 \remove "Clef_engraver"
6622 \remove "Key_engraver"
6623 \override StaffSymbol #'transparent = ##t
6624 \remove "Time_signature_engraver"
6625 \remove "Bar_engraver"
6626 minimumVerticalExtent = ##f
6630 \remove Ligature_bracket_engraver
6631 \consists Vaticana_ligature_engraver
6632 \override NoteHead #'style = #'vaticana_punctum
6633 \override Stem #'transparent = ##t
6641 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6642 \include "gregorian-init.ly"
6644 \notes \transpose c c' {
6645 % Torculus Auctus Descendens
6646 \[ a \pes b \flexa \auctum \descendens g \]
6653 \remove "Bar_number_engraver"
6657 \remove "Clef_engraver"
6658 \remove "Key_engraver"
6659 \override StaffSymbol #'transparent = ##t
6660 \remove "Time_signature_engraver"
6661 \remove "Bar_engraver"
6662 minimumVerticalExtent = ##f
6666 \remove Ligature_bracket_engraver
6667 \consists Vaticana_ligature_engraver
6668 \override NoteHead #'style = #'vaticana_punctum
6669 \override Stem #'transparent = ##t
6677 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6678 \include "gregorian-init.ly"
6680 \notes \transpose c c' {
6681 % Torculus Deminutus
6682 \[ a \pes b \flexa \deminutum g \]
6689 \remove "Bar_number_engraver"
6693 \remove "Clef_engraver"
6694 \remove "Key_engraver"
6695 \override StaffSymbol #'transparent = ##t
6696 \remove "Time_signature_engraver"
6697 \remove "Bar_engraver"
6698 minimumVerticalExtent = ##f
6702 \remove Ligature_bracket_engraver
6703 \consists Vaticana_ligature_engraver
6704 \override NoteHead #'style = #'vaticana_punctum
6705 \override Stem #'transparent = ##t
6713 @code{11. Torculus Initio Debilis}
6716 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6717 \include "gregorian-init.ly"
6719 \notes \transpose c c' {
6720 % Torculus Initio Debilis
6721 \[ \deminutum a \pes b \flexa g \]
6728 \remove "Bar_number_engraver"
6732 \remove "Clef_engraver"
6733 \remove "Key_engraver"
6734 \override StaffSymbol #'transparent = ##t
6735 \remove "Time_signature_engraver"
6736 \remove "Bar_engraver"
6737 minimumVerticalExtent = ##f
6741 \remove Ligature_bracket_engraver
6742 \consists Vaticana_ligature_engraver
6743 \override NoteHead #'style = #'vaticana_punctum
6744 \override Stem #'transparent = ##t
6752 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6753 \include "gregorian-init.ly"
6755 \notes \transpose c c' {
6756 % Torculus Auctus Descendens Initio Debilis
6757 \[ \deminutum a \pes b \flexa \auctum \descendens g \]
6764 \remove "Bar_number_engraver"
6768 \remove "Clef_engraver"
6769 \remove "Key_engraver"
6770 \override StaffSymbol #'transparent = ##t
6771 \remove "Time_signature_engraver"
6772 \remove "Bar_engraver"
6773 minimumVerticalExtent = ##f
6777 \remove Ligature_bracket_engraver
6778 \consists Vaticana_ligature_engraver
6779 \override NoteHead #'style = #'vaticana_punctum
6780 \override Stem #'transparent = ##t
6788 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6789 \include "gregorian-init.ly"
6791 \notes \transpose c c' {
6792 % Torculus Deminutus Initio Debilis
6793 \[ \deminutum a \pes b \flexa \deminutum g \]
6800 \remove "Bar_number_engraver"
6804 \remove "Clef_engraver"
6805 \remove "Key_engraver"
6806 \override StaffSymbol #'transparent = ##t
6807 \remove "Time_signature_engraver"
6808 \remove "Bar_engraver"
6809 minimumVerticalExtent = ##f
6813 \remove Ligature_bracket_engraver
6814 \consists Vaticana_ligature_engraver
6815 \override NoteHead #'style = #'vaticana_punctum
6816 \override Stem #'transparent = ##t
6824 @code{12. Porrectus}
6827 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6828 \include "gregorian-init.ly"
6830 \notes \transpose c c' {
6832 \[ a \flexa g \pes b \]
6839 \remove "Bar_number_engraver"
6843 \remove "Clef_engraver"
6844 \remove "Key_engraver"
6845 \override StaffSymbol #'transparent = ##t
6846 \remove "Time_signature_engraver"
6847 \remove "Bar_engraver"
6848 minimumVerticalExtent = ##f
6852 \remove Ligature_bracket_engraver
6853 \consists Vaticana_ligature_engraver
6854 \override NoteHead #'style = #'vaticana_punctum
6855 \override Stem #'transparent = ##t
6863 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6864 \include "gregorian-init.ly"
6866 \notes \transpose c c' {
6867 % Porrectus Auctus Descendens
6868 \[ a \flexa g \pes \auctum \descendens b \]
6875 \remove "Bar_number_engraver"
6879 \remove "Clef_engraver"
6880 \remove "Key_engraver"
6881 \override StaffSymbol #'transparent = ##t
6882 \remove "Time_signature_engraver"
6883 \remove "Bar_engraver"
6884 minimumVerticalExtent = ##f
6888 \remove Ligature_bracket_engraver
6889 \consists Vaticana_ligature_engraver
6890 \override NoteHead #'style = #'vaticana_punctum
6891 \override Stem #'transparent = ##t
6899 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6900 \include "gregorian-init.ly"
6902 \notes \transpose c c' {
6903 % Porrectus Deminutus
6904 \[ a \flexa g \pes \deminutum b \]
6911 \remove "Bar_number_engraver"
6915 \remove "Clef_engraver"
6916 \remove "Key_engraver"
6917 \override StaffSymbol #'transparent = ##t
6918 \remove "Time_signature_engraver"
6919 \remove "Bar_engraver"
6920 minimumVerticalExtent = ##f
6924 \remove Ligature_bracket_engraver
6925 \consists Vaticana_ligature_engraver
6926 \override NoteHead #'style = #'vaticana_punctum
6927 \override Stem #'transparent = ##t
6938 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6939 \include "gregorian-init.ly"
6941 \notes \transpose c c' {
6943 \[ \virga b \inclinatum a \inclinatum g \]
6950 \remove "Bar_number_engraver"
6954 \remove "Clef_engraver"
6955 \remove "Key_engraver"
6956 \override StaffSymbol #'transparent = ##t
6957 \remove "Time_signature_engraver"
6958 \remove "Bar_engraver"
6959 minimumVerticalExtent = ##f
6963 \remove Ligature_bracket_engraver
6964 \consists Vaticana_ligature_engraver
6965 \override NoteHead #'style = #'vaticana_punctum
6966 \override Stem #'transparent = ##t
6974 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6975 \include "gregorian-init.ly"
6977 \notes \transpose c c' {
6979 \[ \virga b \inclinatum a \inclinatum \auctum g \]
6986 \remove "Bar_number_engraver"
6990 \remove "Clef_engraver"
6991 \remove "Key_engraver"
6992 \override StaffSymbol #'transparent = ##t
6993 \remove "Time_signature_engraver"
6994 \remove "Bar_engraver"
6995 minimumVerticalExtent = ##f
6999 \remove Ligature_bracket_engraver
7000 \consists Vaticana_ligature_engraver
7001 \override NoteHead #'style = #'vaticana_punctum
7002 \override Stem #'transparent = ##t
7010 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
7011 \include "gregorian-init.ly"
7013 \notes \transpose c c' {
7014 % Climacus Deminutus
7015 \[ \virga b \inclinatum a \inclinatum \deminutum g \]
7022 \remove "Bar_number_engraver"
7026 \remove "Clef_engraver"
7027 \remove "Key_engraver"
7028 \override StaffSymbol #'transparent = ##t
7029 \remove "Time_signature_engraver"
7030 \remove "Bar_engraver"
7031 minimumVerticalExtent = ##f
7035 \remove Ligature_bracket_engraver
7036 \consists Vaticana_ligature_engraver
7037 \override NoteHead #'style = #'vaticana_punctum
7038 \override Stem #'transparent = ##t
7046 @code{14. Scandicus}
7049 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
7050 \include "gregorian-init.ly"
7052 \notes \transpose c c' {
7054 \[ g \pes a \virga b \]
7061 \remove "Bar_number_engraver"
7065 \remove "Clef_engraver"
7066 \remove "Key_engraver"
7067 \override StaffSymbol #'transparent = ##t
7068 \remove "Time_signature_engraver"
7069 \remove "Bar_engraver"
7070 minimumVerticalExtent = ##f
7074 \remove Ligature_bracket_engraver
7075 \consists Vaticana_ligature_engraver
7076 \override NoteHead #'style = #'vaticana_punctum
7077 \override Stem #'transparent = ##t
7085 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
7086 \include "gregorian-init.ly"
7088 \notes \transpose c c' {
7089 % Scandicus Auctus Descendens
7090 \[ g \pes a \pes \auctum \descendens b \]
7097 \remove "Bar_number_engraver"
7101 \remove "Clef_engraver"
7102 \remove "Key_engraver"
7103 \override StaffSymbol #'transparent = ##t
7104 \remove "Time_signature_engraver"
7105 \remove "Bar_engraver"
7106 minimumVerticalExtent = ##f
7110 \remove Ligature_bracket_engraver
7111 \consists Vaticana_ligature_engraver
7112 \override NoteHead #'style = #'vaticana_punctum
7113 \override Stem #'transparent = ##t
7121 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
7122 \include "gregorian-init.ly"
7124 \notes \transpose c c' {
7125 % Scandicus Deminutus
7126 \[ g \pes a \pes \deminutum b \]
7133 \remove "Bar_number_engraver"
7137 \remove "Clef_engraver"
7138 \remove "Key_engraver"
7139 \override StaffSymbol #'transparent = ##t
7140 \remove "Time_signature_engraver"
7141 \remove "Bar_engraver"
7142 minimumVerticalExtent = ##f
7146 \remove Ligature_bracket_engraver
7147 \consists Vaticana_ligature_engraver
7148 \override NoteHead #'style = #'vaticana_punctum
7149 \override Stem #'transparent = ##t
7160 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
7161 \include "gregorian-init.ly"
7163 \notes \transpose c c' {
7165 \[ g \oriscus a \pes \virga b \]
7172 \remove "Bar_number_engraver"
7176 \remove "Clef_engraver"
7177 \remove "Key_engraver"
7178 \override StaffSymbol #'transparent = ##t
7179 \remove "Time_signature_engraver"
7180 \remove "Bar_engraver"
7181 minimumVerticalExtent = ##f
7185 \remove Ligature_bracket_engraver
7186 \consists Vaticana_ligature_engraver
7187 \override NoteHead #'style = #'vaticana_punctum
7188 \override Stem #'transparent = ##t
7196 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
7197 \include "gregorian-init.ly"
7199 \notes \transpose c c' {
7200 % Salicus Auctus Descendens
7201 \[ g \oriscus a \pes \auctum \descendens b \]
7208 \remove "Bar_number_engraver"
7212 \remove "Clef_engraver"
7213 \remove "Key_engraver"
7214 \override StaffSymbol #'transparent = ##t
7215 \remove "Time_signature_engraver"
7216 \remove "Bar_engraver"
7217 minimumVerticalExtent = ##f
7221 \remove Ligature_bracket_engraver
7222 \consists Vaticana_ligature_engraver
7223 \override NoteHead #'style = #'vaticana_punctum
7224 \override Stem #'transparent = ##t
7236 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
7237 \include "gregorian-init.ly"
7239 \notes \transpose c c' {
7241 \[ \stropha b \stropha b \stropha a \]
7248 \remove "Bar_number_engraver"
7252 \remove "Clef_engraver"
7253 \remove "Key_engraver"
7254 \override StaffSymbol #'transparent = ##t
7255 \remove "Time_signature_engraver"
7256 \remove "Bar_engraver"
7257 minimumVerticalExtent = ##f
7261 \remove Ligature_bracket_engraver
7262 \consists Vaticana_ligature_engraver
7263 \override NoteHead #'style = #'vaticana_punctum
7264 \override Stem #'transparent = ##t
7276 Unlike most other neumes notation systems, the input language for
7277 neumes does not necessarily reflect directly the typographical
7278 appearance, but is designed to solely focuse on musical meaning. For
7279 example, @code{\[ a \pes b \flexa g \]} produces a Torculus consisting
7280 of three Punctum heads, while @code{\[ a \flexa g \pes b \]} produces
7281 a Porrectus with a curved flexa shape and only a single Punctum head.
7282 There is no command to explicitly typeset the curved flexa shape; the
7283 decision of when to typeset a curved flexa shape is purely taken from
7284 the musical input. The idea of this approach is to separate the
7285 musical aspects of the input from the notation style of the output.
7286 This way, the same input can be reused to typeset the same music in a
7287 different style of Gregorian chant notation.
7289 The following table shows the code fragments that produce the
7290 ligatures in the above neumes table. The letter in the first column
7291 in each line of the below table indicates to which ligature in the
7292 above table it refers. The second column gives the name of the
7293 ligature. The third column shows the code fragment that produces this
7294 ligature, using @code{g}, @code{a} and @code{b} as example pitches.
7296 @multitable @columnfractions .1 .4 .5
7310 Punctum Inclinatum @tab
7311 @code{\[ \inclinatum b \]}
7315 Punctum Auctum Ascendens @tab
7316 @code{\[ \auctum \ascendens b \]}
7320 Punctum Auctum Descendens @tab
7321 @code{\[ \auctum \descendens b \]}
7325 Punctum Inclinatum Auctum @tab
7326 @code{\[ \inclinatum \auctum b \]}
7330 Punctum Inclinatum Parvum @tab
7331 @code{\[ \inclinatum \deminutum b \]}
7336 @code{\[ \virga b \]}
7341 @code{\[ \stropha b \]}
7346 @code{\[ \stropha \auctum b \]}
7351 @code{\[ \oriscus b \]}
7355 Clivis vel Flexa @tab
7356 @code{\[ b \flexa g \]}
7360 Clivis Aucta Descendens @tab
7361 @code{\[ b \flexa \auctum \descendens g \]}
7365 Clivis Aucta Ascendens @tab
7366 @code{\[ b \flexa \auctum \ascendens g \]}
7371 @code{\[ b \flexa \deminutum g \]}
7375 Podatus vel Pes @tab
7376 @code{\[ g \pes b \]}
7380 Pes Auctus Descendens @tab
7381 @code{\[ g \pes \auctum \descendens b \]}
7385 Pes Auctus Ascendens @tab
7386 @code{\[ g \pes \auctum \ascendens b \]}
7391 @code{\[ g \pes \deminutum b \]}
7396 @code{\[ \oriscus g \pes \virga b \]}
7400 Pes Quassus Auctus Descendens @tab
7401 @code{\[ \oriscus g \pes \auctum \descendens b \]}
7406 @code{\[ \quilisma g \pes b \]}
7410 Quilisma Pes Auctus Descendens @tab
7411 @code{\[ \quilisma g \pes \auctum \descendens b \]}
7415 Pes Initio Debilis @tab
7416 @code{\[ \deminutum g \pes b \]}
7420 Pes Auctus Descendens Initio Debilis @tab
7421 @code{\[ \deminutum g \pes \auctum \descendens b \]}
7426 @code{\[ a \pes b \flexa g \]}
7430 Torculus Auctus Descendens @tab
7431 @code{\[ a \pes b \flexa \auctum \descendens g \]}
7435 Torculus Deminutus @tab
7436 @code{\[ a \pes b \flexa \deminutum g \]}
7440 Torculus Initio Debilis @tab
7441 @code{\[ \deminutum a \pes b \flexa g \]}
7445 Torculus Auctus Descendens Initio Debilis @tab
7446 @code{\[ \deminutum a \pes b \flexa \auctum \descendens g \]}
7450 Torculus Deminutus Initio Debilis @tab
7451 @code{\[ \deminutum a \pes b \flexa \deminutum g \]}
7456 @code{\[ a \flexa g \pes b \]}
7460 Porrectus Auctus Descendens @tab
7461 @code{\[ a \flexa g \pes \auctum \descendens b \]}
7465 Porrectus Deminutus @tab
7466 @code{\[ a \flexa g \pes \deminutum b \]}
7471 @code{\[ \virga b \inclinatum a \inclinatum g \]}
7475 Climacus Auctus @tab
7476 @code{\[ \virga b \inclinatum a \inclinatum \auctum g \]}
7480 Climacus Deminutus @tab
7481 @code{\[ \virga b \inclinatum a \inclinatum \deminutum g \]}
7486 @code{\[ g \pes a \virga b \]}
7490 Scandicus Auctus Descendens @tab
7491 @code{\[ g \pes a \pes \auctum \descendens b \]}
7495 Scandicus Deminutus @tab
7496 @code{\[ g \pes a \pes \deminutum b \]}
7501 @code{\[ g \oriscus a \pes \virga b \]}
7505 Salicus Auctus Descendens @tab
7506 @code{\[ g \oriscus a \pes \auctum \descendens b \]}
7511 @code{\[ \stropha b \stropha b \stropha a \]}
7517 The following head prefixes are supported
7519 @cindex @code{\virga}
7521 @cindex @code{\stropha}
7523 @cindex @code{\inclinatum}
7525 @cindex @code{\auctum}
7527 @cindex @code{\descendens}
7529 @cindex @code{\ascendens}
7531 @cindex @code{\oriscus}
7533 @cindex @code{\quilisma}
7535 @cindex @code{\deminutum}
7538 Head prefixes can be accumulated, though restrictions apply. For
7539 example, either @code{\descendens} or @code{\ascendens} can be applied
7540 to a head, but not both to the same head.
7543 @cindex @code{\flexa}
7544 Two adjacent heads can be tied together with the @code{\pes} and
7545 @code{\flexa} infix commands for a rising and falling line of melody,
7550 @node Vaticana style contexts
7551 @subsection Vaticana style contexts
7553 @cindex VaticanaVoiceContext
7554 @cindex VaticanaStaffContext
7556 The predefined @code{VaticanaVoiceContext} and
7557 @code{VaticanaStaffContext} can be used to easily engrave a piece of
7558 Gregorian Chant in the style of the Editio Vaticana. These contexts
7559 initialize all relevant context properties and grob properties to
7560 proper values. With these contexts, you can immediately go ahead
7561 entering the chant, as the following short excerpt demonstrates
7564 @lilypond[raggedright,verbatim,noindent]
7565 \include "gregorian-init.ly"
7568 \context VaticanaVoice = "cantus" {
7569 \override Score.BarNumber #'transparent = ##t
7571 \[ c'\melisma c' \flexa a \]
7572 \[ a \flexa \deminutum g\melismaEnd \]
7574 \[ f\melisma \pes a c' c' \pes d'\melismaEnd \]
7575 c' \divisioMinima \break
7576 \[ c'\melisma c' \flexa a \]
7577 \[ a \flexa \deminutum g\melismaEnd \] f \divisioMinima
7580 \lyricsto "cantus" \new Lyrics \lyrics {
7581 San- ctus, San- ctus, San- ctus
7589 @subsection Figured bass
7591 @cindex Basso continuo
7593 @c TODO: musicological blurb about FB
7596 LilyPond has limited support for figured bass
7599 @lilypond[verbatim,fragment]
7601 \context Voice \notes { \clef bass dis4 c d ais }
7602 \context FiguredBass \figures {
7603 < 6 >4 < 7 >8 < 6+ [_!] >
7610 The support for figured bass consists of two parts: there is an input
7611 mode, introduced by @code{\figures}, where you can enter bass figures
7612 as numbers, and there is a context called @internalsref{FiguredBass} that
7613 takes care of making @internalsref{BassFigure} objects.
7615 In figures input mode, a group of bass figures is delimited by
7616 @code{<} and @code{>}. The duration is entered after the @code{>>}
7622 \context FiguredBass
7627 Accidentals are added when you append @code{-}, @code{!} and @code{+}
7635 \context FiguredBass
7636 \figures { <4- 6+ 7!> }
7640 Spaces or dashes may be inserted by using @code{_}. Brackets are
7641 introduced with @code{[} and @code{]}
7648 \context FiguredBass
7649 \figures { < [4 6] 8 [_! 12]> }
7653 Although the support for figured bass may superficially resemble chord
7654 support, it works much simpler. The @code{\figures} mode simply
7655 stores the numbers , and @internalsref{FiguredBass} context prints
7656 them as entered. There is no conversion to pitches, and no
7657 realizations of the bass are played in the MIDI file.
7659 Internally, the code produces markup texts. You can use any of the
7660 markup text properties to override formatting. For example, the
7661 vertical spacing of the figures may be set with @code{baseline-skip}.
7665 Program reference: @internalsref{BassFigureEvent} music, @internalsref{BassFigure} object,
7666 and @internalsref{FiguredBass} context.
7670 Slash notation for alterations is not supported.
7672 @node Contemporary notation
7673 @section Contemporary notation
7675 In the 20th century, composers have greatly expanded the musical
7676 vocabulary. With this expansion, many innovations in musical notation
7677 have been tried. The book by Stone (1980) gives a comprehensive
7678 overview (see @ref{Literature list}). In general, the use of new,
7679 innovative notation makes a piece harder to understand and perform and
7680 its use should therefore be avoided if possible. For this reason,
7681 support for contemporary notation in LilyPond is limited.
7690 @subsection Clusters
7694 A cluster indicates a continuous range of pitches to be played. They
7695 can be denoted as the envelope of a set of notes. They are entered by
7696 applying the function @code{notes-to-clusters} to a sequence of
7700 @lilypond[relative=2,verbatim]
7701 \apply #notes-to-clusters { <c e > <b f'> }
7705 The following example (from
7706 @inputfileref{input/regression,cluster.ly}) shows what the result
7710 @lilypondfile[]{cluster.ly}
7713 Ordinary notes and clusters can be put together in the same staff,
7714 even simultaneously. In such a case no attempt is made to
7715 automatically avoid collisions between ordinary notes and clusters.
7719 Program reference: @internalsref{ClusterSpanner},
7720 @internalsref{ClusterSpannerBeacon},
7721 @internalsref{Cluster_spanner_engraver}, and
7722 @internalsref{ClusterNoteEvent}.
7724 Examples: @inputfileref{input/regression,cluster.ly}.
7728 Music expressions like @code{<< @{ g8 e8 @} a4 >>} are not printed
7729 accurately. Use @code{<g a>8 <e a>8} instead.
7734 @subsection Fermatas
7740 Contemporary music notation frequently uses special fermata symbols to
7741 indicate fermatas of differing lengths. The following fermatas are
7745 @lilypond[raggedright]
7768 \context Lyrics \lyrics {
7769 \override LyricText #'font-family = #'typewriter
7770 "shortfermata" "fermata" "longfermata" "verylongfermata"
7777 See @ref{Articulations} for general instructions how to apply scripts
7778 such as fermatas to a @code{\notes@{@}} block.
7781 @node Special notation
7782 @section Special notation
7786 * Easy Notation note heads::
7790 @subsection Balloon help
7792 Elements of notation can be marked and named with the help of a square
7793 balloon. The primary purpose of this feature is to explain notation.
7795 The following example demonstrates its use.
7798 @lilypond[verbatim,fragment,raggedright,relative=2]
7801 #(add-balloon-text 'NoteHead "heads, or tails?"
7808 The function @code{add-balloon-text} takes the name of a grob, the
7809 label to print and where to put the label relative to the object. In
7810 the above example, the text ``heads or tails?'' ends 3 spaces below
7814 @cindex notation, explaining
7818 Program reference: @internalsref{text-balloon-interface}.
7820 Examples: @inputfileref{input/regression,balloon.ly}.
7822 @node Easy Notation note heads
7823 @subsection Easy Notation note heads
7825 @cindex easy notation
7828 The `easy play' note head includes a name inside the head. It is
7829 used in music for beginners
7832 @lilypond[raggedright,verbatim,staffsize=26]
7838 The command @code{\setEasyHeads} overrides settings for the
7839 @internalsref{NoteHead} object. To make the letters readable, it has
7840 to be printed in a large font size. To print with a larger font, see
7841 @ref{Setting global staff size}.
7846 If you view the result with Xdvi, staff lines may show through the
7847 letters. Printing the PostScript file obtained does produce the
7852 @cindex \setEasyHeads
7853 @code{\setEasyHeads}
7859 Entered music can also be converted to MIDI output. The performance
7860 is intended for proof-hearing the music for errors.
7862 Ties, dynamics and tempo changes are interpreted. Dynamic marks,
7863 crescendi and decrescendi translate into MIDI volume levels. Dynamic
7864 marks translate to a fixed fraction of the available MIDI volume
7865 range, crescendi and decrescendi make the volume vary linearly between
7866 their two extremities. The fractions can be adjusted by
7867 @code{dynamicAbsoluteVolumeFunction} in @internalsref{Voice} context.
7868 For each type of MIDI instrument, a volume range can be defined. This
7869 gives a basic equalizer control, which can enhance the quality of
7870 the MIDI output remarkably. The equalizer can be controlled by
7871 setting @code{instrumentEqualizer}.
7875 Many musically interesting effects, such as swing, articulation,
7876 slurring, etc., are not translated to MIDI.
7878 The MIDI output allocates a channel for each Staff, and one for global
7879 settings. Hence, the MIDI file should not have more than 15 staves
7880 (or 14 if you do not use drums). Other staves will remain silent.
7885 * MIDI instrument names::
7890 @subsection MIDI block
7894 The MIDI block is analogous to the paper block, but it is somewhat
7895 simpler. The @code{\midi} block can contain
7899 @item a @code{\tempo} definition, and
7900 @item context definitions.
7903 A number followed by a period is interpreted as a real number, so
7904 for setting the tempo for dotted notes, an extra space should be
7905 inserted, for example
7908 \midi @{ \tempo 4 . = 120 @}
7912 @cindex context definition
7914 Context definitions follow precisely the same syntax as within the
7915 \paper block. Translation modules for sound are called performers.
7916 The contexts for MIDI output are defined in @file{ly/performer-init.ly}.
7919 @node MIDI instrument names
7920 @subsection MIDI instrument names
7922 @cindex instrument names
7923 @cindex @code{Staff.midiInstrument}
7925 The MIDI instrument name is set by the @code{Staff.midiInstrument}
7926 property. The instrument name should be chosen from the list in
7927 @ref{MIDI instruments}.
7931 If the selected string does not exactly match, the default is used,
7932 which is the Grand Piano.