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::
47 Dynamics are not centered, but workarounds do exist. See the
48 ``piano centered dynamics'' template in @ref{Piano templates}.
50 @cindex cross staff stem
51 @cindex stem, cross staff
52 @cindex distance between staves in piano music
54 The distance between the two staves is the same for all systems in the
55 score. It is possible to override this per system, but it does require
56 an arcane command incantation. See
57 @inputfileref{input/@/test,piano@/-staff@/-distance@/.ly}.
60 @node Automatic staff changes
61 @subsection Automatic staff changes
62 @cindex Automatic staff changes
64 Voices can be made to switch automatically between the top and the bottom
65 staff. The syntax for this is
69 \autochange @dots{}@var{music}@dots{}
74 This will create two staves inside the current PianoStaff, called
75 @code{up} and @code{down}. The lower staff will be in bass clef by
78 A @code{\relative} section that is outside of @code{\autochange} has
79 no effect on the pitches of @var{music}, so, if necessary, put
80 @code{\relative} inside @code{\autochange} like
84 \autochange \relative @dots{} @dots{}
89 The autochanger switches on basis of the pitch (middle C is the turning
90 point), and it looks ahead skipping over rests to switch in
91 advance. Here is a practical example
93 @lilypond[quote,verbatim,raggedright]
95 \autochange \relative c'
104 In this manual: @ref{Manual staff switches}.
106 Program reference: @internalsref{AutoChangeMusic}.
112 The staff switches may not end up in optimal places. For high
113 quality output, staff switches should be specified manually.
116 @code{\autochange} cannot be inside @code{\times}.
119 @node Manual staff switches
120 @subsection Manual staff switches
122 @cindex manual staff switches
123 @cindex staff switch, manual
125 Voices can be switched between staves manually, using the command
127 \change Staff = @var{staffname} @var{music}
131 The string @var{staffname} is the name of the staff. It switches the
132 current voice from its current staff to the Staff called
133 @var{staffname}. Typically @var{staffname} is @code{"up"} or
134 @code{"down"}. The @context{Staff} referred to must already exist, so
135 usually the setup for a score will start with a setup of the staves,
139 \context Staff = up @{
140 \skip 1 * 10 % @emph{keep staff alive}
142 \context Staff = down @{
143 \skip 1 * 10 % @emph{idem}
149 and the @context{Voice} is inserted afterwards
152 \context Staff = down
153 \new Voice @{ @dots{} \change Staff = up @dots{} @}
161 Pianos have pedals that alter the way sound is produced. Generally, a
162 piano has three pedals, sustain, una corda, and sostenuto.
165 Piano pedal instruction can be expressed by attaching
166 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
167 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
170 @lilypond[quote,raggedright,fragment,verbatim]
171 c'4\sustainDown c'4\sustainUp
174 What is printed can be modified by setting @code{pedal@var{X}Strings},
175 where @var{X} is one of the pedal types: @code{Sustain},
176 @code{Sostenuto} or @code{UnaCorda}. Refer to
177 @internalsref{SustainPedal} in the program reference for more
180 Pedals can also be indicated by a sequence of brackets, by setting the
181 @code{pedalSustainStyle} property to bracket objects
183 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
184 \set Staff.pedalSustainStyle = #'bracket
186 b\sustainUp\sustainDown
187 b g \sustainUp a \sustainDown \bar "|."
190 A third style of pedal notation is a mixture of text and brackets,
191 obtained by setting the @code{pedalSustainStyle} property to
194 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
195 \set Staff.pedalSustainStyle = #'mixed
197 b\sustainUp\sustainDown
198 b g \sustainUp a \sustainDown \bar "|."
201 The default `*Ped.' style for sustain and damper pedals corresponds to
202 style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
205 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
206 c\sostenutoDown d e c, f g a\sostenutoUp
209 For fine-tuning the appearance of a pedal bracket, the properties
210 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
211 @code{PianoPedalBracket} objects (see
212 @internalsref{PianoPedalBracket} in the Program reference) can be
213 modified. For example, the bracket may be extended to the right edge
216 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
217 \override Staff.PianoPedalBracket #'shorten-pair = #'(0 . -1.0)
218 c\sostenutoDown d e c, f g a\sostenutoUp
221 @node Staff switch lines
222 @subsection Staff switch lines
226 @cindex staff switching
229 @cindex @code{followVoice}
231 Whenever a voice switches to another staff, a line connecting the notes
232 can be printed automatically. This is switched on by setting
233 @code{followVoice} to true
235 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
238 \set followVoice = ##t
243 \context Staff=two { \clef bass \skip 1*2 }
249 Program reference: @internalsref{VoiceFollower}.
253 @cindex @code{\showStaffSwitch}
254 @code{\showStaffSwitch},
255 @cindex @code{\hideStaffSwitch}
256 @code{\hideStaffSwitch}.
259 @node Cross staff stems
260 @subsection Cross staff stems
262 Chords that cross staves may be produced by increasing the length
263 of the stem in the lower staff, so it reaches the stem in the upper
264 staff, or vice versa.
266 @lilypond[raggedright,verbatim,quote]
267 stemExtend = \once \override Stem #'length = #22
268 noFlag = \once \override Stem #'flag-style = #'no-flag
269 \context PianoStaff <<
271 \stemDown \stemExtend
289 * Introducing chord names::
291 * Printing chord names::
295 @c awkward name; awkward section name.
296 @c still, the Basic "chords" seems like a good name... :(
297 @node Introducing chord names
298 @subsection Introducing chord names
301 LilyPond has support for printing chord names. Chords may be entered
302 in musical chord notation, i.e., @code{< .. >}, but they can also be
303 entered by name. Internally, the chords are represented as a set of
304 pitches, so they can be transposed
307 @lilypond[quote,raggedright,verbatim,raggedright]
308 twoWays = \transpose c c' {
317 << \context ChordNames \twoWays
318 \context Voice \twoWays >>
321 This example also shows that the chord printing routines do not try to
322 be intelligent. The last chord (@code{f bes d}) is not interpreted as
325 Note that the duration of chords must be specified outside the
334 @subsection Chords mode
337 In chord mode sets of pitches (chords) are entered with normal note
338 names. A chord is entered by the root, which is entered like a
341 @lilypond[quote,raggedright,fragment,verbatim]
342 \chordmode { es4. d8 c2 }
346 The mode is introduced by the keyword @code{\chordmode}.
351 Other chords may be entered by suffixing a colon and introducing a
352 modifier (which may include a number if desired)
353 @lilypond[quote,fragment,verbatim]
354 \chordmode { e1:m e1:7 e1:m7 }
356 The first number following the root is taken to be the `type' of the
357 chord, thirds are added to the root until it reaches the specified
359 @lilypond[quote,fragment,verbatim]
360 \chordmode { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 }
363 @cindex root of chord
364 @cindex additions, in chords
365 @cindex removals, in chords
367 More complex chords may also be constructed adding separate steps
368 to a chord. Additions are added after the number following
369 the colon and are separated by dots
370 @lilypond[quote,verbatim,fragment]
371 \chordmode { c:5.6 c:3.7.8 c:3.6.13 }
373 Chord steps can be altered by suffixing a @code{-} or @code{+} sign
375 @lilypond[quote,verbatim,fragment]
376 \chordmode { c:7+ c:5+.3- c:3-.5-.7- }
378 Removals are specified similarly and are introduced by a caret. They
379 must come after the additions
380 @lilypond[quote,verbatim,fragment]
381 \chordmode { c^3 c:7^5 c:9^3.5 }
384 Modifiers can be used to change pitches. The following modifiers are
389 The minor chord. This modifier lowers the 3rd and (if present) the 7th step.
392 The diminished chord. This modifier lowers the 3rd, 5th and (if present)
396 The augmented chord. This modifier raises the 5th step.
399 The major 7th chord. This modifier raises the 7th step if present.
402 The suspended 4th or 2nd. This modifier removes the 3rd
403 step. Append either @code{2} or @code{4} to add the 2nd or 4th step to
407 Modifiers can be mixed with additions
408 @lilypond[quote,verbatim,fragment]
409 \chordmode { c:sus4 c:7sus4 c:dim7 c:m6 }
412 @cindex modifiers, in chords.
419 Since an unaltered 11 does not sound good when combined with an
420 unaltered 3, the 11 is removed in this case (unless it is added
422 @lilypond[quote,raggedright,fragment,verbatim]
423 \chordmode { c:13 c:13.11 c:m13 }
428 An inversion (putting one pitch of the chord on the bottom), as well
429 as bass notes, can be specified by appending
430 @code{/}@var{pitch} to the chord
431 @lilypond[quote,raggedright,fragment,verbatim]
432 \chordmode { c1 c/g c/f }
436 A bass note can be added instead transposed out of the chord,
437 by using @code{/+}@var{pitch}.
439 @lilypond[quote,raggedright,fragment,verbatim]
440 \chordmode { c1 c/+g c/+f }
443 Chords is a mode similar to @code{\lyricmode}, etc. Most
444 of the commands continue to work, for example, @code{r} and
445 @code{\skip} can be used to insert rests and spaces, and property
446 commands may be used to change various settings.
452 Each step can only be present in a chord once. The following
453 simply produces the augmented chord, since @code{5+} is interpreted
456 @lilypond[quote,raggedright,verbatim,fragment]
457 \chordmode { c:5.5-.5+ }
461 @node Printing chord names
462 @subsection Printing chord names
464 @cindex printing chord names
468 For displaying printed chord names, use the @internalsref{ChordNames} context.
469 The chords may be entered either using the notation
470 described above, or directly using @code{<} and @code{>}
472 @lilypond[quote,verbatim,raggedright]
474 \chordmode {a1 b c} <d' f' a'> <e' g' b'>
477 \context ChordNames \harmonies
478 \context Staff \harmonies
482 You can make the chord changes stand out by setting
483 @internalsref{ChordNames}.@code{chordChanges} to true. This will only
484 display chord names when there is a change in the chords scheme and at
485 the start of a new line
487 @lilypond[quote,verbatim,raggedright]
488 harmonies = \chordmode {
489 c1:m c:m \break c:m c:m d
492 \context ChordNames {
493 \set chordChanges = ##t
495 \context Staff \transpose c c' \harmonies
499 The previous examples all show chords over a staff. This is not
500 necessary. Chords may also be printed separately. It may be necessary
501 to add @internalsref{Volta_engraver} and @internalsref{Bar_engraver}
504 @lilypond[raggedright,verbatim]
505 \new ChordNames \with {
506 \override BarLine #'bar-size = #4
507 voltaOnThisStaff = ##t
508 \consists Bar_engraver
509 \consists "Volta_engraver"
511 \repeat volta 2 \chordmode {
520 The default chord name layout is a system for Jazz music, proposed by
521 Klaus Ignatzek (see @ref{Literature list}). It can be tuned through the
525 @cindex @code{chordNameExceptions}
526 @item chordNameExceptions
527 This is a list that contains the chords that have special formatting.
529 The exceptions list should be encoded as
531 @{ <c f g bes>1 \markup @{ \super "7" "wahh" @} @}
534 To get this information into @code{chordNameExceptions} takes a little
535 manoeuvring. The following code transforms @code{chExceptionMusic}
536 (which is a sequential music) into a list of exceptions.
538 (sequential-music-to-chord-exceptions chExceptionMusic #t)
543 (sequential-music-to-chord-exceptions chExceptionMusic #t)
546 adds the new exceptions to the default ones, which are defined in
547 @file{ly/@/chord@/-modifier@/-init@/.ly}.
549 For an example of tuning this property, see also
550 @inputfileref{input/@/regression,chord@/-name@/-exceptions@/.ly}.
551 @cindex exceptions, chord names.
554 @cindex @code{majorSevenSymbol}
555 @item majorSevenSymbol
556 This property contains the markup object used for the 7th step, when
557 it is major. Predefined options are @code{whiteTriangleMarkup} and
558 @code{blackTriangleMarkup}. See
559 @inputfileref{input/@/regression,chord@/-name@/-major7@/.ly} for an example.
561 @cindex @code{chordNameSeparator}
562 @item chordNameSeparator
563 Different parts of a chord name are normally separated by a
564 slash. By setting @code{chordNameSeparator}, you can specify other
566 @lilypond[quote,raggedright,fragment,verbatim]
567 \context ChordNames \chordmode {
569 \set chordNameSeparator
570 = \markup { \typewriter "|" }
575 @cindex @code{chordRootNamer}
577 The root of a chord is usually printed as a letter with an optional
578 alteration. The transformation from pitch to letter is done by this
579 function. Special note names (for example, the German ``H'' for a
580 B-chord) can be produced by storing a new function in this property.
582 @cindex @code{chordNoteNamer}
584 The default is to print single pitch, e.g., the bass note, using the
585 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
586 to a specialized function to change this behavior. For example, the
587 base can be printed in lower case.
589 @cindex @code{chordPrefixSpacer}
590 @item chordPrefixSpacer
591 The ``m'' for minor chords is usually printed right after the root of
592 the chord. By setting @code{chordPrefixSpacer}, you can fix a spacer
593 between the root and ``m''. The spacer is not used when the root
598 The predefined variables @code{\germanChords},
599 @code{\semiGermanChords}, @code{\italianChords} and @code{\frenchChords}
600 set these variables. The effect is
603 @lilypondfile[raggedright]{chord-names-languages.ly}
605 There are also two other chord name schemes implemented: an alternate
606 Jazz chord notation, and a systematic scheme called Banter chords. The
607 alternate Jazz notation is also shown on the chart in @ref{Chord name
608 chart}. Turning on these styles is described in the input file
609 @inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
618 @cindex @code{\germanChords}
619 @code{\germanChords},
620 @cindex @code{\semiGermanChords}
621 @code{\semiGermanChords}.
622 @cindex @code{\italianChords}
623 @code{\italianChords}.
624 @cindex @code{\frenchChords}
625 @code{\frenchChords}.
632 Examples: @inputfileref{input/@/regression,chord@/-name@/-major7@/.ly},
633 @inputfileref{input/@/regression,chord@/-name@/-exceptions@/.ly},
634 @inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
637 Init files: @file{scm/@/chords@/-ignatzek@/.scm}, and
638 @file{scm/@/chord@/-entry@/.scm}.
643 Chord names are determined solely from the list of pitches. Chord
644 inversions are not identified, and neither are added bass notes. This
645 may result in strange chord names when chords are entered with the
646 @code{< .. >} syntax.
653 There are three different issues when printing vocal music
657 Song texts must be entered as text, not notes. For example, the
658 input@tie{}@code{d} should be interpreted as a one letter syllable, not the
662 Song texts must be printed as text, not as notes.
665 Song texts must be aligned with the notes of their melody.
668 The simplest solution for printing music uses the @code{\addlyrics}
669 function to solve all these problems at once. However, these
670 three functions can be controlled separately, which is necessary
671 for complex vocal music.
675 * Setting simple songs::
677 * Hyphens and extenders::
678 * The Lyrics context::
679 * Flexibility in alignment::
682 * Other vocal issues::
685 @node Setting simple songs
686 @subsection Setting simple songs
688 The easiest way to add lyrics to a melody is to append
691 \addlyrics @{ @var{the lyrics} @}
695 to a melody. Here is an example,
697 @lilypond[raggedright,verbatim,fragment,quote]
699 \relative { c2 e4 g2. }
700 \addlyrics { play the game }
703 More stanzas can be added by adding more
704 @code{\addlyrics} sections
706 @lilypond[raggedright,verbatim,fragment,quote]
708 \relative { c2 e4 g2. }
709 \addlyrics { play the game }
710 \addlyrics { speel het spel }
711 \addlyrics { joue le jeu }
714 @c TODO - this isn't such a great place for this note, but I can't
715 @c find a better place without rearranging a lot of lyric stuff.
716 @c It's yet another thing to look at post-3.0.
718 The @code{\addlyrics} command is actually just a convienient way
719 to write a more complicated LilyPond structure that sets up the
720 lyrics. You should use @code{\addlyrics} unless you need to do
721 fancy things, in which case you should investigate
722 @code{\lyricsto} or @code{\lyricmode}.
726 \addlyrics @{ LYRICS @}
733 \context Voice = blah @{ music @}
734 \lyricsto "blah" \new lyrics @{ LYRICS @}
739 @code{\addlyrics} cannot handle polyphony.
742 @node Entering lyrics
743 @subsection Entering lyrics
746 @cindex @code{\lyricmode}
749 Lyrics are entered in a special input mode. This mode is introduced
750 by the keyword @code{\lyricmode}, or by using @code{\addlyrics} or
751 @code{\lyricsto}. In this mode you can enter lyrics,
752 with punctuation and accents, and the input @code{d} is not parsed as
753 a pitch, but rather as a one letter syllable. Syllables are entered
754 like notes, but with pitches replaced by text. For example,
756 \lyricmode @{ Twin-4 kle4 twin- kle litt- le star2 @}
759 There is a difference between @code{\addlyrics} and
760 @code{\lyricmode}. @code{\addlyrics} and @code{\lyricsto}
761 ignore all durations and aligns syllables to notes; @code{\lyricmode}
762 uses the durations specified.
764 A word lyrics mode begins with an alphabetic character, and ends with
765 any space or digit. The following characters can be any character
766 that is not a digit or white space. One important consequence of this
767 is that a word can end with @code{@}}. The following example is
768 usually a mistake in the input file. The syllable includes a @code{@}}, so the
769 opening brace is not balanced
771 \lyricmode @{ twinkle@}
774 @cindex @code{\property}, in @code{\lyricmode}
776 Similarly, a period which follows an alphabetic sequence is included in
777 the resulting string. As a consequence, spaces must be inserted around
780 \override Score . LyricText #'font-shape = #'italic
784 @cindex spaces, in lyrics
785 @cindex quotes, in lyrics
787 Any @code{_} character that appears in an unquoted word is converted
788 to a space. This provides a mechanism for introducing spaces into words
789 without using quotes.
791 To enter lyrics with characters from non-English languages, or with
792 non-ascii characters (such as the heart symbol or slanted quotes),
793 simply insert the characters directly into the input file and save
794 it with utf-8 encoding. See @ref{Text encoding} for more info.
797 \lyricmode @{ He said: “Let my peo ple go”. @}
800 The full definition of a word start in Lyrics mode is somewhat more
803 A word in Lyrics mode begins with: an alphabetic character, @code{_},
804 @code{?}, @code{!}, @code{:}, @code{'}, the control characters @code{^A}
805 through @code{^F}, @code{^Q} through @code{^W}, @code{^Y}, @code{^^},
806 any 8-bit character with ASCII code over 127, or a two-character
807 combination of a backslash followed by one of @code{`}, @code{'},
808 @code{"}, or @code{^}.
814 Program reference: @internalsref{LyricText}.
818 The definition of lyrics mode is too complex.
820 @node Hyphens and extenders
821 @subsection Hyphens and extenders
825 Centered hyphens are entered as `@code{--}' between syllables.
826 The hyphen will have variable length depending on the space between
827 the syllables and it will be centered between the syllables.
832 When a lyric is sung over many notes (this is called a melisma), this is
833 indicated with a horizontal line centered between a syllable and the
834 next one. Such a line is called an extender line, and it is entered as
837 In tighly engraved music, hyphens can be removed. In some languages
838 (e.g. German and Hungarian), hyphens should not disappear, since
839 spelling depends on hyphenation. For that purpose, hyphens can be
840 forced to remain by overriding @code{minimum-length} of
841 the @code{LyricHyphen} grob.
843 @lilypond[quote,verbatim,raggedright]
846 \new Staff \relative c'' {
847 \time 1/4 c16 c c c c16 c c c c16 c c c
849 \lyricmode { \new Lyrics
851 \override SeparationItem #'padding = #0.0
852 % Otherwise lyrics are so far apart that hyphens don't disappear
855 An -- ti -- cons -- ti --
856 tu -- tion -- nel -- le --
857 \override LyricHyphen #'minimum-length = #0.7
858 \override LyricHyphen #'spacing-procedure =
859 #Hyphen_spanner::set_spacing_rods
860 men -- taire -- ment. ouf~!
868 \Staff \remove "Time_signature_engraver"
876 Program reference: @internalsref{LyricHyphen}, @internalsref{LyricExtender}.
880 @node The Lyrics context
881 @subsection The Lyrics context
884 Lyrics are printed by interpreting them in a @internalsref{Lyrics} context
886 \context Lyrics \lyricmode @dots{}
889 @cindex automatic syllable durations
890 @cindex @code{\lyricsto}
891 @cindex lyrics and melodies
893 This will place the lyrics according to the durations that were
894 entered. The lyrics can also be aligned under a given melody
895 automatically. In this case, it is no longer necessary to enter the
896 correct duration for each syllable. This is achieved by combining the
897 melody and the lyrics with the @code{\lyricsto} expression
899 \lyricsto @var{name} \new Lyrics @dots{}
902 This aligns the lyrics to the
903 notes of the @internalsref{Voice} context called @var{name}, which has
904 to exist. Therefore, normally the @code{Voice} is specified first, and
905 then the lyrics are specified with @code{\lyricsto}. The command
906 @code{\lyricsto} switches to @code{\lyricmode} mode automatically, so the
907 @code{\lyricmode} keyword may be omitted.
909 For different or more complex orderings, the best way is to setup the
910 hierarchy of staves and lyrics first, e.g.,
912 \context ChoirStaff <<
913 \context Lyrics = sopranoLyrics @{ s1 @}
914 \context Voice = soprano @{ @emph{music} @}
915 \context Lyrics = tenorLyrics @{ s1 @}
916 \context Voice = tenor @{ @emph{music} @}
919 and then combine the appropriate melodies and lyric lines
921 \lyricsto "soprano" \context Lyrics = sopranoLyrics
926 The final input would resemble
929 <<\context ChoirStaff << @emph{setup the music} >>
930 \lyricsto "soprano" @emph{etc}
931 \lyricsto "alto" @emph{etc}
937 The @code{\lyricsto} command detects melismata: it only puts one
938 syllable under a tied or slurred group of notes. If you want to force
939 an unslurred group of notes to be a melisma, insert @code{\melisma}
940 after the first note of the group, and @code{\melismaEnd} after the
943 @lilypond[quote,relative=2,raggedright,fragment,verbatim]
945 \context Voice = "lala" {
953 \lyricsto "lala" \new Lyrics {
959 In addition, notes are considered a melisma if they are manually
960 beamed, and automatic beaming (see @ref{Setting automatic beam
961 behavior}) is switched off.
967 The criteria for deciding melismata can
968 be tuned with the property @code{melismaBusyProperties}. See
969 @internalsref{Melisma_translator} in the program reference for more
974 Lyrics can also be entered without @code{\lyricsto}. In this case the
975 duration of each syllable must be entered explicitly, for example,
982 The alignment to a melody can be specified with the
983 @code{associatedVoice} property,
986 \set associatedVoice = #"lala"
990 The value of the property (here: @code{"lala"}) should be the name of
991 a @internalsref{Voice} context. Without this setting, extender lines
992 will not be formatted properly.
994 Here is an example demonstrating manual lyric durations,
996 @lilypond[relative=1,raggedright,verbatim,fragment,quote]
997 << \context Voice = melody {
1001 \new Lyrics \lyricmode {
1002 \set associatedVoice = #"melody"
1008 @cindex choral score
1010 A complete example of a SATB score setup is in section
1011 @ref{Vocal ensembles}.
1016 @code{\melisma}, @code{\melismaEnd}
1017 @cindex @code{\melismaEnd}
1018 @cindex @code{\melisma}
1022 Program reference: @internalsref{LyricCombineMusic},
1023 @internalsref{Lyrics}, @internalsref{Melisma_translator}.
1026 @inputfileref{input/@/regression,lyric@/-combine@/-new@/.ly}.
1027 @c TODO: make separate section for melismata
1031 Melismata are not detected automatically, and extender lines must be
1035 @c TODO: document \new Staff << Voice \lyricsto >> bug
1037 @node Flexibility in alignment
1038 @subsection Flexibility in alignment
1040 Often, different stanzas of one song are put to one melody in slightly
1041 differing ways. Such variations can still be captured with
1044 @subsubsection Lyrics to multiple notes of a melisma
1047 One possibility is that the text has a melisma in one stanza, but
1048 multiple syllables in another one. One solution is to make the faster
1049 voice ignore the melisma. This is done by setting
1050 @code{ignoreMelismata} in the Lyrics context.
1052 There has one tricky aspect. The setting for @code{ignoreMelismata}
1053 must be set one syllable @emph{before} the non-melismatic syllable
1054 in the text, as shown here,
1056 @lilypond[verbatim,raggedright,quote]
1058 \relative \context Voice = "lahlah" {
1059 \set Staff.autoBeaming = ##f
1065 \new Lyrics \lyricsto "lahlah" {
1068 \new Lyrics \lyricsto "lahlah" {
1069 \set ignoreMelismata = ##t % applies to "fas"
1071 \unset ignoreMelismata
1078 The @code{ignoreMelismata} applies to the syllable ``fas'', so it
1079 should be entered before ``go''.
1081 The reverse is also possible: making a lyric line slower than the
1082 standard. This can be achieved by insert @code{\skip}s into the
1083 lyrics. For every @code{\skip}, the text will be delayed another note.
1086 @lilypond[verbatim,raggedright,quote]
1087 \relative { c c g' }
1095 @subsection Switching the melody associated with a lyrics line
1099 More complex variations in text underlay are possible. It is possible
1100 to switch the melody for a line of lyrics during the text. This is
1101 done by setting the @code{associatedVoice} property. In the example
1103 @lilypond[raggedright,quote]
1105 \relative \context Voice = "lahlah" {
1106 \set Staff.autoBeaming = ##f
1109 \context Voice = alternative {
1112 % show associations clearly.
1113 \override NoteColumn #'force-hshift = #-3
1124 \new Lyrics \lyricsto "lahlah" {
1125 Ju -- ras -- sic Park
1127 \new Lyrics \lyricsto "lahlah" {
1128 % Tricky: need to set associatedVoice
1129 % one syllable too soon!
1130 \set associatedVoice = alternative % applies to "ran"
1134 \set associatedVoice = lahlah % applies to "rus"
1140 the text for the first stanza is set to a melody called ``lahlah'',
1143 \new Lyrics \lyricsto "lahlah" @{
1144 Ju -- ras -- sic Park
1149 The second stanza initially is set to the @code{lahlah} context, but
1150 for the syllable ``ran'', it switches to a different melody.
1151 This is achieved with
1153 \set associatedVoice = alternative
1157 Here, @code{alternative} is the name of the @code{Voice} context
1158 containing the triplet.
1160 Again, the command must be one syllable too early, before ``Ty'' in
1164 \new Lyrics \lyricsto "lahlah" @{
1165 \set associatedVoice = alternative % applies to "ran"
1169 \set associatedVoice = lahlah % applies to "rus"
1175 The underlay is switched back to the starting situation by assigning
1176 @code{lahlah} to @code{associatedVoice}.
1180 @subsection Specifying melismata within the lyrics
1182 It is also possible to define melismata entirely in the lyrics. This
1183 can be done by entering @code{_} for every note that is part of the
1186 @lilypond[relative=1,verbatim,fragment]
1187 { \set melismaBusyProperties = #'()
1188 c d( e) f f( e) e e }
1190 { Ky -- _ _ ri __ _ _ _ e }
1193 In this case, you can also have ties and slurs in the melody, if you
1194 set @code{melismaBusyProperties}, as is done in the example above.
1196 @lilypond[relative=1,verbatim,fragment]
1198 \set melismaBusyProperties = #'()
1202 { Ky -- _ _ ri __ _ _ _ e }
1207 @subsection More stanzas
1209 @cindex phrasing, in lyrics
1212 @cindex stanza number
1213 @cindex singer's names
1214 @cindex name of singer
1216 Stanza numbers can be added by setting @code{stanza}, e.g.,
1218 @lilypond[quote,raggedright,verbatim,relative=2,fragment]
1220 \time 3/4 g2 e4 a2 f4 g2.
1223 Hi, my name is Bert.
1226 Oh, che -- ri, je t'aime
1230 These numbers are put just before the start of first syllable.
1232 Names of singers can also be added. They are printed at the start of
1233 the line, just like instrument names. They are created by setting
1234 @code{vocalName}. A short version may be entered as @code{vocNam}.
1237 @lilypond[fragment,raggedright,quote,verbatim,relative=2]
1239 \time 3/4 g2 e4 a2 f4 g2.
1241 \set vocalName = "Bert "
1242 Hi, my name is Bert.
1244 \set vocalName = "Ernie "
1245 Oh, che -- ri, je t'aime
1249 You can display alternate (or divisi) lyrics by naming voice
1250 contexts and attaching lyrics to those specific contexts.
1252 @lilypond[verbatim,raggedright,quote]
1254 \context Voice = "melody" {
1259 \context Voice = splitpart { \voiceTwo c4 }
1264 \new Lyrics \lyricsto "melody" { we shall not o- ver- come }
1265 \new Lyrics \lyricsto "splitpart" { will }
1270 You can use this trick to display different lyrics for a repeated
1273 @lilypond[verbatim,raggedright,quote]
1275 \context Voice = melody \relative c' {
1277 \context Voice = verse \repeat volta 2 {c4 d e f | g1 | }
1279 \lyricsto melody \context Lyrics = mainlyrics \lyricmode {
1282 \lyricsto verse \context Lyrics = mainlyrics \lyricmode {
1284 \lyricsto verse \context Lyrics = repeatlyrics \lyricmode {
1285 dodo rere mimi fafa solsol }
1293 Program reference: @internalsref{LyricText}, @internalsref{StanzaNumber}, @internalsref{VocalName}.
1301 The term @emph{ambitus} denotes a range of pitches for a given voice
1302 in a part of music. It may also denote the pitch range that a musical
1303 instrument is capable of playing. Ambits are printed on vocal parts,
1304 so performers can easily determine it meets their capabilities.
1306 Ambits are denoted at the beginning of a piece near the initial clef.
1307 The range is graphically specified by two note heads that represent the
1308 minimum and maximum pitch. To print such ambits, add the
1309 @internalsref{Ambitus_engraver} to the @internalsref{Voice} context,
1316 \consists Ambitus_engraver
1321 This results in the following output
1323 @lilypond[quote,raggedright]
1327 \consists Ambitus_engraver
1331 \relative \new Staff {
1336 If you have multiple voices in a single staff and you want a single
1337 ambitus per staff rather than per each voice, add the
1338 @internalsref{Ambitus_engraver} to the @internalsref{Staff} context
1339 rather than to the @internalsref{Voice} context. Here is an example,
1341 @lilypond[verbatim,raggedright,quote]
1343 \consists "Ambitus_engraver"
1347 \remove "Ambitus_engraver"
1349 \override Ambitus #'X-offset-callbacks
1350 = #(list (lambda (grob axis) -1.0))
1355 \remove "Ambitus_engraver"
1364 This example uses one advanced feature,
1367 \override Ambitus #'X-offset-callbacks
1368 = #(list (lambda (grob axis) -1.0))
1372 This code moves the ambitus to the left. The same effect could have
1373 been achieved with @code{extra-offset}, but then the formatting system
1374 would not reserve space for the moved object.
1378 Program reference: @internalsref{Ambitus},
1379 @internalsref{AmbitusLine}, @internalsref{AmbitusNoteHead},
1380 @internalsref{AmbitusAccidental}.
1382 Examples: @inputfileref{input/@/regression,ambitus@/.ly}.
1386 There is no collision handling in the case of multiple per-voice
1390 @node Other vocal issues
1391 @subsection Other vocal issues
1394 yeah, I'm giving up somewhat by stuffing a bunch of things in
1395 here. But at least they're in the manual now; it's easier to
1396 move them around in the manual once they're already here.
1398 Besides, if users complain about everything stuffed in here, I
1399 can ask them for specific instructions about where to move these
1400 examples, and that might get them more involved in the docs. -gp
1403 ``Parlato'' is spoken without pitch but still with rhythm; it is
1404 notated by cross noteheads. This is demonstrated in
1405 @ref{Special noteheads}.
1408 @node Rhythmic music
1409 @section Rhythmic music
1411 Rhythmic music is primarily used for percussion and drum notation, but it can
1412 also be used to show the rhythms of melodies.
1415 * Showing melody rhythms::
1416 * Entering percussion::
1417 * Percussion staves::
1421 @node Showing melody rhythms
1422 @subsection Showing melody rhythms
1424 Sometimes you might want to show only the rhythm of a melody. This
1425 can be done with the rhythmic staff. All pitches of notes on such a
1426 staff are squashed, and the staff itself has a single line
1428 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
1429 \context RhythmicStaff {
1431 c4 e8 f g2 | r4 g r2 | g1:32 | r1 |
1437 Program reference: @internalsref{RhythmicStaff}.
1439 Examples: @inputfileref{input/@/regression,rhythmic@/-staff@/.ly}.
1442 @node Entering percussion
1443 @subsection Entering percussion
1449 Percussion notes may be entered in @code{\drummode} mode, which is
1450 similar to the standard mode for entering notes. Each piece of
1451 percussion has a full name and an abbreviated name, and both can be used
1454 @lilypond[quote,raggedright,verbatim]
1456 hihat hh bassdrum bd
1460 The complete list of drum names is in the init file
1461 @file{ly/@/drumpitch@/-init@/.ly}.
1462 @c TODO: properly document this.
1466 Program reference: @internalsref{note-event}.
1468 @node Percussion staves
1469 @subsection Percussion staves
1473 A percussion part for more than one instrument typically uses a
1474 multiline staff where each position in the staff refers to one piece
1478 To typeset the music, the notes must be interpreted in a
1479 @internalsref{DrumStaff} and @internalsref{DrumVoice} contexts
1481 @lilypond[quote,raggedright,verbatim]
1482 up = \drummode { crashcymbal4 hihat8 halfopenhihat hh hh hh openhihat }
1483 down = \drummode { bassdrum4 snare8 bd r bd sn4 }
1485 \new DrumVoice { \voiceOne \up }
1486 \new DrumVoice { \voiceTwo \down }
1490 The above example shows verbose polyphonic notation. The short
1491 polyphonic notation, described in @ref{Polyphony}, can also be used if
1492 the @internalsref{DrumVoice}s are instantiated by hand first. For example,
1494 @lilypond[quote,raggedright,fragment,verbatim]
1496 \context DrumVoice = "1" { s1 *2 }
1497 \context DrumVoice = "2" { s1 *2 }
1501 { \repeat unfold 16 hh16 }
1510 There are also other layout possibilities. To use these, set the
1511 property @code{drumStyleTable} in context @internalsref{DrumVoice}.
1512 The following variables have been predefined
1516 This is the default. It typesets a typical drum kit on a five-line staff
1518 @lilypond[quote,linewidth=10.0\cm]
1520 cymc cyms cymr hh hhc hho hhho hhp
1521 cb hc bd sn ss tomh tommh tomml toml tomfh tomfl }
1523 cymc cyms cymr hh hhc hho hhho hhp \break
1524 cb hc bd sn ss tomh tommh tomml toml tomfh tomfl s16 }
1526 << \new DrumStaff \with {
1527 \remove Bar_engraver
1528 \remove Time_signature_engraver
1529 \override Stem #'transparent = ##t
1530 \override Stem #'Y-extent-callback = ##f
1531 minimumVerticalExtent = #'(-4.0 . 5.0)
1533 \context Lyrics \nam
1538 \override LyricText #'font-family = #'typewriter
1539 \override BarNumber #'transparent =##T
1545 The drum scheme supports six different toms. When there are fewer toms,
1546 simply select the toms that produce the desired result, i.e., to get toms
1547 on the three middle lines you use @code{tommh}, @code{tomml}, and
1550 @item timbales-style
1551 This typesets timbales on a two line staff
1553 @lilypond[quote,raggedright]
1554 nam = \lyricmode { timh ssh timl ssl cb }
1555 mus = \drummode { timh ssh timl ssl cb s16 }
1558 \context DrumStaff \with {
1559 \remove Bar_engraver
1560 \remove Time_signature_engraver
1561 \override Stem #'transparent = ##t
1562 \override Stem #'Y-extent-callback = ##f
1563 \override StaffSymbol #'line-count = #2
1564 \override StaffSymbol #'staff-space = #2
1565 minimumVerticalExtent = #'(-3.0 . 4.0)
1566 drumStyleTable = #timbales-style
1569 \override LyricText #'font-family = #'typewriter
1576 This typesets congas on a two line staff
1578 @lilypond[quote,raggedright]
1579 nam = \lyricmode { cgh cgho cghm ssh cgl cglo cglm ssl }
1580 mus = \drummode { cgh cgho cghm ssh cgl cglo cglm ssl s16 }
1583 \context DrumStaff \with {
1584 \remove Bar_engraver
1585 \remove Time_signature_engraver
1586 drumStyleTable = #congas-style
1587 \override StaffSymbol #'line-count = #2
1589 %% this sucks; it will lengthen stems.
1590 \override StaffSymbol #'staff-space = #2
1591 \override Stem #'transparent = ##t
1592 \override Stem #'Y-extent-callback = ##f
1595 \override LyricText #'font-family = #'typewriter
1602 This typesets bongos on a two line staff
1604 @lilypond[quote,raggedright]
1605 nam = \lyricmode { boh boho bohm ssh bol bolo bolm ssl }
1606 mus = \drummode { boh boho bohm ssh bol bolo bolm ssl s16 }
1609 \context DrumStaff\with {
1610 \remove Bar_engraver
1611 \remove Time_signature_engraver
1612 \override StaffSymbol #'line-count = #2
1613 drumStyleTable = #bongos-style
1615 %% this sucks; it will lengthen stems.
1616 \override StaffSymbol #'staff-space = #2
1617 \override Stem #'transparent = ##t
1618 \override Stem #'Y-extent-callback = ##f
1621 \override LyricText #'font-family = #'typewriter
1627 @item percussion-style
1628 To typeset all kinds of simple percussion on one line staves.
1630 @lilypond[quote,raggedright]
1631 nam = \lyricmode { tri trio trim gui guis guil cb cl tamb cab mar hc }
1632 mus = \drummode { tri trio trim gui guis guil cb cl tamb cab mar hc s16 }
1635 \context DrumStaff\with{
1636 \remove Bar_engraver
1637 drumStyleTable = #percussion-style
1638 \override StaffSymbol #'line-count = #1
1639 \remove Time_signature_engraver
1640 \override Stem #'transparent = ##t
1641 \override Stem #'Y-extent-callback = ##f
1644 \override LyricText #'font-family = #'typewriter
1651 If you do not like any of the predefined lists you can define your own
1652 list at the top of your file
1654 @lilypond[quote,raggedright,verbatim]
1656 (bassdrum default #f -1)
1657 (snare default #f 0)
1659 (pedalhihat xcircle "stopped" 2)
1660 (lowtom diamond #f 3)))
1661 up = \drummode { hh8 hh hh hh hhp4 hhp }
1662 down = \drummode { bd4 sn bd toml8 toml }
1665 \set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)
1666 \new DrumVoice { \voiceOne \up }
1667 \new DrumVoice { \voiceTwo \down }
1674 Init files: @file{ly/@/drumpitch@/-init@/.ly}.
1676 Program reference: @internalsref{DrumStaff}, @internalsref{DrumVoice}.
1680 Because general MIDI does not contain rim shots, the sidestick is used
1681 for this purpose instead.
1689 @cindex guitar tablature
1692 * String number indications::
1693 * Tablatures basic::
1694 * Non-guitar tablatures::
1696 * Other guitar issues::
1699 @node String number indications
1700 @subsection String number indications
1702 @cindex String numbers
1704 String numbers can be added to chords, by indicating the string number
1705 with @code{\}@var{number},
1707 @lilypond[relative,relative=1,raggedright,fragment]
1711 See also @inputfileref{input/regression,string-number.ly}.
1716 Program reference: @internalsref{StringNumber}.
1719 @node Tablatures basic
1720 @subsection Tablatures basic
1721 @cindex Tablatures basic
1723 Tablature notation is used for notating music for plucked string
1724 instruments. Pitches are not denoted with note heads, but by
1725 numbers indicating on which string and fret a note must be played. LilyPond
1726 offers limited support for tablature.
1728 The string number associated to a note is given as a backslash
1729 followed by a number, e.g., @code{c4\3} for a C quarter on the third
1730 string. By default, string 1 is the highest one, and the tuning
1731 defaults to the standard guitar tuning (with 6 strings). The notes
1732 are printed as tablature, by using @internalsref{TabStaff} and
1733 @internalsref{TabVoice} contexts
1735 @lilypond[quote,raggedright,fragment,verbatim]
1742 @cindex @code{minimumFret}
1745 When no string is specified, the first string that does not give a
1746 fret number less than @code{minimumFret} is selected. The default
1747 value for @code{minimumFret} is 0
1752 \set TabStaff.minimumFret = #8
1755 @lilypond[quote,raggedright]
1759 \set TabStaff.minimumFret = #8
1762 \context StaffGroup <<
1763 \context Staff { \clef "G_8" \frag }
1764 \context TabStaff { \frag }
1770 Program reference: @internalsref{TabStaff}, @internalsref{TabVoice}.
1774 Chords are not handled in a special way, and hence the automatic
1775 string selector may easily select the same string to two notes in a
1779 @node Non-guitar tablatures
1780 @subsection Non-guitar tablatures
1781 @cindex Non-guitar tablatures
1783 You can change the number of strings, by setting the number of lines
1784 in the @internalsref{TabStaff}.
1786 You can change the tuning of the strings. A string tuning is given as
1787 a Scheme list with one integer number for each string, the number
1788 being the pitch (measured in semitones relative to middle C) of an
1789 open string. The numbers specified for @code{stringTuning} are the
1790 numbers of semitones to subtract or add, starting the specified pitch
1791 by default middle C, in string order. In the next example,
1792 @code{stringTunings} is set for the pitches e, a, d, and g
1794 @lilypond[quote,raggedright,fragment,verbatim]
1795 \context TabStaff <<
1796 \set TabStaff.stringTunings = #'(-5 -10 -15 -20)
1798 a,4 c' a e' e c' a e'
1805 No guitar special effects have been implemented.
1809 Program reference: @internalsref{Tab_note_heads_engraver}.
1813 @subsection Fret diagrams
1814 @cindex fret diagrams
1815 @cindex chord diagrams
1817 Fret diagrams can be added to music as a markup to the desired note. The
1818 markup contains information about the desired fret diagram, as shown in the
1821 @lilypond[verbatim, raggedright, quote]
1823 d'^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
1825 fis'^\markup \override #'(size . 0.75) {
1826 \override #'(finger-code . below-string) {
1827 \fret-diagram-verbose #'((place-fret 6 2 1) (barre 6 1 2)
1828 (place-fret 5 4 3) (place-fret 4 4 4)
1829 (place-fret 3 3 2) (place-fret 2 2 1)
1834 c'^\markup \override #'(dot-radius . 0.35) {
1835 \override #'(finger-code . in-dot) {
1836 \override #'(dot-color . white) {
1837 \fret-diagram-terse #"x;3-1-(;5-2;5-3;5-4;3-1-);"
1846 There are three different fret-diagram markup interfaces: standard, terse,
1847 and verbose. The three interfaces produce equivalent markups, but have
1848 varying amounts of information in the markup string. Details about the
1849 markup interfaces are found at @ref{Overview of text markup commands}.
1851 You can set a number of graphical properties according to your preference.
1852 Details about the property interface to fret diagrams are found at
1853 @internalsref{fret-diagram-interface}.
1858 Examples: @inputfileref{input/@/test,fret@/-diagram@/.ly}
1861 @node Other guitar issues
1862 @subsection Other guitar issues
1864 This example demonstrates how to include guitar position and
1865 barring indications.
1867 @lilypond[quote,raggedright,fragment,verbatim,relative=0]
1871 \override TextSpanner #'edge-text = #'("XII " . "")
1873 b16 e16 g16 e16 b16 g16\stopTextSpan
1878 Stopped (X) note heads are used in guitar music to signal a place where the
1879 guitarist must play a certain note or chord, with its fingers just
1880 touching the strings instead of fully pressing them. This gives the sound a
1881 percussive noise-like sound that still maintains part of the original
1882 pitch. It is notated with cross noteheads; this is
1883 demonstrated in @ref{Special noteheads}.
1892 * Bagpipe definitions::
1897 @node Bagpipe definitions
1898 @subsection Bagpipe definitions
1900 LilyPond contains special definitions for music for the Scottish
1901 highland bagpipe; to use them, add
1904 \include "bagpipe.ly"
1908 at the top of your input file. This lets you add the special gracenotes
1909 common to bagpipe music with short commands. For example, you could
1910 write @code{\taor} instead of
1913 \grace @{ \small G32[ d G e] @}
1916 @code{bagpipe.ly} also contains pitch definitions for the bagpipe
1917 notes in the appropiate octaves, so you do not need to worry about
1918 @code{\relative} or @code{\transpose}.
1921 @lilypond[raggedright,verbatim,quote,notime]
1922 \include "bagpipe.ly"
1923 { \grg G4 \grg a \grg b \grg c \grg d \grg e \grg f \grA g A }
1928 @node Bagpipe example
1929 @subsection Bagpipe example
1931 This is what the well known tune Amazing Grace looks like in bagpipe
1935 @lilypond[raggedright,verbatim,quote]
1936 \include "bagpipe.ly"
1939 \context { \Score \remove "Bar_number_engraver" }
1942 title = "Amazing Grace"
1944 arranger = "Trad. arr."
1949 \grg \partial 4 a8. d16
1950 \slurd d2 \grg f8[ e32 d16.]
1953 \grG a2 \grg a8. d16
1954 \slurd d2 \grg f8[ e32 d16.]
1955 \grg f2 \grg e8. f16
1958 \grg A2 \hdblf f8[ e32 d16.]
1961 \grG a2 \grg a8. d16
1962 \slurd d2 \grg f8[ e32 d16.]
1972 @node Ancient notation
1973 @section Ancient notation
1975 @cindex Vaticana, Editio
1976 @cindex Medicaea, Editio
1981 Support for ancient notation includes features for mensural notation
1982 and Gregorian Chant notation. There is also limited support for
1983 figured bass notation.
1985 Many graphical objects provide a @code{style} property, see
1988 @ref{Ancient note heads},
1990 @ref{Ancient accidentals},
1992 @ref{Ancient rests},
1994 @ref{Ancient clefs},
1996 @ref{Ancient flags},
1998 @ref{Ancient time signatures}.
2001 By manipulating such a grob property, the typographical appearance of
2002 the affected graphical objects can be accommodated for a specific
2003 notation flavor without the need for introducing any new notational
2006 In addition to the standard articulation signs described in section
2007 @ref{Articulations}, specific articulation signs for ancient notation
2012 @ref{Ancient articulations}
2015 Other aspects of ancient notation can not that easily be expressed
2016 in terms of just changing a style property of a graphical object or
2017 adding articulation signs. Some notational concepts are introduced
2018 specifically for ancient notation,
2029 If this all is too much of documentation for you, and you just want to
2030 dive into typesetting without worrying too much about the details on
2031 how to customize a context, you may have a look at the predefined
2032 contexts. Use them to set up predefined style-specific voice and
2033 staff contexts, and directly go ahead with the note entry,
2037 @ref{Gregorian Chant contexts},
2039 @ref{Mensural contexts}.
2042 There is limited support for figured bass notation which came
2043 up during the baroque period.
2050 Here are all suptopics at a glance:
2053 * Ancient note heads::
2054 * Ancient accidentals::
2058 * Ancient time signatures::
2059 * Ancient articulations::
2063 * Gregorian Chant contexts::
2064 * Mensural contexts::
2065 * Musica ficta accidentals::
2071 @node Ancient note heads
2072 @subsection Ancient note heads
2077 For ancient notation, a note head style other than the @code{default}
2078 style may be chosen. This is accomplished by setting the @code{style}
2079 property of the @internalsref{NoteHead} object to @code{baroque},
2080 @code{neomensural}, @code{mensural} or @code{petrucci}. The
2081 @code{baroque} style differs from the @code{default} style only in
2082 using a square shape for @code{\breve} note heads. The
2083 @code{neomensural} style differs from the @code{baroque} style in that
2084 it uses rhomboidal heads for whole notes and all smaller durations.
2085 Stems are centered on the note heads. This style is particularly
2086 useful when transcribing mensural music, e.g., for the incipit. The
2087 @code{mensural} style produces note heads that mimic the look of note
2088 heads in historic printings of the 16th century. Finally, the
2089 @code{petrucci} style also mimicks historic printings, but uses bigger
2092 The following example demonstrates the @code{neomensural} style
2094 @lilypond[quote,fragment,raggedright,verbatim]
2095 \set Score.skipBars = ##t
2096 \override NoteHead #'style = #'neomensural
2097 a'\longa a'\breve a'1 a'2 a'4 a'8 a'16
2100 When typesetting a piece in Gregorian Chant notation, the
2101 @internalsref{Gregorian_ligature_engraver} will automatically select
2102 the proper note heads, so there is no need to explicitly set the
2103 note head style. Still, the note head style can be set, e.g., to
2104 @code{vaticana_punctum} to produce punctum neumes. Similarly, a
2105 @internalsref{Mensural_ligature_engraver} is used to automatically
2106 assemble mensural ligatures. See @ref{Ligatures} for how ligature
2111 Examples: @inputfileref{input/@/regression,note@/-head@/-style@/.ly} gives an
2112 overview over all available note head styles.
2115 @node Ancient accidentals
2116 @subsection Ancient accidentals
2121 Use the @code{style} property of grob @internalsref{Accidental} to
2122 select ancient accidentals. Supported styles are
2123 @code{mensural}, @code{vaticana}, @code{hufnagel}, and @code{medicaea}.
2125 @lilypond[quote,raggedright,staffsize=26]
2132 \line { " " \musicglyph #"accidentals.vaticana-1"
2133 " " \musicglyph #"accidentals.vaticana0" }
2137 \line { " " \musicglyph #"accidentals.medicaea-1" }
2141 \line { " " \musicglyph #"accidentals.hufnagel-1" }
2145 \line { " " \musicglyph #"accidentals.mensural-1"
2146 " " \musicglyph #"accidentals.mensural1" }
2152 \context { \Score \remove "Bar_number_engraver" }
2154 \remove "Clef_engraver"
2155 \remove "Key_engraver"
2156 \remove "Time_signature_engraver"
2157 \remove "Staff_symbol_engraver"
2158 minimumVerticalExtent = ##f
2164 As shown, not all accidentals are supported by each style. When
2165 trying to access an unsupported accidental, LilyPond will switch to a
2166 different style, as demonstrated in
2167 @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
2169 Similarly to local accidentals, the style of the key signature can be
2170 controlled by the @code{style} property of the
2171 @internalsref{KeySignature} grob.
2175 In this manual: @ref{Pitches}, @ref{Cautionary accidentals} and
2176 @ref{Automatic accidentals} give a general introduction of the use of
2177 accidentals. @ref{Key signature} gives a general introduction of
2178 the use of key signatures.
2180 Program reference: @internalsref{KeySignature}.
2182 Examples: @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
2185 @subsection Ancient rests
2187 @cindex rests, ancient
2190 Use the @code{style} property of grob @internalsref{Rest} to select
2191 ancient rests. Supported styles are @code{classical},
2192 @code{neomensural}, and @code{mensural}. @code{classical} differs
2193 from the @code{default} style only in that the quarter rest looks like
2194 a horizontally mirrored 8th rest. The @code{neomensural} style suits
2195 well for, e.g., the incipit of a transcribed mensural piece of music.
2196 The @code{mensural} style finally mimics the appearance of rests as
2197 in historic prints of the 16th century.
2199 The following example demonstrates the @code{neomensural} style
2201 @lilypond[quote,fragment,raggedright,verbatim]
2202 \set Score.skipBars = ##t
2203 \override Rest #'style = #'neomensural
2204 r\longa r\breve r1 r2 r4 r8 r16
2207 There are no 32th and 64th rests specifically for the mensural or
2208 neo-mensural style. Instead, the rests from the default style will be
2209 taken. See @inputfileref{input/@/test,rests@/.ly} for a chart of all
2212 There are no rests in Gregorian Chant notation; instead, it uses
2217 In this manual: @ref{Rests} gives a general introduction into the use of rests.
2221 @subsection Ancient clefs
2226 LilyPond supports a variety of clefs, many of them ancient.
2228 The following table shows all ancient clefs that are supported via the
2229 @code{\clef} command. Some of the clefs use the same glyph, but
2230 differ only with respect to the line they are printed on. In such
2231 cases, a trailing number in the name is used to enumerate these clefs.
2232 Still, you can manually force a clef glyph to be typeset on an
2233 arbitrary line, as described in @ref{Clef}. The note printed to the
2234 right side of each clef in the example column denotes the @code{c'}
2235 with respect to that clef.
2237 @multitable @columnfractions .4 .4 .2
2246 modern style mensural C clef
2248 @code{neomensural-c1}, @code{neomensural-c2},@*
2249 @code{neomensural-c3}, @code{neomensural-c4}
2251 @lilypond[fragment,relative=1,notime]
2252 \clef "neomensural-c2" c
2256 petrucci style mensural C clefs, for use on different staff lines
2257 (the examples show the 2nd staff line C clef)
2259 @code{petrucci-c1}, @code{petrucci-c2},@*
2260 @code{petrucci-c3}, @code{petrucci-c4},@*
2263 @lilypond[fragment,relative=1,notime]
2265 \override NoteHead #'style = #'mensural
2270 petrucci style mensural F clef
2274 @lilypond[fragment,relative=1,notime]
2276 \override NoteHead #'style = #'mensural
2281 petrucci style mensural G clef
2285 @lilypond[fragment,relative=1,notime]
2287 \override NoteHead #'style = #'mensural
2292 historic style mensural C clef
2294 @code{mensural-c1}, @code{mensural-c2},@*
2295 @code{mensural-c3}, @code{mensural-c4}
2297 @lilypond[fragment,relative=1,notime]
2299 \override NoteHead #'style = #'mensural
2304 historic style mensural F clef
2308 @lilypond[fragment,relative=1,notime]
2310 \override NoteHead #'style = #'mensural
2315 historic style mensural G clef
2319 @lilypond[fragment,relative=1,notime]
2321 \override NoteHead #'style = #'mensural
2326 Editio Vaticana style do clef
2328 @code{vaticana-do1}, @code{vaticana-do2},@*
2331 @lilypond[fragment,relative=1,notime]
2332 \override Staff.StaffSymbol #'line-count = #4
2333 \override Staff.StaffSymbol #'color = #red
2334 \override Staff.LedgerLineSpanner #'color = #red
2335 \override Voice.Stem #'transparent = ##t
2336 \override NoteHead #'style = #'vaticana.punctum
2337 \clef "vaticana-do2"
2342 Editio Vaticana style fa clef
2344 @code{vaticana-fa1}, @code{vaticana-fa2}
2346 @lilypond[fragment,relative=1,notime]
2347 \override Staff.StaffSymbol #'line-count = #4
2348 \override Staff.StaffSymbol #'color = #red
2349 \override Staff.LedgerLineSpanner #'color = #red
2350 \override Voice.Stem #'transparent = ##t
2351 \override NoteHead #'style = #'vaticana.punctum
2352 \clef "vaticana-fa2"
2357 Editio Medicaea style do clef
2359 @code{medicaea-do1}, @code{medicaea-do2},@*
2362 @lilypond[fragment,relative=1,notime]
2363 \override Staff.StaffSymbol #'line-count = #4
2364 \override Staff.StaffSymbol #'color = #red
2365 \override Staff.LedgerLineSpanner #'color = #red
2366 \override Voice.Stem #'transparent = ##t
2367 \override NoteHead #'style = #'medicaea.punctum
2368 \clef "medicaea-do2"
2373 Editio Medicaea style fa clef
2375 @code{medicaea-fa1}, @code{medicaea-fa2}
2377 @lilypond[fragment,relative=1,notime]
2378 \override Staff.StaffSymbol #'line-count = #4
2379 \override Staff.StaffSymbol #'color = #red
2380 \override Staff.LedgerLineSpanner #'color = #red
2381 \override Voice.Stem #'transparent = ##t
2382 \override NoteHead #'style = #'medicaea.punctum
2383 \clef "medicaea-fa2"
2388 historic style hufnagel do clef
2390 @code{hufnagel-do1}, @code{hufnagel-do2},@*
2393 @lilypond[fragment,relative=1,notime]
2394 \override Staff.StaffSymbol #'line-count = #4
2395 \override Staff.StaffSymbol #'color = #red
2396 \override Staff.LedgerLineSpanner #'color = #red
2397 \override Voice.Stem #'transparent = ##t
2398 \override NoteHead #'style = #'hufnagel.punctum
2399 \clef "hufnagel-do2"
2404 historic style hufnagel fa clef
2406 @code{hufnagel-fa1}, @code{hufnagel-fa2}
2408 @lilypond[fragment,relative=1,notime]
2409 \override Staff.StaffSymbol #'line-count = #4
2410 \override Staff.StaffSymbol #'color = #red
2411 \override Staff.LedgerLineSpanner #'color = #red
2412 \override Voice.Stem #'transparent = ##t
2413 \override NoteHead #'style = #'hufnagel.punctum
2414 \clef "hufnagel-fa2"
2419 historic style hufnagel combined do/fa clef
2421 @code{hufnagel-do-fa}
2423 @lilypond[fragment,relative=1,notime]
2424 \override Staff.StaffSymbol #'color = #red
2425 \override Staff.LedgerLineSpanner #'color = #red
2426 \override Voice.Stem #'transparent = ##t
2427 \override NoteHead #'style = #'hufnagel.punctum
2428 \clef "hufnagel-do-fa"
2435 @emph{Modern style} means ``as is typeset in contemporary editions of
2436 transcribed mensural music''.
2438 @emph{Petrucci style} means ``inspired by printings published by the
2439 famous engraver Petrucci (1466-1539)''.
2441 @emph{Historic style} means ``as was typeset or written in historic
2442 editions (other than those of Petrucci)''.
2444 @emph{Editio XXX style} means ``as is/was printed in Editio XXX''.
2446 Petrucci used C clefs with differently balanced left-side vertical
2447 beams, depending on which staff line it is printed.
2451 In this manual: see @ref{Clef}.
2455 The mensural g clef is mapped to the Petrucci g clef.
2460 @subsection Ancient flags
2465 Use the @code{flag-style} property of grob @internalsref{Stem} to
2466 select ancient flags. Besides the @code{default} flag style,
2467 only the @code{mensural} style is supported
2469 @lilypond[quote,fragment,raggedright,verbatim]
2470 \override Stem #'flag-style = #'mensural
2471 \override Stem #'thickness = #1.0
2472 \override NoteHead #'style = #'mensural
2474 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
2475 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
2478 Note that the innermost flare of each mensural flag always is
2479 vertically aligned with a staff line.
2481 There is no particular flag style for neo-mensural notation. Hence,
2482 when typesetting the incipit of a transcribed piece of mensural
2483 music, the default flag style should be used. There are no flags in
2484 Gregorian Chant notation.
2488 The attachment of ancient flags to stems is slightly off due to a
2489 change in early 2.3.x.
2491 Vertically aligning each flag with a staff line assumes that stems
2492 always end either exactly on or exactly in the middle between two
2493 staff lines. This may not always be true when using advanced layout
2494 features of classical notation (which however are typically out of
2495 scope for mensural notation).
2497 @node Ancient time signatures
2498 @subsection Ancient time signatures
2500 @cindex time signatures
2503 There is limited support for mensural time signatures. The
2504 glyphs are hard-wired to particular time fractions. In other words,
2505 to get a particular mensural signature glyph with the @code{\time n/m}
2506 command, @code{n} and @code{m} have to be chosen according to the
2509 @lilypond[quote,raggedright]
2514 \remove Staff_symbol_engraver
2515 \remove Clef_engraver
2516 \remove Time_signature_engraver
2520 \set Score.timing = ##f
2521 \set Score.barAlways = ##t
2522 s_\markup { "\\time 4/4" }^\markup { " " \musicglyph #"timesig.neomensural44" }
2524 s_\markup { "\\time 2/2" }^\markup { " " \musicglyph #"timesig.neomensural22" }
2526 s_\markup { "\\time 6/4" }^\markup { " " \musicglyph #"timesig.neomensural64" }
2528 s_\markup { "\\time 6/8" }^\markup { " " \musicglyph #"timesig.neomensural68" }
2530 s_\markup { "\\time 3/2" }^\markup { " " \musicglyph #"timesig.neomensural32" }
2532 s_\markup { "\\time 3/4" }^\markup { " " \musicglyph #"timesig.neomensural34" }
2534 s_\markup { "\\time 9/4" }^\markup { " " \musicglyph #"timesig.neomensural94" }
2536 s_\markup { "\\time 9/8" }^\markup { " " \musicglyph #"timesig.neomensural98" }
2538 s_\markup { "\\time 4/8" }^\markup { " " \musicglyph #"timesig.neomensural48" }
2540 s_\markup { "\\time 2/4" }^\markup { " " \musicglyph #"timesig.neomensural24" }
2544 Use the @code{style} property of grob @internalsref{TimeSignature} to
2545 select ancient time signatures. Supported styles are
2546 @code{neomensural} and @code{mensural}. The above table uses the
2547 @code{neomensural} style. This style is appropriate for the
2548 incipit of transcriptions of mensural pieces. The @code{mensural}
2549 style mimics the look of historical printings of the 16th century.
2551 The following examples show the differences in style,
2553 @lilypond[raggedright,fragment,relative=1,quote]
2558 c1^\markup { \hspace #-2.0 \typewriter default }
2560 \override Staff.TimeSignature #'style = #'numbered
2562 c1^\markup { \hspace #-2.0 \typewriter numbered }
2564 \override Staff.TimeSignature #'style = #'mensural
2566 c1^\markup { \hspace #-2.0 \typewriter mensural }
2568 \override Staff.TimeSignature #'style = #'neomensural
2570 c1^\markup { \hspace #-2.0 \typewriter neomensural }
2571 \override Staff.TimeSignature #'style = #'single-digit
2573 c1^\markup { \hspace #-2.0 \typewriter single-digit }
2579 This manual: @ref{Time signature} gives a general introduction to
2580 the use of time signatures.
2584 Ratios of note durations do not change with the time signature. For
2585 example, the ratio of 1 brevis = 3 semibrevis (tempus perfectum) must
2586 be made by hand, by setting
2589 breveTP = #(ly:make-duration -1 0 3 2)
2595 This sets @code{breveTP} to 3/2 times 2 = 3 times a whole note.
2597 The @code{old6/8alt} symbol (an alternate symbol for 6/8) is not
2598 addressable with @code{\time}. Use a @code{\markup} instead
2600 @node Ancient articulations
2601 @subsection Ancient articulations
2603 @cindex articulations
2605 In addition to the standard articulation signs described in section
2606 @ref{Articulations}, articulation signs for ancient notation are
2607 provided. These are specifically designed for use with notation in
2608 Editio Vaticana style.
2610 @lilypond[quote,raggedright,verbatim]
2611 \include "gregorian-init.ly"
2613 \context VaticanaVoice {
2614 \override Staff.StaffSymbol #'color = #red
2615 \override Staff.LedgerLineSpanner #'color = #red
2616 \override TextScript #'font-family = #'typewriter
2617 \override TextScript #'font-shape = #'upright
2618 \override Script #'padding = #-0.1
2620 a4\circulus_"circulus" s1
2621 a4\semicirculus_"semicirculus" s1 s
2622 a4\accentus_"accentus" s1
2623 \[ a4_"episem" \episemInitium \pes b \flexa a \episemFinis \]
2630 Some articulations are vertically placed too closely to the
2631 correpsonding note heads.
2634 @subsection Custodes
2639 A @emph{custos} (plural: @emph{custodes}; Latin word for `guard') is a
2640 symbol that appears at the end of a staff. It anticipates the pitch
2641 of the first note(s) of the following line thus helping the performer
2642 to manage line breaks during performance.
2644 Custodes were frequently used in music notation until the 17th
2645 century. Nowadays, they have survived only in a few particular forms
2646 of musical notation such as contemporary editions of Gregorian chant
2647 like the @emph{editio vaticana}. There are different custos glyphs
2648 used in different flavors of notational style.
2650 For typesetting custodes, just put a @internalsref{Custos_engraver} into the
2651 @internalsref{Staff} context when declaring the @code{\layout} block,
2652 as shown in the following example
2658 \consists Custos_engraver
2659 Custos \override #'style = #'mensural
2664 The result looks like this
2666 @lilypond[quote,raggedright]
2670 \override Staff.Custos #'style = #'mensural
2675 \context { \Staff \consists Custos_engraver }
2680 The custos glyph is selected by the @code{style} property. The styles
2681 supported are @code{vaticana}, @code{medicaea}, @code{hufnagel}, and
2682 @code{mensural}. They are demonstrated in the following fragment
2684 @lilypond[quote,raggedright,fragment]
2685 \new Lyrics \lyricmode {
2687 \typewriter "vaticana"
2688 \line { " " \musicglyph #"custodes.vaticana.u0" }
2691 \typewriter "medicaea"
2692 \line { " " \musicglyph #"custodes.medicaea.u0" }
2695 \typewriter "hufnagel"
2696 \line { " " \musicglyph #"custodes.hufnagel.u0" }
2699 \typewriter "mensural"
2700 \line { " " \musicglyph #"custodes.mensural.u0" }
2707 Program reference: @internalsref{Custos}.
2709 Examples: @inputfileref{input/@/regression,custos@/.ly}.
2713 @subsection Divisiones
2719 A @emph{divisio} (plural: @emph{divisiones}; Latin word for
2720 `division') is a staff context symbol that is used to structure
2721 Gregorian music into phrases and sections. The musical meaning of
2722 @emph{divisio minima}, @emph{divisio maior}, and @emph{divisio maxima}
2723 can be characterized as short, medium, and long pause, somewhat like
2724 the breathmarks from @ref{Breath marks}. The @emph{finalis} sign not
2725 only marks the end of a chant, but is also frequently used within a
2726 single antiphonal/responsorial chant to mark the end of each section.
2729 To use divisiones, include the file @file{gregorian@/-init@/.ly}. It
2730 contains definitions that you can apply by just inserting
2731 @code{\divisioMinima}, @code{\divisioMaior}, @code{\divisioMaxima},
2732 and @code{\finalis} at proper places in the input. Some editions use
2733 @emph{virgula} or @emph{caesura} instead of divisio minima.
2734 Therefore, @file{gregorian@/-init@/.ly} also defines @code{\virgula} and
2737 @lilypondfile[quote,raggedright]{divisiones.ly}
2741 @cindex @code{\virgula}
2743 @cindex @code{\caesura}
2745 @cindex @code{\divisioMinima}
2746 @code{\divisioMinima},
2747 @cindex @code{\divisioMaior}
2748 @code{\divisioMaior},
2749 @cindex @code{\divisioMaxima}
2750 @code{\divisioMaxima},
2751 @cindex @code{\finalis}
2756 In this manual: @ref{Breath marks}.
2758 Program reference: @internalsref{BreathingSign}.
2760 Examples: @inputfileref{input/@/test,divisiones@/.ly}.
2763 @subsection Ligatures
2767 @c TODO: Should double check if I recalled things correctly when I wrote
2768 @c down the following paragraph by heart.
2770 A ligature is a graphical symbol that represents at least two distinct
2771 notes. Ligatures originally appeared in the manuscripts of Gregorian
2772 chant notation to denote ascending or descending sequences of notes.
2774 Ligatures are entered by enclosing them in @code{\[} and @code{\]}.
2775 Some ligature styles may need additional input syntax specific for
2776 this particular type of ligature. By default, the
2777 @internalsref{LigatureBracket} engraver just puts a square bracket
2780 @lilypond[quote,raggedright,verbatim]
2788 To select a specific style of ligatures, a proper ligature engraver
2789 has to be added to the @internalsref{Voice} context, as explained in
2790 the following subsections. Only white mensural ligatures
2791 are supported with certain limitations.
2797 Ligatures need special spacing that has not yet been implemented. As
2798 a result, there is too much space between ligatures most of the time,
2799 and line breaking often is unsatisfactory. Also, lyrics do not
2800 correctly align with ligatures.
2802 Accidentals must not be printed within a ligature, but instead need to
2803 be collected and printed in front of it.
2805 Augmentum dots within ligatures are not handled correctly.
2807 The syntax still uses the deprecated infix style @code{\[ music expr
2808 \]}. For consistency reasons, it will eventually be changed to
2809 postfix style @code{note\[ ... note\]}. Alternatively, the file
2810 @file{gregorian@/-init@/.ly} can be included; it provides a scheme
2813 \ligature @var{music expr}
2815 with the same effect and is believed to be stable.
2818 * White mensural ligatures::
2819 * Gregorian square neumes ligatures::
2822 @node White mensural ligatures
2823 @subsubsection White mensural ligatures
2825 @cindex Mensural ligatures
2826 @cindex White mensural ligatures
2828 There is limited support for white mensural ligatures.
2830 To engrave white mensural ligatures, in the layout block put the
2831 @internalsref{Mensural_ligature_engraver} into the
2832 @internalsref{Voice} context, and remove the
2833 @internalsref{Ligature_bracket_engraver}, like this
2839 \remove Ligature_bracket_engraver
2840 \consists Mensural_ligature_engraver
2845 There is no additional input language to describe the shape of a
2846 white mensural ligature. The shape is rather determined solely from
2847 the pitch and duration of the enclosed notes. While this approach may
2848 take a new user a while to get accustomed to, it has the great advantage
2849 that the full musical information of the ligature is known internally.
2850 This is not only required for correct MIDI output, but also allows for
2851 automatic transcription of the ligatures.
2856 \set Score.timing = ##f
2857 \set Score.defaultBarType = "empty"
2858 \override NoteHead #'style = #'neomensural
2859 \override Staff.TimeSignature #'style = #'neomensural
2863 \[ d\longa c\breve f e d \]
2865 \[ c'\maxima d'\longa \]
2869 @lilypond[quote,raggedright]
2872 \set Score.timing = ##f
2873 \set Score.defaultBarType = "empty"
2874 \override NoteHead #'style = #'neomensural
2875 \override Staff.TimeSignature #'style = #'neomensural
2879 \[ d\longa c\breve f e d \]
2881 \[ c'\maxima d'\longa \]
2888 \remove Ligature_bracket_engraver
2889 \consists Mensural_ligature_engraver
2895 Without replacing @internalsref{Ligature_bracket_engraver} with
2896 @internalsref{Mensural_ligature_engraver}, the same music transcribes
2899 @lilypond[quote,raggedright]
2901 \set Score.timing = ##f
2902 \set Score.defaultBarType = "empty"
2903 \override NoteHead #'style = #'neomensural
2904 \override Staff.TimeSignature #'style = #'neomensural
2908 \[ d\longa c\breve f e d \]
2910 \[ c'\maxima d'\longa \]
2918 The invisible rests (@code{s4}) in the example are used to compensate
2919 for the poor horizontal spacing.
2921 @node Gregorian square neumes ligatures
2922 @subsubsection Gregorian square neumes ligatures
2924 @cindex Square neumes ligatures
2925 @cindex Gregorian square neumes ligatures
2927 There is limited support for Gregorian square neumes notation
2928 (following the style of the Editio Vaticana). Core ligatures can
2929 already be typeset, but essential issues for serious typesetting are
2930 still lacking, such as (among others) horizontal alignment of multiple
2931 ligatures, lyrics alignment and proper handling of accidentals.
2934 The following table contains the extended neumes table of the 2nd
2935 volume of the Antiphonale Romanum (@emph{Liber Hymnarius}), published
2936 1983 by the monks of Solesmes.
2938 @multitable @columnfractions .4 .2 .2 .2
2955 @c TODO: \layout block is identical in all of the below examples.
2956 @c Therefore, it should somehow be included rather than duplicated all
2959 @c why not make identifiers in ly/engraver-init.ly? --hwn
2961 @c Because it's just used to typeset plain notes without
2962 @c a staff for demonstration purposes rather than something
2963 @c special of Gregorian chant notation. --jr
2968 @lilypond[staffsize=26,linewidth=1.5\cm]
2969 \include "gregorian-init.ly"
2974 \noBreak s^\markup {"a"} \noBreak
2976 % Punctum Inclinatum
2978 \noBreak s^\markup {"b"}
2980 \layout { \neumeDemoLayout }}
2983 @lilypond[staffsize=26,linewidth=2.5\cm]
2984 \include "gregorian-init.ly"
2987 % Punctum Auctum Ascendens
2988 \[ \auctum \ascendens b \]
2989 \noBreak s^\markup {"c"} \noBreak
2991 % Punctum Auctum Descendens
2992 \[ \auctum \descendens b \]
2993 \noBreak s^\markup {"d"} \noBreak
2995 % Punctum Inclinatum Auctum
2996 \[ \inclinatum \auctum b \]
2997 \noBreak s^\markup {"e"}
2999 \layout { \neumeDemoLayout }}
3002 @lilypond[staffsize=26,linewidth=1.0\cm]
3003 \include "gregorian-init.ly"
3006 % Punctum Inclinatum Parvum
3007 \[ \inclinatum \deminutum b \]
3008 \noBreak s^\markup {"f"}
3010 \layout { \neumeDemoLayout }}
3016 @lilypond[staffsize=26,linewidth=1.0\cm]
3017 \include "gregorian-init.ly"
3022 \noBreak s^\markup {"g"}
3024 \layout { \neumeDemoLayout }}
3030 @code{3. Apostropha vel Stropha}
3032 @lilypond[staffsize=26,linewidth=1.0\cm]
3033 \include "gregorian-init.ly"
3038 \noBreak s^\markup {"h"}
3040 \layout { \neumeDemoLayout }}
3043 @lilypond[staffsize=26,linewidth=1.0\cm]
3044 \include "gregorian-init.ly"
3048 \[ \stropha \auctum b \]
3049 \noBreak s^\markup {"i"}
3051 \layout { \neumeDemoLayout }}
3058 @lilypond[staffsize=26,linewidth=1.0\cm]
3059 \include "gregorian-init.ly"
3064 \noBreak s^\markup {"j"}
3066 \layout { \neumeDemoLayout }}
3072 @code{5. Clivis vel Flexa}
3074 @lilypond[staffsize=26,linewidth=1.0\cm]
3075 \include "gregorian-init.ly"
3082 \layout { \neumeDemoLayout }}
3085 @lilypond[staffsize=26,linewidth=2.0\cm]
3086 \include "gregorian-init.ly"
3089 % Clivis Aucta Descendens
3090 \[ b \flexa \auctum \descendens g \]
3091 \noBreak s^\markup {"l"} \noBreak
3093 % Clivis Aucta Ascendens
3094 \[ b \flexa \auctum \ascendens g \]
3095 \noBreak s^\markup {"m"}
3097 \layout { \neumeDemoLayout }}
3100 @lilypond[staffsize=26,linewidth=1.0\cm]
3101 \include "gregorian-init.ly"
3105 \[ b \flexa \deminutum g \]
3108 \layout { \neumeDemoLayout }}
3112 @code{6. Podatus vel Pes}
3114 @lilypond[staffsize=26,linewidth=1.0\cm]
3115 \include "gregorian-init.ly"
3122 \layout { \neumeDemoLayout }}
3125 @lilypond[staffsize=26,linewidth=2.0\cm]
3126 \include "gregorian-init.ly"
3129 % Pes Auctus Descendens
3130 \[ g \pes \auctum \descendens b \]
3131 \noBreak s^\markup {"p"} \noBreak
3133 % Pes Auctus Ascendens
3134 \[ g \pes \auctum \ascendens b \]
3135 \noBreak s^\markup {"q"}
3137 \layout { \neumeDemoLayout }}
3140 @lilypond[staffsize=26,linewidth=1.0\cm]
3141 \include "gregorian-init.ly"
3145 \[ g \pes \deminutum b \]
3148 \layout { \neumeDemoLayout }}
3152 @code{7. Pes Quassus}
3154 @lilypond[staffsize=26,linewidth=1.0\cm]
3155 \include "gregorian-init.ly"
3159 \[ \oriscus g \pes \virga b \]
3162 \layout { \neumeDemoLayout }}
3165 @lilypond[staffsize=26,linewidth=1.0\cm]
3166 \include "gregorian-init.ly"
3169 % Pes Quassus Auctus Descendens
3170 \[ \oriscus g \pes \auctum \descendens b \]
3173 \layout { \neumeDemoLayout }}
3178 @code{8. Quilisma Pes}
3180 @lilypond[staffsize=26,linewidth=1.0\cm]
3181 \include "gregorian-init.ly"
3185 \[ \quilisma g \pes b \]
3188 \layout { \neumeDemoLayout }}
3191 @lilypond[staffsize=26,linewidth=1.0\cm]
3192 \include "gregorian-init.ly"
3195 % Quilisma Pes Auctus Descendens
3196 \[ \quilisma g \pes \auctum \descendens b \]
3199 \layout { \neumeDemoLayout }}
3204 @code{9. Podatus Initio Debilis}
3206 @lilypond[staffsize=26,linewidth=1.0\cm]
3207 \include "gregorian-init.ly"
3210 % Pes Initio Debilis
3211 \[ \deminutum g \pes b \]
3214 \layout { \neumeDemoLayout }}
3217 @lilypond[staffsize=26,linewidth=1.0\cm]
3218 \include "gregorian-init.ly"
3221 % Pes Auctus Descendens Initio Debilis
3222 \[ \deminutum g \pes \auctum \descendens b \]
3225 \layout { \neumeDemoLayout }}
3232 @lilypond[staffsize=26,linewidth=1.0\cm]
3233 \include "gregorian-init.ly"
3237 \[ a \pes b \flexa g \]
3240 \layout { \neumeDemoLayout }}
3243 @lilypond[staffsize=26,linewidth=1.0\cm]
3244 \include "gregorian-init.ly"
3247 % Torculus Auctus Descendens
3248 \[ a \pes b \flexa \auctum \descendens g \]
3251 \layout { \neumeDemoLayout }}
3254 @lilypond[staffsize=26,linewidth=1.0\cm]
3255 \include "gregorian-init.ly"
3258 % Torculus Deminutus
3259 \[ a \pes b \flexa \deminutum g \]
3262 \layout { \neumeDemoLayout }}
3266 @code{11. Torculus Initio Debilis}
3268 @lilypond[staffsize=26,linewidth=1.0\cm]
3269 \include "gregorian-init.ly"
3272 % Torculus Initio Debilis
3273 \[ \deminutum a \pes b \flexa g \]
3276 \layout { \neumeDemoLayout }}
3279 @lilypond[staffsize=26,linewidth=1.0\cm]
3280 \include "gregorian-init.ly"
3283 % Torculus Auctus Descendens Initio Debilis
3284 \[ \deminutum a \pes b \flexa \auctum \descendens g \]
3287 \layout { \neumeDemoLayout }}
3290 @lilypond[staffsize=26,linewidth=1.0\cm]
3291 \include "gregorian-init.ly"
3294 % Torculus Deminutus Initio Debilis
3295 \[ \deminutum a \pes b \flexa \deminutum g \]
3298 \layout { \neumeDemoLayout }}
3302 @code{12. Porrectus}
3304 @lilypond[staffsize=26,linewidth=1.0\cm]
3305 \include "gregorian-init.ly"
3309 \[ a \flexa g \pes b \]
3312 \layout { \neumeDemoLayout }}
3315 @lilypond[staffsize=26,linewidth=1.0\cm]
3316 \include "gregorian-init.ly"
3319 % Porrectus Auctus Descendens
3320 \[ a \flexa g \pes \auctum \descendens b \]
3323 \layout { \neumeDemoLayout }}
3326 @lilypond[staffsize=26,linewidth=1.0\cm]
3327 \include "gregorian-init.ly"
3330 % Porrectus Deminutus
3331 \[ a \flexa g \pes \deminutum b \]
3334 \layout { \neumeDemoLayout }}
3340 @lilypond[staffsize=26,linewidth=1.0\cm]
3341 \include "gregorian-init.ly"
3345 \[ \virga b \inclinatum a \inclinatum g \]
3348 \layout { \neumeDemoLayout }
3352 @lilypond[staffsize=26,linewidth=1.0\cm]
3353 \include "gregorian-init.ly"
3357 \[ \virga b \inclinatum a \inclinatum \auctum g \]
3360 \layout { \neumeDemoLayout }}
3363 @lilypond[staffsize=26,linewidth=1.0\cm]
3364 \include "gregorian-init.ly"
3367 % Climacus Deminutus
3368 \[ \virga b \inclinatum a \inclinatum \deminutum g \]
3371 \layout { \neumeDemoLayout }}
3375 @code{14. Scandicus}
3377 @lilypond[staffsize=26,linewidth=1.0\cm]
3378 \include "gregorian-init.ly"
3382 \[ g \pes a \virga b \]
3385 \layout { \neumeDemoLayout }}
3388 @lilypond[staffsize=26,linewidth=1.0\cm]
3389 \include "gregorian-init.ly"
3392 % Scandicus Auctus Descendens
3393 \[ g \pes a \pes \auctum \descendens b \]
3396 \layout { \neumeDemoLayout }}
3399 @lilypond[staffsize=26,linewidth=1.0\cm]
3400 \include "gregorian-init.ly"
3403 % Scandicus Deminutus
3404 \[ g \pes a \pes \deminutum b \]
3407 \layout { \neumeDemoLayout }}
3413 @lilypond[staffsize=26,linewidth=1.0\cm]
3414 \include "gregorian-init.ly"
3418 \[ g \oriscus a \pes \virga b \]
3421 \layout { \neumeDemoLayout }}
3424 @lilypond[staffsize=26,linewidth=1.0\cm]
3425 \include "gregorian-init.ly"
3428 % Salicus Auctus Descendens
3429 \[ g \oriscus a \pes \auctum \descendens b \]
3432 \layout { \neumeDemoLayout }}
3439 @lilypond[staffsize=26,linewidth=1.0\cm]
3440 \include "gregorian-init.ly"
3444 \[ \stropha b \stropha b \stropha a \]
3447 \layout { \neumeDemoLayout }
3456 Unlike most other neumes notation systems, the input language for
3457 neumes does not reflect the typographical appearance, but is designed
3458 to focus on musical meaning. For example, @code{\[ a \pes b
3459 \flexa g \]} produces a Torculus consisting of three Punctum heads,
3460 while @code{\[ a \flexa g \pes b \]} produces a Porrectus with a
3461 curved flexa shape and only a single Punctum head. There is no
3462 command to explicitly typeset the curved flexa shape; the decision of
3463 when to typeset a curved flexa shape is based on the musical
3464 input. The idea of this approach is to separate the musical aspects
3465 of the input from the notation style of the output. This way, the
3466 same input can be reused to typeset the same music in a different
3467 style of Gregorian chant notation.
3469 The following table shows the code fragments that produce the
3470 ligatures in the above neumes table. The letter in the first column
3471 in each line of the below table indicates to which ligature in the
3472 above table it refers. The second column gives the name of the
3473 ligature. The third column shows the code fragment that produces this
3474 ligature, using @code{g}, @code{a}, and @code{b} as example pitches.
3476 @multitable @columnfractions .02 .31 .67
3496 @code{\[ \inclinatum b \]}
3504 @code{\[ \auctum \ascendens b \]}
3512 @code{\[ \auctum \descendens b \]}
3517 Punctum Inclinatum@*
3520 @code{\[ \inclinatum \auctum b \]}
3525 Punctum Inclinatum@*
3527 @code{\[ \inclinatum \deminutum b \]}
3534 @code{\[ \virga b \]}
3541 @code{\[ \stropha b \]}
3548 @code{\[ \stropha \auctum b \]}
3555 @code{\[ \oriscus b \]}
3562 @code{\[ b \flexa g \]}
3570 @code{\[ b \flexa \auctum \descendens g \]}
3578 @code{\[ b \flexa \auctum \ascendens g \]}
3585 @code{\[ b \flexa \deminutum g \]}
3592 @code{\[ g \pes b \]}
3600 @code{\[ g \pes \auctum \descendens b \]}
3608 @code{\[ g \pes \auctum \ascendens b \]}
3615 @code{\[ g \pes \deminutum b \]}
3622 @code{\[ \oriscus g \pes \virga b \]}
3628 Auctus Descendens @tab
3629 @code{\[ \oriscus g \pes \auctum \descendens b \]}
3636 @code{\[ \quilisma g \pes b \]}
3644 @code{\[ \quilisma g \pes \auctum \descendens b \]}
3651 @code{\[ \deminutum g \pes b \]}
3656 Pes Auctus Descendens@*
3659 @code{\[ \deminutum g \pes \auctum \descendens b \]}
3666 @code{\[ a \pes b \flexa g \]}
3674 @code{\[ a \pes b \flexa \auctum \descendens g \]}
3681 @code{\[ a \pes b \flexa \deminutum g \]}
3686 Torculus Initio Debilis
3688 @code{\[ \deminutum a \pes b \flexa g \]}
3694 Descendens Initio Debilis
3696 @code{\[ \deminutum a \pes b \flexa \auctum \descendens g \]}
3701 Torculus Deminutus@*
3704 @code{\[ \deminutum a \pes b \flexa \deminutum g \]}
3711 @code{\[ a \flexa g \pes b \]}
3719 @code{\[ a \flexa g \pes \auctum \descendens b \]}
3726 @code{\[ a \flexa g \pes \deminutum b \]}
3733 @code{\[ \virga b \inclinatum a \inclinatum g \]}
3740 @code{\[ \virga b \inclinatum a \inclinatum \auctum g \]}
3747 @code{\[ \virga b \inclinatum a \inclinatum \deminutum g \]}
3754 @code{\[ g \pes a \virga b \]}
3762 @code{\[ g \pes a \pes \auctum \descendens b \]}
3769 @code{\[ g \pes a \pes \deminutum b \]}
3776 @code{\[ g \oriscus a \pes \virga b \]}
3781 Salicus Auctus Descendens
3783 @code{\[ g \oriscus a \pes \auctum \descendens b \]}
3790 @code{\[ \stropha b \stropha b \stropha a \]}
3795 The following head prefixes are supported
3797 @cindex @code{\virga}
3799 @cindex @code{\stropha}
3801 @cindex @code{\inclinatum}
3803 @cindex @code{\auctum}
3805 @cindex @code{\descendens}
3807 @cindex @code{\ascendens}
3809 @cindex @code{\oriscus}
3811 @cindex @code{\quilisma}
3813 @cindex @code{\deminutum}
3816 Head prefixes can be accumulated, though restrictions apply. For
3817 example, either @code{\descendens} or @code{\ascendens} can be applied
3818 to a head, but not both to the same head.
3821 @cindex @code{\flexa}
3822 Two adjacent heads can be tied together with the @code{\pes} and
3823 @code{\flexa} infix commands for a rising and falling line of melody,
3828 @node Gregorian Chant contexts
3829 @subsection Gregorian Chant contexts
3831 @cindex VaticanaVoiceContext
3832 @cindex VaticanaStaffContext
3834 The predefined @code{VaticanaVoiceContext} and
3835 @code{VaticanaStaffContext} can be used to engrave a piece of
3836 Gregorian Chant in the style of the Editio Vaticana. These contexts
3837 initialize all relevant context properties and grob properties to
3838 proper values, so you can immediately go ahead entering the chant, as
3839 the following excerpt demonstrates
3841 @lilypond[quote,raggedright,packed,verbatim]
3842 \include "gregorian-init.ly"
3845 \context VaticanaVoice = "cantus" {
3846 \override Staff.StaffSymbol #'color = #red
3847 \override Staff.LedgerLineSpanner #'color = #red
3848 \override Score.BarNumber #'transparent = ##t {
3849 \[ c'\melisma c' \flexa a \]
3850 \[ a \flexa \deminutum g\melismaEnd \]
3852 \[ f\melisma \pes a c' c' \pes d'\melismaEnd \]
3853 c' \divisioMinima \break
3854 \[ c'\melisma c' \flexa a \]
3855 \[ a \flexa \deminutum g\melismaEnd \] f \divisioMinima
3858 \lyricsto "cantus" \new Lyrics {
3859 San- ctus, San- ctus, San- ctus
3866 @node Mensural contexts
3867 @subsection Mensural contexts
3869 @cindex MensuralVoiceContext
3870 @cindex MensuralStaffContext
3872 The predefined @code{MensuralVoiceContext} and
3873 @code{MensuralStaffContext} can be used to engrave a piece in mensural
3874 style. These contexts initialize all relevant context properties and
3875 grob properties to proper values, so you can immediately go ahead
3876 entering the chant, as the following excerpt demonstrates
3878 @lilypond[quote,raggedright,verbatim]
3881 \context MensuralVoice = "discantus" \transpose c c' {
3882 \override Score.BarNumber #'transparent = ##t {
3883 c'1\melisma bes a g\melismaEnd
3885 \[ f1\melisma a c'\breve d'\melismaEnd \]
3887 c'\breve\melisma a1 g1\melismaEnd
3888 fis\longa^\signumcongruentiae
3891 \lyricsto "discantus" \new Lyrics {
3892 San -- ctus, San -- ctus, San -- ctus
3898 @node Musica ficta accidentals
3899 @subsection Musica ficta accidentals
3901 In European music from before about 1600, singers were often expected
3902 to chromatically alter notes at their own initiative. This is called
3903 ``Musica Ficta''. In modern transcriptions, these accidentals are
3904 usually printed over the note.
3906 @cindex Musica ficta
3908 Support for such suggested accidentals is included, and can be
3909 switched on by setting @code{suggestAccidentals} to true.
3911 @cindex @code{suggestAccidentals}
3913 @lilypond[verbatim,fragment,relative=1]
3915 \set suggestAccidentals = ##t
3921 Program reference: @internalsref{Accidental_engraver} engraver and the
3922 @internalsref{AccidentalSuggestion} object.
3925 @subsection Figured bass
3927 @cindex Basso continuo
3929 @c TODO: musicological blurb about FB
3932 LilyPond has limited support for figured bass
3934 @lilypond[quote,raggedright,verbatim,fragment]
3936 \context Voice { \clef bass dis4 c d ais g fis}
3937 \context FiguredBass \figuremode {
3938 < 6 >4 < 7 >8 < 6+ [_!] >
3945 The support for figured bass consists of two parts: there is an input
3946 mode, introduced by @code{\figuremode}, where you can enter bass figures
3947 as numbers, and there is a context called @internalsref{FiguredBass} that
3948 takes care of making @internalsref{BassFigure} objects.
3950 In figures input mode, a group of bass figures is delimited by
3951 @code{<} and @code{>}. The duration is entered after the @code{>}
3955 @lilypond[quote,raggedright,fragment]
3956 \context FiguredBass
3957 \figuremode { <4 6> }
3960 Accidentals are added when you append @code{-}, @code{!}, and @code{+}
3966 @lilypond[quote,raggedright,fragment]
3967 \context FiguredBass
3968 \figuremode { <4- 6+ 7!> }
3971 Spaces or dashes may be inserted by using @code{_}. Brackets are
3972 introduced with @code{[} and @code{]}. You can also include text
3973 strings and text markups, see @ref{Overview of text markup commands}.
3976 < [4 6] 8 [_! 12] > < 5 \markup @{ + \number 6 @} >
3978 @lilypond[quote,raggedright,fragment]
3979 \context FiguredBass
3980 \figuremode { < [4 6] 8 [_! 12] > < 5 \markup{ + \number 6 } > }
3984 Although the support for figured bass may superficially resemble chord
3985 support, it works much simpler. The @code{\figuremode} mode simply
3986 stores the numbers and @internalsref{FiguredBass} context prints
3987 them as entered. There is no conversion to pitches and no
3988 realizations of the bass are played in the MIDI file.
3990 Internally, the code produces markup texts. You can use any of the
3991 markup text properties to override formatting. For example, the
3992 vertical spacing of the figures may be set with @code{baseline-skip}.
3996 Program reference: @internalsref{BassFigure} object,
3997 @internalsref{FiguredBass} context.
4001 Slash notation for alterations is not supported.
4005 @node Other instrument specific notation
4006 @section Other instrument specific notation
4008 This section includes extra information for writing for instruments.
4011 * Artificial harmonics (strings)::
4014 @node Artificial harmonics (strings)
4015 @subsection Artificial harmonics (strings)
4017 @cindex artificial harmonics
4019 Artificial harmonics are notated with a different notehead style. They
4020 are entered by marking the harmonic pitch with @code{\harmonic}.
4022 @lilypond[raggedright,verbatim,quote,fragment,relative=1]