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 automagically fill in these menus before saving changes
8 @c FIXME: singular vs. plural: Beams/Beam
12 @chapter Notation manual
14 This chapter describes all the different types of notation supported
15 by LilyPond. It is intended as a reference for users that are already
16 somewhat familiar with using LilyPond.
20 * Easier music entry::
34 * Contemporary notation::
42 @c FIXME: Note entry vs Music entry at top level menu is confusing.
48 The basic elements of any piece of music are the notes. This section
49 is about basic notation elements notes, rests and related constructs,
50 such as stems, tuplets and ties.
55 * Chromatic alterations::
70 A note is printed by specifying its pitch and then its duration:
71 @footnote{Notes constitute the most basic elements of LilyPond input,
72 but they do not form valid input on their own without a @code{\score}
73 block. However, for the sake of brevity and simplicity we will
74 generally omit @code{\score} blocks and @code{\paper} declarations in
77 @lilypond[fragment,verbatim]
86 @cindex Note specification
88 @cindex entering notes
90 The most common syntax for pitch entry is used in @code{\chords} and
91 @code{\notes} mode. In Note and Chord mode, pitches may be designated
92 by names. The notes are specified by the letters @code{a} through
93 @code{g}, while the octave is formed with notes ranging from @code{c}
94 to @code{b}. The pitch @code{c} is an octave below middle C and the
95 letters span the octave above that C:
97 @lilypond[fragment,verbatim]
99 a,4 b, c d e f g a b c' d' e' \clef treble f' g' a' b' c''
102 @cindex note names, Dutch
104 A sharp is formed by adding @code{-is} to the end of a pitch name and
105 a flat is formed by adding @code{-es}. Double sharps and double flats
106 are obtained by adding @code{-isis} or @code{-eses}. These
107 names are the Dutch note names. In Dutch, @code{aes} is contracted to
108 @code{as}, but both forms are accepted. Similarly, both
109 @code{es} and @code{ees} are accepted.
111 Half-flats and half-sharps are formed by adding @code{-eh} and
112 @code{-ih}; the following is a series of Cs with increasing pitches:
114 @cindex quarter tones
115 @cindex semi-flats, semi-sharps
117 @lilypond[verbatim,relative=2]
129 There are predefined sets of note names for various other languages.
130 To use them, include the language specific init file. For
131 example: @code{\include "english.ly"}. The available language files
132 and the note names they define are:
137 Note Names sharp flat
138 nederlands.ly c d e f g a bes b -is -es
139 english.ly c d e f g a bf b -s/-sharp -f/-flat
141 deutsch.ly c d e f g a b h -is -es
142 norsk.ly c d e f g a b h -iss/-is -ess/-es
143 svenska.ly c d e f g a b h -iss -ess
144 italiano.ly do re mi fa sol la sib si -d -b
145 catalan.ly do re mi fa sol la sib si -d/-s -b
146 espanol.ly do re mi fa sol la sib si -s -b
155 The optional octave specification takes the form of a series of
156 single quote (`@code{'}') characters or a series of comma
157 (`@code{,}') characters. Each @code{'} raises the pitch by one
158 octave; each @code{,} lowers the pitch by an octave:
160 @lilypond[fragment,verbatim,center]
161 c' c'' es' g' as' gisis' ais'
167 Notes can be hidden and unhidden with the following commands:
169 @cindex @code{\hideNotes}
171 @cindex @code{\unHideNotes}
177 Internals: @internalsref{NoteEvent}, and @internalsref{NoteHead}.
179 @node Chromatic alterations
180 @subsection Chromatic alterations
182 Normally accidentals are printed automatically, but you may also
183 print them manually. A reminder accidental
184 @cindex reminder accidental
186 can be forced by adding an exclamation mark @code{!}
187 after the pitch. A cautionary accidental
188 @cindex cautionary accidental
189 @cindex parenthesized accidental
190 (i.e. an accidental within parentheses) can be obtained by adding the
191 question mark `@code{?}' after the pitch:
193 @lilypond[fragment,verbatim]
194 cis' cis' cis'! cis'?
198 The automatic production of accidentals can be tuned in many
199 ways. For more information, refer to @ref{Accidentals}.
204 A chord is formed by a enclosing a set of pitches in @code{<} and
205 @code{>}. A chord may be followed by a duration, and a set of
206 articulations, just like simple notes.
216 Rests are entered like notes, with the note name @code{r}:
218 @lilypond[raggedright,verbatim]
222 Whole bar rests, centered in middle of the bar,
223 must be done with multi measure rests. They are discussed in
224 @ref{Multi measure rests}.
227 A rest's vertical position may be explicitly specified by entering a
228 note with the @code{\rest} keyword appended. This makes manual
229 formatting in polyphonic music easier. Rest collision testing will
230 leave these rests alone:
232 @lilypond[raggedright,verbatim]
238 Internals: @internalsref{RestEvent}, and @internalsref{Rest}.
245 @cindex Invisible rest
248 An invisible rest (also called a `skip') can be entered like a note
249 with note name `@code{s}' or with @code{\skip @var{duration}}:
251 @lilypond[raggedright,verbatim]
255 The @code{s} syntax is only available in note mode and chord mode. In
256 other situations, you should use the @code{\skip} command:
258 @lilypond[raggedright,verbatim]
261 { \time 4/8 \skip 2 \time 4/4 }
262 \notes\relative c'' { a2 a1 }
267 The skip command is merely an empty musical placeholder. It does not
268 produce any output, not even transparent output.
270 The @code{s} skip command does create @internalsref{Staff} and
271 @internalsref{Voice} when necessary, similar to note and rest
272 commands. For example, the following results in an empty staff.
274 @lilypond[raggedright,verbatim]
275 \score { \notes { s4 } }
278 The same fragment using @code{\skip} results in an empty page.
282 Internals: @internalsref{SkipEvent}, @internalsref{SkipMusic}.
287 @subsection Durations
293 In Note, Chord, and Lyrics mode, durations are designated by numbers
294 and dots: durations are entered as their reciprocal values. For example,
295 a quarter note is entered using a @code{4} (since it is a 1/4 note), while
296 a half note is entered using a @code{2} (since it is a 1/2 note). For notes
297 longer than a whole you must use variables:
301 c'1 c'2 c'4 c'8 c'16 c'32 c'64 c'64
303 r1 r2 r4 r8 r16 r32 r64 r64
308 \notes \relative c'' {
310 a1 a2 a4 a8 a16 a32 a64 a64
312 r1 r2 r4 r8 r16 r32 r64 r64
317 \remove "Clef_engraver"
318 \override StaffSymbol #'transparent = ##t
319 \override TimeSignature #'transparent = ##t
320 \consists "Pitch_squash_engraver"
327 If the duration is omitted then it is set to the previously entered
328 duration. The default for the first note is a quarter note. The duration
329 can be followed by dots (`@code{.}') in order to obtain dotted note
333 @lilypond[fragment,verbatim,center]
334 a' b' c''8 b' a'4 a'4. b'4.. c'8.
339 You can alter the length of duration by a fraction @var{N/M}
340 appending `@code{*}@var{N/M}' (or `@code{*}@var{N}' if @var{M=1}). This
341 will not affect the appearance of the notes or rests produced.
342 In the following example, the first three notes take up exactly two
344 @lilypond[fragment,relative=2,verbatim]
346 a4*2/3 gis4*2/3 a4*2/3
353 Dots are normally moved up to avoid staff lines, except in polyphonic
354 situations. The following commands may be used to force a particular
357 @cindex @code{\dotsUp}
359 @cindex @code{\dotsDown}
361 @cindex @code{\dotsBoth}
366 Internals: @internalsref{Dots}, and @internalsref{DotColumn}.
371 Whenever a note is found, a @internalsref{Stem} object is created
372 automatically. For whole notes and rests, they are also created but
377 @cindex @code{\stemUp}
379 @cindex @code{\stemDown}
381 @cindex @code{\stemBoth}
392 A tie connects two adjacent note heads of the same pitch. The tie in
393 effect extends the length of a note. Ties should not be confused with
394 slurs, which indicate articulation, or phrasing slurs, which indicate
395 musical phrasing. A tie is entered using the tilde symbol `@code{~}':
397 @lilypond[fragment,verbatim,center]
398 e' ~ e' <c' e' g'> ~ <c' e' g'>
401 When a tie is applied to a chord, all note heads whose pitches match
402 are connected. When no note heads match, no ties will be created.
404 In its meaning a tie is just a way of extending a note duration, similar
405 to the augmentation dot; in the following example there are two ways of
406 notating exactly the same concept:
408 @lilypond[fragment,raggedright,quote]
409 \time 3/4 c'2. c'2 ~ c'4
411 If you need to tie a lot of notes over bars, it may be easier to use automatic
412 note splitting (see @ref{Automatic note splitting}).
417 @cindex @code{\tieUp}
419 @cindex @code{\tieDown}
421 @cindex @code{\tieBoth}
423 @cindex @code{\tieDotted}
425 @cindex @code{\tieSolid}
430 In this manual: @ref{Automatic note splitting}.
432 Internals: @internalsref{TieEvent}, @internalsref{Tie}.
434 Examples: if you want less ties created for a chord, see
435 @inputfileref{input/test,tie-sparse.ly}.
437 For tying only a subset of the note heads of a pair of chords, see
438 @inputfileref{input/regression,tie-chord-partial.ly}.
443 Switching staves when a tie is active will not produce a slanted tie.
445 Formatting of ties is a difficult subject. The results are often not
455 @cindex @code{\times}
457 Tuplets are made out of a music expression by multiplying all durations
460 @cindex @code{\times}
462 \times @var{fraction} @var{musicexpr}
466 The duration of @var{musicexpr} will be multiplied by the fraction.
467 The fraction's denominator will be printed over the notes, optionally
468 with a bracket. The most common tuplet is the triplet in which 3
469 notes have the length of 2, so the notes are 2/3 of their written
472 @lilypond[fragment,verbatim,center]
473 g'4 \times 2/3 {c'4 c' c'} d'4 d'4
476 The property @code{tupletSpannerDuration} specifies how long each
477 bracket should last. With this, you can make lots of tuplets while
478 typing @code{\times} only once, saving lots of typing. In the next
479 example, there are two triplets shown, while @code{\times} was only
482 @lilypond[fragment,relative,raggedright,verbatim]
483 \set tupletSpannerDuration = #(ly:make-moment 1 4)
484 \times 2/3 { c'8 c c c c c }
487 The format of the number is determined by the property
488 @code{tupletNumberFormatFunction}. The default prints only the
489 denominator, but if it is set to the Scheme function
490 @code{fraction-tuplet-formatter}, @var{num}:@var{den} will be printed
494 @cindex @code{tupletNumberFormatFunction}
495 @cindex tuplet formatting
500 @cindex @code{\tupletUp}
502 @cindex @code{\tupletDown}
504 @cindex @code{\tupletBoth}
509 Internals: @internalsref{TupletBracket}, and @internalsref{TimeScaledMusic}.
511 Examples: @inputfileref{input/regression,tuplet-nest.ly}.
515 Nested tuplets are not formatted automatically. In this case, outer
516 tuplet brackets should be moved manually, which is demonstrated in
517 @inputfileref{input/regression,tuplet-nest.ly}.
521 @node Easier music entry
522 @section Easier music entry
525 When entering music it is easy to introduce errors. This section deals
526 with tricks and features of the input language that were added solely
527 to help entering music, and find and correct mistakes.
529 It is also possible to use external programs, for example GUI
530 interfaces, or MIDI transcription programs, to enter or edit
531 music. Refer to the website for more information. Finally, there are
532 tools make debugging easier, by linking the input file and the output
533 shown on screen. See @ref{Point and click} for more information.
540 * Skipping corrected music::
541 * Automatic note splitting::
547 @node Relative octaves
548 @subsection Relative octaves
550 @cindex relative octave specification
552 Octaves are specified by adding @code{'} and @code{,} to pitch names.
553 When you copy existing music, it is easy to accidentally put a pitch
554 in the wrong octave and hard to find such an error. The relative
555 octave mode prevents these errors: a single error puts the rest of the
556 piece off by one octave:
558 @cindex @code{\relative}
560 \relative @var{startpitch} @var{musicexpr}
563 The octave of notes that appear in @var{musicexpr} are calculated as
564 follows: If no octave changing marks are used, the basic interval
565 between this and the last note is always taken to be a fourth or less
566 (; this distance is determined without regarding alterations: a
567 @code{fisis} following a @code{ceses} will be put above the
570 The octave changing marks @code{'} and @code{,} can be added to raise
571 or lower the pitch by an extra octave. Upon entering relative mode,
572 an absolute starting pitch must be specified that will act as the
573 predecessor of the first note of @var{musicexpr}.
575 Here is the relative mode shown in action:
576 @lilypond[fragment,raggedright,verbatim,center]
582 Octave changing marks are used for intervals greater than a fourth:
583 @lilypond[fragment,verbatim,center]
588 If the preceding item is a chord, the first note of the chord is used
589 to determine the first note of the next chord:
591 @lilypond[fragment,verbatim,center]
598 @cindex @code{\notes}
600 The pitch after the @code{\relative} contains a note name. To parse
601 the pitch as a note name, you have to be in note mode, so there must
602 be a surrounding @code{\notes} keyword (which is not
605 The relative conversion will not affect @code{\transpose},
606 @code{\chords} or @code{\relative} sections in its argument. If you
607 want to use relative within transposed music, you must place an
608 additional @code{\relative} inside the @code{\transpose}.
611 @subsection Octave check
614 Octave checks make octave errors easier to correct: a note may be
615 followed by @code{=}@var{quotes} which indicates what its absolute
616 octave should be. In the following example,
618 \relative c'' @{ c='' b=' d,='' @}
622 @c take care with @code, adds confusing quotes.
623 the d will generate a warning, because a d'' is expected, but a d' is
624 found. In the output, the octave is corrected this and the following
629 There is also a syntax that is separate from the notes.
634 This checks that @var{pitch} (without octave) yields @var{pitch} (with
635 octave) in \relative mode. If not, a warning is printed, and the
636 octave is corrected, for example, the first check is passed
637 successfully. The second check fails with an error message. The
638 octave is adjusted so the following notes are in the correct octave
649 The octave of a note following an octave check is determined with
650 respect to the note preceding it. In the next fragment, the last note
651 is a @code{a'}, above central C. Hence, the @code{\octave} check may
652 be deleted without changing the meaning of the piece.
654 @lilypond[verbatim,fragment]
663 @subsection Bar check
667 @cindex @code{barCheckSynchronize}
670 Bar checks help detect errors in the durations. A bar check is
671 entered using the bar symbol, `@code{|}'. Whenever it is encountered
672 during interpretation, it should fall on a measure boundary. If it
673 does not, a warning is printed. Depending on the value of
674 @code{barCheckSynchronize}, the beginning of the measure will be
677 In the next example, the second bar check will signal an error:
679 \time 3/4 c2 e4 | g2 |
682 Bar checks can also be used in lyrics, for example
687 Twin -- kle | Twin -- kle
692 @cindex skipTypesetting
694 Failed bar checks are caused by entering incorrect
695 durations. Incorrect durations often completely garble up the score,
696 especially if it is polyphonic, so you should start correcting the
697 score by scanning for failed bar checks and incorrect durations. To
698 speed up this process, you can use @code{skipTypesetting}, described
701 @node Skipping corrected music
702 @subsection Skipping corrected music
704 The property @code{Score.skipTypesetting} can be used to switch on and
705 off typesetting completely during the interpretation phase. When
706 typesetting is switched off, the music is processed much more quickly.
707 This can be used to skip over the parts of a score that have already
708 been checked for errors:
710 @lilypond[fragment,raggedright,verbatim]
712 \set Score.skipTypesetting = ##t
714 \set Score.skipTypesetting = ##f
718 @node Automatic note splitting
719 @subsection Automatic note splitting
721 Long notes can be converted automatically to tied notes. This is done
722 by replacing the @internalsref{Note_heads_engraver} by the
723 @internalsref{Completion_heads_engraver}.
724 In the following examples, notes crossing the barline are split and tied.
727 @lilypond[noindent,verbatim,relative=1]
729 \remove "Note_heads_engraver"
730 \consists "Completion_heads_engraver"
732 c2. c8 d4 e f g a b c8 c2 b4 a g16 f4 e d c8. c2
736 This engraver splits all running notes at the bar line, and inserts
737 ties. One of its uses is to debug complex scores: if the measures are
738 not entirely filled, then the ties exactly show how much each measure
743 Not all durations (especially those containing tuplets) can be
744 represented exactly; the engraver will not insert tuplets.
748 Examples: @inputfileref{input/regression,completion-heads.ly}.
750 Internals: @internalsref{Completion_heads_engraver}.
754 @section Staff notation
756 This section describes music notation that occurs on staff level,
757 such as keys, clefs and time signatures.
759 @cindex Staff notation
773 @subsection Staff symbol
775 @cindex adjusting staff symbol
777 Notes, dynamic signs, etc. are grouped
778 with a set of horizontal lines, into a staff (plural `staves'). In our
779 system, these lines are drawn using a separate layout object called
783 @cindex staff lines, setting number of
784 @cindex staff lines, setting thickness of
785 @cindex thickness of staff lines, setting
786 @cindex number of staff lines, setting
790 Internals: @internalsref{StaffSymbol}.
792 Examples: @inputfileref{input/test,staff-lines.ly},
793 @inputfileref{input/test,staff-size.ly}.
797 If a staff is ended halfway a piece, the staff symbol may not end
798 exactly on the barline.
802 @subsection Key signature
803 @cindex Key signature
807 The key signature indicates the scale in which a piece is played. It
808 is denoted by a set of alterations (flats or sharps) at the start of
813 Setting or changing the key signature is done with the @code{\key}
816 @code{\key} @var{pitch} @var{type}
819 @cindex @code{\minor}
820 @cindex @code{\major}
821 @cindex @code{\minor}
822 @cindex @code{\ionian}
823 @cindex @code{\locrian}
824 @cindex @code{\aeolian}
825 @cindex @code{\mixolydian}
826 @cindex @code{\lydian}
827 @cindex @code{\phrygian}
828 @cindex @code{\dorian}
830 Here, @var{type} should be @code{\major} or @code{\minor} to get
831 @var{pitch}-major or @var{pitch}-minor, respectively.
832 The standard mode names @code{\ionian},
833 @code{\locrian}, @code{\aeolian}, @code{\mixolydian}, @code{\lydian},
834 @code{\phrygian}, and @code{\dorian} are also defined.
836 This command sets the context property
837 @internalsref{Staff}.@code{keySignature}. Non-standard key signatures
838 can be specified by setting this property directly.
840 Accidentals and key signatures often confuse new users, because
841 unaltered notes get natural signs depending on the keysignature. The
842 tutorial explains why this is so in @ref{More about pitches}.
846 The ordering of a key cancellation is wrong when it is combined with
847 repeat bar lines. The cancellation is also printed after a line break.
851 Internals: @internalsref{KeyChangeEvent}, and @internalsref{KeySignature}.
853 @cindex @code{keySignature}
860 The clef indicates which lines of the staff correspond to which
865 The clef can be set or changed with the @code{\clef} command:
866 @lilypond[fragment,verbatim]
867 \key f\major c''2 \clef alto g'2
870 Supported clef-names include:
871 @c Moved standard clefs to the top /MB
875 @item treble, violin, G, G2
888 G clef on 1st line, so-called French violin clef
893 @cindex mezzosoprano clef
896 @cindex baritone clef
899 @cindex varbaritone clef
908 By adding @code{_8} or @code{^8} to the clef name, the clef is
909 transposed one octave down or up, respectively, and @code{_15} and
910 @code{^15} transposes by two octaves. The argument @var{clefname}
911 must be enclosed in quotes when it contains underscores or digits. For
915 @cindex choral tenor clef
916 @lilypond[verbatim,fragment,relative]
920 This command is equivalent to setting @code{clefGlyph},
921 @code{clefPosition} (which controls the Y position of the clef),
922 @code{centralCPosition} and @code{clefOctavation}. A clef is printed
923 when any of these properties are changed.
927 Internals: the object for this symbol is @internalsref{Clef}.
931 @node Ottava brackets
932 @subsection Ottava brackets
934 ``Ottava'' brackets introduce an extra transposition of an octave for
935 the staff. They are created by invoking the function
936 @code{set-octavation}:
942 @lilypond[verbatim,fragment]
951 The @code{set-octavation} function also takes -1 (for 8va bassa) and 2
952 (for 15ma) as arguments. Internally the function sets the properties
953 @code{ottavation} (eg. to @code{"8va"}) and
954 @code{centralCPosition}. For overriding the text of the bracket, set
955 @code{ottavation} after invoking @code{set-octavation}, i.e.,
959 \set Staff.ottavation = #"8"
964 Internals: @internalsref{OttavaBracket}.
966 Examples: @inputfileref{input/regression,ottava.ly},
967 @inputfileref{input/regression,ottava-broken.ly}.
971 @code{set-octavation} will get confused when clef changes happen
972 during an octavation bracket.
975 @subsection Time signature
976 @cindex Time signature
980 Time signature indicates the metrum of a piece: a regular pattern of
981 strong and weak beats. It is denoted by a fraction at the start of the
986 The time signature is set or changed by the @code{\time}
988 @lilypond[fragment,verbatim]
989 \time 2/4 c'2 \time 3/4 c'2.
992 The symbol that is printed can be customized with the @code{style}
993 property. Setting it to @code{#'()} uses fraction style for 4/4 and
994 2/2 time. There are many more options for its layout. See
995 @inputfileref{input/test,time.ly} for more examples.
998 This command sets the property @code{timeSignatureFraction},
999 @code{beatLength} and @code{measureLength} in the @code{Timing}
1000 context, which is normally aliased to @internalsref{Score}. The
1001 property @code{measureLength} determines where bar lines should be
1002 inserted, and how automatic beams should be generated. Changing the
1003 value of @code{timeSignatureFraction} also causes the symbol to be
1006 More options are available through the Scheme function
1007 @code{set-time-signature}. In combination with the
1008 @internalsref{Measure_grouping_engraver}, it will create
1009 @internalsref{MeasureGrouping} signs. Such signs ease reading
1010 rhythmically complex modern music. In the following example, the 9/8
1011 measure is subdivided in 2, 2, 2 and 3. This is passed to
1012 @code{set-time-signature} as the third argument @code{(2 2 2 3)}:
1015 \score { \notes \relative c'' {
1016 #(set-time-signature 9 8 '(2 2 2 3))
1017 g8[ g] d[ d] g[ g] a8[( bes g]) |
1018 #(set-time-signature 5 8 '(3 2))
1023 \translator { \StaffContext
1024 \consists "Measure_grouping_engraver"
1030 Internals: @internalsref{TimeSignature}, and @internalsref{Timing_engraver}.
1035 Automatic beaming does not use measure grouping specified with
1036 @code{set-time-signature}.
1038 @node Partial measures
1039 @subsection Partial measures
1042 @cindex partial measure
1043 @cindex measure, partial
1044 @cindex shorten measures
1045 @cindex @code{\partial}
1047 Partial measures, for example in upsteps, are entered using the
1048 @code{\partial} command:
1049 @lilypond[fragment,verbatim,relative=1]
1050 \partial 16*5 c16 cis d dis e | a2. c,4 | b2
1053 The syntax for this command is
1055 \partial @var{duration}
1057 This is internally translated into
1059 \set Timing.measurePosition = -@var{length of duration}
1062 The property @code{measurePosition} contains a rational number
1063 indicating how much of the measure has passed at this point.
1065 @node Unmetered music
1066 @subsection Unmetered music
1068 Bar lines and bar numbers are calculated automatically. For unmetered
1069 music (e.g. cadenzas), this is not desirable. By setting
1070 @code{Score.timing} to false, this automatic timing can be switched
1076 @cindex @code{\cadenzaOn}
1078 @cindex @code{\cadenzaOff}
1082 @subsection Bar lines
1086 @cindex measure lines
1090 Bar lines delimit measures, but are also used to indicate repeats.
1091 Normally, they are inserted automatically. Line breaks may only
1097 of barlines can be forced with the @code{\bar} command:
1099 @lilypond[relative=1,fragment,verbatim]
1103 The following bar types are available:
1104 @lilypond[fragment,relative,raggedright,verbatim]
1117 For allowing linebreaks, there is a special command,
1121 This will insert an invisible barline, and allow linebreaks at this
1124 In scores with many staves, a @code{\bar} command in one staff is
1125 automatically applied to all staves. The resulting bar lines are
1126 connected between different staves of a @internalsref{StaffGroup}:
1128 @lilypond[fragment,verbatim]
1129 << \context StaffGroup <<
1133 \new Staff { \clef bass c4 g e g } >>
1134 \new Staff { \clef bass c2 c2 } >>
1138 The command @code{\bar @var{bartype}} is a short cut for doing
1139 @code{\set Score.whichBar = @var{bartype}} Whenever
1140 @code{whichBar} is set to a string, a bar line of that type is
1141 created. At the start of a measure it is set to
1142 @code{defaultBarType}. The contents of @code{repeatCommands} are used
1143 to override default measure bars.
1145 Property @code{whichBar} can also be set directly, using @code{\set}
1146 or @code{\bar}. These settings take precedence over the automatic
1147 @code{whichBar} settings.
1150 @cindex repeatCommands
1151 @cindex defaultBarType
1153 You are encouraged to use @code{\repeat} for repetitions. See
1160 In this manual: @ref{Repeats}.
1163 Internals: the bar line objects that are created at
1164 @internalsref{Staff} level are called @internalsref{BarLine}, the bar
1165 lines that span staves are @internalsref{SpanBar}s.
1167 @cindex bar lines at start of system
1168 @cindex start of system
1170 The barlines at the start of each system are
1171 @internalsref{SystemStartBar}, @internalsref{SystemStartBrace}, and
1172 @internalsref{SystemStartBracket}. Only one of these types is created
1173 in every context, and that type is determined by the property
1174 @code{systemStartDelimiter}.
1176 Examples: @inputfileref{input/test,bar-lines.ly},
1182 The easiest way to enter fragments with more than one voice on a staff
1183 is to split chords using the separator @code{\\}. You can use it for
1184 small, short-lived voices or for single chords:
1186 @lilypond[verbatim,fragment]
1187 \context Staff \relative c'' {
1188 c4 << { f d e } \\ { b c2 } >>
1189 c4 << g' \\ b, \\ f' \\ d >>
1193 The separator causes @internalsref{Voice} contexts@footnote{Polyphonic
1194 voices are sometimes called "layers" other notation packages}
1196 to be instantiated. They bear the names @code{"1"}, @code{"2"}, etc. In
1197 each of these contexts, vertical direction of slurs, stems, etc. is set
1200 @cindex @code{\voiceOne}
1201 @cindex @code{\voiceFour}
1203 This can also be done by instantiating @internalsref{Voice} contexts
1204 by hand, and using @code{\voiceOne}, up to @code{\voiceFour} to assign
1205 a stem directions and horizontal shift for each part:
1208 @lilypond[raggedright,verbatim]
1210 \context Staff << \new Voice { \voiceOne cis2 b }
1211 \new Voice { \voiceThree b4 ais ~ ais4 gis4 }
1212 \new Voice { \voiceTwo fis4~ fis4 f ~ f } >>
1216 The command @code{\oneVoice} will revert back to the normal setting.
1217 @cindex @code{\oneVoice}
1220 Normally, note heads with a different number of dots are not merged, but
1221 when the object property @code{merge-differently-dotted} is set in
1222 the @internalsref{NoteCollision} object, they are merged:
1223 @lilypond[verbatim,fragment,raggedright]
1224 \relative c'' \context Voice << {
1226 \override Staff.NoteCollision
1227 #'merge-differently-dotted = ##t
1229 } \\ { g8.[ f16] g8.[ f16] }
1233 Similarly, you can merge half note heads with eighth notes, by setting
1234 @code{merge-differently-headed}:
1235 @lilypond[fragment,relative=2,verbatim]
1238 \override Staff.NoteCollision
1239 #'merge-differently-headed = ##t
1240 c8 c4. } \\ { c2 c2 } >>
1243 LilyPond also vertically shifts rests that are opposite of a stem:
1246 @lilypond[raggedright,fragment,verbatim]
1247 \context Voice << c''4 \\ r4 >>
1255 @cindex @code{\oneVoice}
1257 @cindex @code{\voiceOne}
1259 @cindex @code{\voiceTwo}
1261 @cindex @code{\voiceThree}
1263 @cindex @code{\voiceFour}
1267 The following commands specify in what chords of the current voice
1268 should be shifted: the outer voice has @code{\shiftOff}, and the inner
1269 voices have @code{\shiftOn}, @code{\shiftOnn}, etc.
1272 @cindex @code{\shiftOn}
1274 @cindex @code{\shiftOnn}
1276 @cindex @code{\shiftOnnn}
1278 @cindex @code{\shiftOff}
1285 Internals: the objects responsible for resolving collisions are
1286 @internalsref{NoteCollision} and @internalsref{RestCollision}.
1288 Examples: See also example files
1289 @inputfileref{input/regression,collision-dots.ly},
1290 @inputfileref{input/regression,collision-head-chords.ly},
1291 @inputfileref{input/regression,collision-heads.ly},
1292 @inputfileref{input/regression,collision-mesh.ly}, and
1293 @inputfileref{input/regression,collisions.ly}.
1298 Resolving collisions is a intricate subject, and only a few situations
1299 are handled. When LilyPond cannot cope, the @code{force-hshift}
1300 property of the @internalsref{NoteColumn} object and pitched rests can
1301 be used to override typesetting decisions.
1303 When using @code{merge-differently-headed} with an upstem 8th or a shorter
1304 note, and a downstem half note, the 8th note gets the wrong offset.
1306 There is no support for clusters where the same note occurs with
1307 different accidentals in the same chord. In this case, it is
1308 recommended to use enharmonic transcription, or to use special cluster
1309 notation (see @ref{Clusters}).
1314 Beams are used to group short notes into chunks that are aligned with
1315 the metrum. They are inserted automatically in most cases:
1317 @lilypond[fragment,verbatim,relative=2]
1318 \time 2/4 c8 c c c \time 6/8 c c c c8. c16 c8
1321 When these automatic decisions are not good enough, beaming can be
1322 entered explicitly. It is also possible to define beaming patterns
1323 that differ from the defaults.
1325 Individual notes may be marked with @code{\noBeam}, to prevent them
1328 @lilypond[fragment,verbatim,relative=2]
1329 \time 2/4 c8 c\noBeam c c
1335 Internals: @internalsref{Beam}.
1338 @cindex Automatic beams
1341 * Setting automatic beam behavior::
1345 @subsection Manual beams
1346 @cindex beams, manual
1350 In some cases it may be necessary to override the automatic beaming
1351 algorithm. For example, the auto beamer will not put beams over rests
1352 or bar lines. Such beams are specified by manually: the begin and end
1353 point are marked with @code{[} and @code{]}:
1355 @lilypond[fragment,relative,verbatim]
1357 r4 r8[ g' a r8] r8 g[ | a] r8
1361 @cindex @code{stemLeftBeamCount}
1363 Normally, beaming patterns within a beam are determined automatically.
1364 When this mechanism fouls up, the properties
1365 @code{stemLeftBeamCount} and @code{stemRightBeamCount} can
1366 be used to control the beam subdivision on a stem. If either property
1367 is set, its value will be used only once, and then it is erased:
1369 @lilypond[fragment,relative,verbatim]
1372 f8[ r16 \set stemLeftBeamCount = #1 f g a]
1375 @cindex @code{stemRightBeamCount}
1378 The property @code{subdivideBeams} can be set in order to subdivide
1379 all 16th or shorter beams at beat positions, as defined by the
1380 @code{beatLength} property. This accomplishes the same effect as
1381 twiddling with @code{stemLeftBeamCount} and @code{stemRightBeamCount},
1382 but it take less typing:
1385 @lilypond[relative=1,verbatim,noindent]
1387 \set subdivideBeams = ##t
1389 \set Score.beatLength = #(ly:make-moment 1 8)
1392 @cindex subdivideBeams
1394 Kneed beams are inserted automatically, when a large gap is detected
1395 between the note heads. This behavior can be tuned through the object
1396 property @code{auto-knee-gap}.
1398 Normally, line breaks are forbidden when beams cross bar lines. This
1399 behavior can be changed by setting @code{allowBeamBreak}.
1401 @cindex @code{allowBeamBreak}
1402 @cindex beams and line breaks
1404 @cindex beams, kneed
1406 @cindex auto-knee-gap
1412 @cindex Frenched staves
1414 Automatically kneed beams cannot be used together with hidden staves.
1419 @node Setting automatic beam behavior
1420 @subsection Setting automatic beam behavior
1422 @cindex @code{autoBeamSettings}
1423 @cindex @code{(end * * * *)}
1424 @cindex @code{(begin * * * *)}
1425 @cindex automatic beams, tuning
1426 @cindex tuning automatic beaming
1428 @c [TODO: use \applycontext]
1430 In normal time signatures, automatic beams can start on any note but can
1431 only end in a few positions within the measure: beams can end on a beat,
1432 or at durations specified by the properties in
1433 @code{autoBeamSettings}. The defaults for @code{autoBeamSettings}
1434 are defined in @file{scm/auto-beam.scm}.
1436 The value of @code{autoBeamSettings} is changed with two functions:
1438 #(override-auto-beam-setting
1439 '(@var{be} @var{p} @var{q} @var{n} @var{m}) @var{a} @var{b}
1441 #(revert-auto-beam-setting '(@var{be} @var{p} @var{q} @var{n} @var{m}))
1443 Here, @var{be} is the symbol @code{begin} or @code{end}. It determines
1444 whether the rule applies to begin or end-points. The quantity
1445 @var{p}/@var{q} refers to the length of the beamed notes (and `@code{*
1446 *}' designates notes of any length), @var{n}/@var{M} refers to a time
1447 signature (wildcards `@code{* *}' may be entered to designate all time
1448 signatures), @var{a}/@var{b} is a duration. By default, this command
1449 changes settings for the current voice. It is also possible to adjust
1450 settings at higher contexts, by adding a @var{context} argument.
1452 For example, if automatic beams should end on every quarter note, use
1455 #(override-auto-beam-setting '(end * * * *) 1 4)
1457 Since the duration of a quarter note is 1/4 of a whole note, it is
1458 entered as @code{(ly:make-moment 1 4)}.
1460 The same syntax can be used to specify beam starting points. In this
1461 example, automatic beams can only end on a dotted quarter note:
1463 #(override-auto-beam-setting '(end * * * *) 3 8)
1465 In 4/4 time signature, this means that automatic beams could end only on
1466 3/8 and on the fourth beat of the measure (after 3/4, that is 2 times
1467 3/8, has passed within the measure).
1469 Rules can also be restricted to specific time signatures. A rule that
1470 should only be applied in @var{N}/@var{M} time signature is formed by
1471 replacing the second asterisks by @var{N} and @var{M}. For example, a
1472 rule for 6/8 time exclusively looks like
1474 #(override-auto-beam-setting '(begin * * 6 8) @dots{})
1477 If a rule should be to applied only to certain types of beams, use the
1478 first pair of asterisks. Beams are classified according to the
1479 shortest note they contain. For a beam ending rule that only applies
1480 to beams with 32nd notes (and no shorter notes), use @code{(end 1 32 *
1483 If a score ends while an automatic beam has not been ended and is still
1484 accepting notes, this last beam will not be typeset at all.
1486 @cindex automatic beam generation
1488 @cindex @code{autoBeaming}
1491 For melodies that have lyrics, you may want to switch off
1492 automatic beaming. This is done by setting @code{autoBeaming} to
1497 @cindex @code{\autoBeamOff}
1498 @code{\autoBeamOff},
1499 @cindex @code{\autoBeamOn}
1505 The rules for ending a beam depend on the shortest note in a beam.
1506 So, while it is possible to have different ending rules for eight
1507 beams and sixteenth beams, a beam that contains both eight and
1508 sixteenth notes will use the rules for the sixteenth beam.
1510 In the example below, the autobeamer makes eight beams and sixteenth
1511 end at 3 eights; the third beam can only be corrected by specifying
1514 @lilypond[raggedright,fragment,relative,noverbatim,quote]
1515 #(override-auto-beam-setting '(end * * * *) 3 8)
1516 % rather show case where it goes wrong
1517 %\time 12/8 c'8 c c c16 c c c c c c[ c c c] c8[ c] c4
1518 \time 12/8 c'8 c c c16 c c c c c c c c c c8 c c4
1520 It is not possible to specify beaming parameters that act differently in
1521 different parts of a measure. This means that it is not possible to use
1522 automatic beaming in irregular meters such as @code{5/8}.
1525 @section Accidentals
1528 This section describes how to change the way that accidentals are
1529 inserted automatically before the running notes.
1533 * Using the predefined accidental variables::
1534 * Customized accidental rules::
1537 @node Using the predefined accidental variables
1538 @subsection Using the predefined accidental variables
1541 Common rules for typesetting macros have been canned in a
1542 function. This function is called as follows:
1544 @cindex @code{set-accidental-style}
1546 #(set-accidental-style 'modern 'Voice)
1549 The function takes two arguments: a symbol that denotes the style (in
1550 the example, @code{modern}), and another symbol that denotes the
1551 context name (in this example, @code{Staff}). If no context name is
1552 supplied, @code{Staff} is the default.
1554 The following styles are supported:
1557 This is the default typesetting behaviour. It should correspond
1558 to 18th century common practice: Accidentals are
1559 remembered to the end of the measure in which they occur and
1560 only on their own octave.
1564 The normal behaviour is to remember the accidentals on
1565 Staff-level. This variable, however, typesets accidentals
1566 individually for each voice. Apart from that, the rule is similar to
1569 This leads to some weird and often unwanted results
1570 because accidentals from one voice do not get cancelled in other
1572 @lilypond[raggedright,relative,fragment,verbatim,quote]
1574 #(set-accidental-style 'voice)
1580 Hence you should only use @code{voice} if the voices
1581 are to be read solely by individual musicians. If the staff is to be
1582 used by one musician (e.g. a conductor) then you use
1583 @code{modern} or @code{modern-cautionary}
1587 @cindex @code{modern} style accidentals
1588 This rule corresponds to the common practice in the 20th
1590 This rule prints the same accidentals as @code{default}, but temporary
1591 accidentals also are cancelled in other octaves. Furthermore,
1592 in the same octave, they also get cancelled in the following
1595 @lilypond[raggedright,fragment,verbatim]
1596 #(set-accidental-style 'modern)
1597 cis' c'' cis'2 | c'' c'
1600 @item @code{modern-cautionary}
1601 @cindex @code{modern-cautionary}
1602 This rule is similar to @code{modern}, but the
1603 ``extra'' accidentals (the ones not typeset by
1604 @code{default}) are typeset as cautionary accidentals.
1605 They are printed in reduced size or with parentheses:
1606 @lilypond[raggedright,fragment,verbatim]
1607 #(set-accidental-style 'modern-cautionary)
1608 cis' c'' cis'2 | c'' c'
1611 @cindex @code{modern-voice}
1613 is used for multivoice accidentals to be read both by musicians
1614 playing one voice and musicians playing all voices. Accidentals are
1615 typeset for each voice, but they @emph{are} cancelled across voices in
1616 the same @internalsref{Staff}.
1618 @cindex @code{modern-voice-cautionary}
1619 @item modern-voice-cautionary
1620 is the same as @code{modern-voice}, but with the extra
1621 accidentals (the ones not typeset by @code{voice}) typeset
1622 as cautionaries. Even though all accidentals typeset by
1623 @code{default} @emph{are} typeset by this variable then
1624 some of them are typeset as cautionaries.
1627 @cindex @code{piano} accidentals
1628 20th century practice for piano notation. Very similar to
1629 @code{modern} but accidentals also get cancelled
1630 across the staves in the same @internalsref{GrandStaff} or
1631 @internalsref{PianoStaff}.
1633 @item piano-cautionary
1634 @cindex @code{#(set-accidental-style 'piano-cautionary)}
1635 As @code{#(set-accidental-style 'piano)' , str)} but with the extra accidentals
1636 typeset as cautionaries.
1639 @cindex @code{no-reset} accidental style
1640 Same as @code{default} but with accidentals lasting
1641 ``forever'' and not only until the next measure:
1642 @lilypond[raggedright,fragment,verbatim,relative]
1643 #(set-accidental-style 'no-reset)
1648 This is sort of the opposite of @code{no-reset}: Accidentals
1649 are not remembered at all---and hence all accidentals are
1650 typeset relative to the key signature, regardless of what was
1651 before in the music:
1653 @lilypond[raggedright,fragment,verbatim,relative]
1654 #(set-accidental-style 'forget)
1655 \key d\major c4 c cis cis d d dis dis
1659 @node Customized accidental rules
1660 @subsection Customized accidental rules
1662 For determining when to print an accidental, several different rules
1663 are tried. The rule that gives the highest number of accidentals is
1664 used. Each rule consists of
1667 In which context is the rule applied. For example, if
1668 @var{context} is @internalsref{Score} then all staves share
1669 accidentals, and if @var{context} is @internalsref{Staff} then all
1670 voices in the same staff share accidentals, but staves do not.
1673 Whether the accidental changes all octaves or only the current
1674 octave. Valid choices are
1678 This is the default algorithm. Accidentals are typeset if the note changes
1679 the accidental of that note in that octave. Accidentals lasts to the end of the measure
1680 and then as many measures as specified in the value. I.e. 1 means to the end
1681 of next measure, -1 means to the end of previous measure (that is: no duration at all), etc. #t means forever.
1683 Accidentals are typeset if the note is different from
1684 the previous note on the same pitch in any octave. The value has same meaning as in
1690 Over how many barlines the accidental lasts.
1691 If @var{lazyness} is @code{-1} then the accidental is forget
1692 immediately, and if @var{lazyness} is @code{#t} then the accidental
1699 Internals: @internalsref{Accidental_engraver},
1700 @internalsref{Accidental}, and @internalsref{AccidentalPlacement}.
1705 Currently the simultaneous notes are considered to be entered in
1706 sequential mode. This means that in a chord the accidentals are
1707 typeset as if the notes in the chord happened once at a time - in the
1708 order in which they appear in the input file.
1710 This is only a problem when there are simultaneous notes whose
1711 accidentals depend on each other. The problem only occurs when using
1712 non-default accidentals. In the default scheme, accidentals only
1713 depend on other accidentals with the same pitch on the same staff, so
1714 no conflicts possible.
1716 This example shows two examples of the same music giving different
1717 accidentals depending on the order in which the notes occur in the
1720 @lilypond[raggedright,fragment,verbatim]
1721 \set Staff.autoAccidentals = #'( Staff (any-octave . 0) )
1722 cis'4 <c'' c'> r2 | cis'4 <c' c''> r2
1723 | <cis' c''> r | <c'' cis'> r |
1726 This problem can be solved by manually inserting @code{!} and @code{?}
1727 for the problematic notes.
1729 @node Expressive marks
1730 @section Expressive marks
1733 @c todo: should change ordering
1734 @c where to put text spanners, metronome marks,
1743 * Analysis brackets::
1745 * Fingering instructions::
1756 A slur indicates that notes are to be played bound or @emph{legato}.
1760 They are entered using parentheses:
1761 @lilypond[relative=1,fragment,verbatim,center]
1762 f( g)( a) a8 b( a4 g2 f4)
1767 @c TODO: should explain that ^( and _( set directions
1768 @c should set attachments with ^ and _ ?
1770 Slurs avoid crossing stems, and are generally attached to note heads.
1771 However, in some situations with beams, slurs may be attached to stem
1772 ends. If you want to override this layout you can do this through the
1773 object property @code{attachment} of @internalsref{Slur} in
1774 @internalsref{Voice} context. Its value is a pair of symbols, specifying
1775 the attachment type of the left and right end points:
1777 @lilypond[fragment,relative,verbatim]
1779 \override Stem #'length = #5.5
1781 \override Slur #'attachment = #'(stem . stem)
1785 If a slur would strike through a stem or beam, the slur will be moved
1786 away upward or downward. If this happens, attaching the slur to the
1787 stems might look better:
1789 @lilypond[fragment,relative,verbatim]
1792 \override Slur #'attachment = #'(stem . stem)
1799 @cindex @code{\slurUp}
1801 @cindex @code{\slurDown}
1803 @cindex @code{\slurBoth}
1805 @cindex @code{\slurDotted}
1807 @cindex @code{\slurSolid}
1812 Internals: @seeinternals{Slur}, and @internalsref{SlurEvent}.
1817 Producing nice slurs is a difficult problem, and LilyPond currently
1818 uses a simple, empiric method to produce slurs. In some cases, its
1822 @cindex Adjusting slurs
1824 @node Phrasing slurs
1825 @subsection Phrasing slurs
1827 @cindex phrasing slurs
1828 @cindex phrasing marks
1830 A phrasing slur (or phrasing mark) connects chords and is used to
1831 indicate a musical sentence. It is started using @code{\(} and @code{\)}
1834 @lilypond[fragment,verbatim,center,relative]
1835 \time 6/4 c'\( d( e) f( e) d\)
1838 Typographically, the phrasing slur behaves almost exactly like a
1839 normal slur. However, they are treated as different objects. A
1840 @code{\slurUp} will have no effect on a phrasing slur; instead, you
1841 should use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
1842 @code{\phrasingSlurBoth}.
1844 The commands @code{\slurUp}, @code{\slurDown}, and @code{\slurBoth}
1845 will only affect normal slurs and not phrasing slurs.
1849 @cindex @code{\phrasingSlurUp}
1850 @code{\phrasingSlurUp},
1851 @cindex @code{\phrasingSlurDown}
1852 @code{\phrasingSlurDown},
1853 @cindex @code{\phrasingSlurBoth}
1854 @code{\phrasingSlurBoth}.
1858 Internals: see also @internalsref{PhrasingSlur}, and
1859 @internalsref{PhrasingSlurEvent}.
1863 Phrasing slurs have the same limitations in their formatting as normal
1864 slurs. Putting phrasing slurs over rests leads to spurious warnings.
1867 @subsection Breath marks
1869 Breath marks are entered using @code{\breathe}:
1872 @lilypond[fragment,relative,verbatim]
1876 The glyph of the breath mark can be tweaked by overriding the
1877 @code{text} property of the @code{BreathingSign} layout object with
1878 any markup text. For example,
1879 @lilypond[fragment,verbatim,relative]
1881 \override BreathingSign #'text
1882 = #(make-musicglyph-markup "scripts-rvarcomma")
1889 Internals: @internalsref{BreathingSign},
1890 @internalsref{BreathingSignEvent}.
1892 Examples: @inputfileref{input/regression,breathing-sign.ly}.
1895 @node Metronome marks
1896 @subsection Metronome marks
1899 @cindex beats per minute
1900 @cindex metronome marking
1902 Metronome settings can be entered as follows:
1904 \tempo @var{duration} = @var{perminute}
1907 In the MIDI output, they are interpreted as a tempo change, and in the
1908 paper output, a metronome marking is printed:
1909 @cindex @code{\tempo}
1910 @lilypond[fragment,verbatim]
1916 Internals: @internalsref{MetronomeChangeEvent}.
1921 @subsection Text spanners
1922 @cindex Text spanners
1924 Some performance indications, e.g. @i{rallentando} or @i{accelerando},
1925 are written as texts, and extended over many measures with dotted
1926 lines. You can create such texts using text spanners: attach
1927 @code{\startTextSpan} and @code{\stopTextSpan} to the
1928 start and ending note of the spanner.
1930 The string to be printed, as well as the style, is set through object
1933 @lilypond[fragment,relative,verbatim]
1935 \override TextSpanner #'direction = #-1
1936 \override TextSpanner #'edge-text = #'("rall " . "")
1937 c2\startTextSpan b c\stopTextSpan a }
1943 Internals @internalsref{TextSpanEvent},
1944 @internalsref{TextSpanner}.
1946 Examples: @inputfileref{input/regression,text-spanner.ly}.
1949 @node Analysis brackets
1950 @subsection Analysis brackets
1952 @cindex phrasing brackets
1953 @cindex musicological analysis
1954 @cindex note grouping bracket
1956 Brackets are used in musical analysis to indicate structure in musical
1957 pieces. LilyPond supports a simple form of nested horizontal brackets.
1958 To use this, add the @internalsref{Horizontal_bracket_engraver} to
1959 @internalsref{Staff} context. A bracket is started with
1960 @code{\startGroup} and closed with @code{\stopGroup}:
1962 @lilypond[raggedright,verbatim]
1963 \score { \notes \relative c'' {
1964 c4\startGroup\startGroup
1967 c4\stopGroup\stopGroup
1969 \paper { \translator {
1970 \StaffContext \consists "Horizontal_bracket_engraver"
1976 Internals: @internalsref{HorizontalBracket},
1977 @internalsref{NoteGroupingEvent}.
1979 Examples: @inputfileref{input/regression,note-group-bracket.ly}.
1983 @subsection Articulations
1984 @cindex Articulations
1986 @cindex articulations
1990 A variety of symbols can appear above and below notes to indicate
1991 different characteristics of the performance. They are added to a note
1992 by adding a dash and the character signifying the
1993 articulation. They are demonstrated here:
1995 @lilypondfile[]{script-abbreviations.ly}
1997 The meanings of these shorthands can be changed: see
1998 @file{ly/script-init.ly} for examples.
2001 The script is automatically placed, but if you need to force
2002 directions, you can use @code{_} to force them down, or @code{^} to
2004 @lilypond[fragment,verbatim]
2008 Other symbols can be added using the syntax
2009 @var{note}@code{\}@var{name}, e.g. @code{c4\fermata}. Again, they
2010 can be forced up or down using @code{^} and @code{_},
2013 @lilypond[verbatim,fragment,relative=2]
2014 c\fermata c^\fermata c_\fermata
2021 @cindex staccatissimo
2030 @cindex organ pedal marks
2039 @cindex prallmordent
2043 @cindex thumb marking
2048 @lilypondfile[]{script-chart.ly}
2053 @cindex @code{\scriptUp}
2055 @cindex @code{\scriptDown}
2057 @cindex @code{\scriptBoth}
2062 Internals: @internalsref{ScriptEvent}, and @internalsref{Script}.
2066 These note ornaments appear in the printed output but have no
2067 effect on the MIDI rendering of the music.
2070 @node Fingering instructions
2071 @subsection Fingering instructions
2075 Fingering instructions can be entered using
2077 @var{note}-@var{digit}
2079 For finger changes, use markup texts:
2081 @lilypond[verbatim,raggedright,fragment]
2082 c'4-1 c'4-2 c'4-3 c'4-4
2083 c'^\markup { \fontsize #-3 \number "2-3" }
2086 @cindex finger change
2091 You can use the thumb-script to indicate that a note should be
2092 played with the thumb (e.g. in cello music):
2094 @lilypond[verbatim,raggedright,fragment]
2095 <a' a''-3>8(_\thumb <b' b''-3>)_\thumb
2096 <c'' c'''-3>(_\thumb <d'' d'''-3>)_\thumb
2099 Fingerings for chords can also be added to individual notes
2100 of the chord by adding them after the pitches:
2101 @lilypond[verbatim,raggedright,fragment,relative=1]
2102 < c-1 e-2 g-3 b-5 > 4
2106 In this case, setting @code{fingeringOrientations} will put fingerings next
2109 @lilypond[verbatim,raggedright,fragment,relative=1]
2110 \set fingeringOrientations = #'(left down)
2111 <c-1 es-2 g-4 bes-5 > 4
2112 \set fingeringOrientations = #'(up right down)
2113 <c-1 es-2 g-4 bes-5 > 4
2116 By using single note chords, fingering instructions can be put close
2117 to note heads in monophonic music.
2121 Internals: @internalsref{FingerEvent}, and @internalsref{Fingering}.
2123 Examples: @inputfileref{input/regression,finger-chords.ly}.
2126 @subsection Text scripts
2127 @cindex Text scripts
2129 @cindex text items, non-empty
2130 @cindex non-empty texts
2132 It is possible to place arbitrary strings of text or markup text (see
2133 @ref{Text markup}) above or below notes by using a string:
2134 @code{c^"text"}. By default, these indications do not influence the
2135 note spacing, but by using the command @code{\fatText}, the widths
2136 will be taken into account:
2138 @lilypond[fragment,raggedright,verbatim] \relative c' {
2139 c4^"longtext" \fatText c4_"longlongtext" c4 }
2142 It is possible to use @TeX{} commands in the strings, but this should
2143 be avoided because the exact dimensions of the string can then no
2148 @cindex @code{\fatText}
2150 @cindex @code{\emptyText}
2155 In this manual: @ref{Text markup}.
2157 Internals: @internalsref{TextScriptEvent}, @internalsref{TextScript}.
2163 @subsection Grace notes
2166 @c should have blurb about accaciatura / appogiatura
2168 @cindex @code{\grace}
2172 Grace notes are ornaments that are written out. The most common ones
2173 are acciaccatura, which should be played as very short. It is denoted
2174 by a slurred small note with a slashed stem. The appoggiatura is a
2175 grace note that takes a fixed fraction of the main note, is and
2176 denoted as a slurred note in small print without a slash.
2177 They are entered with the commands @code{\acciaccatura} and
2178 @code{\appoggiatura}, as demonstrated in the following example:
2181 @cindex appoggiatura
2182 @cindex acciaccatura
2184 @lilypond[relative=2,verbatim,fragment]
2185 b4 \acciaccatura d8 c4 \appoggiatura e8 d4
2186 \acciaccatura { g16[ f] } e4
2189 Both are special forms of the @code{\grace} command. By prefixing this
2190 keyword to a music expression, a new one is formed, which will be
2191 printed in a smaller font and takes up no logical time in a measure.
2192 @lilypond[relative=2,verbatim,fragment]
2194 \grace { c16[ d16] } c2 c4
2198 Unlike @code{\acciaccatura} and @code{\appoggiatura}, the
2199 @code{\grace} command does not start a slur.
2201 Internally, timing for grace notes is done using a second, `grace'
2202 time. Every point in time consists of two rational numbers: one
2203 denotes the logical time, one denotes the grace timing. The above
2204 example is shown here with timing tuples:
2206 @lilypond[raggedright]
2209 c4 \grace c16 c4 \grace {
2212 \new Lyrics \lyrics {
2215 ( \fraction 1 4 , \fraction -1 16 ) } 16 }
2216 \markup { (\fraction 1 4 , 0 ) } 4
2218 \markup { (\fraction 2 4 , \fraction "-1" 8 ) } 16
2219 \markup { (\fraction 2 4 , \fraction "-1" 16 ) } 16
2221 \markup { ( \fraction 2 4 , 0 ) }
2226 The placement of grace notes is synchronized between different staves.
2227 In the following example, there are two sixteenth graces notes for
2228 every eighth grace note:
2230 @lilypond[relative=2,verbatim,fragment]
2231 << \new Staff { e4 \grace { c16[ d e f] } e4 }
2232 \new Staff { c'4 \grace { g8[ b] } c4 } >>
2237 If you want to end a note with a grace, then the standard trick
2238 is to put the grace notes after a ``space note'', e.g.
2239 @lilypond[fragment,verbatim,relative=2]
2242 { s2 \grace { c16[ d] } } >>
2248 By adjusting the duration of the skip note (here it is a half-note),
2249 the space between the main-note and the grace is adjusted.
2252 A @code{\grace} section will introduce special typesetting settings,
2253 for example, to produce smaller type, and set directions. Hence, when
2254 introducing layout tweaks, they should be inside the grace section,
2256 @lilypond[fragment,verbatim,relative=1]
2259 \override Stem #'direction = #-1
2261 \revert Stem #'direction
2268 The overrides should also be reverted inside the grace section.
2270 If the layout of grace sections must be changed throughout the music,
2271 then this can be accomplished through the function
2272 @code{add-grace-property}. The following example
2273 undefines the Stem direction grace section, so stems do not always
2278 #(add-grace-property "Voice" Stem direction '())
2284 Another option is to change the variables @code{startGraceMusic},
2285 @code{stopGraceMusic}, @code{startAccacciaturaMusic},
2286 @code{stopAccacciaturaMusic}, @code{startAppoggiaturaMusic},
2287 @code{stopAppoggiaturaMusic}. More information is in the file
2288 @file{ly/grace-init.ly}.
2293 Internals: @internalsref{GraceMusic}.
2297 A score that starts with an @code{\grace} section needs an explicit
2298 @code{\context Voice} declaration, otherwise the main note and grace
2299 note end up on different staves.
2301 Grace note synchronization can also lead to surprises. Staff notation,
2302 such as key signatures, barlines, etc. are also synchronized. Take
2303 care when you mix staves with grace notes and staves without, for example,
2305 @lilypond[relative=2,verbatim,fragment]
2306 << \new Staff { e4 \bar "|:" \grace c16 d4 }
2307 \new Staff { c4 \bar "|:" d4 } >>
2310 Grace sections should only be used within sequential music
2311 expressions. Nesting or juxtaposing grace sections is not supported,
2312 and might produce crashes or other errors.
2316 @subsection Glissando
2319 @cindex @code{\glissando}
2321 A glissando is a smooth change in pitch. It is denoted by a line or a
2322 wavy line between two notes.
2326 A glissando line can be requested by attaching a @code{\glissando} to
2329 @lilypond[fragment,relative,verbatim]
2335 Internals: @internalsref{Glissando}, and @internalsref{GlissandoEvent}.
2340 Adding additional texts (such as @emph{gliss.}) is not supported.
2344 @subsection Dynamics
2357 @cindex @code{\ffff}
2367 Absolute dynamic marks are specified using an variable after a
2368 note: @code{c4\ff}. The available dynamic marks are @code{\ppp},
2369 @code{\pp}, @code{\p}, @code{\mp}, @code{\mf}, @code{\f}, @code{\ff},
2370 @code{\fff}, @code{\fff}, @code{\fp}, @code{\sf}, @code{\sff},
2371 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}:
2373 @lilypond[verbatim,raggedright,fragment,relative]
2374 c'\ppp c\pp c \p c\mp c\mf c\f c\ff c\fff
2380 @cindex @code{\decr}
2381 @cindex @code{\rced}
2388 A crescendo mark is started with @code{\<} and terminated with
2389 @code{\!}. A decrescendo is started with @code{\>} and also terminated
2390 with @code{\!}. Because these marks are bound to notes, if you must
2391 use spacer notes if multiple marks during one note are needed:
2393 @lilypond[fragment,verbatim,center,quote]
2394 c''\< c''\! d''\decr e''\rced
2395 << f''1 { s4 s4\< s4\! \> s4\! } >>
2397 This may give rise to very short hairpins. Use @code{minimum-length}
2398 in @internalsref{Voice}.@internalsref{Hairpin} to lengthen them, for
2402 \override Staff.Hairpin #'minimum-length = #5
2405 You can also use a text saying @emph{cresc.} instead of hairpins. Here
2406 is an example how to do it:
2408 @lilypond[fragment,relative=2,verbatim]
2409 c4 \cresc c4 c c c \endcresc c4
2415 You can also supply your own texts:
2416 @lilypond[fragment,relative,verbatim]
2418 \set crescendoText = \markup { \italic "cresc. poco" }
2419 \set crescendoSpanner = #'dashed-line
2429 @cindex @code{\dynamicUp}
2431 @cindex @code{\dynamicDown}
2432 @code{\dynamicDown},
2433 @cindex @code{\dynamicBoth}
2434 @code{\dynamicBoth}.
2436 @cindex direction, of dynamics
2440 Internals: @internalsref{CrescendoEvent}, @internalsref{DecrescendoEvent}, and
2441 @internalsref{AbsoluteDynamicEvent}.
2443 Dynamics are objects of @internalsref{DynamicText} and
2444 @internalsref{Hairpin}. Vertical positioning of these symbols is
2445 handled by the @internalsref{DynamicLineSpanner} object.
2447 If you want to adjust padding or vertical direction of the dynamics, you
2448 must set properties for the @internalsref{DynamicLineSpanner} object.
2456 @cindex @code{\repeat}
2459 Repetition is a central concept in music, and multiple notations exist
2460 for repetitions. In LilyPond, most of these notations can be captured
2461 in a uniform syntax. One of the advantages is that they can be
2462 rendered in MIDI accurately.
2464 The following types of repetition are supported:
2468 Repeated music is fully written (played) out. Useful for MIDI
2469 output, and entering repetitive music.
2472 This is the normal notation: Repeats are not written out, but
2473 alternative endings (voltas) are printed, left to right.
2477 Alternative endings are written stacked. This has limited use but may be
2478 used to typeset two lines of lyrics in songs with repeats, see
2479 @inputfileref{input,star-spangled-banner.ly}.
2487 Make beat or measure repeats. These look like percent signs.
2493 * Repeats and MIDI::
2494 * Manual repeat commands::
2496 * Tremolo subdivisions::
2501 @subsection Repeat syntax
2505 LilyPond has one syntactic construct for specifying different types of
2506 repeats. The syntax is
2509 \repeat @var{variant} @var{repeatcount} @var{repeatbody}
2512 If you have alternative endings, you may add
2513 @cindex @code{\alternative}
2515 \alternative @code{@{} @var{alternative1}
2517 @var{alternative3} @dots{} @code{@}}
2519 where each @var{alternative} is a music expression. If you do not
2520 give enough alternatives for all of the repeats, then the first
2521 alternative is assumed to be played more than once.
2523 Normal notation repeats are used like this:
2524 @lilypond[fragment,verbatim,relative=1]
2526 \repeat volta 2 { c4 d e f }
2527 \repeat volta 2 { f e d c }
2530 With alternative endings:
2531 @lilypond[fragment,verbatim,relative=1]
2533 \repeat volta 2 {c4 d e f}
2534 \alternative { {d2 d} {f f,} }
2538 @lilypond[fragment,verbatim,relative=1]
2541 \repeat volta 4 { e | c2 d2 | e2 f2 | }
2542 \alternative { { g4 g g } { a | a a a a | b2. } }
2548 If you do a nested repeat like
2557 then it is ambiguous to which @code{\repeat} the @code{\alternative}
2558 belongs. This ambiguity is resolved by always having the
2559 @code{\alternative} belong to the inner @code{\repeat}. For clarity,
2560 it is advisable to use braces in such situations.
2563 @node Repeats and MIDI
2564 @subsection Repeats and MIDI
2566 @cindex expanding repeats
2568 For instructions on how to unfold repeats for MIDI output, see the
2569 example file @inputfileref{input/test,unfold-all-repeats.ly}.
2574 Timing information is not remembered at the start of an alternative,
2575 so after a repeat timing information must be reset by hand, for
2576 example by setting @code{Score.measurePosition} or entering
2577 @code{\partial}. Similarly, slurs or ties are also not repeated.
2580 @node Manual repeat commands
2581 @subsection Manual repeat commands
2583 @cindex @code{repeatCommands}
2585 The property @code{repeatCommands} can be used to control the layout of
2586 repeats. Its value is a Scheme list of repeat commands, where each repeat
2590 @item the symbol @code{start-repeat},
2591 which prints a @code{|:} bar line,
2592 @item the symbol @code{end-repeat},
2593 which prints a @code{:|} bar line,
2594 @item the list @code{(volta @var{text})},
2595 which prints a volta bracket saying @var{text}: The text can be specified as
2596 a text string or as a markup text, see @ref{Text markup}. Do not
2597 forget to change the font, as the default number font does not contain
2598 alphabetic characters. Or,
2599 @item the list @code{(volta #f)}, which
2600 stops a running volta bracket:
2603 @lilypond[verbatim,fragment,relative=2]
2605 \set Score.repeatCommands = #'((volta "93") end-repeat)
2607 \set Score.repeatCommands = #'((volta #f))
2614 Internals: @internalsref{VoltaBracket}, @internalsref{RepeatedMusic},
2615 @internalsref{VoltaRepeatedMusic},
2616 @internalsref{UnfoldedRepeatedMusic}, and
2617 @internalsref{FoldedRepeatedMusic}.
2619 @node Tremolo repeats
2620 @subsection Tremolo repeats
2621 @cindex tremolo beams
2623 To place tremolo marks between notes, use @code{\repeat} with tremolo
2625 @lilypond[verbatim,raggedright]
2627 \context Voice \notes\relative c' {
2628 \repeat "tremolo" 8 { c16 d16 }
2629 \repeat "tremolo" 4 { c16 d16 }
2630 \repeat "tremolo" 2 { c16 d16 }
2635 Tremolo marks can also be put on a single note. In this case, the
2636 note should not be surrounded by braces.
2637 @lilypond[verbatim,raggedright]
2638 \repeat "tremolo" 4 c16
2641 A similar mechanism is the tremolo subdivision, described in
2642 @ref{Tremolo subdivisions}.
2646 In this manual: @ref{Tremolo subdivisions}, @ref{Repeats}.
2648 Internals: tremolo beams are @internalsref{Beam} objects. Single stem
2649 tremolos are @internalsref{StemTremolo}s. The music expression is
2650 @internalsref{TremoloEvent}.
2652 Example files: @inputfileref{input/regression,chord-tremolo.ly},
2653 @inputfileref{input/regression,stem-tremolo.ly}.
2655 @node Tremolo subdivisions
2656 @subsection Tremolo subdivisions
2657 @cindex tremolo marks
2658 @cindex @code{tremoloFlags}
2660 Tremolo marks can be printed on a single note by adding
2661 `@code{:}[@var{length}]' after the note. The length must be at least 8.
2662 A @var{length} value of 8 gives one line across the note stem. If the
2663 length is omitted, then then the last value (stored in
2664 @code{tremoloFlags}) is used:
2666 @lilypond[verbatim,fragment,center]
2667 c'2:8 c':32 | c': c': |
2670 @c [TODO : stok is te kort bij 32en]
2674 Tremolos in this style do not carry over into the MIDI output.
2678 In this manual: @ref{Tremolo repeats}.
2680 Elsewhere: @internalsref{StemTremolo}, @internalsref{TremoloEvent}.
2682 @node Measure repeats
2683 @subsection Measure repeats
2685 @cindex percent repeats
2686 @cindex measure repeats
2688 In the @code{percent} style, a note pattern can be repeated. It is
2689 printed once, and then the pattern is replaced with a special sign.
2690 Patterns of a one and two measures are replaced by percent-like signs,
2691 patterns that divide the measure length are replaced by slashes:
2693 @lilypond[verbatim,raggedright]
2694 \context Voice { \repeat "percent" 4 { c'4 }
2695 \repeat "percent" 2 { c'2 es'2 f'4 fis'4 g'4 c''4 }
2701 Internals: @internalsref{RepeatSlash}, @internalsref{PercentRepeat},
2702 @internalsref{PercentRepeatedMusic}, and
2703 @internalsref{DoublePercentRepeat}.
2707 @node Rhythmic music
2708 @section Rhythmic music
2712 * Showing melody rhythms::
2713 * Entering percussion::
2714 * Percussion staves::
2718 @node Showing melody rhythms
2719 @subsection Showing melody rhythms
2721 Sometimes you might want to show only the rhythm of a melody. This
2722 can be done with the rhythmic staff. All pitches of notes on such a
2723 staff are squashed, and the staff itself has a single line:
2725 @lilypond[fragment,relative,verbatim]
2726 \context RhythmicStaff {
2728 c4 e8 f g2 | r4 g r2 | g1:32 | r1 |
2734 Internals: @internalsref{RhythmicStaff}.
2736 Examples: @inputfileref{input/regression,rhythmic-staff.ly}.
2739 @node Entering percussion
2740 @subsection Entering percussion
2747 Percussion notes may be entered in @code{\drums} mode, which is
2748 similar to @code{notes}. Each piece of percussion has a full name and
2749 an abbreviated name, and both be used in input files:
2751 @lilypond[raggedright]
2752 \drums { hihat4 hh4 }
2755 The complete list of drum names is in the init file
2756 @file{ly/drumpitch-init.ly}.
2757 @c TODO: properly document this.
2761 Internals: @internalsref{DrumNoteEvent}.
2763 @node Percussion staves
2764 @subsection Percussion staves
2768 A percussion part for more than one instrument typically uses a
2769 multiline staff where each position in the staff refers to one piece
2773 To typeset the music, the notes must be interpreted in a
2774 @internalsref{DrumStaff} and @internalsref{DrumVoice} contexts:
2777 @lilypond[raggedright,verbatim,quote]
2778 up = \drums { crashcymbal4 hihat8 halfopenhihat hh hh hh openhihat }
2779 down = \drums { bassdrum4 snare8 bd r bd sn4 }
2782 << \new DrumVoice { \voiceOne \up }
2783 \new DrumVoice { \voiceTwo \down }
2787 The above example shows verbose polyphonic notation. The short
2788 polyphonic notation, described in @ref{Polyphony}, can also be used if
2789 the @internalsref{DrumVoices} are instantiated by hand first. For example,
2792 \drums \new DrumStaff <<
2793 \context DrumVoice = "1" { s1 *2 }
2794 \context DrumVoice = "2" { s1 *2 }
2798 { \repeat unfold 16 hh16 }
2807 There are also other layout possibilities. To use these, set the
2808 property @code{drumStyleTable} in context @internalsref{DrumVoice}.
2809 The following variables have been predefined:
2813 is the default. It typesets a typical drum kit on a five-line staff
2816 nam = \lyrics { cymc cyms cymr hh hhc hho hhho hhp cb hc
2817 bd sn ss tomh tommh tomml toml tomfh tomfl }
2818 mus = \drums { cymc cyms cymr hh | hhc hho hhho hhp | \break cb hc
2819 bd sn ss tomh tommh tomml toml tomfh tomfl s16 }
2821 << \new DrumStaff\with {
2822 \remove Bar_engraver
2823 \remove Time_signature_engraver
2824 \override Stem #'transparent = ##t
2825 \override Stem #'Y-extent-callback = ##f
2826 minimumVerticalExtent = #'(-4.0 . 5.0)
2828 \context Lyrics \nam
2831 %% need to do this, because of indented @itemize
2833 \translator { \ScoreContext
2834 \override BarNumber #'transparent =##T
2838 The drum scheme supports six different toms. When there fewer toms, simply
2839 select the toms that produce the desired result, i.e. to get toms on
2840 the three middle lines you use @code{tommh}, @code{tomml} and
2843 @item timbales-style
2844 to typeset timbales on a two line staff:
2846 @lilypond[raggedright]
2847 nam = \lyrics { timh ssh timl ssl cb }
2848 mus = \drums { timh ssh timl ssl cb s16 }
2851 \context DrumStaff \with {
2852 \remove Bar_engraver
2853 \remove Time_signature_engraver
2854 \override Stem #'transparent = ##t
2855 \override Stem #'Y-extent-callback = ##f
2856 \override StaffSymbol #'line-count = #2
2857 \override StaffSymbol #'staff-space = #2
2858 minimumVerticalExtent = #'(-3.0 . 4.0)
2859 drumStyleTable = #timbales-style
2861 \context Lyrics \nam
2866 to typeset congas on a two line staff:
2868 @lilypond[raggedright]
2869 nam = \lyrics { cgh cgho cghm ssh cgl cglo cglm ssl }
2870 mus = \drums { cgh cgho cghm ssh cgl cglo cglm ssl s16 }
2873 \context DrumStaff\with {
2874 \remove Bar_engraver
2875 \remove Time_signature_engraver
2876 drumStyleTable = #congas-style
2877 \override StaffSymbol #'line-count = #2
2879 %% this sucks; it will lengthen stems.
2880 \override StaffSymbol #'staff-space = #2
2881 \override Stem #'transparent = ##t
2882 \override Stem #'Y-extent-callback = ##f
2884 \context Lyrics \nam
2889 to typeset bongos on a two line staff:
2891 @lilypond[raggedright]
2892 nam = \lyrics { boh boho bohm ssh bol bolo bolm ssl }
2893 mus = \drums { boh boho bohm ssh bol bolo bolm ssl s16 }
2896 \context DrumStaff\with {
2897 \remove Bar_engraver
2898 \remove Time_signature_engraver
2899 \override StaffSymbol #'line-count = #2
2900 drumStyleTable = #bongos-style
2902 %% this sucks; it will lengthen stems.
2903 \override StaffSymbol #'staff-space = #2
2904 \override Stem #'transparent = ##t
2905 \override Stem #'Y-extent-callback = ##f
2907 \context Lyrics \nam
2912 @item percussion-style
2913 to typeset all kinds of simple percussion on one line staves:
2914 @lilypond[raggedright]
2915 nam = \lyrics { tri trio trim gui guis guil cb cl tamb cab mar hc }
2916 mus = \drums { tri trio trim gui guis guil cb cl tamb cab mar hc s16 }
2919 \context DrumStaff\with{
2920 \remove Bar_engraver
2921 drumStyleTable = #percussion-style
2922 \override StaffSymbol #'line-count = #1
2923 \remove Time_signature_engraver
2924 \override Stem #'transparent = ##t
2925 \override Stem #'Y-extent-callback = ##f
2927 \context Lyrics \nam
2933 If you do not like any of the predefined lists you can define your own
2934 list at the top of your file:
2936 @lilypond[raggedright,verbatim]
2938 (bassdrum default #f -1)
2939 (snare default #f 0)
2941 (pedalhihat xcircle "stopped" 2)
2942 (lowtom diamond #f 3)
2944 up = \drums { hh8 hh hh hh hhp4 hhp }
2945 down = \drums { bd4 sn bd toml8 toml }
2948 \set DrumStaff.drumStyleTable
2949 = #(alist->hash-table mydrums)
2950 \new DrumVoice { \voiceOne \up }
2951 \new DrumVoice { \voiceTwo \down }
2959 Init files: @file{ly/drumpitch-init.ly}.
2961 Internals: @internalsref{DrumStaff}, @internalsref{DrumVoice}.
2965 Short polyphonic notation, @code{<< @dots{} \\ @dots{} >>}, does not
2966 work for @internalsref{DrumVoices}.
2968 Because general MIDI does not contain rimshots the sidestick is used
2969 for this purpose instead.
2972 @section Piano music
2974 Piano staves are two normal staves coupled with a brace. The staves
2975 are largely independent, but sometimes voices can cross between the
2976 two staves. The same notation is also used for harps and other key
2977 instruments. The @internalsref{PianoStaff} is especially built to
2978 handle this cross-staffing behavior. In this section we discuss the
2979 @internalsref{PianoStaff} and some other pianistic peculiarities.
2983 * Automatic staff changes::
2984 * Manual staff switches::
2987 * Staff switch lines::
2992 There is no support for putting chords across staves. You can get
2993 this result by increasing the length of the stem in the lower stave so
2994 it reaches the stem in the upper stave, or vice versa. An example is
2995 included with the distribution as
2996 @inputfileref{input/test,stem-cross-staff.ly}.
2998 Dynamics are not centered, but kludges do exist. See
2999 @inputfileref{input/template,piano-dynamics.ly}.
3001 @cindex cross staff stem
3002 @cindex stem, cross staff
3004 The distance between the two staves is normally fixed across the
3005 entire score. It is possible to tune this per system, but it does
3006 require arcane command incantations. See
3007 @inputfileref{input/test,piano-staff-distance.ly}.
3014 @node Automatic staff changes
3015 @subsection Automatic staff changes
3016 @cindex Automatic staff changes
3018 Voices can switch automatically between the top and the bottom
3019 staff. The syntax for this is
3021 \autochange \context Voice @{ @dots{}@var{music}@dots{} @}
3023 The two staffs of the piano staff must be named @code{up} and
3026 The autochanger switches on basis of pitch (central C is the turning
3027 point), and it looks ahead skipping over rests to switch in
3028 advance. Here is a practical example:
3030 @lilypond[verbatim,raggedright,quote]
3031 \score { \notes \context PianoStaff <<
3032 \context Staff = "up" {
3033 \autochange \new Voice \relative c' {
3034 g4 a b c d r4 a g } }
3035 \context Staff = "down" {
3042 In this example, spacer rests are used to prevent the bottom staff from
3043 terminating too soon.
3048 In this manual: @ref{Manual staff switches}.
3050 Internals: @internalsref{AutoChangeMusic}.
3056 The staff switches often do not end up in optimal places. For high
3057 quality output, staff switches should be specified manually.
3061 @node Manual staff switches
3062 @subsection Manual staff switches
3064 @cindex manual staff switches
3065 @cindex staff switch, manual
3067 Voices can be switched between staves manually, using the following command:
3069 \change Staff = @var{staffname} @var{music}
3073 The string @var{staffname} is the name of the staff. It switches the
3074 current voice from its current staff to the Staff called
3075 @var{staffname}. Typically @var{staffname} is @code{"up"} or
3084 Pianos have pedals that alter the way sound are produced. Generally, a
3085 piano has three pedals, sustain, una corda, and sostenuto.
3089 Piano pedal instruction can be expressed by attaching
3090 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
3091 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
3094 @lilypond[fragment,verbatim]
3095 c'4\sustainDown c'4\sustainUp
3098 What is printed can be modified by setting @code{pedal@var{X}Strings},
3099 where @var{X} is one of the pedal types: @code{Sustain},
3100 @code{Sostenuto} or @code{UnaCorda}. Refer to the generated
3101 documentation of @internalsref{SustainPedal} for more information.
3103 Pedals can also be indicated by a sequence of brackets, by setting the
3104 @code{pedalSustainStyle} property to @code{bracket} objects:
3106 @lilypond[fragment,verbatim]
3107 \set Staff.pedalSustainStyle = #'bracket
3108 c''4\sustainDown d''4 e''4
3109 a'4\sustainUp\sustainDown
3110 f'4 g'4 a'4\sustainUp
3113 A third style of pedal notation is a mixture of text and brackets,
3114 obtained by setting the @code{pedalSustainStyle} style property to
3117 @lilypond[fragment,verbatim]
3118 \set Staff.pedalSustainStyle = #'mixed
3119 c''4\sustainDown d''4 e''4
3120 c'4\sustainUp\sustainDown
3121 f'4 g'4 a'4\sustainUp
3124 The default `*Ped' style for sustain and damper pedals corresponds to
3125 style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
3128 @lilypond[fragment,verbatim]
3129 c''4\sostenutoDown d''4 e''4 c'4 f'4 g'4 a'4\sostenutoUp
3132 For fine-tuning of the appearance of a pedal bracket, the properties
3133 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
3134 @code{PianoPedalBracket} objects (see
3135 @internalsref{PianoPedalBracket} in the Program reference) can be modified. For example, the
3136 bracket may be extended to the end of the note head:
3138 @lilypond[fragment,verbatim]
3139 \override Staff.PianoPedalBracket
3140 #'shorten-pair = #'(0 . -1.0)
3141 c''4\sostenutoDown d''4 e''4 c'4
3142 f'4 g'4 a'4\sostenutoUp
3146 @subsection Arpeggio
3149 @cindex broken arpeggio
3150 @cindex @code{\arpeggio}
3152 You can specify an arpeggio sign on a chord by attaching an
3153 @code{\arpeggio} to a chord:
3156 @lilypond[fragment,relative,verbatim]
3160 When an arpeggio crosses staves, you attach an arpeggio to the chords
3161 in both staves, and set
3162 @internalsref{PianoStaff}.@code{connectArpeggios}:
3164 @lilypond[fragment,relative,verbatim]
3165 \context PianoStaff <<
3166 \set PianoStaff.connectArpeggios = ##t
3167 \new Staff { <c' e g c>\arpeggio }
3168 \new Staff { \clef bass <c,, e g>\arpeggio }
3172 The direction of the arpeggio is sometimes denoted by adding an
3173 arrowhead to the wiggly line. This can be typeset by setting
3174 @code{arpeggio-direction}:
3176 @lilypond[fragment,relative,verbatim]
3178 \override Arpeggio #'arpeggio-direction = #1
3180 \override Arpeggio #'arpeggio-direction = #-1
3185 A square bracket on the left indicates that the player should not
3186 arpeggiate the chord. To draw these brackets, set the
3187 @code{print-function} property of @code{Arpeggio} or
3188 @code{PianoStaff.Arpeggio} objects to @code{\arpeggioBracket}, and use
3189 @code{\arpeggio} statements within the chords as before:
3191 @lilypond[fragment,relative,verbatim]
3192 \override PianoStaff.Arpeggio
3193 #'print-function = \arpeggioBracket
3199 @cindex @code{\arpeggioBracket}
3200 @code{\arpeggioBracket},
3201 @cindex @code{\arpeggio}
3206 Internals: @internalsref{ArpeggioEvent} music expressions lead to
3207 @internalsref{Arpeggio} objects. Cross staff arpeggios are
3208 @internalsref{PianoStaff}.@internalsref{Arpeggio}.
3212 It is not possible to mix connected arpeggios and unconnected
3213 arpeggios in one @internalsref{PianoStaff} at the same time.
3215 @node Staff switch lines
3216 @subsection Staff switch lines
3219 @cindex follow voice
3220 @cindex staff switching
3223 @cindex @code{followVoice}
3225 Whenever a voice switches to another staff a line connecting the notes
3226 can be printed automatically. This is enabled if the property
3227 @code{PianoStaff.followVoice} is set to true:
3229 @lilypond[fragment,relative,verbatim]
3230 \context PianoStaff <<
3231 \set PianoStaff.followVoice = ##t
3232 \context Staff \context Voice {
3237 \context Staff=two { \clef bass \skip 1*2 }
3241 The associated object is @internalsref{VoiceFollower}.
3245 @cindex @code{\showStaffSwitch}
3246 @code{\showStaffSwitch},
3247 @cindex @code{\hideStaffSwitch}
3248 @code{\hideStaffSwitch}.
3252 @section Vocal music
3254 This section discusses how to enter and print lyrics.
3258 * The Lyrics context::
3263 @node Entering lyrics
3264 @subsection Entering lyrics
3268 @cindex @code{\lyrics}
3271 Lyrics are entered in a special input mode. This mode is is introduced
3272 by the keyword @code{\lyrics}. In this mode you can enter lyrics, with
3273 punctuation and accents without any hassle. Syllables are entered like
3274 notes, but with pitches replaced by text. For example,
3276 \lyrics @{ Twin-4 kle4 twin- kle litt- le star2 @}
3279 A word in Lyrics mode begins with: an alphabetic character, @code{_},
3280 @code{?}, @code{!}, @code{:}, @code{'}, the control characters @code{^A}
3281 through @code{^F}, @code{^Q} through @code{^W}, @code{^Y}, @code{^^},
3282 any 8-bit character with ASCII code over 127, or a two-character
3283 combination of a backslash followed by one of @code{`}, @code{'},
3284 @code{"}, or @code{^}.
3286 Subsequent characters of a word can be any character that is not a digit
3287 and not white space. One important consequence of this is that a word
3288 can end with @code{@}}. The following example is usually a bug. The
3289 syllable includes a @code{@}}, and hence the opening brace is not balanced:
3291 \lyrics @{ twinkle@}
3294 @cindex @code{\property}, in @code{\lyrics}
3295 Similarly, a period following a alphabetic sequence, is included in
3296 the resulting string. As a consequence, spaces must be inserted around
3299 \override Score . LyricText #'font-shape = #'italic
3303 @cindex spaces, in lyrics
3304 @cindex quotes, in lyrics
3306 Any @code{_} character which appears in an unquoted word is converted
3307 to a space. This provides a mechanism for introducing spaces into words
3308 without using quotes. Quoted words can also be used in Lyrics mode to
3309 specify words that cannot be written with the above rules:
3312 \lyrics @{ He said: "\"Let" my peo ple "go\"" @}
3316 Hyphens can be entered as ordinary hyphens at the end of a syllable, i.e.
3321 These will be attached to the end of the first syllable.
3323 Centered hyphens are entered using the special `@code{-}@code{-}' lyric
3324 as a separate word between syllables. The hyphen will have variable
3325 length depending on the space between the syllables and it will be
3326 centered between the syllables.
3331 When a lyric is sung over many notes (this is called a melisma), this is
3332 indicated with a horizontal line centered between a syllable and the
3333 next one. Such a line is called an extender line, and it is entered as
3338 Internals: @internalsref{LyricEvent}, @internalsref{HyphenEvent}, and
3339 @internalsref{ExtenderEvent}.
3341 Examples: @inputfileref{input/test,lyric-hyphen-retain.ly}.
3345 The definition of lyrics mode is too complex.
3349 @node The Lyrics context
3350 @subsection The Lyrics context
3352 Lyrics are printed by interpreting them in a @internalsref{Lyrics} context:
3354 \context Lyrics \lyrics @dots{}
3357 @cindex automatic syllable durations
3358 @cindex @code{\lyricsto}
3359 @cindex lyrics and melodies
3361 This will place the lyrics according to the durations that were
3362 entered. The lyrics can also be aligned under a given melody
3363 automatically. In this case, it is no longer necessary to enter the
3364 correct duration for each syllable. This is achieved by combining the
3365 melody and the lyrics with the @code{\lyricsto} expression:
3367 \lyricsto @var{name} \new Lyrics @dots{}
3370 This aligns the lyrics to the
3372 notes of the @internalsref{Voice} context called @var{name}, which has
3373 to exist. Therefore, normally the @code{Voice} is specified first, and
3374 then the lyrics are specified with @code{\lyricsto}.
3376 For different or more complex orderings, the best way is to setup the
3377 hierarchy of staves and lyrics first, e.g.
3379 \context ChoirStaff \notes <<
3380 \context Lyrics = sopranoLyrics @{ s1 @}
3381 \context Voice = soprano @{ @emph{music} @}
3382 \context Lyrics = tenor @{ s1 @}
3383 \context Voice = tenorLyrics @{ @emph{music} @}
3386 and then combine the appropriate melodies and lyric lines:
3388 \lyricsto "soprano" \new Lyrics @emph{the lyrics}
3392 The final input would resemble
3395 << \context ChoirStaff \notes << @emph{setup the music} >>
3396 \lyricsto "soprano" @emph{etc}
3397 \lyricsto "alto" @emph{etc}
3403 The @code{\lyricsto} command detects melismata: it only puts one
3404 syllable under a tied or slurred group of notes. If you want to force
3405 an unslurred group of notes to be a melisma, then insert
3406 @code{\melisma} after the first note of the group, and
3407 @code{\melismaEnd} after the last one, e.g.
3409 @lilypond[relative=1,raggedright,fragment,verbatim]
3410 << \context Voice = "lala" { \time 3/4
3416 \lyricsto "lala" \new Lyrics \lyrics {
3421 In addition, notes are considered a melisma if they are manually
3422 beamed, and automatic beaming (see @ref{Setting automatic beam
3423 behavior}) is switched off. The criteria for deciding melismata
3424 can be tuned with the property @code{melismaBusyProperties}. See
3425 @internalsref{Melisma_translator} for more information.
3427 When multiple stanzas are put on the same melody, it can happen that
3428 two stanzas have melismata in different locations. This can be
3429 remedied by switching off melismata for one
3430 @internalsref{Lyrics}. This is achieved by setting
3431 the @code{ignoreMelismata} property to @code{#t}. An example is shown
3432 in @inputfileref{input/regression,lyric-combine-new.ly}.
3435 @cindex choral score
3437 A complete example of a SATB score setup is in the file
3438 @inputfileref{input/template,satb.ly}.
3443 @code{\melisma}, @code{\melismaEnd}
3444 @cindex @code{\melismaEnd}
3445 @cindex @code{\melisma}
3449 Internals: Music expressions: @internalsref{LyricCombineMusic},
3450 Contexts: @internalsref{Lyrics}, @internalsref{Melisma_translator}.
3452 Examples: @inputfileref{input/template,satb.ly},
3453 @inputfileref{input/regression,lyric-combine-new.ly}.
3457 Melismata are not detected automatically, and extender lines must be
3461 For proper processing of extender lines, the
3462 @internalsref{Lyrics} and @internalsref{Voice} should be
3463 linked. This can be achieved either by using @code{\lyricsto} or by
3464 setting corresponding names for both contexts. The latter is explained
3465 in @ref{More stanzas}.
3468 @subsection More stanzas
3470 @cindex phrasing, in lyrics
3473 The lyrics should be aligned with the note heads of the melody. To
3474 achieve this, each line of lyrics should be marked to correspond with
3475 the melodic line. This is done automatically when @code{\lyricsto},
3476 but it can also be done manually.
3478 To this end, give the @internalsref{Voice} context an identity:
3480 \context Voice = duet @{
3485 Then set the @internalsref{Lyrics} contexts to names starting with
3486 that identity followed by a dash. In the preceding example, the
3487 @internalsref{Voice} identity is @code{duet}, so the identities of the
3488 @internalsref{Lyrics}s are marked @code{duet-1} and @code{duet-2}:
3490 \context Lyrics = "duet-1" @{
3491 Hi, my name is bert. @}
3492 \context Lyrics = "duet-2" @{
3493 Ooooo, ch\'e -- ri, je t'aime. @}
3496 The complete example is shown here:
3497 @lilypond[raggedright,verbatim]
3499 << \notes \relative c'' \context Voice = duet { \time 3/4
3501 \lyrics << \lyricsto "duet" \new Lyrics {
3503 \set vocNam = "Bert"
3504 Hi, my name is bert. }
3505 \lyricsto "duet" \new Lyrics {
3507 \set vocNam = "Ernie"
3508 Ooooo, ch\'e -- ri, je t'aime.
3514 @cindex stanza number
3515 @cindex singer's names
3516 @cindex name of singer
3518 Stanza numbers can be added by setting @code{stanza}, e.g.
3526 Notice how dots are surrounded with spaces in @code{\lyrics} mode, to
3527 prevent @code{stanza} being interpreted as a single
3530 This example also demonstrates how names of the singers can be added
3531 using @code{vocalName} analogous to instrument annotations for staves.
3532 A short version may be entered as @code{vocNam}.
3534 To make empty spaces in lyrics, use @code{\skip}.
3539 Internals: Layout objects @internalsref{LyricText} and
3540 @internalsref{VocalName}. Music expressions:
3541 @internalsref{LyricEvent}.
3547 Input for lyrics introduces a syntactical ambiguity:
3554 is interpreted as assigning a string identifier @code{\foo} such that
3555 it contains @code{"bar"}. However, it could also be interpreted as
3556 making or a music identifier @code{\foo} containing the syllable
3557 `bar'. The force the latter interpretation, use
3567 The term @emph{ambitus} (plural: ambituses) denotes a range of pitches
3568 for a given voice in a part of music. It also may denote the pitch
3569 range that a musical instrument is capable of playing. Most musical
3570 instruments have their ambitus standardized (or at least there is
3571 agreement upon the minimal ambitus of a particular type of
3572 instrument), such that a composer or arranger of a piece of music can
3573 easily meet the ambitus constraints of the targeted instrument.
3574 However, the ambitus of the human voice depends on individual
3575 physiological state, including education and training of the voice.
3576 Therefore, a singer potentially has to check for each piece of music
3577 if the ambitus of that piece meets his individual capabilities. This
3578 is why the ambitus of a piece may be of particular value to vocal
3581 The ambitus is typically notated on a per-voice basis at the very
3582 beginning of a piece, e.g. nearby the initial clef or time signature of
3583 each staff. The range is graphically specified by two noteheads, that
3584 represent the minimum and maximum pitch. Some publishers use a textual
3585 notation: they put the range in words in front of the corresponding
3586 staff. LilyPond only supports the graphical ambitus notation.
3588 To apply, add the @internalsref{Ambitus_engraver} to the
3589 @internalsref{Voice} context, i.e.
3595 \consists Ambitus_engraver
3600 This results in the following output:
3602 @lilypond[raggedright]
3603 upper = \notes \relative c {
3606 as'' c e2 bes f cis d4 e f2 g
3608 lower = \notes \relative c {
3611 e'4 b g a c es fis a cis b a g f e d2
3614 \context ChoirStaff {
3616 \new Staff { \upper }
3617 \new Staff { \lower }
3623 \consists Ambitus_engraver
3629 If you have multiple voices in a single staff, and you want a single
3630 ambitus per staff rather than per each voice, then add the
3631 @internalsref{Ambitus_engraver} to the @internalsref{Staff} context
3632 rather than to the @internalsref{Voice} context.
3634 It is possible to tune individual ambituses for multiple voices on a
3635 single staff, for example by erasing or shifting them horizontally. An
3636 example is in @inputfileref{input/test,ambitus-mixed.ly}.
3640 Internals: @internalsref{Ambitus}.
3642 Examples: @inputfileref{input/regression,ambitus.ly},
3643 @inputfileref{input/test,ambitus-mixed.ly}.
3647 There is no collision handling in the case of multiple per-voice
3653 Tablature notation is used for notating music for plucked string
3654 instruments. It notates pitches not by using note heads, but by
3655 indicating on which string and fret a note must be played. LilyPond
3656 offers limited support for tablature.
3659 * Tablatures basic::
3660 * Non-guitar tablatures::
3663 @node Tablatures basic
3664 @subsection Tablatures basic
3665 @cindex Tablatures basic
3667 The string number associated to a note is given as a backslash
3668 followed by a number, e.g. @code{c4\3} for a C quarter on the third
3669 string. By default, string 1 is the highest one, and the tuning
3670 defaults to the standard guitar tuning (with 6 strings). The notes
3671 are printed as tablature, by using @internalsref{TabStaff} and
3672 @internalsref{TabVoice} contexts:
3674 @lilypond[fragment,verbatim]
3675 \notes \context TabStaff {
3683 When no string is specified, the first string that does not give a
3684 fret number less than @code{minimumFret} is selected. The default
3685 value for @code{minimumFret} is 0:
3689 e8 fis gis a b cis' dis' e'
3690 \set TabStaff.minimumFret = #8
3691 e8 fis gis a b cis' dis' e'
3696 e8 fis gis a b cis' dis' e'
3697 \set TabStaff.minimumFret = #8
3698 e8 fis gis a b cis' dis' e'
3701 \context StaffGroup <<
3702 \context Staff { \clef "G_8" \frag }
3703 \context TabStaff { \frag }
3710 Internals: @internalsref{TabStaff}, @internalsref{TabVoice}, and
3711 @internalsref{StringNumberEvent}.
3715 Chords are not handled in a special way, and hence the automatic
3716 string selector may easily select the same string to two notes in a
3720 @node Non-guitar tablatures
3721 @subsection Non-guitar tablatures
3722 @cindex Non-guitar tablatures
3724 You can change the number of strings, by setting the number of lines
3725 in the @internalsref{TabStaff}.
3727 You can change the tuning of the strings. A string tuning is given as
3728 a Scheme list with one integer number for each string, the number
3729 being the pitch (measured in semitones relative to central C) of an
3730 open string. The numbers specified for @code{stringTuning} are the
3731 numbers of semitones to subtract or add, starting the specified pitch
3732 by default middle C, in string order. Thus, the notes are e, a, d, and
3735 @lilypond[fragment,verbatim]
3736 \context TabStaff <<
3737 \set TabStaff.stringTunings = #'(-5 -10 -15 -20)
3740 a,4 c' a e' e c' a e'
3745 It is possible to change the Scheme function to format the tablature
3746 note text. The default is @code{fret-number-tablature-format}, which
3747 uses the fret number. For instruments that do not use this notation,
3748 you can create a special tablature formatting function. This function
3749 takes three argument: string number, string tuning and note pitch.
3753 No guitar special effects have been implemented.
3758 @section Chord names
3761 LilyPond has support for both printing chord names. Chords may be
3762 entered in musical chord notation, i.e. @code{< .. >}, but they can
3763 also be entered by name. Internally, the chords are represented as a
3764 set of pitches, so they can be transposed:
3767 @lilypond[verbatim,raggedright]
3768 twoWays = \notes \transpose c c' {
3778 << \context ChordNames \twoWays
3779 \context Voice \twoWays >> }
3782 This example also shows that the chord printing routines do not try to
3783 be intelligent. The last chord (@code{f bes d}) is not interpreted as
3789 * Printing chord names::
3794 @subsection Chords mode
3797 Chord mode is a mode where you can input sets of pitches using common
3798 names. It is introduced by the keyword @code{\chords}.
3799 In chords mode, a chord is entered by the root, which is entered
3800 like a common pitch:
3801 @lilypond[fragment,verbatim,quote,relative=1]
3802 \chords { es4. d8 c2 }
3807 Other chords may be entered by suffixing a colon, and introducing a
3808 modifier, and optionally, a number:
3810 @lilypond[fragment,verbatim,quote]
3811 \chords { e1:m e1:7 e1:m7 }
3813 The first number following the root is taken to be the `type' of the
3814 chord, thirds are added to the root until it reaches the specified
3816 @lilypond[fragment,verbatim]
3817 \chords { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 }
3820 @cindex root of chord
3821 @cindex additions, in chords
3822 @cindex removals, in chords
3824 More complex chords may also be constructed adding separate steps
3825 to a chord. Additions are added after the number following
3826 the colon, and are separated by dots:
3828 @lilypond[verbatim,fragment,quote]
3829 \chords { c:5.6 c:3.7.8 c:3.6.13 }
3831 Chord steps can be altered by suffixing a @code{-} or @code{+} sign
3833 @lilypond[verbatim,fragment,quote]
3834 \chords { c:7+ c:5+.3- c:3-.5-.7- }
3836 Removals are specified similarly, and are introduced by a caret. They
3837 must come after the additions:
3838 @lilypond[verbatim,fragment]
3839 \chords { c^3 c:7^5 c:9^3.5 }
3842 Modifiers can be used to change pitches. The following modifiers are
3846 is the minor chord. This modifier lowers the 3rd and (if present) the 7th step.
3848 is the diminished chord. This modifier lowers the 3rd, 5th and (if present)
3851 is the augmented chord. This modifier raises the 5th step.
3853 is the major 7th chord. This modifier raises the 7th step if present.
3855 is the suspended 4th or 2nd. This modifier removes the 3rd
3856 step. Append either @code{2} or @code{4} to add the 2nd or 4th step to
3859 Modifiers can be mixed with additions:
3860 @lilypond[verbatim,fragment]
3861 \chords { c:sus4 c:7sus4 c:dim7 c:m6 }
3864 @cindex modifiers, in chords.
3871 Since an unaltered 11 does not sound good when combined with an
3872 unaltered 13, the 11 is removed in this case (unless it is added
3875 @lilypond[fragment,verbatim]
3876 \chords { c:13 c:13.11 c:m13 }
3881 An inversion (putting one pitch of the chord on the bottom), as well
3882 as bass notes, can be specified by appending
3883 @code{/}@var{pitch} to the chord:
3884 @lilypond[fragment,verbatim,center]
3885 \chords { c1 c/g c/f }
3889 A bass note can be added instead of transposed out of the chord,
3890 by using @code{/+}@var{pitch}.
3892 @lilypond[fragment,verbatim,center]
3893 \chords { c1 c/+g c/+f }
3896 Chords is a mode similar to @code{\lyrics}, @code{\notes} etc. Most
3897 of the commands continue to work, for example, @code{r} and
3898 @code{\skip} can be used to insert rests and spaces, and property
3899 commands may be used to change various settings.
3905 Each step can only be present in a chord once. The following
3906 simply produces the augmented chord, since @code{5+} is interpreted
3909 @lilypond[verbatim,fragment]
3910 \chords { c:5.5-.5+ }
3914 @node Printing chord names
3915 @subsection Printing chord names
3917 @cindex printing chord names
3921 For displaying printed chord names, use the @internalsref{ChordNames} context.
3922 The chords may be entered either using the notation
3923 described above, or directly using @code{<} and @code{>}:
3925 @lilypond[verbatim,raggedright]
3927 \chords {a1 b c} <d' f' a'> <e' g' b'>
3931 \context ChordNames \scheme
3932 \context Staff \scheme
3937 You can make the chord changes stand out by setting
3938 @internalsref{ChordNames}.@code{chordChanges} to true. This will only
3939 display chord names when there is a change in the chords scheme and at
3940 the start of a new line:
3942 @lilypond[verbatim,linewidth=9\cm]
3944 c1:m c:m \break c:m c:m d
3948 \context ChordNames {
3949 \set chordChanges = ##t
3951 \context Staff \transpose c c' \scheme
3956 The default chord name layout is a system for Jazz music, proposed by
3957 Klaus Ignatzek (see @ref{Literature list}). It can be tuned through the
3958 following properties:
3961 @cindex chordNameExceptions
3962 @item chordNameExceptions
3963 This is a list that contains the chords that have special formatting.
3965 @inputfileref{input/regression,chord-name-exceptions.ly}.
3966 @cindex exceptions, chord names.
3969 @cindex majorSevenSymbol
3970 @item majorSevenSymbol
3971 This property contains the markup object used for the 7th step, when
3972 it is major. Predefined options are @code{whiteTriangleMarkup} and
3973 @code{blackTriangleMarkup}. See
3974 @inputfileref{input/regression,chord-name-major7.ly} for an example.
3976 @cindex chordNameSeparator
3977 @item chordNameSeparator
3978 Different parts of a chord name are normally separated by a
3979 slash. By setting @code{chordNameSeparator}, you can specify other
3981 @lilypond[fragment,verbatim]
3982 \context ChordNames \chords {
3984 \set chordNameSeparator
3985 = \markup { \typewriter "|" }
3989 @cindex chordRootNamer
3990 @item chordRootNamer
3991 The root of a chord is usually printed as a letter with an optional
3992 alteration. The transformation from pitch to letter is done by this
3993 function. Special note names (for example, the German ``H'' for a
3994 B-chord) can be produced by storing a new function in this property.
3996 The pre-defined variables @code{\germanChords},
3997 @code{\semiGermanChords} set these variables.
4000 @cindex chordNoteNamer
4001 @item chordNoteNamer
4002 The default is to print single pitch, e.g. the bass note, using the
4003 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
4004 to a specialized function to change this behavior. For example, the
4005 base can be printed in lower case.
4010 There are also two other chord name schemes implemented: an alternate
4011 Jazz chord notation, and a systematic scheme called Banter chords. The
4012 alternate jazz notation is also shown on the chart in @ref{Chord name
4013 chart}. Turning on these styles is described in the input file
4014 @inputfileref{input/test,chord-names-jazz.ly}.
4018 @cindex chords, jazz
4023 @cindex @code{\germanChords}
4024 @code{\germanChords},
4025 @cindex @code{\semiGermanChords}
4026 @code{\semiGermanChords}.
4033 Examples: @inputfileref{input/regression,chord-name-major7.ly},
4034 @inputfileref{input/regression,chord-name-exceptions.ly},
4035 @inputfileref{input/test,chord-names-jazz.ly},
4036 @inputfileref{input/test,chord-names-german.ly}.
4038 Init files: @file{scm/chords-ignatzek.scm}, and @file{scm/chord-entry.scm}.
4043 Chord names are determined solely from the list of pitches. Chord
4044 inversions are not identified, and neither are added bass notes. This
4045 may result in strange chord names when chords are entered with the
4046 @code{< .. >} syntax.
4051 @node Orchestral music
4052 @section Orchestral music
4054 @cindex Writing parts
4056 Orchestral music involves some special notation, both in the full
4057 score and the individual parts. This section explains how to tackle
4058 some common problems in orchestral music.
4063 * Multiple staff contexts::
4066 * Instrument names::
4068 * Multi measure rests::
4069 * Automatic part combining::
4071 * Different editions from one source::
4072 * Sound output for transposing instruments::
4075 @node Multiple staff contexts
4076 @subsection Multiple staff contexts
4078 Polyphonic scores consist of many staves. These staves can be
4079 constructed in three different ways:
4081 @item The group is started with a brace at the left. This is done with the
4082 @internalsref{GrandStaff} context.
4083 @item The group is started with a bracket. This is done with the
4084 @internalsref{StaffGroup} context
4085 @item The group is started with a vertical line. This is the default
4089 @cindex Staff, multiple
4090 @cindex bracket, vertical
4091 @cindex brace, vertical
4098 @node Rehearsal marks
4099 @subsection Rehearsal marks
4100 @cindex Rehearsal marks
4102 @cindex @code{\mark}
4104 To print a rehearsal mark, use the @code{\mark} command:
4105 @lilypond[fragment,verbatim]
4116 (The letter I is skipped in accordance with engraving traditions.)
4118 The mark is incremented automatically if you use @code{\mark
4119 \default}, but you can also use an integer argument to set the mark
4120 manually. The value to use is stored in the property
4121 @code{rehearsalMark}.
4123 The style is defined by the property @code{markFormatter}. It is a
4124 function taking the current mark (an integer) and the current context
4125 as argument. It should return a markup object. In the following
4126 example, @code{markFormatter} is set to a canned procedure. After a
4127 few measures, it is set to function that produces a boxed number.
4129 @lilypond[verbatim,fragment,relative=1]
4130 \set Score.markFormatter = #format-mark-numbers
4133 \set Score.markFormatter
4134 = #(lambda (mark context)
4135 (make-bold-markup (make-box-markup (number->string mark))))
4140 The file @file{scm/translation-functions.scm} contains the definitions
4141 of @code{format-mark-numbers} (the default format) and
4142 @code{format-mark-letters}. They can be used as inspiration for other
4143 formatting functions.
4146 @cindex coda on bar line
4147 @cindex segno on bar line
4148 @cindex fermata on bar line
4149 @cindex bar lines, symbols on
4151 The @code{\mark} command can also be used to put signs like coda,
4152 segno and fermatas on a barline. Use @code{\markup} to
4153 to access the appropriate symbol:
4155 @lilypond[fragment,verbatim,relative=1]
4156 c1 \mark \markup { \musicglyph #"scripts-ufermata" }
4160 In this case, during line breaks, marks must also be printed at the
4161 end of the line, and not at the beginning. Use the following to force
4164 \override Score.RehearsalMark
4165 #'break-visibility = #begin-of-line-invisible
4171 @cindex barlines, putting symbols on
4175 Internals: @internalsref{MarkEvent}, @internalsref{RehearsalMark}.
4177 Init files: @file{scm/translation-functions.scm} contains the
4178 definition of @code{format-mark-numbers} and
4179 @code{format-mark-letters}. They can be used as inspiration for other
4180 formatting functions.
4182 Examples: @inputfileref{input/regression,rehearsal-mark-letter.ly},
4183 @inputfileref{input/regression,rehearsal-mark-number.ly}.
4187 @subsection Bar numbers
4191 @cindex measure numbers
4192 @cindex currentBarNumber
4194 Bar numbers are printed by default at the start of the line. The
4195 number itself is stored in the
4196 @code{currentBarNumber} property,
4197 which is normally updated automatically for every measure.
4199 Bar numbers can be typeset at regular intervals instead of at the
4200 beginning of each line. This is illustrated in the following example,
4201 whose source is available as
4202 @inputfileref{input/test,bar-number-regular-interval.ly}:
4204 @lilypondfile[]{bar-number-regular-interval.ly}
4209 Internals: @internalsref{BarNumber}.
4211 Examples: @inputfileref{input/test,bar-number-every-five-reset.ly},
4212 and @inputfileref{input/test,bar-number-regular-interval.ly}.
4216 Bar numbers can collide with the @internalsref{StaffGroup} bracket, if
4217 there is one at the top. To solve this, the
4218 @code{padding} property of @internalsref{BarNumber} can be
4219 used to position the number correctly.
4221 @node Instrument names
4222 @subsection Instrument names
4224 In an orchestral score, instrument names are printed left side of the
4227 This can be achieved by setting @internalsref{Staff}.@code{instrument}
4228 and @internalsref{Staff}.@code{instr}. This will print a string before
4229 the start of the staff. For the first start, @code{instrument} is
4230 used, for the next ones @code{instr} is used:
4233 @lilypond[verbatim,raggedright]
4234 \set Staff.instrument = "ploink " { c''4 }
4238 You can also use markup texts to construct more complicated instrument
4242 @lilypond[fragment,verbatim,raggedright]
4244 \set Staff.instrument = \markup {
4245 \column < "Clarinetti"
4258 Internals: @internalsref{InstrumentName}.
4262 When you put a name on a grand staff or piano staff the width of the
4263 brace is not taken into account. You must add extra spaces to the end of
4264 the name to avoid a collision.
4267 @subsection Transpose
4269 @cindex transposition of pitches
4270 @cindex @code{\transpose}
4272 A music expression can be transposed with @code{\transpose}. The syntax
4275 \transpose @var{from} @var{to} @var{musicexpr}
4278 This means that @var{musicexpr} is transposed by the interval between
4279 the pitches @var{from} and @var{to}: any note with pitch @code{from}
4280 is changed to @code{to}.
4283 For example, consider a piece written in the key of D major. If
4284 this piece is a little too low for its performer, it can be
4285 transposed up to E major with
4287 \tranpose d e @dots{}
4290 Consider a part written for violin (a C instrument). If
4291 this part is to be played on the A clarinet, the following
4292 transposition will produce the appropriate part
4295 \transpose a c @dots{}
4298 Since @var{from} and @var{to} are pitches, @code{\transpose} must be
4299 inside a @code{\notes} section. @code{\transpose} distinguishes
4300 between enharmonic pitches: both @code{\transpose c cis} or
4301 @code{\transpose c des} will transpose up half a tone. The first
4302 version will print sharps and the second version will print flats:
4304 @lilypond[raggedright,verbatim]
4305 mus =\notes { \key d \major cis d fis g }
4306 \score { \notes \context Staff {
4309 \transpose c g' \mus
4310 \transpose c f' \mus
4317 Internals: @internalsref{TransposedMusic}, and
4318 @internalsref{UntransposableMusic}.
4322 If you want to use both @code{\transpose} and @code{\relative}, then
4323 you must put @code{\transpose} outside of @code{\relative}, since
4324 @code{\relative} will have no effect music that appears inside a
4330 @node Multi measure rests
4331 @subsection Multi measure rests
4332 @cindex multi measure rests
4333 @cindex Rests, multi measure
4337 Multi measure rests are entered using `@code{R}'. It is specifically
4338 meant for full bar rests and for entering parts: the rest can expand
4339 to fill a score with rests, or it can be printed as a single
4340 multimeasure rest. This expansion is controlled by the property
4341 @code{Score.skipBars}. If this is set to true, empty measures will not
4342 be expanded, and the appropriate number is added automatically:
4344 @lilypond[fragment,verbatim]
4345 \time 4/4 r1 | R1 | R1*2
4346 \set Score.skipBars = ##t R1*17 R1*4
4349 The @code{1} in @code{R1} is similar to the duration notation used for
4350 notes. Hence, for time signatures other than 4/4, you must enter other
4351 durations. This can be done with augmentation dots or fractions:
4353 @lilypond[fragment,verbatim]
4354 \set Score.skipBars = ##t
4362 An @code{R} spanning a single measure is printed as either a whole rest
4363 or a breve, centered in the measure regardless of the time signature.
4365 @cindex text on multi-measure rest
4366 @cindex script on multi-measure rest
4367 @cindex fermata on multi-measure rest
4369 Texts can be added to multi-measure rests by using the
4370 @var{note}-@code{markup} syntax (see @ref{Text markup}). In this case, the number is
4371 replaced. If you need both texts and the number, you must add the
4372 number by hand. A variable (@code{\fermataMarkup}) is provided for
4376 @lilypond[verbatim,fragment]
4378 R2._\markup { "Ad lib" }
4382 If you want to have a text on the left end of a multi-measure rest,
4383 attach the text to a zero-length skip note, i.e.
4391 @cindex whole rests for a full measure
4395 Internals: @internalsref{MultiMeasureRestEvent},
4396 @internalsref{MultiMeasureTextEvent},
4397 @internalsref{MultiMeasureRestMusicGroup}, and
4398 @internalsref{MultiMeasureRest}.
4400 The layout object @internalsref{MultiMeasureRestNumber} is for the
4401 default number, and @internalsref{MultiMeasureRestText} for user
4406 It is not possible to use fingerings (e.g. @code{R1-4}) to put numbers
4407 over multi-measure rests.
4409 @cindex condensing rests
4411 There is no way to automatically condense multiple rests into a single
4412 multimeasure rest. Multi measure rests do not take part in rest
4415 Be careful when entering multimeasure rests followed by whole
4416 notes. The following will enter two notes lasting four measures each:
4420 When @code{skipBars} is set, then the result will look OK, but the
4421 bar numbering will be off.
4423 @node Automatic part combining
4424 @subsection Automatic part combining
4425 @cindex automatic part combining
4426 @cindex part combiner
4429 Automatic part combining is used to merge two parts of music onto a
4430 staff. It is aimed at typesetting orchestral scores. When the two
4431 parts are identical for a period of time, only one is shown. In
4432 places where the two parts differ, they are typeset as separate
4433 voices, and stem directions are set automatically. Also, solo and
4434 @emph{a due} parts are identified and can be marked.
4438 The syntax for part combining is
4441 \partcombine @var{musicexpr1} @var{musicexpr2}
4444 The music expressions will be interpreted as @internalsref{Voice} contexts.
4446 The following example demonstrates the basic functionality of the part
4447 combiner: putting parts on one staff, and setting stem directions and
4450 @lilypond[verbatim,raggedright,fragment,relative=1]
4451 \new Staff \partcombine
4460 The first @code{g} appears only once, although it was
4461 specified twice (once in each part). Stem, slur and tie directions are
4462 set automatically, depending whether there is a solo or unisono. The
4463 first part (with context called @code{one}) always gets up stems, and
4464 `solo', while the second (called @code{two}) always gets down stems and
4467 If you just want the merging parts, and not the textual markings, you
4468 may set the property @var{soloADue} to false:
4470 @lilypond[verbatim,raggedright,fragment]
4472 \set Staff.soloADue = ##f
4484 Internals: @internalsref{PartCombineMusic},
4485 @internalsref{SoloOneEvent}, and
4486 @internalsref{SoloTwoEvent}, and
4487 @internalsref{UnisonoEvent}.
4491 In @code{soloADue} mode, when the two voices play the same notes on and
4492 off, the part combiner may typeset @code{a2} more than once in a
4495 @code{\partcombine} can not be inside @code{\times}.
4500 @subsection Hiding staves
4502 @cindex Frenched scores
4503 @cindex Hiding staves
4505 In orchestral scores, staff lines that only have rests are usually
4506 removed. This saves some space. This style is called `French Score'.
4507 For @internalsref{Lyrics}, @internalsref{Lyrics},
4508 @internalsref{ChordNames} and @internalsref{FiguredBass}, this is
4509 switched on by default. When these line of these contexts turn out
4510 empty after the line-breaking process, they are removed.
4512 For normal staves, a specialized @internalsref{Staff} context is
4513 available, which does the same: staves containing nothing (or only
4514 multi measure rests) are removed. The context definition is stored in
4515 @code{\RemoveEmptyStaffContext} variable. Observe how the second staff
4516 in this example disappears in the second line:
4521 \notes \relative c' <<
4522 \new Staff { e4 f g a \break c1 }
4523 \new Staff { c4 d e f \break R1 }
4527 \translator { \RemoveEmptyStaffContext }
4532 The first page shows all staffs in full. If they should be removed
4533 from the first page too, set @code{remove-first} to false
4534 in @internalsref{RemoveEmptyVerticalGroup}.
4536 Another application is making ossia sections, i.e. alternative
4537 melodies on a separate piece of staff, with help of a Frenched
4538 staff. See @inputfileref{input/test,ossia.ly} for an example.
4541 @node Different editions from one source
4542 @subsection Different editions from one source
4544 The @code{\tag} command marks music expressions with a name. These
4545 tagged expressions can be filtered out later. With this mechanism it
4546 is possible to make different versions of the same music source.
4548 In the following example, we see two versions of a piece of music, one
4549 for the full score, and one with cue notes for the instrumental part:
4565 The same can be applied to articulations, texts, etc.: they are
4568 -\tag #@var{your-tag}
4570 to an articulation, for example,
4575 This defines a note with a conditional fingering indication.
4577 By applying the @code{remove-tag} function, tagged expressions can be
4578 filtered. For example,
4582 \apply #(remove-tag 'score) @var{the music}
4583 \apply #(remove-tag 'part) @var{the music}
4588 @lilypondfile[]{tag-filter.ly}
4590 The argument of the @code{\tag} command should be a symbol, or a list
4591 of symbols, for example,
4593 \tag #'(original-part transposed-part) @dots{}
4598 Examples: @inputfileref{input/regression,tag-filter.ly}.
4601 @node Sound output for transposing instruments
4602 @subsection Sound output for transposing instruments
4604 When you want to make a MIDI file from a score containing transposed
4605 and untransposed instruments, you have to instruct LilyPond the pitch
4606 offset (in semitones) for the transposed instruments. This is done
4607 using the @code{transposing} property. It does not affect printed
4610 @cindex @code{transposing}
4613 \set Staff.instrument = #"Cl. in B-flat"
4614 \set Staff.transposing = #-2
4618 @node Ancient notation
4619 @section Ancient notation
4621 @cindex Vaticana, Editio
4622 @cindex Medicaea, Editio
4627 @c [TODO: write more comprehensive introduction on ancient notation]
4629 Support for ancient notation is still under heavy development.
4630 Regardless of all of the current limitations (see the bugs section
4631 below for details), it includes features for mensural
4632 notation and Gregorian Chant notation. There is also limited support
4633 for figured bass notation.
4635 Many graphical objects provide a @code{style} property, see
4636 @ref{Ancient note heads}, @ref{Ancient accidentals}, @ref{Ancient
4637 rests}, @ref{Ancient clefs}, @ref{Ancient flags} and @ref{Ancient time
4638 signatures}. By manipulating such a grob property, the typographical
4639 appearance of the affected graphical objects can be accomodated for a
4640 specific notation flavour without need for introducing any new
4644 Other aspects of ancient notation can not that easily be expressed as
4645 in terms of just changing a style property of a graphical object.
4646 Therefore, some notational concepts are introduced specifically for
4647 ancient notation, see @ref{Custodes}, @ref{Divisiones},
4648 @ref{Ligatures}, and @ref{Figured bass}.
4652 * Ancient note heads::
4653 * Ancient accidentals::
4657 * Ancient time signatures::
4662 * Vaticana style contexts::
4665 If this all is way too much of documentation for you, and you just
4666 want to dive into typesetting without worrying too much about the
4667 details on how to customize a context, then you may have a look at the
4668 predefined contexts (see @ref{Vaticana style contexts}). Use them to
4669 set up predefined style-specific voice and staff contexts, and
4670 directly go ahead with the note entry.
4674 Ligatures need special spacing that has not yet been implemented. As
4675 a result, there is too much space between ligatures most of the time,
4676 and line breaking often is unsatisfactory. Also, lyrics do not
4677 correctly align with ligatures.
4679 Accidentals must not be printed within a ligature, but instead need to
4680 be collected and printed in front of it.
4682 Augmentum dots within ligatures are not handled correctly.
4685 @node Ancient note heads
4686 @subsection Ancient note heads
4692 For ancient notation, a note head style other than the @code{default}
4693 style may be chosen. This is accomplished by setting the @code{style}
4694 property of the NoteHead object to the desired value (@code{baroque},
4695 @code{neo_mensural} or @code{mensural}). The @code{baroque} style
4696 differs from the @code{default} style only in using a square shape for
4697 @code{\breve} note heads. The @code{neo_mensural} style differs from
4698 the @code{baroque} style in that it uses rhomboidal heads for whole
4699 notes and all smaller durations. Stems are centered on the note
4700 heads. This style is in particular useful when transcribing mensural
4701 music, e.g. for the incipit. The @code{mensural} style finally
4702 produces note heads that mimick the look of note heads in historic
4703 printings of the 16th century.
4705 The following example demonstrates the @code{neo_mensural} style:
4707 @lilypond[fragment,raggedright,verbatim]
4708 \override NoteHead #'style = #'neo_mensural
4709 a'\longa a'\breve a'1 a'2 a'4 a'8 a'16
4712 When typesetting a piece in Gregorian Chant notation, a Gregorian
4713 ligature engraver will automatically select the proper note heads,
4714 such there is no need to explicitly set the note head style. Still,
4715 the note head style can be set e.g. to @code{vaticana_punctum} to
4716 produce punctum neumes. Similarly, a mensural ligature engraver is
4717 used to automatically assemble mensural ligatures. See
4718 @ref{Ligatures} for how ligature engravers work.
4723 @ref{Percussion staves} use note head styles of their own that are
4724 frequently used in contemporary music notation.
4726 Examples: @inputfileref{input/regression,note-head-style.ly} gives an
4727 overview over all available note head styles.
4730 @node Ancient accidentals
4731 @subsection Ancient accidentals
4737 Use the @code{style} property of grob @internalsref{Accidental} to
4738 select ancient accidentals. Supported styles are
4739 @code{mensural}, @code{vaticana}, @code{hufnagel} and @code{medicaea}.
4741 @lilypond[raggedright,staffsize=26]
4749 { " " \musicglyph #"accidentals-vaticana-1"
4750 " " \musicglyph #"accidentals-vaticana0" }
4754 { " " \musicglyph #"accidentals-medicaea-1" }
4758 { " " \musicglyph #"accidentals-hufnagel-1" }
4762 { " " \musicglyph #"accidentals-mensural-1"
4763 " " \musicglyph #"accidentals-mensural1" }
4772 \remove "Bar_number_engraver"
4776 \remove "Clef_engraver"
4777 \remove "Key_engraver"
4778 \remove "Time_signature_engraver"
4779 \remove "Staff_symbol_engraver"
4780 minimumVerticalExtent = ##f
4786 As shown, not all accidentals are supported by each style. When
4787 trying to access an unsupported accidental, LilyPond will switch to a
4788 different style, as demonstrated in
4789 @inputfileref{input/test,ancient-accidentals.ly}.
4791 Similarly to local accidentals, the style of the key signature can be
4792 controlled by the @code{style} property of the
4793 @internalsref{KeySignature} grob.
4797 In this manual: @ref{Pitches}, @ref{Chromatic alterations} and
4798 @ref{Accidentals} give a general introduction into the use of
4799 accidentals. @ref{Key signature} gives a general introduction into
4800 the use of key signatures.
4802 Internals: @internalsref{KeySignature}.
4804 Examples: @inputfileref{input/test,ancient-accidentals.ly}.
4807 @subsection Ancient rests
4813 Use the @code{style} property of grob @internalsref{Rest} to select
4814 ancient accidentals. Supported styles are @code{classical},
4815 @code{neo_mensural} and @code{mensural}. @code{classical} differs
4816 from the @code{default} style only in that the quarter rest looks like
4817 a horizontally mirrored 8th rest. The @code{neo_mensural} style suits
4818 well for e.g. the incipit of a transcribed mensural piece of music.
4819 The @code{mensural} style finally mimicks the appearance of rests as
4820 in historic prints of the 16th century.
4822 The following example demonstrates the @code{neo_mensural} style:
4824 @lilypond[fragment,raggedright,verbatim]
4825 \override Rest #'style = #'neo_mensural
4826 r\longa r\breve r1 r2 r4 r8 r16
4829 There are no 32th and 64th rests specifically for the mensural or
4830 neo-mensural style. Instead, the rests from the default style will be
4831 taken. See @inputfileref{input/test,rests.ly} for a chart of all
4834 There are no rests in Gregorian Chant notation; instead, it uses
4839 In this manual: @ref{Rests} gives a general introduction into the use of rests.
4843 @subsection Ancient clefs
4849 LilyPond supports a variety of clefs, many of them ancient.
4851 The following table shows all ancient clefs that are supported via the
4852 @code{\clef} command. Some of the clefs use the same glyph, but
4853 differ only with respect to the line they are printed on. In such
4854 cases, a trailing number in the name is used to enumerate these clefs.
4855 Still, you can manually force a clef glyph to be typeset on an
4856 arbitrary line, as described in @ref{Clef}. The note printed to the
4857 right side of each clef in the example column denotes the @code{c'}
4858 with respect to that clef.
4860 @multitable @columnfractions .3 .3 .3 .1
4864 @b{Description} @tab
4865 @b{Supported Clefs} @tab
4869 @code{clefs-neo_mensural_c} @tab
4870 modern style mensural C clef @tab
4871 @code{neo_mensural_c1}, @code{neo_mensural_c2},
4872 @code{neo_mensural_c3}, @code{neo_mensural_c4} @tab
4873 @lilypond[relative,notime]
4874 \override Staff.TimeSignature #'transparent = ##t
4875 \clef "neo_mensural_c2" c
4879 @code{clefs-petrucci_c1}
4880 @code{clefs-petrucci_c2}
4881 @code{clefs-petrucci_c3}
4882 @code{clefs-petrucci_c4}
4883 @code{clefs-petrucci_c5}
4886 petrucci style mensural C clefs, for use on different stafflines
4887 (the examples shows the 2nd staffline C clef).
4897 @lilypond[relative,notime]
4898 \override Staff.TimeSignature #'transparent = ##t
4899 \clef "petrucci_c2" c
4903 @code{clefs-petrucci_f} @tab
4904 petrucci style mensural F clef @tab
4905 @code{petrucci_f} @tab
4906 @lilypond[relative,notime]
4907 \override Staff.TimeSignature #'transparent = ##t
4908 \clef "petrucci_f" c
4912 @code{clefs-petrucci_g} @tab
4913 petrucci style mensural G clef @tab
4914 @code{petrucci_g} @tab
4915 @lilypond[relative,notime]
4916 \override Staff.TimeSignature #'transparent = ##t
4917 \clef "petrucci_g" c
4921 @code{clefs-mensural_c} @tab
4922 historic style mensural C clef @tab
4923 @code{mensural_c1}, @code{mensural_c2}, @code{mensural_c3},
4924 @code{mensural_c4} @tab
4925 @lilypond[relative,notime]
4926 \override Staff.TimeSignature #'transparent = ##t
4927 \clef "mensural_c2" c
4931 @code{clefs-mensural_f} @tab
4932 historic style mensural F clef @tab
4933 @code{mensural_f} @tab
4934 @lilypond[relative,notime]
4935 \override Staff.TimeSignature #'transparent = ##t
4936 \clef "mensural_f" c
4940 @code{clefs-mensural_g} @tab
4941 historic style mensural G clef @tab
4942 @code{mensural_g} @tab
4943 @lilypond[relative,notime]
4944 \override Staff.TimeSignature #'transparent = ##t
4945 \clef "mensural_g" c
4949 @code{clefs-vaticana_do} @tab
4950 Editio Vaticana style do clef @tab
4951 @code{vaticana_do1}, @code{vaticana_do2}, @code{vaticana_do3} @tab
4952 @lilypond[relative,notime]
4953 \override Staff.StaffSymbol #'line-count = #4
4954 \override Staff.TimeSignature #'transparent = ##t
4955 \clef "vaticana_do2" c
4959 @code{clefs-vaticana_fa} @tab
4960 Editio Vaticana style fa clef @tab
4961 @code{vaticana_fa1}, @code{vaticana_fa2} @tab
4962 @lilypond[relative,notime]
4963 \override Staff.StaffSymbol #'line-count = #4
4964 \override Staff.TimeSignature #'transparent = ##t
4965 \clef "vaticana_fa2" c
4969 @code{clefs-medicaea_do} @tab
4970 Editio Medicaea style do clef @tab
4971 @code{medicaea_do1}, @code{medicaea_do2}, @code{medicaea_do3} @tab
4972 @lilypond[relative,notime]
4973 \override Staff.StaffSymbol #'line-count = #4
4974 \override Staff.TimeSignature #'transparent = ##t
4975 \clef "medicaea_do2" c
4979 @code{clefs-medicaea_fa} @tab
4980 Editio Medicaea style fa clef @tab
4981 @code{medicaea_fa1}, @code{medicaea_fa2} @tab
4982 @lilypond[relative,notime]
4983 \override Staff.StaffSymbol #'line-count = #4
4984 \override Staff.TimeSignature #'transparent = ##t
4985 \clef "medicaea_fa2" c
4989 @code{clefs-hufnagel_do} @tab
4990 historic style hufnagel do clef @tab
4991 @code{hufnagel_do1}, @code{hufnagel_do2}, @code{hufnagel_do3} @tab
4992 @lilypond[relative,notime]
4993 \override Staff.StaffSymbol #'line-count = #4
4994 \override Staff.TimeSignature #'transparent = ##t
4995 \clef "hufnagel_do2" c
4999 @code{clefs-hufnagel_fa} @tab
5000 historic style hufnagel fa clef @tab
5001 @code{hufnagel_fa1}, @code{hufnagel_fa2} @tab
5002 @lilypond[relative,notime]
5003 \override Staff.StaffSymbol #'line-count = #4
5004 \override Staff.TimeSignature #'transparent = ##t
5005 \clef "hufnagel_fa2" c
5009 @code{clefs-hufnagel_do_fa} @tab
5010 historic style hufnagel combined do/fa clef @tab
5011 @code{hufnagel_do_fa} @tab
5012 @lilypond[relative,notime]
5013 \override Staff.TimeSignature #'transparent = ##t
5014 \clef "hufnagel_do_fa" c
5019 @c --- This should go somewhere else: ---
5020 @c @item modern style percussion clef (glyph: @code{clefs-percussion})
5023 @c @code{percussion}
5025 @c @lilypond{\override Staff.TimeSignature #'transparent = ##t \clef "percussion" c'}
5027 @c @item modern style tab clef (glyph: @code{clefs-tab})
5032 @c @lilypond{\context Staff \outputproperty #(make-type-checker 'staff-symbol-interface) #'line-count = #6 \override Staff.TimeSignature #'transparent = ##t \clef "tab" c'}
5034 @emph{Modern style} means ``as is typeset in contemporary editions of
5035 transcribed mensural music''.
5037 @emph{Petrucci style} means ``inspired by printings published by the
5038 famous engraver Petrucci (1466-1539)''.
5040 @emph{Historic style} means ``as was typeset or written in historic
5041 editions (other than those of Petrucci)''.
5043 @emph{Editio XXX style} means ``as is/was printed in Editio XXX''.
5045 Petrucci used C clefs with differently balanced left-side vertical
5046 beams, depending on which staffline it is printed.
5050 In this manual: for the percussion clef, see @ref{Percussion staves}.
5051 For the @code{TAB} clef, see @ref{Tablatures}.
5053 Internals: for modern clefs, see @ref{Clef}.
5057 The mensural g clef is temporarily mapped to the Petrucci g clef,
5058 until a new mensural g clef will have been implemented.
5063 @subsection Ancient flags
5069 Use the @code{flag-style} property of grob @internalsref{Stem} to
5070 select ancient flags. Besides the @code{default} flag style,
5071 only @code{mensural} style is supported:
5073 @lilypond[fragment,raggedright,verbatim]
5074 \override Stem #'flag-style = #'mensural
5075 \override Stem #'thickness = #1.0
5076 \override NoteHead #'style = #'mensural
5078 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
5079 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
5082 Note that the innermost flare of each mensural flag always is
5083 vertically aligned with a staff line. If you do not like this
5084 behaviour, you can set the @code{adjust-if-on-staffline} property of
5085 grob @internalsref{Stem} to @code{##f}. Then, the vertical position
5086 of the end of each flare is different between notes on staff lines and
5087 notes between staff lines:
5089 @lilypond[fragment,raggedright]
5090 \override Stem #'flag-style = #'mensural
5091 \override Stem #'thickness = #1.0
5092 \override Stem #'adjust-if-on-staffline = ##f
5093 \override NoteHead #'style = #'mensural
5095 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
5096 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
5099 There is no particular flag style for neo-mensural notation. Hence,
5100 when typesetting e.g. the incipit of a transcibed piece of mensural
5101 music, the default flag style should be used. There are no flags in
5102 Gregorian Chant notation.
5105 @node Ancient time signatures
5106 @subsection Ancient time signatures
5108 @cindex time signatures
5112 There is limited support for mensural time signatures. The
5113 glyphs are hard-wired to particular time fractions. In other words,
5114 to get a particular mensural signature glyph with the @code{\time n/m}
5115 command, @code{n} and @code{m} have to be chosen according to the
5121 \set Score.timing = ##f
5122 \set Score.barAlways = ##t
5123 s_\markup { "$\\backslash$time 4/4" }
5124 ^\markup { " " \musicglyph #"timesig-neo_mensural4/4" }
5126 s_\markup { "$\\backslash$time 2/2" }
5127 ^\markup { " " \musicglyph #"timesig-neo_mensural2/2" }
5129 s_\markup { "$\\backslash$time 6/4" }
5130 ^\markup { " " \musicglyph #"timesig-neo_mensural6/4" }
5132 s_\markup { "$\\backslash$time 6/8" }
5133 ^\markup { " " \musicglyph #"timesig-neo_mensural6/8" }
5135 s_\markup { "$\\backslash$time 3/2" }
5136 ^\markup { " " \musicglyph #"timesig-neo_mensural3/2" }
5138 s_\markup { "$\\backslash$time 3/4" }
5139 ^\markup { " " \musicglyph #"timesig-neo_mensural3/4" }
5141 s_\markup { "$\\backslash$time 9/4" }
5142 ^\markup { " " \musicglyph #"timesig-neo_mensural9/4" }
5144 s_\markup { "$\\backslash$time 9/8" }
5145 ^\markup { " " \musicglyph #"timesig-neo_mensural9/8" }
5147 s_\markup { "$\\backslash$time 4/8" }
5148 ^\markup { " " \musicglyph #"timesig-neo_mensural4/8" }
5150 s_\markup { "$\\backslash$time 2/4" }
5151 ^\markup { " " \musicglyph #"timesig-neo_mensural2/4" }
5159 \remove Staff_symbol_engraver
5160 \remove Clef_engraver
5161 \remove Time_signature_engraver
5167 Use the @code{style} property of grob @internalsref{TimeSignature} to
5168 select ancient time signatures. Supported styles are
5169 @code{neo_mensural} and @code{mensural}. The above table uses the
5170 @code{neo_mensural} style. This style is appropriate e.g. for the
5171 incipit of transcriptions of mensural pieces. The @code{mensural}
5172 style mimicks the look of historical printings of the 16th century.
5174 @inputfileref{input/test,time.ly} gives an overview over all available
5175 ancient and modern styles.
5179 Internals: @ref{Time signature} gives a general introduction into the use of time
5184 Mensural signature glyphs are mapped to time fractions in a
5185 hard-wired way. This mapping is sensible, but still arbitrary: given
5186 a mensural time signature, the time fraction represents a modern meter
5187 that usually will be a good choice when transcribing a mensural piece
5188 of music. For a particular piece of mensural music, however, the
5189 mapping may be unsatisfactory. In particular, the mapping assumes a
5190 fixed transcription of durations (e.g. brevis = half note in 2/2,
5191 i.e. 4:1). Some glyphs (such as the alternate glyph for 6/8 meter)
5192 are not at all accessible through the @code{\time} command.
5194 Mensural time signatures are supported typographically, but not yet
5195 musically. The internal representation of durations is
5196 based on a purely binary system; a ternary division such as 1 brevis =
5197 3 semibrevis (tempus perfectum) or 1 semibrevis = 3 minima (cum
5198 prolatione maiori) is not correctly handled: event times in ternary
5199 modes will be badly computed, resulting e.g. in horizontally
5200 misaligned note heads, and bar checks are likely to erroneously fail.
5202 The syntax and semantics of the @code{\time} command for mensural
5203 music is subject to change.
5206 @subsection Custodes
5211 A @emph{custos} (plural: @emph{custodes}; latin word for `guard') is a
5212 symbol that appears at the end of a staff. It anticipates the pitch
5213 of the first note(s) of the following line and thus helps the player
5214 or singer to manage line breaks during performance, thus enhancing
5215 readability of a score.
5217 Custodes were frequently used in music notation until the 17th
5218 century. Nowadays, they have survived only in a few particular forms
5219 of musical notation such as contemporary editions of Gregorian chant
5220 like the @emph{editio vaticana}. There are different custos glyphs
5221 used in different flavours of notational style.
5225 For typesetting custodes, just put a @internalsref{Custos_engraver} into the
5226 @internalsref{Staff} context when declaring the @code{\paper} block,
5227 as shown in the following example:
5233 \consists Custos_engraver
5234 Custos \override #'style = #'mensural
5239 The result looks like this:
5245 \override Staff.Custos #'style = #'mensural
5252 \consists Custos_engraver
5259 The custos glyph is selected by the @code{style} property. The styles
5260 supported are @code{vaticana}, @code{medicaea}, @code{hufnagel} and
5261 @code{mensural}. They are demonstrated in the following fragment:
5271 { " " \musicglyph #"custodes-vaticana-u0" }
5275 { " " \musicglyph #"custodes-medicaea-u0" }
5279 { " " \musicglyph #"custodes-hufnagel-u0" }
5283 { " " \musicglyph #"custodes-mensural-u0" }
5292 \remove "Bar_number_engraver"
5296 \remove "Clef_engraver"
5297 \remove "Key_engraver"
5298 \remove "Time_signature_engraver"
5299 \remove "Staff_symbol_engraver"
5300 minimumVerticalExtent = ##f
5306 If the boolean property @code{adjust-if-on-staffline} is set to
5307 @code{#t} (which it is by default), lily typesets slightly different
5308 variants of the custos glyph, depending on whether the custos, is
5309 typeset on or between stafflines. The glyph will
5310 optically fit well into the staff, with the appendage on the right of
5311 the custos always ending at the same vertical position between two
5312 stafflines regardless of the pitch. If you set
5313 @code{adjust-if-on-staffline} to @code{#f}, then
5314 a compromise between both forms is used.
5316 Just like stems can be attached to noteheads in two directions
5317 @emph{up} and @emph{down}, each custos glyph is available with its
5318 appendage pointing either up or down. If the pitch of a custos is
5319 above a selectable position, the appendage will point downwards; if
5320 the pitch is below this position, the appendage will point upwards.
5321 Use property @code{neutral-position} to select this position. By
5322 default, it is set to @code{0}, such that the neutral position is the
5323 center of the staff. Use property @code{neutral-direction} to control
5324 what happens if a custos is typeset on the neutral position itself.
5325 By default, this property is set to @code{-1}, such that the appendage
5326 will point downwards. If set to @code{1}, the appendage will point
5327 upwards. Other values such as @code{0} are reserved for future
5328 extensions and should not be used.
5332 Internals: @internalsref{Custos}.
5334 Examples: @inputfileref{input/regression,custos.ly}.
5338 @subsection Divisiones
5344 A @emph{divisio} (plural: @emph{divisiones}; latin word for
5345 `division') is a staff context symbol that is used to structure
5346 Gregorian music into phrases and sections. The musical meaning of
5347 @emph{divisio minima}, @emph{divisio maior} and @emph{divisio maxima}
5348 can be characterized as short, medium and long pause, somewhat like
5349 @ref{Breath marks}. The @emph{finalis} sign not only marks the end of
5350 a chant, but is also frequently used within a single
5351 antiphonal/responsorial chant to mark the end of each section.
5355 To use divisiones, include the file @code{gregorian-init.ly}. It
5356 contains definitions that you can apply by just inserting
5357 @code{\divisioMinima}, @code{\divisioMaior}, @code{\divisioMaxima},
5358 and @code{\finalis} at proper places in the input. Some editions use
5359 @emph{virgula} or @emph{caesura} instead of divisio minima.
5360 Therefore, @code{gregorian-init.ly} also defines @code{\virgula} and
5363 @lilypondfile[]{divisiones.ly}
5367 @cindex @code{\virgula}
5369 @cindex @code{\caesura}
5371 @cindex @code{\divisioMinima}
5372 @code{\divisioMinima},
5373 @cindex @code{\divisioMaior}
5374 @code{\divisioMaior},
5375 @cindex @code{\divisioMaxima}
5376 @code{\divisioMaxima},
5377 @cindex @code{\finalis}
5382 In this manual: @ref{Breath marks}.
5384 Internals: @internalsref{BreathingSign}, @internalsref{BreathingSignEvent}.
5386 Examples: @inputfileref{input/test,divisiones.ly}.
5389 @subsection Ligatures
5393 @c TODO: Should double check if I recalled things correctly when I wrote
5394 @c down the following paragraph by heart.
5396 In musical terminology, a ligature is a coherent graphical symbol that
5397 represents at least two distinct notes. Ligatures originally appeared
5398 in the manuscripts of Gregorian chant notation roughly since the 9th
5399 century as an allusion to the accent symbols of greek lyric poetry to
5400 denote ascending or descending sequences of notes. Both, the shape
5401 and the exact meaning of ligatures changed tremendously during the
5402 following centuries: In early notation, ligatures were used for
5403 monophonic tunes (Gregorian chant) and very soon denoted also the way
5404 of performance in the sense of articulation. With upcoming
5405 multiphony, the need for a metric system arised, since multiple voices
5406 of a piece have to be synchronized some way. New notation systems
5407 were invented that used the manifold shapes of ligatures to now denote
5408 rhythmical patterns (e.g. black mensural notation, mannered notation,
5409 ars nova). With the invention of the metric system of the white
5410 mensural notation, the need for ligatures to denote such patterns
5411 disappeared. Nevertheless, ligatures were still in use in the
5412 mensural system for a couple of decades until they finally disappeared
5413 during the late 16th / early 17th century. Still, ligatures have
5414 survived in contemporary editions of Gregorian chant such as the
5415 Editio Vaticana from 1905/08.
5419 Syntactically, ligatures are simply enclosed by @code{\[} and
5420 @code{\]}. Some ligature styles (such as Editio Vaticana) may need
5421 additional input syntax specific for this particular type of ligature.
5422 By default, the @internalsref{LigatureBracket} engraver just puts a
5423 square bracket above the ligature:
5425 @lilypond[raggedright,verbatim]
5427 \notes \transpose c c' {
5435 To select a specific style of ligatures, a proper ligature engraver
5436 has to be added to the @internalsref{Voice} context, as explained in
5437 the following subsections. Only white mensural ligatures
5438 are supported with certain limitations. Support for Editio Vaticana
5439 will be added in the future.
5442 * White mensural ligatures::
5443 * Gregorian square neumes ligatures::
5446 @node White mensural ligatures
5447 @subsubsection White mensural ligatures
5449 @cindex Mensural ligatures
5450 @cindex White mensural ligatures
5452 There is limited support for white mensural ligatures. The
5453 implementation is still experimental; it may output strange
5454 warnings or even crash in some cases or produce weird results on more
5459 To engrave white mensural ligatures, in the paper block the
5460 @internalsref{Mensural_ligature_engraver} has to be put into the
5461 @internalsref{Voice} context, and remove the
5462 @internalsref{Ligature_bracket_engraver}:
5468 \remove Ligature_bracket_engraver
5469 \consists Mensural_ligature_engraver
5474 There is no additional input language to describe the shape of a
5475 white mensural ligature. The shape is rather determined solely from
5476 the pitch and duration of the enclosed notes. While this approach may
5477 take a new user a while to get accustomed, it has the great advantage
5478 that the full musical information of the ligature is known internally.
5479 This is not only required for correct MIDI output, but also allows for
5480 automatic transcription of the ligatures.
5485 \set Score.timing = ##f
5486 \set Score.defaultBarType = "empty"
5487 \override NoteHead #'style = #'neo_mensural
5488 \override Staff.TimeSignature #'style = #'neo_mensural
5490 \[ g\longa c\breve a\breve f\breve d'\longa \]
5492 \[ e1 f1 a\breve g\longa \]
5494 @lilypond[raggedright]
5496 \notes \transpose c c' {
5497 \set Score.timing = ##f
5498 \set Score.defaultBarType = "empty"
5499 \override NoteHead #'style = #'neo_mensural
5500 \override Staff.TimeSignature #'style = #'neo_mensural
5502 \[ g\longa c\breve a\breve f\breve d'\longa \]
5504 \[ e1 f1 a\breve g\longa \]
5509 \remove Ligature_bracket_engraver
5510 \consists Mensural_ligature_engraver
5516 Without replacing @internalsref{Ligature_bracket_engraver} with
5517 @internalsref{Mensural_ligature_engraver}, the same music transcribes
5520 @lilypond[raggedright]
5522 \notes \transpose c c' {
5523 \set Score.timing = ##f
5524 \set Score.defaultBarType = "empty"
5525 \override NoteHead #'style = #'neo_mensural
5526 \override Staff.TimeSignature #'style = #'neo_mensural
5528 \[ g\longa c\breve a\breve f\breve d'\longa \]
5530 \[ e1 f1 a\breve g\longa \]
5536 @node Gregorian square neumes ligatures
5537 @subsubsection Gregorian square neumes ligatures
5539 @cindex Square neumes ligatures
5540 @cindex Gregorian square neumes ligatures
5542 Gregorian square neumes notation (following the style of the Editio
5543 Vaticana) is under heavy development, but not yet really usable for
5544 production purposes. Core ligatures can already be typeset, but
5545 essential issues for serious typesetting are still under development,
5546 such as (among others) horizontal alignment of multiple ligatures,
5547 lyrics alignment and proper accidentals handling. Still, this section
5548 gives a sneak preview of what Gregorian chant may look like once it
5551 The following table contains the extended neumes table of the 2nd
5552 volume of the Antiphonale Romanum (@emph{Liber Hymnarius}), published
5553 1983 by the monks of Solesmes.
5555 @multitable @columnfractions .4 .2 .2 .2
5558 @b{Neuma aut@*Neumarum Elementa} @tab
5559 @b{Figurae@*Rectae} @tab
5560 @b{Figurae@*Liquescentes Auctae} @tab
5561 @b{Figurae@*Liquescentes Deminutae}
5563 @c TODO: \paper block is identical in all of the below examples.
5564 @c Therefore, it should somehow be included rather than duplicated all
5567 @c why not make identifiers in ly/engraver-init.ly? --hwn
5569 @c Because it's just used to typeset plain notes without
5570 @c a staff for demonstration purposes rather than something
5571 @c special of Gregorian chant notation. --jr
5576 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.5\cm]
5577 \include "gregorian-init.ly"
5579 \notes \transpose c c' {
5582 \noBreak s^\markup {"a"} \noBreak
5584 % Punctum Inclinatum
5586 \noBreak s^\markup {"b"}
5592 \remove "Bar_number_engraver"
5596 \remove "Clef_engraver"
5597 \remove "Key_engraver"
5598 \override StaffSymbol #'transparent = ##t
5599 \remove "Time_signature_engraver"
5600 \remove "Bar_engraver"
5601 minimumVerticalExtent = ##f
5605 \remove Ligature_bracket_engraver
5606 \consists Vaticana_ligature_engraver
5607 \override NoteHead #'style = #'vaticana_punctum
5608 \override Stem #'transparent = ##t
5614 @lilypond[noindent,staffsize=26,nofragment,linewidth=2.5\cm]
5615 \include "gregorian-init.ly"
5617 \notes \transpose c c' {
5618 % Punctum Auctum Ascendens
5619 \[ \auctum \ascendens b \]
5620 \noBreak s^\markup {"c"} \noBreak
5622 % Punctum Auctum Descendens
5623 \[ \auctum \descendens b \]
5624 \noBreak s^\markup {"d"} \noBreak
5626 % Punctum Inclinatum Auctum
5627 \[ \inclinatum \auctum b \]
5628 \noBreak s^\markup {"e"}
5634 \remove "Bar_number_engraver"
5638 \remove "Clef_engraver"
5639 \remove "Key_engraver"
5640 \override StaffSymbol #'transparent = ##t
5641 \remove "Time_signature_engraver"
5642 \remove "Bar_engraver"
5643 minimumVerticalExtent = ##f
5647 \remove Ligature_bracket_engraver
5648 \consists Vaticana_ligature_engraver
5649 \override NoteHead #'style = #'vaticana_punctum
5650 \override Stem #'transparent = ##t
5656 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5657 \include "gregorian-init.ly"
5659 \notes \transpose c c' {
5660 % Punctum Inclinatum Parvum
5661 \[ \inclinatum \deminutum b \]
5662 \noBreak s^\markup {"f"}
5668 \remove "Bar_number_engraver"
5672 \remove "Clef_engraver"
5673 \remove "Key_engraver"
5674 \override StaffSymbol #'transparent = ##t
5675 \remove "Time_signature_engraver"
5676 \remove "Bar_engraver"
5677 minimumVerticalExtent = ##f
5681 \remove Ligature_bracket_engraver
5682 \consists Vaticana_ligature_engraver
5683 \override NoteHead #'style = #'vaticana_punctum
5684 \override Stem #'transparent = ##t
5693 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5694 \include "gregorian-init.ly"
5696 \notes \transpose c c' {
5699 \noBreak s^\markup {"g"}
5705 \remove "Bar_number_engraver"
5709 \remove "Clef_engraver"
5710 \remove "Key_engraver"
5711 \override StaffSymbol #'transparent = ##t
5712 \remove "Time_signature_engraver"
5713 \remove "Bar_engraver"
5714 minimumVerticalExtent = ##f
5718 \remove Ligature_bracket_engraver
5719 \consists Vaticana_ligature_engraver
5720 \override NoteHead #'style = #'vaticana_punctum
5721 \override Stem #'transparent = ##t
5730 @code{3. Apostropha vel Stropha}
5732 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5733 \include "gregorian-init.ly"
5735 \notes \transpose c c' {
5738 \noBreak s^\markup {"h"}
5744 \remove "Bar_number_engraver"
5748 \remove "Clef_engraver"
5749 \remove "Key_engraver"
5750 \override StaffSymbol #'transparent = ##t
5751 \remove "Time_signature_engraver"
5752 \remove "Bar_engraver"
5753 minimumVerticalExtent = ##f
5757 \remove Ligature_bracket_engraver
5758 \consists Vaticana_ligature_engraver
5759 \override NoteHead #'style = #'vaticana_punctum
5760 \override Stem #'transparent = ##t
5766 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5767 \include "gregorian-init.ly"
5769 \notes \transpose c c' {
5771 \[ \stropha \auctum b \]
5772 \noBreak s^\markup {"i"}
5778 \remove "Bar_number_engraver"
5782 \remove "Clef_engraver"
5783 \remove "Key_engraver"
5784 \override StaffSymbol #'transparent = ##t
5785 \remove "Time_signature_engraver"
5786 \remove "Bar_engraver"
5787 minimumVerticalExtent = ##f
5791 \remove Ligature_bracket_engraver
5792 \consists Vaticana_ligature_engraver
5793 \override NoteHead #'style = #'vaticana_punctum
5794 \override Stem #'transparent = ##t
5804 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5805 \include "gregorian-init.ly"
5807 \notes \transpose c c' {
5810 \noBreak s^\markup {"j"}
5816 \remove "Bar_number_engraver"
5820 \remove "Clef_engraver"
5821 \remove "Key_engraver"
5822 \override StaffSymbol #'transparent = ##t
5823 \remove "Time_signature_engraver"
5824 \remove "Bar_engraver"
5825 minimumVerticalExtent = ##f
5829 \remove Ligature_bracket_engraver
5830 \consists Vaticana_ligature_engraver
5831 \override NoteHead #'style = #'vaticana_punctum
5832 \override Stem #'transparent = ##t
5841 @code{5. Clivis vel Flexa}
5843 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5844 \include "gregorian-init.ly"
5846 \notes \transpose c c' {
5855 \remove "Bar_number_engraver"
5859 \remove "Clef_engraver"
5860 \remove "Key_engraver"
5861 \override StaffSymbol #'transparent = ##t
5862 \remove "Time_signature_engraver"
5863 \remove "Bar_engraver"
5864 minimumVerticalExtent = ##f
5868 \remove Ligature_bracket_engraver
5869 \consists Vaticana_ligature_engraver
5870 \override NoteHead #'style = #'vaticana_punctum
5871 \override Stem #'transparent = ##t
5877 @lilypond[noindent,staffsize=26,nofragment,linewidth=2.0\cm]
5878 \include "gregorian-init.ly"
5880 \notes \transpose c c' {
5881 % Clivis Aucta Descendens
5882 \[ b \flexa \auctum \descendens g \]
5883 \noBreak s^\markup {"l"} \noBreak
5885 % Clivis Aucta Ascendens
5886 \[ b \flexa \auctum \ascendens g \]
5887 \noBreak s^\markup {"m"}
5893 \remove "Bar_number_engraver"
5897 \remove "Clef_engraver"
5898 \remove "Key_engraver"
5899 \override StaffSymbol #'transparent = ##t
5900 \remove "Time_signature_engraver"
5901 \remove "Bar_engraver"
5902 minimumVerticalExtent = ##f
5906 \remove Ligature_bracket_engraver
5907 \consists Vaticana_ligature_engraver
5908 \override NoteHead #'style = #'vaticana_punctum
5909 \override Stem #'transparent = ##t
5915 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5916 \include "gregorian-init.ly"
5918 \notes \transpose c c' {
5920 \[ b \flexa \deminutum g \]
5927 \remove "Bar_number_engraver"
5931 \remove "Clef_engraver"
5932 \remove "Key_engraver"
5933 \override StaffSymbol #'transparent = ##t
5934 \remove "Time_signature_engraver"
5935 \remove "Bar_engraver"
5936 minimumVerticalExtent = ##f
5940 \remove Ligature_bracket_engraver
5941 \consists Vaticana_ligature_engraver
5942 \override NoteHead #'style = #'vaticana_punctum
5943 \override Stem #'transparent = ##t
5950 @code{6. Podatus vel Pes}
5952 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
5953 \include "gregorian-init.ly"
5955 \notes \transpose c c' {
5964 \remove "Bar_number_engraver"
5968 \remove "Clef_engraver"
5969 \remove "Key_engraver"
5970 \override StaffSymbol #'transparent = ##t
5971 \remove "Time_signature_engraver"
5972 \remove "Bar_engraver"
5973 minimumVerticalExtent = ##f
5977 \remove Ligature_bracket_engraver
5978 \consists Vaticana_ligature_engraver
5979 \override NoteHead #'style = #'vaticana_punctum
5980 \override Stem #'transparent = ##t
5986 @lilypond[noindent,staffsize=26,nofragment,linewidth=2.0\cm]
5987 \include "gregorian-init.ly"
5989 \notes \transpose c c' {
5990 % Pes Auctus Descendens
5991 \[ g \pes \auctum \descendens b \]
5992 \noBreak s^\markup {"p"} \noBreak
5994 % Pes Auctus Ascendens
5995 \[ g \pes \auctum \ascendens b \]
5996 \noBreak s^\markup {"q"}
6002 \remove "Bar_number_engraver"
6006 \remove "Clef_engraver"
6007 \remove "Key_engraver"
6008 \override StaffSymbol #'transparent = ##t
6009 \remove "Time_signature_engraver"
6010 \remove "Bar_engraver"
6011 minimumVerticalExtent = ##f
6015 \remove Ligature_bracket_engraver
6016 \consists Vaticana_ligature_engraver
6017 \override NoteHead #'style = #'vaticana_punctum
6018 \override Stem #'transparent = ##t
6024 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6025 \include "gregorian-init.ly"
6027 \notes \transpose c c' {
6029 \[ g \pes \deminutum b \]
6036 \remove "Bar_number_engraver"
6040 \remove "Clef_engraver"
6041 \remove "Key_engraver"
6042 \override StaffSymbol #'transparent = ##t
6043 \remove "Time_signature_engraver"
6044 \remove "Bar_engraver"
6045 minimumVerticalExtent = ##f
6049 \remove Ligature_bracket_engraver
6050 \consists Vaticana_ligature_engraver
6051 \override NoteHead #'style = #'vaticana_punctum
6052 \override Stem #'transparent = ##t
6059 @code{7. Pes Quassus}
6061 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6062 \include "gregorian-init.ly"
6064 \notes \transpose c c' {
6066 \[ \oriscus g \pes \virga b \]
6073 \remove "Bar_number_engraver"
6077 \remove "Clef_engraver"
6078 \remove "Key_engraver"
6079 \override StaffSymbol #'transparent = ##t
6080 \remove "Time_signature_engraver"
6081 \remove "Bar_engraver"
6082 minimumVerticalExtent = ##f
6086 \remove Ligature_bracket_engraver
6087 \consists Vaticana_ligature_engraver
6088 \override NoteHead #'style = #'vaticana_punctum
6089 \override Stem #'transparent = ##t
6095 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6096 \include "gregorian-init.ly"
6098 \notes \transpose c c' {
6099 % Pes Quassus Auctus Descendens
6100 \[ \oriscus g \pes \auctum \descendens b \]
6107 \remove "Bar_number_engraver"
6111 \remove "Clef_engraver"
6112 \remove "Key_engraver"
6113 \override StaffSymbol #'transparent = ##t
6114 \remove "Time_signature_engraver"
6115 \remove "Bar_engraver"
6116 minimumVerticalExtent = ##f
6120 \remove Ligature_bracket_engraver
6121 \consists Vaticana_ligature_engraver
6122 \override NoteHead #'style = #'vaticana_punctum
6123 \override Stem #'transparent = ##t
6131 @code{8. Quilisma Pes}
6133 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6134 \include "gregorian-init.ly"
6136 \notes \transpose c c' {
6138 \[ \quilisma g \pes b \]
6145 \remove "Bar_number_engraver"
6149 \remove "Clef_engraver"
6150 \remove "Key_engraver"
6151 \override StaffSymbol #'transparent = ##t
6152 \remove "Time_signature_engraver"
6153 \remove "Bar_engraver"
6154 minimumVerticalExtent = ##f
6158 \remove Ligature_bracket_engraver
6159 \consists Vaticana_ligature_engraver
6160 \override NoteHead #'style = #'vaticana_punctum
6161 \override Stem #'transparent = ##t
6167 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6168 \include "gregorian-init.ly"
6170 \notes \transpose c c' {
6171 % Quilisma Pes Auctus Descendens
6172 \[ \quilisma g \pes \auctum \descendens b \]
6179 \remove "Bar_number_engraver"
6183 \remove "Clef_engraver"
6184 \remove "Key_engraver"
6185 \override StaffSymbol #'transparent = ##t
6186 \remove "Time_signature_engraver"
6187 \remove "Bar_engraver"
6188 minimumVerticalExtent = ##f
6192 \remove Ligature_bracket_engraver
6193 \consists Vaticana_ligature_engraver
6194 \override NoteHead #'style = #'vaticana_punctum
6195 \override Stem #'transparent = ##t
6203 @code{9. Podatus Initio Debilis}
6205 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6206 \include "gregorian-init.ly"
6208 \notes \transpose c c' {
6209 % Pes Initio Debilis
6210 \[ \deminutum g \pes b \]
6217 \remove "Bar_number_engraver"
6221 \remove "Clef_engraver"
6222 \remove "Key_engraver"
6223 \override StaffSymbol #'transparent = ##t
6224 \remove "Time_signature_engraver"
6225 \remove "Bar_engraver"
6226 minimumVerticalExtent = ##f
6230 \remove Ligature_bracket_engraver
6231 \consists Vaticana_ligature_engraver
6232 \override NoteHead #'style = #'vaticana_punctum
6233 \override Stem #'transparent = ##t
6239 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6240 \include "gregorian-init.ly"
6242 \notes \transpose c c' {
6243 % Pes Auctus Descendens Initio Debilis
6244 \[ \deminutum g \pes \auctum \descendens b \]
6251 \remove "Bar_number_engraver"
6255 \remove "Clef_engraver"
6256 \remove "Key_engraver"
6257 \override StaffSymbol #'transparent = ##t
6258 \remove "Time_signature_engraver"
6259 \remove "Bar_engraver"
6260 minimumVerticalExtent = ##f
6264 \remove Ligature_bracket_engraver
6265 \consists Vaticana_ligature_engraver
6266 \override NoteHead #'style = #'vaticana_punctum
6267 \override Stem #'transparent = ##t
6277 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6278 \include "gregorian-init.ly"
6280 \notes \transpose c c' {
6282 \[ a \pes b \flexa g \]
6289 \remove "Bar_number_engraver"
6293 \remove "Clef_engraver"
6294 \remove "Key_engraver"
6295 \override StaffSymbol #'transparent = ##t
6296 \remove "Time_signature_engraver"
6297 \remove "Bar_engraver"
6298 minimumVerticalExtent = ##f
6302 \remove Ligature_bracket_engraver
6303 \consists Vaticana_ligature_engraver
6304 \override NoteHead #'style = #'vaticana_punctum
6305 \override Stem #'transparent = ##t
6311 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6312 \include "gregorian-init.ly"
6314 \notes \transpose c c' {
6315 % Torculus Auctus Descendens
6316 \[ a \pes b \flexa \auctum \descendens g \]
6323 \remove "Bar_number_engraver"
6327 \remove "Clef_engraver"
6328 \remove "Key_engraver"
6329 \override StaffSymbol #'transparent = ##t
6330 \remove "Time_signature_engraver"
6331 \remove "Bar_engraver"
6332 minimumVerticalExtent = ##f
6336 \remove Ligature_bracket_engraver
6337 \consists Vaticana_ligature_engraver
6338 \override NoteHead #'style = #'vaticana_punctum
6339 \override Stem #'transparent = ##t
6345 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6346 \include "gregorian-init.ly"
6348 \notes \transpose c c' {
6349 % Torculus Deminutus
6350 \[ a \pes b \flexa \deminutum g \]
6357 \remove "Bar_number_engraver"
6361 \remove "Clef_engraver"
6362 \remove "Key_engraver"
6363 \override StaffSymbol #'transparent = ##t
6364 \remove "Time_signature_engraver"
6365 \remove "Bar_engraver"
6366 minimumVerticalExtent = ##f
6370 \remove Ligature_bracket_engraver
6371 \consists Vaticana_ligature_engraver
6372 \override NoteHead #'style = #'vaticana_punctum
6373 \override Stem #'transparent = ##t
6380 @code{11. Torculus Initio Debilis}
6382 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6383 \include "gregorian-init.ly"
6385 \notes \transpose c c' {
6386 % Torculus Initio Debilis
6387 \[ \deminutum a \pes b \flexa g \]
6394 \remove "Bar_number_engraver"
6398 \remove "Clef_engraver"
6399 \remove "Key_engraver"
6400 \override StaffSymbol #'transparent = ##t
6401 \remove "Time_signature_engraver"
6402 \remove "Bar_engraver"
6403 minimumVerticalExtent = ##f
6407 \remove Ligature_bracket_engraver
6408 \consists Vaticana_ligature_engraver
6409 \override NoteHead #'style = #'vaticana_punctum
6410 \override Stem #'transparent = ##t
6416 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6417 \include "gregorian-init.ly"
6419 \notes \transpose c c' {
6420 % Torculus Auctus Descendens Initio Debilis
6421 \[ \deminutum a \pes b \flexa \auctum \descendens g \]
6428 \remove "Bar_number_engraver"
6432 \remove "Clef_engraver"
6433 \remove "Key_engraver"
6434 \override StaffSymbol #'transparent = ##t
6435 \remove "Time_signature_engraver"
6436 \remove "Bar_engraver"
6437 minimumVerticalExtent = ##f
6441 \remove Ligature_bracket_engraver
6442 \consists Vaticana_ligature_engraver
6443 \override NoteHead #'style = #'vaticana_punctum
6444 \override Stem #'transparent = ##t
6450 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6451 \include "gregorian-init.ly"
6453 \notes \transpose c c' {
6454 % Torculus Deminutus Initio Debilis
6455 \[ \deminutum a \pes b \flexa \deminutum g \]
6462 \remove "Bar_number_engraver"
6466 \remove "Clef_engraver"
6467 \remove "Key_engraver"
6468 \override StaffSymbol #'transparent = ##t
6469 \remove "Time_signature_engraver"
6470 \remove "Bar_engraver"
6471 minimumVerticalExtent = ##f
6475 \remove Ligature_bracket_engraver
6476 \consists Vaticana_ligature_engraver
6477 \override NoteHead #'style = #'vaticana_punctum
6478 \override Stem #'transparent = ##t
6485 @code{12. Porrectus}
6487 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6488 \include "gregorian-init.ly"
6490 \notes \transpose c c' {
6492 \[ a \flexa g \pes b \]
6499 \remove "Bar_number_engraver"
6503 \remove "Clef_engraver"
6504 \remove "Key_engraver"
6505 \override StaffSymbol #'transparent = ##t
6506 \remove "Time_signature_engraver"
6507 \remove "Bar_engraver"
6508 minimumVerticalExtent = ##f
6512 \remove Ligature_bracket_engraver
6513 \consists Vaticana_ligature_engraver
6514 \override NoteHead #'style = #'vaticana_punctum
6515 \override Stem #'transparent = ##t
6521 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6522 \include "gregorian-init.ly"
6524 \notes \transpose c c' {
6525 % Porrectus Auctus Descendens
6526 \[ a \flexa g \pes \auctum \descendens b \]
6533 \remove "Bar_number_engraver"
6537 \remove "Clef_engraver"
6538 \remove "Key_engraver"
6539 \override StaffSymbol #'transparent = ##t
6540 \remove "Time_signature_engraver"
6541 \remove "Bar_engraver"
6542 minimumVerticalExtent = ##f
6546 \remove Ligature_bracket_engraver
6547 \consists Vaticana_ligature_engraver
6548 \override NoteHead #'style = #'vaticana_punctum
6549 \override Stem #'transparent = ##t
6555 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6556 \include "gregorian-init.ly"
6558 \notes \transpose c c' {
6559 % Porrectus Deminutus
6560 \[ a \flexa g \pes \deminutum b \]
6567 \remove "Bar_number_engraver"
6571 \remove "Clef_engraver"
6572 \remove "Key_engraver"
6573 \override StaffSymbol #'transparent = ##t
6574 \remove "Time_signature_engraver"
6575 \remove "Bar_engraver"
6576 minimumVerticalExtent = ##f
6580 \remove Ligature_bracket_engraver
6581 \consists Vaticana_ligature_engraver
6582 \override NoteHead #'style = #'vaticana_punctum
6583 \override Stem #'transparent = ##t
6592 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6593 \include "gregorian-init.ly"
6595 \notes \transpose c c' {
6597 \[ \virga b \inclinatum a \inclinatum g \]
6604 \remove "Bar_number_engraver"
6608 \remove "Clef_engraver"
6609 \remove "Key_engraver"
6610 \override StaffSymbol #'transparent = ##t
6611 \remove "Time_signature_engraver"
6612 \remove "Bar_engraver"
6613 minimumVerticalExtent = ##f
6617 \remove Ligature_bracket_engraver
6618 \consists Vaticana_ligature_engraver
6619 \override NoteHead #'style = #'vaticana_punctum
6620 \override Stem #'transparent = ##t
6626 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6627 \include "gregorian-init.ly"
6629 \notes \transpose c c' {
6631 \[ \virga b \inclinatum a \inclinatum \auctum g \]
6638 \remove "Bar_number_engraver"
6642 \remove "Clef_engraver"
6643 \remove "Key_engraver"
6644 \override StaffSymbol #'transparent = ##t
6645 \remove "Time_signature_engraver"
6646 \remove "Bar_engraver"
6647 minimumVerticalExtent = ##f
6651 \remove Ligature_bracket_engraver
6652 \consists Vaticana_ligature_engraver
6653 \override NoteHead #'style = #'vaticana_punctum
6654 \override Stem #'transparent = ##t
6660 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6661 \include "gregorian-init.ly"
6663 \notes \transpose c c' {
6664 % Climacus Deminutus
6665 \[ \virga b \inclinatum a \inclinatum \deminutum g \]
6672 \remove "Bar_number_engraver"
6676 \remove "Clef_engraver"
6677 \remove "Key_engraver"
6678 \override StaffSymbol #'transparent = ##t
6679 \remove "Time_signature_engraver"
6680 \remove "Bar_engraver"
6681 minimumVerticalExtent = ##f
6685 \remove Ligature_bracket_engraver
6686 \consists Vaticana_ligature_engraver
6687 \override NoteHead #'style = #'vaticana_punctum
6688 \override Stem #'transparent = ##t
6695 @code{14. Scandicus}
6697 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6698 \include "gregorian-init.ly"
6700 \notes \transpose c c' {
6702 \[ g \pes a \virga b \]
6709 \remove "Bar_number_engraver"
6713 \remove "Clef_engraver"
6714 \remove "Key_engraver"
6715 \override StaffSymbol #'transparent = ##t
6716 \remove "Time_signature_engraver"
6717 \remove "Bar_engraver"
6718 minimumVerticalExtent = ##f
6722 \remove Ligature_bracket_engraver
6723 \consists Vaticana_ligature_engraver
6724 \override NoteHead #'style = #'vaticana_punctum
6725 \override Stem #'transparent = ##t
6731 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6732 \include "gregorian-init.ly"
6734 \notes \transpose c c' {
6735 % Scandicus Auctus Descendens
6736 \[ g \pes a \pes \auctum \descendens b \]
6743 \remove "Bar_number_engraver"
6747 \remove "Clef_engraver"
6748 \remove "Key_engraver"
6749 \override StaffSymbol #'transparent = ##t
6750 \remove "Time_signature_engraver"
6751 \remove "Bar_engraver"
6752 minimumVerticalExtent = ##f
6756 \remove Ligature_bracket_engraver
6757 \consists Vaticana_ligature_engraver
6758 \override NoteHead #'style = #'vaticana_punctum
6759 \override Stem #'transparent = ##t
6765 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6766 \include "gregorian-init.ly"
6768 \notes \transpose c c' {
6769 % Scandicus Deminutus
6770 \[ g \pes a \pes \deminutum b \]
6777 \remove "Bar_number_engraver"
6781 \remove "Clef_engraver"
6782 \remove "Key_engraver"
6783 \override StaffSymbol #'transparent = ##t
6784 \remove "Time_signature_engraver"
6785 \remove "Bar_engraver"
6786 minimumVerticalExtent = ##f
6790 \remove Ligature_bracket_engraver
6791 \consists Vaticana_ligature_engraver
6792 \override NoteHead #'style = #'vaticana_punctum
6793 \override Stem #'transparent = ##t
6802 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6803 \include "gregorian-init.ly"
6805 \notes \transpose c c' {
6807 \[ g \oriscus a \pes \virga b \]
6814 \remove "Bar_number_engraver"
6818 \remove "Clef_engraver"
6819 \remove "Key_engraver"
6820 \override StaffSymbol #'transparent = ##t
6821 \remove "Time_signature_engraver"
6822 \remove "Bar_engraver"
6823 minimumVerticalExtent = ##f
6827 \remove Ligature_bracket_engraver
6828 \consists Vaticana_ligature_engraver
6829 \override NoteHead #'style = #'vaticana_punctum
6830 \override Stem #'transparent = ##t
6836 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6837 \include "gregorian-init.ly"
6839 \notes \transpose c c' {
6840 % Salicus Auctus Descendens
6841 \[ g \oriscus a \pes \auctum \descendens b \]
6848 \remove "Bar_number_engraver"
6852 \remove "Clef_engraver"
6853 \remove "Key_engraver"
6854 \override StaffSymbol #'transparent = ##t
6855 \remove "Time_signature_engraver"
6856 \remove "Bar_engraver"
6857 minimumVerticalExtent = ##f
6861 \remove Ligature_bracket_engraver
6862 \consists Vaticana_ligature_engraver
6863 \override NoteHead #'style = #'vaticana_punctum
6864 \override Stem #'transparent = ##t
6874 @lilypond[noindent,staffsize=26,nofragment,linewidth=1.0\cm]
6875 \include "gregorian-init.ly"
6877 \notes \transpose c c' {
6879 \[ \stropha b \stropha b \stropha a \]
6886 \remove "Bar_number_engraver"
6890 \remove "Clef_engraver"
6891 \remove "Key_engraver"
6892 \override StaffSymbol #'transparent = ##t
6893 \remove "Time_signature_engraver"
6894 \remove "Bar_engraver"
6895 minimumVerticalExtent = ##f
6899 \remove Ligature_bracket_engraver
6900 \consists Vaticana_ligature_engraver
6901 \override NoteHead #'style = #'vaticana_punctum
6902 \override Stem #'transparent = ##t
6914 Unlike most other neumes notation systems, the input language for
6915 neumes does not necessarily reflect directly the typographical
6916 appearance, but is designed to solely focuse on musical meaning. For
6917 example, @code{\[ a \pes b \flexa g \]} produces a Torculus consisting
6918 of three Punctum heads, while @code{\[ a \flexa g \pes b \]} produces
6919 a Porrectus with a curved flexa shape and only a single Punctum head.
6920 There is no command to explicitly typeset the curved flexa shape; the
6921 decision of when to typeset a curved flexa shape is purely taken from
6922 the musical input. The idea of this approach is to separate the
6923 musical aspects of the input from the notation style of the output.
6924 This way, the same input can be reused to typeset the same music in a
6925 different style of Gregorian chant notation such as Hufnagel (also
6926 known as German gothic neumes) or Medicaea (kind of a very simple
6927 forerunner of the Editio Vaticana). As soon as Hufnagel ligature
6928 engraver and Medicaea ligature engraver will have been implemented, it
6929 will be as simple as replacing the ligature engraver in the
6930 @internalsref{Voice} context to get the desired notation style from
6933 The following table shows the code fragments that produce the
6934 ligatures in the above neumes table. The letter in the first column
6935 in each line of the below table indicates to which ligature in the
6936 above table it refers. The second column gives the name of the
6937 ligature. The third column shows the code fragment that produces this
6938 ligature, using @code{g}, @code{a} and @code{b} as example pitches.
6940 @multitable @columnfractions .1 .4 .5
6954 Punctum Inclinatum @tab
6955 @code{\[ \inclinatum b \]}
6959 Punctum Auctum Ascendens @tab
6960 @code{\[ \auctum \ascendens b \]}
6964 Punctum Auctum Descendens @tab
6965 @code{\[ \auctum \descendens b \]}
6969 Punctum Inclinatum Auctum @tab
6970 @code{\[ \inclinatum \auctum b \]}
6974 Punctum Inclinatum Parvum @tab
6975 @code{\[ \inclinatum \deminutum b \]}
6980 @code{\[ \virga b \]}
6985 @code{\[ \stropha b \]}
6990 @code{\[ \stropha \auctum b \]}
6995 @code{\[ \oriscus b \]}
6999 Clivis vel Flexa @tab
7000 @code{\[ b \flexa g \]}
7004 Clivis Aucta Descendens @tab
7005 @code{\[ b \flexa \auctum \descendens g \]}
7009 Clivis Aucta Ascendens @tab
7010 @code{\[ b \flexa \auctum \ascendens g \]}
7015 @code{\[ b \flexa \deminutum g \]}
7019 Podatus vel Pes @tab
7020 @code{\[ g \pes b \]}
7024 Pes Auctus Descendens @tab
7025 @code{\[ g \pes \auctum \descendens b \]}
7029 Pes Auctus Ascendens @tab
7030 @code{\[ g \pes \auctum \ascendens b \]}
7035 @code{\[ g \pes \deminutum b \]}
7040 @code{\[ \oriscus g \pes \virga b \]}
7044 Pes Quassus Auctus Descendens @tab
7045 @code{\[ \oriscus g \pes \auctum \descendens b \]}
7050 @code{\[ \quilisma g \pes b \]}
7054 Quilisma Pes Auctus Descendens @tab
7055 @code{\[ \quilisma g \pes \auctum \descendens b \]}
7059 Pes Initio Debilis @tab
7060 @code{\[ \deminutum g \pes b \]}
7064 Pes Auctus Descendens Initio Debilis @tab
7065 @code{\[ \deminutum g \pes \auctum \descendens b \]}
7070 @code{\[ a \pes b \flexa g \]}
7074 Torculus Auctus Descendens @tab
7075 @code{\[ a \pes b \flexa \auctum \descendens g \]}
7079 Torculus Deminutus @tab
7080 @code{\[ a \pes b \flexa \deminutum g \]}
7084 Torculus Initio Debilis @tab
7085 @code{\[ \deminutum a \pes b \flexa g \]}
7089 Torculus Auctus Descendens Initio Debilis @tab
7090 @code{\[ \deminutum a \pes b \flexa \auctum \descendens g \]}
7094 Torculus Deminutus Initio Debilis @tab
7095 @code{\[ \deminutum a \pes b \flexa \deminutum g \]}
7100 @code{\[ a \flexa g \pes b \]}
7104 Porrectus Auctus Descendens @tab
7105 @code{\[ a \flexa g \pes \auctum \descendens b \]}
7109 Porrectus Deminutus @tab
7110 @code{\[ a \flexa g \pes \deminutum b \]}
7115 @code{\[ \virga b \inclinatum a \inclinatum g \]}
7119 Climacus Auctus @tab
7120 @code{\[ \virga b \inclinatum a \inclinatum \auctum g \]}
7124 Climacus Deminutus @tab
7125 @code{\[ \virga b \inclinatum a \inclinatum \deminutum g \]}
7130 @code{\[ g \pes a \virga b \]}
7134 Scandicus Auctus Descendens @tab
7135 @code{\[ g \pes a \pes \auctum \descendens b \]}
7139 Scandicus Deminutus @tab
7140 @code{\[ g \pes a \pes \deminutum b \]}
7145 @code{\[ g \oriscus a \pes \virga b \]}
7149 Salicus Auctus Descendens @tab
7150 @code{\[ g \oriscus a \pes \auctum \descendens b \]}
7155 @code{\[ \stropha b \stropha b \stropha a \]}
7161 The following head prefixes are supported:
7163 @cindex @code{\virga}
7165 @cindex @code{\stropha}
7167 @cindex @code{\inclinatum}
7169 @cindex @code{\auctum}
7171 @cindex @code{\descendens}
7173 @cindex @code{\ascendens}
7175 @cindex @code{\oriscus}
7177 @cindex @code{\quilisma}
7179 @cindex @code{\deminutum}
7182 Head prefixes can be accumulated, though restrictions apply. For
7183 example, either @code{\descendens} or @code{\ascendens} can be applied
7184 to a head, but not both to the same head.
7187 @cindex @code{\flexa}
7188 Two adjacent heads can be tied together with the @code{\pes} and
7189 @code{\flexa} infix commands for a rising and falling line of melody,
7194 Trigonus: apply equal spacing, regardless of pitch.
7197 @subsection Figured bass
7199 @cindex Basso continuo
7201 @c TODO: musicological blurb about FB
7205 LilyPond has limited support for figured bass:
7207 @lilypond[verbatim,fragment]
7209 \context Voice \notes { \clef bass dis4 c d ais}
7210 \context FiguredBass
7212 < 6 >4 < 7 >8 < 6+ [_!] >
7218 The support for figured bass consists of two parts: there is an input
7219 mode, introduced by @code{\figures}, where you can enter bass figures
7220 as numbers, and there is a context called @internalsref{FiguredBass} that
7221 takes care of making @internalsref{BassFigure} objects.
7223 In figures input mode, a group of bass figures is delimited by
7224 @code{<} and @code{>}. The duration is entered after the @code{>>}:
7229 \context FiguredBass
7233 Accidentals are added when you append @code{-}, @code{!} and @code{+}
7240 \context FiguredBass
7241 \figures { <4- 6+ 7!> }
7244 Spaces or dashes may be inserted by using @code{_}. Brackets are
7245 introduced with @code{[} and @code{]}:
7251 \context FiguredBass
7252 \figures { < [4 6] 8 [_! 12]> }
7255 Although the support for figured bass may superficially resemble chord
7256 support, it works much simpler. The @code{\figures} mode simply
7257 stores the numbers , and @internalsref{FiguredBass} context prints
7258 them as entered. There is no conversion to pitches, and no
7259 realizations of the bass are played in the MIDI file.
7261 Internally, the code produces markup texts. You can use any of the
7262 markup text properties to override formatting. For example, the
7263 vertical spacing of the figures may be set with @code{baseline-skip}.
7267 Internals: @internalsref{BassFigureEvent} music, @internalsref{BassFigure} object,
7268 and @internalsref{FiguredBass} context.
7272 Slash notation for alterations is not supported.
7275 @node Vaticana style contexts
7276 @subsection Vaticana style contexts
7278 @cindex VaticanaVoiceContext
7279 @cindex VaticanaStaffContext
7281 The predefined @code{VaticanaVoiceContext} and
7282 @code{VaticanaStaffContext} can be used to easily engrave a piece of
7283 Gregorian Chant in the style of the Editio Vaticana. These contexts
7284 initialize all relevant context properties and grob properties to
7285 proper values. With these contexts, you can immediately go ahead
7286 entering the chant, as the following short excerpt demonstrates:
7288 @lilypond[raggedright,verbatim,noindent]
7289 \include "gregorian-init.ly"
7292 \context VaticanaVoice = "cantus" {
7293 \override Score.BarNumber #'transparent = ##t
7295 \[ c'\melisma c' \flexa a \] \[ a \flexa \deminutum g\melismaEnd \] f \divisioMinima
7296 \[ f\melisma \pes a c' c' \pes d'\melismaEnd \] c' \divisioMinima \break
7297 \[ c'\melisma c' \flexa a \] \[ a \flexa \deminutum g\melismaEnd \] f \divisioMinima
7300 \lyricsto "cantus" \new Lyrics \lyrics {
7301 San- ctus, San- ctus, San- ctus
7307 @node Contemporary notation
7308 @section Contemporary notation
7310 In the 20th century, composers have greatly expanded the musical
7311 vocabulary. With this expansion, many innovations in musical notation
7312 have been tried. The book by Stone (1980) gives a comprehensive
7313 overview (see @ref{Literature list}). In general, the use of new,
7314 innovative notation makes a piece harder to understand and perform and
7315 its use should therefore be avoided if possible. For this reason,
7316 support for contemporary notation in LilyPond is limited.
7325 @subsection Clusters
7329 In musical terminology, a @emph{cluster} denotes a range of
7330 simultaneously sounding pitches that may change over time. The set of
7331 available pitches to apply usually depends on the accoustic source.
7332 Thus, in piano music, a cluster typically consists of a continous range
7333 of the semitones as provided by the piano's fixed set of a chromatic
7334 scale. In choral music, each singer of the choir typically may sing an
7335 arbitrary pitch within the cluster's range that is not bound to any
7336 diatonic, chromatic or other scale. In electronic music, a cluster
7337 (theoretically) may even cover a continuous range of pitches, thus
7338 resulting in coloured noise, such as pink noise.
7340 Clusters can be denoted in the context of ordinary staff notation by
7341 engraving simple geometrical shapes that replace ordinary notation of
7342 notes. Ordinary notes as musical events specify starting time and
7343 duration of pitches; however, the duration of a note is expressed by the
7344 shape of the note head rather than by the horizontal graphical extent of
7345 the note symbol. In contrast, the shape of a cluster geometrically
7346 describes the development of a range of pitches (vertical extent) over
7347 time (horizontal extent). Still, the geometrical shape of a cluster
7348 covers the area in wich any single pitch contained in the cluster would
7349 be notated as an ordinary note. From this point of view, it is
7350 reasonable to specify a cluster as the envelope of a set of notes.
7354 A cluster is engraved as the envelope of a set of
7355 cluster-notes. Cluster notes are created by applying the function
7356 @code{notes-to-clusters} to a sequence of chords, e.g.
7358 @lilypond[relative=1,verbatim]
7359 \apply #notes-to-clusters { <c e > <b f'> }
7362 The following example (from
7363 @inputfileref{input/regression,cluster.ly}) shows what the result
7366 @lilypondfile[]{cluster.ly}
7368 By default, @internalsref{Cluster_spanner_engraver} is in the
7369 @internalsref{Voice} context. This allows putting ordinary notes and
7370 clusters together in the same staff, even simultaneously. In such a
7371 case no attempt is made to automatically avoid collisions between
7372 ordinary notes and clusters.
7376 Internals: @internalsref{ClusterSpanner},
7377 @internalsref{ClusterSpannerBeacon},
7378 @internalsref{Cluster_spanner_engraver}, and
7379 @internalsref{ClusterNoteEvent}.
7381 Examples: @inputfileref{input/regression,cluster.ly}.
7385 Music expressions like @code{<< @{ g8 e8 @} a4 >>} are not printed
7386 accurately. Use @code{<g a>8 <e a>8} instead.
7391 @subsection Fermatas
7397 Contemporary music notation frequently uses special fermata symbols to
7398 indicate fermatas of differing lengths.
7402 The following are supported
7404 @lilypond[raggedright]
7406 << \addlyrics \notes {
7426 \context Lyrics \lyrics {
7427 "shortfermata" "fermata" "longfermata" "verylongfermata"
7432 See @ref{Articulations} for general instructions how to apply scripts
7433 such as fermatas to a @code{\notes@{@}} block.
7436 @node Special notation
7437 @section Special notation
7441 * Easy Notation note heads::
7445 @subsection Balloon help
7447 Elements of notation can be marked and named with the help of a square
7448 balloon. The primary purpose of this feature is to explain notation.
7450 The following example demonstrates its use.
7452 @lilypond[verbatim,fragment,raggedright,relative=1]
7455 #(add-balloon-text 'NoteHead "heads, or tails?"
7461 The function @code{add-balloon-text} takes the name of a grob, the
7462 label to print and where to put the label relative to the object. In
7463 the above example, the text ``heads or tails?'' ends 3 spaces below
7467 @cindex notation, explaining
7471 Internals: @internalsref{text-balloon-interface}.
7473 Examples: @inputfileref{input/regression,balloon.ly}.
7475 @node Easy Notation note heads
7476 @subsection Easy Notation note heads
7478 @cindex easy notation
7481 The `easy play' note head includes a note name inside the head. It is
7482 used in music aimed at beginners:
7484 @lilypond[raggedright,verbatim,staffsize=26]
7486 \notes { c'2 e'4 f' | g'1 }
7487 \paper { \translator { \EasyNotation } }
7491 The @code{EasyNotation} variable overrides a @internalsref{Score} @c
7492 context. To make the letters readable, it has to be printed in a
7493 large font size. To print with a larger font, see @ref{Font Size}.
7498 If you view the result with Xdvi, then staff lines may show through
7499 the letters. Printing the PostScript file obtained does produce the
7505 @section Tuning output
7507 There are situations where default layout decisions are not
7508 sufficient. In this section we discuss ways to override these
7511 Formatting is internally done by manipulating so called objects
7512 (graphic objects). Each object carries with it a set of properties
7513 (object or layout properties) specific to that object. For example, a
7514 stem object has properties that specify its direction, length and
7517 The most direct way of tuning the output is by altering the values of
7518 these properties. There are two ways of doing that: first, you can
7519 temporarily change the definition of one type of object, thus
7520 affecting a whole set of objects. Second, you can select one specific
7521 object, and set a layout property in that object.
7523 Do not confuse layout properties with translation
7524 properties. Translation properties always use a mixed caps style
7525 naming, and are manipulated using @code{\set} and @code{\unset}:
7527 \set Context.propertyName = @var{value}
7530 Layout properties are use Scheme style variable naming, i.e. lower
7531 case words separated with dashes. They are symbols, and should always
7532 be quoted using @code{#'}. For example, this could be an imaginary
7533 layout property name:
7535 #'layout-property-name
7540 The introduction of the @ref{Technical manual} gives a more in-depth
7541 treatment of the difference between translation and layout.
7545 * Constructing a tweak::
7552 @node Tuning objects
7553 @subsection Tuning objects
7555 @cindex object description
7557 The definition of an object is a list of default object
7558 properties. For example, the definition of the Stem object (available
7559 in @file{scm/define-grobs.scm}), includes the following definitions
7560 for @internalsref{Stem}:
7564 (beamed-lengths . (3.5 3.5 3.5 4.5 5.0))
7565 (Y-extent-callback . ,Stem::height)
7570 Adding variables on top of this existing definition overrides the
7571 system default, and alters the resulting appearance of the layout
7577 Changing a variable for only one object is commonly achieved with
7581 \once \override @var{context}.@var{objectname}
7582 @var{symbol} = @var{value}
7584 Here @var{symbol} is a Scheme expression of symbol type, @var{context}
7585 and @var{objectname} is a string and @var{value} is a Scheme expression.
7586 This command applies a setting only during one moment in the score.
7588 In the following example, only one @internalsref{Stem} object is
7589 changed from its original setting:
7591 @lilypond[verbatim,fragment,relative=1]
7593 \once \override Voice.Stem #'thickness = #4
7597 @cindex @code{\once}
7599 For changing more objects, the same command, without @code{\once} can
7602 \override @var{context}.@var{objectname} @var{symbol} = @var{value}
7604 This command adds @code{@var{symbol} = @var{value}} to the definition
7605 of @var{objectname} in the context @var{context}, and this definition
7606 stays in place until it is removed.
7608 An existing definition may be removed by the following command:
7611 \property @var{context}.@var{objectname} \revert @var{symbol}
7616 @lilypond[verbatim,quote]
7617 c'4 \override Stem #'thickness = #4.0
7619 c'4 \revert Stem #'thickness
7623 The following example gives exactly the same result as the previous
7624 one (assuming the system default for stem thickness is 1.3):
7626 @lilypond[verbatim,quote]
7627 c'4 \override Stem #'thickness = #4.0
7629 c'4 \override Stem #'thickness = #1.3
7633 Reverting a setting which was not set in the first place has no
7639 Internals: @internalsref{OverrideProperty}, @internalsref{RevertProperty},
7640 @internalsref{PropertySet}, @internalsref{All-backend-properties}, and
7641 @internalsref{All-layout-objects}.
7646 The backend is not very strict in type-checking object properties.
7647 Cyclic references in Scheme values for properties can cause hangs
7651 * Constructing a tweak::
7657 @node Constructing a tweak
7658 @subsection Constructing a tweak
7661 @cindex internal documentation
7662 @cindex finding graphical objects
7663 @cindex graphical object descriptions
7665 @cindex @code{\override}
7667 @cindex internal documentation
7671 Three pieces of information are required to use @code{\override} and
7672 @code{\set}: the name of the layout object, the context and the name
7673 of the property. We demonstrate how to glean this information from
7674 the notation manual and the generated documentation.
7676 The generated documentation is a set of HTML pages which should be
7677 included if you installed a binary distribution, typically in
7678 @file{/usr/share/doc/lilypond}. They are also available on the web:
7679 go to the @uref{http://lilypond.org,LilyPond website}, click
7680 ``Documentation'', select the correct version, and click then
7681 ``Program reference.'' It is advisable to bookmark the local HTML
7682 files. They will load faster than the ones on the web. If you use the
7683 version from the web, you must check whether the documentation matches
7684 the program version: it is generated from the definitions that the
7685 program uses, and therefore it is strongly tied to the LilyPond
7689 @c [TODO: revise for new site.]
7691 Suppose we want to move the fingering indication in the fragment below:
7693 @lilypond[relative=2,verbatim]
7699 If you visit the documentation of @code{Fingering} (in @ref{Fingering
7700 instructions}), you will notice that there is written:
7705 Internals: @internalsref{FingerEvent} and @internalsref{Fingering}.
7712 In other words, the fingerings once entered, are internally stored as
7713 @code{FingerEvent} music objects. When printed, a @code{Fingering}
7714 layout object is created for every @code{FingerEvent}.
7716 The Fingering object has a number of different functions, and each of
7717 those is captured in an interface. The interfaces are listed under
7718 @internalsref{Fingering} in the program reference.
7722 The @code{Fingering} object has a fixed size
7723 (@internalsref{item-interface}), the symbol is a piece of text
7724 (@internalsref{text-interface}), whose font can be set
7725 (@internalsref{font-interface}). It is centered horizontally
7726 (@internalsref{self-alignment-interface}), it is placed next to other
7727 objects (@internalsref{side-position-interface}) vertically, and its
7728 placement is coordinated with other scripts
7729 (@internalsref{text-script-interface}). It also has the standard
7730 @internalsref{grob-interface} (grob stands for Graphical object)
7732 @cindex graphical object
7733 @cindex layout object
7734 @cindex object, layout
7735 with all the variables that come with
7736 it. Finally, it denotes a fingering instruction, so it has
7737 @internalsref{finger-interface}.
7739 For the vertical placement, we have to look under
7740 @code{side-position-interface}:
7742 @code{side-position-interface}
7744 Position a victim object (this one) next to other objects (the
7745 support). In this case, the property @code{direction} signifies where to put the
7746 victim object relative to the support (left or right, up or down?)
7751 below this description, the variable @code{padding} is described as
7755 (dimension, in staff space)
7757 add this much extra space between objects that are next to each
7758 other. Default value: @code{0.6}
7762 By increasing the value of @code{padding}, we can move away the
7763 fingering. The following command inserts 3 staff spaces of white
7764 between the note and the fingering:
7766 \once \override Fingering #'padding = #3
7769 Inserting this command before the Fingering object is created,
7770 i.e. before @code{c2}, yields the following result:
7772 @lilypond[relative=2,fragment,verbatim]
7773 \once \override Fingering
7780 The context name @code{Voice} in the example above can be determined
7781 as follows. In the documentation for @internalsref{Fingering}, it says
7783 Fingering grobs are created by: @internalsref{Fingering_engraver} @c
7786 Clicking @code{Fingering_engraver} shows the documentation of
7787 the module responsible for interpreting the fingering instructions and
7788 translating them to a @code{Fingering} object. Such a module is called
7789 an @emph{engraver}. The documentation of the @code{Fingering_engraver}
7792 Fingering_engraver is part of contexts: Voice
7794 so tuning the settings for Fingering should be done with
7796 \override Fingering @dots{}
7799 Of course, the tweak may also done in a larger context than
7800 @code{Voice}, for example, @internalsref{Staff} or
7801 @internalsref{Score}.
7805 Internals: the program reference also contains alphabetical lists of
7806 @internalsref{Contexts}, @internalsref{All-layout-objects} and
7807 @internalsref{Music-expressions}, so you can also find which objects
7808 to tweak by browsing the internals document.
7812 @subsection Applyoutput
7814 The most versatile way of tuning an object is @code{\applyoutput}. Its
7817 \applyoutput @var{proc}
7821 where @var{proc} is a Scheme function, taking three arguments.
7823 When interpreted, the function @var{proc} is called for every layout
7824 object found in the context, with the following arguments:
7826 @item the layout object itself,
7827 @item the context where the layout object was created, and
7828 @item the context where @code{\applyoutput} is processed.
7832 In addition, the cause of the layout object, i.e. the music
7833 expression or object that was responsible for creating it, is in the
7834 object property @code{cause}. For example, for a note head, this is a
7835 @internalsref{NoteHead} event, and for a @internalsref{Stem} object,
7836 this is a @internalsref{NoteHead} object.
7838 Here is a simple example of @code{\applyoutput}; it blanks note-heads on the
7841 (define (blanker grob grob-origin context)
7842 (if (and (memq (ly:get-grob-property grob 'interfaces)
7843 note-head-interface)
7844 (eq? (ly:get-grob-property grob 'staff-position) 0))
7846 (ly:set-grob-property! grob 'transparent #t)))
7851 @node Font selection
7852 @subsection Font selection
7854 The most common thing to change about the appearance of fonts is their
7855 size. The font size of any context can be easily changed by setting
7856 the @code{fontSize} property for that context. Its value is a number:
7857 negative numbers make the font smaller, positive numbers larger. An
7858 example is given below:
7860 @lilypond[fragment,relative=1,verbatim,quote]
7861 c4 c4 \set fontSize = #-1
7864 This command will set @code{font-size} (see below), and does
7865 not change the size of variable symbols, such as beams or slurs.
7867 One of the uses of @code{fontSize} is to get smaller symbols for cue
7868 notes. An elaborate example of those is in
7869 @inputfileref{input/test,cue-notes.ly}.
7871 @cindex magnification
7874 The font used for printing a object can be selected by setting
7875 @code{font-name}, e.g.
7877 \override Staff.TimeSignature
7878 #'font-name = #"cmr17"
7882 Any font can be used, as long as it is available to @TeX{}. Possible
7883 fonts include foreign fonts or fonts that do not belong to the
7884 Computer Modern font family. The size of fonts selected in this way
7885 can be changed with the @code{font-magnification} property. For
7886 example, @code{2.0} blows up all letters by a factor 2 in both
7890 @cindex font magnification
7892 Font selection for the standard fonts, @TeX{}'s Computer Modern fonts,
7893 can also be adjusted with a more fine-grained mechanism. By setting
7894 the object properties described below, you can select a different font;
7895 all three mechanisms work for every object that supports
7896 @code{font-interface}:
7901 is a symbol indicating the general class of the typeface. Supported are
7902 @code{roman} (Computer Modern), @code{braces} (for piano staff
7903 braces), @code{music} (the standard music font, including ancient
7904 glyphs), @code{dynamic} (for dynamic signs) and @code{typewriter}.
7907 is a symbol indicating the shape of the font, there are typically several
7908 font shapes available for each font family. Choices are @code{italic},
7909 @code{caps} and @code{upright}.
7912 is a symbol indicating the series of the font. There are typically several
7913 font series for each font family and shape. Choices are @code{medium}
7918 For any of these properties, the value @code{*} (i.e. the symbol
7919 @code{*}, entered as @code{#'*}), acts as a wildcard. This can be used
7920 to override default setting, which are always present. For example:
7922 \override Lyrics .LyricText #'font-series = #'bold
7923 \override Lyrics .LyricText #'font-family = #'typewriter
7924 \override Lyrics .LyricText #'font-shape = #'*
7927 @cindex @code{font-style}
7929 The font size is set by modifying the @code{font-size} property. Its
7930 value is a number indicating the size relative to the standard size.
7931 Each step up is an increase of approximately 12% of the font size. Six
7932 steps is exactly a factor two. The Scheme function @code{magstep}
7933 converts a @code{font-size} number to a scaling factor.
7935 LilyPond has fonts in different design sizes: the music fonts for
7936 smaller sizes are chubbier, while the text fonts are relatively wider.
7937 Font size changes are achieved by scaling the design size that is
7938 closest to the desired size.
7940 The @code{font-size} mechanism does not work for fonts selected
7941 through @code{font-name}. These may be scaled with
7942 @code{font-magnification}.
7946 The following commands set @code{fontSize} for the current voice.
7948 @cindex @code{\tiny}
7950 @cindex @code{\small}
7952 @cindex @code{\normalsize}
7957 Init files: @file{ly/declarations-init.ly} contains hints how new
7958 fonts may be added to LilyPond.
7962 There is no style sheet provided for other fonts besides the @TeX{}
7963 Computer Modern family.
7965 @cindex font selection
7966 @cindex font magnification
7967 @cindex @code{font-interface}
7971 @section Text markup
7976 @cindex typeset text
7978 LilyPond has an internal mechanism to typeset texts. You can access it
7979 with the keyword @code{\markup}. Within markup mode, you can enter texts
7980 similar to lyrics: simply enter them, surrounded by spaces:
7983 @lilypond[verbatim,fragment,relative=1]
7984 c1^\markup { hello }
7985 c1_\markup { hi there }
7986 c1^\markup { hi \bold there, is \italic anyone home? }
7989 @cindex font switching
7991 The markup in the example demonstrates font switching commands. The
7992 command @code{\bold} and @code{\italic} only apply to the first
7993 following word; enclose a set of texts with braces to apply a command
7996 \markup @{ \bold @{ hi there @} @}
8000 For clarity, you can also do this for single arguments, e.g.
8003 \markup { is \italic { anyone } home }
8006 @cindex font size, texts
8009 In markup mode you can compose expressions, similar to mathematical
8010 expressions, XML documents and music expressions. The braces group
8011 notes into horizontal lines. Other types of lists also exist: you can
8012 stack expressions grouped with @code{<}, and @code{>} vertically with
8013 the command @code{\column}. Similarly, @code{\center} aligns texts by
8016 @lilypond[verbatim,fragment,relative=1]
8017 c1^\markup { \column < a bbbb c > }
8018 c1^\markup { \center < a bbbb c > }
8019 c1^\markup { \line < a b c > }
8023 Markups can be stored in variables, and these variables
8024 may be attached to notes, like
8026 allegro = \markup { \bold \large { Allegro } }
8027 \notes { a^\allegro b c d }
8031 Some objects have alignment procedures of their own, which cancel out
8032 any effects of alignments applied to their markup arguments as a
8033 whole. For example, the @internalsref{RehearsalMark} is horizontally
8034 centered, so using @code{\mark \markup @{ \left-align .. @}} has no
8035 effect. Similarly, whole texts over notes cannot be moved vertically
8036 with @code{\raise}. For moving and aligning complete objects, grob
8037 properties should be used.
8043 Init files: @file{scm/new-markup.scm}.
8048 Text layout is ultimately done by @TeX{}, which does kerning of
8049 letters. LilyPond does not account for kerning, so texts will be
8050 spaced slightly too wide.
8052 Syntax errors for markup mode are confusing.
8054 Markup texts cannot be used in the titling of the @code{\header}
8055 field. Titles are made by La@TeX{}, so La@TeX{} commands should be used
8061 * Overview of text markup commands::
8062 * Markup construction in scheme::
8063 * Markup command definition::
8066 @node Overview of text markup commands
8067 @subsection Overview of text markup commands
8069 @include markup-commands.tely
8071 @node Markup construction in scheme
8072 @subsection Markup construction in scheme
8074 @cindex defining markup commands
8076 The @code{markup} macro builds markup expressions in Scheme while
8077 providing a LilyPond-like syntax. For example,
8079 (markup #:column (#:line (#:bold #:italic "hello" #:raise 0.4 "world")
8080 #:bigger #:line ("foo" "bar" "baz")))
8086 \markup \column < @{ \bold \italic "hello" \raise #0.4 "world" @}
8087 \bigger @{ foo bar baz @} >
8091 This example exposes the main translation rules between regular
8092 LilyPond markup syntax and scheme markup syntax, which are summed up
8094 @multitable @columnfractions .5 .5
8095 @item @b{LilyPond} @tab @b{Scheme}
8096 @item @code{\command} @tab @code{#:command}
8097 @item @code{\variable} @tab @code{variable}
8098 @item @code{@{ ... @}} @tab @code{#:line ( ... )}
8099 @item @code{\center < ... >} @tab @code{#:center ( ... )}
8100 @item @code{string} @tab @code{"string"}
8101 @item @code{#scheme-arg} @tab @code{scheme-arg}
8104 Besides, the whole scheme language is accessible inside the
8105 @code{markup} macro: thus, one may use function calls inside
8106 @code{markup} in order to manipulate character strings for
8107 instance. This proves useful when defining new markup commands (see
8108 @ref{Markup command definition}).
8112 One can not feed the @code{#:line} (resp @code{#:center},
8113 @code{#:column}) command with a variable or the result of a function
8116 (markup #:line (fun-that-returns-markups))
8118 is illegal. One should use the @code{make-line-markup} (resp
8119 @code{make-center-markup}, @code{make-column-markup}) function
8122 (markup (make-line-markup (fun-that-returns-markups)))
8125 @node Markup command definition
8126 @subsection Markup command definition
8128 New markup commands can be defined thanks to the @code{def-markup-command} scheme macro.
8130 (def-markup-command (@var{command-name} @var{paper} @var{props} @var{arg1} @var{arg2} ...)
8131 (@var{arg1-type?} @var{arg2-type?} ...)
8134 @var{argi}: i@var{th} command argument
8135 @var{argi-type?}: a type predicate for the i@var{th} argument
8136 @var{paper}: the `paper' definition
8137 @var{props}: a list of alists, containing all active properties.
8140 As a simple example, we show how to add a @code{\smallcaps} command,
8141 which selects @TeX{}'s small caps font. Normally, we could select the
8142 small caps font as follows:
8145 \markup { \override #'(font-shape . caps) Text-in-caps }
8148 This selects the caps font by setting the @code{font-shape} property to
8149 @code{#'caps} for interpreting @code{Text-in-caps}.
8151 To make the above available as @code{\smallcaps} command, we have to
8152 define a function using @code{def-markup-command}. The command should
8153 take a single argument, of markup type. Therefore, the start of the
8154 definition should read
8156 (def-markup-command (smallcaps paper props argument) (markup?)
8161 What follows is the content of the command: we should interpret
8162 the @code{argument} as a markup, i.e.
8165 (interpret-markup paper @dots{} argument)
8169 This interpretation should add @code{'(font-shape . caps)} to the active
8170 properties, so we substitute the the following for the @dots{} in the
8174 (cons (list '(font-shape . caps) ) props)
8178 The variable @code{props} is a list of alists, and we prepend to it by
8179 consing a list with the extra setting.
8181 However, suppose that we are using a font that does not have a
8182 small-caps variant. In that case, we have to fake the small caps font,
8183 by setting a string in upcase, with the first letter a little larger:
8186 #(def-markup-command (smallcaps paper props str) (string?)
8187 "Print the string argument in small caps. Syntax: \\smallcaps #\"string\""
8188 (interpret-markup paper props
8191 (if (= (string-length s) 0)
8193 (markup #:large (string-upcase (substring s 0 1))
8194 #:translate (cons -0.6 0)
8195 #:tiny (string-upcase (substring s 1)))))
8196 (string-split str #\Space)))))
8199 The @code{smallcaps} command first splits its string argument into
8200 tokens separated by spaces (@code{(string-split str #\Space)}); for
8201 each token, a markup is built with the first letter made large and
8202 upcased (@code{#:large (string-upcase (substring s 0 1))}), and a
8203 second markup built with the following letters made tiny and upcased
8204 (@code{#:tiny (string-upcase (substring s 1))}). As LilyPond
8205 introduces a space between markups on a line, the second markup is
8206 translated to the left (@code{#:translate (cons -0.6 0) ...}). Then,
8207 the markups built for each token are put in a line
8208 (@code{(make-line-markup ...)}). Finally, the resulting markup is
8209 passed to the @code{interpret-markup} function, with the @code{paper}
8210 and @code{props} arguments.
8212 Finally, suppose that we are typesetting a recitative in an opera, and
8213 we would like to define a command that will show character names in a
8214 custom manner. Names should be printed with small caps and translated a
8215 bit to the left and top. We will define a @code{\character} command
8216 that takes into account the needed translation, and uses the newly
8217 defined @code{\smallcaps} command:
8220 #(def-markup-command (character paper props name) (string?)
8221 "Print the character name in small caps, translated to the left and
8222 top. Syntax: \\character #\"name\""
8223 (interpret-markup paper props
8224 (markup "" #:translate (cons -4 2) #:smallcaps name)))
8227 There is one complication that needs explanation: texts above and below
8228 the staff are moved vertically to be at a certain distance (the
8229 @code{padding} property) from the staff and the notes. To make sure
8230 that this mechanism does not annihilate the vertical effect of our
8231 @code{#:translate}, we add an empty string (@code{""}) before the
8232 translated text. Now the @code{""} will be put above the notes, and the
8233 @code{name} is moved in relation to that empty string. The net effect is
8234 that the text is moved to the upper left.
8236 The final result is as follows:
8240 c''^\markup \character #"Cleopatra"
8241 e'^\markup \character #"Giulio Cesare"
8246 @lilypond[raggedright]
8247 #(def-markup-command (smallcaps paper props str) (string?)
8248 "Print the string argument in small caps. Syntax: \\smallcaps #\"string\""
8249 (interpret-markup paper props
8252 (if (= (string-length s) 0)
8254 (markup #:large (string-upcase (substring s 0 1))
8255 #:translate (cons -0.6 0)
8256 #:tiny (string-upcase (substring s 1)))))
8257 (string-split str #\Space)))))
8259 #(def-markup-command (character paper props name) (string?)
8260 "Print the character name in small caps, translated to the left and
8261 top. Syntax: \\character #\"name\""
8262 (interpret-markup paper props
8263 (markup "" #:translate (cons -4 0) #:smallcaps name)))
8267 c''^\markup \character #"Cleopatra"
8268 e'^\markup \character #"Giulio Cesare"
8276 @section Global layout
8278 The global layout determined by three factors: the page layout, the
8279 line breaks and the spacing. These all influence each other. The
8280 choice of spacing determines how densely each system of music is set,
8281 which influences where line breaks breaks are chosen, and thus
8282 ultimately how many pages a piece of music takes. This section
8283 explains how to tune the algorithm for spacing.
8285 Globally spoken, this procedure happens in three steps: first,
8286 flexible distances (``springs'') are chosen, based on durations. All
8287 possible line breaking combination are tried, and the one with the
8288 best results---a layout that has uniform density and requires as
8289 little stretching or cramping as possible---is chosen. When the score
8290 is processed by @TeX{}, each page is filled with systems, and page breaks
8291 are chosen whenever the page gets full.
8296 * Vertical spacing::
8297 * Horizontal spacing::
8304 @node Vertical spacing
8305 @subsection Vertical spacing
8307 @cindex vertical spacing
8308 @cindex distance between staves
8309 @cindex staff distance
8310 @cindex between staves, distance
8311 @cindex staffs per page
8312 @cindex space between staves
8314 The height of each system is determined automatically by LilyPond, to
8315 keep systems from bumping into each other, some minimum distances are
8316 set. By changing these, you can put staves closer together, and thus
8317 put more systems onto one page.
8319 Normally staves are stacked vertically. To make
8320 staves maintain a distance, their vertical size is padded. This is
8321 done with the property @code{minimumVerticalExtent}. It takes a pair
8322 of numbers, so if you want to make it smaller from its, then you could
8325 \set Staff.minimumVerticalExtent = #'(-4 . 4)
8327 This sets the vertical size of the current staff to 4 staff spaces on
8328 either side of the center staff line. The argument of
8329 @code{minimumVerticalExtent} is interpreted as an interval, where the
8330 center line is the 0, so the first number is generally negative. The
8331 staff can be made larger at the bottom by setting it to @code{(-6
8334 The piano staves are handled a little differently: to make cross-staff
8335 beaming work correctly, it is necessary that the distance between staves
8336 is fixed beforehand. This is also done with a
8337 @internalsref{VerticalAlignment} object, created in
8338 @internalsref{PianoStaff}. In this object the distance between the
8339 staves is fixed by setting @code{forced-distance}. If you want to
8340 override this, use a @code{\translator} block as follows:
8344 VerticalAlignment \override #'forced-distance = #9
8347 This would bring the staves together at a distance of 9 staff spaces,
8348 measured from the center line of each staff.
8352 Internals: Vertical alignment of staves is handled by the
8353 @internalsref{VerticalAlignment} object.
8357 @node Horizontal spacing
8358 @subsection Horizontal Spacing
8360 The spacing engine translates differences in durations into
8361 stretchable distances (``springs'') of differing lengths. Longer
8362 durations get more space, shorter durations get less. The shortest
8363 durations get a fixed amount of space (which is controlled by
8364 @code{shortest-duration-space} in the @internalsref{SpacingSpanner} object).
8365 The longer the duration, the more space it gets: doubling a
8366 duration adds a fixed amount (this amount is controlled by
8367 @code{spacing-increment}) of space to the note.
8369 For example, the following piece contains lots of half, quarter and
8370 8th notes, the eighth note is followed by 1 note head width (NHW).
8371 The quarter note is followed by 2 NHW, the half by 3 NHW, etc.
8372 @lilypond[fragment,verbatim,relative=1] c2 c4. c8 c4. c8 c4. c8 c8
8376 Normally, @code{shortest-duration-space} is set to 1.2, which is the
8377 width of a note head, and @code{shortest-duration-space} is set to
8378 2.0, meaning that the shortest note gets 2 NHW (i.e. 2 times
8379 @code{shortest-duration-space}) of space. For normal notes, this space
8380 is always counted from the left edge of the symbol, so the shortest
8381 notes are generally followed by one NHW of space.
8383 If one would follow the above procedure exactly, then adding a single
8384 32th note to a score that uses 8th and 16th notes, would widen up the
8385 entire score a lot. The shortest note is no longer a 16th, but a 32nd,
8386 thus adding 1 NHW to every note. To prevent this, the
8387 shortest duration for spacing is not the shortest note in the score,
8388 but the most commonly found shortest note. Notes that are even
8389 shorter this are followed by a space that is proportional to their
8390 duration relative to the common shortest note. So if we were to add
8391 only a few 16th notes to the example above, they would be followed by
8394 @lilypond[fragment,verbatim,relative=2]
8395 c2 c4. c8 c4. c16[ c] c4. c8 c8 c8 c4 c4 c4
8398 The most common shortest duration is determined as follows: in every
8399 measure, the shortest duration is determined. The most common short
8400 duration, is taken as the basis for the spacing, with the stipulation
8401 that this shortest duration should always be equal to or shorter than
8402 1/8th note. The shortest duration is printed when you run lilypond
8403 with @code{--verbose}. These durations may also be customized. If you
8404 set the @code{common-shortest-duration} in
8405 @internalsref{SpacingSpanner}, then this sets the base duration for
8406 spacing. The maximum duration for this base (normally 1/8th), is set
8407 through @code{base-shortest-duration}.
8409 @cindex @code{common-shortest-duration}
8410 @cindex @code{base-shortest-duration}
8411 @cindex @code{stem-spacing-correction}
8412 @cindex @code{spacing}
8414 In the introduction it was explained that stem directions influence
8415 spacing. This is controlled with @code{stem-spacing-correction}
8416 property in @internalsref{NoteSpacing}, which are generated for every
8417 @internalsref{Voice} context. The @code{StaffSpacing} object
8418 (generated at @internalsref{Staff} context) contains the same property
8419 for controlling the stem/barline spacing. The following example
8420 shows these corrections, once with default settings, and once with
8421 exaggerated corrections:
8427 \override Staff.NoteSpacing #'stem-spacing-correction
8429 \override Staff.StaffSpacing #'stem-spacing-correction
8434 \paper { raggedright = ##t } }
8437 @cindex SpacingSpanner, overriding properties
8439 Properties of the @internalsref{SpacingSpanner} must be overridden
8440 from the @code{\paper} block, since the @internalsref{SpacingSpanner} is
8441 created before any property commands are interpreted.
8443 \paper @{ \translator @{
8445 SpacingSpanner \override #'spacing-increment = #3.0
8452 Internals: @internalsref{SpacingSpanner}, @internalsref{NoteSpacing},
8453 @internalsref{StaffSpacing}, @internalsref{SeparationItem}, and
8454 @internalsref{SeparatingGroupSpanner}.
8458 Spacing is determined on a score wide basis. If you have a score that
8459 changes its character (measured in durations) halfway during the
8460 score, the part containing the longer durations will be spaced too
8463 There is no convenient mechanism to manually override spacing.
8468 @subsection Font size
8469 @cindex font size, setting
8470 @cindex staff size, setting
8471 @cindex @code{paper} file
8473 The Feta font provides musical symbols at eight seven different
8474 sizes. Each font is tuned for a different staff size: at smaller sizes
8475 the font gets heavier, to match the relatively heavier staff lines.
8476 The recommended font sizes are listed in the following table:
8478 @multitable @columnfractions .25 .25 .25 .25
8481 @tab @b{staff height (pt)}
8482 @tab @b{staff height (mm)}
8524 @c modern rental material ?
8528 These fonts are available in any sizes. The context property
8529 @code{fontSize} and the layout property @code{staff-space} (in
8530 @internalsref{StaffSymbol}) can be used to tune size for individual
8531 staffs. The size of individual staffs are relative to the global size,
8532 which can be set in the following manner:
8535 #(set-global-staff-size 14)
8538 This sets the global default size to 14pt staff height, and scales all
8544 @subsection Line breaking
8547 @cindex breaking lines
8549 Line breaks are normally computed automatically. They are chosen such
8550 that lines look neither cramped nor loose, and that consecutive lines
8551 have similar density.
8553 Occasionally you might want to override the automatic breaks; you can
8554 do this by specifying @code{\break}. This will force a line break at
8555 this point. Line breaks can only occur at places where there are bar
8556 lines. If you want to have a line break where there is no bar line,
8557 you can force an invisible bar line by entering @code{\bar
8558 ""}. Similarly, @code{\noBreak} forbids a line break at a
8562 @cindex regular line breaks
8563 @cindex four bar music.
8565 For linebreaks at regular intervals use @code{\break} separated by
8566 skips and repeated with @code{\repeat}:
8568 << \repeat unfold 7 @{
8569 s1 \noBreak s1 \noBreak
8570 s1 \noBreak s1 \break @}
8571 @emph{the real music}
8576 This makes the following 28 measures (assuming 4/4 time) be broken every
8577 4 measures, and only there.
8581 @code{\break}, @code{\noBreak}
8582 @cindex @code{\break}
8583 @cindex @code{\noBreak}
8587 Internals: @internalsref{BreakEvent}.
8591 @subsection Page layout
8594 @cindex breaking pages
8596 @cindex @code{indent}
8597 @cindex @code{linewidth}
8599 The most basic settings influencing the spacing are @code{indent} and
8600 @code{linewidth}. They are set in the @code{\paper} block. They
8601 control the indentation of the first line of music, and the lengths of
8604 If @code{raggedright} is set to true in the @code{\paper}
8605 block, then the lines are justified at their natural length. This
8606 useful for short fragments, and for checking how tight the natural
8610 @cindex vertical spacing
8612 The page layout process happens outside the LilyPond formatting
8613 engine: variables controlling page layout are passed to the output,
8614 and are further interpreted by @code{lilypond} wrapper program. It
8615 responds to the following variables in the @code{\paper} block. The
8616 variable @code{textheight} sets the total height of the music on each
8617 page. The spacing between systems is controlled with
8618 @code{interscoreline}, its default is 16pt. The distance between the
8619 score lines will stretch in order to fill the full page
8620 @code{interscorelinefill} is set to a positive number. In that case
8621 @code{interscoreline} specifies the minimum spacing.
8623 @cindex @code{textheight}
8624 @cindex @code{interscoreline}
8625 @cindex @code{interscorelinefill}
8627 If the variable @code{lastpagefill} is defined,
8628 @c fixme: this should only be done if lastpagefill= #t
8629 systems are evenly distributed vertically on the last page. This
8630 might produce ugly results in case there are not enough systems on the
8631 last page. The @command{lilypond-book} command ignores
8632 @code{lastpagefill}. See @ref{lilypond-book manual} for more
8635 @cindex @code{lastpagefill}
8637 Page breaks are normally computed by @TeX{}, so they are not under
8638 direct control of LilyPond. However, you can insert a commands into
8639 the @file{.tex} output to instruct @TeX{} where to break pages. This
8640 is done by setting the @code{between-systems-strings} on the
8641 @internalsref{NonMusicalPaperColumn} where the system is broken.
8642 An example is shown in @inputfileref{input/regression,between-systems.ly}.
8643 The predefined command @code{\newpage} also does this.
8647 @cindex @code{papersize}
8649 To change the paper size, use the following Scheme code:
8652 #(set-paper-size "a4")
8659 @cindex @code{\newpage}
8665 In this manual: @ref{Invoking lilypond}.
8667 Examples: @inputfileref{input/regression,between-systems.ly}.
8669 Internals: @internalsref{NonMusicalPaperColumn}.
8673 LilyPond has no concept of page layout, which makes it difficult to
8674 reliably choose page breaks in longer pieces.
8683 Entered music can also be converted to MIDI output. The performance
8684 is good enough for proof-hearing the music for errors.
8686 Ties, dynamics and tempo changes are interpreted. Dynamic marks,
8687 crescendi and decrescendi translate into MIDI volume levels. Dynamic
8688 marks translate to a fixed fraction of the available MIDI volume
8689 range, crescendi and decrescendi make the volume vary linearly between
8690 their two extremities. The fractions can be adjusted by
8691 @code{dynamicAbsoluteVolumeFunction} in @internalsref{Voice} context.
8692 For each type of MIDI instrument, a volume range can be defined. This
8693 gives a basic equalizer control, which can enhance the quality of
8694 the MIDI output remarkably. The equalizer can be controlled by
8695 setting @code{instrumentEqualizer}.
8699 Many musically interesting effects, such as swing, articulation,
8700 slurring, etc., are not translated to MIDI.
8702 Since slurs are not interpreted, @code{\lyricsto} and
8703 @code{\addlyrics} sections will be interpreted wrongly.
8705 The MIDI output allocates a channel for each Staff, and one for global
8706 settings. Hence, the MIDI file should not have more than 15 staves
8707 (or 14 if you do not use drums).
8712 * MIDI instrument names::
8717 @subsection MIDI block
8721 The MIDI block is analogous to the paper block, but it is somewhat
8722 simpler. The @code{\midi} block can contain:
8726 @item a @code{\tempo} definition, and
8727 @item context definitions.
8730 Assignments in the @code{\midi} block are not allowed.
8732 A number followed by a period is interpreted as a real number, so
8733 for setting the tempo for dotted notes, an extra space should be
8734 inserted, for example:
8737 \midi @{ \tempo 4 . = 120 @}
8741 @cindex context definition
8743 Context definitions follow precisely the same syntax as within the
8744 \paper block. Translation modules for sound are called performers.
8745 The contexts for MIDI output are defined in @file{ly/performer-init.ly}.
8748 @node MIDI instrument names
8749 @subsection MIDI instrument names
8751 @cindex instrument names
8752 @cindex @code{Staff.midiInstrument}
8754 The MIDI instrument name is set by the @code{Staff.midiInstrument}
8755 property. The instrument name should be chosen from the list in
8756 @ref{MIDI instruments}.
8760 If the selected string does not exactly match, then the default is
8761 used, which is the Grand Piano.