3 @c A menu is needed before every deeper *section nesting of @node's; run
4 @c M-x texinfo-all-menus-update
5 @c to automagically fill in these menus before saving changes
7 @c FIXME: singular vs. plural: Beams/Beam
11 @chapter Notation manual
13 This chapter describes all the different types of notation supported
14 by LilyPond. It is intended as a reference for users that are already
15 somewhat familiar with using LilyPond.
19 * Easier music entry::
33 * Contemporary notation::
39 @c FIXME: Note entry vs Music entry at top level menu is confusing.
45 The basic elements of any piece of music are the notes. This section
46 is about basic notation elements notes, rests and related constructs,
47 such as stems, tuplets and ties.
52 * Chromatic alterations::
60 * Easy Notation note heads ::
68 A note is printed by specifying its pitch and then its duration:
69 @footnote{Notes constitute the most basic elements of LilyPond input,
70 but they do not form valid input on their own without a @code{\score}
71 block. However, for the sake of brevity and simplicity we will
72 generally omit @code{\score} blocks and @code{\paper} declarations in
75 @lilypond[fragment,verbatim]
84 @cindex Note specification
86 @cindex entering notes
88 The most common syntax for pitch entry is used in @code{\chords} and
89 @code{\notes} mode. In Note and Chord mode, pitches may be designated
90 by names. The notes are specified by the letters @code{a} through
91 @code{g}, while the octave is formed with notes ranging from @code{c}
92 to @code{b}. The pitch @code{c} is an octave below middle C and the
93 letters span the octave above that C:
95 @lilypond[fragment,verbatim]
97 a,4 b, c d e f g a b c' d' e' \clef treble f' g' a' b' c''
100 @cindex note names, Dutch
102 A sharp is formed by adding @code{-is} to the end of a pitch name and
103 a flat is formed by adding @code{-es}. Double sharps and double flats
104 are obtained by adding @code{-isis} or @code{-eses}. These
105 names are the Dutch note names. In Dutch, @code{aes} is contracted to
106 @code{as}, but both forms are accepted. Similarly, both
107 @code{es} and @code{ees} are accepted.
109 Half-flats and half-sharps are formed by adding @code{-eh} and
110 @code{-ih}; the following is a series of Cs with increasing pitches:
112 @cindex quarter tones
113 @cindex semi-flats, semi-sharps
115 @lilypond[verbatim,relative 2]
127 There are predefined sets of note names for various other languages.
128 To use them, include the language specific init file. For
129 example: @code{\include "english.ly"}. The available language files
130 and the note names they define are:
135 Note Names sharp flat
136 nederlands.ly c d e f g a bes b -is -es
137 english.ly c d e f g a bf b -s/-sharp -f/-flat
139 deutsch.ly c d e f g a b h -is -es
140 norsk.ly c d e f g a b h -iss/-is -ess/-es
141 svenska.ly c d e f g a b h -iss -ess
142 italiano.ly do re mi fa sol la sib si -d -b
143 catalan.ly do re mi fa sol la sib si -d/-s -b
144 espanol.ly do re mi fa sol la sib si -s -b
153 The optional octave specification takes the form of a series of
154 single quote (`@code{'}') characters or a series of comma
155 (`@code{,}') characters. Each @code{'} raises the pitch by one
156 octave; each @code{,} lowers the pitch by an octave:
158 @lilypond[fragment,verbatim,center]
159 c' c'' es' g' as' gisis' ais'
165 Notes can be hidden and unhidden with the following commands:
167 @cindex @code{\hideNotes}
169 @cindex @code{\unHideNotes}
179 @internalsref{NoteEvent}, and @internalsref{NoteHead}.
181 @node Chromatic alterations
182 @subsection Chromatic alterations
184 Normally accidentals are printed automatically, but you may also
185 print them manually. A reminder accidental
186 @cindex reminder accidental
188 can be forced by adding an exclamation mark @code{!}
189 after the pitch. A cautionary accidental
190 @cindex cautionary accidental
191 @cindex parenthesized accidental
192 (an accidental within parentheses) can be obtained by adding the
193 question mark `@code{?}' after the pitch:
195 @lilypond[fragment,verbatim]
196 cis' cis' cis'! cis'?
200 The automatic production of accidentals can be tuned in many
201 ways. For more information, refer to @ref{Accidentals}.
206 A chord is formed by a enclosing a set of pitches in @code{<} and
207 @code{>}. A chord may be followed by a duration, and a set of
208 articulations, just like simple notes.
218 Rests are entered like notes, with the note name @code{r}:
220 @lilypond[singleline,verbatim]
224 Whole bar rests, centered in middle of the bar,
225 must be done with multi measure rests. They are discussed in
226 @ref{Multi measure rests}.
229 A rest's vertical position may be explicitly specified by entering a
230 note with the @code{\rest} keyword appended. This makes manual
231 formatting in polyphonic music easier. Rest collision testing will
232 leave these rests alone:
234 @lilypond[singleline,verbatim]
240 @internalsref{RestEvent}, and @internalsref{Rest}.
247 @cindex Invisible rest
250 An invisible rest (also called a `skip') can be entered like a note
251 with note name `@code{s}' or with @code{\skip @var{duration}}:
253 @lilypond[singleline,verbatim]
257 The @code{s} syntax is only available in Note mode and Chord mode. In
258 other situations, you should use the @code{\skip} command:
260 @lilypond[singleline,verbatim]
263 { \time 4/8 \skip 2 \time 4/4 }
264 \notes\relative c'' { a2 a1 }
269 The skip command is merely an empty musical placeholder. It does not
270 produce any output, not even transparent output.
274 @internalsref{SkipEvent}.
279 @subsection Durations
285 In Note, Chord, and Lyrics mode, durations are designated by numbers
286 and dots: durations are entered as their reciprocal values. For example,
287 a quarter note is entered using a @code{4} (since it is a 1/4 note), while
288 a half note is entered using a @code{2} (since it is a 1/2 note). For notes
289 longer than a whole you must use variables:
291 @c FIXME: what is an identifier? I do not think it's been introduced yet.
292 @c and if it has, I obviously skipped that part. - Graham
296 c'1 c'2 c'4 c'8 c'16 c'32 c'64 c'64
298 r1 r2 r4 r8 r16 r32 r64 r64
303 \notes \relative c'' {
305 a1 a2 a4 a8 a16 a32 a64 a64
307 r1 r2 r4 r8 r16 r32 r64 r64
312 \remove "Clef_engraver"
313 \remove "Staff_symbol_engraver"
314 \remove "Time_signature_engraver"
315 \consists "Pitch_squash_engraver"
322 If the duration is omitted then it is set to the previously entered
323 duration. The default for the first note is a quarter note. The duration
324 can be followed by dots (`@code{.}') in order to obtain dotted note
328 @lilypond[fragment,verbatim,center]
329 a' b' c''8 b' a'4 a'4. b'4.. c'8.
334 You can alter the length of duration by a fraction @var{N/M}
335 appending `@code{*}@var{N/M}' (or `@code{*}@var{N}' if @var{M=1}). This
336 will not affect the appearance of the notes or rests produced.
337 In the following example, the first three notes take up exactly two
339 @lilypond[fragment,relative 2,verbatim]
341 a4*2/3 gis4*2/3 a4*2/3
348 Dots are normally moved up to avoid staff lines, except in polyphonic
349 situations. The following commands may be used to force a particular
352 @cindex @code{\dotsUp}
354 @cindex @code{\dotsDown}
356 @cindex @code{\dotsBoth}
361 @internalsref{Dots}, and @internalsref{DotColumn}.
365 In dense chords, dots can overlap.
370 Whenever a note is found, a @internalsref{Stem} object is created
371 automatically. For whole notes and rests, they are also created but
376 @cindex @code{\stemUp}
378 @cindex @code{\stemDown}
380 @cindex @code{\stemBoth}
391 A tie connects two adjacent note heads of the same pitch. The tie in
392 effect extends the length of a note. Ties should not be confused with
393 slurs, which indicate articulation, or phrasing slurs, which indicate
394 musical phrasing. A tie is entered using the tilde symbol `@code{~}':
396 @lilypond[fragment,verbatim,center]
397 e' ~ e' <c' e' g'> ~ <c' e' g'>
400 When a tie is applied to a chord, all note heads whose pitches match
401 are connected. When no note heads match, no ties will be created.
403 In its meaning a tie is just a way of extending a note duration, similar
404 to the augmentation dot; in the following example there are two ways of
405 notating exactly the same concept:
407 @lilypond[fragment, singleline,quote]
408 \time 3/4 c'2. c'2 ~ c'4
410 If you need to tie a lot of notes over bars, it may be easier to use automatic
411 note splitting (See @ref{Automatic note splitting}).
416 @cindex @code{\tieUp}
418 @cindex @code{\tieDown}
420 @cindex @code{\tieBoth}
422 @cindex @code{\tieDotted}
424 @cindex @code{\tieSolid}
429 @internalsref{TieEvent}, @internalsref{NewTieEvent},
430 @internalsref{Tie}, and @ref{Automatic note splitting}.
433 ties created for a chord, see @inputfileref{input/test,tie-sparse.ly}.
437 Tieing only a subset of the note heads of a pair of chords is not
438 supported in a simple way.
441 It can be achieved by moving the
442 tie-engraver into the @internalsref{Thread} context and turning on and
443 off ties per @internalsref{Thread}.
446 Switching staves when a tie is active will not produce a slanted tie.
448 Formatting of ties is a difficult subject. The results are often not
458 @cindex @code{\times}
460 Tuplets are made out of a music expression by multiplying all durations
463 @cindex @code{\times}
465 \times @var{fraction} @var{musicexpr}
469 The duration of @var{musicexpr} will be multiplied by the fraction.
470 The fraction's denominator will be printed over the notes, optionally
471 with a bracket. The most common tuplet is the triplet in which 3
472 notes have the length of 2, so the notes are 2/3 of their written
475 @lilypond[fragment,verbatim,center]
476 g'4 \times 2/3 {c'4 c' c'} d'4 d'4
479 The property @code{tupletSpannerDuration} specifies how long each
480 bracket should last. With this, you can make lots of tuplets while
481 typing @code{\times} only once, saving lots of typing. In the next
482 example, there are two triplets shown, while @code{\times} was only
485 @lilypond[fragment, relative, singleline, verbatim]
486 \property Voice.tupletSpannerDuration = #(ly:make-moment 1 4)
487 \times 2/3 { c'8 c c c c c }
490 The format of the number is determined by the property
491 @code{tupletNumberFormatFunction}. The default prints only the
492 denominator, but if it is set to the Scheme function
493 @code{fraction-tuplet-formatter}, @var{num}:@var{den} will be printed
497 @cindex @code{tupletNumberFormatFunction}
498 @cindex tuplet formatting
503 @cindex @code{\tupletUp}
505 @cindex @code{\tupletDown}
507 @cindex @code{\tupletBoth}
512 @internalsref{TupletBracket}, and @internalsref{TimeScaledMusic}.
516 Nested tuplets are not formatted automatically. In this case, outer
517 tuplet brackets should be moved manually.
519 @node Easy Notation note heads
520 @subsection Easy Notation note heads
522 @cindex easy notation
525 The `easy play' note head includes a note name inside the head. It is
526 used in music aimed at beginners:
528 @lilypond[singleline,verbatim,26pt]
530 \notes { c'2 e'4 f' | g'1 }
531 \paper { \translator { \EasyNotation } }
535 The @code{EasyNotation} variable overrides a @internalsref{Score} context.
536 You probably will want to print it with magnification or a
537 large font size to make it more readable. To print with
538 magnification, you must create a DVI file (with @file{lilypond}) and
539 then enlarge it with something like @file{dvips -x 2000 file.dvi}.
540 See the @code{dvips} documentation for more details. To print with a
541 larger font, see @ref{Font Size}.
547 If you view the result with Xdvi, then staff lines will show through
548 the letters. Printing the PostScript file obtained does produce the
552 @node Easier music entry
553 @section Easier music entry
556 When entering music it is easy to introduce errors. This section deals
557 with tricks and features of the input language that were added solely
558 to help entering music, and find and correct mistakes.
560 It is also possible to use external programs, for example GUI
561 interfaces, or MIDI transcription programs, to enter or edit
562 music. Refer to the website for more information. Finally, there are
563 tools make debugging easier, by linking the input file and the output
564 shown on screen. See @ref{Point and click} for more information.
571 * Skipping corrected music::
572 * Automatic note splitting ::
578 @node Relative octaves
579 @subsection Relative octaves
581 @cindex relative octave specification
583 Octaves are specified by adding @code{'} and @code{,} to pitch names.
584 When you copy existing music, it is easy to accidentally put a pitch
585 in the wrong octave and hard to find such an error. The relative
586 octave mode prevents these errors: a single error puts the rest of the
587 piece off by one octave:
589 @cindex @code{\relative}
591 \relative @var{startpitch} @var{musicexpr}
594 The octave of notes that appear in @var{musicexpr} are calculated as
595 follows: If no octave changing marks are used, the basic interval
596 between this and the last note is always taken to be a fourth or less
597 (; this distance is determined without regarding alterations: a
598 @code{fisis} following a @code{ceses} will be put above the
601 The octave changing marks @code{'} and @code{,} can be added to raise
602 or lower the pitch by an extra octave. Upon entering relative mode,
603 an absolute starting pitch must be specified that will act as the
604 predecessor of the first note of @var{musicexpr}.
606 Here is the relative mode shown in action:
607 @lilypond[fragment,singleline,verbatim,center]
613 Octave changing marks are used for intervals greater than a fourth:
614 @lilypond[fragment,verbatim,center]
619 If the preceding item is a chord, the first note of the chord is used
620 to determine the first note of the next chord:
622 @lilypond[fragment,verbatim,center]
629 @cindex @code{\notes}
631 The pitch after the @code{\relative} contains a note name. To parse
632 the pitch as a note name, you have to be in note mode, so there must
633 be a surrounding @code{\notes} keyword (which is not
636 The relative conversion will not affect @code{\transpose},
637 @code{\chords} or @code{\relative} sections in its argument. If you
638 want to use relative within transposed music, you must place an
639 additional @code{\relative} inside the @code{\transpose}.
642 @subsection Octave check
645 Octave checks make octave errors easier to correct.
651 This checks that @var{pitch} (without octave) yields @var{pitch} (with
652 octave) in \relative mode. If not, a warning is printed, and the
653 octave is corrected, for example, the first check is passed
654 successfully. The second check fails with an error message. The
655 octave is adjusted so the following notes are in the correct octave
666 The octave of a note following an octave check is determined with
667 respect to the note preceding it. In the next fragment, the last note
668 is a @code{a'}, above central C. Hence, the @code{\octave} check may
669 be deleted without changing the meaning of the piece.
671 @lilypond[verbatim,fragment]
682 @subsection Bar check
686 @cindex @code{barCheckSynchronize}
689 Bar checks help detect errors in the durations. A bar check is
690 entered using the bar symbol, `@code{|}'. Whenever it is encountered
691 during interpretation, it should fall on a measure boundary. If it
692 does not, a warning is printed. Depending on the value of
693 @code{barCheckSynchronize}, the beginning of the measure will be
696 In the next example, the second bar check will signal an error:
698 \time 3/4 c2 e4 | g2 |
703 @cindex skipTypesetting
705 Failed bar checks are caused by entering incorrect
706 durations. Incorrect durations often completely garble up the score,
707 especially if it is polyphonic, so you should start correcting the
708 score by scanning for failed bar checks and incorrect durations. To
709 speed up this process, you can use @code{skipTypesetting}, described
712 @node Skipping corrected music
713 @subsection Skipping corrected music
715 The property @code{Score.skipTypesetting} can be used to switch on and
716 off typesetting completely during the interpretation phase. When
717 typesetting is switched off, the music is processed much more quickly.
718 This can be used to skip over the parts of a score that have already
719 been checked for errors:
721 @lilypond[fragment,singleline,verbatim]
723 \property Score.skipTypesetting = ##t
725 \property Score.skipTypesetting = ##f
729 @node Automatic note splitting
730 @subsection Automatic note splitting
732 Long notes can be converted automatically to tied notes. This is done
733 by replacing the @internalsref{Note_heads_engraver} by the
734 @internalsref{Completion_heads_engraver}:
737 \paper @{ \translator @{
739 \remove "Note_heads_engraver"
740 \consists "Completion_heads_engraver"
744 which will make long notes tied in the following example:
747 c2. c8 d4 e f g a b c8 c2 b4 a g16 f4 e d c8. c2
754 c2. c8 d4 e f g a b c8 c2 b4 a g16 f4 e d c8. c2
756 \paper { \translator {
758 \remove "Note_heads_engraver"
759 \consists "Completion_heads_engraver"
764 This engraver splits all running notes at the bar line, and inserts
765 ties. One of its uses is to debug complex scores: if the measures are
766 not entirely filled, then the ties exactly show how much each measure
771 Not all durations (especially those containing tuplets) can be
772 represented exactly; the engraver will not insert tuplets.
778 @section Staff notation
780 This section describes music notation that occurs on staff level,
781 such as keys, clefs and time signatures.
783 @cindex Staff notation
797 @subsection Staff symbol
799 @cindex adjusting staff symbol
800 @cindex StaffSymbol, using \property
802 Notes, dynamic signs, etc. are grouped
803 with a set of horizontal lines, into a staff (plural `staves'). In our
804 system, these lines are drawn using a separate layout object called
808 @cindex staff lines, setting number of
809 @cindex staff lines, setting thickness of
810 @cindex thickness of staff lines, setting
811 @cindex number of staff lines, setting
813 This object is created whenever a @internalsref{Staff} context is
814 created. The appearance of the staff symbol cannot be changed by
815 using @code{\override} or @code{\set}. At the moment that
816 @code{\property Staff} is interpreted, a @internalsref{Staff} context
817 is made, and the @internalsref{StaffSymbol} is created before any
818 @code{\override} is effective. Properties can be changed in a
819 @code{\translator} definition, or by using @code{\applyoutput}.
823 If a staff is ended halfway a piece, the staff symbol may not end
824 exactly on the barline.
828 @subsection Key signature
829 @cindex Key signature
833 The key signature indicates the scale in which a piece is played. It
834 is denoted by a set of alterations (flats or sharps) at the start of
839 Setting or changing the key signature is done with the @code{\key}
842 @code{\key} @var{pitch} @var{type}
845 @cindex @code{\minor}
846 @cindex @code{\major}
847 @cindex @code{\minor}
848 @cindex @code{\ionian}
849 @cindex @code{\locrian}
850 @cindex @code{\aeolian}
851 @cindex @code{\mixolydian}
852 @cindex @code{\lydian}
853 @cindex @code{\phrygian}
854 @cindex @code{\dorian}
856 Here, @var{type} should be @code{\major} or @code{\minor} to get
857 @var{pitch}-major or @var{pitch}-minor, respectively.
858 The standard mode names @code{\ionian},
859 @code{\locrian}, @code{\aeolian}, @code{\mixolydian}, @code{\lydian},
860 @code{\phrygian}, and @code{\dorian} are also defined.
862 This command sets the context property
863 @internalsref{Staff}.@code{keySignature}. Non-standard key signatures
864 can be specified by setting this property directly.
866 Accidentals and key signatures often confuse new users, because
867 unaltered notes get natural signs depending on the keysignature. The
868 tutorial explains why this is so in @ref{More about pitches}.
872 The ordering of a key cancellation is wrong when it is combined with
873 repeat bar lines. The cancellation is also printed after a line break.
877 @internalsref{KeyChangeEvent}, and @internalsref{KeySignature}.
879 @cindex @code{keySignature}
886 The clef indicates which lines of the staff correspond to which
891 The clef can be set or changed with the @code{\clef} command:
892 @lilypond[fragment,verbatim]
893 \key f\major c''2 \clef alto g'2
896 Supported clef-names include:
897 @c Moved standard clefs to the top /MB
901 @item treble, violin, G, G2
914 G clef on 1st line, so-called French violin clef
919 @cindex mezzosoprano clef
922 @cindex baritone clef
925 @cindex varbaritone clef
934 By adding @code{_8} or @code{^8} to the clef name, the clef is
935 transposed one octave down or up, respectively, and @code{_15} and
936 @code{^15} transposes by two octaves. The argument @var{clefname}
937 must be enclosed in quotes when it contains underscores or digits. For
941 @cindex choral tenor clef
942 @lilypond[verbatim,fragment,relative]
946 This command is equivalent to setting @code{clefGlyph},
947 @code{clefPosition} (which controls the Y position of the clef),
948 @code{centralCPosition} and @code{clefOctavation}. A clef is printed
949 when any of these properties are changed.
953 The object for this symbol is @internalsref{Clef}.
957 @node Ottava brackets
958 @subsection Ottava brackets
960 ``Ottava'' brackets introduce an extra transposition of an octave for
961 the staff. They are created by invoking the function
962 @code{set-octavation}:
968 @lilypond[verbatim,fragment]
977 Internally the @code{set-octavation} function sets the properties
978 @code{ottavation} (eg. to @code{"8va"}) and
979 @code{centralCPosition}. The function also takes arguments -1 (for 8va
980 bassa) and 2 (for 15ma).
982 @internalsref{OttavaSpanner}.
986 @code{set-octavation} will get confused when clef changes happen
987 during an octavation bracket.
990 @subsection Time signature
991 @cindex Time signature
995 Time signature indicates the metrum of a piece: a regular pattern of
996 strong and weak beats. It is denoted by a fraction at the start of the
1001 The time signature is set or changed by the @code{\time}
1003 @lilypond[fragment,verbatim]
1004 \time 2/4 c'2 \time 3/4 c'2.
1007 The symbol that is printed can be customized with the @code{style}
1008 property. Setting it to @code{#'()} uses fraction style for 4/4 and
1009 2/2 time. There are many more options for its layout. See
1010 @inputfileref{input/test,time.ly} for more examples.
1013 This command sets the property @code{timeSignatureFraction},
1014 @code{beatLength} and @code{measureLength} in the @code{Timing}
1015 context, which is normally aliased to @internalsref{Score}. The
1016 property @code{measureLength} determines where bar lines should be
1017 inserted, and how automatic beams should be generated. Changing the
1018 value of @code{timeSignatureFraction} also causes the symbol to be
1021 More options are available through the Scheme function
1022 @code{set-time-signature}. In combination with the
1023 @internalsref{Measure_grouping_engraver}, it will create
1024 @internalsref{MeasureGrouping} signs. Such signs ease reading
1025 rhythmically complex modern music. In the following example, the 9/8
1026 measure is subdivided in 2, 2, 2 and 3. This is passed to
1027 @code{set-time-signature} as the third argument @code{(2 2 2 3)}:
1030 \score { \notes \relative c'' {
1031 #(set-time-signature 9 8 '(2 2 2 3))
1032 g8[ g] d[ d] g[ g] a8[( bes g]) |
1033 #(set-time-signature 5 8 '(3 2))
1038 \translator { \StaffContext
1039 \consists "Measure_grouping_engraver"
1045 @internalsref{TimeSignature}, and @internalsref{Timing_engraver}.
1050 Automatic beaming does not use measure grouping specified with
1051 @code{set-time-signature}.
1053 @node Partial measures
1054 @subsection Partial measures
1057 @cindex partial measure
1058 @cindex measure, partial
1059 @cindex shorten measures
1060 @cindex @code{\partial}
1062 Partial measures, for example in upsteps, are entered using the
1063 @code{\partial} command:
1064 @lilypond[fragment,verbatim,relative 1]
1065 \partial 16*5 c16 cis d dis e | a2. c,4 | b2
1068 The syntax for this command is
1070 \partial @var{duration}
1072 This is internally translated into
1074 \property Timing.measurePosition = -@var{length of duration}
1077 The property @code{measurePosition} contains a rational number
1078 indicating how much of the measure has passed at this point.
1080 @node Unmetered music
1081 @subsection Unmetered music
1083 Bar lines and bar numbers are calculated automatically. For unmetered
1084 music (e.g. cadenzas), this is not desirable. By setting
1085 @code{Score.timing} to false, this automatic timing can be switched
1091 @cindex @code{\cadenzaOn}
1093 @cindex @code{\cadenzaOff}
1097 @subsection Bar lines
1101 @cindex measure lines
1105 Bar lines delimit measures, but are also used to indicate repeats.
1106 Normally, they are inserted automatically. Line breaks may only
1112 of barlines can be forced with the @code{\bar} command:
1114 @lilypond[relative=1,fragment,verbatim]
1118 The following bar types are available:
1119 @lilypond[fragment, relative, singleline, verbatim]
1130 For allowing linebreaks, there is a special command,
1134 This will insert an invisible barline, and allow linebreaks at this
1137 In scores with many staves, a @code{\bar} command in one staff is
1138 automatically applied to all staves. The resulting bar lines are
1139 connected between different staves of a @internalsref{StaffGroup}:
1141 @lilypond[fragment, verbatim]
1142 << \context StaffGroup <<
1146 \new Staff { \clef bass c4 g e g } >>
1147 \new Staff { \clef bass c2 c2 } >>
1151 The command @code{\bar @var{bartype}} is a short cut for doing
1152 @code{\property Score.whichBar = @var{bartype}} Whenever
1153 @code{whichBar} is set to a string, a bar line of that type is
1154 created. At the start of a measure it is set to
1155 @code{defaultBarType}. The contents of @code{repeatCommands} are used
1156 to override default measure bars.
1158 Property @code{whichBar} can also be set directly, using @code{\property}
1159 or @code{\bar}. These settings take precedence over the automatic
1160 @code{whichBar} settings.
1163 @cindex repeatCommands
1164 @cindex defaultBarType
1166 You are encouraged to use @code{\repeat} for repetitions. See
1176 The bar line objects that are created at @internalsref{Staff} level
1177 are called @internalsref{BarLine}, the bar lines that span staves are
1178 @internalsref{SpanBar}s.
1180 @cindex bar lines at start of system
1181 @cindex start of system
1183 The barlines at the start of each system are
1184 @internalsref{SystemStartBar}, @internalsref{SystemStartBrace}, and
1185 @internalsref{SystemStartBracket}. They are spanner objects and
1186 typically must be tuned from a @code{\translator} block.
1193 The easiest way to enter fragments with more than one voice on a staff
1194 is to split chords using the separator @code{\\}. You can use it for
1195 small, short-lived voices or for single chords:
1197 @lilypond[verbatim,fragment]
1198 \context Staff \relative c'' {
1199 c4 << { f d e } \\ { b c2 } >>
1200 c4 << g' \\ b, \\ f' \\ d >>
1204 The separator causes @internalsref{Voice} contexts to be
1206 bear the names @code{"1"}, @code{"2"}, etc. In each of these
1207 contexts, vertical direction of slurs, stems, etc. is set
1210 This can also be done by instantiating @internalsref{Voice} contexts
1211 by hand, and using @code{\voiceOne}, up to @code{\voiceFour} to assign
1212 a stem directions and horizontal shift for each part:
1215 @lilypond[singleline, verbatim]
1217 \context Staff << \new Voice { \voiceOne cis2 b }
1218 \new Voice { \voiceThree b4 ais ~ ais4 gis4 }
1219 \new Voice { \voiceTwo fis4~ fis4 f ~ f } >>
1222 Normally, note heads with a different number of dots are not merged, but
1223 when the object property @code{merge-differently-dotted} is set in
1224 the @internalsref{NoteCollision} object, they are merged:
1225 @lilypond[verbatim,fragment,singleline]
1226 \relative c'' \context Voice << {
1228 \property Staff.NoteCollision \override
1229 #'merge-differently-dotted = ##t
1231 } \\ { g8.[ f16] g8.[ f16] }
1235 Similarly, you can merge half note heads with eighth notes, by setting
1236 @code{merge-differently-headed}:
1237 @lilypond[fragment, relative=2,verbatim]
1240 \property Staff.NoteCollision
1241 \override #'merge-differently-headed = ##t
1242 c8 c4. } \\ { c2 c2 } >>
1245 LilyPond also vertically shifts rests that are opposite of a stem:
1248 @lilypond[singleline,fragment,verbatim]
1249 \context Voice << c''4 \\ r4 >>
1257 @cindex @code{\oneVoice}
1259 @cindex @code{\voiceOne}
1261 @cindex @code{\voiceTwo}
1263 @cindex @code{\voiceThree}
1265 @cindex @code{\voiceFour}
1268 The following commands specify in what chords of the current voice
1269 should be shifted: the outer voice has @code{\shiftOff}, and the inner
1270 voices have @code{\shiftOn}, @code{\shiftOnn}, etc.
1273 @cindex @code{\shiftOn}
1275 @cindex @code{\shiftOnn}
1277 @cindex @code{\shiftOnnn}
1279 @cindex @code{\shiftOff}
1286 The objects responsible for resolving collisions are
1287 @internalsref{NoteCollision} and @internalsref{RestCollision}. See
1288 also example files @inputfileref{input/regression,collision-dots.ly},
1289 @inputfileref{input/regression,collision-head-chords.ly},
1290 @inputfileref{input/regression,collision-heads.ly},
1291 @inputfileref{input/regression,collision-mesh.ly}, and
1292 @inputfileref{input/regression,collisions.ly}.
1297 Resolving collisions is a intricate subject, and only a few situations
1298 are handled. When LilyPond cannot cope, the @code{force-hshift}
1299 property of the @internalsref{NoteColumn} object and pitched rests can
1300 be used to override typesetting decisions.
1302 When using @code{merge-differently-headed} with an upstem 8th or a shorter
1303 note, and a downstem half note, the 8th note gets the wrong offset.
1308 Beams are used to group short notes into chunks that are aligned with
1309 the metrum. They are inserted automatically in most cases:
1311 @lilypond[fragment,verbatim, relative=2]
1312 \time 2/4 c8 c c c \time 6/8 c c c c8. c16 c8
1315 When these automatic decisions are not good enough, beaming can be
1316 entered explicitly. It is also possible to define beaming patterns
1317 that differ from the defaults.
1321 @internalsref{Beam}.
1324 @cindex Automatic beams
1325 @subsection Manual beams
1326 @cindex beams, manual
1330 In some cases it may be necessary to override the automatic beaming
1331 algorithm. For example, the auto beamer will not put beams over rests
1332 or bar lines. Such beams are specified by manually: the begin and end
1333 point are marked with @code{[} and @code{]}:
1335 @lilypond[fragment,relative,verbatim]
1337 r4 r8[ g' a r8] r8 g[ | a] r8
1341 @cindex @code{stemLeftBeamCount}
1343 Normally, beaming patterns within a beam are determined automatically.
1344 When this mechanism fouls up, the properties
1345 @code{Voice.stemLeftBeamCount} and @code{Voice.stemRightBeamCount} can
1346 be used to control the beam subdivision on a stem. If either property
1347 is set, its value will be used only once, and then it is erased.
1349 @lilypond[fragment,relative,verbatim]
1352 f8[ r16 \property Voice.stemLeftBeamCount = #1 f g a]
1355 @cindex @code{stemRightBeamCount}
1358 The property @code{subdivideBeams} can be set in order to subdivide
1359 all 16th or shorter beams at beat positions, as defined by the
1360 @code{beatLength} property . This accomplishes the same effect as
1361 twiddling with @code{stemLeftBeamCount} and @code{stemRightBeamCount},
1362 but it take less typing:
1365 @lilypond[relative=1,verbatim,noindent]
1367 \property Voice.subdivideBeams = ##t
1369 \property Score.beatLength = #(ly:make-moment 1 8)
1372 @cindex subdivideBeams
1374 Kneed beams are inserted automatically, when a large gap is detected
1375 between the note heads. This behavior can be tuned through the object
1376 property @code{auto-knee-gap}.
1378 Normally, line breaks are forbidden when beams cross bar lines. This
1379 behavior can be changed by setting @code{allowBeamBreak}.
1381 @cindex @code{allowBeamBreak}
1382 @cindex beams and line breaks
1384 @cindex beams, kneed
1386 @cindex auto-knee-gap
1392 @cindex Frenched staves
1394 Automatically kneed beams cannot be used together with hidden staves.
1399 * Setting automatic beam behavior ::
1403 @no de Beam typography
1404 @sub section Beam typography
1406 One of the strong points of LilyPond is how beams are formatted. Beams
1407 are quantized, meaning that the left and right endpoints beams start
1408 exactly on staff lines. Without quantization, small wedges of white
1409 space appear between the beam and staff line, and this looks untidy.
1411 Beams are also slope-damped: melodies that go up or down should also
1412 have beams that go up or down, but the slope of the beams should be
1413 less than the slope of the notes themselves.
1415 Some beams should be horizontal. These are so-called concave beams.
1417 [TODO: some pictures.]
1421 @node Setting automatic beam behavior
1422 @subsection Setting automatic beam behavior
1424 @cindex @code{autoBeamSettings}
1425 @cindex @code{(end * * * *)}
1426 @cindex @code{(begin * * * *)}
1427 @cindex automatic beams, tuning
1428 @cindex tuning automatic beaming
1430 @c [TODO: use \applycontext]
1432 In normal time signatures, automatic beams can start on any note but can
1433 only end in a few positions within the measure: beams can end on a beat,
1434 or at durations specified by the properties in
1435 @code{Voice.autoBeamSettings}. The defaults for @code{autoBeamSettings}
1436 are defined in @file{scm/auto-beam.scm}.
1438 The value of @code{autoBeamSettings} is changed using
1439 @code{\override} and restored with @code{\revert}:
1441 \property Voice.autoBeamSettings \override #'(@var{BE} @var{P} @var{Q} @var{N} @var{M}) = @var{dur}
1442 \property Voice.autoBeamSettings \revert #'(@var{BE} @var{P} @var{Q} @var{N} @var{M})
1444 Here, @var{BE} is the symbol @code{begin} or @code{end}. It determines
1445 whether the rule applies to begin or end-points. The quantity
1446 @var{P}/@var{Q} refers to the length of the beamed notes (and `@code{*
1447 *}' designates notes of any length), @var{N}/@var{M} refers to a time
1448 signature (wildcards, `@code{* *}' may be entered to designate all time
1451 For example, if automatic beams should end on every quarter note, use
1454 \property Voice.autoBeamSettings \override
1455 #'(end * * * *) = #(ly:make-moment 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 \property Voice.autoBeamSettings \override
1464 #'(end * * * *) = #(ly:make-moment 3 8)
1466 In 4/4 time signature, this means that automatic beams could end only on
1467 3/8 and on the fourth beat of the measure (after 3/4, that is 2 times
1468 3/8 has passed within the measure).
1470 Rules can also be restricted to specific time signatures. A rule that
1471 should only be applied in @var{N}/@var{M} time signature is formed by
1472 replacing the second asterisks by @var{N} and @var{M}. For example, a
1473 rule for 6/8 time exclusively looks like
1475 \property Voice.autoBeamSettings \override
1476 #'(begin * * 6 8) = ...
1479 If a rule should be to applied only to certain types of beams, use the
1480 first pair of asterisks. Beams are classified according to the
1481 shortest note they contain. For a beam ending rule that only applies
1482 to beams with 32nd notes (and no shorter notes), use @code{(end 1 32 *
1485 If a score ends while an automatic beam has not been ended and is still
1486 accepting notes, this last beam will not be typeset at all.
1488 @cindex automatic beam generation
1490 @cindex @code{Voice.autoBeaming}
1493 For melodies that have lyrics, you may want to switch off
1494 automatic beaming. This is done by setting @code{Voice.autoBeaming} to
1499 @cindex @code{\autoBeamOff}
1500 @code{\autoBeamOff},
1501 @cindex @code{\autoBeamOn}
1507 The rules for ending a beam depend on the shortest note in a beam.
1508 So, while it is possible to have different ending rules for eight
1509 beams and sixteenth beams, a beam that contains both eight and
1510 sixteenth notes will use the rules for the sixteenth beam.
1512 In the example below, the autobeamer makes eight beams and sixteenth
1513 end at 3 eights; the third beam can only be corrected by specifying
1516 @lilypond[singleline,fragment,relative,noverbatim,quote]
1517 \property Voice.autoBeamSettings
1518 \override #'(end * * * *) = #(ly:make-moment 3 8)
1519 % rather show case where it goes wrong
1520 %\time 12/8 c'8 c c c16 c c c c c c[ c c c] c8[ c] c4
1521 \time 12/8 c'8 c c c16 c c c c c c c c c c8 c c4
1523 It is not possible to specify beaming parameters that act differently in
1524 different parts of a measure. This means that it is not possible to use
1525 automatic beaming in irregular meters such as @code{5/8}.
1528 @section Accidentals
1531 This section describes how to change the way that accidentals are
1532 inserted automatically before the running notes.
1536 * Using the predefined accidental variables::
1537 * Customized accidental rules::
1540 @node Using the predefined accidental variables
1541 @subsection Using the predefined accidental variables
1543 The constructs for describing the accidental typesetting rules are
1544 quite hairy, so non-experts should stick to the variables
1545 defined in @file{ly/property-init.ly}.
1546 @cindex @file{property-init.ly}
1548 The variables set properties in the ``@code{Current}'' context (see
1549 @ref{Context properties}). This means that the variables should
1550 normally be added right after the creation of the context in which the
1551 accidental typesetting described by the variable is to take
1552 effect. For example, if you want to use piano-accidentals in a piano
1553 staff then issue @code{\pianoAccidentals} first thing after the
1554 creation of the piano staff:
1557 \notes \relative c'' <<
1558 \new Staff @{ cis4 d e2 @}
1559 \context GrandStaff <<
1561 \new Staff @{ cis4 d e2 @}
1562 \new Staff @{ es2 c @}
1564 \new Staff @{ es2 c @}
1568 @lilypond[singleline]
1570 \notes \relative c'' <<
1571 \new Staff { cis4 d e2 }
1572 \context GrandStaff <<
1574 \new Staff { cis4 d e2 }
1575 \new Staff { es2 c }
1577 \new Staff { es2 c }
1582 minimumVerticalExtent = #'(-4.0 . 4.0)
1590 @item \defaultAccidentals
1591 @cindex @code{\defaultAccidentals}
1592 This is the default typesetting behaviour. It should correspond
1593 to 18th century common practice: Accidentals are
1594 remembered to the end of the measure in which they occur and
1595 only on their own octave.
1597 @item \voiceAccidentals
1598 @cindex @code{\voiceAccidentals}
1600 The normal behaviour is to
1601 remember the accidentals on Staff-level. This variable, however,
1602 typesets accidentals individually for each voice. Apart from that the
1603 rule is similar to @code{\defaultAccidentals}.
1605 This leads to some weird and often unwanted results
1606 because accidentals from one voice do not get cancelled in other
1608 @lilypond[singleline,relative,fragment,verbatim,quote]
1616 Hence you should only use @code{\voiceAccidentals} if the voices
1617 are to be read solely by individual musicians. If the staff is to be
1618 used by one musician (e.g. a conductor) then you use
1619 @code{\modernVoiceAccidentals} or @code{\modernVoiceCautionaries}
1622 @item \modernAccidentals
1623 @cindex @code{\modernAccidentals}
1624 This rule corresponds to the common practice in the 20th
1626 The rule is more complex than @code{\defaultAccidentals}.
1627 You get all the same accidentals, but temporary
1628 accidentals also get cancelled in other octaves. Furthermore,
1629 in the same octave, they also get cancelled in the following measure:
1630 @lilypond[singleline,fragment,verbatim]
1632 cis' c'' cis'2 | c'' c'
1635 @item \modernCautionaries
1636 @cindex @code{\modernCautionaries}
1637 This rule is similar to @code{\modernAccidentals}, but the
1638 ``extra'' accidentals (the ones not typeset by
1639 @code{\defaultAccidentals}) are typeset as cautionary accidentals.
1640 They are printed in reduced size or with parentheses:
1641 @lilypond[singleline,fragment,verbatim]
1643 cis' c'' cis'2 | c'' c'
1646 @cindex @code{\modernVoiceAccidentals}
1647 @item \modernVoiceAccidentals
1648 is used for multivoice accidentals to be read both by musicians
1649 playing one voice and musicians playing all voices. Accidentals are
1650 typeset for each voice, but they @emph{are} cancelled across voices in
1651 the same @internalsref{Staff}.
1653 @cindex @code{\modernVoiceCautionaries}
1654 @item \modernVoiceCautionaries
1655 is the same as @code{\modernVoiceAccidentals}, but with the extra
1656 accidentals (the ones not typeset by @code{\voiceAccidentals}) typeset
1657 as cautionaries. Even though all accidentals typeset by
1658 @code{\defaultAccidentals} @emph{are} typeset by this variable then
1659 some of them are typeset as cautionaries.
1661 @item \pianoAccidentals
1662 @cindex @code{\pianoAccidentals}
1663 20th century practice for piano notation. Very similar to
1664 @code{\modernAccidentals} but accidentals also get cancelled
1665 across the staves in the same @internalsref{GrandStaff} or
1666 @internalsref{PianoStaff}.
1668 @item \pianoCautionaries
1669 @cindex @code{\pianoCautionaries}
1670 As @code{\pianoAccidentals} but with the extra accidentals
1671 typeset as cautionaries.
1674 @cindex @code{\noResetKey}
1675 Same as @code{\defaultAccidentals} but with accidentals lasting
1676 ``forever'' and not only until the next measure:
1677 @lilypond[singleline,fragment,verbatim,relative]
1682 @item \forgetAccidentals
1683 @cindex @code{\forgetAccidentals}
1684 This is sort of the opposite of @code{\noResetKey}: Accidentals
1685 are not remembered at all---and hence all accidentals are
1686 typeset relative to the key signature, regardless of what was
1687 before in the music:
1688 @lilypond[singleline,fragment,verbatim,relative]
1690 \key d\major c4 c cis cis d d dis dis
1694 @node Customized accidental rules
1695 @subsection Customized accidental rules
1697 For determining when to print an accidental, several different rules
1698 are tried. The rule that gives the highest number of accidentals is
1699 used. Each rule consists of
1702 In which context is the rule applied. For example, if
1703 @var{context} is @internalsref{Score} then all staves share
1704 accidentals, and if @var{context} is @internalsref{Staff} then all
1705 voices in the same staff share accidentals, but staves do not.
1707 Whether the accidental changes all octaves or only the current
1710 Over how many barlines the accidental lasts.
1711 If @var{lazyness} is @code{-1} then the accidental is forget
1712 immediately, and if @var{lazyness} is @code{#t} then the accidental
1715 @c [TODO: should use +infinity for this case?]
1721 @cindex @code{\defaultAccidentals}
1722 @code{\defaultAccidentals},
1723 @cindex @code{\voiceAccidentals}
1724 @code{\voiceAccidentals},
1725 @cindex @code{\modernAccidentals}
1726 @code{\modernAccidentals},
1727 @cindex @code{\modernCautionaries}
1728 @code{\modernCautionaries},
1729 @cindex @code{\modernVoiceAccidentals}
1730 @code{\modernVoiceAccidentals},
1731 @cindex @code{\modernVoiceCautionaries}
1732 @code{\modernVoiceCautionaries},
1733 @cindex @code{\pianoAccidentals}
1734 @code{\pianoAccidentals},
1735 @cindex @code{\pianoCautionaries}
1736 @code{\pianoCautionaries},
1737 @cindex @code{\noResetKey}
1739 @cindex @code{\forgetAccidentals}
1740 @code{\forgetAccidentals}.
1744 @internalsref{Accidental_engraver}, @internalsref{Accidental}, and
1745 @internalsref{AccidentalPlacement}.
1750 Currently the simultaneous notes are considered to be entered in
1751 sequential mode. This means that in a chord the accidentals are
1752 typeset as if the notes in the chord happened once at a time - in the
1753 order in which they appear in the input file.
1755 This is only a problem when there are simultaneous notes whose
1756 accidentals depend on each other. The problem only occurs when using
1757 non-default accidentals. In the default scheme, accidentals only
1758 depend on other accidentals with the same pitch on the same staff, so
1759 no conflicts possible.
1761 This example shows two examples of the same music giving different
1762 accidentals depending on the order in which the notes occur in the
1765 @lilypond[singleline,fragment,verbatim]
1766 \property Staff.autoAccidentals = #'( Staff (any-octave . 0) )
1767 cis'4 <c'' c'> r2 | cis'4 <c' c''> r2
1768 | <cis' c''> r | <c'' cis'> r |
1771 This problem can be solved by manually inserting @code{!} and @code{?}
1772 for the problematic notes.
1774 @node Expressive marks
1775 @section Expressive marks
1778 @c todo: should change ordering
1779 @c where to put text spanners, metronome marks,
1788 * Analysis brackets::
1790 * Fingering instructions::
1801 A slur indicates that notes are to be played bound or @emph{legato}.
1805 They are entered using parentheses:
1806 @lilypond[relative 1,fragment,verbatim,center]
1807 f( g)( a) a8 b( a4 g2 f4)
1812 @c TODO: should explain that ^( and _( set directions
1813 @c should set attachments with ^ and _ ?
1815 Slurs avoid crossing stems, and are generally attached to note heads.
1816 However, in some situations with beams, slurs may be attached to stem
1817 ends. If you want to override this layout you can do this through the
1818 object property @code{attachment} of @internalsref{Slur} in
1819 @internalsref{Voice} context. Its value is a pair of symbols, specifying
1820 the attachment type of the left and right end points:
1822 @lilypond[fragment,relative,verbatim]
1824 \property Voice.Stem \set #'length = #5.5
1826 \property Voice.Slur \set #'attachment = #'(stem . stem)
1830 If a slur would strike through a stem or beam, the slur will be moved
1831 away upward or downward. If this happens, attaching the slur to the
1832 stems might look better:
1834 @lilypond[fragment,relative,verbatim]
1837 \property Voice.Slur \set #'attachment = #'(stem . stem)
1844 @cindex @code{\slurUp}
1846 @cindex @code{\slurDown}
1848 @cindex @code{\slurBoth}
1850 @cindex @code{\slurDotted}
1852 @cindex @code{\slurSolid}
1857 @seeinternals{Slur}, and @internalsref{SlurEvent}.
1862 Producing nice slurs is a difficult problem, and LilyPond currently
1863 uses a simple, empiric method to produce slurs. In some cases, its
1867 @cindex Adjusting slurs
1869 @node Phrasing slurs
1870 @subsection Phrasing slurs
1872 @cindex phrasing slurs
1873 @cindex phrasing marks
1875 A phrasing slur (or phrasing mark) connects chords and is used to
1876 indicate a musical sentence. It is started using @code{\(} and @code{\)}
1879 @lilypond[fragment,verbatim,center,relative]
1880 \time 6/4 c'\( d( e) f( e) d\)
1883 Typographically, the phrasing slur behaves almost exactly like a
1884 normal slur. However, they are treated as different objects. A
1885 @code{\slurUp} will have no effect on a phrasing slur; instead, you
1886 should use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
1887 @code{\phrasingSlurBoth}.
1889 The commands @code{\slurUp}, @code{\slurDown}, and @code{\slurBoth}
1890 will only affect normal slurs and not phrasing slurs.
1894 @cindex @code{\phrasingSlurUp}
1895 @code{\phrasingSlurUp},
1896 @cindex @code{\phrasingSlurDown}
1897 @code{\phrasingSlurDown},
1898 @cindex @code{\phrasingSlurBoth}
1899 @code{\phrasingSlurBoth},
1903 See also @internalsref{PhrasingSlur}, and
1904 @internalsref{PhrasingSlurEvent}.
1908 Phrasing slurs have the same limitations in their formatting as normal
1909 slurs. Putting phrasing slurs over rests leads to spurious warnings.
1912 @subsection Breath marks
1914 Breath marks are entered using @code{\breathe}:
1917 @lilypond[fragment,relative,verbatim]
1921 The glyph of the breath mark can be tweaked by overriding the
1922 @code{text} property of the @code{BreathingSign} layout object with
1923 any markup text. For example,
1924 @lilypond[fragment,verbatim,relative]
1926 \property Voice.BreathingSign \override #'text
1927 = #(make-musicglyph-markup "scripts-rvarcomma")
1934 @internalsref{BreathingSign}, @internalsref{BreathingSignEvent}, and
1935 @inputfileref{input/regression,breathing-sign.ly}.
1938 @node Metronome marks
1939 @subsection Metronome marks
1942 @cindex beats per minute
1943 @cindex metronome marking
1945 Metronome settings can be entered as follows:
1947 \tempo @var{duration} = @var{perminute}
1950 In the MIDI output, they are interpreted as a tempo change, and in the
1951 paper output, a metronome marking is printed:
1952 @cindex @code{\tempo}
1953 @lilypond[fragment,verbatim]
1959 @internalsref{MetronomeChangeEvent}.
1964 @subsection Text spanners
1965 @cindex Text spanners
1967 Some performance indications, e.g. @i{rallentando} or @i{accelerando},
1968 are written as texts, and extended over many measures with dotted
1969 lines. You can create such texts using text spanners: attach
1970 @code{\startTextSpan} and @code{\stopTextSpan} to the
1971 start and ending note of the spanner.
1973 The string to be printed, as well as the style, is set through object
1976 @lilypond[fragment,relative,verbatim]
1978 \property Voice.TextSpanner \set #'direction = #-1
1979 \property Voice.TextSpanner \set #'edge-text = #'("rall " . "")
1980 c2\startTextSpan b c\stopTextSpan a }
1986 @internalsref{TextSpanEvent},
1987 @internalsref{TextSpanner}, and
1988 @inputfileref{input/regression,text-spanner.ly}.
1991 @node Analysis brackets
1992 @subsection Analysis brackets
1994 @cindex phrasing brackets
1995 @cindex musicological analysis
1996 @cindex note grouping bracket
1998 Brackets are used in musical analysis to indicate structure in musical
1999 pieces. LilyPond supports a simple form of nested horizontal brackets.
2000 To use this, add the @internalsref{Horizontal_bracket_engraver} to
2001 @internalsref{Staff} context. A bracket is started with
2002 @code{\startGroup} and closed with @code{\stopGroup}:
2004 @lilypond[singleline,verbatim]
2005 \score { \notes \relative c'' {
2006 c4\startGroup\startGroup
2009 c4\stopGroup\stopGroup
2011 \paper { \translator {
2012 \StaffContext \consists "Horizontal_bracket_engraver"
2018 @internalsref{HorizontalBracket}, @internalsref{NoteGroupingEvent}, and
2019 @inputfileref{input/regression,note-group-bracket.ly}.
2023 @subsection Articulations
2024 @cindex Articulations
2026 @cindex articulations
2030 A variety of symbols can appear above and below notes to indicate
2031 different characteristics of the performance. They are added to a note
2032 by adding a dash and the character signifying the
2033 articulation. They are demonstrated here:
2035 @lilypondfile[notexidoc]{script-abbreviations.ly}
2037 The meanings of these shorthands can be changed: see
2038 @file{ly/script-init.ly} for examples.
2041 The script is automatically placed, but if you need to force
2042 directions, you can use @code{_} to force them down, or @code{^} to
2044 @lilypond[fragment, verbatim]
2048 Other symbols can be added using the syntax
2049 @var{note}@code{\}@var{name}, e.g. @code{c4\fermata}. Again, they
2050 can be forced up or down using @code{^} and @code{_},
2053 @lilypond[verbatim,fragment,relative 2]
2054 c\fermata c^\fermata c_\fermata
2061 @cindex staccatissimo
2070 @cindex organ pedal marks
2079 @cindex prallmordent
2083 @cindex thumb marking
2088 @lilypondfile[notexidoc]{script-chart.ly}
2093 @cindex @code{\scriptUp}
2095 @cindex @code{\scriptDown}
2097 @cindex @code{\scriptBoth}
2102 @internalsref{ScriptEvent}, and @internalsref{Script}.
2106 These note ornaments appear in the printed output but have no
2107 effect on the MIDI rendering of the music.
2110 @node Fingering instructions
2111 @subsection Fingering instructions
2115 Fingering instructions can be entered using
2117 @var{note}-@var{digit}
2119 For finger changes, use markup texts:
2121 @lilypond[verbatim, singleline, fragment]
2122 c'4-1 c'4-2 c'4-3 c'4-4
2123 c'^\markup { \fontsize #-3 \number "2-3" }
2126 @cindex finger change
2131 You can use the thumb-script to indicate that a note should be
2132 played with your thumb (used in cello music):
2134 @lilypond[verbatim, singleline, fragment]
2135 <a' a''-3>8(_\thumb <b' b''-3>)_\thumb
2136 <c'' c'''-3>(_\thumb <d'' d'''-3>)_\thumb
2139 Fingerings for chords can also be added to individual notes
2140 of the chord by adding them after the pitches:
2141 @lilypond[verbatim,singleline,fragment,relative=1]
2142 < c-1 e-2 g-3 b-5 > 4
2145 Setting @code{fingeringOrientations} will put fingerings next
2148 @lilypond[verbatim,singleline,fragment,relative=1]
2149 \property Voice.fingeringOrientations = #'(left down)
2150 <c-1 es-2 g-4 bes-5 > 4
2151 \property Voice.fingeringOrientations = #'(up right down)
2152 <c-1 es-2 g-4 bes-5 > 4
2157 @internalsref{FingerEvent}, and @internalsref{Fingering}.
2161 @subsection Text scripts
2162 @cindex Text scripts
2164 It is possible to place arbitrary strings of text or markup text (see
2165 @ref{Text markup}) above or below notes by using a string:
2166 @code{c^"text"}. By default, these indications do not influence the
2167 note spacing, but by using the command @code{\fatText}, the widths
2168 will be taken into account:
2170 @lilypond[fragment,singleline,verbatim] \relative c' {
2171 c4^"longtext" \fatText c4_"longlongtext" c4 }
2174 It is possible to use @TeX{} commands in the strings, but this should
2175 be avoided because the exact dimensions of the string can then no
2181 @internalsref{TextScriptEvent}, @internalsref{TextScript}, and
2187 @subsection Grace notes
2190 @c should have blurb about accaciatura / appogiatura
2192 @cindex @code{\grace}
2196 Grace notes are ornaments that are written out. The most common ones
2197 are acciaccatura, which should be played as very short. It is denoted
2198 by a slurred small note with a slashed stem. The appoggiatura is a
2199 grace note that takes a fixed fraction of the main note, is and
2200 denoted as a slurred note in small print without a slash.
2201 They are entered with the commands @code{\acciaccatura} and
2202 @code{\appoggiatura}, as demonstrated in the following example:
2205 @cindex appoggiatura
2206 @cindex acciaccatura
2208 @lilypond[relative=2,verbatim,fragment]
2209 b4 \acciaccatura d8 c4 \appoggiatura e8 d4
2210 \acciaccatura { g16[ f] } e4
2213 Both are special forms of the @code{\grace} command. By prefixing this
2214 keyword to a music expression, a new one is formed, which will be
2215 printed in a smaller font and takes up no logical time in a measure.
2216 @lilypond[relative=2,verbatim,fragment]
2218 \grace { c16[ d16] } c2 c4
2222 Unlike @code{\acciaccatura} and @code{\appoggiatura}, the
2223 @code{\grace} command does not start a slur.
2225 Internally, timing for grace notes is done using a second, `grace'
2226 time. Every point in time consists of two rational numbers: one
2227 denotes the logical time, one denotes the grace timing. The above
2228 example is shown here with timing tuples:
2230 @lilypond[singleline]
2233 c4 \grace c16 c4 \grace {
2236 \new Lyrics \lyrics {
2239 ( \fraction 1 4 , \fraction -1 16 ) } 16 }
2240 \markup { (\fraction 1 4 , 0 ) } 4
2242 \markup { (\fraction 2 4 , \fraction "-1" 8 ) } 16
2243 \markup { (\fraction 2 4 , \fraction "-1" 16 ) } 16
2245 \markup { ( \fraction 2 4 , 0 ) }
2250 The placement of grace notes is synchronized between different staves.
2251 In the following example, there are two sixteenth graces notes for
2252 every eighth grace note:
2254 @lilypond[relative=2,verbatim,fragment]
2255 << \new Staff { e4 \grace { c16[ d e f] } e4 }
2256 \new Staff { c'4 \grace { g8[ b] } c4 } >>
2261 If you want to end a note with a grace, then the standard trick
2262 is to put the grace notes after a ``space note'', e.g.
2263 @lilypond[fragment,verbatim, relative=2]
2266 { s2 \grace { c16[ d] } } >>
2272 By adjusting the duration of the skip note (here it is a half-note),
2273 the space between the main-note and the grace is adjusted.
2276 A @code{\grace} section will introduce special typesetting settings,
2277 for example, to produce smaller type, and set directions. Hence, when
2278 introducing layout tweaks, they should be inside the grace section,
2280 @lilypond[fragment,verbatim,relative 1]
2283 \property Voice.Stem \override #'direction = #-1
2285 \property Voice.Stem \revert #'direction
2292 The overrides should also be reverted inside the grace section.
2294 If the layout of grace sections must be changed throughout the music,
2295 then this can be accomplished through the function
2296 @code{add-grace-property}. The following example
2297 undefines the Stem direction grace section, so stems do not always
2302 #(add-grace-property "Voice" Stem direction '())
2308 Another option is to change the variables @code{startGraceMusic},
2309 @code{stopGraceMusic}, @code{startAccacciaturaMusic},
2310 @code{stopAccacciaturaMusic}, @code{startAppoggiaturaMusic},
2311 @code{stopAppoggiaturaMstuic}. More information is in the file
2312 @file{ly/grace-init.ly}
2317 @internalsref{GraceMusic}.
2321 Grace notes cannot be used in the smallest size (@file{paper11.ly}).
2323 A score that starts with an @code{\grace} section needs an explicit
2324 @code{\context Voice} declaration, otherwise the main note and grace
2325 note end up on different staves.
2327 Grace note synchronization can also lead to surprises. Staff notation,
2328 such as key signatures, barlines, etc. are also synchronized. Take
2329 care when you mix staves with grace notes and staves without, for example,
2331 @lilypond[relative=2,verbatim,fragment]
2332 << \new Staff { e4 \bar "|:" \grace c16 d4 }
2333 \new Staff { c4 \bar "|:" d4 } >>
2336 Grace sections should only be used within sequential music
2337 expressions. Nesting or juxtaposing grace sections is not supported,
2338 and might produce crashes or other errors.
2340 Overriding settings cannot be done in separate styles for appoggiatura
2345 @subsection Glissando
2348 @cindex @code{\glissando}
2350 A glissando is a smooth change in pitch. It is denoted by a line or a
2351 wavy line between two notes.
2355 A glissando line can be requested by attaching a @code{\glissando} to
2358 @lilypond[fragment,relative,verbatim]
2364 @internalsref{Glissando}, and @internalsref{GlissandoEvent}.
2369 Adding additional texts (such as @emph{gliss.}) is not supported.
2373 @subsection Dynamics
2386 @cindex @code{\ffff}
2396 Absolute dynamic marks are specified using an variable after a
2397 note: @code{c4\ff}. The available dynamic marks are @code{\ppp},
2398 @code{\pp}, @code{\p}, @code{\mp}, @code{\mf}, @code{\f}, @code{\ff},
2399 @code{\fff}, @code{\fff}, @code{\fp}, @code{\sf}, @code{\sff},
2400 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}:
2402 @lilypond[verbatim,singleline,fragment,relative]
2403 c'\ppp c\pp c \p c\mp c\mf c\f c\ff c\fff
2409 @cindex @code{\decr}
2410 @cindex @code{\rced}
2417 A crescendo mark is started with @code{\<} and terminated with
2418 @code{\!}. A decrescendo is started with @code{\>} and also terminated
2419 with @code{\!}. Because these marks are bound to notes, if you must
2420 use spacer notes if multiple marks during one note are needed:
2422 @lilypond[fragment,verbatim,center,quote]
2423 c''\< c''\! d''\decr e''\rced
2424 << f''1 { s4 s4\< s4\! \> s4\! } >>
2426 This may give rise to very short hairpins. Use @code{minimum-length}
2427 in @internalsref{Voice}.@internalsref{Hairpin} to lengthen them, for
2431 \property Staff.Hairpin \override #'minimum-length = #5
2434 You can also use a text saying @emph{cresc.} instead of hairpins. Here
2435 is an example how to do it:
2437 @lilypond[fragment,relative=2,verbatim]
2438 c4 \cresc c4 c c c \endcresc c4
2444 You can also supply your own texts:
2445 @lilypond[fragment,relative,verbatim]
2447 \property Voice.crescendoText = \markup { \italic "cresc. poco" }
2448 \property Voice.crescendoSpanner = #'dashed-line
2458 @cindex @code{\dynamicUp}
2460 @cindex @code{\dynamicDown}
2461 @code{\dynamicDown},
2462 @cindex @code{\dynamicBoth}
2463 @code{\dynamicBoth}.
2465 @cindex direction, of dynamics
2469 @internalsref{CrescendoEvent}, @internalsref{DecrescendoEvent}, and
2470 @internalsref{AbsoluteDynamicEvent}.
2472 Dynamics are objects of @internalsref{DynamicText} and
2473 @internalsref{Hairpin}. Vertical positioning of these symbols is
2474 handled by the @internalsref{DynamicLineSpanner} object.
2476 If you want to adjust padding or vertical direction of the dynamics, you
2477 must set properties for the @internalsref{DynamicLineSpanner} object.
2485 @cindex @code{\repeat}
2488 Repetition is a central concept in music, and multiple notations exist
2489 for repetitions. In LilyPond, most of these notations can be captured
2490 in a uniform syntax. One of the advantages is that they can be
2491 rendered in MIDI accurately.
2493 The following types of repetition are supported:
2497 Repeated music is fully written (played) out. Useful for MIDI
2498 output, and entering repetitive music.
2501 This is the normal notation: Repeats are not written out, but
2502 alternative endings (voltas) are printed, left to right.
2506 Alternative endings are written stacked. This has limited use but may be
2507 used to typeset two lines of lyrics in songs with repeats, see
2508 @inputfileref{input,star-spangled-banner.ly}.
2515 Make beat or measure repeats. These look like percent signs.
2521 * Repeats and MIDI::
2522 * Manual repeat commands::
2524 * Tremolo subdivisions::
2529 @subsection Repeat syntax
2533 LilyPond has one syntactic construct for specifying different types of
2534 repeats. The syntax is
2537 \repeat @var{variant} @var{repeatcount} @var{repeatbody}
2540 If you have alternative endings, you may add
2541 @cindex @code{\alternative}
2543 \alternative @code{@{} @var{alternative1}
2545 @var{alternative3} @dots{} @code{@}}
2547 where each @var{alternative} is a music expression. If you do not
2548 give enough alternatives for all of the repeats, then the first
2549 alternative is assumed to be played more than once.
2551 Normal notation repeats are used like this:
2552 @lilypond[fragment,verbatim,relative 1]
2554 \repeat volta 2 { c4 d e f }
2555 \repeat volta 2 { f e d c }
2558 With alternative endings:
2559 @lilypond[fragment,verbatim,relative 1]
2561 \repeat volta 2 {c4 d e f}
2562 \alternative { {d2 d} {f f,} }
2566 @lilypond[fragment,verbatim,relative 1]
2569 \repeat volta 4 { e | c2 d2 | e2 f2 | }
2570 \alternative { { g4 g g } { a | a a a a | b2. } }
2576 If you do a nested repeat like
2585 then it is ambiguous to which @code{\repeat} the @code{\alternative}
2586 belongs. This ambiguity is resolved by always having the
2587 @code{\alternative} belong to the inner @code{\repeat}. For clarity,
2588 it is advisable to use braces in such situations.
2591 @node Repeats and MIDI
2592 @subsection Repeats and MIDI
2594 @cindex expanding repeats
2596 For instructions on how to unfold repeats for MIDI output, see the
2597 example file @inputfileref{input/test,unfold-all-repeats.ly}.
2602 Timing information is not remembered at the start of an alternative,
2603 so after a repeat timing information must be reset by hand, for
2604 example by setting @code{Score.measurePosition} or entering
2605 @code{\partial}. Similarly, slurs or ties are also not repeated.
2608 @node Manual repeat commands
2609 @subsection Manual repeat commands
2611 @cindex @code{repeatCommands}
2613 The property @code{repeatCommands} can be used to control the layout of
2614 repeats. Its value is a Scheme list of repeat commands, where each repeat
2618 @item the symbol @code{start-repeat},
2619 which prints a @code{|:} bar line,
2620 @item the symbol @code{end-repeat},
2621 which prints a @code{:|} bar line,
2622 @item the list @code{(volta @var{text})},
2623 which prints a volta bracket saying @var{text}: The text can be specified as
2624 a text string or as a markup text, see @ref{Text markup}. Do not
2625 forget to change the font, as the default number font does not contain
2626 alphabetic characters. Or,
2627 @item the list @code{(volta #f)}, which
2628 stops a running volta bracket:
2631 @lilypond[verbatim, fragment,relative 2]
2633 \property Score.repeatCommands = #'((volta "93") end-repeat)
2635 \property Score.repeatCommands = #'((volta #f))
2642 @internalsref{VoltaBracket}, @internalsref{RepeatedMusic},
2643 @internalsref{VoltaRepeatedMusic},
2644 @internalsref{UnfoldedRepeatedMusic}, and
2645 @internalsref{FoldedRepeatedMusic}.
2647 @node Tremolo repeats
2648 @subsection Tremolo repeats
2649 @cindex tremolo beams
2651 To place tremolo marks between notes, use @code{\repeat} with tremolo
2653 @lilypond[verbatim,center,singleline]
2655 \context Voice \notes\relative c' {
2656 \repeat "tremolo" 8 { c16 d16 }
2657 \repeat "tremolo" 4 { c16 d16 }
2658 \repeat "tremolo" 2 { c16 d16 }
2659 \repeat "tremolo" 4 c16
2666 Tremolo beams are @internalsref{Beam} objects. Single stem tremolos
2667 are @internalsref{StemTremolo}s. The music expression is
2668 @internalsref{TremoloEvent}.
2673 The single stem tremolo must be entered without @code{@{} and
2676 @node Tremolo subdivisions
2677 @subsection Tremolo subdivisions
2678 @cindex tremolo marks
2679 @cindex @code{tremoloFlags}
2681 Tremolo marks can be printed on a single note by adding
2682 `@code{:}[@var{length}]' after the note. The length must be at least 8.
2683 A @var{length} value of 8 gives one line across the note stem. If the
2684 length is omitted, then then the last value (stored in
2685 @code{Voice.tremoloFlags}) is used:
2687 @lilypond[verbatim,fragment,center]
2688 c'2:8 c':32 | c': c': |
2691 @c [TODO : stok is te kort bij 32en]
2695 Tremolos in this style do not carry over into the MIDI output.
2698 @node Measure repeats
2699 @subsection Measure repeats
2701 @cindex percent repeats
2702 @cindex measure repeats
2704 In the @code{percent} style, a note pattern can be repeated. It is
2705 printed once, and then the pattern is replaced with a special sign.
2706 Patterns of a one and two measures are replaced by percent-like signs,
2707 patterns that divide the measure length are replaced by slashes:
2709 @lilypond[verbatim,singleline]
2710 \context Voice { \repeat "percent" 4 { c'4 }
2711 \repeat "percent" 2 { c'2 es'2 f'4 fis'4 g'4 c''4 }
2717 @internalsref{RepeatSlash}, @internalsref{PercentRepeat},
2718 @internalsref{PercentRepeatedMusic}, and
2719 @internalsref{DoublePercentRepeat}.
2723 @node Rhythmic music
2724 @section Rhythmic music
2726 Sometimes you might want to show only the rhythm of a melody. This
2727 can be done with the rhythmic staff. All pitches of notes on such a
2728 staff are squashed, and the staff itself has a single line:
2730 @lilypond[fragment,relative,verbatim]
2731 \context RhythmicStaff {
2733 c4 e8 f g2 | r4 g r2 | g1:32 | r1 |
2738 * Percussion staves::
2739 * Percussion MIDI output::
2742 @node Percussion staves
2743 @subsection Percussion staves
2747 A percussion part for more than one instrument typically uses a
2748 multiline staff where each position in the staff refers to one piece
2753 Percussion staves are typeset with help of a set of Scheme
2754 functions. The system is based on the general MIDI drum-pitches.
2755 Include @file{drumpitch-init.ly} to use drum pitches. This file
2756 defines the pitches from the Scheme variable @code{drum-pitch-names},
2757 the definition of which can be read in @file{scm/drums.scm}. Each
2758 piece of percussion has a full name and an abbreviated name, and either
2759 the full name or the abbreviation may be used in input files.
2761 To typeset the music on a staff apply the function @code{drums->paper}
2762 to the percussion music. This function takes a list of percussion
2763 instrument names, notehead scripts and staff positions (that is:
2764 pitches relative to the C-clef) and transforms the input
2765 music by moving the pitch, changing the notehead and (optionally)
2768 @lilypond[singleline,verbatim,quote]
2769 \include "drumpitch-init.ly"
2770 up = \notes { crashcymbal4 hihat8 halfopenhihat hh hh hh openhihat }
2771 down = \notes { bassdrum4 snare8 bd r bd sn4 }
2773 \apply #(drums->paper 'drums) \context Staff <<
2775 \new Voice { \voiceOne \up }
2776 \new Voice { \voiceTwo \down }
2781 In the above example the music was transformed using the list @code{'drums}.
2782 The following lists are defined in @file{scm/drums.scm}:
2785 to typeset a typical drum kit on a five-line staff:
2788 \include "drumpitch-init.ly"
2789 nam = \lyrics { cymc cyms cymr hh hhc hho hhho hhp cb hc
2790 bd sn ss tomh tommh tomml toml tomfh tomfl }
2791 mus = \notes { cymc cyms cymr hh hhc hho hhho hhp cb hc
2792 bd sn ss tomh tommh tomml toml tomfh tomfl s16 }
2795 \apply #(drums->paper 'drums) \context Staff <<
2799 \context Lyrics \nam
2802 linewidth = 100.0\mm
2805 \remove Bar_engraver
2806 \remove Time_signature_engraver
2807 minimumVerticalExtent = #'(-4.0 . 5.0)
2811 \remove Stem_engraver
2817 The drum scheme supports six different toms. When there fewer toms, simply
2818 select the toms that produce the desired result, i.e. to get toms on
2819 the three middle lines you use @code{tommh}, @code{tomml} and
2822 Because general MIDI does not contain rimshots the sidestick is used
2823 for this purpose instead.
2825 to typeset timbales on a two line staff:
2827 @lilypond[singleline]
2828 \include "drumpitch-init.ly"
2829 nam = \lyrics { timh ssh timl ssl cb }
2830 mus = \notes { timh ssh timl ssl cb s16 }
2833 \apply #(drums->paper 'timbales) \context Staff <<
2837 \context Lyrics \nam
2842 \remove Bar_engraver
2843 \remove Time_signature_engraver
2844 StaffSymbol \override #'line-count = #2
2845 StaffSymbol \override #'staff-space = #2
2846 minimumVerticalExtent = #'(-3.0 . 4.0)
2850 \remove Stem_engraver
2857 to typeset congas on a two line staff:
2859 @lilypond[singleline]
2860 \include "drumpitch-init.ly"
2861 nam = \lyrics { cgh cgho cghm ssh cgl cglo cglm ssl }
2862 mus = \notes { cgh cgho cghm ssh cgl cglo cglm ssl s16 }
2865 \apply #(drums->paper 'congas) \context Staff <<
2869 \context Lyrics \nam
2874 \remove Bar_engraver
2875 \remove Time_signature_engraver
2876 StaffSymbol \override #'line-count = #2
2877 StaffSymbol \override #'staff-space = #2
2878 minimumVerticalExtent = #'(-3.0 . 4.0)
2882 \remove Stem_engraver
2888 to typeset bongos on a two line staff:
2890 @lilypond[singleline]
2891 \include "drumpitch-init.ly"
2892 nam = \lyrics { boh boho bohm ssh bol bolo bolm ssl }
2893 mus = \notes { boh boho bohm ssh bol bolo bolm ssl s16 }
2896 \apply #(drums->paper 'bongos) \context Staff <<
2900 \context Lyrics \nam
2905 \remove Bar_engraver
2906 \remove Time_signature_engraver
2907 StaffSymbol \override #'line-count = #2
2908 StaffSymbol \override #'staff-space = #2
2909 minimumVerticalExtent = #'(-3.0 . 4.0)
2913 \remove Stem_engraver
2919 to typeset all kinds of simple percussion on one line staves:
2920 @lilypond[singleline]
2921 \include "drumpitch-init.ly"
2922 nam = \lyrics { tri trio trim gui guis guil cb cl tamb cab mar hc }
2923 mus = \notes { tri trio trim gui guis guil cb cl tamb cab mar hc s16 }
2926 \apply #(drums->paper 'percussion) \context Staff <<
2930 \context Lyrics \nam
2935 \remove Bar_engraver
2936 \remove Time_signature_engraver
2937 StaffSymbol \override #'line-count = #1
2938 minimumVerticalExtent = #'(-2.0 . 3.0)
2942 \remove Stem_engraver
2949 If you do not like any of the predefined lists you can define your own
2950 list at the top of your file:
2952 @lilypond[singleline, verbatim]
2953 #(set-drum-kit 'mydrums `(
2954 (bassdrum default #f ,(ly:make-pitch -1 2 0))
2955 (snare default #f ,(ly:make-pitch 0 1 0))
2956 (hihat cross #f ,(ly:make-pitch 0 5 0))
2957 (pedalhihat xcircle "stopped" ,(ly:make-pitch 0 5 0))
2958 (lowtom diamond #f ,(ly:make-pitch -1 6 0))
2960 \include "drumpitch-init.ly"
2961 up = \notes { hh8 hh hh hh hhp4 hhp }
2962 down = \notes { bd4 sn bd toml8 toml }
2964 \apply #(drums->paper 'mydrums) \context Staff <<
2966 \new Voice { \voiceOne \up }
2967 \new Voice { \voiceTwo \down }
2972 To use a modified existing list, one can prepend modifications to the
2976 #(set-drum-kit 'mydrums (append `(
2977 (bassdrum default #f ,(ly:make-pitch -1 2 0))
2978 (lowtom diamond #f ,(ly:make-pitch -1 6 0))
2979 ) (get-drum-kit 'drums)))
2982 You can easily combine percussion notation with pitched notation.
2983 Indeed, the file @file{drumpitch-init.ly} replaces the normal pitch
2984 names, so you will have to reinclude @file{nederlands.ly} after the
2985 drum-pattern-definitions to enter normal notes:
2987 @lilypond[singleline,verbatim]
2988 \include "drumpitch-init.ly"
2989 up = \notes { crashcymbal4 hihat8 halfopenhihat hh hh hh openhihat }
2990 down = \notes { bassdrum4 snare8 bd r bd sn4 }
2991 \include "nederlands.ly"
2992 bass = \notes \transpose c c,, { a4. e8 r e g e }
2995 \apply #(drums->paper 'drums) \new Staff <<
2997 \new Voice { \voiceOne \up }
2998 \new Voice { \voiceTwo \down }
3000 \new Staff { \clef "F_8" \bass }
3005 @node Percussion MIDI output
3006 @subsection Percussion MIDI output
3008 In order to produce correct MIDI output you need to produce two score
3009 blocks---one for the paper and one for the MIDI output. To use the
3010 percussion channel you set the property @code{instrument} to
3011 @code{'drums}. Because the drum-pitches themselves are similar to the
3012 general MIDI pitches all you have to do is to insert the voices with
3013 none of the scheme functions to get the correct MIDI output:
3017 \apply #(drums->paper 'mydrums) \context Staff <<
3026 \property Staff.instrument = #'drums
3035 This scheme is a temporary implementation.
3039 @section Piano music
3041 Piano staves are two normal staves coupled with a brace. The staves
3042 are largely independent, but sometimes voices can cross between the
3043 two staves. The same notation is also used for harps and other key
3044 instruments. The @internalsref{PianoStaff} is especially built to
3045 handle this cross-staffing behavior. In this section we discuss the
3046 @internalsref{PianoStaff} and some other pianistic peculiarities.
3050 * Automatic staff changes::
3051 * Manual staff switches::
3054 * Staff switch lines::
3059 There is no support for putting chords across staves. You can get
3060 this result by increasing the length of the stem in the lower stave so
3061 it reaches the stem in the upper stave, or vice versa. An example is
3062 included with the distribution as @inputfileref{input/test,stem-cross-staff.ly}.
3064 Dynamics are not centered, but kludges do exist. See
3065 @inputfileref{input/template,piano-dynamics.ly}.
3067 @cindex cross staff stem
3068 @cindex stem, cross staff
3071 @c fixme: should have hyperlinks as well.
3077 @node Automatic staff changes
3078 @subsection Automatic staff changes
3079 @cindex Automatic staff changes
3081 Voices can switch automatically between the top and the bottom
3082 staff. The syntax for this is
3084 \autochange Staff \context Voice @{ @dots{}@var{music}@dots{} @}
3086 The two staffs of the piano staff must be named @code{up} and
3089 The autochanger switches on basis of pitch (central C is the turning
3090 point), and it looks ahead skipping over rests to switch in
3091 advance. Here is a practical example:
3093 @lilypond[verbatim,singleline,quote]
3094 \score { \notes \context PianoStaff <<
3095 \context Staff = "up" {
3096 \autochange Staff \context Voice = VA << \relative c' {
3097 g4 a b c d r4 a g } >> }
3098 \context Staff = "down" {
3105 In this example, spacer rests are used to prevent the bottom staff from
3106 terminating too soon.
3111 @internalsref{AutoChangeMusic}.
3115 The staff switches often do not end up in optimal places. For high
3116 quality output, staff switches should be specified manually.
3120 @node Manual staff switches
3121 @subsection Manual staff switches
3123 @cindex manual staff switches
3124 @cindex staff switch, manual
3126 Voices can be switched between staves manually, using the following command:
3128 \translator Staff = @var{staffname} @var{music}
3132 The string @var{staffname} is the name of the staff. It switches the
3133 current voice from its current staff to the Staff called
3134 @var{staffname}. Typically @var{staffname} is @code{"up"} or
3142 Pianos have pedals that alter the way sound are produced. Generally, a
3143 piano has three pedals, sustain, una corda, and sostenuto.
3147 Piano pedal instruction can be expressed by attaching
3148 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
3149 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
3152 @lilypond[fragment,verbatim]
3153 c'4\sustainDown c'4\sustainUp
3156 What is printed can be modified by setting @code{pedal@var{X}Strings},
3157 where @var{X} is one of the pedal types: @code{Sustain},
3158 @code{Sostenuto} or @code{UnaCorda}. Refer to the generated
3159 documentation of @internalsref{SustainPedal} for more information.
3161 Pedals can also be indicated by a sequence of brackets, by setting the
3162 @code{pedalSustainStyle} property to @code{bracket} objects:
3164 @lilypond[fragment,verbatim]
3165 \property Staff.pedalSustainStyle = #'bracket
3166 c''4\sustainDown d''4 e''4
3167 a'4\sustainUp\sustainDown
3168 f'4 g'4 a'4\sustainUp
3171 A third style of pedal notation is a mixture of text and brackets,
3172 obtained by setting @code{pedal-type} to @code{mixed}:
3174 @lilypond[fragment,verbatim]
3175 \property Staff.pedalSustainStyle = #'mixed
3176 c''4\sustainDown d''4 e''4
3177 c'4\sustainUp\sustainDown
3178 f'4 g'4 a'4\sustainUp
3181 The default `*Ped' style for sustain and damper pedals corresponds to
3182 @code{\pedal-type = #'text}. However, @code{mixed} is the default style
3183 for a sostenuto pedal:
3185 @lilypond[fragment,verbatim]
3186 c''4\sostenutoDown d''4 e''4 c'4 f'4 g'4 a'4\sostenutoUp
3189 For fine-tuning of the appearance of a pedal bracket, the properties
3190 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
3191 @code{PianoPedalBracket} objects (see
3192 @internalsref{PianoPedalBracket} in the Program reference) can be modified. For example, the
3193 bracket may be extended to the end of the note head:
3195 @lilypond[fragment,verbatim]
3196 \property Staff.PianoPedalBracket \override
3197 #'shorten-pair = #'(0 . -1.0)
3198 c''4\sostenutoDown d''4 e''4 c'4
3199 f'4 g'4 a'4\sostenutoUp
3203 @subsection Arpeggio
3206 @cindex broken arpeggio
3207 @cindex @code{\arpeggio}
3209 You can specify an arpeggio sign on a chord by attaching an
3210 @code{\arpeggio} to a chord:
3213 @lilypond[fragment,relative,verbatim]
3217 When an arpeggio crosses staves, you attach an arpeggio to the chords
3218 in both staves, and set
3219 @internalsref{PianoStaff}.@code{connectArpeggios}:
3221 @lilypond[fragment,relative,verbatim]
3222 \context PianoStaff <<
3223 \property PianoStaff.connectArpeggios = ##t
3224 \new Staff { <c' e g c>\arpeggio }
3225 \new Staff { \clef bass <c,, e g>\arpeggio }
3229 The direction of the arpeggio is sometimes denoted by adding an
3230 arrowhead to the wiggly line. This can be typeset by setting
3231 @code{arpeggio-direction}:
3233 @lilypond[fragment,relative,verbatim]
3235 \property Voice.Arpeggio \set #'arpeggio-direction = #1
3237 \property Voice.Arpeggio \set #'arpeggio-direction = #-1
3242 A square bracket on the left indicates that the player should not
3243 arpeggiate the chord. To draw these brackets, set the
3244 @code{molecule-callback} property of @code{Arpeggio} or
3245 @code{PianoStaff.Arpeggio} objects to @code{\arpeggioBracket}, and use
3246 @code{\arpeggio} statements within the chords as before:
3248 @lilypond[fragment,relative,verbatim]
3249 \property PianoStaff.Arpeggio \override
3250 #'molecule-callback = \arpeggioBracket
3256 @cindex @code{\arpeggioBracket}
3257 @code{\arpeggioBracket},
3258 @cindex @code{\arpeggio}
3263 @internalsref{ArpeggioEvent} music expressions lead to
3264 @internalsref{Arpeggio} objects. Cross staff arpeggios are
3265 @internalsref{PianoStaff}.@internalsref{Arpeggio}.
3269 It is not possible to mix connected arpeggios and unconnected
3270 arpeggios in one @internalsref{PianoStaff} at the same time.
3272 @node Staff switch lines
3273 @subsection Staff switch lines
3276 @cindex follow voice
3277 @cindex staff switching
3280 @cindex @code{followVoice}
3282 Whenever a voice switches to another staff a line connecting the notes
3283 can be printed automatically. This is enabled if the property
3284 @code{PianoStaff.followVoice} is set to true:
3286 @lilypond[fragment,relative,verbatim]
3287 \context PianoStaff <<
3288 \property PianoStaff.followVoice = ##t
3289 \context Staff \context Voice {
3291 \translator Staff=two
3294 \context Staff=two { \clef bass \skip 1*2 }
3298 The associated object is @internalsref{VoiceFollower}.
3302 @cindex @code{\showStaffSwitch}
3303 @code{\showStaffSwitch},
3304 @cindex @code{\hideStaffSwitch}
3305 @code{\hideStaffSwitch}.
3309 @section Vocal music
3311 This section discusses how to enter and print lyrics.
3315 * The Lyrics context::
3320 @node Entering lyrics
3321 @subsection Entering lyrics
3325 @cindex @code{\lyrics}
3328 Lyrics are entered in a special input mode. This mode is is introduced
3329 by the keyword @code{\lyrics}. In this mode you can enter lyrics, with
3330 punctuation and accents without any hassle. Syllables are entered like
3331 notes, but with pitches replaced by text. For example,
3333 \lyrics @{ Twin-4 kle4 twin- kle litt- le star2 @}
3336 A word in Lyrics mode begins with: an alphabetic character, @code{_},
3337 @code{?}, @code{!}, @code{:}, @code{'}, the control characters @code{^A}
3338 through @code{^F}, @code{^Q} through @code{^W}, @code{^Y}, @code{^^},
3339 any 8-bit character with ASCII code over 127, or a two-character
3340 combination of a backslash followed by one of @code{`}, @code{'},
3341 @code{"}, or @code{^}.
3343 Subsequent characters of a word can be any character that is not a digit
3344 and not white space. One important consequence of this is that a word
3345 can end with @code{@}}. The following example is usually a bug. The
3346 syllable includes a @code{@}}, and hence the opening brace is not balanced:
3348 \lyrics @{ twinkle@}
3351 @cindex @code{\property}, in @code{\lyrics}
3352 Similarly, a period following a alphabetic sequence, is included in the
3353 resulting string. As a consequence, spaces must be inserted around
3354 @code{\property} commands:
3356 \property Lyrics . LyricText \set #'font-shape = #'italic
3360 @cindex spaces, in lyrics
3361 @cindex quotes, in lyrics
3363 Any @code{_} character which appears in an unquoted word is converted
3364 to a space. This provides a mechanism for introducing spaces into words
3365 without using quotes. Quoted words can also be used in Lyrics mode to
3366 specify words that cannot be written with the above rules:
3369 \lyrics @{ He said: "\"Let" my peo ple "go\"" @}
3373 Hyphens can be entered as ordinary hyphens at the end of a syllable, i.e.
3378 These will be attached to the end of the first syllable.
3380 Centered hyphens are entered using the special `@code{-}@code{-}' lyric
3381 as a separate word between syllables. The hyphen will have variable
3382 length depending on the space between the syllables and it will be
3383 centered between the syllables.
3388 When a lyric is sung over many notes (this is called a melisma), this is
3389 indicated with a horizontal line centered between a syllable and the
3390 next one. Such a line is called an extender line, and it is entered as
3395 @internalsref{LyricEvent}, @internalsref{HyphenEvent}, and
3396 @internalsref{ExtenderEvent}.
3400 The definition of lyrics mode is too complex.
3402 @node The Lyrics context
3403 @subsection The Lyrics context
3405 Lyrics are printed by interpreting them in @internalsref{Lyrics} context:
3407 \context Lyrics \lyrics @dots{}
3410 @cindex automatic syllable durations
3411 @cindex @code{\addlyrics}
3412 @cindex lyrics and melodies
3414 This will place the lyrics according to the durations that were
3415 entered. The lyrics can also be aligned under a given melody
3416 automatically. In this case, it is no longer necessary to enter the
3417 correct duration for each syllable. This is achieved by combining the
3418 melody and the lyrics with the @code{\addlyrics} expression:
3422 \context Lyrics @dots{}
3425 @cindex staff order, with @code{\addlyrics}
3427 Normally, this will put the lyrics below the staff. For different or
3428 more complex orderings, the best way is to setup the hierarchy of
3429 staves and lyrics first, e.g.
3431 \context ChoirStaff \notes <<
3432 \context Lyrics = sopr @{ s1 @}
3433 \context Staff = soprStaff @{ s1 @}
3434 \context Lyrics = tenor @{ s1 @}
3435 \context Staff = tenorStaff @{ s1 @}
3438 and then combine the appropriate melodies and lyric lines:
3441 \context Staff = soprStaff @emph{the music}
3442 \context Lyrics = sopr @emph{the lyrics}
3445 putting both together, you would get
3447 \context ChoirStaff \notes <<
3448 \context Lyrics = @dots{}
3449 \context Staff = @dots{}
3455 @cindex choral score
3457 A complete example of a SATB score setup is in the file
3458 @inputfileref{input/template,satb.ly}.
3462 @internalsref{LyricCombineMusic}, @internalsref{Lyrics}, and
3463 @inputfileref{input/template,satb.ly}.
3467 @code{\addlyrics} is not automatic enough: melismata are not detected
3468 automatically, and melismata are not stopped when they hit a rest. A
3469 melisma on the last note in a melody is not printed.
3473 @subsection More stanzas
3476 @cindex phrasing, in lyrics
3478 When multiple stanzas are printed underneath each other, the vertical
3479 groups of syllables should be aligned around punctuation. This can be
3480 done automatically when corresponding lyric lines and melodies are
3483 To this end, give the @internalsref{Voice} context an identity:
3485 \context Voice = duet @{
3490 Then set the @internalsref{LyricsVoice} contexts to names starting with
3491 that identity followed by a dash. In the preceding example, the
3492 @internalsref{Voice} identity is @code{duet}, so the identities of the
3493 @internalsref{LyricsVoice}s are marked @code{duet-1} and @code{duet-2}:
3495 \context LyricsVoice = "duet-1" @{
3496 Hi, my name is bert. @}
3497 \context LyricsVoice = "duet-2" @{
3498 Ooooo, ch\'e -- ri, je t'aime. @}
3500 The convention for naming @internalsref{LyricsVoice} and
3501 @internalsref{Voice} must also be used to get melismata correct in
3502 conjunction with rests.
3504 The complete example is shown here:
3505 @lilypond[singleline,verbatim]
3508 \notes \relative c'' \context Voice = duet { \time 3/4
3510 \lyrics \context Lyrics <<
3511 \context LyricsVoice = "duet-1" {
3512 \property LyricsVoice . stanza = "Bert"
3513 Hi, my name is bert. }
3514 \context LyricsVoice = "duet-2" {
3515 \property LyricsVoice . stanza = "Ernie"
3516 Ooooo, ch\'e -- ri, je t'aime. }
3521 Stanza numbers, or the names of the singers can be added by setting
3522 @code{LyricsVoice.Stanza} (for the first system) and
3523 @code{LyricsVoice.stz} for the following systems. Notice how dots are
3524 surrounded with spaces in @code{\lyrics} mode:
3527 \property LyricsVoice . stanza = "Bert"
3529 \property LyricsVoice . stanza = "Ernie"
3532 To make empty spaces in lyrics, use @code{\skip}.
3540 Input for lyrics introduces a syntactical ambiguity:
3547 is interpreted as assigning a string identifier @code{\foo} such that
3548 it contains @code{"bar"}. However, it could also be interpreted as
3549 making or a music identifier @code{\foo} containing the syllable
3550 `bar'. The force the latter interpretation, use
3560 The term @emph{ambitus} denotes a range of pitches for a given voice in
3561 a part of music. It also may denote the pitch range that a musical
3562 instrument is capable of playing. Most musical instruments have their
3563 ambitus standardized (or at least there is agreement upon the minimal
3564 ambitus of a particular type of instrument), such that a composer or
3565 arranger of a piece of music can easily meet the ambitus constraints of
3566 the targeted instrument. However, the ambitus of the human voice
3567 depends on individual physiological state, including education and
3568 training of the voice. Therefore, a singer potentially has to check for
3569 each piece of music if the ambitus of that piece meets his individual
3570 capabilities. This is why the ambitus of a piece may be of particular
3571 value to vocal performers.
3573 The ambitus is typically notated on a per-voice basis at the very
3574 beginning of a piece, e.g. nearby the initial clef or time signature of
3575 each staff. The range is graphically specified by two noteheads, that
3576 represent the minimum and maximum pitch. Some publishers use a textual
3577 notation: they put the range in words in front of the corresponding
3578 staff. LilyPond only supports the graphical ambitus notation.
3580 To apply, add the @internalsref{Ambitus_engraver} to the
3581 @internalsref{Voice} context, i.e.
3587 \consists Ambitus_engraver
3592 This results in the following output:
3593 @lilypond[singleline]
3594 upper = \notes \relative c {
3597 as'' c e2 bes f cis d4 e f2 g
3599 lower = \notes \relative c {
3602 e'4 b g a c es fis a cis b a g f e d2
3605 \context ChoirStaff {
3607 \new Staff { \upper }
3608 \new Staff { \lower }
3614 \consists Ambitus_engraver
3620 If you have multiple voices in a single staff, and you want a single
3621 ambitus per staff rather than per each voice, then add the
3622 @internalsref{Ambitus_engraver} to the @internalsref{Staff} context
3623 rather than to the @internalsref{Voice} context.
3625 It is possible to tune individual ambiti for multiple voices on a
3626 single staff, for example by erasing or shifting them horizontally. An
3627 example is in @inputfileref{input/test,ambitus-mixed.ly}
3631 @internalsref{Ambitus}, @inputfileref{input/regression,ambitus.ly},
3632 @inputfileref{input/test,ambitus-mixed.ly}.
3636 There is no collision handling in the case of multiple per-voice
3642 Tablature notation is used for notating music for plucked string
3643 instruments. It notates pitches not by using note heads, but by
3644 indicating on which string and fret a note must be played. LilyPond
3645 offers limited support for tablature.
3648 * Tablatures basic::
3649 * Non-guitar tablatures::
3652 @node Tablatures basic
3653 @subsection Tablatures basic
3654 @cindex Tablatures basic
3656 The string number associated to a note is given as a backslash
3657 followed by a number, e.g. @code{c4\3} for a C quarter on the third
3658 string. By default, string 1 is the highest one, and the tuning
3659 defaults to the standard guitar tuning (with 6 strings). The notes
3660 are printed as tablature, by using @internalsref{TabStaff} and
3661 @internalsref{TabVoice} contexts:
3663 @lilypond[fragment,verbatim]
3664 \notes \context TabStaff {
3670 When no string is specified, the first string that does not give a
3671 fret number less than @code{minimumFret} is selected. The default
3672 value for @code{minimumFret} is 0:
3676 e8 fis gis a b cis' dis' e'
3677 \property TabStaff.minimumFret = #8
3678 e8 fis gis a b cis' dis' e'
3683 e8 fis gis a b cis' dis' e'
3684 \property TabStaff.minimumFret = #8
3685 e8 fis gis a b cis' dis' e'
3688 \context StaffGroup <<
3689 \context Staff { \clef "G_8" \frag }
3690 \context TabStaff { \frag }
3697 @internalsref{TabStaff}, @internalsref{TabVoice}, and
3698 @internalsref{StringNumberEvent}.
3702 Chords are not handled in a special way, and hence the automatic
3703 string selector may easily select the same string to two notes in a
3707 @node Non-guitar tablatures
3708 @subsection Non-guitar tablatures
3709 @cindex Non-guitar tablatures
3711 You can change the number of strings, by setting the number of lines
3712 in the @internalsref{TabStaff} (the @code{line-count} property of
3713 @internalsref{TabStaff} can only be changed using
3714 @code{\applyoutput}, for more information, see @ref{Tuning
3717 You can change the tuning of the strings. A string tuning is given as
3718 a Scheme list with one integer number for each string, the number
3719 being the pitch (measured in semitones relative to central C) of an
3720 open string. The numbers specified for @code{stringTuning} are the
3721 numbers of semitones to subtract or add, starting the specified pitch
3722 by default middle C, in string order. Thus, the notes are e, a, d, and
3725 @lilypond[fragment,verbatim]
3726 \context TabStaff <<
3728 \applyoutput #(outputproperty-compatibility (make-type-checker 'staff-symbol-interface)
3730 \property TabStaff.stringTunings = #'(-5 -10 -15 -20)
3733 a,4 c' a e' e c' a e'
3738 It is possible to change the Scheme function to format the tablature
3739 note text. The default is @code{fret-number-tablature-format}, which
3740 uses the fret number. For instruments that do not use this notation,
3741 you can create a special tablature formatting function. This function
3742 takes three argument: string number, string tuning and note pitch.
3746 No guitar special effects have been implemented.
3751 @section Chord names
3754 LilyPond has support for both printing chord names. Chords may be
3755 entered in musical chord notation, i.e. @code{< .. >}, but they can
3756 also be entered by name. Internally, the chords are represented as a
3757 set of pitches, so they can be transposed:
3760 @lilypond[verbatim,singleline]
3761 twoWays = \notes \transpose c c' {
3771 << \context ChordNames \twoWays
3772 \context Voice \twoWays >> }
3775 This example also shows that the chord printing routines do not try to
3776 be intelligent. The last chord (@code{f bes d}) is not interpreted as
3782 * Printing chord names::
3787 @subsection Chords mode
3790 Chord mode is a mode where you can input sets of pitches using common
3791 names. It is introduced by the keyword @code{\chords}.
3792 In chords mode, a chord is entered by the root, which is entered
3793 like a common pitch:
3794 @lilypond[fragment,verbatim,quote, relative=1]
3795 \chords { es4. d8 c2 }
3800 Other chords may be entered by suffixing a colon, and introducing a
3801 modifier, and optionally, a number:
3803 @lilypond[fragment,verbatim,quote]
3804 \chords { e1:m e1:7 e1:m7 }
3806 The first number following the root is taken to be the `type' of the
3807 chord, thirds are added to the root until it reaches the specified
3809 @lilypond[fragment,verbatim]
3810 \chords { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 }
3813 @cindex root of chord
3814 @cindex additions, in chords
3815 @cindex removals, in chords
3817 More complex chords may also be constructed adding separate steps
3818 to a chord. Additions are added after the number following
3819 the colon, and are separated by dots:
3821 @lilypond[verbatim,fragment,quote]
3822 \chords { c:5.6 c:3.7.8 c:3.6.13 }
3824 Chord steps can be altered by suffixing a @code{-} or @code{+} sign
3826 @lilypond[verbatim,fragment,quote]
3827 \chords { c:7+ c:5+.3- c:3-.5-.7- }
3829 Removals are specified similarly, and are introduced by a caret. They
3830 must come after the additions:
3831 @lilypond[verbatim,fragment]
3832 \chords { c^3 c:7^5 c:9^3.5 }
3835 Modifiers can be used to change pitches. The following modifiers are
3839 is the minor chord. This modifier lowers the 3rd and (if present) the 7th step.
3841 is the diminished chord. This modifier lowers the 3rd, 5th and (if present)
3844 is the augmented chord. This modifier raises the 5th step.
3846 is the major 7th chord. This modifier raises the 7th step if present.
3848 is the suspended 4th or 2nd. This modifier removes the 3rd
3849 step. Append either @code{2} or @code{4} to add the 2nd or 4th step to
3852 Modifiers can be mixed with additions:
3853 @lilypond[verbatim,fragment]
3854 \chords { c:sus4 c:7sus4 c:dim7 c:m6 }
3857 @cindex modifiers, in chords.
3864 Since an unaltered 11 does not sound good when combined with an
3865 unaltered 13, the 11 is removed in this case (unless it is added
3868 @lilypond[fragment,verbatim]
3869 \chords { c:13 c:13.11 c:m13 }
3874 An inversion (putting one pitch of the chord on the bottom), as well
3875 as bass notes, can be specified by appending
3876 @code{/}@var{pitch} to the chord:
3877 @lilypond[fragment,verbatim,center]
3878 \chords { c1 c/g c/f }
3882 A bass note can be added instead of transposed out of the chord,
3883 by using @code{/+}@var{pitch}.
3885 @lilypond[fragment,verbatim,center]
3886 \chords { c1 c/+g c/+f }
3889 Chords is a mode similar to @code{\lyrics}, @code{\notes} etc. Most
3890 of the commands continue to work, for example, @code{r} and
3891 @code{\skip} can be used to insert rests and spaces, and
3892 @code{\property} may be used to change various settings.
3898 Each step can only be present in a chord once. The following
3899 simply produces the augmented chord, since @code{5+} is interpreted
3902 @lilypond[verbatim,fragment]
3903 \chords { c:5.5-.5+ }
3907 @node Printing chord names
3908 @subsection Printing chord names
3910 @cindex printing chord names
3914 For displaying printed chord names, use the @internalsref{ChordNames} context.
3915 The chords may be entered either using the notation
3916 described above, or directly using @code{<} and @code{>}:
3918 @lilypond[verbatim,singleline]
3920 \chords {a1 b c} <d' f' a'> <e' g' b'>
3924 \context ChordNames \scheme
3925 \context Staff \scheme
3930 You can make the chord changes stand out by setting
3931 @internalsref{ChordNames}.@code{chordChanges} to true. This will only
3932 display chord names when there is a change in the chords scheme and at
3933 the start of a new line:
3935 @lilypond[verbatim, linewidth=9cm]
3937 c1:m c:m \break c:m c:m d
3941 \context ChordNames {
3942 \property ChordNames.chordChanges = ##t
3944 \context Staff \transpose c c' \scheme
3949 The default chord name layout is a system for Jazz music, proposed by
3950 Klaus Ignatzek (see @ref{Literature list}). It can be tuned through the
3951 following properties:
3954 @cindex chordNameExceptions
3955 @item chordNameExceptions
3956 This is a list that contains the chords that have special formatting.
3958 @inputfileref{input/regression,chord-name-exceptions.ly}.
3959 @cindex exceptions, chord names.
3962 @cindex majorSevenSymbol
3963 @item majorSevenSymbol
3964 This property contains the markup object used for the 7th step, when
3965 it is major. Predefined options are @code{whiteTriangleMarkup} and
3966 @code{blackTriangleMarkup}. See
3967 @inputfileref{input/regression,chord-name-major7.ly} for an example.
3969 @cindex chordNameSeparator
3970 @item chordNameSeparator
3971 Different parts of a chord name are normally separated by a
3972 slash. By setting @code{chordNameSeparator}, you can specify other
3974 @lilypond[fragment,verbatim]
3975 \context ChordNames \chords {
3977 \property ChordNames.chordNameSeparator
3978 = \markup { \typewriter "|" }
3982 @cindex chordRootNamer
3983 @item chordRootNamer
3984 The root of a chord is usually printed as a letter with an optional
3985 alteration. The transformation from pitch to letter is done by this
3986 function. Special note names (for example, the German ``H'' for a
3987 B-chord) can be produced by storing a new function in this property.
3989 The pre-defined variables @code{\germanChords},
3990 @code{\semiGermanChords} set these variables.
3993 @cindex chordNoteNamer
3994 @item chordNoteNamer
3995 The default is to print single pitch, e.g. the bass note, using the
3996 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
3997 to a specialized function to change this behavior. For example, the
3998 base can be printed in lower case.
4003 There are also two other chord name schemes implemented: an alternate
4004 Jazz chord notation, and a systematic scheme called Banter chords. The
4005 alternate jazz notation is also shown on the chart in @ref{Chord name
4006 chart}. Turning on these styles is described in the input file
4007 @inputfileref{input/test,chord-names-jazz.ly}.
4011 @cindex chords, jazz
4016 @cindex @code{\germanChords}
4017 @code{\germanChords},
4018 @cindex @code{\semiGermanChords}
4019 @code{\semiGermanChords}.
4026 @inputfileref{input/regression,chord-name-major7.ly},
4027 @inputfileref{input/regression,chord-name-exceptions.ly},
4028 @inputfileref{input/test,chord-names-jazz.ly},
4029 @inputfileref{input/test,chord-names-german.ly},
4030 @file{scm/chords-ignatzek.scm}, and @file{scm/chord-entry.scm}.
4035 Chord names are determined solely from the list of pitches. Chord
4036 inversions are not identified, and neither are added bass notes. This
4037 may result in strange chord names when chords are entered with the
4038 @code{< .. >} syntax.
4043 @node Orchestral music
4044 @section Orchestral music
4046 @cindex Writing parts
4048 Orchestral music involves some special notation, both in the full
4049 score and the individual parts. This section explains how to tackle
4050 some common problems in orchestral music.
4055 * Multiple staff contexts::
4058 * Instrument names::
4060 * Multi measure rests::
4061 * Automatic part combining::
4063 * Different editions from one source::
4064 * Sound output for transposing instruments::
4067 @node Multiple staff contexts
4068 @subsection Multiple staff contexts
4070 Polyphonic scores consist of many staves. These staves can be
4071 constructed in three different ways:
4073 @item The group is started with a brace at the left. This is done with the
4074 @internalsref{GrandStaff} context.
4075 @item The group is started with a bracket. This is done with the
4076 @internalsref{StaffGroup} context
4077 @item The group is started with a vertical line. This is the default
4081 @cindex Staff, multiple
4082 @cindex bracket, vertical
4083 @cindex brace, vertical
4090 @node Rehearsal marks
4091 @subsection Rehearsal marks
4092 @cindex Rehearsal marks
4094 @cindex @code{\mark}
4096 To print a rehearsal mark, use the @code{\mark} command:
4097 @lilypond[fragment,verbatim]
4107 The mark is incremented automatically if you use @code{\mark
4108 \default}. The value to use is stored in the property
4109 @code{rehearsalMark} is used and automatically incremented.
4111 The @code{\mark} command can also be used to put signs like coda,
4112 segno and fermatas on a barline. Use @code{\markup} to
4113 to access the appropriate symbol:
4115 @lilypond[fragment,verbatim,relative=1]
4116 c1 \mark \markup { \musicglyph #"scripts-ufermata" }
4120 In this case, during line breaks,
4121 marks must also be printed at the end of the line, and not at the
4122 beginning. Use the following to force that behavior:
4124 \property Score.RehearsalMark \override
4125 #'break-visibility = #begin-of-line-invisible
4128 See @inputfileref{input/test,boxed-molecule.ly} for putting boxes
4134 @cindex barlines, putting symbols on
4138 @internalsref{MarkEvent}, @internalsref{RehearsalMark}, and
4139 @inputfileref{input/test,boxed-molecule.ly}.
4143 @subsection Bar numbers
4147 @cindex measure numbers
4148 @cindex currentBarNumber
4150 Bar numbers are printed by default at the start of the line. The
4151 number itself is stored in the
4152 @code{currentBarNumber} property,
4153 which is normally updated automatically for every measure.
4155 Bar numbers can be typeset at regular intervals instead of at the
4156 beginning of each line. This is illustrated in the following example,
4157 whose source is available as
4158 @inputfileref{input/test,bar-number-regular-interval.ly}:
4160 @lilypondfile[notexidoc]{bar-number-regular-interval.ly}
4165 @internalsref{BarNumber},
4166 @inputfileref{input/test,bar-number-every-five-reset.ly}, and
4167 @inputfileref{input/test,bar-number-regular-interval.ly}.
4171 Bar numbers can collide with the @internalsref{StaffGroup} bracket, if
4172 there is one at the top. To solve this, the
4173 @code{padding} property of @internalsref{BarNumber} can be
4174 used to position the number correctly.
4176 @node Instrument names
4177 @subsection Instrument names
4179 In an orchestral score, instrument names are printed left side of the
4182 This can be achieved by setting @internalsref{Staff}.@code{instrument}
4183 and @internalsref{Staff}.@code{instr}. This will print a string before
4184 the start of the staff. For the first start, @code{instrument} is
4185 used, for the next ones @code{instr} is used:
4188 @lilypond[verbatim,singleline]
4189 \property Staff.instrument = "ploink " { c''4 }
4193 You can also use markup texts to construct more complicated instrument
4197 @lilypond[fragment,verbatim,singleline]
4199 \property Staff.instrument = \markup {
4200 \column < "Clarinetti"
4202 \smaller \musicglyph #"accidentals--1"
4213 @internalsref{InstrumentName}.
4217 When you put a name on a grand staff or piano staff the width of the
4218 brace is not taken into account. You must add extra spaces to the end of
4219 the name to avoid a collision.
4222 @subsection Transpose
4224 @cindex transposition of pitches
4225 @cindex @code{\transpose}
4227 A music expression can be transposed with @code{\transpose}. The syntax
4230 \transpose @var{from} @var{to} @var{musicexpr}
4233 This means that @var{musicexpr} is transposed by the interval
4234 between @var{from} and @var{to}.
4236 @code{\transpose} distinguishes between enharmonic pitches: both
4237 @code{\transpose c cis} or @code{\transpose c des} will transpose up
4238 half a tone. The first version will print sharps and the second
4239 version will print flats:
4241 @lilypond[singleline, verbatim]
4242 mus =\notes { \key d \major cis d fis g }
4243 \score { \notes \context Staff {
4246 \transpose c g' \mus
4247 \transpose c f' \mus
4253 @internalsref{TransposedMusic}, and @internalsref{UntransposableMusic}.
4257 If you want to use both @code{\transpose} and @code{\relative}, then
4258 you must put @code{\transpose} outside of @code{\relative}, since
4259 @code{\relative} will have no effect music that appears inside a
4265 @node Multi measure rests
4266 @subsection Multi measure rests
4267 @cindex multi measure rests
4268 @cindex Rests, multi measure
4272 Multi measure rests are entered using `@code{R}'. It is specifically
4273 meant for full bar rests and for entering parts: the rest can expand
4274 to fill a score with rests, or it can be printed as a single
4275 multimeasure rest. This expansion is controlled by the property
4276 @code{Score.skipBars}. If this is set to true, empty measures will not
4277 be expanded, and the appropriate number is added automatically:
4279 @lilypond[fragment,verbatim]
4280 \time 4/4 r1 | R1 | R1*2
4281 \property Score.skipBars = ##t R1*17 R1*4
4284 The @code{1} in @code{R1} is similar to the duration notation used for
4285 notes. Hence, for time signatures other than 4/4, you must enter other
4286 durations. This can be done with augmentation dots or fractions:
4288 @lilypond[fragment,verbatim]
4289 \property Score.skipBars = ##t
4297 An @code{R} spanning a single measure is printed as either a whole rest
4298 or a breve, centered in the measure regardless of the time signature.
4300 @cindex text on multi-measure rest
4301 @cindex script on multi-measure rest
4302 @cindex fermata on multi-measure rest
4304 Texts can be added to multi-measure rests by using the
4305 @var{note}-@code{markup} syntax (see @ref{Text markup}). In this case, the number is
4306 replaced. If you need both texts and the number, you must add the
4307 number by hand. A variable (@code{\fermataMarkup}) is provided for
4311 @lilypond[verbatim,fragment]
4313 R2._\markup { "Ad lib" }
4318 @cindex whole rests for a full measure
4322 @internalsref{MultiMeasureRestEvent},
4323 @internalsref{MultiMeasureTextEvent},
4324 @internalsref{MultiMeasureRestMusicGroup}, and
4325 @internalsref{MultiMeasureRest}.
4327 The layout object @internalsref{MultiMeasureRestNumber} is for the
4328 default number, and @internalsref{MultiMeasureRestText} for user
4333 It is not possible to use fingerings (e.g. @code{R1-4}) to put numbers
4334 over multi-measure rests.
4336 @cindex condensing rests
4338 There is no way to automatically condense multiple rests into a single
4339 multimeasure rest. Multi measure rests do not take part in rest
4342 Be careful when entering multimeasure rests followed by whole
4343 notes. The following will enter two notes lasting four measures each:
4347 When @code{skipBars} is set, then the result will look OK, but the
4348 bar numbering will be off.
4350 @node Automatic part combining
4351 @subsection Automatic part combining
4352 @cindex automatic part combining
4353 @cindex part combiner
4356 Automatic part combining is used to merge two parts of music onto a
4357 staff. It is aimed at typesetting orchestral scores. When the two
4358 parts are identical for a period of time, only one is shown. In
4359 places where the two parts differ, they are typeset as separate
4360 voices, and stem directions are set automatically. Also, solo and
4361 @emph{a due} parts are identified and can be marked.
4365 The syntax for part combining is
4368 \partcombine @var{context} @var{musicexpr1} @var{musicexpr2}
4370 where the pieces of music @var{musicexpr1} and @var{musicexpr2} will be
4371 combined into one context of type @var{context}. The music expressions
4372 must be interpreted by contexts whose names should start with @code{one}
4375 The following example demonstrates the basic functionality of the part
4376 combiner: putting parts on one staff, and setting stem directions and
4379 @lilypond[verbatim,singleline,fragment]
4381 \context Voice=one \partcombine Voice
4382 \context Thread=one \relative c'' {
4385 \context Thread=two \relative c'' {
4391 The first @code{g} appears only once, although it was
4392 specified twice (once in each part). Stem, slur and tie directions are
4393 set automatically, depending whether there is a solo or unisono. The
4394 first part (with context called @code{one}) always gets up stems, and
4395 `solo', while the second (called @code{two}) always gets down stems and
4398 If you just want the merging parts, and not the textual markings, you
4399 may set the property @var{soloADue} to false:
4401 @lilypond[verbatim,singleline,fragment]
4403 \property Staff.soloADue = ##f
4404 \context Voice=one \partcombine Voice
4405 \context Thread=one \relative c'' {
4408 \context Thread=two \relative c'' {
4416 @internalsref{PartCombineMusic},
4417 @internalsref{Thread_devnull_engraver}, and
4418 @internalsref{Voice_devnull_engraver} and @internalsref{A2_engraver}.
4422 The syntax for naming contexts in inconsistent with the syntax for
4425 In @code{soloADue} mode, when the two voices play the same notes on and
4426 off, the part combiner may typeset @code{a2} more than once in a
4429 @lilypond[fragment,singleline]
4431 \context Voice=one \partcombine Voice
4432 \context Thread=one \relative c'' {
4435 \context Thread=two \relative c'' {
4441 The part combiner is rather buggy, and it will be replaced by a better
4442 mechanism in the near future.
4444 @cindex @code{Thread_devnull_engraver}
4445 @cindex @code{Voice_engraver}
4446 @cindex @code{A2_engraver}
4449 @subsection Hiding staves
4451 @cindex Frenched scores
4452 @cindex Hiding staves
4454 In orchestral scores, staff lines that only have rests are usually
4455 removed. This saves some space. This style is called `French Score'.
4456 For @internalsref{Lyrics}, @internalsref{LyricsVoice},
4457 @internalsref{ChordNames} and @internalsref{FiguredBass}, this is
4458 switched on by default. When these line of these contexts turn out
4459 empty after the line-breaking process, they are removed.
4461 For normal staves, a specialized @internalsref{Staff} context is
4462 available, which does the same: staves containing nothing (or only
4463 multi measure rests) are removed. The context definition is stored in
4464 @code{\RemoveEmptyStaffContext} variable. Observe how the second staff
4465 in this example disappears in the second line:
4470 \notes \relative c' <<
4471 \new Staff { e4 f g a \break c1 }
4472 \new Staff { c4 d e f \break R1 }
4476 \translator { \RemoveEmptyStaffContext }
4481 The first page shows all staffs in full. If they should be removed
4482 from the first page too, set @code{remove-first} to false
4483 in @internalsref{RemoveEmptyVerticalGroup}.
4485 @node Different editions from one source
4486 @subsection Different editions from one source
4488 The @code{\tag} command marks music expressions with a name. These
4489 tagged expressions can be filtered out later. With this mechanism it
4490 is possible to make different versions of the same music source.
4492 In the following example, we see two versions of a piece of music, one
4493 for the full score, and one with cue notes for the instrumental part:
4501 \property Voice.fontSize = #-1
4509 The same can be applied to articulations, texts, etc.: they are
4512 -\tag #@var{your-tag}
4514 to an articulation, for example,
4519 This defines a note with a conditional fingering indication.
4521 By applying the @code{remove-tag} function, tagged expressions can be
4522 filtered. For example,
4526 \apply #(remove-tag 'score) @var{the music}
4527 \apply #(remove-tag 'part) @var{the music}
4532 @lilypondfile[notexidoc]{tag-filter.ly}
4534 The argument of the @code{\tag} command should be a symbol, or a list
4535 of symbols, for example,
4537 \tag #'(original-part transposed-part) @dots{}
4542 @inputfileref{input/regression,tag-filter.ly}
4545 @node Sound output for transposing instruments
4546 @subsection Sound output for transposing instruments
4548 When you want to make a MIDI file from a score containing transposed
4549 and untransposed instruments, you have to instruct LilyPond the pitch
4550 offset (in semitones) for the transposed instruments. This is done
4551 using the @code{transposing} property. It does not affect printed
4554 @cindex @code{transposing}
4557 \property Staff.instrument = #"Cl. in B-flat"
4558 \property Staff.transposing = #-2
4562 @node Ancient notation
4563 @section Ancient notation
4565 @cindex Vaticana, Editio
4566 @cindex Medicaea, Editio
4571 @c [TODO: write more comprehensive introduction on ancient notation]
4573 Support for ancient notation is still under heavy development.
4574 Regardless of all of the current limitations (see the bugs section
4575 below for details), it includes features for mensural
4576 notation and Gregorian Chant notation. There is also limited support
4577 for figured bass notation.
4579 Many graphical objects provide a @code{style} property, see
4580 @ref{Ancient note heads}, @ref{Ancient accidentals}, @ref{Ancient
4581 rests}, @ref{Ancient clefs}, @ref{Ancient flags} and @ref{Ancient time
4582 signatures}. By manipulating such a grob property, the typographical
4583 appearance of the affected graphical objects can be accomodated for a
4584 specific notation flavour without need for introducing any new
4588 Other aspects of ancient notation can not that easily be expressed as
4589 in terms of just changing a style property of a graphical object.
4590 Therefore, some notational concepts are introduced specifically for
4591 ancient notation, see @ref{Custodes}, @ref{Divisiones},
4592 @ref{Ligatures}, and @ref{Figured bass}.
4596 * Ancient note heads::
4597 * Ancient accidentals::
4601 * Ancient time signatures::
4606 * Vaticana style contexts::
4609 If this all is way too much of documentation for you, and you just
4610 want to dive into typesetting without worrying too much about the
4611 details on how to customize a context, then you may have a look at the
4612 predefined contexts (see @ref{Vaticana style contexts}). Use them to
4613 set up predefined style-specific voice and staff contexts, and
4614 directly go ahead with the note entry.
4618 Ligatures need special spacing that has not yet been implemented. As
4619 a result, there is too much space between ligatures most of the time,
4620 and line breaking often is unsatisfactory. Also, lyrics do not
4621 correctly align with ligatures.
4623 Accidentals must not be printed within a ligature, but instead need to
4624 be collected and printed in front of it.
4626 Augmentum dots within ligatures are not handled correctly.
4629 @node Ancient note heads
4630 @subsection Ancient note heads
4636 For ancient notation, a note head style other than the @code{default}
4637 style may be chosen. This is accomplished by setting the @code{style}
4638 property of the NoteHead object to the desired value (@code{baroque},
4639 @code{neo_mensural} or @code{mensural}). The @code{baroque} style
4640 differs from the @code{default} style only in using a square shape for
4641 @code{\breve} note heads. The @code{neo_mensural} style differs from
4642 the @code{baroque} style in that it uses rhomboidal heads for whole
4643 notes and all smaller durations. Stems are centered on the note
4644 heads. This style is in particular useful when transcribing mensural
4645 music, e.g. for the incipit. The @code{mensural} style finally
4646 produces note heads that mimick the look of note heads in historic
4647 printings of the 16th century.
4649 The following example demonstrates the @code{neo_mensural} style:
4651 @lilypond[fragment,singleline,verbatim]
4652 \property Voice.NoteHead \set #'style = #'neo_mensural
4653 a'\longa a'\breve a'1 a'2 a'4 a'8 a'16
4656 When typesetting a piece in Gregorian Chant notation, a Gregorian
4657 ligature engraver will automatically select the proper note heads,
4658 such there is no need to explicitly set the note head style. Still,
4659 the note head style can be set e.g. to @code{vaticana_punctum} to
4660 produce punctum neumes. Similarly, a mensural ligature engraver is
4661 used to automatically assemble mensural ligatures. See
4662 @ref{Ligatures} for how ligature engravers work.
4666 @inputfileref{input/regression,note-head-style.ly} gives an overview
4667 over all available note head styles.
4669 @ref{Percussion staves} use note head styles of their own that are
4670 frequently used in contemporary music notation.
4672 @node Ancient accidentals
4673 @subsection Ancient accidentals
4679 Use the @code{style} property of grob @internalsref{Accidental} to
4680 select ancient accidentals. Supported styles are
4681 @code{mensural}, @code{vaticana}, @code{hufnagel} and @code{medicaea}.
4683 @lilypond[singleline,26pt]
4691 { " " \musicglyph #"accidentals-vaticana-1"
4692 " " \musicglyph #"accidentals-vaticana0" }
4696 { " " \musicglyph #"accidentals-medicaea-1" }
4700 { " " \musicglyph #"accidentals-hufnagel-1" }
4704 { " " \musicglyph #"accidentals-mensural-1"
4705 " " \musicglyph #"accidentals-mensural1" }
4714 \remove "Bar_number_engraver"
4718 \remove "Clef_engraver"
4719 \remove "Key_engraver"
4720 \remove "Time_signature_engraver"
4721 \remove "Staff_symbol_engraver"
4722 minimumVerticalExtent = ##f
4728 As shown, not all accidentals are supported by each style. When
4729 trying to access an unsupported accidental, LilyPond will switch to a
4730 different style, as demonstrated in
4731 @inputfileref{input/test,ancient-accidentals.ly}.
4733 Similarly to local accidentals, the style of the key signature can be
4734 controlled by the @code{style} property of the
4735 @internalsref{KeySignature} grob.
4739 @ref{Pitches}, @ref{Chromatic alterations} and @ref{Accidentals} give
4740 a general introduction into the use of accidentals. @ref{Key
4741 signature} gives a general introduction into the use of key
4746 @subsection Ancient rests
4752 Use the @code{style} property of grob @internalsref{Rest} to select
4753 ancient accidentals. Supported styles are @code{classical},
4754 @code{neo_mensural} and @code{mensural}. @code{classical} differs
4755 from the @code{default} style only in that the quarter rest looks like
4756 a horizontally mirrored 8th rest. The @code{neo_mensural} style suits
4757 well for e.g. the incipit of a transcribed mensural piece of music.
4758 The @code{mensural} style finally mimicks the appearance of rests as
4759 in historic prints of the 16th century.
4761 The following example demonstrates the @code{neo_mensural} style:
4763 @lilypond[fragment,singleline,verbatim]
4764 \property Voice.Rest \set #'style = #'neo_mensural
4765 r\longa r\breve r1 r2 r4 r8 r16
4768 There are no 32th and 64th rests specifically for the mensural or
4769 neo-mensural style. Instead, the rests from the default style will be
4770 taken. See @inputfileref{input/test,rests.ly} for a chart of all
4773 There are no rests in Gregorian Chant notation; instead, it uses
4778 @ref{Rests} gives a general introduction into the use of rests.
4782 @subsection Ancient clefs
4788 LilyPond supports a variety of clefs, many of them ancient.
4790 The following table shows all ancient clefs that are supported via the
4791 @code{\clef} command. Some of the clefs use the same glyph, but
4792 differ only with respect to the line they are printed on. In such
4793 cases, a trailing number in the name is used to enumerate these clefs.
4794 Still, you can manually force a clef glyph to be typeset on an
4795 arbitrary line, as described in @ref{Clef}. The note printed to the
4796 right side of each clef in the example column denotes the @code{c'}
4797 with respect to that clef.
4799 @multitable @columnfractions .3 .3 .3 .1
4803 @b{Description} @tab
4804 @b{Supported Clefs} @tab
4808 @code{clefs-neo_mensural_c} @tab
4809 modern style mensural C clef @tab
4810 @code{neo_mensural_c1}, @code{neo_mensural_c2},
4811 @code{neo_mensural_c3}, @code{neo_mensural_c4} @tab
4812 @lilypond[relative 0, notime]
4813 \property Staff.TimeSignature \set #'transparent = ##t
4814 \clef "neo_mensural_c2" c
4818 @code{clefs-petrucci_c1}
4819 @code{clefs-petrucci_c2}
4820 @code{clefs-petrucci_c3}
4821 @code{clefs-petrucci_c4}
4822 @code{clefs-petrucci_c5}
4825 petrucci style mensural C clefs, for use on different stafflines
4826 (the examples shows the 2nd staffline C clef).
4836 @lilypond[relative 0, notime]
4837 \property Staff.TimeSignature \set #'transparent = ##t
4838 \clef "petrucci_c2" c
4842 @code{clefs-petrucci_f} @tab
4843 petrucci style mensural F clef @tab
4844 @code{petrucci_f} @tab
4845 @lilypond[relative 0, notime]
4846 \property Staff.TimeSignature \set #'transparent = ##t
4847 \clef "petrucci_f" c
4851 @code{clefs-petrucci_g} @tab
4852 petrucci style mensural G clef @tab
4853 @code{petrucci_g} @tab
4854 @lilypond[relative 0, notime]
4855 \property Staff.TimeSignature \set #'transparent = ##t
4856 \clef "petrucci_g" c
4860 @code{clefs-mensural_c} @tab
4861 historic style mensural C clef @tab
4862 @code{mensural_c1}, @code{mensural_c2}, @code{mensural_c3},
4863 @code{mensural_c4} @tab
4864 @lilypond[relative 0, notime]
4865 \property Staff.TimeSignature \set #'transparent = ##t
4866 \clef "mensural_c2" c
4870 @code{clefs-mensural_f} @tab
4871 historic style mensural F clef @tab
4872 @code{mensural_f} @tab
4873 @lilypond[relative 0, notime]
4874 \property Staff.TimeSignature \set #'transparent = ##t
4875 \clef "mensural_f" c
4879 @code{clefs-mensural_g} @tab
4880 historic style mensural G clef @tab
4881 @code{mensural_g} @tab
4882 @lilypond[relative 0, notime]
4883 \property Staff.TimeSignature \set #'transparent = ##t
4884 \clef "mensural_g" c
4888 @code{clefs-vaticana_do} @tab
4889 Editio Vaticana style do clef @tab
4890 @code{vaticana_do1}, @code{vaticana_do2}, @code{vaticana_do3} @tab
4891 @lilypond[relative 0, notime]
4893 \applyoutput #(outputproperty-compatibility (make-type-checker 'staff-symbol-interface) 'line-count 4)
4894 \property Staff.TimeSignature \set #'transparent = ##t
4895 \clef "vaticana_do2" c
4899 @code{clefs-vaticana_fa} @tab
4900 Editio Vaticana style fa clef @tab
4901 @code{vaticana_fa1}, @code{vaticana_fa2} @tab
4902 @lilypond[relative 0, notime]
4904 \applyoutput #(outputproperty-compatibility (make-type-checker 'staff-symbol-interface) 'line-count 4)
4905 \property Staff.TimeSignature \set #'transparent = ##t
4906 \clef "vaticana_fa2" c
4910 @code{clefs-medicaea_do} @tab
4911 Editio Medicaea style do clef @tab
4912 @code{medicaea_do1}, @code{medicaea_do2}, @code{medicaea_do3} @tab
4913 @lilypond[relative 0, notime]
4915 \applyoutput #(outputproperty-compatibility (make-type-checker 'staff-symbol-interface) 'line-count 4)
4916 \property Staff.TimeSignature \set #'transparent = ##t
4917 \clef "medicaea_do2" c
4921 @code{clefs-medicaea_fa} @tab
4922 Editio Medicaea style fa clef @tab
4923 @code{medicaea_fa1}, @code{medicaea_fa2} @tab
4924 @lilypond[relative 0, notime]
4926 \applyoutput #(outputproperty-compatibility (make-type-checker 'staff-symbol-interface) 'line-count 4)
4927 \property Staff.TimeSignature \set #'transparent = ##t
4928 \clef "medicaea_fa2" c
4932 @code{clefs-hufnagel_do} @tab
4933 historic style hufnagel do clef @tab
4934 @code{hufnagel_do1}, @code{hufnagel_do2}, @code{hufnagel_do3} @tab
4935 @lilypond[relative 0, notime]
4937 \applyoutput #(outputproperty-compatibility (make-type-checker 'staff-symbol-interface) 'line-count 4)
4938 \property Staff.TimeSignature \set #'transparent = ##t
4939 \clef "hufnagel_do2" c
4943 @code{clefs-hufnagel_fa} @tab
4944 historic style hufnagel fa clef @tab
4945 @code{hufnagel_fa1}, @code{hufnagel_fa2} @tab
4946 @lilypond[relative 0, notime]
4948 \applyoutput #(outputproperty-compatibility (make-type-checker 'staff-symbol-interface) 'line-count 4)
4949 \property Staff.TimeSignature \set #'transparent = ##t
4950 \clef "hufnagel_fa2" c
4954 @code{clefs-hufnagel_do_fa} @tab
4955 historic style hufnagel combined do/fa clef @tab
4956 @code{hufnagel_do_fa} @tab
4957 @lilypond[relative 0, notime]
4958 \property Staff.TimeSignature \set #'transparent = ##t
4959 \clef "hufnagel_do_fa" c
4964 @c --- This should go somewhere else: ---
4965 @c @item modern style percussion clef (glyph: @code{clefs-percussion})
4968 @c @code{percussion}
4970 @c @lilypond{\property Staff.TimeSignature \set #'transparent = ##t \clef "percussion" c'}
4972 @c @item modern style tab clef (glyph: @code{clefs-tab})
4977 @c @lilypond{\context Staff \outputproperty #(make-type-checker 'staff-symbol-interface) #'line-count = #6 \property Staff.TimeSignature \set #'transparent = ##t \clef "tab" c'}
4979 @emph{Modern style} means ``as is typeset in contemporary editions of
4980 transcribed mensural music''.
4982 @emph{Petrucci style} means ``inspired by printings published by the
4983 famous engraver Petrucci (1466-1539)''.
4985 @emph{Historic style} means ``as was typeset or written in historic
4986 editions (other than those of Petrucci)''.
4988 @emph{Editio XXX style} means ``as is/was printed in Editio XXX''.
4990 Petrucci used C clefs with differently balanced left-side vertical
4991 beams, depending on which staffline it is printed.
4995 For modern clefs, see @ref{Clef}. For the percussion clef, see
4996 @ref{Percussion staves}. For the @code{TAB} clef, see
5001 @subsection Ancient flags
5007 Use the @code{flag-style} property of grob @internalsref{Stem} to
5008 select ancient flags. Besides the @code{default} flag style,
5009 only @code{mensural} style is supported:
5011 @lilypond[fragment,singleline,verbatim]
5012 \property Voice.Stem \set #'flag-style = #'mensural
5013 \property Voice.Stem \set #'thickness = #1.0
5014 \property Voice.NoteHead \set #'style = #'mensural
5016 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
5017 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
5020 Note that the innermost flare of each mensural flag always is
5021 vertically aligned with a staff line. If you do not like this
5022 behaviour, you can set the @code{adjust-if-on-staffline} property of
5023 grob @internalsref{Stem} to @code{##f}. Then, the vertical position
5024 of the end of each flare is different between notes on staff lines and
5025 notes between staff lines:
5027 @lilypond[fragment,singleline]
5028 \property Voice.Stem \set #'flag-style = #'mensural
5029 \property Voice.Stem \set #'thickness = #1.0
5030 \property Voice.Stem \set #'adjust-if-on-staffline = ##f
5031 \property Voice.NoteHead \set #'style = #'mensural
5033 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
5034 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
5037 There is no particular flag style for neo-mensural notation. Hence,
5038 when typesetting e.g. the incipit of a transcibed piece of mensural
5039 music, the default flag style should be used. There are no flags in
5040 Gregorian Chant notation.
5043 @node Ancient time signatures
5044 @subsection Ancient time signatures
5046 @cindex time signatures
5050 There is limited support for mensural time signatures. The
5051 glyphs are hard-wired to particular time fractions. In other words,
5052 to get a particular mensural signature glyph with the @code{\time n/m}
5053 command, @code{n} and @code{m} have to be chosen according to the
5059 \property Score.timing = ##f
5060 \property Score.barAlways = ##t
5061 s_\markup { "$\\backslash$time 4/4" }
5062 ^\markup { " " \musicglyph #"timesig-neo\_mensural4/4" }
5064 s_\markup { "$\\backslash$time 2/2" }
5065 ^\markup { " " \musicglyph #"timesig-neo\_mensural2/2" }
5067 s_\markup { "$\\backslash$time 6/4" }
5068 ^\markup { " " \musicglyph #"timesig-neo\_mensural6/4" }
5070 s_\markup { "$\\backslash$time 6/8" }
5071 ^\markup { " " \musicglyph #"timesig-neo\_mensural6/8" }
5073 s_\markup { "$\\backslash$time 3/2" }
5074 ^\markup { " " \musicglyph #"timesig-neo\_mensural3/2" }
5076 s_\markup { "$\\backslash$time 3/4" }
5077 ^\markup { " " \musicglyph #"timesig-neo\_mensural3/4" }
5079 s_\markup { "$\\backslash$time 9/4" }
5080 ^\markup { " " \musicglyph #"timesig-neo\_mensural9/4" }
5082 s_\markup { "$\\backslash$time 9/8" }
5083 ^\markup { " " \musicglyph #"timesig-neo\_mensural9/8" }
5085 s_\markup { "$\\backslash$time 4/8" }
5086 ^\markup { " " \musicglyph #"timesig-neo\_mensural4/8" }
5088 s_\markup { "$\\backslash$time 2/4" }
5089 ^\markup { " " \musicglyph #"timesig-neo\_mensural2/4" }
5097 \remove Staff_symbol_engraver
5098 \remove Clef_engraver
5099 \remove Time_signature_engraver
5105 Use the @code{style} property of grob @internalsref{TimeSignature} to
5106 select ancient time signatures. Supported styles are
5107 @code{neo_mensural} and @code{mensural}. The above table uses the
5108 @code{neo_mensural} style. This style is appropriate e.g. for the
5109 incipit of transcriptions of mensural pieces. The @code{mensural}
5110 style mimicks the look of historical printings of the 16th century.
5112 @inputfileref{input/test,time.ly} gives an overview over all available
5113 ancient and modern styles.
5117 @ref{Time signature} gives a general introduction into the use of time
5122 Mensural signature glyphs are mapped to time fractions in a
5123 hard-wired way. This mapping is sensible, but still arbitrary: given
5124 a mensural time signature, the time fraction represents a modern meter
5125 that usually will be a good choice when transcribing a mensural piece
5126 of music. For a particular piece of mensural music, however, the
5127 mapping may be unsatisfactory. In particular, the mapping assumes a
5128 fixed transcription of durations (e.g. brevis = half note in 2/2,
5129 i.e. 4:1). Some glyphs (such as the alternate glyph for 6/8 meter)
5130 are not at all accessible through the @code{\time} command.
5132 Mensural time signatures are supported typographically, but not yet
5133 musically. The internal representation of durations is
5134 based on a purely binary system; a ternary division such as 1 brevis =
5135 3 semibrevis (tempus perfectum) or 1 semibrevis = 3 minima (cum
5136 prolatione maiori) is not correctly handled: event times in ternary
5137 modes will be badly computed, resulting e.g. in horizontally
5138 misaligned note heads, and bar checks are likely to erroneously fail.
5140 The syntax and semantics of the @code{\time} command for mensural
5141 music is subject to change.
5144 @subsection Custodes
5149 A @emph{custos} (plural: @emph{custodes}; latin word for `guard') is a
5150 symbol that appears at the end of a staff. It anticipates the pitch
5151 of the first note(s) of the following line and thus helps the player
5152 or singer to manage line breaks during performance, thus enhancing
5153 readability of a score.
5155 Custodes were frequently used in music notation until the 17th
5156 century. Nowadays, they have survived only in a few particular forms
5157 of musical notation such as contemporary editions of Gregorian chant
5158 like the @emph{editio vaticana}. There are different custos glyphs
5159 used in different flavours of notational style.
5163 For typesetting custodes, just put a @internalsref{Custos_engraver} into the
5164 @internalsref{Staff} context when declaring the @code{\paper} block,
5165 as shown in the following example:
5171 \consists Custos_engraver
5172 Custos \override #'style = #'mensural
5177 The result looks like this:
5183 \property Staff.Custos \set #'style = #'mensural
5190 \consists Custos_engraver
5197 The custos glyph is selected by the @code{style} property. The styles
5198 supported are @code{vaticana}, @code{medicaea}, @code{hufnagel} and
5199 @code{mensural}. They are demonstrated in the following fragment:
5209 { " " \musicglyph #"custodes-vaticana-u0" }
5213 { " " \musicglyph #"custodes-medicaea-u0" }
5217 { " " \musicglyph #"custodes-hufnagel-u0" }
5221 { " " \musicglyph #"custodes-mensural-u0" }
5230 \remove "Bar_number_engraver"
5234 \remove "Clef_engraver"
5235 \remove "Key_engraver"
5236 \remove "Time_signature_engraver"
5237 \remove "Staff_symbol_engraver"
5238 minimumVerticalExtent = ##f
5244 If the boolean property @code{adjust-if-on-staffline} is set to
5245 @code{#t} (which it is by default), lily typesets slightly different
5246 variants of the custos glyph, depending on whether the custos, is
5247 typeset on or between stafflines. The glyph will
5248 optically fit well into the staff, with the appendage on the right of
5249 the custos always ending at the same vertical position between two
5250 stafflines regardless of the pitch. If you set
5251 @code{adjust-if-on-staffline} to @code{#f}, then
5252 a compromise between both forms is used.
5254 Just like stems can be attached to noteheads in two directions
5255 @emph{up} and @emph{down}, each custos glyph is available with its
5256 appendage pointing either up or down. If the pitch of a custos is
5257 above a selectable position, the appendage will point downwards; if
5258 the pitch is below this position, the appendage will point upwards.
5259 Use property @code{neutral-position} to select this position. By
5260 default, it is set to @code{0}, such that the neutral position is the
5261 center of the staff. Use property @code{neutral-direction} to control
5262 what happens if a custos is typeset on the neutral position itself.
5263 By default, this property is set to @code{-1}, such that the appendage
5264 will point downwards. If set to @code{1}, the appendage will point
5265 upwards. Other values such as @code{0} are reserved for future
5266 extensions and should not be used.
5270 @internalsref{Custos} and @inputfileref{input/regression,custos.ly}.
5274 @subsection Divisiones
5280 A @emph{divisio} (plural: @emph{divisiones}; latin word for
5281 `division') is a staff context symbol that is used to structure
5282 Gregorian music into phrases and sections. The musical meaning of
5283 @emph{divisio minima}, @emph{divisio maior} and @emph{divisio maxima}
5284 can be characterized as short, medium and long pause, somewhat like
5285 @ref{Breath marks}. The @emph{finalis} sign not only marks the end of
5286 a chant, but is also frequently used within a single
5287 antiphonal/responsorial chant to mark the end of each section.
5291 To use divisiones, include the file @code{gregorian-init.ly}. It
5292 contains definitions that you can apply by just inserting
5293 @code{\divisioMinima}, @code{\divisioMaior}, @code{\divisioMaxima},
5294 and @code{\finalis} at proper places in the input. Some editions use
5295 @emph{virgula} or @emph{caesura} instead of divisio minima.
5296 Therefore, @code{gregorian-init.ly} also defines @code{\virgula} and
5299 @lilypondfile[notexidoc]{divisiones.ly}
5303 @cindex @code{\virgula}
5305 @cindex @code{\caesura}
5307 @cindex @code{\divisioMinima}
5308 @code{\divisioMinima},
5309 @cindex @code{\divisioMaior}
5310 @code{\divisioMaior},
5311 @cindex @code{\divisioMaxima}
5312 @code{\divisioMaxima},
5313 @cindex @code{\finalis}
5318 @internalsref{BreathingSign}, @internalsref{BreathingSignEvent},
5319 @inputfileref{input/test,divisiones.ly}, and @ref{Breath marks}.
5322 @subsection Ligatures
5326 @c TODO: Should double check if I recalled things correctly when I wrote
5327 @c down the following paragraph by heart.
5329 In musical terminology, a ligature is a coherent graphical symbol that
5330 represents at least two distinct notes. Ligatures originally appeared
5331 in the manuscripts of Gregorian chant notation roughly since the 9th
5332 century as an allusion to the accent symbols of greek lyric poetry to
5333 denote ascending or descending sequences of notes. Both, the shape
5334 and the exact meaning of ligatures changed tremendously during the
5335 following centuries: In early notation, ligatures were used for
5336 monophonic tunes (Gregorian chant) and very soon denoted also the way
5337 of performance in the sense of articulation. With upcoming
5338 multiphony, the need for a metric system arised, since multiple voices
5339 of a piece have to be synchronized some way. New notation systems
5340 were invented that used the manifold shapes of ligatures to now denote
5341 rhythmical patterns (e.g. black mensural notation, mannered notation,
5342 ars nova). With the invention of the metric system of the white
5343 mensural notation, the need for ligatures to denote such patterns
5344 disappeared. Nevertheless, ligatures were still in use in the
5345 mensural system for a couple of decades until they finally disappeared
5346 during the late 16th / early 17th century. Still, ligatures have
5347 survived in contemporary editions of Gregorian chant such as the
5348 Editio Vaticana from 1905/08.
5352 Syntactically, ligatures are simply enclosed by @code{\[} and
5353 @code{\]}. Some ligature styles (such as Editio Vaticana) may need
5354 additional input syntax specific for this particular type of ligature.
5355 By default, the @internalsref{LigatureBracket} engraver just puts a
5356 square bracket above the ligature:
5358 @lilypond[singleline,verbatim]
5360 \notes \transpose c c' {
5368 To select a specific style of ligatures, a proper ligature engraver
5369 has to be added to the @internalsref{Voice} context, as explained in
5370 the following subsections. Only white mensural ligatures
5371 are supported with certain limitations. Support for Editio Vaticana
5372 will be added in the future.
5375 * White mensural ligatures::
5376 * Gregorian square neumes ligatures::
5379 @node White mensural ligatures
5380 @subsubsection White mensural ligatures
5382 @cindex Mensural ligatures
5383 @cindex White mensural ligatures
5385 There is limited support for white mensural ligatures. The
5386 implementation is still experimental; it may output strange
5387 warnings or even crash in some cases or produce weird results on more
5392 To engrave white mensural ligatures, in the paper block the
5393 @internalsref{Mensural_ligature_engraver} has to be put into the
5394 @internalsref{Voice} context, and remove the
5395 @internalsref{Ligature_bracket_engraver}:
5401 \remove Ligature_bracket_engraver
5402 \consists Mensural_ligature_engraver
5407 There is no additional input language to describe the shape of a
5408 white mensural ligature. The shape is rather determined solely from
5409 the pitch and duration of the enclosed notes. While this approach may
5410 take a new user a while to get accustomed, it has the great advantage
5411 that the full musical information of the ligature is known internally.
5412 This is not only required for correct MIDI output, but also allows for
5413 automatic transcription of the ligatures.
5418 \property Score.timing = ##f
5419 \property Score.defaultBarType = "empty"
5420 \property Voice.NoteHead \set #'style = #'neo_mensural
5421 \property Staff.TimeSignature \set #'style = #'neo_mensural
5423 \[ g\longa c\breve a\breve f\breve d'\longa \]
5425 \[ e1 f1 a\breve g\longa \]
5427 @lilypond[singleline]
5429 \notes \transpose c c' {
5430 \property Score.timing = ##f
5431 \property Score.defaultBarType = "empty"
5432 \property Voice.NoteHead \set #'style = #'neo_mensural
5433 \property Staff.TimeSignature \set #'style = #'neo_mensural
5435 \[ g\longa c\breve a\breve f\breve d'\longa \]
5437 \[ e1 f1 a\breve g\longa \]
5442 \remove Ligature_bracket_engraver
5443 \consists Mensural_ligature_engraver
5449 Without replacing @internalsref{Ligature_bracket_engraver} with
5450 @internalsref{Mensural_ligature_engraver}, the same music transcribes
5453 @lilypond[singleline]
5455 \notes \transpose c c' {
5456 \property Score.timing = ##f
5457 \property Score.defaultBarType = "empty"
5458 \property Voice.NoteHead \set #'style = #'neo_mensural
5459 \property Staff.TimeSignature \set #'style = #'neo_mensural
5461 \[ g\longa c\breve a\breve f\breve d'\longa \]
5463 \[ e1 f1 a\breve g\longa \]
5469 @node Gregorian square neumes ligatures
5470 @subsubsection Gregorian square neumes ligatures
5472 @cindex Square neumes ligatures
5473 @cindex Gregorian square neumes ligatures
5475 Gregorian square neumes notation (following the style of the Editio
5476 Vaticana) is under heavy development, but not yet really usable for
5477 production purposes. Core ligatures can already be typeset, but
5478 essential issues for serious typesetting are still under development,
5479 such as (among others) horizontal alignment of multiple ligatures,
5480 lyrics alignment and proper accidentals handling. Still, this section
5481 gives a sneak preview of what Gregorian chant may look like once it
5484 The following table contains the extended neumes table of the 2nd
5485 volume of the Antiphonale Romanum (@emph{Liber Hymnarius}), published
5486 1983 by the monks of Solesmes.
5488 @multitable @columnfractions .4 .2 .2 .2
5491 @b{Neuma aut@*Neumarum Elementa} @tab
5492 @b{Figurae@*Rectae} @tab
5493 @b{Figurae@*Liquescentes Auctae} @tab
5494 @b{Figurae@*Liquescentes Deminutae}
5496 @c TODO: \paper block is identical in all of the below examples.
5497 @c Therefore, it should somehow be included rather than duplicated all
5500 @c why not make identifiers in ly/engraver-init.ly? --hwn
5502 @c Because it's just used to typeset plain notes without
5503 @c a staff for demonstration purposes rather than something
5504 @c special of Gregorian chant notation. --jr
5509 @lilypond[noindent, 26pt, nofragment, linewidth=1.5cm]
5510 \include "gregorian-init.ly"
5512 \notes \transpose c c' {
5515 \noBreak s^\markup {"a"} \noBreak
5517 % Punctum Inclinatum
5519 \noBreak s^\markup {"b"}
5525 \remove "Bar_number_engraver"
5529 \remove "Clef_engraver"
5530 \remove "Key_engraver"
5531 StaffSymbol \set #'transparent = ##t
5532 \remove "Time_signature_engraver"
5533 \remove "Bar_engraver"
5534 minimumVerticalExtent = ##f
5538 \remove Ligature_bracket_engraver
5539 \consists Vaticana_ligature_engraver
5540 NoteHead \set #'style = #'vaticana_punctum
5541 Stem \set #'transparent = ##t
5547 @lilypond[noindent, 26pt, nofragment, linewidth=2.5cm]
5548 \include "gregorian-init.ly"
5550 \notes \transpose c c' {
5551 % Punctum Auctum Ascendens
5552 \[ \auctum \ascendens b \]
5553 \noBreak s^\markup {"c"} \noBreak
5555 % Punctum Auctum Descendens
5556 \[ \auctum \descendens b \]
5557 \noBreak s^\markup {"d"} \noBreak
5559 % Punctum Inclinatum Auctum
5560 \[ \inclinatum \auctum b \]
5561 \noBreak s^\markup {"e"}
5567 \remove "Bar_number_engraver"
5571 \remove "Clef_engraver"
5572 \remove "Key_engraver"
5573 StaffSymbol \set #'transparent = ##t
5574 \remove "Time_signature_engraver"
5575 \remove "Bar_engraver"
5576 minimumVerticalExtent = ##f
5580 \remove Ligature_bracket_engraver
5581 \consists Vaticana_ligature_engraver
5582 NoteHead \set #'style = #'vaticana_punctum
5583 Stem \set #'transparent = ##t
5589 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
5590 \include "gregorian-init.ly"
5592 \notes \transpose c c' {
5593 % Punctum Inclinatum Parvum
5594 \[ \inclinatum \deminutum b \]
5595 \noBreak s^\markup {"f"}
5601 \remove "Bar_number_engraver"
5605 \remove "Clef_engraver"
5606 \remove "Key_engraver"
5607 StaffSymbol \set #'transparent = ##t
5608 \remove "Time_signature_engraver"
5609 \remove "Bar_engraver"
5610 minimumVerticalExtent = ##f
5614 \remove Ligature_bracket_engraver
5615 \consists Vaticana_ligature_engraver
5616 NoteHead \set #'style = #'vaticana_punctum
5617 Stem \set #'transparent = ##t
5626 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
5627 \include "gregorian-init.ly"
5629 \notes \transpose c c' {
5632 \noBreak s^\markup {"g"}
5638 \remove "Bar_number_engraver"
5642 \remove "Clef_engraver"
5643 \remove "Key_engraver"
5644 StaffSymbol \set #'transparent = ##t
5645 \remove "Time_signature_engraver"
5646 \remove "Bar_engraver"
5647 minimumVerticalExtent = ##f
5651 \remove Ligature_bracket_engraver
5652 \consists Vaticana_ligature_engraver
5653 NoteHead \set #'style = #'vaticana_punctum
5654 Stem \set #'transparent = ##t
5663 @code{3. Apostropha vel Stropha}
5665 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
5666 \include "gregorian-init.ly"
5668 \notes \transpose c c' {
5671 \noBreak s^\markup {"h"}
5677 \remove "Bar_number_engraver"
5681 \remove "Clef_engraver"
5682 \remove "Key_engraver"
5683 StaffSymbol \set #'transparent = ##t
5684 \remove "Time_signature_engraver"
5685 \remove "Bar_engraver"
5686 minimumVerticalExtent = ##f
5690 \remove Ligature_bracket_engraver
5691 \consists Vaticana_ligature_engraver
5692 NoteHead \set #'style = #'vaticana_punctum
5693 Stem \set #'transparent = ##t
5699 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
5700 \include "gregorian-init.ly"
5702 \notes \transpose c c' {
5704 \[ \stropha \auctum b \]
5705 \noBreak s^\markup {"i"}
5711 \remove "Bar_number_engraver"
5715 \remove "Clef_engraver"
5716 \remove "Key_engraver"
5717 StaffSymbol \set #'transparent = ##t
5718 \remove "Time_signature_engraver"
5719 \remove "Bar_engraver"
5720 minimumVerticalExtent = ##f
5724 \remove Ligature_bracket_engraver
5725 \consists Vaticana_ligature_engraver
5726 NoteHead \set #'style = #'vaticana_punctum
5727 Stem \set #'transparent = ##t
5737 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
5738 \include "gregorian-init.ly"
5740 \notes \transpose c c' {
5743 \noBreak s^\markup {"j"}
5749 \remove "Bar_number_engraver"
5753 \remove "Clef_engraver"
5754 \remove "Key_engraver"
5755 StaffSymbol \set #'transparent = ##t
5756 \remove "Time_signature_engraver"
5757 \remove "Bar_engraver"
5758 minimumVerticalExtent = ##f
5762 \remove Ligature_bracket_engraver
5763 \consists Vaticana_ligature_engraver
5764 NoteHead \set #'style = #'vaticana_punctum
5765 Stem \set #'transparent = ##t
5774 @code{5. Clivis vel Flexa}
5776 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
5777 \include "gregorian-init.ly"
5779 \notes \transpose c c' {
5788 \remove "Bar_number_engraver"
5792 \remove "Clef_engraver"
5793 \remove "Key_engraver"
5794 StaffSymbol \set #'transparent = ##t
5795 \remove "Time_signature_engraver"
5796 \remove "Bar_engraver"
5797 minimumVerticalExtent = ##f
5801 \remove Ligature_bracket_engraver
5802 \consists Vaticana_ligature_engraver
5803 NoteHead \set #'style = #'vaticana_punctum
5804 Stem \set #'transparent = ##t
5810 @lilypond[noindent, 26pt, nofragment, linewidth=2.0cm]
5811 \include "gregorian-init.ly"
5813 \notes \transpose c c' {
5814 % Clivis Aucta Descendens
5815 \[ b \flexa \auctum \descendens g \]
5816 \noBreak s^\markup {"l"} \noBreak
5818 % Clivis Aucta Ascendens
5819 \[ b \flexa \auctum \ascendens g \]
5820 \noBreak s^\markup {"m"}
5826 \remove "Bar_number_engraver"
5830 \remove "Clef_engraver"
5831 \remove "Key_engraver"
5832 StaffSymbol \set #'transparent = ##t
5833 \remove "Time_signature_engraver"
5834 \remove "Bar_engraver"
5835 minimumVerticalExtent = ##f
5839 \remove Ligature_bracket_engraver
5840 \consists Vaticana_ligature_engraver
5841 NoteHead \set #'style = #'vaticana_punctum
5842 Stem \set #'transparent = ##t
5848 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
5849 \include "gregorian-init.ly"
5851 \notes \transpose c c' {
5853 \[ b \flexa \deminutum g \]
5860 \remove "Bar_number_engraver"
5864 \remove "Clef_engraver"
5865 \remove "Key_engraver"
5866 StaffSymbol \set #'transparent = ##t
5867 \remove "Time_signature_engraver"
5868 \remove "Bar_engraver"
5869 minimumVerticalExtent = ##f
5873 \remove Ligature_bracket_engraver
5874 \consists Vaticana_ligature_engraver
5875 NoteHead \set #'style = #'vaticana_punctum
5876 Stem \set #'transparent = ##t
5883 @code{6. Podatus vel Pes}
5885 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
5886 \include "gregorian-init.ly"
5888 \notes \transpose c c' {
5897 \remove "Bar_number_engraver"
5901 \remove "Clef_engraver"
5902 \remove "Key_engraver"
5903 StaffSymbol \set #'transparent = ##t
5904 \remove "Time_signature_engraver"
5905 \remove "Bar_engraver"
5906 minimumVerticalExtent = ##f
5910 \remove Ligature_bracket_engraver
5911 \consists Vaticana_ligature_engraver
5912 NoteHead \set #'style = #'vaticana_punctum
5913 Stem \set #'transparent = ##t
5919 @lilypond[noindent, 26pt, nofragment, linewidth=2.0cm]
5920 \include "gregorian-init.ly"
5922 \notes \transpose c c' {
5923 % Pes Auctus Descendens
5924 \[ g \pes \auctum \descendens b \]
5925 \noBreak s^\markup {"p"} \noBreak
5927 % Pes Auctus Ascendens
5928 \[ g \pes \auctum \ascendens b \]
5929 \noBreak s^\markup {"q"}
5935 \remove "Bar_number_engraver"
5939 \remove "Clef_engraver"
5940 \remove "Key_engraver"
5941 StaffSymbol \set #'transparent = ##t
5942 \remove "Time_signature_engraver"
5943 \remove "Bar_engraver"
5944 minimumVerticalExtent = ##f
5948 \remove Ligature_bracket_engraver
5949 \consists Vaticana_ligature_engraver
5950 NoteHead \set #'style = #'vaticana_punctum
5951 Stem \set #'transparent = ##t
5957 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
5958 \include "gregorian-init.ly"
5960 \notes \transpose c c' {
5962 \[ g \pes \deminutum b \]
5969 \remove "Bar_number_engraver"
5973 \remove "Clef_engraver"
5974 \remove "Key_engraver"
5975 StaffSymbol \set #'transparent = ##t
5976 \remove "Time_signature_engraver"
5977 \remove "Bar_engraver"
5978 minimumVerticalExtent = ##f
5982 \remove Ligature_bracket_engraver
5983 \consists Vaticana_ligature_engraver
5984 NoteHead \set #'style = #'vaticana_punctum
5985 Stem \set #'transparent = ##t
5992 @code{7. Pes Quassus}
5994 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
5995 \include "gregorian-init.ly"
5997 \notes \transpose c c' {
5999 \[ \oriscus g \pes \virga b \]
6006 \remove "Bar_number_engraver"
6010 \remove "Clef_engraver"
6011 \remove "Key_engraver"
6012 StaffSymbol \set #'transparent = ##t
6013 \remove "Time_signature_engraver"
6014 \remove "Bar_engraver"
6015 minimumVerticalExtent = ##f
6019 \remove Ligature_bracket_engraver
6020 \consists Vaticana_ligature_engraver
6021 NoteHead \set #'style = #'vaticana_punctum
6022 Stem \set #'transparent = ##t
6028 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6029 \include "gregorian-init.ly"
6031 \notes \transpose c c' {
6032 % Pes Quassus Auctus Descendens
6033 \[ \oriscus g \pes \auctum \descendens b \]
6040 \remove "Bar_number_engraver"
6044 \remove "Clef_engraver"
6045 \remove "Key_engraver"
6046 StaffSymbol \set #'transparent = ##t
6047 \remove "Time_signature_engraver"
6048 \remove "Bar_engraver"
6049 minimumVerticalExtent = ##f
6053 \remove Ligature_bracket_engraver
6054 \consists Vaticana_ligature_engraver
6055 NoteHead \set #'style = #'vaticana_punctum
6056 Stem \set #'transparent = ##t
6064 @code{8. Quilisma Pes}
6066 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6067 \include "gregorian-init.ly"
6069 \notes \transpose c c' {
6071 \[ \quilisma g \pes b \]
6078 \remove "Bar_number_engraver"
6082 \remove "Clef_engraver"
6083 \remove "Key_engraver"
6084 StaffSymbol \set #'transparent = ##t
6085 \remove "Time_signature_engraver"
6086 \remove "Bar_engraver"
6087 minimumVerticalExtent = ##f
6091 \remove Ligature_bracket_engraver
6092 \consists Vaticana_ligature_engraver
6093 NoteHead \set #'style = #'vaticana_punctum
6094 Stem \set #'transparent = ##t
6100 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6101 \include "gregorian-init.ly"
6103 \notes \transpose c c' {
6104 % Quilisma Pes Auctus Descendens
6105 \[ \quilisma g \pes \auctum \descendens b \]
6112 \remove "Bar_number_engraver"
6116 \remove "Clef_engraver"
6117 \remove "Key_engraver"
6118 StaffSymbol \set #'transparent = ##t
6119 \remove "Time_signature_engraver"
6120 \remove "Bar_engraver"
6121 minimumVerticalExtent = ##f
6125 \remove Ligature_bracket_engraver
6126 \consists Vaticana_ligature_engraver
6127 NoteHead \set #'style = #'vaticana_punctum
6128 Stem \set #'transparent = ##t
6136 @code{9. Podatus Initio Debilis}
6138 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6139 \include "gregorian-init.ly"
6141 \notes \transpose c c' {
6142 % Pes Initio Debilis
6143 \[ \deminutum g \pes b \]
6150 \remove "Bar_number_engraver"
6154 \remove "Clef_engraver"
6155 \remove "Key_engraver"
6156 StaffSymbol \set #'transparent = ##t
6157 \remove "Time_signature_engraver"
6158 \remove "Bar_engraver"
6159 minimumVerticalExtent = ##f
6163 \remove Ligature_bracket_engraver
6164 \consists Vaticana_ligature_engraver
6165 NoteHead \set #'style = #'vaticana_punctum
6166 Stem \set #'transparent = ##t
6172 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6173 \include "gregorian-init.ly"
6175 \notes \transpose c c' {
6176 % Pes Auctus Descendens Initio Debilis
6177 \[ \deminutum g \pes \auctum \descendens b \]
6184 \remove "Bar_number_engraver"
6188 \remove "Clef_engraver"
6189 \remove "Key_engraver"
6190 StaffSymbol \set #'transparent = ##t
6191 \remove "Time_signature_engraver"
6192 \remove "Bar_engraver"
6193 minimumVerticalExtent = ##f
6197 \remove Ligature_bracket_engraver
6198 \consists Vaticana_ligature_engraver
6199 NoteHead \set #'style = #'vaticana_punctum
6200 Stem \set #'transparent = ##t
6210 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6211 \include "gregorian-init.ly"
6213 \notes \transpose c c' {
6215 \[ a \pes b \flexa g \]
6222 \remove "Bar_number_engraver"
6226 \remove "Clef_engraver"
6227 \remove "Key_engraver"
6228 StaffSymbol \set #'transparent = ##t
6229 \remove "Time_signature_engraver"
6230 \remove "Bar_engraver"
6231 minimumVerticalExtent = ##f
6235 \remove Ligature_bracket_engraver
6236 \consists Vaticana_ligature_engraver
6237 NoteHead \set #'style = #'vaticana_punctum
6238 Stem \set #'transparent = ##t
6244 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6245 \include "gregorian-init.ly"
6247 \notes \transpose c c' {
6248 % Torculus Auctus Descendens
6249 \[ a \pes b \flexa \auctum \descendens g \]
6256 \remove "Bar_number_engraver"
6260 \remove "Clef_engraver"
6261 \remove "Key_engraver"
6262 StaffSymbol \set #'transparent = ##t
6263 \remove "Time_signature_engraver"
6264 \remove "Bar_engraver"
6265 minimumVerticalExtent = ##f
6269 \remove Ligature_bracket_engraver
6270 \consists Vaticana_ligature_engraver
6271 NoteHead \set #'style = #'vaticana_punctum
6272 Stem \set #'transparent = ##t
6278 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6279 \include "gregorian-init.ly"
6281 \notes \transpose c c' {
6282 % Torculus Deminutus
6283 \[ a \pes b \flexa \deminutum g \]
6290 \remove "Bar_number_engraver"
6294 \remove "Clef_engraver"
6295 \remove "Key_engraver"
6296 StaffSymbol \set #'transparent = ##t
6297 \remove "Time_signature_engraver"
6298 \remove "Bar_engraver"
6299 minimumVerticalExtent = ##f
6303 \remove Ligature_bracket_engraver
6304 \consists Vaticana_ligature_engraver
6305 NoteHead \set #'style = #'vaticana_punctum
6306 Stem \set #'transparent = ##t
6313 @code{11. Torculus Initio Debilis}
6315 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6316 \include "gregorian-init.ly"
6318 \notes \transpose c c' {
6319 % Torculus Initio Debilis
6320 \[ \deminutum a \pes b \flexa g \]
6327 \remove "Bar_number_engraver"
6331 \remove "Clef_engraver"
6332 \remove "Key_engraver"
6333 StaffSymbol \set #'transparent = ##t
6334 \remove "Time_signature_engraver"
6335 \remove "Bar_engraver"
6336 minimumVerticalExtent = ##f
6340 \remove Ligature_bracket_engraver
6341 \consists Vaticana_ligature_engraver
6342 NoteHead \set #'style = #'vaticana_punctum
6343 Stem \set #'transparent = ##t
6349 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6350 \include "gregorian-init.ly"
6352 \notes \transpose c c' {
6353 % Torculus Auctus Descendens Initio Debilis
6354 \[ \deminutum a \pes b \flexa \auctum \descendens g \]
6361 \remove "Bar_number_engraver"
6365 \remove "Clef_engraver"
6366 \remove "Key_engraver"
6367 StaffSymbol \set #'transparent = ##t
6368 \remove "Time_signature_engraver"
6369 \remove "Bar_engraver"
6370 minimumVerticalExtent = ##f
6374 \remove Ligature_bracket_engraver
6375 \consists Vaticana_ligature_engraver
6376 NoteHead \set #'style = #'vaticana_punctum
6377 Stem \set #'transparent = ##t
6383 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6384 \include "gregorian-init.ly"
6386 \notes \transpose c c' {
6387 % Torculus Deminutus Initio Debilis
6388 \[ \deminutum a \pes b \flexa \deminutum g \]
6395 \remove "Bar_number_engraver"
6399 \remove "Clef_engraver"
6400 \remove "Key_engraver"
6401 StaffSymbol \set #'transparent = ##t
6402 \remove "Time_signature_engraver"
6403 \remove "Bar_engraver"
6404 minimumVerticalExtent = ##f
6408 \remove Ligature_bracket_engraver
6409 \consists Vaticana_ligature_engraver
6410 NoteHead \set #'style = #'vaticana_punctum
6411 Stem \set #'transparent = ##t
6418 @code{12. Porrectus}
6420 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6421 \include "gregorian-init.ly"
6423 \notes \transpose c c' {
6425 \[ a \flexa g \pes b \]
6432 \remove "Bar_number_engraver"
6436 \remove "Clef_engraver"
6437 \remove "Key_engraver"
6438 StaffSymbol \set #'transparent = ##t
6439 \remove "Time_signature_engraver"
6440 \remove "Bar_engraver"
6441 minimumVerticalExtent = ##f
6445 \remove Ligature_bracket_engraver
6446 \consists Vaticana_ligature_engraver
6447 NoteHead \set #'style = #'vaticana_punctum
6448 Stem \set #'transparent = ##t
6454 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6455 \include "gregorian-init.ly"
6457 \notes \transpose c c' {
6458 % Porrectus Auctus Descendens
6459 \[ a \flexa g \pes \auctum \descendens b \]
6466 \remove "Bar_number_engraver"
6470 \remove "Clef_engraver"
6471 \remove "Key_engraver"
6472 StaffSymbol \set #'transparent = ##t
6473 \remove "Time_signature_engraver"
6474 \remove "Bar_engraver"
6475 minimumVerticalExtent = ##f
6479 \remove Ligature_bracket_engraver
6480 \consists Vaticana_ligature_engraver
6481 NoteHead \set #'style = #'vaticana_punctum
6482 Stem \set #'transparent = ##t
6488 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6489 \include "gregorian-init.ly"
6491 \notes \transpose c c' {
6492 % Porrectus Deminutus
6493 \[ a \flexa g \pes \deminutum b \]
6500 \remove "Bar_number_engraver"
6504 \remove "Clef_engraver"
6505 \remove "Key_engraver"
6506 StaffSymbol \set #'transparent = ##t
6507 \remove "Time_signature_engraver"
6508 \remove "Bar_engraver"
6509 minimumVerticalExtent = ##f
6513 \remove Ligature_bracket_engraver
6514 \consists Vaticana_ligature_engraver
6515 NoteHead \set #'style = #'vaticana_punctum
6516 Stem \set #'transparent = ##t
6525 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6526 \include "gregorian-init.ly"
6528 \notes \transpose c c' {
6530 \[ \virga b \inclinatum a \inclinatum g \]
6537 \remove "Bar_number_engraver"
6541 \remove "Clef_engraver"
6542 \remove "Key_engraver"
6543 StaffSymbol \set #'transparent = ##t
6544 \remove "Time_signature_engraver"
6545 \remove "Bar_engraver"
6546 minimumVerticalExtent = ##f
6550 \remove Ligature_bracket_engraver
6551 \consists Vaticana_ligature_engraver
6552 NoteHead \set #'style = #'vaticana_punctum
6553 Stem \set #'transparent = ##t
6559 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6560 \include "gregorian-init.ly"
6562 \notes \transpose c c' {
6564 \[ \virga b \inclinatum a \inclinatum \auctum g \]
6571 \remove "Bar_number_engraver"
6575 \remove "Clef_engraver"
6576 \remove "Key_engraver"
6577 StaffSymbol \set #'transparent = ##t
6578 \remove "Time_signature_engraver"
6579 \remove "Bar_engraver"
6580 minimumVerticalExtent = ##f
6584 \remove Ligature_bracket_engraver
6585 \consists Vaticana_ligature_engraver
6586 NoteHead \set #'style = #'vaticana_punctum
6587 Stem \set #'transparent = ##t
6593 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6594 \include "gregorian-init.ly"
6596 \notes \transpose c c' {
6597 % Climacus Deminutus
6598 \[ \virga b \inclinatum a \inclinatum \deminutum g \]
6605 \remove "Bar_number_engraver"
6609 \remove "Clef_engraver"
6610 \remove "Key_engraver"
6611 StaffSymbol \set #'transparent = ##t
6612 \remove "Time_signature_engraver"
6613 \remove "Bar_engraver"
6614 minimumVerticalExtent = ##f
6618 \remove Ligature_bracket_engraver
6619 \consists Vaticana_ligature_engraver
6620 NoteHead \set #'style = #'vaticana_punctum
6621 Stem \set #'transparent = ##t
6628 @code{14. Scandicus}
6630 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6631 \include "gregorian-init.ly"
6633 \notes \transpose c c' {
6635 \[ g \pes a \virga b \]
6642 \remove "Bar_number_engraver"
6646 \remove "Clef_engraver"
6647 \remove "Key_engraver"
6648 StaffSymbol \set #'transparent = ##t
6649 \remove "Time_signature_engraver"
6650 \remove "Bar_engraver"
6651 minimumVerticalExtent = ##f
6655 \remove Ligature_bracket_engraver
6656 \consists Vaticana_ligature_engraver
6657 NoteHead \set #'style = #'vaticana_punctum
6658 Stem \set #'transparent = ##t
6664 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6665 \include "gregorian-init.ly"
6667 \notes \transpose c c' {
6668 % Scandicus Auctus Descendens
6669 \[ g \pes a \pes \auctum \descendens b \]
6676 \remove "Bar_number_engraver"
6680 \remove "Clef_engraver"
6681 \remove "Key_engraver"
6682 StaffSymbol \set #'transparent = ##t
6683 \remove "Time_signature_engraver"
6684 \remove "Bar_engraver"
6685 minimumVerticalExtent = ##f
6689 \remove Ligature_bracket_engraver
6690 \consists Vaticana_ligature_engraver
6691 NoteHead \set #'style = #'vaticana_punctum
6692 Stem \set #'transparent = ##t
6698 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6699 \include "gregorian-init.ly"
6701 \notes \transpose c c' {
6702 % Scandicus Deminutus
6703 \[ g \pes a \pes \deminutum b \]
6710 \remove "Bar_number_engraver"
6714 \remove "Clef_engraver"
6715 \remove "Key_engraver"
6716 StaffSymbol \set #'transparent = ##t
6717 \remove "Time_signature_engraver"
6718 \remove "Bar_engraver"
6719 minimumVerticalExtent = ##f
6723 \remove Ligature_bracket_engraver
6724 \consists Vaticana_ligature_engraver
6725 NoteHead \set #'style = #'vaticana_punctum
6726 Stem \set #'transparent = ##t
6735 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6736 \include "gregorian-init.ly"
6738 \notes \transpose c c' {
6740 \[ g \oriscus a \pes \virga b \]
6747 \remove "Bar_number_engraver"
6751 \remove "Clef_engraver"
6752 \remove "Key_engraver"
6753 StaffSymbol \set #'transparent = ##t
6754 \remove "Time_signature_engraver"
6755 \remove "Bar_engraver"
6756 minimumVerticalExtent = ##f
6760 \remove Ligature_bracket_engraver
6761 \consists Vaticana_ligature_engraver
6762 NoteHead \set #'style = #'vaticana_punctum
6763 Stem \set #'transparent = ##t
6769 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6770 \include "gregorian-init.ly"
6772 \notes \transpose c c' {
6773 % Salicus Auctus Descendens
6774 \[ g \oriscus a \pes \auctum \descendens b \]
6781 \remove "Bar_number_engraver"
6785 \remove "Clef_engraver"
6786 \remove "Key_engraver"
6787 StaffSymbol \set #'transparent = ##t
6788 \remove "Time_signature_engraver"
6789 \remove "Bar_engraver"
6790 minimumVerticalExtent = ##f
6794 \remove Ligature_bracket_engraver
6795 \consists Vaticana_ligature_engraver
6796 NoteHead \set #'style = #'vaticana_punctum
6797 Stem \set #'transparent = ##t
6807 @lilypond[noindent, 26pt, nofragment, linewidth=1.0cm]
6808 \include "gregorian-init.ly"
6810 \notes \transpose c c' {
6812 \[ \stropha b \stropha b \stropha a \]
6819 \remove "Bar_number_engraver"
6823 \remove "Clef_engraver"
6824 \remove "Key_engraver"
6825 StaffSymbol \set #'transparent = ##t
6826 \remove "Time_signature_engraver"
6827 \remove "Bar_engraver"
6828 minimumVerticalExtent = ##f
6832 \remove Ligature_bracket_engraver
6833 \consists Vaticana_ligature_engraver
6834 NoteHead \set #'style = #'vaticana_punctum
6835 Stem \set #'transparent = ##t
6847 Unlike most other neumes notation systems, the input language for
6848 neumes does not necessarily reflect directly the typographical
6849 appearance, but is designed to solely focuse on musical meaning. For
6850 example, @code{\[ a \pes b \flexa g \]} produces a Torculus consisting
6851 of three Punctum heads, while @code{\[ a \flexa g \pes b \]} produces
6852 a Porrectus with a curved flexa shape and only a single Punctum head.
6853 There is no command to explicitly typeset the curved flexa shape; the
6854 decision of when to typeset a curved flexa shape is purely taken from
6855 the musical input. The idea of this approach is to separate the
6856 musical aspects of the input from the notation style of the output.
6857 This way, the same input can be reused to typeset the same music in a
6858 different style of Gregorian chant notation such as Hufnagel (also
6859 known as German gothic neumes) or Medicaea (kind of a very simple
6860 forerunner of the Editio Vaticana). As soon as Hufnagel ligature
6861 engraver and Medicaea ligature engraver will have been implemented, it
6862 will be as simple as replacing the ligature engraver in the
6863 @internalsref{Voice} context to get the desired notation style from
6866 The following table shows the code fragments that produce the
6867 ligatures in the above neumes table. The letter in the first column
6868 in each line of the below table indicates to which ligature in the
6869 above table it refers. The second column gives the name of the
6870 ligature. The third column shows the code fragment that produces this
6871 ligature, using @code{g}, @code{a} and @code{b} as example pitches.
6873 @multitable @columnfractions .1 .4 .5
6887 Punctum Inclinatum @tab
6888 @code{\[ \inclinatum b \]}
6892 Punctum Auctum Ascendens @tab
6893 @code{\[ \auctum \ascendens b \]}
6897 Punctum Auctum Descendens @tab
6898 @code{\[ \auctum \descendens b \]}
6902 Punctum Inclinatum Auctum @tab
6903 @code{\[ \inclinatum \auctum b \]}
6907 Punctum Inclinatum Parvum @tab
6908 @code{\[ \inclinatum \deminutum b \]}
6913 @code{\[ \virga b \]}
6918 @code{\[ \stropha b \]}
6923 @code{\[ \stropha \auctum b \]}
6928 @code{\[ \oriscus b \]}
6932 Clivis vel Flexa @tab
6933 @code{\[ b \flexa g \]}
6937 Clivis Aucta Descendens @tab
6938 @code{\[ b \flexa \auctum \descendens g \]}
6942 Clivis Aucta Ascendens @tab
6943 @code{\[ b \flexa \auctum \ascendens g \]}
6948 @code{\[ b \flexa \deminutum g \]}
6952 Podatus vel Pes @tab
6953 @code{\[ g \pes b \]}
6957 Pes Auctus Descendens @tab
6958 @code{\[ g \pes \auctum \descendens b \]}
6962 Pes Auctus Ascendens @tab
6963 @code{\[ g \pes \auctum \ascendens b \]}
6968 @code{\[ g \pes \deminutum b \]}
6973 @code{\[ \oriscus g \pes \virga b \]}
6977 Pes Quassus Auctus Descendens @tab
6978 @code{\[ \oriscus g \pes \auctum \descendens b \]}
6983 @code{\[ \quilisma g \pes b \]}
6987 Quilisma Pes Auctus Descendens @tab
6988 @code{\[ \quilisma g \pes \auctum \descendens b \]}
6992 Pes Initio Debilis @tab
6993 @code{\[ \deminutum g \pes b \]}
6997 Pes Auctus Descendens Initio Debilis @tab
6998 @code{\[ \deminutum g \pes \auctum \descendens b \]}
7003 @code{\[ a \pes b \flexa g \]}
7007 Torculus Auctus Descendens @tab
7008 @code{\[ a \pes b \flexa \auctum \descendens g \]}
7012 Torculus Deminutus @tab
7013 @code{\[ a \pes b \flexa \deminutum g \]}
7017 Torculus Initio Debilis @tab
7018 @code{\[ \deminutum a \pes b \flexa g \]}
7022 Torculus Auctus Descendens Initio Debilis @tab
7023 @code{\[ \deminutum a \pes b \flexa \auctum \descendens g \]}
7027 Torculus Deminutus Initio Debilis @tab
7028 @code{\[ \deminutum a \pes b \flexa \deminutum g \]}
7033 @code{\[ a \flexa g \pes b \]}
7037 Porrectus Auctus Descendens @tab
7038 @code{\[ a \flexa g \pes \auctum \descendens b \]}
7042 Porrectus Deminutus @tab
7043 @code{\[ a \flexa g \pes \deminutum b \]}
7048 @code{\[ \virga b \inclinatum a \inclinatum g \]}
7052 Climacus Auctus @tab
7053 @code{\[ \virga b \inclinatum a \inclinatum \auctum g \]}
7057 Climacus Deminutus @tab
7058 @code{\[ \virga b \inclinatum a \inclinatum \deminutum g \]}
7063 @code{\[ g \pes a \virga b \]}
7067 Scandicus Auctus Descendens @tab
7068 @code{\[ g \pes a \pes \auctum \descendens b \]}
7072 Scandicus Deminutus @tab
7073 @code{\[ g \pes a \pes \deminutum b \]}
7078 @code{\[ g \oriscus a \pes \virga b \]}
7082 Salicus Auctus Descendens @tab
7083 @code{\[ g \oriscus a \pes \auctum \descendens b \]}
7088 @code{\[ \stropha b \stropha b \stropha a \]}
7094 The following head prefixes are supported:
7096 @cindex @code{\virga}
7098 @cindex @code{\stropha}
7100 @cindex @code{\inclinatum}
7102 @cindex @code{\auctum}
7104 @cindex @code{\descendens}
7106 @cindex @code{\ascendens}
7108 @cindex @code{\oriscus}
7110 @cindex @code{\quilisma}
7112 @cindex @code{\deminutum}
7115 Head prefixes can be accumulated, though restrictions apply. For
7116 example, either @code{\descendens} or @code{\ascendens} can be applied
7117 to a head, but not both to the same head.
7120 @cindex @code{\flexa}
7121 Two adjacent heads can be tied together with the @code{\pes} and
7122 @code{\flexa} infix commands for a rising and falling line of melody,
7127 Trigonus: apply equal spacing, regardless of pitch.
7130 @subsection Figured bass
7132 @cindex Basso continuo
7134 @c TODO: musicological blurb about FB
7138 LilyPond has limited support for figured bass:
7140 @lilypond[verbatim,fragment]
7142 \context Voice \notes { \clef bass dis4 c d ais}
7143 \context FiguredBass
7145 < 6 >4 < 7 >8 < 6+ [_!] >
7151 The support for figured bass consists of two parts: there is an input
7152 mode, introduced by @code{\figures}, where you can enter bass figures
7153 as numbers, and there is a context called @internalsref{FiguredBass} that
7154 takes care of making @internalsref{BassFigure} objects.
7156 In figures input mode, a group of bass figures is delimited by
7157 @code{<} and @code{>}. The duration is entered after the @code{>>}:
7162 \context FiguredBass
7166 Accidentals are added when you append @code{-}, @code{!} and @code{+}
7173 \context FiguredBass
7174 \figures { <4- 6+ 7!> }
7177 Spaces or dashes may be inserted by using @code{_}. Brackets are
7178 introduced with @code{[} and @code{]}:
7184 \context FiguredBass
7185 \figures { < [4 6] 8 [_! 12]> }
7188 Although the support for figured bass may superficially resemble chord
7189 support, it works much simpler. The @code{\figures} mode simply
7190 stores the numbers , and @internalsref{FiguredBass} context prints
7191 them as entered. There is no conversion to pitches, and no
7192 realizations of the bass are played in the MIDI file.
7194 Internally, the code produces markup texts. You can use any of the
7195 markup text properties to override formatting. For example, the
7196 vertical spacing of the figures may be set with @code{baseline-skip}.
7200 @internalsref{BassFigureEvent} music, @internalsref{BassFigure} object,
7201 and @internalsref{FiguredBass} context.
7205 Slash notation for alterations is not supported.
7208 @node Vaticana style contexts
7209 @subsection Vaticana style contexts
7211 @cindex VaticanaVoiceContext
7212 @cindex VaticanaStaffContext
7214 The predefined @code{VaticanaVoiceContext} and
7215 @code{VaticanaStaffContext} can be used to easily engrave a piece of
7216 Gregorian Chant in the style of the Editio Vaticana. These contexts
7217 initialize all relevant context properties and grob properties to
7218 proper values. With these contexts, you can immediately go ahead
7219 entering the chant, as the following short excerpt demonstrates:
7221 @lilypond[raggedright,verbatim,noindent]
7222 \include "gregorian-init.ly"
7225 \context VaticanaVoice {
7226 \property Score.BarNumber \set #'transparent = ##t
7228 \[ c'( c' \flexa a \] \[ a \flexa \deminutum g) \] f \divisioMinima
7229 \[ f( \pes a c' c' \pes d') \] c' \divisioMinima \break
7230 \[ c'( c' \flexa a \] \[ a \flexa \deminutum g) \] f \divisioMinima
7233 \context Lyrics \lyrics {
7234 San- ctus, San- ctus, San- ctus
7239 @node Contemporary notation
7240 @section Contemporary notation
7242 In the 20th century, composers have greatly expanded the musical
7243 vocabulary. With this expansion, many innovations in musical notation
7244 have been tried. The book by Stone (1980) gives a comprehensive
7245 overview (see @ref{Literature list}). In general, the use of new,
7246 innovative notation makes a piece harder to understand and perform and
7247 its use should therefore be avoided if possible. For this reason,
7248 support for contemporary notation in LilyPond is limited.
7257 @subsection Clusters
7261 In musical terminology, a @emph{cluster} denotes a range of
7262 simultaneously sounding pitches that may change over time. The set of
7263 available pitches to apply usually depends on the accoustic source.
7264 Thus, in piano music, a cluster typically consists of a continous range
7265 of the semitones as provided by the piano's fixed set of a chromatic
7266 scale. In choral music, each singer of the choir typically may sing an
7267 arbitrary pitch within the cluster's range that is not bound to any
7268 diatonic, chromatic or other scale. In electronic music, a cluster
7269 (theoretically) may even cover a continuous range of pitches, thus
7270 resulting in coloured noise, such as pink noise.
7272 Clusters can be denoted in the context of ordinary staff notation by
7273 engraving simple geometrical shapes that replace ordinary notation of
7274 notes. Ordinary notes as musical events specify starting time and
7275 duration of pitches; however, the duration of a note is expressed by the
7276 shape of the note head rather than by the horizontal graphical extent of
7277 the note symbol. In contrast, the shape of a cluster geometrically
7278 describes the development of a range of pitches (vertical extent) over
7279 time (horizontal extent). Still, the geometrical shape of a cluster
7280 covers the area in wich any single pitch contained in the cluster would
7281 be notated as an ordinary note. From this point of view, it is
7282 reasonable to specify a cluster as the envelope of a set of notes.
7286 A cluster is engraved as the envelope of a set of
7287 cluster-notes. Cluster notes are created by applying the function
7288 @code{notes-to-clusters} to a sequence of chords, e.g.
7290 @lilypond[relative 1,verbatim]
7291 \apply #notes-to-clusters { <c e > <b f'> }
7294 The following example (from
7295 @inputfileref{input/regression,cluster.ly}) shows what the result
7298 @lilypondfile[notexidoc]{cluster.ly}
7300 By default, @internalsref{Cluster_spanner_engraver} is in the
7301 @internalsref{Voice} context. This allows putting ordinary notes and
7302 clusters together in the same staff, even simultaneously. In such a
7303 case no attempt is made to automatically avoid collisions between
7304 ordinary notes and clusters.
7308 @internalsref{ClusterSpanner}, @internalsref{ClusterSpannerBeacon},
7309 @inputfileref{input/regression,cluster.ly},
7310 @internalsref{Cluster_spanner_engraver}, and @internalsref{ClusterNoteEvent}.
7314 Music expressions like @code{<< @{ g8 e8 @} a4 >>} are not printed
7315 accurately. Use @code{<g a>8 <e a>8} instead.
7320 @subsection Fermatas
7326 Contemporary music notation frequently uses special fermata symbols to
7327 indicate fermatas of differing lengths.
7331 The following are supported
7333 @lilypond[singleline]
7335 << \addlyrics \notes {
7355 \context Lyrics \lyrics {
7356 "shortfermata" "fermata" "longfermata" "verylongfermata"
7361 See @ref{Articulations} for general instructions how to apply scripts
7362 such as fermatas to a @code{\notes@{@}} block.
7365 @section Tuning output
7367 There are situations where default layout decisions are not
7368 sufficient. In this section we discuss ways to override these
7371 Formatting is internally done by manipulating so called objects
7372 (graphic objects). Each object carries with it a set of properties
7373 (object or layout properties) specific to that object. For example, a
7374 stem object has properties that specify its direction, length and
7377 The most direct way of tuning the output is by altering the values of
7378 these properties. There are two ways of doing that: first, you can
7379 temporarily change the definition of one type of object, thus
7380 affecting a whole set of objects. Second, you can select one specific
7381 object, and set a layout property in that object.
7383 Do not confuse layout properties with translation
7384 properties. Translation properties always use a mixed caps style
7385 naming, and are manipulated using @code{\property}:
7387 \property Context.propertyName = @var{value}
7389 Layout properties are use Scheme style variable naming, i.e. lower
7390 case words separated with dashes. They are symbols, and should always
7391 be quoted using @code{#'}. For example, this could be an imaginary
7392 layout property name:
7394 #'layout-property-name
7399 * Constructing a tweak::
7407 @node Tuning objects
7408 @subsection Tuning objects
7410 @cindex object description
7412 The definition of an object is a list of default object
7413 properties. For example, the definition of the Stem object (available
7414 in @file{scm/define-grobs.scm}), includes the following definitions
7415 for @internalsref{Stem}:
7419 (beamed-lengths . (0.0 2.5 2.0 1.5))
7420 (Y-extent-callback . ,Stem::height)
7425 Adding variables on top of this existing definition overrides the
7426 system default, and alters the resulting appearance of the layout
7432 Changing a variable for only one object is commonly achieved with
7436 \once \property @var{context}.@var{objectname}
7437 \override @var{symbol} = @var{value}
7439 Here @var{symbol} is a Scheme expression of symbol type, @var{context}
7440 and @var{objectname} is a string and @var{value} is a Scheme expression.
7441 This command applies a setting only during one moment in the score.
7443 In the following example, only one @internalsref{Stem} object is
7444 changed from its original setting:
7446 @lilypond[verbatim, fragment, relative=1]
7448 \once \property Voice.Stem \set #'thickness = #4
7452 @cindex @code{\once}
7454 For changing more objects, the same command, without @code{\once} can
7457 \property @var{context}.@var{objectname} \override @var{symbol} = @var{value}
7459 This command adds @code{@var{symbol} = @var{value}} to the definition
7460 of @var{objectname} in the context @var{context}, and this definition
7461 stays in place until it is removed.
7463 An existing definition may be removed by the following command:
7466 \property @var{context}.@var{objectname} \revert @var{symbol}
7469 All @code{\override} and @code{\revert} commands should be balanced.
7470 The @code{\set} shorthand performs a revert followed by an override,
7471 and is often more convenient to use
7474 \property @var{context}.@var{objectname} \set @var{symbol} = @var{value}
7478 @lilypond[verbatim,quote]
7479 c'4 \property Voice.Stem \override #'thickness = #4.0
7481 c'4 \property Voice.Stem \revert #'thickness
7485 The following example gives exactly the same result as the previous
7486 one (assuming the system default for stem thickness is 1.3):
7488 @lilypond[verbatim,quote]
7489 c'4 \property Voice.Stem \set #'thickness = #4.0
7491 c'4 \property Voice.Stem \set #'thickness = #1.3
7495 Reverting a setting which was not set in the first place has no
7496 effect. However, if the setting was set as a system default, this may
7497 remove the default value, and this may give surprising results,
7498 including crashes. In other words, @code{\override} and
7499 @code{\revert} must be carefully balanced. The following are examples
7500 of correct nesting of @code{\override}, @code{\set}, @code{\revert}:
7504 a clumsy but correct form:
7506 \override \revert \override \revert \override \revert
7510 shorter version of the same:
7512 \override \set \set \revert
7516 a short form, using only @code{\set}. This requires you to know the
7519 \set \set \set \set @var{to default value}
7523 if there is no default (i.e. by default, the object property is unset),
7526 \set \set \set \revert
7530 The object description is an Scheme association
7531 list. Since a Scheme list is a singly linked list, we can treat it as
7532 a stack, and @code{\override} and @code{\revert} are push and pop
7533 operations. The association list is stored in a normal context
7536 \property Voice.NoteHead = #'()
7538 will effectively erase @internalsref{NoteHead}s from the current
7539 @internalsref{Voice}. Typically, this will blank the object. However,
7540 this mechanism should not be used: it may cause crashes or other
7545 @internalsref{OverrideProperty}, @internalsref{RevertProperty},
7546 @internalsref{PropertySet}, @internalsref{All-backend-properties}, and
7547 @internalsref{All-layout-objects}.
7552 The backend is not very strict in type-checking object properties.
7553 Cyclic references in Scheme values for properties cause hangs and/or
7554 crashes. Reverting properties that are system defaults may also lead
7557 @node Constructing a tweak
7558 @subsection Constructing a tweak
7561 @cindex internal documentation
7562 @cindex finding graphical objects
7563 @cindex graphical object descriptions
7565 @cindex @code{\override}
7567 @cindex internal documentation
7571 Three pieces of information are required to use @code{\override} and
7572 @code{\set}: the name of the layout object, the context and the name
7573 of the property. We demonstrate how to glean this information from
7574 the notation manual and the generated documentation.
7576 The generated documentation is a set of HTML pages which should be
7577 included if you installed a binary distribution, typically in
7578 @file{/usr/share/doc/lilypond}. They are also available on the web:
7579 go to the @uref{http://lilypond.org,LilyPond website}, click
7580 ``Documentation'', select the correct version, and click then
7581 ``Program reference.'' It is advisable to bookmark the local HTML
7582 files. They will load faster than the ones on the web. If you use the
7583 version from the web, you must check whether the documentation matches
7584 the program version: it is generated from the definitions that the
7585 program uses, and therefore it is strongly tied to the LilyPond
7589 @c [TODO: revise for new site.]
7591 Suppose we want to move the fingering indication in the fragment below:
7593 @lilypond[relative=2,verbatim]
7599 If you visit the documentation of @code{Fingering} (in @ref{Fingering
7600 instructions}), you will notice that there is written:
7605 @internalsref{FingerEvent} and @internalsref{Fingering}.
7612 In other words, the fingerings once entered, are internally stored as
7613 @code{FingerEvent} music objects. When printed, a @code{Fingering}
7614 layout object is created for every @code{FingerEvent}.
7616 The Fingering object has a number of different functions, and each of
7617 those is captured in an interface. The interfaces are listed under
7618 @internalsref{Fingering} in the program reference.
7622 The @code{Fingering} object has a fixed size
7623 (@internalsref{item-interface}), the symbol is a piece of text
7624 (@internalsref{text-interface}), whose font can be set
7625 (@internalsref{font-interface}). It is centered horizontally
7626 (@internalsref{self-alignment-interface}), it is placed next to other
7627 objects (@internalsref{side-position-interface}) vertically, and its
7628 placement is coordinated with other scripts
7629 (@internalsref{text-script-interface}). It also has the standard
7630 @internalsref{grob-interface} (grob stands for Graphical object)
7632 @cindex graphical object
7633 @cindex layout object
7634 @cindex object, layout
7635 with all the variables that come with
7636 it. Finally, it denotes a fingering instruction, so it has
7637 @internalsref{finger-interface}.
7639 For the vertical placement, we have to look under
7640 @code{side-position-interface}:
7642 @code{side-position-interface}
7644 Position a victim object (this one) next to other objects (the
7645 support). In this case, the property @code{direction} signifies where to put the
7646 victim object relative to the support (left or right, up or down?)
7651 below this description, the variable @code{padding} is described as
7655 (dimension, in staff space)
7657 add this much extra space between objects that are next to each
7658 other. Default value: @code{0.6}
7662 By increasing the value of @code{padding}, we can move away the
7663 fingering. The following command inserts 3 staff spaces of white
7664 between the note and the fingering:
7666 \once \property Voice.Fingering \set #'padding = #3
7669 Inserting this command before the Fingering object is created,
7670 i.e. before @code{c2}, yields the following result:
7672 @lilypond[relative=2,fragment,verbatim]
7673 \once \property Voice.Fingering
7680 The context name @code{Voice} in the example above can be determined
7681 as follows. In the documentation for @internalsref{Fingering}, it says
7683 Fingering grobs are created by: @internalsref{Fingering_engraver}
7686 Clicking @code{Fingering_engraver} shows the documentation of
7687 the module responsible for interpreting the fingering instructions and
7688 translating them to a @code{Fingering} object. Such a module is called
7689 an @emph{engraver}. The documentation of the @code{Fingering_engraver}
7692 Fingering_engraver is part of contexts: Voice
7694 so tuning the settings for Fingering should be done with
7696 \property Voice.Fingering \set @dots{}
7699 Of course, the tweak may also done in a larger context than
7700 @code{Voice}, for example, @internalsref{Staff} or
7701 @internalsref{Score}.
7705 The program reference also contains alphabetical lists of
7706 @internalsref{Contexts}, @internalsref{All-layout-objects} and
7707 @internalsref{Music-expressions}, so you can also find which objects to
7708 tweak by browsing the internals document.
7712 @subsection Applyoutput
7714 The most versatile way of tuning an object is @code{\applyoutput}. Its
7717 \applyoutput @var{proc}
7721 where @var{proc} is a Scheme function, taking three arguments.
7723 When interpreted, the function @var{proc} is called for every layout
7724 object found in the context, with the following arguments:
7726 @item the layout object itself,
7727 @item the context where the layout object was created, and
7728 @item the context where @code{\applyoutput} is processed.
7732 In addition, the cause of the layout object, i.e. the music
7733 expression or object that was responsible for creating it, is in the
7734 object property @code{cause}. For example, for a note head, this is a
7735 @internalsref{NoteHead} event, and for a @internalsref{Stem} object,
7736 this is a @internalsref{NoteHead} object.
7738 Here is a simple example of @code{\applyoutput}; it blanks note-heads on the
7741 (define (blanker grob grob-origin context)
7742 (if (and (memq (ly:get-grob-property grob 'interfaces)
7743 note-head-interface)
7744 (eq? (ly:get-grob-property grob 'staff-position) 0))
7746 (ly:set-grob-property! grob 'transparent #t)))
7751 @node Font selection
7752 @subsection Font selection
7754 The most common thing to change about the appearance of fonts is their
7755 size. The font size of any context can be easily changed by setting
7756 the @code{fontSize} property for that context. Its value is an
7757 integer: negative numbers make the font smaller, positive numbers
7758 larger. An example is given below:
7760 @lilypond[fragment,relative=1,verbatim,quote]
7761 c4 c4 \property Voice.fontSize = #-1
7764 This command will set @code{font-relative-size} (see below), and does
7765 not change the size of variable symbols, such as beams or slurs.
7768 One of the uses of @code{fontSize} is to get smaller symbol for cue
7769 notes. An elaborate example of those is in
7770 @inputfileref{input/test,cue-notes.ly}.
7772 @cindex magnification
7774 The size of the font may be scaled with the object property
7775 @code{font-magnification}. For example, @code{2.0} blows up all
7776 letters by a factor 2 in both directions.
7785 The font used for printing a object can be selected by setting
7786 @code{font-name}, e.g.
7788 \property Staff.TimeSignature
7789 \set #'font-name = #"cmr17"
7793 Any font can be used, as long as it is available to @TeX{}. Possible
7794 fonts include foreign fonts or fonts that do not belong to the
7795 Computer Modern font family.
7797 Font selection for the standard fonts, @TeX{}'s Computer Modern fonts,
7798 can also be adjusted with a more fine-grained mechanism. By setting
7799 the object properties described below, you can select a different font;
7800 all three mechanisms work for every object that supports
7801 @code{font-interface}:
7805 is a symbol indicating the general class of the typeface. Supported are
7806 @code{roman} (Computer Modern), @code{braces} (for piano staff
7807 braces), @code{music} (the standard music font, including ancient
7808 glyphs), @code{dynamic} (for dynamic signs) and @code{typewriter}.
7811 is a symbol indicating the shape of the font, there are typically several
7812 font shapes available for each font family. Choices are @code{italic},
7813 @code{caps} and @code{upright}.
7816 is a symbol indicating the series of the font. There are typically several
7817 font series for each font family and shape. Choices are @code{medium}
7820 @item font-relative-size
7821 is a number indicating the size relative the standard size. For example,
7822 with 20pt staff height, relative size -1 corresponds to 16pt staff
7823 height, and relative size +1 corresponds to 23 pt staff height.
7825 There are small differences in design between fonts designed for
7826 different sizes, hence @code{font-relative-size} is preferred over
7827 @code{font-magnification} for changing font sizes.
7830 @item font-design-size
7831 is a number indicating the design size of the font.
7833 This is a feature of the Computer Modern Font: each point size has a
7834 slightly different design. Smaller design sizes are relatively wider,
7835 which enhances readability.
7838 For any of these properties, the value @code{*} (i.e. the symbol
7839 @code{*}, entered as @code{#'*}), acts as a wildcard. This can be used
7840 to override default setting, which are always present. For example:
7842 \property Lyrics . LyricText \override #'font-series = #'bold
7843 \property Lyrics . LyricText \override #'font-family = #'typewriter
7844 \property Lyrics . LyricText \override #'font-shape = #'*
7847 @cindex @code{font-style}
7851 The following commands set @code{fontSize} for the current voice.
7853 @cindex @code{\tiny}
7855 @cindex @code{\small}
7857 @cindex @code{\normalsize}
7862 Relative size is not linked to any real size.
7864 There is no style sheet provided for other fonts besides the @TeX{}
7865 family, and the style sheet cannot be modified easily.
7867 @cindex font selection
7868 @cindex font magnification
7869 @cindex @code{font-interface}
7873 @subsection Text markup
7878 @cindex typeset text
7880 LilyPond has an internal mechanism to typeset texts. You can access it
7881 with the keyword @code{\markup}. Within markup mode, you can enter texts
7882 similar to lyrics: simply enter them, surrounded by spaces:
7885 @lilypond[verbatim,fragment,relative=1]
7886 c1^\markup { hello }
7887 c1_\markup { hi there }
7888 c1^\markup { hi \bold there, is \italic anyone home? }
7891 @cindex font switching
7893 The markup in the example demonstrates font switching commands. The
7894 command @code{\bold} and @code{\italic} only apply to the first
7895 following word; enclose a set of texts with braces to apply a command
7898 \markup @{ \bold @{ hi there @} @}
7902 For clarity, you can also do this for single arguments, e.g.
7904 \markup @{ is \italic @{ anyone @} home @}
7907 @cindex font size, texts
7909 The following size commands set absolute sizes:
7911 @cindex @code{\teeny}
7912 @cindex @code{\tiny}
7913 @cindex @code{\small}
7914 @cindex @code{\large}
7915 @cindex @code{\huge}
7925 You can also make letter larger or smaller relative to their neighbors,
7926 with the commands @code{\larger} and @code{\smaller}.
7930 @cindex font style, for texts
7931 @cindex @code{\bold}
7932 @cindex @code{\dynamic}
7933 @cindex @code{\number}
7934 @cindex @code{\italic}
7936 The following font change commands are defined:
7939 changes to the font used in dynamic signs. This font does not
7940 contain all characters of the alphabet, so when producing ``piu f'',
7941 the ``piu'' should be done in a different font.
7945 changes to the font used in time signatures. It only contains
7946 numbers and a few punctuation marks.
7948 changes @code{font-shape} to @code{italic}.
7950 changes @code{font-series} to @code{bold}.
7953 @cindex raising text
7954 @cindex lowering text
7956 @cindex translating text
7959 @cindex @code{\super}
7961 Raising and lowering texts can be done with @code{\super} and
7964 @lilypond[verbatim,fragment,relative=1]
7965 c1^\markup { E "=" mc \super "2" }
7968 @cindex @code{\raise}
7970 If you want to give an explicit amount for lowering or raising, use
7971 @code{\raise}. This command takes a Scheme valued first argument, and
7972 a markup object as second argument:
7974 @lilypond[verbatim,fragment,relative=1,quote]
7975 c1^\markup { C \small \raise #1.0 \bold { "9/7+" }}
7977 The argument to @code{\raise} is the vertical displacement amount,
7978 measured in (global) staff spaces. @code{\raise} and @code{\super}
7979 raise objects in relation to their surrounding markups. They cannot be
7980 used to move a single text up or down, when it is above or below a
7981 note, since the mechanism that positions it next to the note cancels
7982 any vertical shift. For vertical positioning, use the @code{padding}
7983 and/or @code{extra-offset} properties.
7985 Other commands taking single arguments include
7988 @item \bracket, \hbracket
7989 Bracket the argument markup with normal and horizontal brackets
7993 @cindex @code{\musicglyph}
7994 This is converted to a musical symbol, e.g. @code{\musicglyph
7995 #"accidentals-0"} will select the natural sign from the music font.
7996 See @ref{The Feta font} for a complete listing of the possible glyphs.
7998 This produces a single character, e.g. @code{\char #65} produces the
8001 @item \note @var{log} @var{dots} @var{dir}
8002 @cindex @code{\note}
8004 This produces a note with a stem pointing in @var{dir} direction, with
8005 duration log @var{log} and @var{dots} augmentation dots. The duration
8006 log is the negative 2-logarithm of the duration denominator. For
8007 example, a quarter note has log 2, an eighth note 3 and a breve has
8010 @item \hspace #@var{amount}
8011 @cindex @code{\hspace}
8012 This produces a invisible object taking horizontal space.
8014 \markup @{ A \hspace #2.0 B @}
8016 will put extra space between A and B, on top of the space that is
8017 normally inserted before elements on a line.
8019 @item \fontsize #@var{size}
8020 @cindex @code{\fontsize}
8021 This sets the relative font size, eg.
8023 A \fontsize #2 @{ B C @} D
8027 This will enlarge the B and the C by two steps.
8028 @item \translate #(cons @var{x} @var{y})
8030 This translates an object. Its first argument is a cons of numbers
8032 A \translate #(cons 2 -3) @{ B C @} D
8034 This moves `B C' 2 spaces to the right, and 3 down.
8036 @item \magnify #@var{mag}
8037 @cindex @code{\magnify}
8038 This sets the font magnification for the its argument. In the following
8039 example, the middle A will be 10% larger:
8041 A \magnify #1.1 @{ A @} A
8045 @item \override #(@var{key} . @var{value})
8046 @cindex @code{\override}
8047 This overrides a formatting property for its argument. The argument
8048 should be a key/value pair, e.g.
8050 m \override #'(font-family . math) m m
8054 In markup mode you can compose expressions, similar to mathematical
8055 expressions, XML documents and music expressions. The braces group
8056 notes into horizontal lines. Other types of lists also exist: you can
8057 stack expressions grouped with @code{<}, and @code{>} vertically with
8058 the command @code{\column}. Similarly, @code{\center} aligns texts by
8061 @lilypond[verbatim,fragment,relative=1]
8062 c1^\markup { \column < a bbbb c > }
8063 c1^\markup { \center < a bbbb c > }
8064 c1^\markup { \line < a b c > }
8067 The markup mechanism is extensible. Refer to
8068 @file{scm/new-markup.scm} for more information.
8074 @internalsref{Markup-functions}, and @file{scm/new-markup.scm}.
8081 Text layout is ultimately done by @TeX{}, which does kerning of
8082 letters. LilyPond does not account for kerning, so texts will be
8083 spaced slightly too wide.
8085 Syntax errors for markup mode are confusing.
8087 Markup texts cannot be used in the titling of the @code{\header}
8088 field. Titles are made by La@TeX{}, so La@TeX{} commands should be used
8095 @section Global layout
8097 The global layout determined by three factors: the page layout, the
8098 line breaks and the spacing. These all influence each other. The
8099 choice of spacing determines how densely each system of music is set,
8100 which influences where line breaks breaks are chosen, and thus
8101 ultimately how many pages a piece of music takes. This section
8102 explains how to tune the algorithm for spacing.
8104 Globally spoken, this procedure happens in three steps: first,
8105 flexible distances (``springs'') are chosen, based on durations. All
8106 possible line breaking combination are tried, and the one with the
8107 best results---a layout that has uniform density and requires as
8108 little stretching or cramping as possible---is chosen. When the score
8109 is processed by @TeX{}, each page is filled with systems, and page breaks
8110 are chosen whenever the page gets full.
8115 * Vertical spacing::
8116 * Horizontal spacing::
8123 @node Vertical spacing
8124 @subsection Vertical spacing
8126 @cindex vertical spacing
8127 @cindex distance between staves
8128 @cindex staff distance
8129 @cindex between staves, distance
8130 @cindex staffs per page
8131 @cindex space between staves
8133 The height of each system is determined automatically by LilyPond, to
8134 keep systems from bumping into each other, some minimum distances are
8135 set. By changing these, you can put staves closer together, and thus
8136 put more systems onto one page.
8138 Normally staves are stacked vertically. To make
8139 staves maintain a distance, their vertical size is padded. This is
8140 done with the property @code{minimumVerticalExtent}. It takes a pair
8141 of numbers, so if you want to make it smaller from its, then you could
8144 \property Staff.minimumVerticalExtent = #'(-4 . 4)
8146 This sets the vertical size of the current staff to 4 staff spaces on
8147 either side of the center staff line. The argument of
8148 @code{minimumVerticalExtent} is interpreted as an interval, where the
8149 center line is the 0, so the first number is generally negative. The
8150 staff can be made larger at the bottom by setting it to @code{(-6
8153 The piano staves are handled a little differently: to make cross-staff
8154 beaming work correctly, it is necessary that the distance between staves
8155 is fixed beforehand. This is also done with a
8156 @internalsref{VerticalAlignment} object, created in
8157 @internalsref{PianoStaff}. In this object the distance between the
8158 staves is fixed by setting @code{forced-distance}. If you want to
8159 override this, use a @code{\translator} block as follows:
8163 VerticalAlignment \override #'forced-distance = #9
8166 This would bring the staves together at a distance of 9 staff spaces,
8167 measured from the center line of each staff.
8171 Vertical alignment of staves is handled by the
8172 @internalsref{VerticalAlignment} object.
8176 @node Horizontal spacing
8177 @subsection Horizontal Spacing
8179 The spacing engine translates differences in durations into
8180 stretchable distances (``springs'') of differing lengths. Longer
8181 durations get more space, shorter durations get less. The shortest
8182 durations get a fixed amount of space (which is controlled by
8183 @code{shortest-duration-space} in the @internalsref{SpacingSpanner} object).
8184 /The longer the duration, the more space it gets: doubling a
8185 duration adds a fixed amount (this amount is controlled by
8186 @code{spacing-increment}) of space to the note.
8188 For example, the following piece contains lots of half, quarter and
8189 8th notes, the eighth note is followed by 1 note head width (NHW).
8190 The quarter note is followed by 2 NHW, the half by 3 NHW, etc.
8191 @lilypond[fragment, verbatim, relative=1] c2 c4. c8 c4. c8 c4. c8 c8
8195 Normally, @code{shortest-duration-space} is set to 1.2, which is the
8196 width of a note head, and @code{shortest-duration-space} is set to
8197 2.0, meaning that the shortest note gets 2 NHW (2 times
8198 @code{shortest-duration-space}) of space. For normal notes, this space
8199 is always counted from the left edge of the symbol, so the shortest
8200 notes are generally followed by one NHW of space.
8202 If one would follow the above procedure exactly, then adding a single
8203 32th note to a score that uses 8th and 16th notes, would widen up the
8204 entire score a lot. The shortest note is no longer a 16th, but a 32nd,
8205 thus adding 1 NHW to every note. To prevent this, the
8206 shortest duration for spacing is not the shortest note in the score,
8207 but the most commonly found shortest note. Notes that are even
8208 shorter this are followed by a space that is proportional to their
8209 duration relative to the common shortest note. So if we were to add
8210 only a few 16th notes to the example above, they would be followed by
8213 @lilypond[fragment, verbatim, relative=2]
8214 c2 c4. c8 c4. c16[ c] c4. c8 c8 c8 c4 c4 c4
8217 The most common shortest duration is determined as follows: in every
8218 measure, the shortest duration is determined. The most common short
8219 duration, is taken as the basis for the spacing, with the stipulation
8220 that this shortest duration should always be equal to or shorter than
8221 1/8th note. The shortest duration is printed when you run lilypond
8222 with @code{--verbose}. These durations may also be customized. If you
8223 set the @code{common-shortest-duration} in
8224 @internalsref{SpacingSpanner}, then this sets the base duration for
8225 spacing. The maximum duration for this base (normally 1/8th), is set
8226 through @code{base-shortest-duration}.
8228 @cindex @code{common-shortest-duration}
8229 @cindex @code{base-shortest-duration}
8230 @cindex @code{stem-spacing-correction}
8231 @cindex @code{spacing}
8233 In the introduction it was explained that stem directions influence
8234 spacing. This is controlled with @code{stem-spacing-correction}
8235 property in @internalsref{NoteSpacing}, which are generated for every
8236 @internalsref{Voice} context. The @code{StaffSpacing} object
8237 (generated at @internalsref{Staff} context) contains the same property
8238 for controlling the stem/barline spacing. The following example
8239 shows these corrections, once with default settings, and once with
8240 exaggerated corrections:
8246 \property Staff.NoteSpacing \override #'stem-spacing-correction
8248 \property Staff.StaffSpacing \override #'stem-spacing-correction
8253 \paper { raggedright = ##t } }
8256 @cindex SpacingSpanner, overriding properties
8258 Properties of the @internalsref{SpacingSpanner} must be overridden
8259 from the @code{\paper} block, since the @internalsref{SpacingSpanner} is
8260 created before any @code{\property} statements are interpreted.
8262 \paper @{ \translator @{
8264 SpacingSpanner \override #'spacing-increment = #3.0
8271 @internalsref{SpacingSpanner}, @internalsref{NoteSpacing},
8272 @internalsref{StaffSpacing}, @internalsref{SeparationItem}, and
8273 @internalsref{SeparatingGroupSpanner}.
8277 Spacing is determined on a score wide basis. If you have a score that
8278 changes its character (measured in durations) halfway during the
8279 score, the part containing the longer durations will be spaced too
8282 There is no convenient mechanism to manually override spacing.
8287 @subsection Font size
8288 @cindex font size, setting
8289 @cindex staff size, setting
8290 @cindex @code{paper} file
8292 The Feta font provides musical symbols at seven different sizes.
8293 These fonts are 11 point, 13 point, 16 point, 20 point, 23 point, and
8294 26 point. The point size of a font is the height of the corresponding
8295 staff (excluding line thicknesses).
8297 Definitions for these sizes are the files @file{paperSZ.ly}, where
8298 @code{SZ} is one of 11, 13, 16, 20, 23 and 26. If you include any
8299 of these files, the variables @code{paperEleven},
8300 @code{paperThirteen}, @code{paperSixteen},
8301 @code{paperTwenty}, @code{paperTwentythree}, and @code{paperTwentysix}
8302 are defined respectively. The default @code{\paper} block is also
8303 set. These files should be imported at toplevel, i.e.
8305 \include "paper26.ly"
8309 The default font size settings for each staff heights are generated
8310 from the 20pt style sheet. For more details, see the file
8311 @file{scm/font.scm}.
8315 @subsection Line breaking
8318 @cindex breaking lines
8320 Line breaks are normally computed automatically. They are chosen such
8321 that lines look neither cramped nor loose, and that consecutive lines
8322 have similar density.
8324 Occasionally you might want to override the automatic breaks; you can
8325 do this by specifying @code{\break}. This will force a line break at
8326 this point. Line breaks can only occur at places where there are bar
8327 lines. If you want to have a line break where there is no bar line,
8328 you can force an invisible bar line by entering @code{\bar
8329 ""}. Similarly, @code{\noBreak} forbids a line break at a
8333 @cindex regular line breaks
8334 @cindex four bar music.
8336 For linebreaks at regular intervals use @code{\break} separated by
8337 skips and repeated with @code{\repeat}:
8339 << \repeat unfold 7 @{ s1 * 4 \break @}
8340 @emph{the real music}
8345 This makes the following 28 measures (assuming 4/4 time) be broken every
8350 @internalsref{BreakEvent}.
8354 @subsection Page layout
8357 @cindex breaking pages
8359 @cindex @code{indent}
8360 @cindex @code{linewidth}
8362 The most basic settings influencing the spacing are @code{indent} and
8363 @code{linewidth}. They are set in the @code{\paper} block. They
8364 control the indentation of the first line of music, and the lengths of
8367 If @code{raggedright} is set to true in the @code{\paper}
8368 block, then the lines are justified at their natural length. This
8369 useful for short fragments, and for checking how tight the natural
8373 @cindex vertical spacing
8375 The page layout process happens outside the LilyPond formatting
8376 engine: variables controlling page layout are passed to the output,
8377 and are further interpreted by @code{lilypond} wrapper program. It
8378 responds to the following variables in the @code{\paper} block. The
8379 variable @code{textheight} sets the total height of the music on each
8380 page. The spacing between systems is controlled with
8381 @code{interscoreline}, its default is 16pt. The distance between the
8382 score lines will stretch in order to fill the full page
8383 @code{interscorelinefill} is set to a positive number. In that case
8384 @code{interscoreline} specifies the minimum spacing.
8386 @cindex @code{textheight}
8387 @cindex @code{interscoreline}
8388 @cindex @code{interscorelinefill}
8390 If the variable @code{lastpagefill} is defined,
8391 @c fixme: this should only be done if lastpagefill == #t
8392 systems are evenly distributed vertically on the last page. This
8393 might produce ugly results in case there are not enough systems on the
8394 last page. The @command{lilypond-book} command ignores
8395 @code{lastpagefill}. See @ref{lilypond-book manual} for more
8398 @cindex @code{lastpagefill}
8400 Page breaks are normally computed by @TeX{}, so they are not under
8401 direct control of LilyPond. However, you can insert a commands into
8402 the @file{.tex} output to instruct @TeX{} where to break pages. This
8403 is done by setting the @code{between-systems-strings} on the
8404 @internalsref{NonMusicalPaperColumn} where the system is broken.
8405 An example is shown in @inputfileref{input/regression,between-systems.ly}.
8406 The predefined command @code{\newpage} also does this.
8410 @cindex @code{papersize}
8412 To change the paper size, you must first set the @code{papersize} paper
8413 variable variable as in the example below. Set it to
8414 the strings @code{a4}, @code{letter}, or @code{legal}. After this
8415 specification, you must set the font as described above. If you want
8416 the default font, then use the 20 point font.
8419 \paper@{ papersize = "a4" @}
8420 \include "paper16.ly"
8423 The file @code{paper16.ly} will now include a file named @file{a4.ly}, which
8424 will set the paper variables @code{hsize} and @code{vsize} (used by
8425 @code{lilypond-book} and @code{lilypond}).
8430 @cindex @code{\newpage}
8436 @ref{Invoking lilypond},
8437 @inputfileref{input/regression,between-systems.ly}, and
8438 @internalsref{NonMusicalPaperColumn}.
8442 LilyPond has no concept of page layout, which makes it difficult to
8443 reliably choose page breaks in longer pieces.
8452 Entered music can also be converted to MIDI output. The performance
8453 is good enough for proof-hearing the music for errors.
8455 Ties, dynamics and tempo changes are interpreted. Dynamic marks,
8456 crescendi and decrescendi translate into MIDI volume levels. Dynamic
8457 marks translate to a fixed fraction of the available MIDI volume
8458 range, crescendi and decrescendi make the volume vary linearly between
8459 their two extremities. The fractions can be adjusted by
8460 @code{dynamicAbsoluteVolumeFunction} in @internalsref{Voice} context.
8461 For each type of MIDI instrument, a volume range can be defined. This
8462 gives a basic equalizer control, which can enhance the quality of
8463 the MIDI output remarkably. The equalizer can be controlled by
8464 setting @code{instrumentEqualizer}.
8468 Many musically interesting effects, such as swing, articulation,
8469 slurring, etc., are not translated to MIDI.
8474 * MIDI instrument names::
8479 @subsection MIDI block
8483 The MIDI block is analogous to the paper block, but it is somewhat
8484 simpler. The @code{\midi} block can contain:
8488 @item a @code{\tempo} definition, and
8489 @item context definitions.
8492 Assignments in the @code{\midi} block are not allowed.
8494 A number followed by a period is interpreted as a real number, so
8495 for setting the tempo for dotted notes, an extra space should be
8496 inserted, for example:
8499 \midi @{ \tempo 4 . = 120 @}
8503 @cindex context definition
8505 Context definitions follow precisely the same syntax as within the
8506 \paper block. Translation modules for sound are called performers.
8507 The contexts for MIDI output are defined in @file{ly/performer-init.ly}.
8510 @node MIDI instrument names
8511 @subsection MIDI instrument names
8513 @cindex instrument names
8514 @cindex @code{Staff.midiInstrument}
8515 @cindex @code{Staff.instrument}
8517 The MIDI instrument name is set by the @code{Staff.midiInstrument}
8518 property or, if that property is not set, the @code{Staff.instrument}
8519 property. The instrument name should be chosen from the list in
8520 @ref{MIDI instruments}.
8524 If the selected string does not exactly match, then LilyPond uses the
8525 default (Grand Piano). It is not possible to select an instrument by