1 @c -*- coding: latin-1; mode: texinfo; -*-
2 @c This file is part of lilypond.tely
4 @c A menu is needed before every deeper *section nesting of @node's; run
5 @c M-x texinfo-all-menus-update
6 @c to automatically fill in these menus before saving changes
9 @chapter Notation manual
11 This chapter describes all the different types of notation supported
12 by LilyPond. It is intended as a reference for users who are already
13 somewhat familiar with LilyPond.
17 * Easier music entry::
27 * Other instrument specific notation::
32 * Contemporary notation::
36 @c FIXME: Note entry vs Music entry at top level menu is confusing.
42 This section is about basic notation elements like notes, rests, and
43 related constructs, such as stems, tuplets and ties.
48 * Chromatic alterations::
66 A note is printed by specifying its pitch and then its duration,
68 @lilypond[quote,verbatim,raggedright]
69 { cis'4 d'8 e'16 c'16 }
77 @cindex Note specification
79 @cindex entering notes
81 The most common syntax for pitch entry is used for standard notes and
82 @code{\chordmode} modes. In these modes, pitches may be designated by
83 names. The notes are specified by the letters @code{a} through
84 @code{g}. The octave is formed with notes ranging from @code{c}
85 to @code{b}. The pitch @code{c} is an octave below middle C and the
86 letters span the octave above that C
88 @lilypond[quote,fragment,verbatim]
90 a,4 b, c d e f g a b c' d' e' \clef treble f' g' a' b' c''
93 @cindex note names, Dutch
95 A sharp is formed by adding @code{-is} to the end of a pitch name and
96 a flat is formed by adding @code{-es}. Double sharps and double flats
97 are obtained by adding @code{-isis} or @code{-eses}. These
98 names are the Dutch note names. In Dutch, @code{aes} is contracted to
99 @code{as}, but both forms are accepted. Similarly, both
100 @code{es} and @code{ees} are accepted
102 @lilypond[fragment,quote,raggedright,verbatim,relative=2]
110 In accordance with standard typsetting rules, a natural sign is printed
111 before a sharp or flat if a previous accidental needs to be
112 cancelled. To change this behaviour, use
113 @code{\set Staff.extraNatural = ##f}
115 @lilypond[fragment,quote,raggedright,verbatim,relative=2]
117 \set Staff.extraNatural = ##f
121 There are predefined sets of note names for various other languages.
122 To use them, include the language specific init file. For
123 example: @code{\include "english.ly"}. The available language files
124 and the note names they define are
129 Note Names sharp flat
130 nederlands.ly c d e f g a bes b -is -es
131 english.ly c d e f g a bf b -s/-sharp -f/-flat
133 deutsch.ly c d e f g a b h -is -es
134 norsk.ly c d e f g a b h -iss/-is -ess/-es
135 svenska.ly c d e f g a b h -iss -ess
136 italiano.ly do re mi fa sol la sib si -d -b
137 catalan.ly do re mi fa sol la sib si -d/-s -b
138 espanol.ly do re mi fa sol la sib si -s -b
146 The optional octave specification takes the form of a series of
147 single quote (`@code{'}') characters or a series of comma
148 (`@code{,}') characters. Each @code{'} raises the pitch by one
149 octave; each @code{,} lowers the pitch by an octave
151 @lilypond[quote,raggedright,fragment,verbatim]
152 c' c'' es' g' as' gisis' ais'
155 @c FIXME: we need this info (hide/unhide) somewhere in the manual, but this ain't the place. -gp
157 Notes can be hidden and unhidden with the following commands
159 @cindex @code{\hideNotes}
161 @cindex @code{\unHideNotes}
167 Program reference: @internalsref{NoteEvent}, and @internalsref{NoteHead}.
171 @node Chromatic alterations
172 @subsection Chromatic alterations
174 Normally accidentals are printed automatically, but you may also
175 print them manually. A reminder accidental
176 @cindex reminder accidental
178 can be forced by adding an exclamation mark @code{!}
179 after the pitch. A cautionary accidental
180 @cindex cautionary accidental
181 @cindex parenthesized accidental
182 (i.e., an accidental within parentheses) can be obtained by adding the
183 question mark `@code{?}' after the pitch.
185 @lilypond[quote,raggedright,fragment,verbatim]
186 cis' cis' cis'! cis'?
192 The automatic production of accidentals can be tuned in many
193 ways. For more information, refer to @ref{Automatic accidentals}.
198 @subsection Micro tones
200 Half-flats and half-sharps are formed by adding @code{-eh} and
201 @code{-ih}; the following is a series of Cs with increasing pitches
203 @cindex quarter tones
204 @cindex semi-flats, semi-sharps
206 @lilypond[verbatim,raggedright,quote,relative=2,fragment]
207 { ceseh ceh cih cisih }
210 Micro tones are also exported to the MIDI file
215 There are no generally accepted standards for denoting three quarter
216 flats, so LilyPond's symbol does not conform to any standard.
221 A chord is formed by a enclosing a set of pitches in @code{<} and
222 @code{>}. A chord may be followed by a duration, and a set of
223 articulations, just like simple notes
225 @lilypond[verbatim,raggedright,fragment,quote,relative=1]
237 Rests are entered like notes, with the note name @code{r}
239 @lilypond[fragment,quote,raggedright,verbatim]
243 Whole bar rests, centered in middle of the bar,
244 must be done with multi-measure rests. They are discussed in
245 @ref{Multi measure rests}.
248 A rest's vertical position may be explicitly specified by entering a
249 note with the @code{\rest} keyword appended, the rest will be placed at
250 the note's place. This makes manual formatting in polyphonic music
251 easier. Automatic rest collision formatting will leave these rests
254 @lilypond[fragment,quote,raggedright,verbatim]
260 Program reference: @internalsref{RestEvent}, and @internalsref{Rest}.
267 @cindex Invisible rest
272 An invisible rest (also called a `skip') can be entered like a note
273 with note name `@code{s}' or with @code{\skip @var{duration}}
275 @lilypond[fragment,quote,raggedright,verbatim,relative=2]
276 a4 a4 s4 a4 \skip 1 a4
279 The @code{s} syntax is only available in note mode and chord mode. In
280 other situations, for example, when entering lyrics, you should use
281 the @code{\skip} command
283 @lilypond[quote,raggedright,verbatim]
286 \new Lyrics \lyricmode { \skip 2 bla1 }
290 The skip command is merely an empty musical placeholder. It does not
291 produce any output, not even transparent output.
293 The @code{s} skip command does create @internalsref{Staff} and
294 @internalsref{Voice} when necessary, similar to note and rest
295 commands. For example, the following results in an empty staff.
297 @lilypond[quote,raggedright,verbatim]
301 The fragment @code{@{ \skip 4 @} } would produce an empty page.
305 Program reference: @internalsref{SkipEvent}, @internalsref{SkipMusic}.
310 @subsection Durations
314 @cindex @code{\longa}
315 @cindex @code{\breve}
316 @cindex @code{\maxima}
319 In Note, Chord, and Lyrics mode, durations are designated by numbers and
320 dots: durations are entered as their reciprocal values. For example, a
321 quarter note is entered using a @code{4} (since it is a 1/4 note), while
322 a half note is entered using a @code{2} (since it is a 1/2 note). For
323 notes longer than a whole you must use the variables @code{\longa} and
328 c'1 c'2 c'4 c'8 c'16 c'32 c'64 c'64
330 r1 r2 r4 r8 r16 r32 r64 r64
336 a\breve*1/2 \autoBeamOff
337 a1 a2 a4 a8 a16 a32 a64 a64
340 r\longa*1/4 r\breve *1/2
341 r1 r2 r4 r8 r16 r32 r64 r64
347 \remove "Clef_engraver"
348 \override StaffSymbol #'transparent = ##t
349 \override TimeSignature #'transparent = ##t
350 \override BarLine #'transparent = ##t
351 \consists "Pitch_squash_engraver"
357 If the duration is omitted then it is set to the previously entered
358 duration. The default for the first note is a quarter note.
360 @lilypond[quote,raggedright,verbatim,fragment]
361 { a a a2 a a4 a a1 a }
366 @node Augmentation dots
367 @subsection Augmentation dots
370 To obtain dotted note lenghts, simply add a dot (`@code{.}') to
371 the number. Double-dotted notes are produced in a similar way.
373 @lilypond[quote,raggedright,fragment,verbatim]
374 a'4 b' c''4. b'8 a'4. b'4.. c''8.
379 Dots are normally moved up to avoid staff lines, except in polyphonic
380 situations. The following commands may be used to force a particular
383 @cindex @code{\dotsUp}
385 @cindex @code{\dotsDown}
387 @cindex @code{\dotsNeutral}
392 Program reference: @internalsref{Dots}, and @internalsref{DotColumn}.
394 @node Scaling durations
395 @subsection Scaling durations
397 You can alter the length of duration by a fraction @var{N/M}
398 appending `@code{*}@var{N/M}' (or `@code{*}@var{N}' if @var{M=1}). This
399 will not affect the appearance of the notes or rests produced.
401 In the following example, the first three notes take up exactly two
402 beats, but no triplet bracket is printed.
403 @lilypond[quote,raggedright,fragment,relative=2,verbatim]
405 a4*2/3 gis4*2/3 a4*2/3
413 This manual: @ref{Tuplets}
416 @c TODO: I'm not certain that Stems belong here in the manual. -gp
420 Whenever a note is found, a @internalsref{Stem} object is created
421 automatically. For whole notes and rests, they are also created but
426 @cindex @code{\stemUp}
428 @cindex @code{\stemDown}
430 @cindex @code{\stemNeutral}
441 A tie connects two adjacent note heads of the same pitch. The tie in
442 effect extends the length of a note. Ties should not be confused with
443 slurs, which indicate articulation, or phrasing slurs, which indicate
444 musical phrasing. A tie is entered using the tilde symbol `@code{~}'
446 @lilypond[quote,raggedright,fragment,verbatim]
447 e' ~ e' <c' e' g'> ~ <c' e' g'>
450 When a tie is applied to a chord, all note heads whose pitches match
451 are connected. When no note heads match, no ties will be created.
453 A tie is just a way of extending a note duration, similar to the
454 augmentation dot. The following example shows two ways of notating
455 exactly the same concept
457 @lilypond[quote,fragment,raggedright]
458 \time 3/4 c'2. c'2 ~ c'4
462 Ties are used either when the note crosses a bar line, or when dots
463 cannot be used to denote the rhythm. When using ties, larger note
464 values should be aligned to subdivisions of the measure, eg.
466 @lilypond[fragment,quote,raggedright]
468 r8 c8 ~ c2 r4 | r8^"not" c2 ~ c8 r4
472 If you need to tie a lot of notes over bars, it may be easier to use
473 automatic note splitting (see @ref{Automatic note splitting}). This
474 mechanism automatically splits long notes, and ties them across bar
480 @cindex @code{\tieUp}
482 @cindex @code{\tieDown}
484 @cindex @code{\tieNeutral}
486 @cindex @code{\tieDotted}
488 @cindex @code{\tieSolid}
493 In this manual: @ref{Automatic note splitting}.
495 Program reference: @internalsref{TieEvent}, @internalsref{Tie}.
500 Switching staves when a tie is active will not produce a slanted tie.
502 Formatting of ties is a difficult subject. The results are often not
510 @cindex @code{\times}
512 Tuplets are made out of a music expression by multiplying all durations
515 @cindex @code{\times}
517 \times @var{fraction} @var{musicexpr}
521 The duration of @var{musicexpr} will be multiplied by the fraction.
522 The fraction's denominator will be printed over the notes, optionally
523 with a bracket. The most common tuplet is the triplet in which 3
524 notes have the length of 2, so the notes are 2/3 of their written
527 @lilypond[quote,raggedright,fragment,verbatim]
528 g'4 \times 2/3 {c'4 c' c'} d'4 d'4
531 The property @code{tupletSpannerDuration} specifies how long each
532 bracket should last. With this, you can make lots of tuplets while
533 typing @code{\times} only once, thus saving lots of typing. In the next
534 example, there are two triplets shown, while @code{\times} was only
537 @lilypond[quote,fragment,relative=1,raggedright,verbatim]
538 \set tupletSpannerDuration = #(ly:make-moment 1 4)
539 \times 2/3 { c'8 c c c c c }
542 The format of the number is determined by the property
543 @code{tupletNumberFormatFunction}. The default prints only the
544 denominator, but if it is set to the Scheme function
545 @code{fraction-tuplet-formatter}, @var{num}:@var{den} will be printed
549 @cindex @code{tupletNumberFormatFunction}
550 @cindex tuplet formatting
555 @cindex @code{\tupletUp}
557 @cindex @code{\tupletDown}
559 @cindex @code{\tupletNeutral}
560 @code{\tupletNeutral}.
564 User manual: @ref{Changing context properties on the fly} for the
568 Program reference: @internalsref{TupletBracket}, and @internalsref{TimeScaledMusic}.
570 Examples: @inputfileref{input/@/regression,tuplet@/-nest@/.ly}.
574 Nested tuplets are not formatted automatically. In this case, outer
575 tuplet brackets should be moved manually, which is demonstrated in
576 @inputfileref{input/@/regression,tuplet@/-nest@/.ly}.
580 @node Easier music entry
581 @section Easier music entry
584 This section deals with tricks and features of the input language that
585 were added solely to help entering music and finding and correcting
586 mistakes. There are also external tools that make debugging easier.
587 See @ref{Point and click} for more information.
589 It is also possible to enter and edit music using other programs, such as
590 GUI interfaces or MIDI sequencers. Refer to the LilyPond
591 website for more information.
598 * Skipping corrected music::
599 * Automatic note splitting::
605 @node Relative octaves
606 @subsection Relative octaves
608 @cindex relative octave specification
610 Octaves are specified by adding @code{'} and @code{,} to pitch names.
611 When you copy existing music, it is easy to accidentally put a pitch
612 in the wrong octave and hard to find such an error. The relative
613 octave mode prevents these errors by making the mistakes much
614 larger: a single error puts the rest of the piece off by one octave
616 @cindex @code{\relative}
618 \relative @var{startpitch} @var{musicexpr}
625 \relative @var{musicexpr}
628 The octave of notes that appear in @var{musicexpr} are calculated as
629 follows: if no octave changing marks are used, the basic interval
630 between this and the last note is always taken to be a fourth or
631 less. This distance is determined without regarding alterations; a
632 @code{fisis} following a @code{ceses} will be put above the
633 @code{ceses}. In other words, a doubly-augmented fourth is considered
634 a smaller interval than a diminshed fifth, even though the fourth is
635 seven semitones while the fifth is only six semitones.
637 The octave changing marks @code{'} and @code{,} can be added to raise
638 or lower the pitch by an extra octave. Upon entering relative mode,
639 an absolute starting pitch can be specified that will act as the
640 predecessor of the first note of @var{musicexpr}. If no starting pitch
641 is specified, then middle C is used as a start.
643 Here is the relative mode shown in action
644 @lilypond[quote,fragment,raggedright,verbatim]
650 Octave changing marks are used for intervals greater than a fourth
651 @lilypond[quote,raggedright,fragment,verbatim]
657 If the preceding item is a chord, the first note of the chord is used
658 to determine the first note of the next chord
660 @lilypond[quote,raggedright,fragment,verbatim]
668 The pitch after the @code{\relative} contains a note name.
671 The relative conversion will not affect @code{\transpose},
672 @code{\chordmode} or @code{\relative} sections in its argument. To use
673 relative within transposed music, an additional @code{\relative} must
674 be placed inside @code{\transpose}.
677 @subsection Octave check
680 Octave checks make octave errors easier to correct: a note may be
681 followed by @code{=}@var{quotes} which indicates what its absolute
682 octave should be. In the following example,
684 \relative c'' @{ c='' b=' d,='' @}
688 @c take care with @code, adds confusing quotes.
689 the @code{d} will generate a warning, because a @code{d''} is expected
690 (because @code{b'} to @code{d''} is only a third), but a @code{d}' is
691 found. In the output, the octave is corrected to be a @code{d''} and
692 the next note is calculated relative to @code{d''} instead of @code{d'}.
696 There is also a syntax that is separate from the notes. The syntax
702 This checks that @var{pitch} (without quotes) yields @var{pitch} (with
703 quotes) in \relative mode. If not, a warning is printed, and the
706 In the example below, the first check passes without incident, since
707 the @code{e} (in relative mode) is within a fifth of @code{a'}. However,
708 the second check produces a warning, since the @code{e} is not within
709 a fifth of @code{b'}. The warning message is printed, and the octave
710 is adjusted so that the following notes are in the correct octave
722 The octave of a note following an octave check is determined with
723 respect to the note preceding it. In the next fragment, the last note
724 is a @code{a'}, above middle C. That means that the @code{\octave}
725 check passes successfully, so the check could be deleted without changing
726 the output of the piece.
728 @lilypond[quote,raggedright,verbatim,fragment]
737 @subsection Bar check
741 @cindex @code{barCheckSynchronize}
744 Bar checks help detect errors in the durations. A bar check is
745 entered using the bar symbol, `@code{|}'. Whenever it is encountered
746 during interpretation, it should fall on a measure boundary. If it
747 does not, a warning is printed. In the next example, the second bar
748 check will signal an error
750 \time 3/4 c2 e4 | g2 |
753 Bar checks can also be used in lyrics, for example
758 Twin -- kle | Twin -- kle
763 @cindex @code{skipTypesetting}
765 Failed bar checks are caused by entering incorrect
766 durations. Incorrect durations often completely garble up the score,
767 especially if the score is polyphonic, so a good place to start correcting
768 input is by scanning for failed bar checks and incorrect durations. To
769 speed up this process, the @code{skipTypesetting} feature may be
770 used. It is described in the next section.
773 @cindex @code{pipeSymbol}
775 It is also possible to redefine the meaning of @code{|}. This is done
776 by assigning a music expression to @code{pipeSymbol},
778 @lilypond[quote,raggedright,verbatim]
779 pipeSymbol = \bar "||"
785 @node Skipping corrected music
786 @subsection Skipping corrected music
788 The property @code{Score.skipTypesetting} can be used to switch on and
789 off typesetting completely during the interpretation phase. When
790 typesetting is switched off, the music is processed much more
791 quickly. This can be used to skip over the parts of a score that
792 have already been checked for errors
794 @lilypond[quote,fragment,raggedright,verbatim]
797 \set Score.skipTypesetting = ##t
799 \set Score.skipTypesetting = ##f
803 In polyphonic music, @code{Score.skipTypesetting} will affect all
804 voices and staves, saving even more time.
806 @node Automatic note splitting
807 @subsection Automatic note splitting
809 Long notes can be converted automatically to tied notes. This is done
810 by replacing the @internalsref{Note_heads_engraver} by the
811 @internalsref{Completion_heads_engraver}.
812 In the following examples, notes crossing the bar line are split and tied.
815 @lilypond[quote,fragment,verbatim,relative=1,linewidth=12\cm]
817 \remove "Note_heads_engraver"
818 \consists "Completion_heads_engraver"
820 c2. c8 d4 e f g a b c8 c2 b4 a g16 f4 e d c8. c2
824 This engraver splits all running notes at the bar line, and inserts
825 ties. One of its uses is to debug complex scores: if the measures are
826 not entirely filled, then the ties exactly show how much each measure
831 Not all durations (especially those containing tuplets) can be
832 represented exactly with normal notes and dots, but the engraver will
837 Examples: @inputfileref{input/@/regression,completion@/-heads@/.ly}.
841 Program reference: @internalsref{Completion_heads_engraver}.
845 @section Staff notation
847 This section describes music notation that occurs on staff level,
848 such as key signatures, clefs and time signatures.
850 @cindex Staff notation
861 * Time administration::
862 * Controlling formatting of prefatory matter::
866 @subsection Staff symbol
868 @cindex adjusting staff symbol
870 Notes, dynamic signs, etc., are grouped
871 with a set of horizontal lines, into a staff (plural `staves'). In our
872 system, these lines are drawn using a separate layout object called
876 @cindex staff lines, setting number of
877 @cindex staff lines, setting thickness of
878 @cindex thickness of staff lines, setting
879 @cindex number of staff lines, setting
883 Program reference: @internalsref{StaffSymbol}.
885 Examples: @inputfileref{input/@/test,staff@/-lines@/.ly},
886 @inputfileref{input/@/test,staff@/-size@/.ly}.
890 If a staff is ended halfway a piece, the staff symbol may not end
891 exactly on the bar line.
895 @subsection Key signature
896 @cindex Key signature
900 The key signature indicates the tonality in which a piece is played. It
901 is denoted by a set of alterations (flats or sharps) at the start of the
905 Setting or changing the key signature is done with the @code{\key}
908 @code{\key} @var{pitch} @var{type}
911 @cindex @code{\minor}
912 @cindex @code{\major}
913 @cindex @code{\minor}
914 @cindex @code{\ionian}
915 @cindex @code{\locrian}
916 @cindex @code{\aeolian}
917 @cindex @code{\mixolydian}
918 @cindex @code{\lydian}
919 @cindex @code{\phrygian}
920 @cindex @code{\dorian}
922 Here, @var{type} should be @code{\major} or @code{\minor} to get
923 @var{pitch}-major or @var{pitch}-minor, respectively.
924 The standard mode names @code{\ionian},
925 @code{\locrian}, @code{\aeolian}, @code{\mixolydian}, @code{\lydian},
926 @code{\phrygian}, and @code{\dorian} are also defined.
928 This command sets the context property
929 @internalsref{Staff}.@code{keySignature}. Non-standard key signatures
930 can be specified by setting this property directly.
932 A natural sign is printed to cancel any previous accidentals. This
933 can be suppressed by setting the @code{Staff.printKeyCancellation}
936 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
942 \set Staff.printKeyCancellation = ##f
950 Accidentals and key signatures often confuse new users, because
951 unaltered notes get natural signs depending on the key signature. For
952 more information, see @ref{More about pitches}.
956 Program reference: @internalsref{KeyChangeEvent},
957 @internalsref{KeyCancellation} and @internalsref{KeySignature}.
959 @cindex @code{keySignature}
966 The clef indicates which lines of the staff correspond to which
970 The clef can be set with the @code{\clef} command
971 @lilypond[quote,raggedright,fragment,verbatim]
972 { c''2 \clef alto g'2 }
975 Supported clef-names include
976 @c Moved standard clefs to the top /MB
980 @item treble, violin, G, G2
993 G clef on 1st line, so-called French violin clef
998 @cindex mezzosoprano clef
1001 @cindex baritone clef
1004 @cindex varbaritone clef
1007 @cindex subbass clef
1015 By adding @code{_8} or @code{^8} to the clef name, the clef is
1016 transposed one octave down or up, respectively, and @code{_15} and
1017 @code{^15} transposes by two octaves. The argument @var{clefname}
1018 must be enclosed in quotes when it contains underscores or digits. For
1022 @cindex choral tenor clef
1023 @lilypond[quote,raggedright,verbatim,fragment,relative=1]
1027 This command is equivalent to setting @code{clefGlyph},
1028 @code{clefPosition} (which controls the Y position of the clef),
1029 @code{middleCPosition} and @code{clefOctavation}. A clef is printed
1030 when any of these properties are changed. The following example shows
1031 possibilities when setting properties manually.
1034 should to be fixed very quickly -gp
1036 @lilypond[quote,raggedright,verbatim]
1038 \set Staff.clefGlyph = #"clefs.F"
1039 \set Staff.clefPosition = #2
1041 \set Staff.clefGlyph = #"clefs.G"
1043 \set Staff.clefGlyph = #"clefs.C"
1045 \set Staff.clefOctavation = #7
1047 \set Staff.clefOctavation = #0
1048 \set Staff.clefPosition = #0
1052 \set Staff.middleCPosition = #4
1061 Program reference: @internalsref{Clef}.
1065 @node Ottava brackets
1066 @subsection Ottava brackets
1068 `Ottava' brackets introduce an extra transposition of an octave for
1069 the staff. They are created by invoking the function
1070 @code{set-octavation}
1076 @lilypond[quote,raggedright,verbatim,fragment]
1086 The @code{set-octavation} function also takes -1 (for 8va bassa) and 2
1087 (for 15ma) as arguments. Internally the function sets the properties
1088 @code{ottavation} (e.g., to @code{"8va"}) and
1089 @code{centralCPosition}. For overriding the text of the bracket, set
1090 @code{ottavation} after invoking @code{set-octavation}, i.e.,
1092 @lilypond[quote,raggedright,verbatim]
1095 \set Staff.ottavation = #"8"
1102 Program reference: @internalsref{OttavaBracket}.
1104 Examples: @inputfileref{input/@/regression,ottava@/.ly},
1105 @inputfileref{input/@/regression,ottava@/-broken@/.ly}.
1109 @code{set-octavation} will get confused when clef changes happen
1110 during an octavation bracket.
1115 @node Time signature
1116 @subsection Time signature
1117 @cindex Time signature
1119 @cindex @code{\time}
1121 Time signature indicates the metrum of a piece: a regular pattern of
1122 strong and weak beats. It is denoted by a fraction at the start of the
1126 The time signature is set or changed by the @code{\time}
1128 @lilypond[quote,raggedright,fragment,verbatim]
1129 \time 2/4 c'2 \time 3/4 c'2.
1132 The symbol that is printed can be customized with the @code{style}
1133 property. Setting it to @code{#'()} uses fraction style for 4/4 and
1136 @lilypond[fragment,quote,raggedright,verbatim]
1139 \override Staff.TimeSignature #'style = #'()
1146 There are many more options for its layout. See @ref{Ancient time
1147 signatures} for more examples.
1150 This command sets the property @code{timeSignatureFraction},
1151 @code{beatLength} and @code{measureLength} in the @code{Timing}
1152 context, which is normally aliased to @internalsref{Score}. The
1153 property @code{measureLength} determines where bar lines should be
1154 inserted, and how automatic beams should be generated. Changing the
1155 value of @code{timeSignatureFraction} also causes the symbol to be
1158 More options are available through the Scheme function
1159 @code{set-time-signature}. In combination with the
1160 @internalsref{Measure_grouping_engraver}, it will create
1161 @internalsref{MeasureGrouping} signs. Such signs ease reading
1162 rhythmically complex modern music. In the following example, the 9/8
1163 measure is subdivided in 2, 2, 2 and 3. This is passed to
1164 @code{set-time-signature} as the third argument @code{(2 2 2 3)}
1166 @lilypond[quote,raggedright,verbatim]
1169 #(set-time-signature 9 8 '(2 2 2 3))
1170 g8[ g] d[ d] g[ g] a8[( bes g]) |
1171 #(set-time-signature 5 8 '(3 2))
1177 \consists "Measure_grouping_engraver"
1185 Program reference: @internalsref{TimeSignature}, and @internalsref{Timing_engraver}.
1190 Automatic beaming does not use the measure grouping specified with
1191 @code{set-time-signature}.
1193 @node Partial measures
1194 @subsection Partial measures
1197 @cindex partial measure
1198 @cindex measure, partial
1199 @cindex shorten measures
1200 @cindex @code{\partial}
1202 Partial measures, for example in upsteps, are entered using the
1203 @code{\partial} command
1204 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
1205 \partial 16*5 c16 cis d dis e | a2. c,4 | b2
1208 The syntax for this command is
1210 \partial @var{duration}
1212 This is internally translated into
1214 \set Timing.measurePosition = -@var{length of duration}
1217 The property @code{measurePosition} contains a rational number
1218 indicating how much of the measure has passed at this point.
1222 This command does not take into account grace notes at the start of
1223 the music. When a piece starts with graces notes in the pickup, then
1224 the @code{\partial} should follow the grace notes
1226 @lilypond[verbatim,quote,raggedright,relative,fragment]
1236 @node Unmetered music
1237 @subsection Unmetered music
1241 Bar lines and bar numbers are calculated automatically. For unmetered
1242 music (cadenzas, for example), this is not desirable. By setting
1243 @code{Score.timing} to false, this automatic timing can be switched
1244 off. Empty bar lines,
1251 indicate where line breaks can occur.
1255 @cindex @code{\cadenzaOn}
1257 @cindex @code{\cadenzaOff}
1264 @subsection Bar lines
1268 @cindex measure lines
1272 Bar lines delimit measures, but are also used to indicate repeats.
1273 Normally, they are inserted automatically. Line breaks may only
1274 happen on bar lines.
1276 Special types of bar lines can be forced with the @code{\bar} command
1278 @lilypond[quote,raggedright,relative=2,fragment,verbatim]
1282 The following bar types are available
1283 @lilypondfile[raggedright,quote]{bar-lines.ly}
1285 For allowing line breaks, there is a special command,
1289 This will insert an invisible bar line, and allow line breaks at this
1292 In scores with many staves, a @code{\bar} command in one staff is
1293 automatically applied to all staves. The resulting bar lines are
1294 connected between different staves of a @internalsref{StaffGroup}
1296 @lilypond[quote,raggedright,fragment,verbatim]
1298 \context StaffGroup <<
1304 \new Staff { \clef bass c4 g e g }
1306 \new Staff { \clef bass c2 c2 }
1311 The command @code{\bar }@var{bartype} is a short cut for doing
1312 @code{\set Timing.whichBar = }@var{bartype}. Whenever @code{whichBar}
1313 is set to a string, a bar line of that type is created.
1315 A bar line is created whenever the @code{whichBar} property is set.
1316 At the start of a measure it is set to the contents of
1317 @code{Timing.defaultBarType}. The contents of @code{repeatCommands} are used
1318 to override default measure bars.
1320 @cindex @code{whichBar}
1321 @cindex @code{repeatCommands}
1322 @cindex @code{defaultBarType}
1324 You are encouraged to use @code{\repeat} for repetitions. See
1331 In this manual: @ref{Repeats}, @ref{System start delimiters}.
1334 Program reference: @internalsref{BarLine} (created at
1335 @internalsref{Staff} level), @internalsref{SpanBar} (across staves).
1337 @cindex bar lines at start of system
1338 @cindex start of system
1342 Examples: @inputfileref{input/@/test,bar@/-lines@/.ly},
1345 @node Time administration
1346 @subsection Time administration
1348 Time is administered by the @internalsref{Time_signature_engraver},
1349 which usually lives in the @internalsref{Score} context.
1350 The bookkeeping deals with the following variables
1353 @item currentBarNumber
1357 The length of the measures in the current time signature. For a 4/4
1358 time this is@tie{}1, and for 6/8 it is 3/4.
1360 @item measurePosition
1361 The point within the measure where we currently are. This quantity
1362 is reset to@tie{}0 whenever it exceeds @code{measureLength}. When that
1363 happens, @code{currentBarNumber} is incremented.
1366 If set to true, the above variables are updated for every time
1367 step. When set to false, the engraver stays in the current measure
1371 Timing can be changed by setting any of these variables explicitly.
1372 In the next example, the 4/4 time signature is printed, but
1373 @code{measureLength} is set to 5/4. After a while, the measure is
1374 shortened by 1/8, by setting @code{measurePosition} to 7/8 at 2/4
1375 in the measure, so the next bar line will fall at 2/4 + 3/8. The
1376 3/8 arises because 5/4 normally has 10/8, but we have manually
1377 set the measure position to be 7/8 and 10/8 - 7/8 = 3/8.
1379 @lilypond[quote,raggedright,verbatim,relative,fragment]
1380 \set Score.measureLength = #(ly:make-moment 5 4)
1384 \set Score.measurePosition = #(ly:make-moment 7 8)
1390 @node Controlling formatting of prefatory matter
1391 @subsection Controlling formatting of prefatory matter
1393 @c This section will be moved to somewhere else soon. -gp
1394 This example demonstrates how to place prefatory matter
1395 (such as the clef and key signature) at the end of a line.
1397 @lilypond[quote,verbatim]
1399 \override Staff.Clef
1400 #'break-visibility = #end-of-line-visible
1401 \override Staff.KeySignature
1402 #'break-visibility = #end-of-line-visible
1403 \set Staff.explicitClefVisibility = #end-of-line-visible
1404 \set Staff.explicitKeySignatureVisibility = #end-of-line-visible
1406 % We want the time sig to take space, otherwise there is not
1407 % enough white at the start of the line.
1409 \override Staff.TimeSignature #'transparent = ##t
1410 \set Score.defaultBarType = #"empty"
1430 Polyphony in music refers to having more than one voice occuring in
1431 a piece of music. Polyphony in LilyPond refers to having more than
1432 one voice on the same staff.
1435 * Writing polyphonic music::
1438 @node Writing polyphonic music
1439 @subsection Writing polyphonic music
1442 The easiest way to enter fragments with more than one voice on a staff
1443 is to split chords using the separator @code{\\}. You can use it for
1444 small, short-lived voices or for single chords
1448 @lilypond[quote,raggedright,verbatim,fragment]
1449 \context Staff \relative c'' {
1450 c4 << { f d e } \\ { b c2 } >>
1451 c4 << g' \\ b, \\ f' \\ d >>
1455 The separator causes @internalsref{Voice} contexts@footnote{Polyphonic
1456 voices are sometimes called ``layers'' in other notation packages}
1458 to be instantiated. They bear the names @code{"1"}, @code{"2"}, etc. In
1459 each of these contexts, vertical direction of slurs, stems, etc., is set
1460 appropriately. Specifically,
1463 << \upper \\ \lower >>
1471 \context Voice = "1" @{ \voiceOne \upper @}
1472 \context Voice = "2" @{ \voiceTwo \lower @}
1476 @cindex @code{\voiceOne}
1477 @cindex @code{\voiceFour}
1479 This can also be done by instantiating @internalsref{Voice} contexts
1480 by hand, and using @code{\voiceOne}, up to @code{\voiceFour} to assign
1481 a stem directions and horizontal shift for each part
1484 @lilypond[quote,raggedright,verbatim]
1487 \new Voice { \voiceOne cis2 b }
1488 \new Voice { \voiceThree b4 ais ~ ais4 gis4 }
1489 \new Voice { \voiceTwo fis4~ fis4 f ~ f } >>
1493 The command @code{\oneVoice} will revert back to the normal setting.
1494 @cindex @code{\oneVoice}
1496 Defining voices (either with the separator @code{\\} or with
1497 @code{\voiceXXX}) will set the direction of stems, slurs, ties,
1498 articulations, text annotations, augmentation dots of dotted
1499 notes, and fingerings. @code{\voiceOne} makes these objects
1500 point upwards, while @code{\voiceTwo} makes them point down.
1502 Normally, note heads with a different number of dots are not merged, but
1503 when the object property @code{merge-differently-dotted} is set in
1504 the @internalsref{NoteCollision} object, they are merged
1505 @lilypond[quote,verbatim,fragment,raggedright,relative=2]
1508 \override Staff.NoteCollision
1509 #'merge-differently-dotted = ##t
1511 } \\ { g8.[ f16] g8.[ f16] } >>
1514 Similarly, you can merge half note heads with eighth notes, by setting
1515 @code{merge-differently-headed}
1516 @lilypond[quote,raggedright,fragment,relative=2,verbatim]
1519 \override Staff.NoteCollision
1520 #'merge-differently-headed = ##t
1521 c8 c4. } \\ { c2 c2 } >>
1524 LilyPond also vertically shifts rests that are opposite of a stem,
1527 @lilypond[quote,raggedright,fragment,verbatim]
1528 \context Voice << c''4 \\ r4 >>
1536 @cindex @code{\oneVoice}
1538 @cindex @code{\voiceOne}
1540 @cindex @code{\voiceTwo}
1542 @cindex @code{\voiceThree}
1544 @cindex @code{\voiceFour}
1549 @cindex @code{\shiftOn}
1551 @cindex @code{\shiftOnn}
1553 @cindex @code{\shiftOnnn}
1555 @cindex @code{\shiftOff}
1556 @code{\shiftOff}: these commands specify in what chords of the current
1557 voice should be shifted. The outer voices (normally: voice one and
1558 two) have @code{\shiftOff}, while the inner voices (three and four)
1559 have @code{\shiftOn}. @code{\shiftOnn} and @code{\shiftOnnn} define
1560 further shift levels.
1563 When LilyPond cannot cope, the @code{force-hshift}
1564 property of the @internalsref{NoteColumn} object and pitched rests can
1565 be used to override typesetting decisions.
1567 @lilypond[quote,verbatim,raggedright]
1574 \once \override NoteColumn #'force-hshift = #1.7
1583 Program reference: the objects responsible for resolving collisions are
1584 @internalsref{NoteCollision} and @internalsref{RestCollision}.
1587 @inputfileref{input/@/regression,collision@/-dots@/.ly},
1588 @inputfileref{input/@/regression,collision@/-head-chords@/.ly},
1589 @inputfileref{input/@/regression,collision@/-heads@/.ly},
1590 @inputfileref{input/@/regression,collision@/-mesh@/.ly}, and
1591 @inputfileref{input/@/regression,collisions@/.ly}.
1597 When using @code{merge-differently-headed} with an upstem eighth or a
1598 shorter note, and a downstem half note, the eighth note gets the wrong
1601 There is no support for clusters where the same note occurs with
1602 different accidentals in the same chord. In this case, it is
1603 recommended to use enharmonic transcription, or to use special cluster
1604 notation (see @ref{Clusters}).
1609 Beams are used to group short notes into chunks that are aligned with
1610 the metrum. LilyPond normally inserts beams automatically, but if you
1611 wish you may control them manually or changed how beams are automatically
1614 @cindex Automatic beams
1618 * Setting automatic beam behavior::
1622 @node Automatic beams
1623 @subsection Automatic beams
1625 LilyPond inserts beams automatically
1627 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
1628 \time 2/4 c8 c c c \time 6/8 c c c c8. c16 c8
1631 When these automatic decisions are not good enough, beaming can be
1632 entered explicitly. It is also possible to define beaming patterns
1633 that differ from the defaults.
1635 Individual notes may be marked with @code{\noBeam}, to prevent them
1638 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
1639 \time 2/4 c8 c\noBeam c c
1645 Program reference: @internalsref{Beam}.
1649 @subsection Manual beams
1650 @cindex beams, manual
1654 In some cases it may be necessary to override the automatic beaming
1655 algorithm. For example, the autobeamer will not put beams over rests
1656 or bar lines. Such beams are specified manually by marking the begin
1657 and end point with @code{[} and @code{]}
1659 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
1661 r4 r8[ g' a r8] r8 g[ | a] r8
1665 @cindex @code{stemLeftBeamCount}
1667 Normally, beaming patterns within a beam are determined automatically.
1668 If necessary, the properties @code{stemLeftBeamCount} and
1669 @code{stemRightBeamCount} can be used to override the defaults. If
1670 either property is set, its value will be used only once, and then it
1673 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
1678 \set stemLeftBeamCount = #1
1682 @cindex @code{stemRightBeamCount}
1685 The property @code{subdivideBeams} can be set in order to subdivide
1686 all 16th or shorter beams at beat positions, as defined by the
1687 @code{beatLength} property.
1690 @lilypond[fragment,quote,relative=2,verbatim]
1692 \set subdivideBeams = ##t
1694 \set Score.beatLength = #(ly:make-moment 1 8)
1697 @cindex @code{subdivideBeams}
1699 Normally, line breaks are forbidden when beams cross bar lines. This
1700 behavior can be changed by setting @code{allowBeamBreak}.
1702 @cindex @code{allowBeamBreak}
1703 @cindex beams and line breaks
1705 @cindex beams, kneed
1707 @cindex auto-knee-gap
1712 User manual: @ref{Changing context properties on the fly} for the
1718 @cindex Frenched staves
1719 Kneed beams are inserted automatically, when a large gap is detected
1720 between the note heads. This behavior can be tuned through the object.
1723 Automatically kneed cross-staff beams cannot be used together with
1724 hidden staves. See @ref{Hiding staves}.
1726 Beams do not avoid collisions with symbols around the notes, such as
1727 texts and accidentals.
1732 @node Setting automatic beam behavior
1733 @subsection Setting automatic beam behavior
1735 @cindex @code{autoBeamSettings}
1736 @cindex @code{(end * * * *)}
1737 @cindex @code{(begin * * * *)}
1738 @cindex automatic beams, tuning
1739 @cindex tuning automatic beaming
1741 @c [TODO: use \applycontext]
1743 In normal time signatures, automatic beams can start on any note but can
1744 only end in a few positions within the measure: beams can end on a beat,
1745 or at durations specified by the properties in
1746 @code{autoBeamSettings}. The defaults for @code{autoBeamSettings}
1747 are defined in @file{scm/@/auto@/-beam@/.scm}.
1749 The value of @code{autoBeamSettings} is changed with three functions,
1751 #(override-auto-beam-setting
1752 '(@var{be} @var{p} @var{q} @var{n} @var{m}) @var{a} @var{b}
1754 #(score-override-auto-beam-setting
1755 '(@var{be} @var{p} @var{q} @var{n} @var{m}) @var{a} @var{b})
1756 #(revert-auto-beam-setting '(@var{be} @var{p} @var{q} @var{n} @var{m})
1759 Here, @var{be} is the symbol @code{begin} or @code{end}, and
1760 @var{context} is an optional context (default: @code{'Voice}). It
1761 determines whether the rule applies to begin or end-points. The
1762 quantity @var{p}/@var{q} refers to the length of the beamed notes (and
1763 `@code{* *}' designates notes of any length), @var{n}/@var{M} refers
1764 to a time signature (wildcards `@code{* *}' may be entered to
1765 designate all time signatures), @var{a}/@var{b} is a duration. By
1766 default, this command changes settings for the current voice. It is
1767 also possible to adjust settings at higher contexts, by adding a
1768 @var{context} argument. @code{score-override-auto-beam-setting} is
1769 equal to @code{override-auto-beam-setting} with the argument
1770 @var{context} set to @code{'Score}.
1772 For example, if automatic beams should end on every quarter note, use
1775 #(override-auto-beam-setting '(end * * * *) 1 4 'Staff)
1777 Since the duration of a quarter note is 1/4 of a whole note, it is
1778 entered as @code{(ly:make-moment 1 4)}.
1780 The same syntax can be used to specify beam starting points. In this
1781 example, automatic beams can only end on a dotted quarter note
1783 #(override-auto-beam-setting '(end * * * *) 3 8)
1785 In 4/4 time signature, this means that automatic beams could end only on
1786 3/8 and on the fourth beat of the measure (after 3/4, that is 2 times
1787 3/8, has passed within the measure).
1789 Rules can also be restricted to specific time signatures. A rule that
1790 should only be applied in @var{N}/@var{M} time signature is formed by
1791 replacing the second asterisks by @var{N} and @var{M}. For example, a
1792 rule for 6/8 time exclusively looks like
1794 #(override-auto-beam-setting '(begin * * 6 8) @dots{})
1797 If a rule should be to applied only to certain types of beams, use the
1798 first pair of asterisks. Beams are classified according to the
1799 shortest note they contain. For a beam ending rule that only applies
1800 to beams with 32nd notes (and no shorter notes), use @code{(end 1 32 *
1803 @cindex automatic beam generation
1805 @cindex @code{autoBeaming}
1808 If beams are used to indicate melismata in songs, then automatic
1809 beaming should be switched off. This is done by setting
1810 @code{autoBeaming} to @code{#f}.
1814 @cindex @code{\autoBeamOff}
1815 @code{\autoBeamOff},
1816 @cindex @code{\autoBeamOn}
1822 If a score ends while an automatic beam has not been ended and is
1823 still accepting notes, this last beam will not be typeset at all. The
1824 same holds polyphonic voices, entered with @code{<< @dots{} \\ @dots{}
1825 >>}. If a polyphonic voice ends while an automatic beam is still
1826 accepting notes, it is not typeset.
1828 The rules for ending a beam depend on the shortest note in a beam.
1829 So, while it is possible to have different ending rules for eight
1830 beams and sixteenth beams, a beam that contains both eight and
1831 sixteenth notes will use the rules for the sixteenth beam.
1833 In the example below, the autobeamer makes eighth beams and sixteenth
1834 end at three eighths. The third beam can only be corrected by
1835 specifying manual beaming.
1837 @lilypond[quote,raggedright,fragment,relative=1]
1838 #(override-auto-beam-setting '(end * * * *) 3 8)
1839 % rather show case where it goes wrong
1840 %\time 12/8 c'8 c c c16 c c c c c c[ c c c] c8[ c] c4
1841 \time 12/8 c'8 c c c16 c c c c c c c c c c8 c c4
1843 It is not possible to specify beaming parameters that act differently in
1844 different parts of a measure. This means that it is not possible to use
1845 automatic beaming in irregular meters such as @code{5/8}.
1847 @node Beam formatting
1848 @subsection Beam formatting
1851 When a beam falls in the middle of the staff, the beams point normally
1852 down. However, this behaviour can be altered with the
1853 @code{neutral-direction} property.
1856 @lilypond[quote,raggedright,relative=2,fragment,verbatim]
1859 \override Beam #'neutral-direction = #-1
1861 \override Beam #'neutral-direction = #1
1868 @section Accidentals
1870 This section describes how to change the way that accidentals are
1871 inserted automatically before notes.
1874 * Automatic accidentals::
1877 @node Automatic accidentals
1878 @subsection Automatic accidentals
1879 @cindex Automatic accidentals
1881 Common rules for typesetting accidentals have been placed in a
1882 function. This function is called as follows
1884 @cindex @code{set-accidental-style}
1886 #(set-accidental-style 'STYLE #('CONTEXT#))
1889 The function can take two arguments: the name of the accidental style,
1890 and an optional argument that denotes the context that should be
1891 changed. If no context name is supplied, @code{Staff} is the default,
1892 but you may wish to apply the accidental style to a single @code{Voice}
1895 The following accidental styles are supported
1898 This is the default typesetting behavior. It corresponds
1899 to 18th century common practice: Accidentals are
1900 remembered to the end of the measure in which they occur and
1901 only on their own octave.
1904 The normal behavior is to remember the accidentals on
1905 Staff-level. This variable, however, typesets accidentals
1906 individually for each voice. Apart from that, the rule is similar to
1909 As a result, accidentals from one voice do not get canceled in other
1910 voices, which is often an unwanted result
1912 @lilypond[quote,raggedright,relative=1,fragment,verbatim]
1914 #(set-accidental-style 'voice)
1921 The @code{voice} option should be used if the voices
1922 are to be read solely by individual musicians. If the staff is to be
1923 used by one musician (e.g., a conductor) then
1924 @code{modern} or @code{modern-cautionary}
1925 should be used instead.
1928 @cindex @code{modern} style accidentals
1929 This rule corresponds to the common practice in the 20th century. This rule
1930 prints the same accidentals as @code{default}, but temporary
1931 accidentals also are canceled in other octaves. Furthermore,
1932 in the same octave, they also get canceled in the following
1935 @lilypond[quote,raggedright,fragment,verbatim]
1936 #(set-accidental-style 'modern)
1937 cis' c'' cis'2 | c'' c'
1940 @item @code{modern-cautionary}
1941 @cindex @code{modern-cautionary}
1942 This rule is similar to @code{modern}, but the ``extra'' accidentals
1943 (the ones not typeset by @code{default}) are typeset as cautionary
1944 accidentals. They are printed in reduced size or with parentheses
1945 @lilypond[quote,raggedright,fragment,verbatim]
1946 #(set-accidental-style 'modern-cautionary)
1947 cis' c'' cis'2 | c'' c'
1950 @cindex @code{modern-voice}
1952 This rule is used for multivoice accidentals to be read both by musicians
1953 playing one voice and musicians playing all voices. Accidentals are
1954 typeset for each voice, but they @emph{are} canceled across voices in
1955 the same @internalsref{Staff}.
1957 @cindex @code{modern-voice-cautionary}
1958 @item modern-voice-cautionary
1959 This rule is the same as @code{modern-voice}, but with the extra
1960 accidentals (the ones not typeset by @code{voice}) typeset
1961 as cautionaries. Even though all accidentals typeset by
1962 @code{default} @emph{are} typeset by this variable,
1963 some of them are typeset as cautionaries.
1966 @cindex @code{piano} accidentals
1967 This rule reflects 20th century practice for piano notation. Very similar to
1968 @code{modern} but accidentals also get canceled
1969 across the staves in the same @internalsref{GrandStaff} or
1970 @internalsref{PianoStaff}.
1972 @item piano-cautionary
1973 @cindex @code{#(set-accidental-style 'piano-cautionary)}
1974 Same as @code{#(set-accidental-style 'piano)} but with the extra
1975 accidentals typeset as cautionaries.
1978 @cindex @code{no-reset} accidental style
1979 This is the same as @code{default} but with accidentals lasting
1980 ``forever'' and not only until the next measure
1981 @lilypond[quote,raggedright,fragment,verbatim,relative=1]
1982 #(set-accidental-style 'no-reset)
1987 This is sort of the opposite of @code{no-reset}: Accidentals
1988 are not remembered at all---and hence all accidentals are
1989 typeset relative to the key signature, regardless of what was
1992 @lilypond[quote,raggedright,fragment,verbatim,relative=1]
1993 #(set-accidental-style 'forget)
1994 \key d\major c4 c cis cis d d dis dis
2001 Program reference: @internalsref{Accidental_engraver},
2002 @internalsref{Accidental}, and @internalsref{AccidentalPlacement}.
2007 Simultaneous notes are considered to be entered in sequential
2008 mode. This means that in a chord the accidentals are typeset as if the
2009 notes in the chord happened once at a time - in the order in which
2010 they appear in the input file.
2012 This is a problem when accidentals in a chord depend on each other,
2013 which does not happen for the default accidental style. The problem
2014 can be solved by manually inserting @code{!} and @code{?} for the
2018 @node Expressive marks
2019 @section Expressive marks
2022 @c todo: should change ordering
2023 @c where to put text spanners, metronome marks,
2026 Expressive marks help musicians to bring more to the music than simple
2036 * Analysis brackets::
2039 * Fingering instructions::
2049 A slur indicates that notes are to be played bound or @emph{legato}.
2051 They are entered using parentheses
2052 @lilypond[quote,raggedright,relative=2,fragment,verbatim]
2053 f( g a) a8 b( a4 g2 f4)
2057 The direction of a slur can be set with the
2061 \override Slur #'direction = #UP
2062 \slurUp % shortcut for the previous line
2066 However, there is a convenient shorthand for forcing slur
2067 directions. By adding @code{_} or @code{^} before the opening
2068 parentheses, the direction is also set. For example,
2070 @lilypond[relative=2,raggedright,quote,verbatim,fragment]
2074 Some composers write two slurs when they want legato chords. This can
2075 be achieved in LilyPond by setting @code{doubleSlurs},
2077 @lilypond[verbatim,raggedright,relative,fragment,quote]
2078 \set doubleSlurs = ##t
2079 <c e>4 ( <d f> <c e> <d f> )
2086 @cindex @code{\slurUp}
2088 @cindex @code{\slurDown}
2090 @cindex @code{\slurNeutral}
2091 @code{\slurNeutral},
2092 @cindex @code{\slurDotted}
2094 @cindex @code{\slurSolid}
2099 Program reference: @seeinternals{Slur}, and @internalsref{SlurEvent}.
2102 @node Phrasing slurs
2103 @subsection Phrasing slurs
2105 @cindex phrasing slurs
2106 @cindex phrasing marks
2108 A phrasing slur (or phrasing mark) connects chords and is used to
2109 indicate a musical sentence. It is written using @code{\(} and @code{\)}
2112 @lilypond[quote,raggedright,fragment,verbatim,relative=1]
2113 \time 6/4 c'\( d( e) f( e) d\)
2116 Typographically, the phrasing slur behaves almost exactly like a
2117 normal slur. However, they are treated as different objects. A
2118 @code{\slurUp} will have no effect on a phrasing slur; instead, use
2119 @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
2120 @code{\phrasingSlurNeutral}.
2122 The commands @code{\slurUp}, @code{\slurDown}, and @code{\slurNeutral}
2123 will only affect normal slurs and not phrasing slurs.
2127 @cindex @code{\phrasingSlurUp}
2128 @code{\phrasingSlurUp},
2129 @cindex @code{\phrasingSlurDown}
2130 @code{\phrasingSlurDown},
2131 @cindex @code{\phrasingSlurNeutral}
2132 @code{\phrasingSlurNeutral}.
2136 Program reference: see also @internalsref{PhrasingSlur}, and
2137 @internalsref{PhrasingSlurEvent}.
2141 Putting phrasing slurs over rests leads to spurious warnings.
2144 @subsection Breath marks
2146 Breath marks are entered using @code{\breathe}
2149 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
2153 The glyph of the breath mark can be tuned by overriding the
2154 @code{text} property of the @code{BreathingSign} layout object with
2155 any markup text. For example,
2156 @lilypond[quote,raggedright,fragment,verbatim,relative=1]
2158 \override BreathingSign #'text
2159 = #(make-musicglyph-markup "scripts-rvarcomma")
2166 Program reference: @internalsref{BreathingSign},
2167 @internalsref{BreathingSignEvent}.
2169 Examples: @inputfileref{input/@/regression,breathing@/-sign@/.ly}.
2172 @node Metronome marks
2173 @subsection Metronome marks
2176 @cindex beats per minute
2177 @cindex metronome marking
2179 Metronome settings can be entered as follows
2181 \tempo @var{duration} = @var{per-minute}
2184 In the MIDI output, they are interpreted as a tempo change. In the
2185 layout output, a metronome marking is printed
2186 @cindex @code{\tempo}
2187 @lilypond[quote,raggedright,verbatim,fragment]
2193 Program reference: @internalsref{MetronomeChangeEvent}.
2197 @subsection Text scripts
2198 @cindex Text scripts
2200 @cindex text items, non-empty
2201 @cindex non-empty texts
2203 It is possible to place arbitrary strings of text or markup text (see
2204 @ref{Text markup}) above or below notes by using a string
2205 @code{c^"text"}. By default, these indications do not influence the
2206 note spacing, but by using the command @code{\fatText}, the widths
2207 will be taken into account
2209 @lilypond[quote,fragment,raggedright,verbatim,relative=1]
2210 c4^"longtext" \fatText c4_"longlongtext" c4
2213 More complex formatting may also be added to a note by using the
2215 @lilypond[fragment,raggedright,verbatim,quote]
2216 c'4^\markup { bla \bold bla }
2219 The @code{\markup} is described in more detail in
2225 @cindex @code{\fatText}
2227 @cindex @code{\emptyText}
2232 In this manual: @ref{Text markup}.
2234 Program reference: @internalsref{TextScriptEvent}, @internalsref{TextScript}.
2238 @subsection Text spanners
2239 @cindex Text spanners
2241 Some performance indications, e.g., @i{rallentando} or @i{accelerando},
2242 are written as text and are extended over many measures with dotted
2243 lines. Such texts are created using text spanners; attach
2244 @code{\startTextSpan} and @code{\stopTextSpan} to the first and last
2245 notes of the spanner.
2247 The string to be printed, as well as the style, is set through object
2250 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
2252 \override TextSpanner #'direction = #-1
2253 \override TextSpanner #'edge-text = #'("rall " . "")
2254 c2\startTextSpan b c\stopTextSpan a
2260 Internals @internalsref{TextSpanEvent},
2261 @internalsref{TextSpanner}.
2263 Examples: @inputfileref{input/@/regression,text@/-spanner@/.ly}.
2266 @node Analysis brackets
2267 @subsection Analysis brackets
2269 @cindex phrasing brackets
2270 @cindex musicological analysis
2271 @cindex note grouping bracket
2273 Brackets are used in musical analysis to indicate structure in musical
2274 pieces. LilyPond supports a simple form of nested horizontal
2275 brackets. To use this, add the @internalsref{Horizontal_bracket_engraver}
2276 to @internalsref{Staff} context. A bracket is started with
2277 @code{\startGroup} and closed with @code{\stopGroup}
2279 @lilypond[quote,raggedright,verbatim]
2282 c4\startGroup\startGroup
2285 c4\stopGroup\stopGroup
2289 \Staff \consists "Horizontal_bracket_engraver"
2295 Program reference: @internalsref{HorizontalBracket},
2296 @internalsref{NoteGroupingEvent}.
2298 Examples: @inputfileref{input/@/regression,note@/-group@/-bracket@/.ly}.
2302 @subsection Articulations
2303 @cindex Articulations
2305 @cindex articulations
2309 A variety of symbols can appear above and below notes to indicate
2310 different characteristics of the performance. They are added to a note
2311 by adding a dash and the character signifying the
2312 articulation. They are demonstrated here
2314 @lilypondfile[quote,raggedright]{script-abbreviations.ly}
2316 The meanings of these shorthands can be changed. See
2317 @file{ly/@/script@/-init@/.ly} for examples.
2320 The script is automatically placed, but the direction can be forced as
2321 well. Like other pieces of LilyPond code, @code{_} will place them
2322 below the staff, and @code{^} will place them above.
2325 @lilypond[quote,raggedright,fragment,verbatim]
2329 Other symbols can be added using the syntax
2330 @var{note}@code{\}@var{name}. Again, they
2331 can be forced up or down using @code{^} and @code{_},
2334 @lilypond[quote,raggedright,verbatim,fragment,relative=2]
2335 c\fermata c^\fermata c_\fermata
2342 @cindex staccatissimo
2352 @cindex organ pedal marks
2361 @cindex prallmordent
2365 @cindex thumb marking
2370 Here is a chart showing all scripts available,
2372 @lilypondfile[raggedright,quote]{script-chart.ly}
2375 The vertical ordering of scripts is controlled with the
2376 @code{script-priority} property. The lower this number, the closer it
2377 will be put to the note. In this example, the
2378 @internalsref{TextScript} (the sharp symbol) first has the lowest
2379 priority, so it is put lowest in the first example. In the second, the
2380 prall trill (the @internalsref{Script}) has the lowest, so it is on the
2381 inside. When two objects have the same priority, the order in which
2382 they are entered decides which one comes first.
2385 @lilypond[verbatim,relative=3,raggedright,fragment,quote]
2386 \once \override TextScript #'script-priority = #-100
2387 a4^\prall^\markup { \sharp }
2389 \once \override Script #'script-priority = #-100
2390 a4^\prall^\markup { \sharp }
2398 Program reference: @internalsref{ScriptEvent}, and @internalsref{Script}.
2402 These signs appear in the printed output but have no effect on the
2403 MIDI rendering of the music.
2407 @node Running trills
2408 @subsection Running trills
2410 Long running trills are made with @code{\startTrillSpan} and
2411 @code{\stopTrillSpan},
2414 @lilypond[verbatim,raggedright,relative=2,quote,fragment]
2416 << { c1 \startTrillSpan }
2417 { s2. \grace { d16[\stopTrillSpan e] } } >>
2423 @code{\startTrillSpan},
2424 @cindex @code{\startTrillSpan}
2425 @code{\stopTrillSpan}.
2426 @cindex @code{\stopTrillSpan}
2430 Program reference: @internalsref{TrillSpanner},
2431 @internalsref{TrillSpanEvent}.
2433 @node Fingering instructions
2434 @subsection Fingering instructions
2438 Fingering instructions can be entered using
2440 @var{note}-@var{digit}
2442 For finger changes, use markup texts
2444 @lilypond[quote,verbatim,raggedright,fragment,relative=1]
2446 c^\markup { \finger "2-3" }
2449 @cindex finger change
2454 You can use the thumb-script to indicate that a note should be
2455 played with the thumb (e.g., in cello music)
2456 @lilypond[quote,verbatim,raggedright,fragment,relative=2]
2457 <a_\thumb a'-3>8 <b_\thumb b'-3>
2460 Fingerings for chords can also be added to individual notes
2461 of the chord by adding them after the pitches
2462 @lilypond[quote,verbatim,raggedright,fragment,relative=2]
2463 < c-1 e-2 g-3 b-5 >4
2467 In this case, setting @code{fingeringOrientations} will put fingerings next
2470 @lilypond[quote,verbatim,raggedright,fragment,relative=1]
2471 \set fingeringOrientations = #'(left down)
2472 <c-1 es-2 g-4 bes-5 > 4
2473 \set fingeringOrientations = #'(up right down)
2474 <c-1 es-2 g-4 bes-5 > 4
2477 Using this feature, it is also possible to put fingering instructions
2478 very close to note heads in monophonic music,
2480 @lilypond[verbatim,raggedright,quote,fragment]
2481 \set fingeringOrientations = #'(right)
2488 Program reference: @internalsref{FingerEvent}, and @internalsref{Fingering}.
2490 Examples: @inputfileref{input/@/regression,finger@/-chords@/.ly}.
2496 @subsection Grace notes
2499 @c should have blurb about accaciatura / appogiatura
2501 @cindex @code{\grace}
2505 Grace notes are ornaments that are written out. The most common ones
2506 are acciaccatura, which should be played as very short. It is denoted
2507 by a slurred small note with a slashed stem. The appoggiatura is a
2508 grace note that takes a fixed fraction of the main note, and is
2509 denoted as a slurred note in small print without a slash. They
2510 are entered with the commands @code{\acciaccatura} and
2511 @code{\appoggiatura}, as demonstrated in the following example
2514 @cindex appoggiatura
2515 @cindex acciaccatura
2517 @lilypond[quote,raggedright,relative=2,verbatim,fragment]
2518 b4 \acciaccatura d8 c4 \appoggiatura e8 d4
2519 \acciaccatura { g16[ f] } e4
2522 Both are special forms of the @code{\grace} command. By prefixing this
2523 keyword to a music expression, a new one is formed, which will be
2524 printed in a smaller font and takes up no logical time in a measure.
2526 @lilypond[quote,raggedright,relative=2,verbatim,fragment]
2528 \grace { c16[ d16] } c2 c4
2532 Unlike @code{\acciaccatura} and @code{\appoggiatura}, the
2533 @code{\grace} command does not start a slur.
2535 Internally, timing for grace notes is done using a second, `grace'
2536 timing. Every point in time consists of two rational numbers: one
2537 denotes the logical time, one denotes the grace timing. The above
2538 example is shown here with timing tuples
2540 @lilypond[quote,raggedright]
2543 c4 \grace c16 c4 \grace {
2546 \new Lyrics \lyricmode {
2547 \override LyricText #'font-family = #'typewriter
2551 ( \fraction 1 4 , \fraction -1 16 ) } 16 }
2552 \markup { (\fraction 1 4 , 0 ) } 4
2554 \markup { (\fraction 2 4 , \fraction "-1" 8 ) } 16
2555 \markup { (\fraction 2 4 , \fraction "-1" 16 ) } 16
2557 \markup { ( \fraction 2 4 , 0 ) }
2563 The placement of grace notes is synchronized between different staves.
2564 In the following example, there are two sixteenth grace notes for
2565 every eighth grace note
2567 @lilypond[quote,raggedright,relative=2,verbatim,fragment]
2568 << \new Staff { e4 \grace { c16[ d e f] } e4 }
2569 \new Staff { c4 \grace { g8[ b] } c4 } >>
2574 If you want to end a note with a grace, use the @code{\afterGrace}
2575 command. It takes two arguments: the main note, and the grace notes
2576 following the main note.
2578 @lilypond[raggedright, verbatim,relative=2,fragment]
2579 c1 \afterGrace d1 { c16[ d] } c4
2582 This will put the grace notes after a ``space'' lasting 3/4 of the
2583 length of the main note. The fraction 3/4 can be changed by setting
2584 @code{afterGraceFraction}, ie.
2587 afterGraceFraction = #(cons 7 8)
2591 will put the grace note at 7/8 of the main note.
2594 The same effect can be achieved manually by doing
2597 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
2600 { s2 \grace { c16[ d] } } >>
2606 By adjusting the duration of the skip note (here it is a half-note),
2607 the space between the main-note and the grace is adjusted.
2612 A @code{\grace} section will introduce special typesetting settings,
2613 for example, to produce smaller type, and set directions. Hence, when
2614 introducing layout tweaks, they should be inside the grace section,
2616 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
2628 The overrides should also be reverted inside the grace section.
2630 The layout of grace sections can be changed throughout the music using
2631 the function @code{add-grace-property}. The following example
2632 undefines the Stem direction for this grace, so stems do not always
2637 #(add-grace-property 'Voice 'Stem 'direction '())
2643 Another option is to change the variables @code{startGraceMusic},
2644 @code{stopGraceMusic}, @code{startAcciaccaturaMusic},
2645 @code{stopAcciaccaturaMusic}, @code{startAppoggiaturaMusic},
2646 @code{stopAppoggiaturaMusic}. More information is in the file
2647 @file{ly/@/grace@/-init@/.ly}.
2652 Program reference: @internalsref{GraceMusic}.
2656 A score that starts with a @code{\grace} section needs an explicit
2657 @code{\context Voice} declaration, otherwise the main note and the grace
2658 note end up on different staves.
2660 Grace note synchronization can also lead to surprises. Staff notation,
2661 such as key signatures, bar lines, etc., are also synchronized. Take
2662 care when you mix staves with grace notes and staves without, for example,
2664 @lilypond[quote,raggedright,relative=2,verbatim,fragment]
2665 << \new Staff { e4 \bar "|:" \grace c16 d4 }
2666 \new Staff { c4 \bar "|:" d4 } >>
2670 This can be remedied by inserting grace skips, for the above example
2673 \new Staff @{ c4 \bar "|:" \grace s16 d4 @}
2676 Grace sections should only be used within sequential music
2677 expressions. Nesting or juxtaposing grace sections is not supported,
2678 and might produce crashes or other errors.
2682 @subsection Glissando
2685 @cindex @code{\glissando}
2687 A glissando is a smooth change in pitch. It is denoted by a line or a
2688 wavy line between two notes. It is requested by attaching
2689 @code{\glissando} to a note
2691 @lilypond[quote,raggedright,fragment,relative=2,verbatim]
2697 Program reference: @internalsref{Glissando}, and @internalsref{GlissandoEvent}.
2699 Example files: @file{input/@/regression/@/glissando@/.ly}.
2705 Printing text over the line (such as @emph{gliss.}) is not supported.
2709 @subsection Dynamics
2722 @cindex @code{\ffff}
2732 Absolute dynamic marks are specified using a command after a note
2733 @code{c4\ff}. The available dynamic marks are @code{\ppp},
2734 @code{\pp}, @code{\p}, @code{\mp}, @code{\mf}, @code{\f}, @code{\ff},
2735 @code{\fff}, @code{\fff}, @code{\fp}, @code{\sf}, @code{\sff},
2736 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}
2738 @lilypond[quote,verbatim,raggedright,fragment,relative=2]
2739 c\ppp c\pp c \p c\mp c\mf c\f c\ff c\fff
2740 c2\fp c\sf c\sff c\sp c\spp c\sfz c\rfz
2749 A crescendo mark is started with @code{\<} and terminated with
2750 @code{\!}. A decrescendo is started with @code{\>} and also terminated
2751 with @code{\!}. Because these marks are bound to notes, you must
2752 use spacer notes if multiple marks are needed during one note
2754 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
2756 << f1 { s4 s4\< s4\! \> s4\! } >>
2758 This may give rise to very short hairpins. Use @code{minimum-length}
2759 in @internalsref{Voice}.@internalsref{Hairpin} to lengthen them, for
2763 \override Staff.Hairpin #'minimum-length = #5
2766 You can also use a text saying @emph{cresc.} instead of hairpins. Here
2767 is an example how to do it
2769 @lilypond[quote,raggedright,fragment,relative=2,verbatim]
2783 You can also supply your own texts
2784 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
2785 \set crescendoText = \markup { \italic "cresc. poco" }
2786 \set crescendoSpanner = #'dashed-line
2792 To create new dynamic marks or text that should be aligned
2793 with dynamics, see @ref{New dynamic marks}.
2798 @cindex @code{\dynamicUp}
2800 @cindex @code{\dynamicDown}
2801 @code{\dynamicDown},
2802 @cindex @code{\dynamicNeutral}
2803 @code{\dynamicNeutral}.
2805 @cindex direction, of dynamics
2809 Program reference: @internalsref{CrescendoEvent},
2810 @internalsref{DecrescendoEvent}, and
2811 @internalsref{AbsoluteDynamicEvent}.
2813 Dynamics are @internalsref{DynamicText} and @internalsref{Hairpin}
2814 objects. Vertical positioning of these symbols is handled by the
2815 @internalsref{DynamicLineSpanner} object.
2821 Repetition is a central concept in music, and multiple notations exist
2827 * Repeats and MIDI::
2828 * Manual repeat commands::
2830 * Tremolo subdivisions::
2835 @subsection Repeat types
2838 @cindex @code{\repeat}
2840 The following types of repetition are supported
2844 Repeated music is fully written (played) out. This is useful when
2845 entering repetitious music. This is the only kind of repeat that
2846 is included in MIDI output.
2849 Repeats are not written out, but alternative endings (volte) are
2850 printed, left to right with brackets. This is the standard notation
2851 for repeats with alternatives. These are not played in MIDI output by default.
2855 Alternative endings are written stacked. This has limited use but may be
2856 used to typeset two lines of lyrics in songs with repeats, see
2857 @inputfileref{input,star-spangled-banner@/.ly}.
2862 Make tremolo beams. These are not played in MIDI output by default.
2865 Make beat or measure repeats. These look like percent signs. These
2866 are not played in MIDI output by default. Percent repeats must be
2867 declared within a Voice context.
2872 @subsection Repeat syntax
2875 LilyPond has one syntactic construct for specifying different types of
2876 repeats. The syntax is
2879 \repeat @var{variant} @var{repeatcount} @var{repeatbody}
2882 If you have alternative endings, you may add
2883 @cindex @code{\alternative}
2885 \alternative @{ @var{alternative1}
2887 @var{alternative3} @dots{} @}
2889 where each @var{alternative} is a music expression. If you do not
2890 give enough alternatives for all of the repeats, the first alternative
2891 is assumed to be played more than once.
2893 Standard repeats are used like this
2894 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
2896 \repeat volta 2 { c4 d e f }
2897 \repeat volta 2 { f e d c }
2900 With alternative endings
2901 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
2903 \repeat volta 2 {c4 d e f}
2904 \alternative { {d2 d} {f f,} }
2908 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
2911 \repeat volta 4 { e | c2 d2 | e2 f2 | }
2912 \alternative { { g4 g g } { a | a a a a | b2. } }
2916 It is possible to shorten volta brackets
2917 by setting @code{voltaSpannerDuration}. In the next example, the
2918 bracket only lasts one measure, which is a duration of 3/4.
2922 @lilypond[verbatim,raggedright,quote]
2926 \set Staff.voltaSpannerDuration = #(ly:make-moment 3 4)
2927 \repeat "volta" 5 { d d d }
2928 \alternative { { e e e f f f }
2938 Brackets for the repeat are normally only printed over the topmost
2939 staff. This can be adjusted by setting the @code{voltaOnThisStaff}
2940 property; see @inputfileref{input/@/regression,volta@/-multi@/-staff@/.ly}.
2943 @c @inputfileref{input/@/regression,volta@/-chord@/-names@/.ly}.
2948 A nested repeat like
2957 is ambiguous, since it is is not clear to which @code{\repeat} the
2958 @code{\alternative} belongs. This ambiguity is resolved by always
2959 having the @code{\alternative} belong to the inner @code{\repeat}.
2960 For clarity, it is advisable to use braces in such situations.
2965 Timing information is not remembered at the start of an alternative,
2966 so after a repeat timing information must be reset by hand, for
2967 example by setting @code{Score.measurePosition} or entering
2968 @code{\partial}. Similarly, slurs or ties are also not repeated.
2973 @node Repeats and MIDI
2974 @subsection Repeats and MIDI
2976 @cindex expanding repeats
2978 With a little bit of tweaking, all types of repeats can be present
2979 in the MIDI output. This is achieved by applying the
2980 @code{\unfoldrepeats} music function. This functions changes all
2981 repeats to unfold repeats.
2983 @lilypond[quote,verbatim,fragment,linewidth=8.0\cm]
2985 \repeat tremolo 8 {c'32 e' }
2986 \repeat percent 2 { c''8 d'' }
2987 \repeat volta 2 {c'4 d' e' f'}
2996 When creating a score file using @code{\unfoldrepeats} for midi, then
2997 it is necessary to make two @code{\score} blocks. One for MIDI (with
2998 unfolded repeats) and one for notation (with volta, tremolo, and
2999 percent repeats). For example,
3007 \unfoldrepeats @var{..music..}
3012 @node Manual repeat commands
3013 @subsection Manual repeat commands
3015 @cindex @code{repeatCommands}
3017 The property @code{repeatCommands} can be used to control the layout of
3018 repeats. Its value is a Scheme list of repeat commands.
3021 @item @code{start-repeat}
3022 Print a @code{|:} bar line.
3024 @item @code{end-repeat}
3025 Print a @code{:|} bar line.
3027 @item @code{(volta @var{text})}
3028 Print a volta bracket saying @var{text}: The text can be specified as
3029 a text string or as a markup text, see @ref{Text markup}. Do not
3030 forget to change the font, as the default number font does not contain
3031 alphabetic characters;
3033 @item @code{(volta #f)}
3034 Stop a running volta bracket.
3037 @lilypond[quote,raggedright,verbatim,fragment,relative=2]
3039 \set Score.repeatCommands = #'((volta "93") end-repeat)
3041 \set Score.repeatCommands = #'((volta #f))
3049 Program reference: @internalsref{VoltaBracket}, @internalsref{RepeatedMusic},
3050 @internalsref{VoltaRepeatedMusic},
3051 @internalsref{UnfoldedRepeatedMusic}, and
3052 @internalsref{FoldedRepeatedMusic}.
3054 @node Tremolo repeats
3055 @subsection Tremolo repeats
3056 @cindex tremolo beams
3058 To place tremolo marks between notes, use @code{\repeat} with tremolo
3060 @lilypond[quote,verbatim,raggedright]
3061 \new Voice \relative c' {
3062 \repeat "tremolo" 8 { c16 d16 }
3063 \repeat "tremolo" 4 { c16 d16 }
3064 \repeat "tremolo" 2 { c16 d16 }
3068 Tremolo marks can also be put on a single note. In this case, the
3069 note should not be surrounded by braces.
3070 @lilypond[quote,verbatim,raggedright]
3071 \repeat "tremolo" 4 c'16
3074 Similar output is obtained using the tremolo subdivision, described in
3075 @ref{Tremolo subdivisions}.
3079 In this manual: @ref{Tremolo subdivisions}, @ref{Repeats}.
3081 Program reference: tremolo beams are @internalsref{Beam} objects. Single stem
3082 tremolos are @internalsref{StemTremolo} objects. The music expression is
3083 @internalsref{TremoloEvent}.
3085 Example files: @inputfileref{input/@/regression,chord@/-tremolo@/.ly},
3086 @inputfileref{input/@/regression,stem@/-tremolo@/.ly}.
3088 @node Tremolo subdivisions
3089 @subsection Tremolo subdivisions
3090 @cindex tremolo marks
3091 @cindex @code{tremoloFlags}
3093 Tremolo marks can be printed on a single note by adding
3094 `@code{:}[@var{number}]' after the note. The number indicates the
3095 duration of the subdivision, and it must be at least 8. A
3096 @var{length} value of 8 gives one line across the note stem. If the
3097 length is omitted, the last value (stored in @code{tremoloFlags}) is
3100 @lilypond[quote,raggedright,verbatim,fragment]
3101 c'2:8 c':32 | c': c': |
3104 @c [TODO: stok is te kort bij 32en]
3105 @c somebody want to translate that into English?
3106 @c `Stem is too short for 32nds' (wl)
3110 Tremolos entered in this way do not carry over into the MIDI output.
3114 In this manual: @ref{Tremolo repeats}.
3116 Elsewhere: @internalsref{StemTremolo}, @internalsref{TremoloEvent}.
3118 @node Measure repeats
3119 @subsection Measure repeats
3121 @cindex percent repeats
3122 @cindex measure repeats
3124 In the @code{percent} style, a note pattern can be repeated. It is
3125 printed once, and then the pattern is replaced with a special sign.
3126 Patterns of one and two measures are replaced by percent-like signs,
3127 patterns that divide the measure length are replaced by slashes.
3128 Percent repeats must be declared within a @code{Voice} context.
3130 @lilypond[quote,verbatim,raggedright]
3131 \new Voice \relative c' {
3132 \repeat "percent" 4 { c4 }
3133 \repeat "percent" 2 { c2 es2 f4 fis4 g4 c4 }
3139 Program reference: @internalsref{RepeatSlash}, @internalsref{PercentRepeat},
3140 @internalsref{PercentRepeatedMusic}, and
3141 @internalsref{DoublePercentRepeat}.
3145 @node Rhythmic music
3146 @section Rhythmic music
3148 Rhythmic music is primarily used for percussion and drum notation, but it can
3149 also be used to show the rhythms of melodies.
3152 * Showing melody rhythms::
3153 * Entering percussion::
3154 * Percussion staves::
3158 @node Showing melody rhythms
3159 @subsection Showing melody rhythms
3161 Sometimes you might want to show only the rhythm of a melody. This
3162 can be done with the rhythmic staff. All pitches of notes on such a
3163 staff are squashed, and the staff itself has a single line
3165 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
3166 \context RhythmicStaff {
3168 c4 e8 f g2 | r4 g r2 | g1:32 | r1 |
3174 Program reference: @internalsref{RhythmicStaff}.
3176 Examples: @inputfileref{input/@/regression,rhythmic@/-staff@/.ly}.
3179 @node Entering percussion
3180 @subsection Entering percussion
3186 Percussion notes may be entered in @code{\drummode} mode, which is
3187 similar to the standard mode for entering notes. Each piece of
3188 percussion has a full name and an abbreviated name, and both can be used
3191 @lilypond[quote,raggedright,verbatim]
3193 hihat hh bassdrum bd
3197 The complete list of drum names is in the init file
3198 @file{ly/@/drumpitch@/-init@/.ly}.
3199 @c TODO: properly document this.
3203 Program reference: @internalsref{DrumNoteEvent}.
3205 @node Percussion staves
3206 @subsection Percussion staves
3210 A percussion part for more than one instrument typically uses a
3211 multiline staff where each position in the staff refers to one piece
3215 To typeset the music, the notes must be interpreted in a
3216 @internalsref{DrumStaff} and @internalsref{DrumVoice} contexts
3218 @lilypond[quote,raggedright,verbatim]
3219 up = \drummode { crashcymbal4 hihat8 halfopenhihat hh hh hh openhihat }
3220 down = \drummode { bassdrum4 snare8 bd r bd sn4 }
3222 \new DrumVoice { \voiceOne \up }
3223 \new DrumVoice { \voiceTwo \down }
3227 The above example shows verbose polyphonic notation. The short
3228 polyphonic notation, described in @ref{Polyphony}, can also be used if
3229 the @internalsref{DrumVoices} are instantiated by hand first. For example,
3231 @lilypond[quote,raggedright,fragment,verbatim]
3233 \context DrumVoice = "1" { s1 *2 }
3234 \context DrumVoice = "2" { s1 *2 }
3238 { \repeat unfold 16 hh16 }
3247 There are also other layout possibilities. To use these, set the
3248 property @code{drumStyleTable} in context @internalsref{DrumVoice}.
3249 The following variables have been predefined
3253 This is the default. It typesets a typical drum kit on a five-line staff
3255 @lilypond[quote,linewidth=10.0\cm]
3257 cymc cyms cymr hh hhc hho hhho hhp
3258 cb hc bd sn ss tomh tommh tomml toml tomfh tomfl }
3260 cymc cyms cymr hh hhc hho hhho hhp \break
3261 cb hc bd sn ss tomh tommh tomml toml tomfh tomfl s16 }
3263 << \new DrumStaff \with {
3264 \remove Bar_engraver
3265 \remove Time_signature_engraver
3266 \override Stem #'transparent = ##t
3267 \override Stem #'Y-extent-callback = ##f
3268 minimumVerticalExtent = #'(-4.0 . 5.0)
3270 \context Lyrics \nam
3275 \override LyricText #'font-family = #'typewriter
3276 \override BarNumber #'transparent =##T
3282 The drum scheme supports six different toms. When there are fewer toms,
3283 simply select the toms that produce the desired result, i.e., to get toms
3284 on the three middle lines you use @code{tommh}, @code{tomml}, and
3287 @item timbales-style
3288 This typesets timbales on a two line staff
3290 @lilypond[quote,raggedright]
3291 nam = \lyricmode { timh ssh timl ssl cb }
3292 mus = \drummode { timh ssh timl ssl cb s16 }
3295 \context DrumStaff \with {
3296 \remove Bar_engraver
3297 \remove Time_signature_engraver
3298 \override Stem #'transparent = ##t
3299 \override Stem #'Y-extent-callback = ##f
3300 \override StaffSymbol #'line-count = #2
3301 \override StaffSymbol #'staff-space = #2
3302 minimumVerticalExtent = #'(-3.0 . 4.0)
3303 drumStyleTable = #timbales-style
3306 \override LyricText #'font-family = #'typewriter
3313 This typesets congas on a two line staff
3315 @lilypond[quote,raggedright]
3316 nam = \lyricmode { cgh cgho cghm ssh cgl cglo cglm ssl }
3317 mus = \drummode { cgh cgho cghm ssh cgl cglo cglm ssl s16 }
3320 \context DrumStaff \with {
3321 \remove Bar_engraver
3322 \remove Time_signature_engraver
3323 drumStyleTable = #congas-style
3324 \override StaffSymbol #'line-count = #2
3326 %% this sucks; it will lengthen stems.
3327 \override StaffSymbol #'staff-space = #2
3328 \override Stem #'transparent = ##t
3329 \override Stem #'Y-extent-callback = ##f
3332 \override LyricText #'font-family = #'typewriter
3339 This typesets bongos on a two line staff
3341 @lilypond[quote,raggedright]
3342 nam = \lyricmode { boh boho bohm ssh bol bolo bolm ssl }
3343 mus = \drummode { boh boho bohm ssh bol bolo bolm ssl s16 }
3346 \context DrumStaff\with {
3347 \remove Bar_engraver
3348 \remove Time_signature_engraver
3349 \override StaffSymbol #'line-count = #2
3350 drumStyleTable = #bongos-style
3352 %% this sucks; it will lengthen stems.
3353 \override StaffSymbol #'staff-space = #2
3354 \override Stem #'transparent = ##t
3355 \override Stem #'Y-extent-callback = ##f
3358 \override LyricText #'font-family = #'typewriter
3364 @item percussion-style
3365 To typeset all kinds of simple percussion on one line staves.
3367 @lilypond[quote,raggedright]
3368 nam = \lyricmode { tri trio trim gui guis guil cb cl tamb cab mar hc }
3369 mus = \drummode { tri trio trim gui guis guil cb cl tamb cab mar hc s16 }
3372 \context DrumStaff\with{
3373 \remove Bar_engraver
3374 drumStyleTable = #percussion-style
3375 \override StaffSymbol #'line-count = #1
3376 \remove Time_signature_engraver
3377 \override Stem #'transparent = ##t
3378 \override Stem #'Y-extent-callback = ##f
3381 \override LyricText #'font-family = #'typewriter
3388 If you do not like any of the predefined lists you can define your own
3389 list at the top of your file
3391 @lilypond[quote,raggedright,verbatim]
3393 (bassdrum default #f -1)
3394 (snare default #f 0)
3396 (pedalhihat xcircle "stopped" 2)
3397 (lowtom diamond #f 3)))
3398 up = \drummode { hh8 hh hh hh hhp4 hhp }
3399 down = \drummode { bd4 sn bd toml8 toml }
3402 \set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)
3403 \new DrumVoice { \voiceOne \up }
3404 \new DrumVoice { \voiceTwo \down }
3411 Init files: @file{ly/@/drumpitch@/-init@/.ly}.
3413 Program reference: @internalsref{DrumStaff}, @internalsref{DrumVoice}.
3417 Because general MIDI does not contain rim shots, the sidestick is used
3418 for this purpose instead.
3421 @section Piano music
3423 Piano staves are two normal staves coupled with a brace. The staves
3424 are largely independent, but sometimes voices can cross between the
3425 two staves. The same notation is also used for harps and other key
3426 @c Is this `harp' or `harpsichord'?
3427 instruments. The @internalsref{PianoStaff} is especially built to
3428 handle this cross-staffing behavior. In this section we discuss the
3429 @internalsref{PianoStaff} and some other pianistic peculiarities.
3433 * Automatic staff changes::
3434 * Manual staff switches::
3437 * Staff switch lines::
3438 * Cross staff stems::
3443 Dynamics are not centered, but workarounds do exist. See the
3444 ``piano centered dynamics'' template in @ref{Piano templates}.
3446 @cindex cross staff stem
3447 @cindex stem, cross staff
3448 @cindex distance between staves in piano music
3450 The distance between the two staves is the same for all systems in the
3451 score. It is possible to override this per system, but it does require
3452 an arcane command incantation. See
3453 @inputfileref{input/@/test,piano@/-staff@/-distance@/.ly}.
3456 @node Automatic staff changes
3457 @subsection Automatic staff changes
3458 @cindex Automatic staff changes
3460 Voices can be made to switch automatically between the top and the bottom
3461 staff. The syntax for this is
3465 \autochange @dots{}@var{music}@dots{}
3470 This will create two staves inside the current PianoStaff, called
3471 @code{up} and @code{down}. The lower staff will be in bass clef by
3474 A @code{\relative} section that is outside of @code{\autochange} has
3475 no effect on the pitches of @var{music}, so, if necessary, put
3476 @code{\relative} inside @code{\autochange} like
3480 \autochange \relative @dots{} @dots{}
3485 The autochanger switches on basis of the pitch (middle C is the turning
3486 point), and it looks ahead skipping over rests to switch in
3487 advance. Here is a practical example
3489 @lilypond[quote,verbatim,raggedright]
3491 \autochange \relative c'
3500 In this manual: @ref{Manual staff switches}.
3502 Program reference: @internalsref{AutoChangeMusic}.
3508 The staff switches may not end up in optimal places. For high
3509 quality output, staff switches should be specified manually.
3512 @code{\autochange} cannot be inside @code{\times}.
3514 Internally, the @code{\partcombine} interprets both arguments as
3515 @code{Voice}s named @code{one} and @code{two}, and then decides when
3516 the parts can be combined. Consequently, if the arguments switch to
3517 differently named @internalsref{Voice} contexts, the events in those
3521 @node Manual staff switches
3522 @subsection Manual staff switches
3524 @cindex manual staff switches
3525 @cindex staff switch, manual
3527 Voices can be switched between staves manually, using the command
3529 \change Staff = @var{staffname} @var{music}
3533 The string @var{staffname} is the name of the staff. It switches the
3534 current voice from its current staff to the Staff called
3535 @var{staffname}. Typically @var{staffname} is @code{"up"} or
3536 @code{"down"}. The @context{Staff} referred to must already exist, so
3537 usually the setup for a score will start with a setup of the staves,
3541 \context Staff = up @{
3542 \skip 1 * 10 % @emph{keep staff alive}
3544 \context Staff = down @{
3545 \skip 1 * 10 % @emph{idem}
3551 and the @context{Voice} is inserted afterwards
3554 \context Staff = down
3555 \new Voice @{ @dots{} \change Staff = up @dots{} @}
3563 Pianos have pedals that alter the way sound is produced. Generally, a
3564 piano has three pedals, sustain, una corda, and sostenuto.
3567 Piano pedal instruction can be expressed by attaching
3568 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
3569 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
3572 @lilypond[quote,raggedright,fragment,verbatim]
3573 c'4\sustainDown c'4\sustainUp
3576 What is printed can be modified by setting @code{pedal@var{X}Strings},
3577 where @var{X} is one of the pedal types: @code{Sustain},
3578 @code{Sostenuto} or @code{UnaCorda}. Refer to
3579 @internalsref{SustainPedal} in the program reference for more
3582 Pedals can also be indicated by a sequence of brackets, by setting the
3583 @code{pedalSustainStyle} property to bracket objects
3585 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
3586 \set Staff.pedalSustainStyle = #'bracket
3588 b\sustainUp\sustainDown
3589 b g \sustainUp a \sustainDown \bar "|."
3592 A third style of pedal notation is a mixture of text and brackets,
3593 obtained by setting the @code{pedalSustainStyle} property to
3596 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
3597 \set Staff.pedalSustainStyle = #'mixed
3599 b\sustainUp\sustainDown
3600 b g \sustainUp a \sustainDown \bar "|."
3603 The default `*Ped.' style for sustain and damper pedals corresponds to
3604 style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
3607 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
3608 c\sostenutoDown d e c, f g a\sostenutoUp
3611 For fine-tuning the appearance of a pedal bracket, the properties
3612 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
3613 @code{PianoPedalBracket} objects (see
3614 @internalsref{PianoPedalBracket} in the Program reference) can be
3615 modified. For example, the bracket may be extended to the right edge
3618 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
3619 \override Staff.PianoPedalBracket #'shorten-pair = #'(0 . -1.0)
3620 c\sostenutoDown d e c, f g a\sostenutoUp
3624 @subsection Arpeggio
3627 @cindex broken arpeggio
3628 @cindex @code{\arpeggio}
3630 You can specify an arpeggio sign on a chord by attaching an
3631 @code{\arpeggio} to a chord
3634 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
3638 When an arpeggio crosses staves, you attach an arpeggio to the chords
3639 in both staves, and set
3640 @internalsref{PianoStaff}.@code{connectArpeggios}
3642 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
3643 \context PianoStaff <<
3644 \set PianoStaff.connectArpeggios = ##t
3645 \new Staff { <c' e g c>\arpeggio }
3646 \new Staff { \clef bass <c,, e g>\arpeggio }
3650 The direction of the arpeggio is sometimes denoted by adding an
3651 arrowhead to the wiggly line
3653 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
3662 A square bracket on the left indicates that the player should not
3663 arpeggiate the chord
3665 @c todo: ugh, lousy typography. Look for real example. --hwn
3667 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
3674 @cindex @code{\arpeggio}
3676 @cindex @code{\arpeggioUp}
3678 @cindex @code{\arpeggioDown}
3679 @code{\arpeggioDown},
3680 @cindex @code{\arpeggioNeutral}
3681 @code{\arpeggioNeutral},
3682 @cindex @code{\arpeggioBracket}
3683 @code{\arpeggioBracket}.
3687 Program reference: @internalsref{ArpeggioEvent},
3688 @internalsref{Arpeggio}.
3692 It is not possible to mix connected arpeggios and unconnected
3693 arpeggios in one @internalsref{PianoStaff} at the same point in time.
3695 @node Staff switch lines
3696 @subsection Staff switch lines
3699 @cindex follow voice
3700 @cindex staff switching
3703 @cindex @code{followVoice}
3705 Whenever a voice switches to another staff, a line connecting the notes
3706 can be printed automatically. This is switched on by setting
3707 @code{PianoStaff.followVoice} to true
3709 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
3710 \context PianoStaff <<
3711 \set PianoStaff.followVoice = ##t
3712 \context Staff \context Voice {
3717 \context Staff=two { \clef bass \skip 1*2 }
3723 Program reference: @internalsref{VoiceFollower}.
3727 @cindex @code{\showStaffSwitch}
3728 @code{\showStaffSwitch},
3729 @cindex @code{\hideStaffSwitch}
3730 @code{\hideStaffSwitch}.
3733 @node Cross staff stems
3734 @subsection Cross staff stems
3736 Chords that cross staves may be produced by increasing the length
3737 of the stem in the lower staff, so it reaches the stem in the upper
3738 staff, or vice versa.
3740 @lilypond[raggedright,verbatim,quote]
3741 stemExtend = \once \override Stem #'length = #22
3742 noFlag = \once \override Stem #'flag-style = #'no-flag
3743 \context PianoStaff <<
3745 \stemDown \stemExtend
3759 @section Vocal music
3761 There are three different issues when printing vocal music
3765 Song texts must be entered as text, not notes. For example, the
3766 input@tie{}@code{d} should be interpreted as a one letter syllable, not the
3770 Song texts must be printed as text, not as notes.
3773 Song texts must be aligned with the notes of their melody.
3776 The simplest solution for printing music uses the @code{\addlyrics}
3777 function to solve all these problems at once. However, these
3778 three functions can be controlled separately, which is necessary
3779 for complex vocal music.
3783 * Setting simple songs::
3785 * Hyphens and extenders::
3786 * The Lyrics context::
3787 * Flexibility in alignment::
3790 * Other vocal issues::
3793 @node Setting simple songs
3794 @subsection Setting simple songs
3796 The easiest way to add lyrics to a melody is to append
3799 \addlyrics @{ @var{the lyrics} @}
3803 to a melody. Here is an example,
3805 @lilypond[raggedright,verbatim,fragment,quote]
3807 \relative { c2 e4 g2. }
3808 \addlyrics { play the game }
3811 More stanzas can be added by adding more
3812 @code{\addlyrics} sections
3814 @lilypond[raggedright,verbatim,fragment,quote]
3816 \relative { c2 e4 g2. }
3817 \addlyrics { play the game }
3818 \addlyrics { speel het spel }
3819 \addlyrics { joue le jeu }
3822 @c TODO - this isn't such a great place for this note, but I can't
3823 @c find a better place without rearranging a lot of lyric stuff.
3824 @c It's yet another thing to look at post-3.0.
3826 The @code{\addlyrics} command is actually just a convienient way
3827 to write a more complicated LilyPond structure that sets up the
3828 lyrics. You should use @code{\addlyrics} unless you need to do
3829 fancy things, in which case you should investigate
3830 @code{\lyricsto} or @code{\lyricmode}.
3834 \addlyrics @{ LYRICS @}
3841 \context Voice = blah @{ music @}
3842 \lyricsto "blah" \new lyrics @{ LYRICS @}
3847 @code{\addlyrics} cannot handle polyphony.
3850 @node Entering lyrics
3851 @subsection Entering lyrics
3855 @cindex @code{\lyricmode}
3858 Lyrics are entered in a special input mode. This mode is introduced
3859 by the keyword @code{\lyricmode}, or by using @code{addlyrics} or
3860 @code{lyricsto}. In this mode you can enter lyrics,
3861 with punctuation and accents, and the input @code{d} is not parsed as
3862 a pitch, but rather as a one letter syllable. Syllables are entered
3863 like notes, but with pitches replaced by text. For example,
3865 \lyricmode @{ Twin-4 kle4 twin- kle litt- le star2 @}
3869 A word lyrics mode begins with an alphabetic character, and ends with
3870 any space or digit. The following characters can be any character
3871 that is not a digit or white space. One important consequence of this
3872 is that a word can end with @code{@}}. The following example is
3873 usually a mistake in the input file. The syllable includes a @code{@}}, so the
3874 opening brace is not balanced
3876 \lyricmode @{ twinkle@}
3879 @cindex @code{\property}, in @code{\lyricmode}
3881 Similarly, a period which follows an alphabetic sequence is included in
3882 the resulting string. As a consequence, spaces must be inserted around
3885 \override Score . LyricText #'font-shape = #'italic
3889 @cindex spaces, in lyrics
3890 @cindex quotes, in lyrics
3892 Any @code{_} character that appears in an unquoted word is converted
3893 to a space. This provides a mechanism for introducing spaces into words
3894 without using quotes. Quoted words can also be used in Lyrics mode to
3895 specify words that cannot be written with the above rules. The
3896 following example incorporates double quotes
3899 \lyricmode @{ He said: "\"Let" my peo ple "go\"" @}
3902 This example is slightly academic, since it gives better looking
3903 results using single quotes, @code{``} and @code{''}
3905 \lyricmode @{ He said: ``Let my peo ple go'' @}
3909 The full definition of a word start in Lyrics mode is somewhat more
3912 A word in Lyrics mode begins with: an alphabetic character, @code{_},
3913 @code{?}, @code{!}, @code{:}, @code{'}, the control characters @code{^A}
3914 through @code{^F}, @code{^Q} through @code{^W}, @code{^Y}, @code{^^},
3915 any 8-bit character with ASCII code over 127, or a two-character
3916 combination of a backslash followed by one of @code{`}, @code{'},
3917 @code{"}, or @code{^}.
3923 Program reference: events @internalsref{LyricEvent}, and
3924 @internalsref{LyricText}.
3928 The definition of lyrics mode is too complex.
3930 @node Hyphens and extenders
3931 @subsection Hyphens and extenders
3935 Centered hyphens are entered as `@code{-}@code{-}' between syllables.
3936 The hyphen will have variable length depending on the space between
3937 the syllables and it will be centered between the syllables.
3942 When a lyric is sung over many notes (this is called a melisma), this is
3943 indicated with a horizontal line centered between a syllable and the
3944 next one. Such a line is called an extender line, and it is entered as
3948 FIXME: check that this compiles and displays correctly. I don't want
3949 to commit this part blindly.
3951 In tighly engraved music, hyphens can be removed. In some languages
3952 (e.g. German and Hungarian), hyphens should not disappear, since
3953 spelling depends on hyphenation. For that purpose, hyphens can be
3954 forced to remain by overriding @code{minimum-length} of
3955 the @code{LyricHyphen} grob.
3959 << \notes \new Staff \relative c'' { \time 1/4 c16[ c c c]
3966 \lyrics \new Lyrics \with {
3967 % Otherwise lyrics are so far apart that hyphens don't disappear
3968 \override SeparationItem #'padding = #0.0
3969 }{ bla -- bla -- bla -- bla --
3970 bla -- bla -- bla -- bla --
3972 \override LyricHyphen #'minimum-length = #0.7
3973 \override LyricHyphen #'spacing-procedure =
3974 #Hyphen_spanner::set_spacing_rods
3976 bla -- bla -- bla -- bla
3983 \StaffContext \remove "Time_signature_engraver"
3994 Program reference: @internalsref{HyphenEvent},
3995 @internalsref{ExtenderEvent}, @internalsref{LyricHyphen}, and
3996 @internalsref{LyricExtender}
4000 @node The Lyrics context
4001 @subsection The Lyrics context
4004 Lyrics are printed by interpreting them in a @internalsref{Lyrics} context
4006 \context Lyrics \lyricmode @dots{}
4009 @cindex automatic syllable durations
4010 @cindex @code{\lyricsto}
4011 @cindex lyrics and melodies
4013 This will place the lyrics according to the durations that were
4014 entered. The lyrics can also be aligned under a given melody
4015 automatically. In this case, it is no longer necessary to enter the
4016 correct duration for each syllable. This is achieved by combining the
4017 melody and the lyrics with the @code{\lyricsto} expression
4019 \lyricsto @var{name} \new Lyrics @dots{}
4022 This aligns the lyrics to the
4023 notes of the @internalsref{Voice} context called @var{name}, which has
4024 to exist. Therefore, normally the @code{Voice} is specified first, and
4025 then the lyrics are specified with @code{\lyricsto}. The command
4026 @code{\lyricsto} switches to @code{\lyricmode} mode automatically, so the
4027 @code{\lyricmode} keyword may be omitted.
4029 For different or more complex orderings, the best way is to setup the
4030 hierarchy of staves and lyrics first, e.g.,
4032 \context ChoirStaff <<
4033 \context Lyrics = sopranoLyrics @{ s1 @}
4034 \context Voice = soprano @{ @emph{music} @}
4035 \context Lyrics = tenorLyrics @{ s1 @}
4036 \context Voice = tenor @{ @emph{music} @}
4039 and then combine the appropriate melodies and lyric lines
4041 \lyricsto "soprano" \context Lyrics = sopranoLyrics
4046 The final input would resemble
4049 <<\context ChoirStaff << @emph{setup the music} >>
4050 \lyricsto "soprano" @emph{etc}
4051 \lyricsto "alto" @emph{etc}
4057 The @code{\lyricsto} command detects melismata: it only puts one
4058 syllable under a tied or slurred group of notes. If you want to force
4059 an unslurred group of notes to be a melisma, insert @code{\melisma}
4060 after the first note of the group, and @code{\melismaEnd} after the
4063 @lilypond[quote,relative=2,raggedright,fragment,verbatim]
4065 \context Voice = "lala" {
4073 \lyricsto "lala" \new Lyrics {
4079 In addition, notes are considered a melisma if they are manually
4080 beamed, and automatic beaming (see @ref{Setting automatic beam
4081 behavior}) is switched off.
4087 The criteria for deciding melismata can
4088 be tuned with the property @code{melismaBusyProperties}. See
4089 @internalsref{Melisma_translator} in the program reference for more
4094 Lyrics can also be entered without @code{\lyricsto}. In this case the
4095 duration of each syllable must be entered explicitly, for example,
4102 The alignment to a melody can be specified with the
4103 @code{associatedVoice} property,
4106 \set associatedVoice = #"lala"
4110 The value of the property (here: @code{"lala"}) should be the name of
4111 a @internalsref{Voice} context. Without this setting, extender lines
4112 will not be formatted properly.
4114 Here is an example demonstrating manual lyric durations,
4116 @lilypond[relative=1,raggedright,verbatim,fragment,quote]
4117 << \context Voice = melody {
4121 \new Lyrics \lyricmode {
4122 \set associatedVoice = #"melody"
4128 @cindex choral score
4130 A complete example of a SATB score setup is in section
4131 @ref{Vocal ensembles}.
4136 @code{\melisma}, @code{\melismaEnd}
4137 @cindex @code{\melismaEnd}
4138 @cindex @code{\melisma}
4142 Program reference: @internalsref{LyricCombineMusic},
4143 @internalsref{Lyrics}, @internalsref{Melisma_translator}.
4146 @inputfileref{input/@/regression,lyric@/-combine@/-new@/.ly}.
4147 @c TODO: make separate section for melismata
4149 @c I can't find these examples in 2.0 or 2.2; remove. -gp
4150 @c @inputfileref{input/@/test,lyrics@/-melisma@/-variants@/.ly}.
4151 @c @inputfileref{input/@/test,lyrics@/-melisma@/-faster@/.ly}.
4155 Melismata are not detected automatically, and extender lines must be
4159 @c TODO: document \new Staff << Voice \lyricsto >> bug
4161 @node Flexibility in alignment
4162 @subsection Flexibility in alignment
4165 Often, different stanzas of one song are put to one melody in slightly
4166 differing ways. Such variations can still be captured with
4169 One possibility is that the text has a melisma in one stanza, but
4170 multiple syllables in another one. One solution is to make the faster
4171 voice ignore the melisma. This is done by setting
4172 @code{ignoreMelismata} in the Lyrics context.
4174 There has one tricky aspect. The setting for @code{ignoreMelismata}
4175 must be set one syllable @emph{before} the non-melismatic syllable
4176 in the text, as shown here,
4178 @lilypond[verbatim,raggedright,quote]
4180 \relative \context Voice = "lahlah" {
4181 \set Staff.autoBeaming = ##f
4187 \new Lyrics \lyricsto "lahlah" {
4190 \new Lyrics \lyricsto "lahlah" {
4191 \set ignoreMelismata = ##t % applies to "fas"
4193 \unset ignoreMelismata
4200 The @code{ignoreMelismata} applies to the syllable ``fas'', so it
4201 should be entered before ``go''.
4203 The reverse is also possible: making a lyric line slower than the
4204 standard. This can be achieved by insert @code{\skip}s into the
4205 lyrics. For every @code{\skip}, the text will be delayed another note.
4208 @lilypond[verbatim,raggedright,quote]
4209 \relative { c c g' }
4216 More complex variations in text underlay are possible. It is possible
4217 to switch the melody for a line of lyrics during the text. This is
4218 done by setting the @code{associatedVoice} property. In the example
4220 @lilypond[raggedright,quote]
4222 \relative \context Voice = "lahlah" {
4223 \set Staff.autoBeaming = ##f
4226 \context Voice = alternative {
4229 % show associations clearly.
4230 \override NoteColumn #'force-hshift = #-3
4241 \new Lyrics \lyricsto "lahlah" {
4242 Ju -- ras -- sic Park
4244 \new Lyrics \lyricsto "lahlah" {
4245 % Tricky: need to set associatedVoice
4246 % one syllable too soon!
4247 \set associatedVoice = alternative % applies to "ran"
4251 \set associatedVoice = lahlah % applies to "rus"
4257 the text for the first stanza is set to a melody called ``lahlah'',
4260 \new Lyrics \lyricsto "lahlah" @{
4261 Ju -- ras -- sic Park
4266 The second stanza initially is set to the @code{lahlah} context, but
4267 for the syllable ``ran'', it switches to a different melody.
4268 This is achieved with
4270 \set associatedVoice = alternative
4274 Here, @code{alternative} is the name of the @code{Voice} context
4275 containing the triplet.
4277 Again, the command must be one syllable too early, before ``Ty'' in
4281 \new Lyrics \lyricsto "lahlah" @{
4282 \set associatedVoice = alternative % applies to "ran"
4286 \set associatedVoice = lahlah % applies to "rus"
4292 The underlay is switched back to the starting situation by assigning
4293 @code{lahlah} to @code{associatedVoice}.
4299 @subsection More stanzas
4301 @cindex phrasing, in lyrics
4304 @cindex stanza number
4305 @cindex singer's names
4306 @cindex name of singer
4308 Stanza numbers can be added by setting @code{stanza}, e.g.,
4310 @lilypond[quote,raggedright,verbatim,relative=2,fragment]
4312 \time 3/4 g2 e4 a2 f4 g2.
4315 Hi, my name is Bert.
4318 Oh, che -- ri, je t'aime
4322 These numbers are put just before the start of first syllable.
4324 Names of singers can also be added. They are printed at the start of
4325 the line, just like instrument names. They are created by setting
4326 @code{vocalName}. A short version may be entered as @code{vocNam}.
4329 @lilypond[fragment,raggedright,quote,verbatim,relative=2]
4331 \time 3/4 g2 e4 a2 f4 g2.
4333 \set vocalName = "Bert "
4334 Hi, my name is Bert.
4336 \set vocalName = "Ernie "
4337 Oh, che -- ri, je t'aime
4343 Program reference: Layout objects @internalsref{LyricText} and
4344 @internalsref{VocalName}. Music expressions
4345 @internalsref{LyricEvent}.
4353 The term @emph{ambitus} denotes a range of pitches for a given voice
4354 in a part of music. It may also denote the pitch range that a musical
4355 instrument is capable of playing. Ambits are printed on vocal parts,
4356 so performers can easily determine it meets their capabilities.
4358 Ambits are denoted at the beginning of a piece near the initial clef.
4359 The range is graphically specified by two note heads that represent the
4360 minimum and maximum pitch. To print such ambits, add the
4361 @internalsref{Ambitus_engraver} to the @internalsref{Voice} context,
4368 \consists Ambitus_engraver
4373 This results in the following output
4375 @lilypond[quote,raggedright]
4379 \consists Ambitus_engraver
4383 \relative \new Staff {
4388 If you have multiple voices in a single staff and you want a single
4389 ambitus per staff rather than per each voice, add the
4390 @internalsref{Ambitus_engraver} to the @internalsref{Staff} context
4391 rather than to the @internalsref{Voice} context. Here is an example,
4393 @lilypond[verbatim,raggedright,quote]
4395 \consists "Ambitus_engraver"
4399 \remove "Ambitus_engraver"
4401 \override Ambitus #'X-offset-callbacks
4402 = #(list (lambda (grob axis) -1.0))
4407 \remove "Ambitus_engraver"
4416 This example uses one advanced feature,
4419 \override Ambitus #'X-offset-callbacks
4420 = #(list (lambda (grob axis) -1.0))
4424 This code moves the ambitus to the left. The same effect could have
4425 been achieved with @code{extra-offset}, but then the formatting system
4426 would not reserve space for the moved object.
4430 Program reference: @internalsref{Ambitus},
4431 @internalsref{AmbitusLine}, @internalsref{AmbitusNoteHead},
4432 @internalsref{AmbitusAccidental}.
4434 Examples: @inputfileref{input/@/regression,ambitus@/.ly}.
4438 There is no collision handling in the case of multiple per-voice
4441 @node Other vocal issues
4442 @subsection Other vocal issue
4445 yeah, I'm giving up somewhat by stuffing a bunch of things in
4446 here. But at least they're in the manual now; it's easier to
4447 move them around in the manual once they're already here.
4449 Besides, if users complain about everything stuffed in here, I
4450 can ask them for specific instructions about where to move these
4451 examples, and that might get them more involved in the docs. -gp
4454 You can display alternate (or divisi) lyrics by naming voice
4455 contexts and attaching lyrics to those specific contexts.
4457 @lilypond[verbatim,raggedright,quote]
4459 \context Voice = "melody" {
4464 \context Voice = splitpart { \voiceTwo c4 }
4469 \new Lyrics \lyricsto "melody" { we shall not o- ver- come }
4470 \new Lyrics \lyricsto "splitpart" { shall }
4475 You can use this trick to display different lyrics for a repeated
4478 @lilypond[verbatim,raggedright,quote]
4480 \context Voice = melody \relative c' {
4482 \context Voice = verse \repeat volta 2 {c4 d e f | g1 | }
4484 \lyricsto melody \context Lyrics = mainlyrics \lyricmode {
4487 \lyricsto verse \context Lyrics = mainlyrics \lyricmode {
4489 \lyricsto verse \context Lyrics = repeatlyrics \lyricmode {
4490 dodo rere mimi fafa solsol }
4496 @node Other instrument specific notation, Tablatures, Vocal music, Notation manual
4497 @section Other instrument specific notation
4499 This section includes extra information for writing string music, and may
4500 include extra information for other instruments in the future.
4506 @node Harmonic notes, , Other instrument specific notation, Other instrument specific notation
4507 @subsection Harmonic notes
4509 @cindex artificial harmonics
4512 Artificial harmonics are notated with a different notehead style. They
4513 are entered by marking the harmonic pitch with @code{\harmonic}.
4515 @lilypond[raggedright,verbatim,quote,fragment]
4520 @node Tablatures, Popular music, Other instrument specific notation, Notation manual
4524 @cindex guitar tablature
4526 Tablature notation is used for notating music for plucked string
4527 instruments. Pitches are not denoted with note heads, but by
4528 indicating on which string and fret a note must be played. LilyPond
4529 offers limited support for tablature.
4532 * Tablatures basic::
4533 * Non-guitar tablatures::
4536 @node Tablatures basic, Non-guitar tablatures, Tablatures, Tablatures
4537 @subsection Tablatures basic
4538 @cindex Tablatures basic
4540 The string number associated to a note is given as a backslash
4541 followed by a number, e.g., @code{c4\3} for a C quarter on the third
4542 string. By default, string 1 is the highest one, and the tuning
4543 defaults to the standard guitar tuning (with 6 strings). The notes
4544 are printed as tablature, by using @internalsref{TabStaff} and
4545 @internalsref{TabVoice} contexts
4547 @lilypond[quote,raggedright,fragment,verbatim]
4554 @cindex @code{minimumFret}
4557 When no string is specified, the first string that does not give a
4558 fret number less than @code{minimumFret} is selected. The default
4559 value for @code{minimumFret} is 0
4564 \set TabStaff.minimumFret = #8
4567 @lilypond[quote,raggedright]
4571 \set TabStaff.minimumFret = #8
4574 \context StaffGroup <<
4575 \context Staff { \clef "G_8" \frag }
4576 \context TabStaff { \frag }
4582 Program reference: @internalsref{TabStaff}, @internalsref{TabVoice}, and
4583 @internalsref{StringNumberEvent}.
4587 Chords are not handled in a special way, and hence the automatic
4588 string selector may easily select the same string to two notes in a
4592 @node Non-guitar tablatures, , Tablatures basic, Tablatures
4593 @subsection Non-guitar tablatures
4594 @cindex Non-guitar tablatures
4596 You can change the number of strings, by setting the number of lines
4597 in the @internalsref{TabStaff}.
4599 You can change the tuning of the strings. A string tuning is given as
4600 a Scheme list with one integer number for each string, the number
4601 being the pitch (measured in semitones relative to middle C) of an
4602 open string. The numbers specified for @code{stringTuning} are the
4603 numbers of semitones to subtract or add, starting the specified pitch
4604 by default middle C, in string order. In the next example,
4605 @code{stringTunings} is set for the pitches e, a, d, and g
4607 @lilypond[quote,raggedright,fragment,verbatim]
4608 \context TabStaff <<
4609 \set TabStaff.stringTunings = #'(-5 -10 -15 -20)
4611 a,4 c' a e' e c' a e'
4618 No guitar special effects have been implemented.
4622 Program reference: @internalsref{Tab_note_heads_engraver}.
4625 @node Popular music, Orchestral music, Tablatures, Notation manual
4626 @section Popular music
4628 This section discusses issues that arise when writing popular music.
4633 * Printing chord names::
4638 @node Chord names, Chords mode, Popular music, Popular music
4639 @subsection Chord names
4642 LilyPond has support for printing chord names. Chords may be entered
4643 in musical chord notation, i.e., @code{< .. >}, but they can also be
4644 entered by name. Internally, the chords are represented as a set of
4645 pitches, so they can be transposed
4648 @lilypond[quote,raggedright,verbatim,raggedright]
4649 twoWays = \transpose c c' {
4658 << \context ChordNames \twoWays
4659 \context Voice \twoWays >>
4662 This example also shows that the chord printing routines do not try to
4663 be intelligent. The last chord (@code{f bes d}) is not interpreted as
4666 @c this menu isn't needed.
4670 * Printing chord names::
4675 @subsection Chords mode
4678 In chord mode sets of pitches (chords) are entered with normal note
4679 names. A chord is entered by the root, which is entered like a
4682 @lilypond[quote,raggedright,fragment,verbatim]
4683 \chordmode { es4. d8 c2 }
4687 The mode is introduced by the keyword @code{\chordmode}.
4692 Other chords may be entered by suffixing a colon and introducing a
4693 modifier (which may include a number if desired)
4694 @lilypond[quote,fragment,verbatim]
4695 \chordmode { e1:m e1:7 e1:m7 }
4697 The first number following the root is taken to be the `type' of the
4698 chord, thirds are added to the root until it reaches the specified
4700 @lilypond[quote,fragment,verbatim]
4701 \chordmode { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 }
4704 @cindex root of chord
4705 @cindex additions, in chords
4706 @cindex removals, in chords
4708 More complex chords may also be constructed adding separate steps
4709 to a chord. Additions are added after the number following
4710 the colon and are separated by dots
4711 @lilypond[quote,verbatim,fragment]
4712 \chordmode { c:5.6 c:3.7.8 c:3.6.13 }
4714 Chord steps can be altered by suffixing a @code{-} or @code{+} sign
4716 @lilypond[quote,verbatim,fragment]
4717 \chordmode { c:7+ c:5+.3- c:3-.5-.7- }
4719 Removals are specified similarly and are introduced by a caret. They
4720 must come after the additions
4721 @lilypond[quote,verbatim,fragment]
4722 \chordmode { c^3 c:7^5 c:9^3.5 }
4725 Modifiers can be used to change pitches. The following modifiers are
4730 The minor chord. This modifier lowers the 3rd and (if present) the 7th step.
4733 The diminished chord. This modifier lowers the 3rd, 5th and (if present)
4737 The augmented chord. This modifier raises the 5th step.
4740 The major 7th chord. This modifier raises the 7th step if present.
4743 The suspended 4th or 2nd. This modifier removes the 3rd
4744 step. Append either @code{2} or @code{4} to add the 2nd or 4th step to
4748 Modifiers can be mixed with additions
4749 @lilypond[quote,verbatim,fragment]
4750 \chordmode { c:sus4 c:7sus4 c:dim7 c:m6 }
4753 @cindex modifiers, in chords.
4760 Since an unaltered 11 does not sound good when combined with an
4761 unaltered 3, the 11 is removed in this case (unless it is added
4763 @lilypond[quote,raggedright,fragment,verbatim]
4764 \chordmode { c:13 c:13.11 c:m13 }
4769 An inversion (putting one pitch of the chord on the bottom), as well
4770 as bass notes, can be specified by appending
4771 @code{/}@var{pitch} to the chord
4772 @lilypond[quote,raggedright,fragment,verbatim]
4773 \chordmode { c1 c/g c/f }
4777 A bass note can be added instead transposed out of the chord,
4778 by using @code{/+}@var{pitch}.
4780 @lilypond[quote,raggedright,fragment,verbatim]
4781 \chordmode { c1 c/+g c/+f }
4784 Chords is a mode similar to @code{\lyricmode}, etc. Most
4785 of the commands continue to work, for example, @code{r} and
4786 @code{\skip} can be used to insert rests and spaces, and property
4787 commands may be used to change various settings.
4793 Each step can only be present in a chord once. The following
4794 simply produces the augmented chord, since @code{5+} is interpreted
4797 @lilypond[quote,raggedright,verbatim,fragment]
4798 \chordmode { c:5.5-.5+ }
4802 @node Printing chord names
4803 @subsection Printing chord names
4805 @cindex printing chord names
4809 For displaying printed chord names, use the @internalsref{ChordNames} context.
4810 The chords may be entered either using the notation
4811 described above, or directly using @code{<} and @code{>}
4813 @lilypond[quote,verbatim,raggedright]
4815 \chordmode {a1 b c} <d' f' a'> <e' g' b'>
4818 \context ChordNames \harmonies
4819 \context Staff \harmonies
4823 You can make the chord changes stand out by setting
4824 @internalsref{ChordNames}.@code{chordChanges} to true. This will only
4825 display chord names when there is a change in the chords scheme and at
4826 the start of a new line
4828 @lilypond[quote,verbatim,raggedright]
4829 harmonies = \chordmode {
4830 c1:m c:m \break c:m c:m d
4833 \context ChordNames {
4834 \set chordChanges = ##t
4836 \context Staff \transpose c c' \harmonies
4840 The previous examples all show chords over a staff. This is not
4841 necessary. Chords may also be printed separately. It may be necessary
4842 to add @internalsref{Volta_engraver} and @internalsref{Bar_engraver}
4843 for showing repeats.
4845 @lilypond[raggedright,verbatim]
4846 \new ChordNames \with {
4847 \override BarLine #'bar-size = #4
4848 voltaOnThisStaff = ##t
4849 \consists Bar_engraver
4850 \consists "Volta_engraver"
4852 \repeat volta 2 \chordmode {
4861 The default chord name layout is a system for Jazz music, proposed by
4862 Klaus Ignatzek (see @ref{Literature list}). It can be tuned through the
4863 following properties
4866 @cindex @code{chordNameExceptions}
4867 @item chordNameExceptions
4868 This is a list that contains the chords that have special formatting.
4870 The exceptions list should be encoded as
4872 @{ <c f g bes>1 \markup @{ \super "7" "wahh" @} @}
4875 To get this information into @code{chordNameExceptions} takes a little
4876 manoeuvring. The following code transforms @code{chExceptionMusic}
4877 (which is a sequential music) into a list of exceptions.
4879 (sequential-music-to-chord-exceptions chExceptionMusic #t)
4884 (sequential-music-to-chord-exceptions chExceptionMusic #t)
4887 adds the new exceptions to the default ones, which are defined in
4888 @file{ly/@/chord@/-modifier@/-init@/.ly}.
4890 For an example of tuning this property, see also
4891 @inputfileref{input/@/regression,chord@/-name@/-exceptions@/.ly}.
4892 @cindex exceptions, chord names.
4895 @cindex @code{majorSevenSymbol}
4896 @item majorSevenSymbol
4897 This property contains the markup object used for the 7th step, when
4898 it is major. Predefined options are @code{whiteTriangleMarkup} and
4899 @code{blackTriangleMarkup}. See
4900 @inputfileref{input/@/regression,chord@/-name@/-major7@/.ly} for an example.
4902 @cindex @code{chordNameSeparator}
4903 @item chordNameSeparator
4904 Different parts of a chord name are normally separated by a
4905 slash. By setting @code{chordNameSeparator}, you can specify other
4907 @lilypond[quote,raggedright,fragment,verbatim]
4908 \context ChordNames \chordmode {
4910 \set chordNameSeparator
4911 = \markup { \typewriter "|" }
4916 @cindex @code{chordRootNamer}
4917 @item chordRootNamer
4918 The root of a chord is usually printed as a letter with an optional
4919 alteration. The transformation from pitch to letter is done by this
4920 function. Special note names (for example, the German ``H'' for a
4921 B-chord) can be produced by storing a new function in this property.
4923 @cindex @code{chordNoteNamer}
4924 @item chordNoteNamer
4925 The default is to print single pitch, e.g., the bass note, using the
4926 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
4927 to a specialized function to change this behavior. For example, the
4928 base can be printed in lower case.
4932 The predefined variables @code{\germanChords},
4933 @code{\semiGermanChords} set these variables. The effect is
4936 @lilypondfile[raggedright]{chord-names-german.ly}
4938 There are also two other chord name schemes implemented: an alternate
4939 Jazz chord notation, and a systematic scheme called Banter chords. The
4940 alternate Jazz notation is also shown on the chart in @ref{Chord name
4941 chart}. Turning on these styles is described in the input file
4942 @inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
4946 @cindex chords, jazz
4951 @cindex @code{\germanChords}
4952 @code{\germanChords},
4953 @cindex @code{\semiGermanChords}
4954 @code{\semiGermanChords}.
4961 Examples: @inputfileref{input/@/regression,chord@/-name@/-major7@/.ly},
4962 @inputfileref{input/@/regression,chord@/-name@/-exceptions@/.ly},
4963 @inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
4966 Init files: @file{scm/@/chords@/-ignatzek@/.scm}, and
4967 @file{scm/@/chord@/-entry@/.scm}.
4972 Chord names are determined solely from the list of pitches. Chord
4973 inversions are not identified, and neither are added bass notes. This
4974 may result in strange chord names when chords are entered with the
4975 @code{< .. >} syntax.
4979 @subsection Fret diagrams
4980 @cindex fret diagrams
4981 @cindex chord diagrams
4983 Fret diagrams can be added to music as a markup to the desired note. The
4984 markup contains information about the desired fret diagram, as shown in the
4987 @lilypond[verbatim, raggedright, quote]
4989 d' ^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
4991 fis' ^\markup \override #'(size . 0.75) {
4992 \override #'(finger-code . below-string) {
4993 \fret-diagram-verbose #'((place-fret 6 2 1) (barre 6 1 2)
4994 (place-fret 5 4 3) (place-fret 4 4 4)
4995 (place-fret 3 3 2) (place-fret 2 2 1)
5000 c' ^\markup \override #'(dot-radius . 0.35) {
5001 \override #'(finger-code . in-dot) {
5002 \override #'(dot-color . white) {
5003 \fret-diagram-terse #"x;3-1-(;5-2;5-3;5-4;3-1-);"
5012 There are three different fret-diagram markup interfaces: standard, terse,
5013 and verbose. The three interfaces produce equivalent markups, but have
5014 varying amounts of information in the markup string. Details about the
5015 markup interfaces are found at @ref{Overview of text markup commands}.
5017 You can set a number of graphical properties according to your preference.
5018 Details about the property interface to fret diagrams are found at
5019 @internalsref{fret-diagram-interface}.
5024 Examples: @inputfileref{input/@/test,fret@/-diagram@/.ly}
5028 @subsection Improvisation
5030 Improvisation is sometimes denoted with slashed note heads. Such note
5031 heads can be created by adding a @internalsref{Pitch_squash_engraver}
5032 to the @internalsref{Staff} or @internalsref{Voice} context. Then, the
5036 \set squashedPosition = #0
5037 \override NoteHead #'style = #'slash
5041 switches on the slashes.
5043 There are shortcuts @code{\improvisationOn} (and an accompanying
5044 @code{\improvisationOff}) for this command sequence. They are used in
5045 the following example
5047 @lilypond[verbatim,raggedright,quote]
5049 \consists Pitch_squash_engraver
5051 e8 e g a a16(bes)(a8) g \improvisationOn
5054 ~fis2 \improvisationOff a16(bes) a8 g e
5060 @node Orchestral music
5061 @section Orchestral music
5063 @cindex Writing parts
5065 Orchestral music involves some special notation, both in the full
5066 score and the individual parts. This section explains how to tackle
5067 some common problems in orchestral music.
5072 * System start delimiters::
5073 * Aligning to cadenzas::
5076 * Instrument names::
5078 * Instrument transpositions::
5079 * Multi measure rests::
5080 * Automatic part combining::
5082 * Different editions from one source::
5083 * Quoting other voices::
5084 * Formatting cue notes::
5087 @node System start delimiters
5088 @subsection System start delimiters
5090 Polyphonic scores consist of many staves. These staves can be
5091 constructed in three different ways
5093 @item The group is started with a brace at the left, and bar lines are
5094 connected. This is done with the @internalsref{GrandStaff} context.
5096 @lilypond[verbatim,raggedright,quote]
5105 @item The group is started with a bracket, and bar lines are connected.
5106 This is done with the
5107 @internalsref{StaffGroup} context
5109 @lilypond[verbatim,raggedright,quote]
5118 @item The group is started with a vertical line. Bar lines are not
5119 connected. This is the default for the score.
5121 @lilypond[verbatim,raggedright,quote]
5130 @cindex Staff, multiple
5131 @cindex bracket, vertical
5132 @cindex brace, vertical
5139 The bar lines at the start of each system are
5140 @internalsref{SystemStartBar}, @internalsref{SystemStartBrace}, and
5141 @internalsref{SystemStartBracket}. Only one of these types is created
5142 in every context, and that type is determined by the property
5143 @code{systemStartDelimiter}.
5145 @node Aligning to cadenzas
5146 @subsection Aligning to cadenzas
5149 In an orchestral context, cadenzas present a special problem:
5150 when constructing a score that includes a cadenza, all other
5151 instruments should skip just as many notes as the length of the
5152 cadenza, otherwise they will start too soon or too late.
5154 A solution to this problem are the functions @code{mmrest-of-length}
5155 and @code{skip-of-length}. These Scheme functions take a piece of music
5156 as argument, and generate a @code{\skip} or multi-rest, exactly as
5157 long as the piece. The use of @code{mmrest-of-length} is demonstrated
5158 in the following example.
5160 @lilypond[verbatim,raggedright,quote]
5161 cadenza = \relative c' {
5162 c4 d8 << { e f g } \\ { d4. } >>
5167 \new Staff { \cadenza c'4 }
5169 #(ly:export (mmrest-of-length cadenza))
5179 @node Rehearsal marks
5180 @subsection Rehearsal marks
5181 @cindex Rehearsal marks
5183 @cindex @code{\mark}
5185 To print a rehearsal mark, use the @code{\mark} command
5187 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
5196 (The letter@tie{}`I' is skipped in accordance with engraving traditions.)
5197 @c umm, is the manual the right place for feature requests? :) -gp
5198 @c FIXME - should make that tunable.
5200 The mark is incremented automatically if you use @code{\mark
5201 \default}, but you can also use an integer argument to set the mark
5202 manually. The value to use is stored in the property
5203 @code{rehearsalMark}.
5205 The style is defined by the property @code{markFormatter}. It is a
5206 function taking the current mark (an integer) and the current context
5207 as argument. It should return a markup object. In the following
5208 example, @code{markFormatter} is set to a canned procedure. After a
5209 few measures, it is set to function that produces a boxed number.
5211 @lilypond[fragment,quote,raggedright,verbatim,relative=2]
5212 \set Score.markFormatter = #format-mark-numbers
5215 \set Score.markFormatter = #format-mark-box-numbers
5221 The file @file{scm/@/translation@/-functions@/.scm} contains the definitions
5222 of @code{format-mark-numbers} (the default format), @code{format-mark-box-numbers},
5223 @code{format-mark-letters} and @code{format-mark-box-letters}.
5224 These can be used as inspiration for other formatting functions.
5227 @cindex coda on bar line
5228 @cindex segno on bar line
5229 @cindex fermata on bar line
5230 @cindex bar lines, symbols on
5232 The @code{\mark} command can also be used to put signs like coda,
5233 segno, and fermata on a bar line. Use @code{\markup} to
5234 access the appropriate symbol
5236 @lilypond[fragment,quote,raggedright,verbatim,relative=2]
5237 c1 \mark \markup { \musicglyph #"scripts-ufermata" }
5241 If the mark occurs at a line break, the mark will be printed at the
5242 beginning of the next line.
5243 @c IMO this is a bug; hopefully it'll be fixed soon, so I can
5244 @c delete this sentence. -gp
5245 If there is no next line, then the mark will not be printed at all.
5246 To print the mark at the end of the current line, use
5249 \override Score.RehearsalMark
5250 #'break-visibility = #begin-of-line-invisible
5256 @cindex bar lines, putting symbols on
5260 Program reference: @internalsref{MarkEvent}, @internalsref{RehearsalMark}.
5262 Init files: @file{scm/@/translation@/-functions@/.scm} contains the
5263 definition of @code{format-mark-numbers} and
5264 @code{format-mark-letters}. They can be used as inspiration for other
5265 formatting functions.
5267 Examples: @inputfileref{input/@/regression,rehearsal@/-mark@/-letter@/.ly},
5269 @inputfileref{input/@/regression,rehearsal@/-mark@/-number@/.ly}.
5273 @subsection Bar numbers
5277 @cindex measure numbers
5278 @cindex @code{currentBarNumber}
5280 Bar numbers are printed by default at the start of the line. The
5281 number itself is stored in the @code{currentBarNumber} property, which
5282 is normally updated automatically for every measure.
5284 Bar numbers can be typeset at regular intervals instead of at the
5285 beginning of each line. This is illustrated in the following example,
5286 whose source is available as
5287 @inputfileref{input/@/test,bar@/-number@/-regular@/-interval@/.ly}
5289 @lilypondfile[raggedright,quote]{bar-number-regular-interval.ly}
5291 Bar numbers can be typeset manually by tweaking the
5292 @code{markFormatter} property
5294 @lilypond[verbatim,raggedright,quote]
5296 \set Score.markFormatter
5297 = #(lambda (mark context)
5300 (number->string (ly:context-property context
5301 'currentBarNumber)))))
5303 c1 \bar "||" \mark \default c1 c1 \mark \default c1 \bar "|."
5307 Bar numbers can be manually changed by setting the
5308 @code{Staff.currentBarNumber} property
5310 @lilypond[verbatim,raggedright,quote]
5312 \repeat unfold 4 {c4 c c c} \break
5313 \set Score.currentBarNumber = #50
5314 \repeat unfold 4 {c4 c c c}
5320 Program reference: @internalsref{BarNumber}.
5323 @inputfileref{input/@/test,bar@/-number@/-every@/-five@/-reset@/.ly},
5324 and @inputfileref{input/@/test,bar@/-number@/-regular@/-interval@/.ly}.
5328 Bar numbers can collide with the @internalsref{StaffGroup} bracket, if
5329 there is one at the top. To solve this, the
5330 @code{padding} property of @internalsref{BarNumber} can be
5331 used to position the number correctly.
5333 @node Instrument names
5334 @subsection Instrument names
5336 In an orchestral score, instrument names are printed at the left side
5339 This can be achieved by setting @internalsref{Staff}.@code{instrument}
5340 and @internalsref{Staff}.@code{instr}. This will print a string before
5341 the start of the staff. For the first staff, @code{instrument} is
5342 used, for the following ones, @code{instr} is used.
5344 @lilypond[quote,verbatim,raggedright,relative=1,fragment]
5345 \set Staff.instrument = "Ploink "
5346 \set Staff.instr = "Plk "
5352 You can also use markup texts to construct more complicated instrument
5355 @lilypond[quote,fragment,verbatim,raggedright]
5356 \set Staff.instrument = \markup {
5357 \column { "Clarinetti"
5358 \line { "in B" \smaller \flat } } }
5362 For longer instrument names, it may be useful to increase the
5363 @code{indent} setting in the @code{\layout} block.
5367 Program reference: @internalsref{InstrumentName}.
5371 When you put a name on a grand staff or piano staff, the width of the
5372 brace is not taken into account. You must add extra spaces to the end of
5373 the name to avoid a collision.
5376 @subsection Transpose
5378 @cindex transposition of pitches
5379 @cindex @code{\transpose}
5381 A music expression can be transposed with @code{\transpose}. The
5384 \transpose @var{from} @var{to} @var{musicexpr}
5387 This means that @var{musicexpr} is transposed by the interval between
5388 the pitches @var{from} and @var{to}: any note with pitch @code{from}
5389 is changed to @code{to}.
5392 For example, consider a piece written in the key of D-major. If
5393 this piece is a little too low for its performer, it can be
5394 transposed up to E-major with
5396 \transpose d e @dots{}
5399 Consider a part written for violin (a C instrument). If
5400 this part is to be played on the A clarinet, the following
5401 transposition will produce the appropriate part
5404 \transpose a c @dots{}
5407 @code{\transpose} distinguishes between enharmonic pitches: both
5408 @code{\transpose c cis} or @code{\transpose c des} will transpose up
5409 half a tone. The first version will print sharps and the second
5410 version will print flats
5412 @lilypond[quote,raggedright,verbatim]
5413 mus = { \key d \major cis d fis g }
5417 \transpose c g' \mus
5418 \transpose c f' \mus
5425 Program reference: @internalsref{TransposedMusic}, and
5426 @internalsref{UntransposableMusic}.
5430 If you want to use both @code{\transpose} and @code{\relative},
5431 you must put @code{\transpose} outside of @code{\relative}, since
5432 @code{\relative} will have no effect music that appears inside a
5435 @node Instrument transpositions
5436 @subsection Instrument transpositions
5438 The key of a transposing instrument can also be specified. This
5439 applies to many wind instruments, for example, clarinets (B-flat, A, and
5440 E-flat), horn (F) and trumpet (B-flat, C, D, and E-flat).
5442 The transposition is entered after the keyword @code{\transposition}
5445 \transposition bes %% B-flat clarinet
5449 This command sets the property @code{instrumentTransposition}. The value of
5450 this property is used for MIDI output and quotations. It does not
5451 affect how notes are printed in the current staff.
5453 The pitch to use for @code{\transposition} should correspond to the
5454 transposition of the notes. For example, when entering a score in
5455 concert pitch, typically all voices are entered in C, so
5456 they should be entered as
5469 The command @code{\transposition} should be used when the music is
5470 entered from a (transposed) orchestral part. For example, in
5471 classical horn parts, the tuning of the instrument is often changed
5472 during a piece. When copying the notes from the part, use
5473 @code{\transposition}, e.g.,
5486 @cindex transposition, MIDI
5487 @cindex transposition, instrument
5490 @node Multi measure rests
5491 @subsection Multi measure rests
5492 @cindex multi measure rests
5493 @cindex Rests, multi measure
5497 Multi-measure rests are entered using `@code{R}'. It is specifically
5498 meant for full bar rests and for entering parts: the rest can expand
5499 to fill a score with rests, or it can be printed as a single
5500 multi-measure rest. This expansion is controlled by the property
5501 @code{Score.skipBars}. If this is set to true, empty measures will not
5502 be expanded, and the appropriate number is added automatically
5504 @lilypond[quote,raggedright,fragment,verbatim]
5505 \time 4/4 r1 | R1 | R1*2
5506 \set Score.skipBars = ##t R1*17 R1*4
5509 The @code{1} in @code{R1} is similar to the duration notation used for
5510 notes. Hence, for time signatures other than 4/4, you must enter other
5511 durations. This can be done with augmentation dots or fractions
5513 @lilypond[quote,raggedright,fragment,verbatim]
5514 \set Score.skipBars = ##t
5523 An @code{R} spanning a single measure is printed as either a whole rest
5524 or a breve, centered in the measure regardless of the time signature.
5526 If there are only a few measures of rest, LilyPond prints ``church rests''
5527 (a series of rectangles) in the staff. To replace that with a simple
5528 rest, use @code{MultiMeasureRest.expand-limit}.
5530 @lilypond[quote,raggedright,fragment,verbatim]
5531 \set Score.skipBars = ##t
5533 \override MultiMeasureRest #'expand-limit = 1
5538 @cindex text on multi-measure rest
5539 @cindex script on multi-measure rest
5540 @cindex fermata on multi-measure rest
5542 Texts can be added to multi-measure rests by using the
5543 @var{note}-@code{markup} syntax (see @ref{Text markup}).
5544 A variable (@code{\fermataMarkup}) is provided for
5547 @lilypond[quote,raggedright,verbatim,fragment]
5548 \set Score.skipBars = ##t
5550 R2.*10^\markup { \italic "ad lib." }
5554 If you want to have text on the left end of a multi-measure rest,
5555 attach the text to a zero-length skip note, i.e.,
5563 @cindex whole rests for a full measure
5567 Program reference: @internalsref{MultiMeasureRestEvent},
5568 @internalsref{MultiMeasureTextEvent},
5569 @internalsref{MultiMeasureRestMusicGroup}, and
5570 @internalsref{MultiMeasureRest}.
5572 The layout object @internalsref{MultiMeasureRestNumber} is for the
5573 default number, and @internalsref{MultiMeasureRestText} for user
5578 It is not possible to use fingerings (e.g., @code{R1-4}) to put numbers
5579 over multi-measure rests. And the pitch of multi-measure rests (or
5580 staff-centered rests) can not be influenced.
5582 @cindex condensing rests
5584 There is no way to automatically condense multiple rests into a single
5585 multi-measure rest. Multi-measure rests do not take part in rest
5588 Be careful when entering multi-measure rests followed by whole
5589 notes. The following will enter two notes lasting four measures each
5593 When @code{skipBars} is set, the result will look OK, but the bar
5594 numbering will be off.
5596 @node Automatic part combining
5597 @subsection Automatic part combining
5598 @cindex automatic part combining
5599 @cindex part combiner
5602 Automatic part combining is used to merge two parts of music onto a
5603 staff. It is aimed at typesetting orchestral scores. When the two
5604 parts are identical for a period of time, only one is shown. In
5605 places where the two parts differ, they are typeset as separate
5606 voices, and stem directions are set automatically. Also, solo and
5607 @emph{a due} parts are identified and can be marked.
5609 The syntax for part combining is
5612 \partcombine @var{musicexpr1} @var{musicexpr2}
5617 The following example demonstrates the basic functionality of the part
5618 combiner: putting parts on one staff, and setting stem directions and
5621 @lilypond[quote,verbatim,raggedright,fragment]
5622 \new Staff \partcombine
5623 \relative g' { g g a( b) c c r r }
5624 \relative g' { g g r4 r e e g g }
5627 The first @code{g} appears only once, although it was
5628 specified twice (once in each part). Stem, slur, and tie directions are
5629 set automatically, depending whether there is a solo or unisono. The
5630 first part (with context called @code{one}) always gets up stems, and
5631 `Solo', while the second (called @code{two}) always gets down stems and
5634 If you just want the merging parts, and not the textual markings, you
5635 may set the property @code{printPartCombineTexts} to false
5637 @lilypond[quote,verbatim,raggedright,fragment,relative=2]
5639 \set Staff.printPartCombineTexts = ##f
5641 \relative g' { g a( b) r }
5642 \relative g' { g r4 r f }
5646 To change the text that is printed for solos or merging, you may
5647 set the @code{soloText}, @code{soloIIText}, and @code{aDueText}
5650 @lilypond[quote,verbatim,raggedright,fragment,relative=2]
5652 \set Score.soloText = #"ichi"
5653 \set Score.soloIIText = #"ni"
5654 \set Score.aDueText = #"tachi"
5656 \relative g' { g4 g a( b) r }
5657 \relative g' { g4 g r r f }
5661 Both arguments to @code{\partcombine} will be interpreted as
5662 @internalsref{Voice} contexts. If using relative octaves,
5663 @code{\relative} should be specified for both music expressions, i.e.,
5667 \relative @dots{} @var{musicexpr1}
5668 \relative @dots{} @var{musicexpr2}
5672 A @code{\relative} section that is outside of @code{\partcombine} has
5673 no effect on the pitches of @var{musicexpr1} and @var{musicexpr2}.
5677 Program reference: @internalsref{PartCombineMusic},
5678 @internalsref{SoloOneEvent}, and
5679 @internalsref{SoloTwoEvent}, and
5680 @internalsref{UnisonoEvent}.
5684 When @code{printPartCombineTexts} is set, when the two voices play the
5685 same notes on and off, the part combiner may typeset @code{a2} more
5686 than once in a measure.
5688 @code{\partcombine} cannot be inside @code{\times}.
5690 @code{\partcombine} cannot be inside @code{\relative}.
5692 Internally, the @code{\partcombine} interprets both arguments as
5693 @code{Voice}s named @code{one} and @code{two}, and then decides when
5694 the parts can be combined. Consequently, if the arguments switch to
5695 differently named @internalsref{Voice} contexts, the events in those
5699 @subsection Hiding staves
5701 @cindex Frenched scores
5702 @cindex Hiding staves
5704 In orchestral scores, staff lines that only have rests are usually
5705 removed. This saves some space. This style is called `French Score'.
5706 For @internalsref{Lyrics},
5707 @internalsref{ChordNames} and @internalsref{FiguredBass}, this is
5708 switched on by default. When the lines of these contexts turn out
5709 empty after the line-breaking process, they are removed.
5711 For normal staves, a specialized @internalsref{Staff} context is
5712 available, which does the same: staves containing nothing (or only
5713 multi-measure rests) are removed. The context definition is stored in
5714 @code{\RemoveEmptyStaffContext} variable. Observe how the second staff
5715 in this example disappears in the second line
5717 @lilypond[quote,raggedright,verbatim]
5719 \context { \RemoveEmptyStaffContext }
5724 \new Staff { e4 f g a \break c1 }
5725 \new Staff { c4 d e f \break R1 }
5730 The first system shows all staves in full. If empty staves should be
5731 removed from the first system too, set @code{remove-first} to false in
5732 @internalsref{RemoveEmptyVerticalGroup}.
5734 Another application is making ossia sections, i.e., alternative
5735 melodies on a separate piece of staff, with help of a Frenched
5736 staff. See @inputfileref{input/@/test,ossia@/.ly} for an example.
5739 @node Different editions from one source
5740 @subsection Different editions from one source
5743 The @code{\tag} command marks music expressions with a name. These
5744 tagged expressions can be filtered out later. With this mechanism it
5745 is possible to make different versions of the same music source.
5747 In the following example, we see two versions of a piece of music, one
5748 for the full score, and one with cue notes for the instrumental part
5764 The same can be applied to articulations, texts, etc.: they are
5767 -\tag #@var{your-tag}
5769 to an articulation, for example,
5774 This defines a note with a conditional fingering indication.
5777 @cindex removeWithTag
5778 By applying the @code{\keepWithTag} and @code{\removeWithTag}
5779 commands, tagged expressions can be filtered. For example,
5783 \keepWithTag #'score @var{the music}
5784 \keepWithTag #'part @var{the music}
5789 @lilypondfile[raggedright,quote]{tag-filter.ly}
5792 The argument of the @code{\tag} command should be a symbol, or a list
5793 of symbols, for example,
5795 \tag #'(original-part transposed-part) @dots{}
5802 Examples: @inputfileref{input/@/regression,tag@/-filter@/.ly}.
5806 Multiple rests are not merged if you create the score with both tagged
5810 @node Quoting other voices
5811 @subsection Quoting other voices
5813 With quotations, fragments of other parts can be inserted into a part
5814 directly. Before a part can be quoted, it must be marked especially as
5815 quotable. This is done with the @code{\addquote} command.
5818 \addquote @var{name} @var{music}
5823 Here, @var{name} is an identifying string. The @var{music} is any kind
5824 of music. Here is an example of @code{\addquote}
5827 \addquote clarinet \relative c' @{
5832 This command must be entered at toplevel, i.e., outside any music
5835 After calling @code{\addquote}, the quotation may then be done with
5836 @code{\quoteDuring} or @code{\cueDuring},
5839 \quoteDuring #@var{name} @var{music}
5842 During a part, a piece of music can be quoted with the @code{\quoteDuring}
5846 \quoteDuring #"clarinet" @{ s2. @}
5849 This would cite three quarter notes (the duration of @code{s2.}) of
5850 the previously added @code{clarinet} voice.
5853 More precisely, it takes the current time-step of the part being
5854 printed, and extracts the notes at the corresponding point of the
5855 @code{\addquote}d voice. Therefore, the argument to @code{\addquote}
5856 should be the entire part of the voice to be quoted, including any
5857 rests at the beginning.
5859 Quotations take into account the transposition of both source and target
5860 instruments, if they are specified using the @code{\transposition} command.
5862 @lilypond[quote,raggedright,verbatim]
5863 \addquote clarinet \relative c' {
5869 e'8 f'8 \quoteDuring #"clarinet" { s2 }
5873 The type of events that are present in cue notes can be trimmed with
5874 the @code{quotedEventTypes} property. The default value is
5875 @code{(note-event rest-event)}, which means that only notes and
5876 rests of the cued voice end up in the @code{\quoteDuring}.
5880 \set Staff.quotedEventTypes =
5881 #'(note-event articulation-event dynamic-event)
5885 will quote notes (but no rests), together with scripts and dynamics.
5889 Only the contents of the first @internalsref{Voice} occurring in an
5890 @code{\addquote} command will be considered for quotation, so
5891 @var{music} can not contain @code{\new} and @code{\context Voice}
5892 statements that would switch to a different Voice.
5894 Quoting grace notes is broken and can even cause LilyPond to crash.
5898 In this manual: @ref{Instrument transpositions}.
5900 Examples: @inputfileref{input/@/regression,quote@/.ly}
5901 @inputfileref{input/@/regression,quote@/-transposition@/.ly}
5903 Program reference: @internalsref{QuoteMusic}.
5905 @node Formatting cue notes
5906 @subsection Formatting cue notes
5908 The previous section deals with inserting notes from another voice.
5909 There is a more advanced music function called @code{\cueDuring},
5910 which makes formatting cue notes easier.
5915 \cueDuring #@var{name} #@var{updown} @var{music}
5918 This will insert notes from the part @var{name} into a
5919 @internalsref{Voice} called @code{cue}. This happens simultaneously
5920 with @var{music}, which usually is a rest. When the cue notes start,
5921 the staff in effect becomes polyphonic for a moment. The argument
5922 @var{updown} determines whether the cue notes should be notated as a
5923 first or second voice.
5926 @lilypond[verbatim,raggedright]
5929 \override Stem #'length = #5.5
5930 \override Beam #'thickness = #0.384
5931 \override Beam #'space-function =
5932 #(lambda (beam mult) (* 0.8 (Beam::space_function beam mult)))
5935 \addquote clarinet \relative {
5940 \new Staff \relative <<
5942 % setup a context for cue notes.
5943 \context Voice = cue { \smaller \skip 1*21 }
5945 \set Score.skipBars = ##t
5949 \cueDuring #"clarinet" #1 {
5958 Here are a couple of hints for successful cue notes
5962 Cue notes have smaller font sizes.
5964 the cued part is marked with the instrument playing the cue.
5966 when the original part takes over again, this should be marked with
5967 the name of the original instrument.
5969 @c really? Are you sure about that last point? I'll check after 3.0 -gp
5971 @c Yes, this is good practice. Otherwise, the start of the original
5972 @c part can only be seen from the font size. This is not good enough
5973 @c for sight-reading. It is possilbe to use other
5974 @c markers (eg. a big close-bracket over the staff) to indicate the cue notes are
5979 any other changes introduced by the cued part should also be
5980 undone. For example, if the cued instrument plays in a different clef,
5981 the original clef should be stated once again.
5989 @node Ancient notation
5990 @section Ancient notation
5992 @cindex Vaticana, Editio
5993 @cindex Medicaea, Editio
5998 Support for ancient notation includes features for mensural notation
5999 and Gregorian Chant notation. There is also limited support for
6000 figured bass notation.
6002 Many graphical objects provide a @code{style} property, see
6005 @ref{Ancient note heads},
6007 @ref{Ancient accidentals},
6009 @ref{Ancient rests},
6011 @ref{Ancient clefs},
6013 @ref{Ancient flags},
6015 @ref{Ancient time signatures}.
6018 By manipulating such a grob property, the typographical appearance of
6019 the affected graphical objects can be accommodated for a specific
6020 notation flavor without the need for introducing any new notational
6023 In addition to the standard articulation signs described in section
6024 @ref{Articulations}, specific articulation signs for ancient notation
6029 @ref{Ancient articulations}
6032 Other aspects of ancient notation can not that easily be expressed
6033 in terms of just changing a style property of a graphical object or
6034 adding articulation signs. Some notational concepts are introduced
6035 specifically for ancient notation,
6046 If this all is too much of documentation for you, and you just want to
6047 dive into typesetting without worrying too much about the details on
6048 how to customize a context, you may have a look at the predefined
6049 contexts. Use them to set up predefined style-specific voice and
6050 staff contexts, and directly go ahead with the note entry,
6054 @ref{Gregorian Chant contexts},
6056 @ref{Mensural contexts}.
6059 There is limited support for figured bass notation which came
6060 up during the baroque period.
6067 Here are all suptopics at a glance:
6070 * Ancient note heads::
6071 * Ancient accidentals::
6075 * Ancient time signatures::
6076 * Ancient articulations::
6080 * Gregorian Chant contexts::
6081 * Mensural contexts::
6086 @node Ancient note heads
6087 @subsection Ancient note heads
6092 For ancient notation, a note head style other than the @code{default}
6093 style may be chosen. This is accomplished by setting the @code{style}
6094 property of the @internalsref{NoteHead} object to @code{baroque},
6095 @code{neomensural} or @code{mensural}. The @code{baroque} style
6096 differs from the @code{default} style only in using a square shape
6097 for @code{\breve} note heads. The @code{neomensural} style differs from
6098 the @code{baroque} style in that it uses rhomboidal heads for whole notes
6099 and all smaller durations. Stems are centered on the note heads.
6100 This style is particularly useful when transcribing mensural music,
6101 e.g., for the incipit. The @code{mensural} style finally produces note
6102 heads that mimic the look of note heads in historic printings of the
6105 The following example demonstrates the @code{neomensural} style
6107 @lilypond[quote,fragment,raggedright,verbatim]
6108 \set Score.skipBars = ##t
6109 \override NoteHead #'style = #'neomensural
6110 a'\longa a'\breve a'1 a'2 a'4 a'8 a'16
6113 When typesetting a piece in Gregorian Chant notation, the
6114 @internalsref{Gregorian_ligature_engraver} will automatically select
6115 the proper note heads, so there is no need to explicitly set the
6116 note head style. Still, the note head style can be set, e.g., to
6117 @code{vaticana_punctum} to produce punctum neumes. Similarly, a
6118 @internalsref{Mensural_ligature_engraver} is used to automatically
6119 assemble mensural ligatures. See @ref{Ligatures} for how ligature
6124 Examples: @inputfileref{input/@/regression,note@/-head@/-style@/.ly} gives an
6125 overview over all available note head styles.
6128 @node Ancient accidentals
6129 @subsection Ancient accidentals
6134 Use the @code{style} property of grob @internalsref{Accidental} to
6135 select ancient accidentals. Supported styles are
6136 @code{mensural}, @code{vaticana}, @code{hufnagel}, and @code{medicaea}.
6138 @lilypond[quote,raggedright,staffsize=26]
6145 \line { " " \musicglyph #"accidentals-vaticana-1"
6146 " " \musicglyph #"accidentals-vaticana0" }
6150 \line { " " \musicglyph #"accidentals-medicaea-1" }
6154 \line { " " \musicglyph #"accidentals-hufnagel-1" }
6158 \line { " " \musicglyph #"accidentals-mensural-1"
6159 " " \musicglyph #"accidentals-mensural1" }
6165 \context { \Score \remove "Bar_number_engraver" }
6167 \remove "Clef_engraver"
6168 \remove "Key_engraver"
6169 \remove "Time_signature_engraver"
6170 \remove "Staff_symbol_engraver"
6171 minimumVerticalExtent = ##f
6177 As shown, not all accidentals are supported by each style. When
6178 trying to access an unsupported accidental, LilyPond will switch to a
6179 different style, as demonstrated in
6180 @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
6182 Similarly to local accidentals, the style of the key signature can be
6183 controlled by the @code{style} property of the
6184 @internalsref{KeySignature} grob.
6188 In this manual: @ref{Pitches}, @ref{Chromatic alterations} and
6189 @ref{Accidentals} give a general introduction of the use of
6190 accidentals. @ref{Key signature} gives a general introduction of
6191 the use of key signatures.
6193 Program reference: @internalsref{KeySignature}.
6195 Examples: @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
6198 @subsection Ancient rests
6203 Use the @code{style} property of grob @internalsref{Rest} to select
6204 ancient rests. Supported styles are @code{classical},
6205 @code{neomensural}, and @code{mensural}. @code{classical} differs
6206 from the @code{default} style only in that the quarter rest looks like
6207 a horizontally mirrored 8th rest. The @code{neomensural} style suits
6208 well for, e.g., the incipit of a transcribed mensural piece of music.
6209 The @code{mensural} style finally mimics the appearance of rests as
6210 in historic prints of the 16th century.
6212 The following example demonstrates the @code{neomensural} style
6214 @lilypond[quote,fragment,raggedright,verbatim]
6215 \set Score.skipBars = ##t
6216 \override Rest #'style = #'neomensural
6217 r\longa r\breve r1 r2 r4 r8 r16
6220 There are no 32th and 64th rests specifically for the mensural or
6221 neo-mensural style. Instead, the rests from the default style will be
6222 taken. See @inputfileref{input/@/test,rests@/.ly} for a chart of all
6225 There are no rests in Gregorian Chant notation; instead, it uses
6230 In this manual: @ref{Rests} gives a general introduction into the use of rests.
6234 @subsection Ancient clefs
6239 LilyPond supports a variety of clefs, many of them ancient.
6241 The following table shows all ancient clefs that are supported via the
6242 @code{\clef} command. Some of the clefs use the same glyph, but
6243 differ only with respect to the line they are printed on. In such
6244 cases, a trailing number in the name is used to enumerate these clefs.
6245 Still, you can manually force a clef glyph to be typeset on an
6246 arbitrary line, as described in @ref{Clef}. The note printed to the
6247 right side of each clef in the example column denotes the @code{c'}
6248 with respect to that clef.
6250 @multitable @columnfractions .4 .4 .2
6259 modern style mensural C clef
6261 @code{neomensural-c1}, @code{neomensural-c2},@*
6262 @code{neomensural-c3}, @code{neomensural-c4}
6264 @lilypond[fragment,relative=1,notime]
6265 \clef "neomensural-c2" c
6269 petrucci style mensural C clefs, for use on different staff lines
6270 (the examples show the 2nd staff line C clef)
6272 @code{petrucci-c1}, @code{petrucci-c2},@*
6273 @code{petrucci-c3}, @code{petrucci-c4},@*
6276 @lilypond[fragment,relative=1,notime]
6277 \clef "petrucci-c2" c
6281 petrucci style mensural F clef
6285 @lilypond[fragment,relative=1,notime]
6286 \clef "petrucci-f" c
6290 petrucci style mensural G clef
6294 @lilypond[fragment,relative=1,notime]
6295 \clef "petrucci-g" c
6299 historic style mensural C clef
6301 @code{mensural-c1}, @code{mensural-c2},@*
6302 @code{mensural-c3}, @code{mensural-c4}
6304 @lilypond[fragment,relative=1,notime]
6305 \clef "mensural-c2" c
6309 historic style mensural F clef
6313 @lilypond[fragment,relative=1,notime]
6314 \clef "mensural-f" c
6318 historic style mensural G clef
6322 @lilypond[fragment,relative=1,notime]
6323 \clef "mensural-g" c
6327 Editio Vaticana style do clef
6329 @code{vaticana-do1}, @code{vaticana-do2},@*
6332 @lilypond[fragment,relative=1,notime]
6333 \override Staff.StaffSymbol #'line-count = #4
6334 \clef "vaticana-do2" c
6338 Editio Vaticana style fa clef
6340 @code{vaticana-fa1}, @code{vaticana-fa2}
6342 @lilypond[fragment,relative=1,notime]
6343 \override Staff.StaffSymbol #'line-count = #4
6344 \clef "vaticana-fa2" c
6348 Editio Medicaea style do clef
6350 @code{medicaea-do1}, @code{medicaea-do2},@*
6353 @lilypond[fragment,relative=1,notime]
6354 \override Staff.StaffSymbol #'line-count = #4
6355 \clef "medicaea-do2" c
6359 Editio Medicaea style fa clef
6361 @code{medicaea-fa1}, @code{medicaea-fa2}
6363 @lilypond[fragment,relative=1,notime]
6364 \override Staff.StaffSymbol #'line-count = #4
6365 \clef "medicaea-fa2" c
6369 historic style hufnagel do clef
6371 @code{hufnagel-do1}, @code{hufnagel-do2},@*
6374 @lilypond[fragment,relative=1,notime]
6375 \override Staff.StaffSymbol #'line-count = #4
6376 \clef "hufnagel-do2" c
6380 historic style hufnagel fa clef
6382 @code{hufnagel-fa1}, @code{hufnagel-fa2}
6384 @lilypond[fragment,relative=1,notime]
6385 \override Staff.StaffSymbol #'line-count = #4
6386 \clef "hufnagel-fa2" c
6390 historic style hufnagel combined do/fa clef
6392 @code{hufnagel-do-fa}
6394 @lilypond[fragment,relative=1,notime]
6395 \clef "hufnagel-do-fa" c
6401 @emph{Modern style} means ``as is typeset in contemporary editions of
6402 transcribed mensural music''.
6404 @emph{Petrucci style} means ``inspired by printings published by the
6405 famous engraver Petrucci (1466-1539)''.
6407 @emph{Historic style} means ``as was typeset or written in historic
6408 editions (other than those of Petrucci)''.
6410 @emph{Editio XXX style} means ``as is/was printed in Editio XXX''.
6412 Petrucci used C clefs with differently balanced left-side vertical
6413 beams, depending on which staff line it is printed.
6417 In this manual: see @ref{Clef}.
6421 The mensural g clef is mapped to the Petrucci g clef.
6426 @subsection Ancient flags
6431 Use the @code{flag-style} property of grob @internalsref{Stem} to
6432 select ancient flags. Besides the @code{default} flag style,
6433 only the @code{mensural} style is supported
6435 @lilypond[quote,fragment,raggedright,verbatim]
6436 \override Stem #'flag-style = #'mensural
6437 \override Stem #'thickness = #1.0
6438 \override NoteHead #'style = #'mensural
6440 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
6441 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
6444 Note that the innermost flare of each mensural flag always is
6445 vertically aligned with a staff line.
6447 There is no particular flag style for neo-mensural notation. Hence,
6448 when typesetting the incipit of a transcribed piece of mensural
6449 music, the default flag style should be used. There are no flags in
6450 Gregorian Chant notation.
6454 The attachment of ancient flags to stems is slightly off due to a
6455 change in early 2.3.x.
6457 Vertically aligning each flag with a staff line assumes that stems
6458 always end either exactly on or exactly in the middle between two
6459 staff lines. This may not always be true when using advanced layout
6460 features of classical notation (which however are typically out of
6461 scope for mensural notation).
6463 @node Ancient time signatures
6464 @subsection Ancient time signatures
6466 @cindex time signatures
6469 There is limited support for mensural time signatures. The
6470 glyphs are hard-wired to particular time fractions. In other words,
6471 to get a particular mensural signature glyph with the @code{\time n/m}
6472 command, @code{n} and @code{m} have to be chosen according to the
6475 @lilypond[quote,raggedright]
6479 \remove Staff_symbol_engraver
6480 \remove Clef_engraver
6481 \remove Time_signature_engraver
6484 \set Score.timing = ##f
6485 \set Score.barAlways = ##t
6486 s_\markup { "$\\backslash$time 4/4" }
6487 ^\markup { " " \musicglyph #"timesig-neomensural4/4" }
6489 s_\markup { "$\\backslash$time 2/2" }
6490 ^\markup { " " \musicglyph #"timesig-neomensural2/2" }
6492 s_\markup { "$\\backslash$time 6/4" }
6493 ^\markup { " " \musicglyph #"timesig-neomensural6/4" }
6495 s_\markup { "$\\backslash$time 6/8" }
6496 ^\markup { " " \musicglyph #"timesig-neomensural6/8" }
6498 s_\markup { "$\\backslash$time 3/2" }
6499 ^\markup { " " \musicglyph #"timesig-neomensural3/2" }
6501 s_\markup { "$\\backslash$time 3/4" }
6502 ^\markup { " " \musicglyph #"timesig-neomensural3/4" }
6504 s_\markup { "$\\backslash$time 9/4" }
6505 ^\markup { " " \musicglyph #"timesig-neomensural9/4" }
6507 s_\markup { "$\\backslash$time 9/8" }
6508 ^\markup { " " \musicglyph #"timesig-neomensural9/8" }
6510 s_\markup { "$\\backslash$time 4/8" }
6511 ^\markup { " " \musicglyph #"timesig-neomensural4/8" }
6513 s_\markup { "$\\backslash$time 2/4" }
6514 ^\markup { " " \musicglyph #"timesig-neomensural2/4" }
6518 Use the @code{style} property of grob @internalsref{TimeSignature} to
6519 select ancient time signatures. Supported styles are
6520 @code{neomensural} and @code{mensural}. The above table uses the
6521 @code{neomensural} style. This style is appropriate for the
6522 incipit of transcriptions of mensural pieces. The @code{mensural}
6523 style mimics the look of historical printings of the 16th century.
6525 The following examples show the differences in style,
6527 @lilypond[raggedright,fragment,relative=1,quote]
6531 c1^\markup { \hspace #-2.0 \typewriter default }
6533 \override Staff.TimeSignature #'style = #'numbered
6535 c1^\markup { \hspace #-2.0 \typewriter numbered }
6537 \override Staff.TimeSignature #'style = #'mensural
6539 c1^\markup { \hspace #-2.0 \typewriter mensural }
6541 \override Staff.TimeSignature #'style = #'neomensural
6543 c1^\markup { \hspace #-2.0 \typewriter neomensural }
6544 \override Staff.TimeSignature #'style = #'single-digit
6546 c1^\markup { \hspace #-2.0 \typewriter single-digit }
6552 This manual: @ref{Time signature} gives a general introduction to
6553 the use of time signatures.
6557 Ratios of note durations do not change with the time signature. For
6558 example, the ratio of 1 brevis = 3 semibrevis (tempus perfectum) must
6559 be made by hand, by setting
6562 breveTP = #(ly:make-duration -1 0 3 2)
6568 This sets @code{breveTP} to 3/2 times 2 = 3 times a whole note.
6570 The @code{old6/8alt} symbol (an alternate symbol for 6/8) is not
6571 addressable with @code{\time}. Use a @code{\markup} instead
6573 @node Ancient articulations
6574 @subsection Ancient articulations
6576 @cindex articulations
6578 In addition to the standard articulation signs described in section
6579 @ref{Articulations}, articulation signs for ancient notation are
6580 provided. These are specifically designed for use with notation in
6581 Editio Vaticana style.
6583 @lilypond[quote,raggedright,verbatim]
6584 \include "gregorian-init.ly"
6586 \context VaticanaVoice {
6587 \override TextScript #'font-family = #'typewriter
6588 \override TextScript #'font-shape = #'upright
6589 \override Script #'padding = #-0.1
6591 a4\circulus_"circulus" s1
6592 a4\semicirculus_"semicirculus" s1 s
6593 a4\accentus_"accentus" s1
6594 \[ a4_"episem" \episemInitium \pes b \flexa a \episemFinis \]
6601 Some articulations are vertically placed too closely to the
6602 correpsonding note heads.
6605 @subsection Custodes
6610 A @emph{custos} (plural: @emph{custodes}; Latin word for `guard') is a
6611 symbol that appears at the end of a staff. It anticipates the pitch
6612 of the first note(s) of the following line thus helping the performer
6613 to manage line breaks during performance.
6615 Custodes were frequently used in music notation until the 17th
6616 century. Nowadays, they have survived only in a few particular forms
6617 of musical notation such as contemporary editions of Gregorian chant
6618 like the @emph{editio vaticana}. There are different custos glyphs
6619 used in different flavors of notational style.
6621 For typesetting custodes, just put a @internalsref{Custos_engraver} into the
6622 @internalsref{Staff} context when declaring the @code{\layout} block,
6623 as shown in the following example
6629 \consists Custos_engraver
6630 Custos \override #'style = #'mensural
6635 The result looks like this
6637 @lilypond[quote,raggedright]
6641 \override Staff.Custos #'style = #'mensural
6646 \context { \Staff \consists Custos_engraver }
6651 The custos glyph is selected by the @code{style} property. The styles
6652 supported are @code{vaticana}, @code{medicaea}, @code{hufnagel}, and
6653 @code{mensural}. They are demonstrated in the following fragment
6655 @lilypond[quote,raggedright,fragment]
6656 \new Lyrics \lyricmode {
6658 \typewriter "vaticana"
6659 \line { " " \musicglyph #"custodes-vaticana-u0" }
6662 \typewriter "medicaea"
6663 \line { " " \musicglyph #"custodes-medicaea-u0" }
6666 \typewriter "hufnagel"
6667 \line { " " \musicglyph #"custodes-hufnagel-u0" }
6670 \typewriter "mensural"
6671 \line { " " \musicglyph #"custodes-mensural-u0" }
6678 Program reference: @internalsref{Custos}.
6680 Examples: @inputfileref{input/@/regression,custos@/.ly}.
6684 @subsection Divisiones
6690 A @emph{divisio} (plural: @emph{divisiones}; Latin word for
6691 `division') is a staff context symbol that is used to structure
6692 Gregorian music into phrases and sections. The musical meaning of
6693 @emph{divisio minima}, @emph{divisio maior}, and @emph{divisio maxima}
6694 can be characterized as short, medium, and long pause, somewhat like
6695 the breathmarks from @ref{Breath marks}. The @emph{finalis} sign not
6696 only marks the end of a chant, but is also frequently used within a
6697 single antiphonal/responsorial chant to mark the end of each section.
6700 To use divisiones, include the file @file{gregorian@/-init@/.ly}. It
6701 contains definitions that you can apply by just inserting
6702 @code{\divisioMinima}, @code{\divisioMaior}, @code{\divisioMaxima},
6703 and @code{\finalis} at proper places in the input. Some editions use
6704 @emph{virgula} or @emph{caesura} instead of divisio minima.
6705 Therefore, @file{gregorian@/-init@/.ly} also defines @code{\virgula} and
6708 @lilypondfile[quote,raggedright]{divisiones.ly}
6712 @cindex @code{\virgula}
6714 @cindex @code{\caesura}
6716 @cindex @code{\divisioMinima}
6717 @code{\divisioMinima},
6718 @cindex @code{\divisioMaior}
6719 @code{\divisioMaior},
6720 @cindex @code{\divisioMaxima}
6721 @code{\divisioMaxima},
6722 @cindex @code{\finalis}
6727 In this manual: @ref{Breath marks}.
6729 Program reference: @internalsref{BreathingSign}, @internalsref{BreathingSignEvent}.
6731 Examples: @inputfileref{input/@/test,divisiones@/.ly}.
6734 @subsection Ligatures
6738 @c TODO: Should double check if I recalled things correctly when I wrote
6739 @c down the following paragraph by heart.
6741 A ligature is a graphical symbol that represents at least two distinct
6742 notes. Ligatures originally appeared in the manuscripts of Gregorian
6743 chant notation to denote ascending or descending sequences of notes.
6745 Ligatures are entered by enclosing them in @code{\[} and @code{\]}.
6746 Some ligature styles may need additional input syntax specific for
6747 this particular type of ligature. By default, the
6748 @internalsref{LigatureBracket} engraver just puts a square bracket
6751 @lilypond[quote,raggedright,verbatim]
6759 To select a specific style of ligatures, a proper ligature engraver
6760 has to be added to the @internalsref{Voice} context, as explained in
6761 the following subsections. Only white mensural ligatures
6762 are supported with certain limitations.
6768 Ligatures need special spacing that has not yet been implemented. As
6769 a result, there is too much space between ligatures most of the time,
6770 and line breaking often is unsatisfactory. Also, lyrics do not
6771 correctly align with ligatures.
6773 Accidentals must not be printed within a ligature, but instead need to
6774 be collected and printed in front of it.
6776 Augmentum dots within ligatures are not handled correctly.
6780 * White mensural ligatures::
6781 * Gregorian square neumes ligatures::
6784 @node White mensural ligatures
6785 @subsubsection White mensural ligatures
6787 @cindex Mensural ligatures
6788 @cindex White mensural ligatures
6790 There is limited support for white mensural ligatures.
6792 To engrave white mensural ligatures, in the layout block put the
6793 @internalsref{Mensural_ligature_engraver} into the
6794 @internalsref{Voice} context, and remove the
6795 @internalsref{Ligature_bracket_engraver}, like this
6801 \remove Ligature_bracket_engraver
6802 \consists Mensural_ligature_engraver
6807 There is no additional input language to describe the shape of a
6808 white mensural ligature. The shape is rather determined solely from
6809 the pitch and duration of the enclosed notes. While this approach may
6810 take a new user a while to get accustomed to, it has the great advantage
6811 that the full musical information of the ligature is known internally.
6812 This is not only required for correct MIDI output, but also allows for
6813 automatic transcription of the ligatures.
6818 \set Score.timing = ##f
6819 \set Score.defaultBarType = "empty"
6820 \override NoteHead #'style = #'neomensural
6821 \override Staff.TimeSignature #'style = #'neomensural
6823 \[ g\longa c\breve a\breve f\breve d'\longa \]
6825 \[ e1 f1 a\breve g\longa \]
6827 @lilypond[quote,raggedright]
6830 \set Score.timing = ##f
6831 \set Score.defaultBarType = "empty"
6832 \override NoteHead #'style = #'neomensural
6833 \override Staff.TimeSignature #'style = #'neomensural
6835 \[ g\longa c\breve a\breve f\breve d'\longa \]
6837 \[ e1 f1 a\breve g\longa \]
6842 \remove Ligature_bracket_engraver
6843 \consists Mensural_ligature_engraver
6849 Without replacing @internalsref{Ligature_bracket_engraver} with
6850 @internalsref{Mensural_ligature_engraver}, the same music transcribes
6853 @lilypond[quote,raggedright]
6855 \set Score.timing = ##f
6856 \set Score.defaultBarType = "empty"
6857 \override NoteHead #'style = #'neomensural
6858 \override Staff.TimeSignature #'style = #'neomensural
6860 \[ g\longa c\breve a\breve f\breve d'\longa \]
6862 \[ e1 f1 a\breve g\longa \]
6868 The implementation is experimental. It may output strange warnings,
6869 incorrect results, and might even crash on more complex ligatures.
6871 @node Gregorian square neumes ligatures
6872 @subsubsection Gregorian square neumes ligatures
6874 @cindex Square neumes ligatures
6875 @cindex Gregorian square neumes ligatures
6877 There is limited support for Gregorian square neumes notation
6878 (following the style of the Editio Vaticana). Core ligatures can
6879 already be typeset, but essential issues for serious typesetting are
6880 still lacking, such as (among others) horizontal alignment of multiple
6881 ligatures, lyrics alignment and proper handling of accidentals.
6884 The following table contains the extended neumes table of the 2nd
6885 volume of the Antiphonale Romanum (@emph{Liber Hymnarius}), published
6886 1983 by the monks of Solesmes.
6888 @multitable @columnfractions .4 .2 .2 .2
6905 @c TODO: \layout block is identical in all of the below examples.
6906 @c Therefore, it should somehow be included rather than duplicated all
6909 @c why not make identifiers in ly/engraver-init.ly? --hwn
6911 @c Because it's just used to typeset plain notes without
6912 @c a staff for demonstration purposes rather than something
6913 @c special of Gregorian chant notation. --jr
6918 @lilypond[staffsize=26,linewidth=1.5\cm]
6919 \include "gregorian-init.ly"
6924 \noBreak s^\markup {"a"} \noBreak
6926 % Punctum Inclinatum
6928 \noBreak s^\markup {"b"}
6930 \layout { \neumeDemoLayout }}
6933 @lilypond[staffsize=26,linewidth=2.5\cm]
6934 \include "gregorian-init.ly"
6937 % Punctum Auctum Ascendens
6938 \[ \auctum \ascendens b \]
6939 \noBreak s^\markup {"c"} \noBreak
6941 % Punctum Auctum Descendens
6942 \[ \auctum \descendens b \]
6943 \noBreak s^\markup {"d"} \noBreak
6945 % Punctum Inclinatum Auctum
6946 \[ \inclinatum \auctum b \]
6947 \noBreak s^\markup {"e"}
6949 \layout { \neumeDemoLayout }}
6952 @lilypond[staffsize=26,linewidth=1.0\cm]
6953 \include "gregorian-init.ly"
6956 % Punctum Inclinatum Parvum
6957 \[ \inclinatum \deminutum b \]
6958 \noBreak s^\markup {"f"}
6960 \layout { \neumeDemoLayout }}
6966 @lilypond[staffsize=26,linewidth=1.0\cm]
6967 \include "gregorian-init.ly"
6972 \noBreak s^\markup {"g"}
6974 \layout { \neumeDemoLayout }}
6980 @code{3. Apostropha vel Stropha}
6982 @lilypond[staffsize=26,linewidth=1.0\cm]
6983 \include "gregorian-init.ly"
6988 \noBreak s^\markup {"h"}
6990 \layout { \neumeDemoLayout }}
6993 @lilypond[staffsize=26,linewidth=1.0\cm]
6994 \include "gregorian-init.ly"
6998 \[ \stropha \auctum b \]
6999 \noBreak s^\markup {"i"}
7001 \layout { \neumeDemoLayout }}
7008 @lilypond[staffsize=26,linewidth=1.0\cm]
7009 \include "gregorian-init.ly"
7014 \noBreak s^\markup {"j"}
7016 \layout { \neumeDemoLayout }}
7022 @code{5. Clivis vel Flexa}
7024 @lilypond[staffsize=26,linewidth=1.0\cm]
7025 \include "gregorian-init.ly"
7032 \layout { \neumeDemoLayout }}
7035 @lilypond[staffsize=26,linewidth=2.0\cm]
7036 \include "gregorian-init.ly"
7039 % Clivis Aucta Descendens
7040 \[ b \flexa \auctum \descendens g \]
7041 \noBreak s^\markup {"l"} \noBreak
7043 % Clivis Aucta Ascendens
7044 \[ b \flexa \auctum \ascendens g \]
7045 \noBreak s^\markup {"m"}
7047 \layout { \neumeDemoLayout }}
7050 @lilypond[staffsize=26,linewidth=1.0\cm]
7051 \include "gregorian-init.ly"
7055 \[ b \flexa \deminutum g \]
7058 \layout { \neumeDemoLayout }}
7062 @code{6. Podatus vel Pes}
7064 @lilypond[staffsize=26,linewidth=1.0\cm]
7065 \include "gregorian-init.ly"
7072 \layout { \neumeDemoLayout }}
7075 @lilypond[staffsize=26,linewidth=2.0\cm]
7076 \include "gregorian-init.ly"
7079 % Pes Auctus Descendens
7080 \[ g \pes \auctum \descendens b \]
7081 \noBreak s^\markup {"p"} \noBreak
7083 % Pes Auctus Ascendens
7084 \[ g \pes \auctum \ascendens b \]
7085 \noBreak s^\markup {"q"}
7087 \layout { \neumeDemoLayout }}
7090 @lilypond[staffsize=26,linewidth=1.0\cm]
7091 \include "gregorian-init.ly"
7095 \[ g \pes \deminutum b \]
7098 \layout { \neumeDemoLayout }}
7102 @code{7. Pes Quassus}
7104 @lilypond[staffsize=26,linewidth=1.0\cm]
7105 \include "gregorian-init.ly"
7109 \[ \oriscus g \pes \virga b \]
7112 \layout { \neumeDemoLayout }}
7115 @lilypond[staffsize=26,linewidth=1.0\cm]
7116 \include "gregorian-init.ly"
7119 % Pes Quassus Auctus Descendens
7120 \[ \oriscus g \pes \auctum \descendens b \]
7123 \layout { \neumeDemoLayout }}
7128 @code{8. Quilisma Pes}
7130 @lilypond[staffsize=26,linewidth=1.0\cm]
7131 \include "gregorian-init.ly"
7135 \[ \quilisma g \pes b \]
7138 \layout { \neumeDemoLayout }}
7141 @lilypond[staffsize=26,linewidth=1.0\cm]
7142 \include "gregorian-init.ly"
7145 % Quilisma Pes Auctus Descendens
7146 \[ \quilisma g \pes \auctum \descendens b \]
7149 \layout { \neumeDemoLayout }}
7154 @code{9. Podatus Initio Debilis}
7156 @lilypond[staffsize=26,linewidth=1.0\cm]
7157 \include "gregorian-init.ly"
7160 % Pes Initio Debilis
7161 \[ \deminutum g \pes b \]
7164 \layout { \neumeDemoLayout }}
7167 @lilypond[staffsize=26,linewidth=1.0\cm]
7168 \include "gregorian-init.ly"
7171 % Pes Auctus Descendens Initio Debilis
7172 \[ \deminutum g \pes \auctum \descendens b \]
7175 \layout { \neumeDemoLayout }}
7182 @lilypond[staffsize=26,linewidth=1.0\cm]
7183 \include "gregorian-init.ly"
7187 \[ a \pes b \flexa g \]
7190 \layout { \neumeDemoLayout }}
7193 @lilypond[staffsize=26,linewidth=1.0\cm]
7194 \include "gregorian-init.ly"
7197 % Torculus Auctus Descendens
7198 \[ a \pes b \flexa \auctum \descendens g \]
7201 \layout { \neumeDemoLayout }}
7204 @lilypond[staffsize=26,linewidth=1.0\cm]
7205 \include "gregorian-init.ly"
7208 % Torculus Deminutus
7209 \[ a \pes b \flexa \deminutum g \]
7212 \layout { \neumeDemoLayout }}
7216 @code{11. Torculus Initio Debilis}
7218 @lilypond[staffsize=26,linewidth=1.0\cm]
7219 \include "gregorian-init.ly"
7222 % Torculus Initio Debilis
7223 \[ \deminutum a \pes b \flexa g \]
7226 \layout { \neumeDemoLayout }}
7229 @lilypond[staffsize=26,linewidth=1.0\cm]
7230 \include "gregorian-init.ly"
7233 % Torculus Auctus Descendens Initio Debilis
7234 \[ \deminutum a \pes b \flexa \auctum \descendens g \]
7237 \layout { \neumeDemoLayout }}
7240 @lilypond[staffsize=26,linewidth=1.0\cm]
7241 \include "gregorian-init.ly"
7244 % Torculus Deminutus Initio Debilis
7245 \[ \deminutum a \pes b \flexa \deminutum g \]
7248 \layout { \neumeDemoLayout }}
7252 @code{12. Porrectus}
7254 @lilypond[staffsize=26,linewidth=1.0\cm]
7255 \include "gregorian-init.ly"
7259 \[ a \flexa g \pes b \]
7262 \layout { \neumeDemoLayout }}
7265 @lilypond[staffsize=26,linewidth=1.0\cm]
7266 \include "gregorian-init.ly"
7269 % Porrectus Auctus Descendens
7270 \[ a \flexa g \pes \auctum \descendens b \]
7273 \layout { \neumeDemoLayout }}
7276 @lilypond[staffsize=26,linewidth=1.0\cm]
7277 \include "gregorian-init.ly"
7280 % Porrectus Deminutus
7281 \[ a \flexa g \pes \deminutum b \]
7284 \layout { \neumeDemoLayout }}
7290 @lilypond[staffsize=26,linewidth=1.0\cm]
7291 \include "gregorian-init.ly"
7295 \[ \virga b \inclinatum a \inclinatum g \]
7298 \layout { \neumeDemoLayout }
7302 @lilypond[staffsize=26,linewidth=1.0\cm]
7303 \include "gregorian-init.ly"
7307 \[ \virga b \inclinatum a \inclinatum \auctum g \]
7310 \layout { \neumeDemoLayout }}
7313 @lilypond[staffsize=26,linewidth=1.0\cm]
7314 \include "gregorian-init.ly"
7317 % Climacus Deminutus
7318 \[ \virga b \inclinatum a \inclinatum \deminutum g \]
7321 \layout { \neumeDemoLayout }}
7325 @code{14. Scandicus}
7327 @lilypond[staffsize=26,linewidth=1.0\cm]
7328 \include "gregorian-init.ly"
7332 \[ g \pes a \virga b \]
7335 \layout { \neumeDemoLayout }}
7338 @lilypond[staffsize=26,linewidth=1.0\cm]
7339 \include "gregorian-init.ly"
7342 % Scandicus Auctus Descendens
7343 \[ g \pes a \pes \auctum \descendens b \]
7346 \layout { \neumeDemoLayout }}
7349 @lilypond[staffsize=26,linewidth=1.0\cm]
7350 \include "gregorian-init.ly"
7353 % Scandicus Deminutus
7354 \[ g \pes a \pes \deminutum b \]
7357 \layout { \neumeDemoLayout }}
7363 @lilypond[staffsize=26,linewidth=1.0\cm]
7364 \include "gregorian-init.ly"
7368 \[ g \oriscus a \pes \virga b \]
7371 \layout { \neumeDemoLayout }}
7374 @lilypond[staffsize=26,linewidth=1.0\cm]
7375 \include "gregorian-init.ly"
7378 % Salicus Auctus Descendens
7379 \[ g \oriscus a \pes \auctum \descendens b \]
7382 \layout { \neumeDemoLayout }}
7389 @lilypond[staffsize=26,linewidth=1.0\cm]
7390 \include "gregorian-init.ly"
7394 \[ \stropha b \stropha b \stropha a \]
7397 \layout { \neumeDemoLayout }
7406 Unlike most other neumes notation systems, the input language for
7407 neumes does not reflect the typographical appearance, but is designed
7408 to focus on musical meaning. For example, @code{\[ a \pes b
7409 \flexa g \]} produces a Torculus consisting of three Punctum heads,
7410 while @code{\[ a \flexa g \pes b \]} produces a Porrectus with a
7411 curved flexa shape and only a single Punctum head. There is no
7412 command to explicitly typeset the curved flexa shape; the decision of
7413 when to typeset a curved flexa shape is based on the musical
7414 input. The idea of this approach is to separate the musical aspects
7415 of the input from the notation style of the output. This way, the
7416 same input can be reused to typeset the same music in a different
7417 style of Gregorian chant notation.
7419 The following table shows the code fragments that produce the
7420 ligatures in the above neumes table. The letter in the first column
7421 in each line of the below table indicates to which ligature in the
7422 above table it refers. The second column gives the name of the
7423 ligature. The third column shows the code fragment that produces this
7424 ligature, using @code{g}, @code{a}, and @code{b} as example pitches.
7426 @multitable @columnfractions .02 .31 .67
7446 @code{\[ \inclinatum b \]}
7454 @code{\[ \auctum \ascendens b \]}
7462 @code{\[ \auctum \descendens b \]}
7467 Punctum Inclinatum@*
7470 @code{\[ \inclinatum \auctum b \]}
7475 Punctum Inclinatum@*
7477 @code{\[ \inclinatum \deminutum b \]}
7484 @code{\[ \virga b \]}
7491 @code{\[ \stropha b \]}
7498 @code{\[ \stropha \auctum b \]}
7505 @code{\[ \oriscus b \]}
7512 @code{\[ b \flexa g \]}
7520 @code{\[ b \flexa \auctum \descendens g \]}
7528 @code{\[ b \flexa \auctum \ascendens g \]}
7535 @code{\[ b \flexa \deminutum g \]}
7542 @code{\[ g \pes b \]}
7550 @code{\[ g \pes \auctum \descendens b \]}
7558 @code{\[ g \pes \auctum \ascendens b \]}
7565 @code{\[ g \pes \deminutum b \]}
7572 @code{\[ \oriscus g \pes \virga b \]}
7578 Auctus Descendens @tab
7579 @code{\[ \oriscus g \pes \auctum \descendens b \]}
7586 @code{\[ \quilisma g \pes b \]}
7594 @code{\[ \quilisma g \pes \auctum \descendens b \]}
7601 @code{\[ \deminutum g \pes b \]}
7606 Pes Auctus Descendens@*
7609 @code{\[ \deminutum g \pes \auctum \descendens b \]}
7616 @code{\[ a \pes b \flexa g \]}
7624 @code{\[ a \pes b \flexa \auctum \descendens g \]}
7631 @code{\[ a \pes b \flexa \deminutum g \]}
7636 Torculus Initio Debilis
7638 @code{\[ \deminutum a \pes b \flexa g \]}
7644 Descendens Initio Debilis
7646 @code{\[ \deminutum a \pes b \flexa \auctum \descendens g \]}
7651 Torculus Deminutus@*
7654 @code{\[ \deminutum a \pes b \flexa \deminutum g \]}
7661 @code{\[ a \flexa g \pes b \]}
7669 @code{\[ a \flexa g \pes \auctum \descendens b \]}
7676 @code{\[ a \flexa g \pes \deminutum b \]}
7683 @code{\[ \virga b \inclinatum a \inclinatum g \]}
7690 @code{\[ \virga b \inclinatum a \inclinatum \auctum g \]}
7697 @code{\[ \virga b \inclinatum a \inclinatum \deminutum g \]}
7704 @code{\[ g \pes a \virga b \]}
7712 @code{\[ g \pes a \pes \auctum \descendens b \]}
7719 @code{\[ g \pes a \pes \deminutum b \]}
7726 @code{\[ g \oriscus a \pes \virga b \]}
7731 Salicus Auctus Descendens
7733 @code{\[ g \oriscus a \pes \auctum \descendens b \]}
7740 @code{\[ \stropha b \stropha b \stropha a \]}
7745 The following head prefixes are supported
7747 @cindex @code{\virga}
7749 @cindex @code{\stropha}
7751 @cindex @code{\inclinatum}
7753 @cindex @code{\auctum}
7755 @cindex @code{\descendens}
7757 @cindex @code{\ascendens}
7759 @cindex @code{\oriscus}
7761 @cindex @code{\quilisma}
7763 @cindex @code{\deminutum}
7766 Head prefixes can be accumulated, though restrictions apply. For
7767 example, either @code{\descendens} or @code{\ascendens} can be applied
7768 to a head, but not both to the same head.
7771 @cindex @code{\flexa}
7772 Two adjacent heads can be tied together with the @code{\pes} and
7773 @code{\flexa} infix commands for a rising and falling line of melody,
7778 @node Gregorian Chant contexts
7779 @subsection Gregorian Chant contexts
7781 @cindex VaticanaVoiceContext
7782 @cindex VaticanaStaffContext
7784 The predefined @code{VaticanaVoiceContext} and
7785 @code{VaticanaStaffContext} can be used to engrave a piece of
7786 Gregorian Chant in the style of the Editio Vaticana. These contexts
7787 initialize all relevant context properties and grob properties to
7788 proper values, so you can immediately go ahead entering the chant, as
7789 the following excerpt demonstrates
7791 @lilypond[quote,raggedright,verbatim]
7792 \include "gregorian-init.ly"
7795 \context VaticanaVoice = "cantus" {
7796 \override Score.BarNumber #'transparent = ##t {
7797 \[ c'\melisma c' \flexa a \]
7798 \[ a \flexa \deminutum g\melismaEnd \]
7800 \[ f\melisma \pes a c' c' \pes d'\melismaEnd \]
7801 c' \divisioMinima \break
7802 \[ c'\melisma c' \flexa a \]
7803 \[ a \flexa \deminutum g\melismaEnd \] f \divisioMinima
7806 \lyricsto "cantus" \new Lyrics {
7807 San- ctus, San- ctus, San- ctus
7814 @node Mensural contexts
7815 @subsection Mensural contexts
7817 @cindex MensuralVoiceContext
7818 @cindex MensuralStaffContext
7820 The predefined @code{MensuralVoiceContext} and
7821 @code{MensuralStaffContext} can be used to engrave a piece in mensural
7822 style. These contexts initialize all relevant context properties and
7823 grob properties to proper values, so you can immediately go ahead
7824 entering the chant, as the following excerpt demonstrates
7826 @lilypond[quote,raggedright,verbatim]
7829 \context MensuralVoice = "discantus" \transpose c c' {
7830 \override Score.BarNumber #'transparent = ##t {
7831 c'1\melisma bes a g\melismaEnd
7833 \[ f1\melisma a c'\breve d'\melismaEnd \]
7835 c'\breve\melisma a1 g1\melismaEnd
7836 fis\longa^\signumcongruentiae
7839 \lyricsto "discantus" \new Lyrics {
7840 San -- ctus, San -- ctus, San -- ctus
7848 @subsection Figured bass
7850 @cindex Basso continuo
7852 @c TODO: musicological blurb about FB
7855 LilyPond has limited support for figured bass
7857 @lilypond[quote,raggedright,verbatim,fragment]
7859 \context Voice { \clef bass dis4 c d ais g fis}
7860 \context FiguredBass \figuremode {
7861 < 6 >4 < 7 >8 < 6+ [_!] >
7868 The support for figured bass consists of two parts: there is an input
7869 mode, introduced by @code{\figuremode}, where you can enter bass figures
7870 as numbers, and there is a context called @internalsref{FiguredBass} that
7871 takes care of making @internalsref{BassFigure} objects.
7873 In figures input mode, a group of bass figures is delimited by
7874 @code{<} and @code{>}. The duration is entered after the @code{>}
7878 @lilypond[quote,raggedright,fragment]
7879 \context FiguredBass
7880 \figuremode { <4 6> }
7883 Accidentals are added when you append @code{-}, @code{!}, and @code{+}
7889 @lilypond[quote,raggedright,fragment]
7890 \context FiguredBass
7891 \figuremode { <4- 6+ 7!> }
7894 Spaces or dashes may be inserted by using @code{_}. Brackets are
7895 introduced with @code{[} and @code{]}
7900 @lilypond[quote,raggedright,fragment]
7901 \context FiguredBass
7902 \figuremode { < [4 6] 8 [_! 12] > }
7905 Although the support for figured bass may superficially resemble chord
7906 support, it works much simpler. The @code{\figuremode} mode simply
7907 stores the numbers and @internalsref{FiguredBass} context prints
7908 them as entered. There is no conversion to pitches and no
7909 realizations of the bass are played in the MIDI file.
7911 Internally, the code produces markup texts. You can use any of the
7912 markup text properties to override formatting. For example, the
7913 vertical spacing of the figures may be set with @code{baseline-skip}.
7917 Program reference: @internalsref{BassFigureEvent} music,
7918 @internalsref{BassFigure} object, and @internalsref{FiguredBass} context.
7922 Slash notation for alterations is not supported.
7924 @node Contemporary notation
7925 @section Contemporary notation
7927 In the 20th century, composers have greatly expanded the musical
7928 vocabulary. With this expansion, many innovations in musical notation
7929 have been tried. The book ``Music Notation in the 20th century'' by
7930 Kurt Stone gives a comprehensive overview (see @ref{Literature
7931 list}). In general, the use of new, innovative notation makes a piece
7932 harder to understand and perform and its use should therefore be
7933 avoided. For this reason, support for contemporary notation in
7934 LilyPond is limited.
7938 * Polymetric notation::
7940 * Special fermatas::
7944 @node Polymetric notation
7945 @subsection Polymetric notation
7947 Double time signatures are not supported explicitly, but they can be
7948 faked. In the next example, the markup for the time signature is
7949 created with a markup text. This markup text is inserted in the
7950 @internalsref{TimeSignature} grob.
7952 @lilypond[verbatim,raggedright]
7957 \musicglyph #"scripts-stopped"
7958 \bracket \column { "5" "8" }
7963 \override Staff.TimeSignature #'print-function = #Text_interface::print
7964 \override Staff.TimeSignature #'text = #tsMarkup
7966 c'2 \bar ":" c'4 c'4.
7970 Each staff can also have its own time signature. This is done by
7971 moving the @internalsref{Timing_engraver} to the @internalsref{Staff}
7976 \context @{ \Score \remove "Timing_engraver" @}
7977 \context @{ \Staff \consists "Timing_engraver" @}
7982 Now, each staff has its own time signature.
7995 c4. c8 c c c4. c8 c c
8000 @lilypond[quote,raggedright]
8002 \context{ \Score \remove "Timing_engraver" }
8003 \context{ \Staff \consists "Timing_engraver" }
8017 c4. c8 c c c4. c8 c c
8023 A different form of polymetric notation is where note lengths have
8024 different values across staves.
8026 This notation can be created by setting a common time signature for
8027 each staff but replacing it manually using
8028 @code{timeSignatureFraction} to the desired fraction. Then the printed
8029 durations in each staff are scaled to the common time signature.
8030 The latter is done with @code{\compressmusic}, which is similar to
8031 @code{\times}, but does not create a tuplet bracket.
8034 In this example, music with the time signatures of 3/4, 9/8, and 10/8 are
8035 used in parallel. In the second staff, shown durations are multiplied by
8036 2/3, so that 2/3 * 9/8 = 3/4, and in the third staff, shown durations are
8037 multiplied by 3/5, so that 3/5 * 10/8 = 3/4.
8039 @lilypond[quote,raggedright,verbatim,fragment]
8047 \set Staff.timeSignatureFraction = #'(9 . 8)
8048 \compressmusic #'(2 . 3)
8049 \repeat unfold 6 { c8[ c c] }
8053 \set Staff.timeSignatureFraction = #'(10 . 8)
8054 \compressmusic #'(3 . 5) {
8055 \repeat unfold 2 { c8[ c c] }
8056 \repeat unfold 2 { c8[ c] }
8057 | c4. c4. \times 2/3 { c8 c c } c4
8068 When using different time signatures in parallel, the spacing is
8069 aligned vertically, but bar lines distort the regular spacing.
8074 @subsection Clusters
8078 A cluster indicates a continuous range of pitches to be played. They
8079 can be denoted as the envelope of a set of notes. They are entered by
8080 applying the function @code{makeClusters} to a sequence of
8082 @lilypond[quote,raggedright,relative=2,fragment,verbatim]
8083 \makeClusters { <c e > <b f'> }
8086 The following example (from
8087 @inputfileref{input/@/regression,cluster@/.ly}) shows what the result
8090 @lilypondfile[raggedright,quote]{cluster.ly}
8092 Ordinary notes and clusters can be put together in the same staff,
8093 even simultaneously. In such a case no attempt is made to
8094 automatically avoid collisions between ordinary notes and clusters.
8098 Program reference: @internalsref{ClusterSpanner},
8099 @internalsref{ClusterSpannerBeacon},
8100 @internalsref{Cluster_spanner_engraver}, and
8101 @internalsref{ClusterNoteEvent}.
8103 Examples: @inputfileref{input/@/regression,cluster@/.ly}.
8107 Music expressions like @code{<< @{ g8 e8 @} a4 >>} are not printed
8108 accurately. Use @code{<g a>8 <e a>8} instead.
8112 @node Special fermatas
8113 @subsection Special fermatas
8115 @cindex fermatas, special
8117 In contemporary music notation, special fermata symbols denote breaks
8118 of differing lengths. The following fermatas are supported
8120 @lilypond[quote,raggedright]
8143 \context Lyrics \lyricmode {
8144 \override LyricText #'font-family = #'typewriter
8145 "shortfermata" "fermata" "longfermata" "verylongfermata"
8150 See @ref{Articulations} for general instructions how to apply scripts
8151 such as fermatas to notes.
8153 @node Feathered beams
8154 @subsection Feathered beams
8156 Feathered beams are not supported natively, but they can be faked by
8157 forcing two beams to overlap. Here is an example,
8159 @c don't change relative setting witout changing positions!
8160 @lilypond[raggedright,relative=1,fragment,verbatim]
8165 \once \override Voice.Beam #'positions = #'(0 . 0.5)
8170 \once \override Voice.Beam #'positions = #'(0 . -0.5)
8178 @node Educational use
8179 @section Educational use
8181 With the amount of control that LilyPond offers, one can make great
8182 teaching tools in addition to great musical scores.
8186 * Blank music sheet::
8188 * Shaped note heads ::
8189 * Easy Notation note heads::
8193 @subsection Balloon help
8195 Elements of notation can be marked and named with the help of a square
8196 balloon. The primary purpose of this feature is to explain notation.
8198 The following example demonstrates its use.
8200 @lilypond[quote,verbatim,fragment,raggedright,relative=2]
8203 #(add-balloon-text 'NoteHead "heads, or tails?"
8210 The function @code{add-balloon-text} takes the name of a grob, the
8211 label to print, and the position where to put the label relative to
8212 the object. In the above example, the text ``heads or tails?'' ends
8213 3 spaces below and 1 space to the right of the marked head.
8216 @cindex notation, explaining
8220 Program reference: @internalsref{text-balloon-interface}.
8222 Examples: @inputfileref{input/@/regression,balloon@/.ly}.
8227 @node Blank music sheet
8228 @subsection Blank music sheet
8230 A blank music sheet can be produced also by using invisible notes, and
8231 removing @code{Bar_number_engraver}.
8234 @lilypond[quote,verbatim]
8236 \repeat unfold 2 % Change this for more lines.
8241 \override TimeSignature #'transparent = ##t
8242 defaultBarType = #""
8243 \remove Bar_number_engraver
8245 \context Staff \emptymusic
8246 \context TabStaff \emptymusic
8252 @subsection Hidden notes
8254 @cindex Hidden notes
8255 @cindex Invisible notes
8256 @cindex Transparent notes
8258 Hidden (or invisible or transparent) notes can be useful in preparing theory
8259 or composition exercises.
8261 @lilypond[quote,raggedright,verbatim,relative=2,fragment]
8269 Hidden notes are also great for performing weird tricks. For example,
8270 slurs cannot be attached to rests or spacer rests, but you may wish
8271 to include that in your score -- string instruments use this notation
8272 when doing pizzicato to indicate that the note should ring for as long
8275 @lilypond[quote,raggedright,verbatim,relative=0,fragment]
8278 c4^"pizz"( \hideNotes c)
8279 \unHideNotes c( \hideNotes c)
8286 @node Shaped note heads
8287 @subsection Shaped note heads
8289 In shaped note head notation, the shape of the note head corresponds
8290 to the harmonic function of a note in the scale. This notation was
8291 popular in the 19th century American song books.
8293 Shaped note heads can be produced by setting @code{\aikenHeads} or
8294 @code{\sacredHarpHeads}, depending on the style desired.
8296 @lilypond[verbatim,relative=1,fragment]
8303 Shapes are determined on the step in the scale, where the base of the
8304 scale is determined by the @code{\key} command
8307 @findex shapeNoteStyles
8309 @findex \sacredHarpHeads
8311 Shaped note heads are implemented through the @code{shapeNoteStyles}
8312 property. Its value is a vector of symbols. The k-th element indicates
8313 the style to use for the k-th step of the scale. Arbitrary
8314 combinations are possible, eg.,
8317 @lilypond[verbatim,relative=1,fragment]
8318 \set shapeNoteStyles = ##(cross triangle fa #f mensural xcircle diamond)
8323 @node Easy Notation note heads
8324 @subsection Easy Notation note heads
8326 @cindex easy notation
8329 The `easy play' note head includes a note name inside the head. It is
8330 used in music for beginners
8332 @lilypond[quote,raggedright,verbatim,fragment,staffsize=26]
8337 The command @code{\setEasyHeads} overrides settings for the
8338 @internalsref{NoteHead} object. To make the letters readable, it has
8339 to be printed in a large font size. To print with a larger font, see
8340 @ref{Setting global staff size}.
8344 @cindex @code{\setEasyHeads}
8345 @code{\setEasyHeads}