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
8 @node Instrument-specific notation
9 @chapter Instrument-specific notation
11 This chapter explains how to use notation for specific instruments.
21 * Other instrument specific notation::
29 Piano staves are two normal staves coupled with a brace. The staves
30 are largely independent, but sometimes voices can cross between the
31 two staves. The same notation is also used for harps and other key
32 instruments. The @internalsref{PianoStaff} is especially built to
33 handle this cross-staffing behavior. In this section we discuss the
34 @internalsref{PianoStaff} and some other pianistic peculiarities.
37 * Automatic staff changes::
38 * Manual staff switches::
40 * Staff switch lines::
46 Dynamics are not centered, but workarounds do exist. See the
47 ``piano centered dynamics'' template in @ref{Piano templates}.
49 @cindex cross staff stem
50 @cindex stem, cross staff
51 @cindex distance between staves in piano music
53 The distance between the two staves is the same for all systems in the
54 score. It is possible to override this per system, but it does require
55 an arcane command incantation. See
56 @inputfileref{input/@/test,piano@/-staff@/-distance@/.ly}.
59 @node Automatic staff changes
60 @subsection Automatic staff changes
61 @cindex Automatic staff changes
63 Voices can be made to switch automatically between the top and the bottom
64 staff. The syntax for this is
68 \autochange @dots{}@var{music}@dots{}
73 This will create two staves inside the current PianoStaff, called
74 @code{up} and @code{down}. The lower staff will be in bass clef by
77 A @code{\relative} section that is outside of @code{\autochange} has
78 no effect on the pitches of @var{music}, so, if necessary, put
79 @code{\relative} inside @code{\autochange} like
83 \autochange \relative @dots{} @dots{}
88 The autochanger switches on basis of the pitch (middle C is the turning
89 point), and it looks ahead skipping over rests to switch in
90 advance. Here is a practical example
92 @lilypond[quote,verbatim,raggedright]
94 \autochange \relative c'
103 In this manual: @ref{Manual staff switches}.
105 Program reference: @internalsref{AutoChangeMusic}.
111 The staff switches may not end up in optimal places. For high
112 quality output, staff switches should be specified manually.
115 @code{\autochange} cannot be inside @code{\times}.
118 @node Manual staff switches
119 @subsection Manual staff switches
121 @cindex manual staff switches
122 @cindex staff switch, manual
124 Voices can be switched between staves manually, using the command
126 \change Staff = @var{staffname} @var{music}
130 The string @var{staffname} is the name of the staff. It switches the
131 current voice from its current staff to the Staff called
132 @var{staffname}. Typically @var{staffname} is @code{"up"} or
133 @code{"down"}. The @context{Staff} referred to must already exist, so
134 usually the setup for a score will start with a setup of the staves,
138 \context Staff = up @{
139 \skip 1 * 10 % @emph{keep staff alive}
141 \context Staff = down @{
142 \skip 1 * 10 % @emph{idem}
148 and the @context{Voice} is inserted afterwards
151 \context Staff = down
152 \new Voice @{ @dots{} \change Staff = up @dots{} @}
160 Pianos have pedals that alter the way sound is produced. Generally, a
161 piano has three pedals, sustain, una corda, and sostenuto.
164 Piano pedal instruction can be expressed by attaching
165 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
166 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
169 @lilypond[quote,raggedright,fragment,verbatim]
170 c'4\sustainDown c'4\sustainUp
173 What is printed can be modified by setting @code{pedal@var{X}Strings},
174 where @var{X} is one of the pedal types: @code{Sustain},
175 @code{Sostenuto} or @code{UnaCorda}. Refer to
176 @internalsref{SustainPedal} in the program reference for more
179 Pedals can also be indicated by a sequence of brackets, by setting the
180 @code{pedalSustainStyle} property to bracket objects
182 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
183 \set Staff.pedalSustainStyle = #'bracket
185 b\sustainUp\sustainDown
186 b g \sustainUp a \sustainDown \bar "|."
189 A third style of pedal notation is a mixture of text and brackets,
190 obtained by setting the @code{pedalSustainStyle} property to
193 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
194 \set Staff.pedalSustainStyle = #'mixed
196 b\sustainUp\sustainDown
197 b g \sustainUp a \sustainDown \bar "|."
200 The default `*Ped.' style for sustain and damper pedals corresponds to
201 style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
204 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
205 c\sostenutoDown d e c, f g a\sostenutoUp
208 For fine-tuning the appearance of a pedal bracket, the properties
209 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
210 @code{PianoPedalBracket} objects (see
211 @internalsref{PianoPedalBracket} in the Program reference) can be
212 modified. For example, the bracket may be extended to the right edge
215 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
216 \override Staff.PianoPedalBracket #'shorten-pair = #'(0 . -1.0)
217 c\sostenutoDown d e c, f g a\sostenutoUp
220 @node Staff switch lines
221 @subsection Staff switch lines
225 @cindex staff switching
228 @cindex @code{followVoice}
230 Whenever a voice switches to another staff, a line connecting the notes
231 can be printed automatically. This is switched on by setting
232 @code{followVoice} to true
234 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
237 \set followVoice = ##t
242 \context Staff=two { \clef bass \skip 1*2 }
248 Program reference: @internalsref{VoiceFollower}.
252 @cindex @code{\showStaffSwitch}
253 @code{\showStaffSwitch},
254 @cindex @code{\hideStaffSwitch}
255 @code{\hideStaffSwitch}.
258 @node Cross staff stems
259 @subsection Cross staff stems
261 Chords that cross staves may be produced by increasing the length
262 of the stem in the lower staff, so it reaches the stem in the upper
263 staff, or vice versa.
265 @lilypond[raggedright,verbatim,quote]
266 stemExtend = \once \override Stem #'length = #22
267 noFlag = \once \override Stem #'flag-style = #'no-flag
268 \context PianoStaff <<
270 \stemDown \stemExtend
288 * Introducing chord names::
290 * Printing chord names::
294 @c awkward name; awkward section name.
295 @c still, the Basic "chords" seems like a good name... :(
296 @node Introducing chord names
297 @subsection Introducing chord names
300 LilyPond has support for printing chord names. Chords may be entered
301 in musical chord notation, i.e., @code{< .. >}, but they can also be
302 entered by name. Internally, the chords are represented as a set of
303 pitches, so they can be transposed
306 @lilypond[quote,raggedright,verbatim,raggedright]
307 twoWays = \transpose c c' {
316 << \context ChordNames \twoWays
317 \context Voice \twoWays >>
320 This example also shows that the chord printing routines do not try to
321 be intelligent. The last chord (@code{f bes d}) is not interpreted as
324 Note that the duration of chords must be specified outside the
333 @subsection Chords mode
336 In chord mode sets of pitches (chords) are entered with normal note
337 names. A chord is entered by the root, which is entered like a
340 @lilypond[quote,raggedright,fragment,verbatim]
341 \chordmode { es4. d8 c2 }
345 The mode is introduced by the keyword @code{\chordmode}.
350 Other chords may be entered by suffixing a colon and introducing a
351 modifier (which may include a number if desired)
352 @lilypond[quote,fragment,verbatim]
353 \chordmode { e1:m e1:7 e1:m7 }
355 The first number following the root is taken to be the `type' of the
356 chord, thirds are added to the root until it reaches the specified
358 @lilypond[quote,fragment,verbatim]
359 \chordmode { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 }
362 @cindex root of chord
363 @cindex additions, in chords
364 @cindex removals, in chords
366 More complex chords may also be constructed adding separate steps
367 to a chord. Additions are added after the number following
368 the colon and are separated by dots
369 @lilypond[quote,verbatim,fragment]
370 \chordmode { c:5.6 c:3.7.8 c:3.6.13 }
372 Chord steps can be altered by suffixing a @code{-} or @code{+} sign
374 @lilypond[quote,verbatim,fragment]
375 \chordmode { c:7+ c:5+.3- c:3-.5-.7- }
377 Removals are specified similarly and are introduced by a caret. They
378 must come after the additions
379 @lilypond[quote,verbatim,fragment]
380 \chordmode { c^3 c:7^5 c:9^3.5 }
383 Modifiers can be used to change pitches. The following modifiers are
388 The minor chord. This modifier lowers the 3rd and (if present) the 7th step.
391 The diminished chord. This modifier lowers the 3rd, 5th and (if present)
395 The augmented chord. This modifier raises the 5th step.
398 The major 7th chord. This modifier raises the 7th step if present.
401 The suspended 4th or 2nd. This modifier removes the 3rd
402 step. Append either @code{2} or @code{4} to add the 2nd or 4th step to
406 Modifiers can be mixed with additions
407 @lilypond[quote,verbatim,fragment]
408 \chordmode { c:sus4 c:7sus4 c:dim7 c:m6 }
411 @cindex modifiers, in chords.
418 Since an unaltered 11 does not sound good when combined with an
419 unaltered 3, the 11 is removed in this case (unless it is added
421 @lilypond[quote,raggedright,fragment,verbatim]
422 \chordmode { c:13 c:13.11 c:m13 }
427 An inversion (putting one pitch of the chord on the bottom), as well
428 as bass notes, can be specified by appending
429 @code{/}@var{pitch} to the chord
430 @lilypond[quote,raggedright,fragment,verbatim]
431 \chordmode { c1 c/g c/f }
435 A bass note can be added instead transposed out of the chord,
436 by using @code{/+}@var{pitch}.
438 @lilypond[quote,raggedright,fragment,verbatim]
439 \chordmode { c1 c/+g c/+f }
442 Chords is a mode similar to @code{\lyricmode}, etc. Most
443 of the commands continue to work, for example, @code{r} and
444 @code{\skip} can be used to insert rests and spaces, and property
445 commands may be used to change various settings.
451 Each step can only be present in a chord once. The following
452 simply produces the augmented chord, since @code{5+} is interpreted
455 @lilypond[quote,raggedright,verbatim,fragment]
456 \chordmode { c:5.5-.5+ }
460 @node Printing chord names
461 @subsection Printing chord names
463 @cindex printing chord names
467 For displaying printed chord names, use the @internalsref{ChordNames} context.
468 The chords may be entered either using the notation
469 described above, or directly using @code{<} and @code{>}
471 @lilypond[quote,verbatim,raggedright]
473 \chordmode {a1 b c} <d' f' a'> <e' g' b'>
476 \context ChordNames \harmonies
477 \context Staff \harmonies
481 You can make the chord changes stand out by setting
482 @internalsref{ChordNames}.@code{chordChanges} to true. This will only
483 display chord names when there is a change in the chords scheme and at
484 the start of a new line
486 @lilypond[quote,verbatim,raggedright]
487 harmonies = \chordmode {
488 c1:m c:m \break c:m c:m d
491 \context ChordNames {
492 \set chordChanges = ##t
494 \context Staff \transpose c c' \harmonies
498 The previous examples all show chords over a staff. This is not
499 necessary. Chords may also be printed separately. It may be necessary
500 to add @internalsref{Volta_engraver} and @internalsref{Bar_engraver}
503 @lilypond[raggedright,verbatim]
504 \new ChordNames \with {
505 \override BarLine #'bar-size = #4
506 voltaOnThisStaff = ##t
507 \consists Bar_engraver
508 \consists "Volta_engraver"
510 \repeat volta 2 \chordmode {
519 The default chord name layout is a system for Jazz music, proposed by
520 Klaus Ignatzek (see @ref{Literature list}). It can be tuned through the
524 @cindex @code{chordNameExceptions}
525 @item chordNameExceptions
526 This is a list that contains the chords that have special formatting.
528 The exceptions list should be encoded as
530 @{ <c f g bes>1 \markup @{ \super "7" "wahh" @} @}
533 To get this information into @code{chordNameExceptions} takes a little
534 manoeuvring. The following code transforms @code{chExceptionMusic}
535 (which is a sequential music) into a list of exceptions.
537 (sequential-music-to-chord-exceptions chExceptionMusic #t)
542 (sequential-music-to-chord-exceptions chExceptionMusic #t)
545 adds the new exceptions to the default ones, which are defined in
546 @file{ly/@/chord@/-modifier@/-init@/.ly}.
548 For an example of tuning this property, see also
549 @inputfileref{input/@/regression,chord@/-name@/-exceptions@/.ly}.
550 @cindex exceptions, chord names.
553 @cindex @code{majorSevenSymbol}
554 @item majorSevenSymbol
555 This property contains the markup object used for the 7th step, when
556 it is major. Predefined options are @code{whiteTriangleMarkup} and
557 @code{blackTriangleMarkup}. See
558 @inputfileref{input/@/regression,chord@/-name@/-major7@/.ly} for an example.
560 @cindex @code{chordNameSeparator}
561 @item chordNameSeparator
562 Different parts of a chord name are normally separated by a
563 slash. By setting @code{chordNameSeparator}, you can specify other
565 @lilypond[quote,raggedright,fragment,verbatim]
566 \context ChordNames \chordmode {
568 \set chordNameSeparator
569 = \markup { \typewriter "|" }
574 @cindex @code{chordRootNamer}
576 The root of a chord is usually printed as a letter with an optional
577 alteration. The transformation from pitch to letter is done by this
578 function. Special note names (for example, the German ``H'' for a
579 B-chord) can be produced by storing a new function in this property.
581 @cindex @code{chordNoteNamer}
583 The default is to print single pitch, e.g., the bass note, using the
584 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
585 to a specialized function to change this behavior. For example, the
586 base can be printed in lower case.
588 @cindex @code{chordPrefixSpacer}
589 @item chordPrefixSpacer
590 The ``m'' for minor chords is usually printed right after the root of
591 the chord. By setting @code{chordPrefixSpacer}, you can fix a spacer
592 between the root and ``m''. The spacer is not used when the root
597 The predefined variables @code{\germanChords},
598 @code{\semiGermanChords}, @code{\italianChords} and @code{\frenchChords}
599 set these variables. The effect is
602 @lilypondfile[raggedright]{chord-names-languages.ly}
604 There are also two other chord name schemes implemented: an alternate
605 Jazz chord notation, and a systematic scheme called Banter chords. The
606 alternate Jazz notation is also shown on the chart in @ref{Chord name
607 chart}. Turning on these styles is described in the input file
608 @inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
617 @cindex @code{\germanChords}
618 @code{\germanChords},
619 @cindex @code{\semiGermanChords}
620 @code{\semiGermanChords}.
621 @cindex @code{\italianChords}
622 @code{\italianChords}.
623 @cindex @code{\frenchChords}
624 @code{\frenchChords}.
631 Examples: @inputfileref{input/@/regression,chord@/-name@/-major7@/.ly},
632 @inputfileref{input/@/regression,chord@/-name@/-exceptions@/.ly},
633 @inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
636 Init files: @file{scm/@/chords@/-ignatzek@/.scm}, and
637 @file{scm/@/chord@/-entry@/.scm}.
642 Chord names are determined solely from the list of pitches. Chord
643 inversions are not identified, and neither are added bass notes. This
644 may result in strange chord names when chords are entered with the
645 @code{< .. >} syntax.
652 There are three different issues when printing vocal music
656 Song texts must be entered as text, not notes. For example, the
657 input@tie{}@code{d} should be interpreted as a one letter syllable, not the
661 Song texts must be printed as text, not as notes.
664 Song texts must be aligned with the notes of their melody.
667 The simplest solution for printing music uses the @code{\addlyrics}
668 function to solve all these problems at once. However, these
669 three functions can be controlled separately, which is necessary
670 for complex vocal music.
674 * Setting simple songs::
676 * Hyphens and extenders::
677 * The Lyrics context::
678 * Flexibility in alignment::
681 * Other vocal issues::
684 @node Setting simple songs
685 @subsection Setting simple songs
687 The easiest way to add lyrics to a melody is to append
690 \addlyrics @{ @var{the lyrics} @}
694 to a melody. Here is an example,
696 @lilypond[raggedright,verbatim,fragment,quote]
698 \relative { c2 e4 g2. }
699 \addlyrics { play the game }
702 More stanzas can be added by adding more
703 @code{\addlyrics} sections
705 @lilypond[raggedright,verbatim,fragment,quote]
707 \relative { c2 e4 g2. }
708 \addlyrics { play the game }
709 \addlyrics { speel het spel }
710 \addlyrics { joue le jeu }
713 @c TODO - this isn't such a great place for this note, but I can't
714 @c find a better place without rearranging a lot of lyric stuff.
715 @c It's yet another thing to look at post-3.0.
717 The @code{\addlyrics} command is actually just a convienient way
718 to write a more complicated LilyPond structure that sets up the
719 lyrics. You should use @code{\addlyrics} unless you need to do
720 fancy things, in which case you should investigate
721 @code{\lyricsto} or @code{\lyricmode}.
725 \addlyrics @{ LYRICS @}
732 \context Voice = blah @{ music @}
733 \lyricsto "blah" \new lyrics @{ LYRICS @}
738 @code{\addlyrics} cannot handle polyphony.
741 @node Entering lyrics
742 @subsection Entering lyrics
745 @cindex @code{\lyricmode}
748 Lyrics are entered in a special input mode. This mode is introduced
749 by the keyword @code{\lyricmode}, or by using @code{\addlyrics} or
750 @code{\lyricsto}. In this mode you can enter lyrics,
751 with punctuation and accents, and the input @code{d} is not parsed as
752 a pitch, but rather as a one letter syllable. Syllables are entered
753 like notes, but with pitches replaced by text. For example,
755 \lyricmode @{ Twin-4 kle4 twin- kle litt- le star2 @}
758 There is a difference between @code{\addlyrics} and
759 @code{\lyricmode}. @code{\addlyrics} and @code{\lyricsto}
760 ignore all durations and aligns syllables to notes; @code{\lyricmode}
761 uses the durations specified.
763 A word lyrics mode begins with an alphabetic character, and ends with
764 any space or digit. The following characters can be any character
765 that is not a digit or white space. One important consequence of this
766 is that a word can end with @code{@}}. The following example is
767 usually a mistake in the input file. The syllable includes a @code{@}}, so the
768 opening brace is not balanced
770 \lyricmode @{ twinkle@}
773 @cindex @code{\property}, in @code{\lyricmode}
775 Similarly, a period which follows an alphabetic sequence is included in
776 the resulting string. As a consequence, spaces must be inserted around
779 \override Score . LyricText #'font-shape = #'italic
783 @cindex spaces, in lyrics
784 @cindex quotes, in lyrics
786 Any @code{_} character that appears in an unquoted word is converted
787 to a space. This provides a mechanism for introducing spaces into words
788 without using quotes.
790 To enter lyrics with characters from non-English languages, or with
791 non-ascii characters (such as the heart symbol or slanted quotes),
792 simply insert the characters directly into the input file and save
793 it with utf-8 encoding. See @ref{Text encoding} for more info.
796 \lyricmode @{ He said: â
\80\9cLet my peo ple goâ
\80\9d. @}
799 The full definition of a word start in Lyrics mode is somewhat more
802 A word in Lyrics mode begins with: an alphabetic character, @code{_},
803 @code{?}, @code{!}, @code{:}, @code{'}, the control characters @code{^A}
804 through @code{^F}, @code{^Q} through @code{^W}, @code{^Y}, @code{^^},
805 any 8-bit character with ASCII code over 127, or a two-character
806 combination of a backslash followed by one of @code{`}, @code{'},
807 @code{"}, or @code{^}.
813 Program reference: @internalsref{LyricText}.
817 The definition of lyrics mode is too complex.
819 @node Hyphens and extenders
820 @subsection Hyphens and extenders
824 Centered hyphens are entered as `@code{--}' between syllables.
825 The hyphen will have variable length depending on the space between
826 the syllables and it will be centered between the syllables.
831 When a lyric is sung over many notes (this is called a melisma), this is
832 indicated with a horizontal line centered between a syllable and the
833 next one. Such a line is called an extender line, and it is entered as
836 In tighly engraved music, hyphens can be removed. In some languages
837 (e.g. German and Hungarian), hyphens should not disappear, since
838 spelling depends on hyphenation. For that purpose, hyphens can be
839 forced to remain by overriding @code{minimum-length} of
840 the @code{LyricHyphen} grob.
842 @lilypond[quote,verbatim,raggedright]
845 \new Staff \relative c'' {
846 \time 1/4 c16 c c c c16 c c c c16 c c c
848 \lyricmode { \new Lyrics
850 \override SeparationItem #'padding = #0.0
851 % Otherwise lyrics are so far apart that hyphens don't disappear
854 An -- ti -- cons -- ti --
855 tu -- tion -- nel -- le --
856 \override LyricHyphen #'minimum-length = #0.7
857 \override LyricHyphen #'spacing-procedure =
858 #Hyphen_spanner::set_spacing_rods
859 men -- taire -- ment. ouf~!
867 \Staff \remove "Time_signature_engraver"
875 Program reference: @internalsref{LyricHyphen}, @internalsref{LyricExtender}.
879 @node The Lyrics context
880 @subsection The Lyrics context
883 Lyrics are printed by interpreting them in a @internalsref{Lyrics} context
885 \context Lyrics \lyricmode @dots{}
888 @cindex automatic syllable durations
889 @cindex @code{\lyricsto}
890 @cindex lyrics and melodies
892 This will place the lyrics according to the durations that were
893 entered. The lyrics can also be aligned under a given melody
894 automatically. In this case, it is no longer necessary to enter the
895 correct duration for each syllable. This is achieved by combining the
896 melody and the lyrics with the @code{\lyricsto} expression
898 \lyricsto @var{name} \new Lyrics @dots{}
901 This aligns the lyrics to the
902 notes of the @internalsref{Voice} context called @var{name}, which has
903 to exist. Therefore, normally the @code{Voice} is specified first, and
904 then the lyrics are specified with @code{\lyricsto}. The command
905 @code{\lyricsto} switches to @code{\lyricmode} mode automatically, so the
906 @code{\lyricmode} keyword may be omitted.
908 For different or more complex orderings, the best way is to setup the
909 hierarchy of staves and lyrics first, e.g.,
911 \context ChoirStaff <<
912 \context Lyrics = sopranoLyrics @{ s1 @}
913 \context Voice = soprano @{ @emph{music} @}
914 \context Lyrics = tenorLyrics @{ s1 @}
915 \context Voice = tenor @{ @emph{music} @}
918 and then combine the appropriate melodies and lyric lines
920 \lyricsto "soprano" \context Lyrics = sopranoLyrics
925 The final input would resemble
928 <<\context ChoirStaff << @emph{setup the music} >>
929 \lyricsto "soprano" @emph{etc}
930 \lyricsto "alto" @emph{etc}
936 The @code{\lyricsto} command detects melismata: it only puts one
937 syllable under a tied or slurred group of notes. If you want to force
938 an unslurred group of notes to be a melisma, insert @code{\melisma}
939 after the first note of the group, and @code{\melismaEnd} after the
942 @lilypond[quote,relative=2,raggedright,fragment,verbatim]
944 \context Voice = "lala" {
952 \lyricsto "lala" \new Lyrics {
958 In addition, notes are considered a melisma if they are manually
959 beamed, and automatic beaming (see @ref{Setting automatic beam
960 behavior}) is switched off.
966 The criteria for deciding melismata can
967 be tuned with the property @code{melismaBusyProperties}. See
968 @internalsref{Melisma_translator} in the program reference for more
973 Lyrics can also be entered without @code{\lyricsto}. In this case the
974 duration of each syllable must be entered explicitly, for example,
981 The alignment to a melody can be specified with the
982 @code{associatedVoice} property,
985 \set associatedVoice = #"lala"
989 The value of the property (here: @code{"lala"}) should be the name of
990 a @internalsref{Voice} context. Without this setting, extender lines
991 will not be formatted properly.
993 Here is an example demonstrating manual lyric durations,
995 @lilypond[relative=1,raggedright,verbatim,fragment,quote]
996 << \context Voice = melody {
1000 \new Lyrics \lyricmode {
1001 \set associatedVoice = #"melody"
1007 @cindex choral score
1009 A complete example of a SATB score setup is in section
1010 @ref{Vocal ensembles}.
1015 @code{\melisma}, @code{\melismaEnd}
1016 @cindex @code{\melismaEnd}
1017 @cindex @code{\melisma}
1021 Program reference: @internalsref{LyricCombineMusic},
1022 @internalsref{Lyrics}, @internalsref{Melisma_translator}.
1025 @inputfileref{input/@/regression,lyric@/-combine@/-new@/.ly}.
1026 @c TODO: make separate section for melismata
1030 Melismata are not detected automatically, and extender lines must be
1034 @c TODO: document \new Staff << Voice \lyricsto >> bug
1036 @node Flexibility in alignment
1037 @subsection Flexibility in alignment
1039 Often, different stanzas of one song are put to one melody in slightly
1040 differing ways. Such variations can still be captured with
1043 @subsubsection Lyrics to multiple notes of a melisma
1046 One possibility is that the text has a melisma in one stanza, but
1047 multiple syllables in another one. One solution is to make the faster
1048 voice ignore the melisma. This is done by setting
1049 @code{ignoreMelismata} in the Lyrics context.
1051 There has one tricky aspect. The setting for @code{ignoreMelismata}
1052 must be set one syllable @emph{before} the non-melismatic syllable
1053 in the text, as shown here,
1055 @lilypond[verbatim,raggedright,quote]
1057 \relative \context Voice = "lahlah" {
1058 \set Staff.autoBeaming = ##f
1064 \new Lyrics \lyricsto "lahlah" {
1067 \new Lyrics \lyricsto "lahlah" {
1068 \set ignoreMelismata = ##t % applies to "fas"
1070 \unset ignoreMelismata
1077 The @code{ignoreMelismata} applies to the syllable ``fas'', so it
1078 should be entered before ``go''.
1080 The reverse is also possible: making a lyric line slower than the
1081 standard. This can be achieved by insert @code{\skip}s into the
1082 lyrics. For every @code{\skip}, the text will be delayed another note.
1085 @lilypond[verbatim,raggedright,quote]
1086 \relative { c c g' }
1094 @subsection Switching the melody associated with a lyrics line
1098 More complex variations in text underlay are possible. It is possible
1099 to switch the melody for a line of lyrics during the text. This is
1100 done by setting the @code{associatedVoice} property. In the example
1102 @lilypond[raggedright,quote]
1104 \relative \context Voice = "lahlah" {
1105 \set Staff.autoBeaming = ##f
1108 \context Voice = alternative {
1111 % show associations clearly.
1112 \override NoteColumn #'force-hshift = #-3
1123 \new Lyrics \lyricsto "lahlah" {
1124 Ju -- ras -- sic Park
1126 \new Lyrics \lyricsto "lahlah" {
1127 % Tricky: need to set associatedVoice
1128 % one syllable too soon!
1129 \set associatedVoice = alternative % applies to "ran"
1133 \set associatedVoice = lahlah % applies to "rus"
1139 the text for the first stanza is set to a melody called ``lahlah'',
1142 \new Lyrics \lyricsto "lahlah" @{
1143 Ju -- ras -- sic Park
1148 The second stanza initially is set to the @code{lahlah} context, but
1149 for the syllable ``ran'', it switches to a different melody.
1150 This is achieved with
1152 \set associatedVoice = alternative
1156 Here, @code{alternative} is the name of the @code{Voice} context
1157 containing the triplet.
1159 Again, the command must be one syllable too early, before ``Ty'' in
1163 \new Lyrics \lyricsto "lahlah" @{
1164 \set associatedVoice = alternative % applies to "ran"
1168 \set associatedVoice = lahlah % applies to "rus"
1174 The underlay is switched back to the starting situation by assigning
1175 @code{lahlah} to @code{associatedVoice}.
1179 @subsection Specifying melismata within the lyrics
1181 It is also possible to define melismata entirely in the lyrics. This
1182 can be done by entering @code{_} for every note that is part of the
1185 @lilypond[relative=1,verbatim,fragment]
1186 { \set melismaBusyProperties = #'()
1187 c d( e) f f( e) e e }
1189 { Ky -- _ _ ri __ _ _ _ e }
1192 In this case, you can also have ties and slurs in the melody, if you
1193 set @code{melismaBusyProperties}, as is done in the example above.
1195 @lilypond[relative=1,verbatim,fragment]
1197 \set melismaBusyProperties = #'()
1201 { Ky -- _ _ ri __ _ _ _ e }
1206 @subsection More stanzas
1208 @cindex phrasing, in lyrics
1211 @cindex stanza number
1212 @cindex singer's names
1213 @cindex name of singer
1215 Stanza numbers can be added by setting @code{stanza}, e.g.,
1217 @lilypond[quote,raggedright,verbatim,relative=2,fragment]
1219 \time 3/4 g2 e4 a2 f4 g2.
1222 Hi, my name is Bert.
1225 Oh, che -- ri, je t'aime
1229 These numbers are put just before the start of first syllable.
1231 Names of singers can also be added. They are printed at the start of
1232 the line, just like instrument names. They are created by setting
1233 @code{vocalName}. A short version may be entered as @code{vocNam}.
1236 @lilypond[fragment,raggedright,quote,verbatim,relative=2]
1238 \time 3/4 g2 e4 a2 f4 g2.
1240 \set vocalName = "Bert "
1241 Hi, my name is Bert.
1243 \set vocalName = "Ernie "
1244 Oh, che -- ri, je t'aime
1248 You can display alternate (or divisi) lyrics by naming voice
1249 contexts and attaching lyrics to those specific contexts.
1251 @lilypond[verbatim,raggedright,quote]
1253 \context Voice = "melody" {
1258 \context Voice = splitpart { \voiceTwo c4 }
1263 \new Lyrics \lyricsto "melody" { we shall not o- ver- come }
1264 \new Lyrics \lyricsto "splitpart" { will }
1269 You can use this trick to display different lyrics for a repeated
1272 @lilypond[verbatim,raggedright,quote]
1274 \context Voice = melody \relative c' {
1276 \context Voice = verse \repeat volta 2 {c4 d e f | g1 | }
1278 \lyricsto melody \context Lyrics = mainlyrics \lyricmode {
1281 \lyricsto verse \context Lyrics = mainlyrics \lyricmode {
1283 \lyricsto verse \context Lyrics = repeatlyrics \lyricmode {
1284 dodo rere mimi fafa solsol }
1292 Program reference: @internalsref{LyricText}, @internalsref{StanzaNumber}, @internalsref{VocalName}.
1300 The term @emph{ambitus} denotes a range of pitches for a given voice
1301 in a part of music. It may also denote the pitch range that a musical
1302 instrument is capable of playing. Ambits are printed on vocal parts,
1303 so performers can easily determine it meets their capabilities.
1305 Ambits are denoted at the beginning of a piece near the initial clef.
1306 The range is graphically specified by two note heads that represent the
1307 minimum and maximum pitch. To print such ambits, add the
1308 @internalsref{Ambitus_engraver} to the @internalsref{Voice} context,
1315 \consists Ambitus_engraver
1320 This results in the following output
1322 @lilypond[quote,raggedright]
1326 \consists Ambitus_engraver
1330 \relative \new Staff {
1335 If you have multiple voices in a single staff and you want a single
1336 ambitus per staff rather than per each voice, add the
1337 @internalsref{Ambitus_engraver} to the @internalsref{Staff} context
1338 rather than to the @internalsref{Voice} context. Here is an example,
1340 @lilypond[verbatim,raggedright,quote]
1342 \consists "Ambitus_engraver"
1346 \remove "Ambitus_engraver"
1348 \override Ambitus #'X-offset-callbacks
1349 = #(list (lambda (grob axis) -1.0))
1354 \remove "Ambitus_engraver"
1363 This example uses one advanced feature,
1366 \override Ambitus #'X-offset-callbacks
1367 = #(list (lambda (grob axis) -1.0))
1371 This code moves the ambitus to the left. The same effect could have
1372 been achieved with @code{extra-offset}, but then the formatting system
1373 would not reserve space for the moved object.
1377 Program reference: @internalsref{Ambitus},
1378 @internalsref{AmbitusLine}, @internalsref{AmbitusNoteHead},
1379 @internalsref{AmbitusAccidental}.
1381 Examples: @inputfileref{input/@/regression,ambitus@/.ly}.
1385 There is no collision handling in the case of multiple per-voice
1389 @node Other vocal issues
1390 @subsection Other vocal issues
1392 Bagpipe music nominally uses the key of D Major (even though that
1393 isn't really true). However, since that is the only key that can be used,
1394 the key signature is normally not written out. To set this up correctly,
1395 always start your music with @code{\hideKeySignature}. If you for some
1396 reason want to show the key signature, you can use @code{\showKeySignature}
1400 yeah, I'm giving up somewhat by stuffing a bunch of things in
1401 here. But at least they're in the manual now; it's easier to
1402 move them around in the manual once they're already here.
1404 Besides, if users complain about everything stuffed in here, I
1405 can ask them for specific instructions about where to move these
1406 examples, and that might get them more involved in the docs. -gp
1409 ``Parlato'' is spoken without pitch but still with rhythm; it is
1410 notated by cross noteheads. This is demonstrated in
1411 @ref{Special noteheads}.
1413 Some modern music use cross fingering on c and f to flatten those notes.
1414 This can be indicated by @code{cflat} or @code{fflat}. Similarly, the
1415 piobaireachd high g can be written @code{gflat} when it occurs in light
1418 @node Rhythmic music
1419 @section Rhythmic music
1421 Rhythmic music is primarily used for percussion and drum notation, but it can
1422 also be used to show the rhythms of melodies.
1425 * Showing melody rhythms::
1426 * Entering percussion::
1427 * Percussion staves::
1431 @node Showing melody rhythms
1432 @subsection Showing melody rhythms
1434 Sometimes you might want to show only the rhythm of a melody. This
1435 can be done with the rhythmic staff. All pitches of notes on such a
1436 staff are squashed, and the staff itself has a single line
1438 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
1439 \context RhythmicStaff {
1441 c4 e8 f g2 | r4 g r2 | g1:32 | r1 |
1447 Program reference: @internalsref{RhythmicStaff}.
1449 Examples: @inputfileref{input/@/regression,rhythmic@/-staff@/.ly}.
1452 @node Entering percussion
1453 @subsection Entering percussion
1459 Percussion notes may be entered in @code{\drummode} mode, which is
1460 similar to the standard mode for entering notes. Each piece of
1461 percussion has a full name and an abbreviated name, and both can be used
1464 @lilypond[quote,raggedright,verbatim]
1466 hihat hh bassdrum bd
1470 The complete list of drum names is in the init file
1471 @file{ly/@/drumpitch@/-init@/.ly}.
1472 @c TODO: properly document this.
1476 Program reference: @internalsref{note-event}.
1478 @node Percussion staves
1479 @subsection Percussion staves
1483 A percussion part for more than one instrument typically uses a
1484 multiline staff where each position in the staff refers to one piece
1488 To typeset the music, the notes must be interpreted in a
1489 @internalsref{DrumStaff} and @internalsref{DrumVoice} contexts
1491 @lilypond[quote,raggedright,verbatim]
1492 up = \drummode { crashcymbal4 hihat8 halfopenhihat hh hh hh openhihat }
1493 down = \drummode { bassdrum4 snare8 bd r bd sn4 }
1495 \new DrumVoice { \voiceOne \up }
1496 \new DrumVoice { \voiceTwo \down }
1500 The above example shows verbose polyphonic notation. The short
1501 polyphonic notation, described in @ref{Polyphony}, can also be used if
1502 the @internalsref{DrumVoice}s are instantiated by hand first. For example,
1504 @lilypond[quote,raggedright,fragment,verbatim]
1506 \context DrumVoice = "1" { s1 *2 }
1507 \context DrumVoice = "2" { s1 *2 }
1511 { \repeat unfold 16 hh16 }
1520 There are also other layout possibilities. To use these, set the
1521 property @code{drumStyleTable} in context @internalsref{DrumVoice}.
1522 The following variables have been predefined
1526 This is the default. It typesets a typical drum kit on a five-line staff
1528 @lilypond[quote,linewidth=10.0\cm]
1530 cymc cyms cymr hh hhc hho hhho hhp
1531 cb hc bd sn ss tomh tommh tomml toml tomfh tomfl }
1533 cymc cyms cymr hh hhc hho hhho hhp \break
1534 cb hc bd sn ss tomh tommh tomml toml tomfh tomfl s16 }
1536 << \new DrumStaff \with {
1537 \remove Bar_engraver
1538 \remove Time_signature_engraver
1539 \override Stem #'transparent = ##t
1540 \override Stem #'Y-extent-callback = ##f
1541 minimumVerticalExtent = #'(-4.0 . 5.0)
1543 \context Lyrics \nam
1548 \override LyricText #'font-family = #'typewriter
1549 \override BarNumber #'transparent =##T
1555 The drum scheme supports six different toms. When there are fewer toms,
1556 simply select the toms that produce the desired result, i.e., to get toms
1557 on the three middle lines you use @code{tommh}, @code{tomml}, and
1560 @item timbales-style
1561 This typesets timbales on a two line staff
1563 @lilypond[quote,raggedright]
1564 nam = \lyricmode { timh ssh timl ssl cb }
1565 mus = \drummode { timh ssh timl ssl cb s16 }
1568 \context DrumStaff \with {
1569 \remove Bar_engraver
1570 \remove Time_signature_engraver
1571 \override Stem #'transparent = ##t
1572 \override Stem #'Y-extent-callback = ##f
1573 \override StaffSymbol #'line-count = #2
1574 \override StaffSymbol #'staff-space = #2
1575 minimumVerticalExtent = #'(-3.0 . 4.0)
1576 drumStyleTable = #timbales-style
1579 \override LyricText #'font-family = #'typewriter
1586 This typesets congas on a two line staff
1588 @lilypond[quote,raggedright]
1589 nam = \lyricmode { cgh cgho cghm ssh cgl cglo cglm ssl }
1590 mus = \drummode { cgh cgho cghm ssh cgl cglo cglm ssl s16 }
1593 \context DrumStaff \with {
1594 \remove Bar_engraver
1595 \remove Time_signature_engraver
1596 drumStyleTable = #congas-style
1597 \override StaffSymbol #'line-count = #2
1599 %% this sucks; it will lengthen stems.
1600 \override StaffSymbol #'staff-space = #2
1601 \override Stem #'transparent = ##t
1602 \override Stem #'Y-extent-callback = ##f
1605 \override LyricText #'font-family = #'typewriter
1612 This typesets bongos on a two line staff
1614 @lilypond[quote,raggedright]
1615 nam = \lyricmode { boh boho bohm ssh bol bolo bolm ssl }
1616 mus = \drummode { boh boho bohm ssh bol bolo bolm ssl s16 }
1619 \context DrumStaff\with {
1620 \remove Bar_engraver
1621 \remove Time_signature_engraver
1622 \override StaffSymbol #'line-count = #2
1623 drumStyleTable = #bongos-style
1625 %% this sucks; it will lengthen stems.
1626 \override StaffSymbol #'staff-space = #2
1627 \override Stem #'transparent = ##t
1628 \override Stem #'Y-extent-callback = ##f
1631 \override LyricText #'font-family = #'typewriter
1637 @item percussion-style
1638 To typeset all kinds of simple percussion on one line staves.
1640 @lilypond[quote,raggedright]
1641 nam = \lyricmode { tri trio trim gui guis guil cb cl tamb cab mar hc }
1642 mus = \drummode { tri trio trim gui guis guil cb cl tamb cab mar hc s16 }
1645 \context DrumStaff\with{
1646 \remove Bar_engraver
1647 drumStyleTable = #percussion-style
1648 \override StaffSymbol #'line-count = #1
1649 \remove Time_signature_engraver
1650 \override Stem #'transparent = ##t
1651 \override Stem #'Y-extent-callback = ##f
1654 \override LyricText #'font-family = #'typewriter
1661 If you do not like any of the predefined lists you can define your own
1662 list at the top of your file
1664 @lilypond[quote,raggedright,verbatim]
1666 (bassdrum default #f -1)
1667 (snare default #f 0)
1669 (pedalhihat xcircle "stopped" 2)
1670 (lowtom diamond #f 3)))
1671 up = \drummode { hh8 hh hh hh hhp4 hhp }
1672 down = \drummode { bd4 sn bd toml8 toml }
1675 \set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)
1676 \new DrumVoice { \voiceOne \up }
1677 \new DrumVoice { \voiceTwo \down }
1684 Init files: @file{ly/@/drumpitch@/-init@/.ly}.
1686 Program reference: @internalsref{DrumStaff}, @internalsref{DrumVoice}.
1690 Because general MIDI does not contain rim shots, the sidestick is used
1691 for this purpose instead.
1699 @cindex guitar tablature
1702 * String number indications::
1703 * Tablatures basic::
1704 * Non-guitar tablatures::
1706 * Other guitar issues::
1709 @node String number indications
1710 @subsection String number indications
1712 @cindex String numbers
1714 String numbers can be added to chords, by indicating the string number
1715 with @code{\}@var{number},
1717 @lilypond[relative,relative=1,raggedright,fragment]
1721 See also @inputfileref{input/regression,string-number.ly}.
1726 Program reference: @internalsref{StringNumber}.
1729 @node Tablatures basic
1730 @subsection Tablatures basic
1731 @cindex Tablatures basic
1733 Tablature notation is used for notating music for plucked string
1734 instruments. Pitches are not denoted with note heads, but by
1735 numbers indicating on which string and fret a note must be played. LilyPond
1736 offers limited support for tablature.
1738 The string number associated to a note is given as a backslash
1739 followed by a number, e.g., @code{c4\3} for a C quarter on the third
1740 string. By default, string 1 is the highest one, and the tuning
1741 defaults to the standard guitar tuning (with 6 strings). The notes
1742 are printed as tablature, by using @internalsref{TabStaff} and
1743 @internalsref{TabVoice} contexts
1745 @lilypond[quote,raggedright,fragment,verbatim]
1752 @cindex @code{minimumFret}
1755 When no string is specified, the first string that does not give a
1756 fret number less than @code{minimumFret} is selected. The default
1757 value for @code{minimumFret} is 0
1762 \set TabStaff.minimumFret = #8
1765 @lilypond[quote,raggedright]
1769 \set TabStaff.minimumFret = #8
1772 \context StaffGroup <<
1773 \context Staff { \clef "G_8" \frag }
1774 \context TabStaff { \frag }
1780 Program reference: @internalsref{TabStaff}, @internalsref{TabVoice}.
1784 Chords are not handled in a special way, and hence the automatic
1785 string selector may easily select the same string to two notes in a
1789 @node Non-guitar tablatures
1790 @subsection Non-guitar tablatures
1791 @cindex Non-guitar tablatures
1793 You can change the number of strings, by setting the number of lines
1794 in the @internalsref{TabStaff}.
1796 You can change the tuning of the strings. A string tuning is given as
1797 a Scheme list with one integer number for each string, the number
1798 being the pitch (measured in semitones relative to middle C) of an
1799 open string. The numbers specified for @code{stringTuning} are the
1800 numbers of semitones to subtract or add, starting the specified pitch
1801 by default middle C, in string order. In the next example,
1802 @code{stringTunings} is set for the pitches e, a, d, and g
1804 @lilypond[quote,raggedright,fragment,verbatim]
1805 \context TabStaff <<
1806 \set TabStaff.stringTunings = #'(-5 -10 -15 -20)
1808 a,4 c' a e' e c' a e'
1815 No guitar special effects have been implemented.
1819 Program reference: @internalsref{Tab_note_heads_engraver}.
1823 @subsection Fret diagrams
1824 @cindex fret diagrams
1825 @cindex chord diagrams
1827 Fret diagrams can be added to music as a markup to the desired note. The
1828 markup contains information about the desired fret diagram, as shown in the
1831 @lilypond[verbatim, raggedright, quote]
1833 d'^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
1835 fis'^\markup \override #'(size . 0.75) {
1836 \override #'(finger-code . below-string) {
1837 \fret-diagram-verbose #'((place-fret 6 2 1) (barre 6 1 2)
1838 (place-fret 5 4 3) (place-fret 4 4 4)
1839 (place-fret 3 3 2) (place-fret 2 2 1)
1844 c'^\markup \override #'(dot-radius . 0.35) {
1845 \override #'(finger-code . in-dot) {
1846 \override #'(dot-color . white) {
1847 \fret-diagram-terse #"x;3-1-(;5-2;5-3;5-4;3-1-);"
1856 There are three different fret-diagram markup interfaces: standard, terse,
1857 and verbose. The three interfaces produce equivalent markups, but have
1858 varying amounts of information in the markup string. Details about the
1859 markup interfaces are found at @ref{Overview of text markup commands}.
1861 You can set a number of graphical properties according to your preference.
1862 Details about the property interface to fret diagrams are found at
1863 @internalsref{fret-diagram-interface}.
1868 Examples: @inputfileref{input/@/test,fret@/-diagram@/.ly}
1871 @node Other guitar issues
1872 @subsection Other guitar issues
1874 This example demonstrates how to include guitar position and
1875 barring indications.
1877 @lilypond[quote,raggedright,fragment,verbatim,relative=0]
1881 \override TextSpanner #'edge-text = #'("XII " . "")
1883 b16 e16 g16 e16 b16 g16\stopTextSpan
1888 Stopped (X) note heads are used in guitar music to signal a place where the
1889 guitarist must play a certain note or chord, with its fingers just
1890 touching the strings instead of fully pressing them. This gives the sound a
1891 percussive noise-like sound that still maintains part of the original
1892 pitch. It is notated with cross noteheads; this is
1893 demonstrated in @ref{Special noteheads}.
1902 * Bagpipe definitions::
1907 @node Bagpipe definitions
1908 @subsection Bagpipe definitions
1910 LilyPond contains special definitions for music for the Scottish
1911 highland bagpipe; to use them, add
1914 \include "bagpipe.ly"
1918 at the top of your input file. This lets you add the special gracenotes
1919 common to bagpipe music with short commands. For example, you could
1920 write @code{\taor} instead of
1923 \grace @{ \small G32[ d G e] @}
1926 @code{bagpipe.ly} also contains pitch definitions for the bagpipe
1927 notes in the appropiate octaves, so you do not need to worry about
1928 @code{\relative} or @code{\transpose}.
1930 @lilypond[raggedright,verbatim,quote,notime]
1931 \include "bagpipe.ly"
1932 { \grg G4 \grg a \grg b \grg c \grg d \grg e \grg f \grA g A }
1936 @node Bagpipe example
1937 @subsection Bagpipe example
1939 This is what the well known tune Amazing Grace looks like in bagpipe
1942 @lilypond[raggedright,verbatim,quote]
1943 \include "bagpipe.ly"
1946 \context { \Score \remove "Bar_number_engraver" }
1949 title = "Amazing Grace"
1951 arranger = "Trad. arr."
1956 \grg \partial 4 a8. d16
1957 \slurd d2 \grg f8[ e32 d16.]
1960 \grG a2 \grg a8. d16
1961 \slurd d2 \grg f8[ e32 d16.]
1962 \grg f2 \grg e8. f16
1965 \grg A2 \hdblf f8[ e32 d16.]
1968 \grG a2 \grg a8. d16
1969 \slurd d2 \grg f8[ e32 d16.]
1978 @node Ancient notation
1979 @section Ancient notation
1981 @cindex Vaticana, Editio
1982 @cindex Medicaea, Editio
1987 Support for ancient notation includes features for mensural notation
1988 and Gregorian Chant notation. There is also limited support for
1989 figured bass notation.
1991 Many graphical objects provide a @code{style} property, see
1994 @ref{Ancient note heads},
1996 @ref{Ancient accidentals},
1998 @ref{Ancient rests},
2000 @ref{Ancient clefs},
2002 @ref{Ancient flags},
2004 @ref{Ancient time signatures}.
2007 By manipulating such a grob property, the typographical appearance of
2008 the affected graphical objects can be accommodated for a specific
2009 notation flavor without the need for introducing any new notational
2012 In addition to the standard articulation signs described in section
2013 @ref{Articulations}, specific articulation signs for ancient notation
2018 @ref{Ancient articulations}
2021 Other aspects of ancient notation can not that easily be expressed
2022 in terms of just changing a style property of a graphical object or
2023 adding articulation signs. Some notational concepts are introduced
2024 specifically for ancient notation,
2035 If this all is too much of documentation for you, and you just want to
2036 dive into typesetting without worrying too much about the details on
2037 how to customize a context, you may have a look at the predefined
2038 contexts. Use them to set up predefined style-specific voice and
2039 staff contexts, and directly go ahead with the note entry,
2043 @ref{Gregorian Chant contexts},
2045 @ref{Mensural contexts}.
2048 There is limited support for figured bass notation which came
2049 up during the baroque period.
2056 Here are all suptopics at a glance:
2059 * Ancient note heads::
2060 * Ancient accidentals::
2064 * Ancient time signatures::
2065 * Ancient articulations::
2069 * Gregorian Chant contexts::
2070 * Mensural contexts::
2071 * Musica ficta accidentals::
2077 @node Ancient note heads
2078 @subsection Ancient note heads
2083 For ancient notation, a note head style other than the @code{default}
2084 style may be chosen. This is accomplished by setting the @code{style}
2085 property of the @internalsref{NoteHead} object to @code{baroque},
2086 @code{neomensural}, @code{mensural} or @code{petrucci}. The
2087 @code{baroque} style differs from the @code{default} style only in
2088 using a square shape for @code{\breve} note heads. The
2089 @code{neomensural} style differs from the @code{baroque} style in that
2090 it uses rhomboidal heads for whole notes and all smaller durations.
2091 Stems are centered on the note heads. This style is particularly
2092 useful when transcribing mensural music, e.g., for the incipit. The
2093 @code{mensural} style produces note heads that mimic the look of note
2094 heads in historic printings of the 16th century. Finally, the
2095 @code{petrucci} style also mimicks historic printings, but uses bigger
2098 The following example demonstrates the @code{neomensural} style
2100 @lilypond[quote,fragment,raggedright,verbatim]
2101 \set Score.skipBars = ##t
2102 \override NoteHead #'style = #'neomensural
2103 a'\longa a'\breve a'1 a'2 a'4 a'8 a'16
2106 When typesetting a piece in Gregorian Chant notation, the
2107 @internalsref{Gregorian_ligature_engraver} will automatically select
2108 the proper note heads, so there is no need to explicitly set the
2109 note head style. Still, the note head style can be set, e.g., to
2110 @code{vaticana_punctum} to produce punctum neumes. Similarly, a
2111 @internalsref{Mensural_ligature_engraver} is used to automatically
2112 assemble mensural ligatures. See @ref{Ligatures} for how ligature
2117 Examples: @inputfileref{input/@/regression,note@/-head@/-style@/.ly} gives an
2118 overview over all available note head styles.
2121 @node Ancient accidentals
2122 @subsection Ancient accidentals
2127 Use the @code{style} property of grob @internalsref{Accidental} to
2128 select ancient accidentals. Supported styles are
2129 @code{mensural}, @code{vaticana}, @code{hufnagel}, and @code{medicaea}.
2131 @lilypond[quote,raggedright,staffsize=26]
2138 \line { " " \musicglyph #"accidentals.vaticana-1"
2139 " " \musicglyph #"accidentals.vaticana0" }
2143 \line { " " \musicglyph #"accidentals.medicaea-1" }
2147 \line { " " \musicglyph #"accidentals.hufnagel-1" }
2151 \line { " " \musicglyph #"accidentals.mensural-1"
2152 " " \musicglyph #"accidentals.mensural1" }
2158 \context { \Score \remove "Bar_number_engraver" }
2160 \remove "Clef_engraver"
2161 \remove "Key_engraver"
2162 \remove "Time_signature_engraver"
2163 \remove "Staff_symbol_engraver"
2164 minimumVerticalExtent = ##f
2170 As shown, not all accidentals are supported by each style. When
2171 trying to access an unsupported accidental, LilyPond will switch to a
2172 different style, as demonstrated in
2173 @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
2175 Similarly to local accidentals, the style of the key signature can be
2176 controlled by the @code{style} property of the
2177 @internalsref{KeySignature} grob.
2181 In this manual: @ref{Pitches}, @ref{Cautionary accidentals} and
2182 @ref{Automatic accidentals} give a general introduction of the use of
2183 accidentals. @ref{Key signature} gives a general introduction of
2184 the use of key signatures.
2186 Program reference: @internalsref{KeySignature}.
2188 Examples: @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
2191 @subsection Ancient rests
2193 @cindex rests, ancient
2196 Use the @code{style} property of grob @internalsref{Rest} to select
2197 ancient rests. Supported styles are @code{classical},
2198 @code{neomensural}, and @code{mensural}. @code{classical} differs
2199 from the @code{default} style only in that the quarter rest looks like
2200 a horizontally mirrored 8th rest. The @code{neomensural} style suits
2201 well for, e.g., the incipit of a transcribed mensural piece of music.
2202 The @code{mensural} style finally mimics the appearance of rests as
2203 in historic prints of the 16th century.
2205 The following example demonstrates the @code{neomensural} style
2207 @lilypond[quote,fragment,raggedright,verbatim]
2208 \set Score.skipBars = ##t
2209 \override Rest #'style = #'neomensural
2210 r\longa r\breve r1 r2 r4 r8 r16
2213 There are no 32th and 64th rests specifically for the mensural or
2214 neo-mensural style. Instead, the rests from the default style will be
2215 taken. See @inputfileref{input/@/test,rests@/.ly} for a chart of all
2218 There are no rests in Gregorian Chant notation; instead, it uses
2223 In this manual: @ref{Rests} gives a general introduction into the use of rests.
2227 @subsection Ancient clefs
2232 LilyPond supports a variety of clefs, many of them ancient.
2234 The following table shows all ancient clefs that are supported via the
2235 @code{\clef} command. Some of the clefs use the same glyph, but
2236 differ only with respect to the line they are printed on. In such
2237 cases, a trailing number in the name is used to enumerate these clefs.
2238 Still, you can manually force a clef glyph to be typeset on an
2239 arbitrary line, as described in @ref{Clef}. The note printed to the
2240 right side of each clef in the example column denotes the @code{c'}
2241 with respect to that clef.
2243 @multitable @columnfractions .4 .4 .2
2252 modern style mensural C clef
2254 @code{neomensural-c1}, @code{neomensural-c2},@*
2255 @code{neomensural-c3}, @code{neomensural-c4}
2257 @lilypond[fragment,relative=1,notime]
2258 \clef "neomensural-c2" c
2262 petrucci style mensural C clefs, for use on different staff lines
2263 (the examples show the 2nd staff line C clef)
2265 @code{petrucci-c1}, @code{petrucci-c2},@*
2266 @code{petrucci-c3}, @code{petrucci-c4},@*
2269 @lilypond[fragment,relative=1,notime]
2271 \override NoteHead #'style = #'mensural
2276 petrucci style mensural F clef
2280 @lilypond[fragment,relative=1,notime]
2282 \override NoteHead #'style = #'mensural
2287 petrucci style mensural G clef
2291 @lilypond[fragment,relative=1,notime]
2293 \override NoteHead #'style = #'mensural
2298 historic style mensural C clef
2300 @code{mensural-c1}, @code{mensural-c2},@*
2301 @code{mensural-c3}, @code{mensural-c4}
2303 @lilypond[fragment,relative=1,notime]
2305 \override NoteHead #'style = #'mensural
2310 historic style mensural F clef
2314 @lilypond[fragment,relative=1,notime]
2316 \override NoteHead #'style = #'mensural
2321 historic style mensural G clef
2325 @lilypond[fragment,relative=1,notime]
2327 \override NoteHead #'style = #'mensural
2332 Editio Vaticana style do clef
2334 @code{vaticana-do1}, @code{vaticana-do2},@*
2337 @lilypond[fragment,relative=1,notime]
2338 \override Staff.StaffSymbol #'line-count = #4
2339 \override Staff.StaffSymbol #'color = #red
2340 \override Staff.LedgerLineSpanner #'color = #red
2341 \override Voice.Stem #'transparent = ##t
2342 \override NoteHead #'style = #'vaticana.punctum
2343 \clef "vaticana-do2"
2348 Editio Vaticana style fa clef
2350 @code{vaticana-fa1}, @code{vaticana-fa2}
2352 @lilypond[fragment,relative=1,notime]
2353 \override Staff.StaffSymbol #'line-count = #4
2354 \override Staff.StaffSymbol #'color = #red
2355 \override Staff.LedgerLineSpanner #'color = #red
2356 \override Voice.Stem #'transparent = ##t
2357 \override NoteHead #'style = #'vaticana.punctum
2358 \clef "vaticana-fa2"
2363 Editio Medicaea style do clef
2365 @code{medicaea-do1}, @code{medicaea-do2},@*
2368 @lilypond[fragment,relative=1,notime]
2369 \override Staff.StaffSymbol #'line-count = #4
2370 \override Staff.StaffSymbol #'color = #red
2371 \override Staff.LedgerLineSpanner #'color = #red
2372 \override Voice.Stem #'transparent = ##t
2373 \override NoteHead #'style = #'medicaea.punctum
2374 \clef "medicaea-do2"
2379 Editio Medicaea style fa clef
2381 @code{medicaea-fa1}, @code{medicaea-fa2}
2383 @lilypond[fragment,relative=1,notime]
2384 \override Staff.StaffSymbol #'line-count = #4
2385 \override Staff.StaffSymbol #'color = #red
2386 \override Staff.LedgerLineSpanner #'color = #red
2387 \override Voice.Stem #'transparent = ##t
2388 \override NoteHead #'style = #'medicaea.punctum
2389 \clef "medicaea-fa2"
2394 historic style hufnagel do clef
2396 @code{hufnagel-do1}, @code{hufnagel-do2},@*
2399 @lilypond[fragment,relative=1,notime]
2400 \override Staff.StaffSymbol #'line-count = #4
2401 \override Staff.StaffSymbol #'color = #red
2402 \override Staff.LedgerLineSpanner #'color = #red
2403 \override Voice.Stem #'transparent = ##t
2404 \override NoteHead #'style = #'hufnagel.punctum
2405 \clef "hufnagel-do2"
2410 historic style hufnagel fa clef
2412 @code{hufnagel-fa1}, @code{hufnagel-fa2}
2414 @lilypond[fragment,relative=1,notime]
2415 \override Staff.StaffSymbol #'line-count = #4
2416 \override Staff.StaffSymbol #'color = #red
2417 \override Staff.LedgerLineSpanner #'color = #red
2418 \override Voice.Stem #'transparent = ##t
2419 \override NoteHead #'style = #'hufnagel.punctum
2420 \clef "hufnagel-fa2"
2425 historic style hufnagel combined do/fa clef
2427 @code{hufnagel-do-fa}
2429 @lilypond[fragment,relative=1,notime]
2430 \override Staff.StaffSymbol #'color = #red
2431 \override Staff.LedgerLineSpanner #'color = #red
2432 \override Voice.Stem #'transparent = ##t
2433 \override NoteHead #'style = #'hufnagel.punctum
2434 \clef "hufnagel-do-fa"
2441 @emph{Modern style} means ``as is typeset in contemporary editions of
2442 transcribed mensural music''.
2444 @emph{Petrucci style} means ``inspired by printings published by the
2445 famous engraver Petrucci (1466-1539)''.
2447 @emph{Historic style} means ``as was typeset or written in historic
2448 editions (other than those of Petrucci)''.
2450 @emph{Editio XXX style} means ``as is/was printed in Editio XXX''.
2452 Petrucci used C clefs with differently balanced left-side vertical
2453 beams, depending on which staff line it is printed.
2457 In this manual: see @ref{Clef}.
2461 The mensural g clef is mapped to the Petrucci g clef.
2466 @subsection Ancient flags
2471 Use the @code{flag-style} property of grob @internalsref{Stem} to
2472 select ancient flags. Besides the @code{default} flag style,
2473 only the @code{mensural} style is supported
2475 @lilypond[quote,fragment,raggedright,verbatim]
2476 \override Stem #'flag-style = #'mensural
2477 \override Stem #'thickness = #1.0
2478 \override NoteHead #'style = #'mensural
2480 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
2481 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
2484 Note that the innermost flare of each mensural flag always is
2485 vertically aligned with a staff line.
2487 There is no particular flag style for neo-mensural notation. Hence,
2488 when typesetting the incipit of a transcribed piece of mensural
2489 music, the default flag style should be used. There are no flags in
2490 Gregorian Chant notation.
2494 The attachment of ancient flags to stems is slightly off due to a
2495 change in early 2.3.x.
2497 Vertically aligning each flag with a staff line assumes that stems
2498 always end either exactly on or exactly in the middle between two
2499 staff lines. This may not always be true when using advanced layout
2500 features of classical notation (which however are typically out of
2501 scope for mensural notation).
2503 @node Ancient time signatures
2504 @subsection Ancient time signatures
2506 @cindex time signatures
2509 There is limited support for mensural time signatures. The
2510 glyphs are hard-wired to particular time fractions. In other words,
2511 to get a particular mensural signature glyph with the @code{\time n/m}
2512 command, @code{n} and @code{m} have to be chosen according to the
2515 @lilypond[quote,raggedright]
2520 \remove Staff_symbol_engraver
2521 \remove Clef_engraver
2522 \remove Time_signature_engraver
2526 \set Score.timing = ##f
2527 \set Score.barAlways = ##t
2528 s_\markup { "\\time 4/4" }^\markup { " " \musicglyph #"timesig.neomensural44" }
2530 s_\markup { "\\time 2/2" }^\markup { " " \musicglyph #"timesig.neomensural22" }
2532 s_\markup { "\\time 6/4" }^\markup { " " \musicglyph #"timesig.neomensural64" }
2534 s_\markup { "\\time 6/8" }^\markup { " " \musicglyph #"timesig.neomensural68" }
2536 s_\markup { "\\time 3/2" }^\markup { " " \musicglyph #"timesig.neomensural32" }
2538 s_\markup { "\\time 3/4" }^\markup { " " \musicglyph #"timesig.neomensural34" }
2540 s_\markup { "\\time 9/4" }^\markup { " " \musicglyph #"timesig.neomensural94" }
2542 s_\markup { "\\time 9/8" }^\markup { " " \musicglyph #"timesig.neomensural98" }
2544 s_\markup { "\\time 4/8" }^\markup { " " \musicglyph #"timesig.neomensural48" }
2546 s_\markup { "\\time 2/4" }^\markup { " " \musicglyph #"timesig.neomensural24" }
2550 Use the @code{style} property of grob @internalsref{TimeSignature} to
2551 select ancient time signatures. Supported styles are
2552 @code{neomensural} and @code{mensural}. The above table uses the
2553 @code{neomensural} style. This style is appropriate for the
2554 incipit of transcriptions of mensural pieces. The @code{mensural}
2555 style mimics the look of historical printings of the 16th century.
2557 The following examples show the differences in style,
2559 @lilypond[raggedright,fragment,relative=1,quote]
2564 c1^\markup { \hspace #-2.0 \typewriter default }
2566 \override Staff.TimeSignature #'style = #'numbered
2568 c1^\markup { \hspace #-2.0 \typewriter numbered }
2570 \override Staff.TimeSignature #'style = #'mensural
2572 c1^\markup { \hspace #-2.0 \typewriter mensural }
2574 \override Staff.TimeSignature #'style = #'neomensural
2576 c1^\markup { \hspace #-2.0 \typewriter neomensural }
2577 \override Staff.TimeSignature #'style = #'single-digit
2579 c1^\markup { \hspace #-2.0 \typewriter single-digit }
2585 This manual: @ref{Time signature} gives a general introduction to
2586 the use of time signatures.
2590 Ratios of note durations do not change with the time signature. For
2591 example, the ratio of 1 brevis = 3 semibrevis (tempus perfectum) must
2592 be made by hand, by setting
2595 breveTP = #(ly:make-duration -1 0 3 2)
2601 This sets @code{breveTP} to 3/2 times 2 = 3 times a whole note.
2603 The @code{old6/8alt} symbol (an alternate symbol for 6/8) is not
2604 addressable with @code{\time}. Use a @code{\markup} instead
2606 @node Ancient articulations
2607 @subsection Ancient articulations
2609 @cindex articulations
2611 In addition to the standard articulation signs described in section
2612 @ref{Articulations}, articulation signs for ancient notation are
2613 provided. These are specifically designed for use with notation in
2614 Editio Vaticana style.
2616 @lilypond[quote,raggedright,verbatim]
2617 \include "gregorian-init.ly"
2619 \context VaticanaVoice {
2620 \override Staff.StaffSymbol #'color = #red
2621 \override Staff.LedgerLineSpanner #'color = #red
2622 \override TextScript #'font-family = #'typewriter
2623 \override TextScript #'font-shape = #'upright
2624 \override Script #'padding = #-0.1
2626 a4\circulus_"circulus" s1
2627 a4\semicirculus_"semicirculus" s1 s
2628 a4\accentus_"accentus" s1
2629 \[ a4_"episem" \episemInitium \pes b \flexa a \episemFinis \]
2636 Some articulations are vertically placed too closely to the
2637 correpsonding note heads.
2640 @subsection Custodes
2645 A @emph{custos} (plural: @emph{custodes}; Latin word for `guard') is a
2646 symbol that appears at the end of a staff. It anticipates the pitch
2647 of the first note(s) of the following line thus helping the performer
2648 to manage line breaks during performance.
2650 Custodes were frequently used in music notation until the 17th
2651 century. Nowadays, they have survived only in a few particular forms
2652 of musical notation such as contemporary editions of Gregorian chant
2653 like the @emph{editio vaticana}. There are different custos glyphs
2654 used in different flavors of notational style.
2656 For typesetting custodes, just put a @internalsref{Custos_engraver} into the
2657 @internalsref{Staff} context when declaring the @code{\layout} block,
2658 as shown in the following example
2664 \consists Custos_engraver
2665 Custos \override #'style = #'mensural
2670 The result looks like this
2672 @lilypond[quote,raggedright]
2676 \override Staff.Custos #'style = #'mensural
2681 \context { \Staff \consists Custos_engraver }
2686 The custos glyph is selected by the @code{style} property. The styles
2687 supported are @code{vaticana}, @code{medicaea}, @code{hufnagel}, and
2688 @code{mensural}. They are demonstrated in the following fragment
2690 @lilypond[quote,raggedright,fragment]
2691 \new Lyrics \lyricmode {
2693 \typewriter "vaticana"
2694 \line { " " \musicglyph #"custodes.vaticana.u0" }
2697 \typewriter "medicaea"
2698 \line { " " \musicglyph #"custodes.medicaea.u0" }
2701 \typewriter "hufnagel"
2702 \line { " " \musicglyph #"custodes.hufnagel.u0" }
2705 \typewriter "mensural"
2706 \line { " " \musicglyph #"custodes.mensural.u0" }
2713 Program reference: @internalsref{Custos}.
2715 Examples: @inputfileref{input/@/regression,custos@/.ly}.
2719 @subsection Divisiones
2725 A @emph{divisio} (plural: @emph{divisiones}; Latin word for
2726 `division') is a staff context symbol that is used to structure
2727 Gregorian music into phrases and sections. The musical meaning of
2728 @emph{divisio minima}, @emph{divisio maior}, and @emph{divisio maxima}
2729 can be characterized as short, medium, and long pause, somewhat like
2730 the breathmarks from @ref{Breath marks}. The @emph{finalis} sign not
2731 only marks the end of a chant, but is also frequently used within a
2732 single antiphonal/responsorial chant to mark the end of each section.
2735 To use divisiones, include the file @file{gregorian@/-init@/.ly}. It
2736 contains definitions that you can apply by just inserting
2737 @code{\divisioMinima}, @code{\divisioMaior}, @code{\divisioMaxima},
2738 and @code{\finalis} at proper places in the input. Some editions use
2739 @emph{virgula} or @emph{caesura} instead of divisio minima.
2740 Therefore, @file{gregorian@/-init@/.ly} also defines @code{\virgula} and
2743 @lilypondfile[quote,raggedright]{divisiones.ly}
2747 @cindex @code{\virgula}
2749 @cindex @code{\caesura}
2751 @cindex @code{\divisioMinima}
2752 @code{\divisioMinima},
2753 @cindex @code{\divisioMaior}
2754 @code{\divisioMaior},
2755 @cindex @code{\divisioMaxima}
2756 @code{\divisioMaxima},
2757 @cindex @code{\finalis}
2762 In this manual: @ref{Breath marks}.
2764 Program reference: @internalsref{BreathingSign}.
2766 Examples: @inputfileref{input/@/test,divisiones@/.ly}.
2769 @subsection Ligatures
2773 @c TODO: Should double check if I recalled things correctly when I wrote
2774 @c down the following paragraph by heart.
2776 A ligature is a graphical symbol that represents at least two distinct
2777 notes. Ligatures originally appeared in the manuscripts of Gregorian
2778 chant notation to denote ascending or descending sequences of notes.
2780 Ligatures are entered by enclosing them in @code{\[} and @code{\]}.
2781 Some ligature styles may need additional input syntax specific for
2782 this particular type of ligature. By default, the
2783 @internalsref{LigatureBracket} engraver just puts a square bracket
2786 @lilypond[quote,raggedright,verbatim]
2794 To select a specific style of ligatures, a proper ligature engraver
2795 has to be added to the @internalsref{Voice} context, as explained in
2796 the following subsections. Only white mensural ligatures
2797 are supported with certain limitations.
2803 Ligatures need special spacing that has not yet been implemented. As
2804 a result, there is too much space between ligatures most of the time,
2805 and line breaking often is unsatisfactory. Also, lyrics do not
2806 correctly align with ligatures.
2808 Accidentals must not be printed within a ligature, but instead need to
2809 be collected and printed in front of it.
2811 Augmentum dots within ligatures are not handled correctly.
2813 The syntax still uses the deprecated infix style @code{\[ music expr
2814 \]}. For consistency reasons, it will eventually be changed to
2815 postfix style @code{note\[ ... note\]}. Alternatively, the file
2816 @file{gregorian@/-init@/.ly} can be included; it provides a scheme
2819 \ligature @var{music expr}
2821 with the same effect and is believed to be stable.
2824 * White mensural ligatures::
2825 * Gregorian square neumes ligatures::
2828 @node White mensural ligatures
2829 @subsubsection White mensural ligatures
2831 @cindex Mensural ligatures
2832 @cindex White mensural ligatures
2834 There is limited support for white mensural ligatures.
2836 To engrave white mensural ligatures, in the layout block put the
2837 @internalsref{Mensural_ligature_engraver} into the
2838 @internalsref{Voice} context, and remove the
2839 @internalsref{Ligature_bracket_engraver}, like this
2845 \remove Ligature_bracket_engraver
2846 \consists Mensural_ligature_engraver
2851 There is no additional input language to describe the shape of a
2852 white mensural ligature. The shape is rather determined solely from
2853 the pitch and duration of the enclosed notes. While this approach may
2854 take a new user a while to get accustomed to, it has the great advantage
2855 that the full musical information of the ligature is known internally.
2856 This is not only required for correct MIDI output, but also allows for
2857 automatic transcription of the ligatures.
2862 \set Score.timing = ##f
2863 \set Score.defaultBarType = "empty"
2864 \override NoteHead #'style = #'neomensural
2865 \override Staff.TimeSignature #'style = #'neomensural
2869 \[ d\longa c\breve f e d \]
2871 \[ c'\maxima d'\longa \]
2875 @lilypond[quote,raggedright]
2878 \set Score.timing = ##f
2879 \set Score.defaultBarType = "empty"
2880 \override NoteHead #'style = #'neomensural
2881 \override Staff.TimeSignature #'style = #'neomensural
2885 \[ d\longa c\breve f e d \]
2887 \[ c'\maxima d'\longa \]
2894 \remove Ligature_bracket_engraver
2895 \consists Mensural_ligature_engraver
2901 Without replacing @internalsref{Ligature_bracket_engraver} with
2902 @internalsref{Mensural_ligature_engraver}, the same music transcribes
2905 @lilypond[quote,raggedright]
2907 \set Score.timing = ##f
2908 \set Score.defaultBarType = "empty"
2909 \override NoteHead #'style = #'neomensural
2910 \override Staff.TimeSignature #'style = #'neomensural
2914 \[ d\longa c\breve f e d \]
2916 \[ c'\maxima d'\longa \]
2924 The invisible rests (@code{s4}) in the example are used to compensate
2925 for the poor horizontal spacing.
2927 @node Gregorian square neumes ligatures
2928 @subsubsection Gregorian square neumes ligatures
2930 @cindex Square neumes ligatures
2931 @cindex Gregorian square neumes ligatures
2933 There is limited support for Gregorian square neumes notation
2934 (following the style of the Editio Vaticana). Core ligatures can
2935 already be typeset, but essential issues for serious typesetting are
2936 still lacking, such as (among others) horizontal alignment of multiple
2937 ligatures, lyrics alignment and proper handling of accidentals.
2940 The following table contains the extended neumes table of the 2nd
2941 volume of the Antiphonale Romanum (@emph{Liber Hymnarius}), published
2942 1983 by the monks of Solesmes.
2944 @multitable @columnfractions .4 .2 .2 .2
2961 @c TODO: \layout block is identical in all of the below examples.
2962 @c Therefore, it should somehow be included rather than duplicated all
2965 @c why not make identifiers in ly/engraver-init.ly? --hwn
2967 @c Because it's just used to typeset plain notes without
2968 @c a staff for demonstration purposes rather than something
2969 @c special of Gregorian chant notation. --jr
2974 @lilypond[staffsize=26,linewidth=1.5\cm]
2975 \include "gregorian-init.ly"
2980 \noBreak s^\markup {"a"} \noBreak
2982 % Punctum Inclinatum
2984 \noBreak s^\markup {"b"}
2986 \layout { \neumeDemoLayout }}
2989 @lilypond[staffsize=26,linewidth=2.5\cm]
2990 \include "gregorian-init.ly"
2993 % Punctum Auctum Ascendens
2994 \[ \auctum \ascendens b \]
2995 \noBreak s^\markup {"c"} \noBreak
2997 % Punctum Auctum Descendens
2998 \[ \auctum \descendens b \]
2999 \noBreak s^\markup {"d"} \noBreak
3001 % Punctum Inclinatum Auctum
3002 \[ \inclinatum \auctum b \]
3003 \noBreak s^\markup {"e"}
3005 \layout { \neumeDemoLayout }}
3008 @lilypond[staffsize=26,linewidth=1.0\cm]
3009 \include "gregorian-init.ly"
3012 % Punctum Inclinatum Parvum
3013 \[ \inclinatum \deminutum b \]
3014 \noBreak s^\markup {"f"}
3016 \layout { \neumeDemoLayout }}
3022 @lilypond[staffsize=26,linewidth=1.0\cm]
3023 \include "gregorian-init.ly"
3028 \noBreak s^\markup {"g"}
3030 \layout { \neumeDemoLayout }}
3036 @code{3. Apostropha vel Stropha}
3038 @lilypond[staffsize=26,linewidth=1.0\cm]
3039 \include "gregorian-init.ly"
3044 \noBreak s^\markup {"h"}
3046 \layout { \neumeDemoLayout }}
3049 @lilypond[staffsize=26,linewidth=1.0\cm]
3050 \include "gregorian-init.ly"
3054 \[ \stropha \auctum b \]
3055 \noBreak s^\markup {"i"}
3057 \layout { \neumeDemoLayout }}
3064 @lilypond[staffsize=26,linewidth=1.0\cm]
3065 \include "gregorian-init.ly"
3070 \noBreak s^\markup {"j"}
3072 \layout { \neumeDemoLayout }}
3078 @code{5. Clivis vel Flexa}
3080 @lilypond[staffsize=26,linewidth=1.0\cm]
3081 \include "gregorian-init.ly"
3088 \layout { \neumeDemoLayout }}
3091 @lilypond[staffsize=26,linewidth=2.0\cm]
3092 \include "gregorian-init.ly"
3095 % Clivis Aucta Descendens
3096 \[ b \flexa \auctum \descendens g \]
3097 \noBreak s^\markup {"l"} \noBreak
3099 % Clivis Aucta Ascendens
3100 \[ b \flexa \auctum \ascendens g \]
3101 \noBreak s^\markup {"m"}
3103 \layout { \neumeDemoLayout }}
3106 @lilypond[staffsize=26,linewidth=1.0\cm]
3107 \include "gregorian-init.ly"
3111 \[ b \flexa \deminutum g \]
3114 \layout { \neumeDemoLayout }}
3118 @code{6. Podatus vel Pes}
3120 @lilypond[staffsize=26,linewidth=1.0\cm]
3121 \include "gregorian-init.ly"
3128 \layout { \neumeDemoLayout }}
3131 @lilypond[staffsize=26,linewidth=2.0\cm]
3132 \include "gregorian-init.ly"
3135 % Pes Auctus Descendens
3136 \[ g \pes \auctum \descendens b \]
3137 \noBreak s^\markup {"p"} \noBreak
3139 % Pes Auctus Ascendens
3140 \[ g \pes \auctum \ascendens b \]
3141 \noBreak s^\markup {"q"}
3143 \layout { \neumeDemoLayout }}
3146 @lilypond[staffsize=26,linewidth=1.0\cm]
3147 \include "gregorian-init.ly"
3151 \[ g \pes \deminutum b \]
3154 \layout { \neumeDemoLayout }}
3158 @code{7. Pes Quassus}
3160 @lilypond[staffsize=26,linewidth=1.0\cm]
3161 \include "gregorian-init.ly"
3165 \[ \oriscus g \pes \virga b \]
3168 \layout { \neumeDemoLayout }}
3171 @lilypond[staffsize=26,linewidth=1.0\cm]
3172 \include "gregorian-init.ly"
3175 % Pes Quassus Auctus Descendens
3176 \[ \oriscus g \pes \auctum \descendens b \]
3179 \layout { \neumeDemoLayout }}
3184 @code{8. Quilisma Pes}
3186 @lilypond[staffsize=26,linewidth=1.0\cm]
3187 \include "gregorian-init.ly"
3191 \[ \quilisma g \pes b \]
3194 \layout { \neumeDemoLayout }}
3197 @lilypond[staffsize=26,linewidth=1.0\cm]
3198 \include "gregorian-init.ly"
3201 % Quilisma Pes Auctus Descendens
3202 \[ \quilisma g \pes \auctum \descendens b \]
3205 \layout { \neumeDemoLayout }}
3210 @code{9. Podatus Initio Debilis}
3212 @lilypond[staffsize=26,linewidth=1.0\cm]
3213 \include "gregorian-init.ly"
3216 % Pes Initio Debilis
3217 \[ \deminutum g \pes b \]
3220 \layout { \neumeDemoLayout }}
3223 @lilypond[staffsize=26,linewidth=1.0\cm]
3224 \include "gregorian-init.ly"
3227 % Pes Auctus Descendens Initio Debilis
3228 \[ \deminutum g \pes \auctum \descendens b \]
3231 \layout { \neumeDemoLayout }}
3238 @lilypond[staffsize=26,linewidth=1.0\cm]
3239 \include "gregorian-init.ly"
3243 \[ a \pes b \flexa g \]
3246 \layout { \neumeDemoLayout }}
3249 @lilypond[staffsize=26,linewidth=1.0\cm]
3250 \include "gregorian-init.ly"
3253 % Torculus Auctus Descendens
3254 \[ a \pes b \flexa \auctum \descendens g \]
3257 \layout { \neumeDemoLayout }}
3260 @lilypond[staffsize=26,linewidth=1.0\cm]
3261 \include "gregorian-init.ly"
3264 % Torculus Deminutus
3265 \[ a \pes b \flexa \deminutum g \]
3268 \layout { \neumeDemoLayout }}
3272 @code{11. Torculus Initio Debilis}
3274 @lilypond[staffsize=26,linewidth=1.0\cm]
3275 \include "gregorian-init.ly"
3278 % Torculus Initio Debilis
3279 \[ \deminutum a \pes b \flexa g \]
3282 \layout { \neumeDemoLayout }}
3285 @lilypond[staffsize=26,linewidth=1.0\cm]
3286 \include "gregorian-init.ly"
3289 % Torculus Auctus Descendens Initio Debilis
3290 \[ \deminutum a \pes b \flexa \auctum \descendens g \]
3293 \layout { \neumeDemoLayout }}
3296 @lilypond[staffsize=26,linewidth=1.0\cm]
3297 \include "gregorian-init.ly"
3300 % Torculus Deminutus Initio Debilis
3301 \[ \deminutum a \pes b \flexa \deminutum g \]
3304 \layout { \neumeDemoLayout }}
3308 @code{12. Porrectus}
3310 @lilypond[staffsize=26,linewidth=1.0\cm]
3311 \include "gregorian-init.ly"
3315 \[ a \flexa g \pes b \]
3318 \layout { \neumeDemoLayout }}
3321 @lilypond[staffsize=26,linewidth=1.0\cm]
3322 \include "gregorian-init.ly"
3325 % Porrectus Auctus Descendens
3326 \[ a \flexa g \pes \auctum \descendens b \]
3329 \layout { \neumeDemoLayout }}
3332 @lilypond[staffsize=26,linewidth=1.0\cm]
3333 \include "gregorian-init.ly"
3336 % Porrectus Deminutus
3337 \[ a \flexa g \pes \deminutum b \]
3340 \layout { \neumeDemoLayout }}
3346 @lilypond[staffsize=26,linewidth=1.0\cm]
3347 \include "gregorian-init.ly"
3351 \[ \virga b \inclinatum a \inclinatum g \]
3354 \layout { \neumeDemoLayout }
3358 @lilypond[staffsize=26,linewidth=1.0\cm]
3359 \include "gregorian-init.ly"
3363 \[ \virga b \inclinatum a \inclinatum \auctum g \]
3366 \layout { \neumeDemoLayout }}
3369 @lilypond[staffsize=26,linewidth=1.0\cm]
3370 \include "gregorian-init.ly"
3373 % Climacus Deminutus
3374 \[ \virga b \inclinatum a \inclinatum \deminutum g \]
3377 \layout { \neumeDemoLayout }}
3381 @code{14. Scandicus}
3383 @lilypond[staffsize=26,linewidth=1.0\cm]
3384 \include "gregorian-init.ly"
3388 \[ g \pes a \virga b \]
3391 \layout { \neumeDemoLayout }}
3394 @lilypond[staffsize=26,linewidth=1.0\cm]
3395 \include "gregorian-init.ly"
3398 % Scandicus Auctus Descendens
3399 \[ g \pes a \pes \auctum \descendens b \]
3402 \layout { \neumeDemoLayout }}
3405 @lilypond[staffsize=26,linewidth=1.0\cm]
3406 \include "gregorian-init.ly"
3409 % Scandicus Deminutus
3410 \[ g \pes a \pes \deminutum b \]
3413 \layout { \neumeDemoLayout }}
3419 @lilypond[staffsize=26,linewidth=1.0\cm]
3420 \include "gregorian-init.ly"
3424 \[ g \oriscus a \pes \virga b \]
3427 \layout { \neumeDemoLayout }}
3430 @lilypond[staffsize=26,linewidth=1.0\cm]
3431 \include "gregorian-init.ly"
3434 % Salicus Auctus Descendens
3435 \[ g \oriscus a \pes \auctum \descendens b \]
3438 \layout { \neumeDemoLayout }}
3445 @lilypond[staffsize=26,linewidth=1.0\cm]
3446 \include "gregorian-init.ly"
3450 \[ \stropha b \stropha b \stropha a \]
3453 \layout { \neumeDemoLayout }
3462 Unlike most other neumes notation systems, the input language for
3463 neumes does not reflect the typographical appearance, but is designed
3464 to focus on musical meaning. For example, @code{\[ a \pes b
3465 \flexa g \]} produces a Torculus consisting of three Punctum heads,
3466 while @code{\[ a \flexa g \pes b \]} produces a Porrectus with a
3467 curved flexa shape and only a single Punctum head. There is no
3468 command to explicitly typeset the curved flexa shape; the decision of
3469 when to typeset a curved flexa shape is based on the musical
3470 input. The idea of this approach is to separate the musical aspects
3471 of the input from the notation style of the output. This way, the
3472 same input can be reused to typeset the same music in a different
3473 style of Gregorian chant notation.
3475 The following table shows the code fragments that produce the
3476 ligatures in the above neumes table. The letter in the first column
3477 in each line of the below table indicates to which ligature in the
3478 above table it refers. The second column gives the name of the
3479 ligature. The third column shows the code fragment that produces this
3480 ligature, using @code{g}, @code{a}, and @code{b} as example pitches.
3482 @multitable @columnfractions .02 .31 .67
3502 @code{\[ \inclinatum b \]}
3510 @code{\[ \auctum \ascendens b \]}
3518 @code{\[ \auctum \descendens b \]}
3523 Punctum Inclinatum@*
3526 @code{\[ \inclinatum \auctum b \]}
3531 Punctum Inclinatum@*
3533 @code{\[ \inclinatum \deminutum b \]}
3540 @code{\[ \virga b \]}
3547 @code{\[ \stropha b \]}
3554 @code{\[ \stropha \auctum b \]}
3561 @code{\[ \oriscus b \]}
3568 @code{\[ b \flexa g \]}
3576 @code{\[ b \flexa \auctum \descendens g \]}
3584 @code{\[ b \flexa \auctum \ascendens g \]}
3591 @code{\[ b \flexa \deminutum g \]}
3598 @code{\[ g \pes b \]}
3606 @code{\[ g \pes \auctum \descendens b \]}
3614 @code{\[ g \pes \auctum \ascendens b \]}
3621 @code{\[ g \pes \deminutum b \]}
3628 @code{\[ \oriscus g \pes \virga b \]}
3634 Auctus Descendens @tab
3635 @code{\[ \oriscus g \pes \auctum \descendens b \]}
3642 @code{\[ \quilisma g \pes b \]}
3650 @code{\[ \quilisma g \pes \auctum \descendens b \]}
3657 @code{\[ \deminutum g \pes b \]}
3662 Pes Auctus Descendens@*
3665 @code{\[ \deminutum g \pes \auctum \descendens b \]}
3672 @code{\[ a \pes b \flexa g \]}
3680 @code{\[ a \pes b \flexa \auctum \descendens g \]}
3687 @code{\[ a \pes b \flexa \deminutum g \]}
3692 Torculus Initio Debilis
3694 @code{\[ \deminutum a \pes b \flexa g \]}
3700 Descendens Initio Debilis
3702 @code{\[ \deminutum a \pes b \flexa \auctum \descendens g \]}
3707 Torculus Deminutus@*
3710 @code{\[ \deminutum a \pes b \flexa \deminutum g \]}
3717 @code{\[ a \flexa g \pes b \]}
3725 @code{\[ a \flexa g \pes \auctum \descendens b \]}
3732 @code{\[ a \flexa g \pes \deminutum b \]}
3739 @code{\[ \virga b \inclinatum a \inclinatum g \]}
3746 @code{\[ \virga b \inclinatum a \inclinatum \auctum g \]}
3753 @code{\[ \virga b \inclinatum a \inclinatum \deminutum g \]}
3760 @code{\[ g \pes a \virga b \]}
3768 @code{\[ g \pes a \pes \auctum \descendens b \]}
3775 @code{\[ g \pes a \pes \deminutum b \]}
3782 @code{\[ g \oriscus a \pes \virga b \]}
3787 Salicus Auctus Descendens
3789 @code{\[ g \oriscus a \pes \auctum \descendens b \]}
3796 @code{\[ \stropha b \stropha b \stropha a \]}
3801 The following head prefixes are supported
3803 @cindex @code{\virga}
3805 @cindex @code{\stropha}
3807 @cindex @code{\inclinatum}
3809 @cindex @code{\auctum}
3811 @cindex @code{\descendens}
3813 @cindex @code{\ascendens}
3815 @cindex @code{\oriscus}
3817 @cindex @code{\quilisma}
3819 @cindex @code{\deminutum}
3822 Head prefixes can be accumulated, though restrictions apply. For
3823 example, either @code{\descendens} or @code{\ascendens} can be applied
3824 to a head, but not both to the same head.
3827 @cindex @code{\flexa}
3828 Two adjacent heads can be tied together with the @code{\pes} and
3829 @code{\flexa} infix commands for a rising and falling line of melody,
3834 @node Gregorian Chant contexts
3835 @subsection Gregorian Chant contexts
3837 @cindex VaticanaVoiceContext
3838 @cindex VaticanaStaffContext
3840 The predefined @code{VaticanaVoiceContext} and
3841 @code{VaticanaStaffContext} can be used to engrave a piece of
3842 Gregorian Chant in the style of the Editio Vaticana. These contexts
3843 initialize all relevant context properties and grob properties to
3844 proper values, so you can immediately go ahead entering the chant, as
3845 the following excerpt demonstrates
3847 @lilypond[quote,raggedright,packed,verbatim]
3848 \include "gregorian-init.ly"
3851 \context VaticanaVoice = "cantus" {
3852 \override Staff.StaffSymbol #'color = #red
3853 \override Staff.LedgerLineSpanner #'color = #red
3854 \override Score.BarNumber #'transparent = ##t {
3855 \[ c'\melisma c' \flexa a \]
3856 \[ a \flexa \deminutum g\melismaEnd \]
3858 \[ f\melisma \pes a c' c' \pes d'\melismaEnd \]
3859 c' \divisioMinima \break
3860 \[ c'\melisma c' \flexa a \]
3861 \[ a \flexa \deminutum g\melismaEnd \] f \divisioMinima
3864 \lyricsto "cantus" \new Lyrics {
3865 San- ctus, San- ctus, San- ctus
3872 @node Mensural contexts
3873 @subsection Mensural contexts
3875 @cindex MensuralVoiceContext
3876 @cindex MensuralStaffContext
3878 The predefined @code{MensuralVoiceContext} and
3879 @code{MensuralStaffContext} can be used to engrave a piece in mensural
3880 style. These contexts initialize all relevant context properties and
3881 grob properties to proper values, so you can immediately go ahead
3882 entering the chant, as the following excerpt demonstrates
3884 @lilypond[quote,raggedright,verbatim]
3887 \context MensuralVoice = "discantus" \transpose c c' {
3888 \override Score.BarNumber #'transparent = ##t {
3889 c'1\melisma bes a g\melismaEnd
3891 \[ f1\melisma a c'\breve d'\melismaEnd \]
3893 c'\breve\melisma a1 g1\melismaEnd
3894 fis\longa^\signumcongruentiae
3897 \lyricsto "discantus" \new Lyrics {
3898 San -- ctus, San -- ctus, San -- ctus
3904 @node Musica ficta accidentals
3905 @subsection Musica ficta accidentals
3907 In European music from before about 1600, singers were often expected
3908 to chromatically alter notes at their own initiative. This is called
3909 ``Musica Ficta''. In modern transcriptions, these accidentals are
3910 usually printed over the note.
3912 @cindex Musica ficta
3914 Support for such suggested accidentals is included, and can be
3915 switched on by setting @code{suggestAccidentals} to true.
3917 @cindex @code{suggestAccidentals}
3919 @lilypond[verbatim,fragment,relative=1]
3921 \set suggestAccidentals = ##t
3927 Program reference: @internalsref{Accidental_engraver} engraver and the
3928 @internalsref{AccidentalSuggestion} object.
3931 @subsection Figured bass
3933 @cindex Basso continuo
3935 @c TODO: musicological blurb about FB
3938 LilyPond has limited support for figured bass
3940 @lilypond[quote,raggedright,verbatim,fragment]
3942 \context Voice { \clef bass dis4 c d ais g fis}
3943 \context FiguredBass \figuremode {
3944 < 6 >4 < 7 >8 < 6+ [_!] >
3951 The support for figured bass consists of two parts: there is an input
3952 mode, introduced by @code{\figuremode}, where you can enter bass figures
3953 as numbers, and there is a context called @internalsref{FiguredBass} that
3954 takes care of making @internalsref{BassFigure} objects.
3956 In figures input mode, a group of bass figures is delimited by
3957 @code{<} and @code{>}. The duration is entered after the @code{>}
3961 @lilypond[quote,raggedright,fragment]
3962 \context FiguredBass
3963 \figuremode { <4 6> }
3966 Accidentals are added when you append @code{-}, @code{!}, and @code{+}
3972 @lilypond[quote,raggedright,fragment]
3973 \context FiguredBass
3974 \figuremode { <4- 6+ 7!> }
3977 Spaces or dashes may be inserted by using @code{_}. Brackets are
3978 introduced with @code{[} and @code{]}. You can also include text
3979 strings and text markups, see @ref{Overview of text markup commands}.
3982 < [4 6] 8 [_! 12] > < 5 \markup @{ + \number 6 @} >
3984 @lilypond[quote,raggedright,fragment]
3985 \context FiguredBass
3986 \figuremode { < [4 6] 8 [_! 12] > < 5 \markup{ + \number 6 } > }
3990 Although the support for figured bass may superficially resemble chord
3991 support, it works much simpler. The @code{\figuremode} mode simply
3992 stores the numbers and @internalsref{FiguredBass} context prints
3993 them as entered. There is no conversion to pitches and no
3994 realizations of the bass are played in the MIDI file.
3996 Internally, the code produces markup texts. You can use any of the
3997 markup text properties to override formatting. For example, the
3998 vertical spacing of the figures may be set with @code{baseline-skip}.
4002 Program reference: @internalsref{BassFigure} object,
4003 @internalsref{FiguredBass} context.
4007 Slash notation for alterations is not supported.
4011 @node Other instrument specific notation
4012 @section Other instrument specific notation
4014 This section includes extra information for writing for instruments.
4017 * Artificial harmonics (strings)::
4020 @node Artificial harmonics (strings)
4021 @subsection Artificial harmonics (strings)
4023 @cindex artificial harmonics
4025 Artificial harmonics are notated with a different notehead style. They
4026 are entered by marking the harmonic pitch with @code{\harmonic}.
4028 @lilypond[raggedright,verbatim,quote,fragment,relative=1]