1 @c -*- coding: utf-8; mode: texinfo; -*-
2 @c This file is part of lilypond.tely
4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. See TRANSLATION for details.
11 @c A menu is needed before every deeper *section nesting of @node's; run
12 @c M-x texinfo-all-menus-update
13 @c to automatically fill in these menus before saving changes
15 @node Instrument-specific notation
16 @chapter Instrument-specific notation
18 This chapter explains how to use notation for specific instruments.
28 * Other instrument specific notation::
36 Piano staves are two normal staves coupled with a brace. The staves
37 are largely independent, but sometimes voices can cross between the
38 two staves. The same notation is also used for harps and other key
39 instruments. The @internalsref{PianoStaff} is especially built to
40 handle this cross-staffing behavior. In this section we discuss the
41 @internalsref{PianoStaff} and some other pianistic peculiarities.
44 * Automatic staff changes::
45 * Manual staff switches::
47 * Staff switch lines::
53 Dynamics are not centered, but workarounds do exist. See the
54 @q{piano centered dynamics} template in @ref{Piano templates}.
56 @cindex cross staff stem
57 @cindex stem, cross staff
58 @cindex distance between staves in piano music
61 @node Automatic staff changes
62 @subsection Automatic staff changes
63 @cindex Automatic staff changes
65 Voices can be made to switch automatically between the top and the bottom
66 staff. The syntax for this is
70 \autochange @dots{}@var{music}@dots{}
75 This will create two staves inside the current PianoStaff, called
76 @code{up} and @code{down}. The lower staff will be in bass clef by
79 A @code{\relative} section that is outside of @code{\autochange} has
80 no effect on the pitches of @var{music}, so, if necessary, put
81 @code{\relative} inside @code{\autochange} like
85 \autochange \relative @dots{} @dots{}
90 The autochanger switches on basis of the pitch (middle C is the turning
91 point), and it looks ahead skipping over rests to switch in
92 advance. Here is a practical example
94 @lilypond[quote,verbatim,ragged-right]
96 \autochange \relative c'
105 In this manual: @ref{Manual staff switches}.
107 Program reference: @internalsref{AutoChangeMusic}.
113 The staff switches may not end up in optimal places. For high
114 quality output, staff switches should be specified manually.
117 @code{\autochange} cannot be inside @code{\times}.
120 @node Manual staff switches
121 @subsection Manual staff switches
123 @cindex manual staff switches
124 @cindex staff switch, manual
126 Voices can be switched between staves manually, using the command
128 \change Staff = @var{staffname} @var{music}
132 The string @var{staffname} is the name of the staff. It switches the
133 current voice from its current staff to the Staff called
134 @var{staffname}. Typically @var{staffname} is @code{"up"} or
135 @code{"down"}. The @context{Staff} referred to must already exist, so
136 usually the setup for a score will start with a setup of the staves,
141 \skip 1 * 10 % @emph{keep staff alive}
143 \new Staff = "down" @{
144 \skip 1 * 10 % @emph{idem}
150 and the @context{Voice} is inserted afterwards
153 \context Staff = down
154 \new Voice @{ @dots{} \change Staff = up @dots{} @}
162 Pianos have pedals that alter the way sound is produced. Generally, a
163 piano has three pedals, sustain, una corda, and sostenuto.
166 Piano pedal instruction can be expressed by attaching
167 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
168 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
171 @lilypond[quote,ragged-right,fragment,verbatim]
172 c'4\sustainDown c'4\sustainUp
175 What is printed can be modified by setting @code{pedal@var{X}Strings},
176 where @var{X} is one of the pedal types: @code{Sustain},
177 @code{Sostenuto} or @code{UnaCorda}. Refer to
178 @internalsref{SustainPedal} in the program reference for more
181 Pedals can also be indicated by a sequence of brackets, by setting the
182 @code{pedalSustainStyle} property to bracket objects
184 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
185 \set Staff.pedalSustainStyle = #'bracket
187 b\sustainUp\sustainDown
188 b g \sustainUp a \sustainDown \bar "|."
191 A third style of pedal notation is a mixture of text and brackets,
192 obtained by setting the @code{pedalSustainStyle} property to
195 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
196 \set Staff.pedalSustainStyle = #'mixed
198 b\sustainUp\sustainDown
199 b g \sustainUp a \sustainDown \bar "|."
202 The default @q{*Ped.} style for sustain and damper pedals corresponds to
203 style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
206 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
207 c\sostenutoDown d e c, f g a\sostenutoUp
210 For fine-tuning the appearance of a pedal bracket, the properties
211 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
212 @code{PianoPedalBracket} objects (see
213 @internalsref{PianoPedalBracket} in the Program reference) can be
214 modified. For example, the bracket may be extended to the right edge
217 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
218 \override Staff.PianoPedalBracket #'shorten-pair = #'(0 . -1.0)
219 c\sostenutoDown d e c, f g a\sostenutoUp
224 In this manual: @ref{Laissez vibrer ties}
226 @node Staff switch lines
227 @subsection Staff switch lines
231 @cindex staff switching
234 @funindex followVoice
236 Whenever a voice switches to another staff, a line connecting the notes
237 can be printed automatically. This is switched on by setting
238 @code{followVoice} to true
240 @lilypond[quote,ragged-right,fragment,relative=1,verbatim]
243 \set followVoice = ##t
248 \new Staff="two" { \clef bass \skip 1*2 }
254 Program reference: @internalsref{VoiceFollower}.
258 @funindex \showStaffSwitch
259 @code{\showStaffSwitch},
260 @funindex \hideStaffSwitch
261 @code{\hideStaffSwitch}.
264 @node Cross staff stems
265 @subsection Cross staff stems
267 Chords that cross staves may be produced by increasing the length
268 of the stem in the lower staff, so it reaches the stem in the upper
269 staff, or vice versa.
271 @lilypond[ragged-right,verbatim,quote]
273 \once \override Stem #'length = #10
274 \once \override Stem #'cross-staff = ##t
276 noFlag = \once \override Stem #'flag-style = #'no-flag
279 \stemDown \stemExtend
297 * Introducing chord names::
299 * Printing chord names::
303 @c awkward name; awkward section name.
304 @c still, the Basic "chords" seems like a good name... :(
305 @node Introducing chord names
306 @subsection Introducing chord names
309 LilyPond has support for printing chord names. Chords may be entered
310 in musical chord notation, i.e., @code{< .. >}, but they can also be
311 entered by name. Internally, the chords are represented as a set of
312 pitches, so they can be transposed
315 @lilypond[quote,ragged-right,verbatim,ragged-right]
316 twoWays = \transpose c c' {
325 << \new ChordNames \twoWays
326 \new Voice \twoWays >>
329 This example also shows that the chord printing routines do not try to
330 be intelligent. The last chord (@code{f bes d}) is not interpreted as
333 Note that the duration of chords must be specified outside the
342 @subsection Chords mode
345 In chord mode sets of pitches (chords) are entered with normal note
346 names. A chord is entered by the root, which is entered like a
349 @lilypond[quote,ragged-right,fragment,verbatim]
350 \chordmode { es4. d8 c2 }
354 The mode is introduced by the keyword @code{\chordmode}.
359 Other chords may be entered by suffixing a colon and introducing a
360 modifier (which may include a number if desired)
361 @lilypond[quote,fragment,verbatim]
362 \chordmode { e1:m e1:7 e1:m7 }
364 The first number following the root is taken to be the @q{type} of the
365 chord, thirds are added to the root until it reaches the specified
367 @lilypond[quote,fragment,verbatim]
368 \chordmode { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 }
371 @cindex root of chord
372 @cindex additions, in chords
373 @cindex removals, in chords
375 More complex chords may also be constructed adding separate steps
376 to a chord. Additions are added after the number following
377 the colon and are separated by dots
378 @lilypond[quote,verbatim,fragment]
379 \chordmode { c:5.6 c:3.7.8 c:3.6.13 }
381 Chord steps can be altered by suffixing a @code{-} or @code{+} sign
383 @lilypond[quote,verbatim,fragment]
384 \chordmode { c:7+ c:5+.3- c:3-.5-.7- }
386 Removals are specified similarly and are introduced by a caret. They
387 must come after the additions
388 @lilypond[quote,verbatim,fragment]
389 \chordmode { c^3 c:7^5 c:9^3.5 }
392 Modifiers can be used to change pitches. The following modifiers are
397 The minor chord. This modifier lowers the 3rd and (if present) the 7th step.
400 The diminished chord. This modifier lowers the 3rd, 5th and (if present)
404 The augmented chord. This modifier raises the 5th step.
407 The major 7th chord. This modifier raises the 7th step if present.
410 The suspended 4th or 2nd. This modifier removes the 3rd
411 step. Append either @code{2} or @code{4} to add the 2nd or 4th step to
415 Modifiers can be mixed with additions
416 @lilypond[quote,verbatim,fragment]
417 \chordmode { c:sus4 c:7sus4 c:dim7 c:m6 }
420 @cindex modifiers, in chords.
427 Since an unaltered 11 does not sound good when combined with an
428 unaltered 13, the 11 is removed in this case (unless it is added
430 @lilypond[quote,ragged-right,fragment,verbatim]
431 \chordmode { c:13 c:13.11 c:m13 }
436 An inversion (putting one pitch of the chord on the bottom), as well
437 as bass notes, can be specified by appending
438 @code{/}@var{pitch} to the chord
439 @lilypond[quote,ragged-right,fragment,verbatim]
440 \chordmode { c1 c/g c/f }
444 A bass note can be added instead of transposed out of the chord,
445 by using @code{/+}@var{pitch}.
447 @lilypond[quote,ragged-right,fragment,verbatim]
448 \chordmode { c1 c/+g c/+f }
451 Chords is a mode similar to @code{\lyricmode}, etc. Most
452 of the commands continue to work, for example, @code{r} and
453 @code{\skip} can be used to insert rests and spaces, and property
454 commands may be used to change various settings.
460 Each step can only be present in a chord once. The following
461 simply produces the augmented chord, since @code{5+} is interpreted
464 @lilypond[quote,ragged-right,verbatim,fragment]
465 \chordmode { c:5.5-.5+ }
469 @node Printing chord names
470 @subsection Printing chord names
472 @cindex printing chord names
476 For displaying printed chord names, use the @internalsref{ChordNames} context.
477 The chords may be entered either using the notation
478 described above, or directly using @code{<} and @code{>}
480 @lilypond[quote,verbatim,ragged-right]
482 \chordmode {a1 b c} <d' f' a'> <e' g' b'>
485 \new ChordNames \harmonies
486 \new Staff \harmonies
490 You can make the chord changes stand out by setting
491 @internalsref{ChordNames}.@code{chordChanges} to true. This will only
492 display chord names when there is a change in the chords scheme and at
493 the start of a new line
495 @lilypond[quote,verbatim,ragged-right]
496 harmonies = \chordmode {
497 c1:m c:m \break c:m c:m d
501 \set chordChanges = ##t
503 \new Staff \transpose c c' \harmonies
507 The previous examples all show chords over a staff. This is not
508 necessary. Chords may also be printed separately. It may be necessary
509 to add @internalsref{Volta_engraver} and @internalsref{Bar_engraver}
512 @lilypond[ragged-right,verbatim]
513 \new ChordNames \with {
514 \override BarLine #'bar-size = #4
515 voltaOnThisStaff = ##t
516 \consists Bar_engraver
517 \consists "Volta_engraver"
519 \chordmode { \repeat volta 2 {
529 The default chord name layout is a system for Jazz music, proposed by
530 Klaus Ignatzek (see @ref{Literature list}). It can be tuned through the
534 @funindex chordNameExceptions
535 @item chordNameExceptions
536 This is a list that contains the chords that have special formatting.
538 The exceptions list should be encoded as
540 @{ <c f g bes>1 \markup @{ \super "7" "wahh" @} @}
543 To get this information into @code{chordNameExceptions} takes a little
544 manoeuvring. The following code transforms @code{chExceptionMusic}
545 (which is a sequential music) into a list of exceptions.
547 (sequential-music-to-chord-exceptions chExceptionMusic #t)
552 (sequential-music-to-chord-exceptions chExceptionMusic #t)
555 adds the new exceptions to the default ones, which are defined in
556 @file{ly/@/chord@/-modifier@/-init@/.ly}.
558 For an example of tuning this property, see also
559 @lsr{chords/,chord@/-name@/-exceptions@/.ly}
560 @cindex exceptions, chord names.
563 @funindex majorSevenSymbol
564 @item majorSevenSymbol
565 This property contains the markup object used for the 7th step, when
566 it is major. Predefined options are @code{whiteTriangleMarkup} and
567 @code{blackTriangleMarkup}. See
568 @lsr{chords,chord@/-name@/-major7@/.ly} for an example.
570 @funindex chordNameSeparator
571 @item chordNameSeparator
572 Different parts of a chord name are normally separated by a
573 slash. By setting @code{chordNameSeparator}, you can specify other
575 @lilypond[quote,ragged-right,fragment,verbatim]
576 \new ChordNames \chordmode {
578 \set chordNameSeparator
579 = \markup { \typewriter "|" }
584 @funindex chordRootNamer
586 The root of a chord is usually printed as a letter with an optional
587 alteration. The transformation from pitch to letter is done by this
588 function. Special note names (for example, the German @q{H} for a
589 B-chord) can be produced by storing a new function in this property.
591 @funindex chordNoteNamer
593 The default is to print single pitch, e.g., the bass note, using the
594 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
595 to a specialized function to change this behavior. For example, the
596 base can be printed in lower case.
598 @funindex chordPrefixSpacer
599 @item chordPrefixSpacer
600 The @q{m} for minor chords is usually printed right after the root of
601 the chord. By setting @code{chordPrefixSpacer}, you can fix a spacer
602 between the root and @q{m}. The spacer is not used when the root
607 The predefined variables @code{\germanChords},
608 @code{\semiGermanChords}, @code{\italianChords} and @code{\frenchChords}
609 set these variables. The effect is
612 @lilypondfile[ragged-right]{chord-names-languages.ly}
614 There are also two other chord name schemes implemented: an alternate
615 Jazz chord notation, and a systematic scheme called Banter chords. The
616 alternate Jazz notation is also shown on the chart in @ref{Chord name
617 chart}. Turning on these styles is described in the input file
618 @inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
627 @funindex \germanChords
628 @code{\germanChords},
629 @funindex \semiGermanChords
630 @code{\semiGermanChords}.
631 @funindex \italianChords
632 @code{\italianChords}.
633 @funindex \frenchChords
634 @code{\frenchChords}.
642 @lsr{chords/,chord@/-name@/-exceptions@/.ly},
643 @lsr{chords,chord@/-name@/-major7@/.ly}, and
644 @inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
647 Init files: @file{scm/@/chords@/-ignatzek@/.scm}, and
648 @file{scm/@/chord@/-entry@/.scm}.
653 Chord names are determined solely from the list of pitches. Chord
654 inversions are not identified, and neither are added bass notes. This
655 may result in strange chord names when chords are entered with the
656 @code{< .. >} syntax.
663 Since LilyPond input files are text, there are two issues to
664 consider when working with vocal music:
668 Song texts must be entered as text, not notes. For example, the
669 input@tie{}@code{d} should be interpreted as a one letter syllable, not the
673 Song texts must be aligned with the notes of their melody.
676 There are a few different ways to define lyrics; the simplest
677 way is to use the @code{\addlyrics} function.
680 * Setting simple songs::
682 * Hyphens and extenders::
683 * The Lyrics context::
685 * Another way of entering lyrics::
686 * Flexibility in placement::
688 * More about stanzas::
690 * Other vocal issues::
696 Checking to make sure that text scripts and lyrics are within the margins is
697 a relatively large computational task. To speed up processing, lilypond does
698 not perform such calculations by default; to enable it, use
701 \override Score.PaperColumn #'keep-inside-line = ##t
704 To make lyrics avoid barlines as well, use
709 \consists "Bar_engraver"
710 \consists "Separating_line_group_engraver"
711 \override BarLine #'transparent = ##t
717 @node Setting simple songs
718 @subsection Setting simple songs
720 The easiest way to add lyrics to a melody is to append
723 \addlyrics @{ @var{the lyrics} @}
727 to a melody. Here is an example,
729 @lilypond[ragged-right,verbatim,fragment,quote]
731 \relative { c2 e4 g2. }
732 \addlyrics { play the game }
735 More stanzas can be added by adding more
736 @code{\addlyrics} sections
738 @lilypond[ragged-right,verbatim,fragment,quote]
740 \relative { c2 e4 g2. }
741 \addlyrics { play the game }
742 \addlyrics { speel het spel }
743 \addlyrics { joue le jeu }
746 The command @code{\addlyrics} cannot handle polyphony settings. For these
747 cases you should use @code{\lyricsto} and @code{\lyricmode}.
751 @node Entering lyrics
752 @subsection Entering lyrics
758 Lyrics are entered in a special input mode. This mode is introduced
759 by the keyword @code{\lyricmode}, or by using @code{\addlyrics} or
760 @code{\lyricsto}. In this mode you can enter lyrics,
761 with punctuation and accents, and the input @code{d} is not parsed as
762 a pitch, but rather as a one letter syllable. Syllables are entered
763 like notes, but with pitches replaced by text. For example,
765 \lyricmode @{ Twin-4 kle4 twin- kle litt- le star2 @}
768 There are two main methods to specify the horizontal placement
769 of the syllables, either by specifying the duration of each syllable
770 explicitly, like in the example above, or by automatically aligning
771 the lyrics to a melody or other voice of music, using @code{\addlyrics}
772 or @code{\lyricsto}. For more details see @ref{The Lyrics context}.
774 A word or syllable of lyrics begins with an alphabetic character, and ends
776 any space or digit. The following characters can be any character
777 that is not a digit or white space. One important consequence of this
778 is that a word can end with @code{@}}. The following example is
779 usually a mistake in the input file. The syllable includes a @code{@}}, so
781 opening brace is not balanced
783 \lyricmode @{ twinkle@}
786 @funindex \property in \lyricmode
789 Similarly, a period which follows an alphabetic sequence is included in
790 the resulting string. As a consequence, spaces must be inserted around
793 \override Score . LyricText #'font-shape = #'italic
797 @cindex spaces, in lyrics
798 @cindex quotes, in lyrics
799 @cindex ties, in lyrics
801 In order to assign more than one syllable to a single note, you can
802 surround them with quotes or use a @code{_} character, to get spaces
803 between syllables, or use tilde symbol (@code{~}) to get a lyric tie.
805 @lilypond[quote,relative=2,ragged-right,fragment,verbatim]
807 \relative { c2 e4 g2 e4 }
808 \addlyrics { gran- de_a- mi- go }
809 \addlyrics { pu- "ro y ho-" nes- to }
810 \addlyrics { pu- ro~y~ho- nes- to }
813 The lyric ties is implemented with the Unicode character U+203F, so be
814 sure to have a font (Like DejaVuLGC) installed that includes this
818 To enter lyrics with characters from non-English languages, or with
819 accented and special characters (such as the heart symbol or slanted quotes),
820 simply insert the characters directly into the input file and save
821 it with utf-8 encoding. See @ref{Text encoding} for more info.
823 @lilypond[quote,ragged-right,fragment,verbatim]
824 \relative { e4 f e d e f e2 }
825 \addlyrics { He said: “Let my peo ple go”. }
828 To use normal quotes in lyrics, add a backslash before the
831 @lilypond[quote,ragged-right,fragment,verbatim]
832 \relative c' { \time 3/4 e4 e4. e8 d4 e d c2. }
833 \addlyrics { "\"I" am so lone- "ly\"" said she }
836 The full definition of a word start in Lyrics mode is somewhat more
839 A word in Lyrics mode begins with: an alphabetic character, @code{_},
840 @code{?}, @code{!}, @code{:}, @code{'}, the control characters @code{^A}
841 through @code{^F}, @code{^Q} through @code{^W}, @code{^Y}, @code{^^},
842 any 8-bit character with ASCII code over 127, or a two-character
843 combination of a backslash followed by one of @code{`}, @code{'},
844 @code{"}, or @code{^}.
846 To define indentifiers containing lyrics, the function @code{lyricmode}
850 verseOne = \lyricmode @{ Joy to the world the Lord is come @}
853 \new Voice = "one" \relative c'' @{
856 c4 b8. a16 g4. f8 e4 d c2
858 \addlyrics @{ \verseOne @}
866 Program reference: @internalsref{LyricText}, @internalsref{LyricSpace}.
870 @node Hyphens and extenders
871 @subsection Hyphens and extenders
875 Centered hyphens are entered as @samp{--} between syllables.
876 The hyphen will have variable length depending on the space between
877 the syllables and it will be centered between the syllables.
882 When a lyric is sung over many notes (this is called a melisma), this is
883 indicated with a horizontal line centered between a syllable and the
884 next one. Such a line is called an extender line, and it is entered as
887 In tighly engraved music, hyphens can be removed. Whether this
888 happens can be controlled with the @code{minimum-distance} (minimum
889 distance between two syllables) and the @code{minimum-length}
890 (threshold below which hyphens are removed).
894 Program reference: @internalsref{LyricHyphen}, @internalsref{LyricExtender}.
898 @node The Lyrics context
899 @subsection The Lyrics context
901 Lyrics are printed by interpreting them in the context called
902 @internalsref{Lyrics}.
905 \new Lyrics \lyricmode @dots{}
908 @cindex automatic syllable durations
910 @cindex lyrics and melodies
912 This will place the lyrics according to the durations that were
913 entered. The lyrics can also be aligned under a given melody
914 automatically. In this case, it is no longer necessary to enter the
915 correct duration for each syllable. This is achieved by combining the
916 melody and the lyrics with the @code{\lyricsto} expression
919 \new Lyrics \lyricsto @var{name} @dots{}
922 This aligns the lyrics to the
923 notes of the @internalsref{Voice} context called @var{name}, which must
924 already exist. Therefore normally the @code{Voice} is specified first, and
925 then the lyrics are specified with @code{\lyricsto}. The command
926 @code{\lyricsto} switches to @code{\lyricmode} mode automatically, so the
927 @code{\lyricmode} keyword may be omitted.
929 The following example uses different commands for entering lyrics.
931 @lilypond[quote,fragment,ragged-right,verbatim]
933 \new Voice = "one" \relative c'' {
936 c4 b8. a16 g4. f8 e4 d c2
938 \new Lyrics \lyricmode { Joy4 to8. the16 world!4. the8 Lord4 is come.2 }
939 \new Lyrics \lyricmode { Joy to the earth! the Sa -- viour reigns. }
940 \new Lyrics \lyricsto "one" { No more let sins and sor -- rows grow. }
944 The second stanza is not properly aligned because the durations
945 were not specified. A solution for that would be to use @code{\lyricsto}.
947 The @code{\addlyrics} command is actually just a convenient way
948 to write a more complicated LilyPond structure that sets up the
953 \addlyrics @{ LYRICS @}
960 \new Voice = "blah" @{ music @}
961 \new Lyrics \lyricsto "blah" @{ LYRICS @}
964 For different or more complex orderings, the best way is to setup the
965 hierarchy of staves and lyrics first, e.g.,
968 \new Voice = "soprano" @{ @emph{music} @}
969 \new Lyrics = "sopranoLyrics" @{ s1 @}
970 \new Lyrics = "tenorLyrics" @{ s1 @}
971 \new Voice = "tenor" @{ @emph{music} @}
975 and then combine the appropriate melodies and lyric lines
978 \context Lyrics = sopranoLyrics \lyricsto "soprano"
983 The final input would resemble
986 <<\new ChoirStaff << @emph{setup the music} >>
987 \lyricsto "soprano" @emph{etc}
988 \lyricsto "alto" @emph{etc}
995 Program reference: @internalsref{LyricCombineMusic},
996 @internalsref{Lyrics}.
1000 @subsection Melismata
1002 The @code{\lyricsto} command detects melismata: it only puts one
1003 syllable under a tied or slurred group of notes. If you want to force
1004 an unslurred group of notes to be a melisma, insert @code{\melisma}
1005 after the first note of the group, and @code{\melismaEnd} after the
1008 @lilypond[quote,relative=2,ragged-right,fragment,verbatim]
1010 \new Voice = "lala" {
1018 \new Lyrics \lyricsto "lala" {
1024 In addition, notes are considered a melisma if they are manually
1025 beamed, and automatic beaming (see @ref{Setting automatic beam
1026 behavior}) is switched off.
1029 @cindex choral score
1031 A complete example of a SATB score setup is in section
1032 @ref{Vocal ensembles}.
1037 @code{\melisma}, @code{\melismaEnd}
1038 @funindex \melismaEnd
1043 Program reference: @internalsref{Melisma_translator}.
1045 @lsr{vocal,lyric@/-combine.ly}.
1049 Melismata are not detected automatically, and extender lines must be
1053 @node Another way of entering lyrics
1054 @subsection Another way of entering lyrics
1056 Lyrics can also be entered without @code{\lyricsto}. In this case the
1057 duration of each syllable must be entered explicitly, for example,
1064 The alignment to a melody can be specified with the
1065 @code{associatedVoice} property,
1068 \set associatedVoice = #"lala"
1072 The value of the property (here: @code{"lala"}) should be the name of
1073 a @internalsref{Voice} context. Without this setting, extender lines
1074 will not be formatted properly.
1076 Here is an example demonstrating manual lyric durations,
1078 @lilypond[relative=1,ragged-right,verbatim,fragment,quote]
1079 << \new Voice = "melody" {
1083 \new Lyrics \lyricmode {
1084 \set associatedVoice = #"melody"
1090 @c TODO: document \new Staff << Voice \lyricsto >> bug
1092 @node Flexibility in placement
1093 @subsection Flexibility in placement
1095 Often, different stanzas of one song are put to one melody in slightly
1096 differing ways. Such variations can still be captured with
1100 * Lyrics to multiple notes of a melisma::
1102 * Switching the melody associated with a lyrics line::
1103 * Specifying melismata within the lyrics::
1104 * Lyrics independent of notes::
1107 @node Lyrics to multiple notes of a melisma
1108 @subsubsection Lyrics to multiple notes of a melisma
1111 One possibility is that the text has a melisma in one stanza, but
1112 multiple syllables in another one. One solution is to make the faster
1113 voice ignore the melisma. This is done by setting
1114 @code{ignoreMelismata} in the Lyrics context.
1116 There is one tricky aspect: the setting for @code{ignoreMelismata}
1117 must be set one syllable @emph{before} the non-melismatic syllable
1118 in the text, as shown here,
1120 @c FIXME: breaks compile
1121 @lilypond[verbatim,ragged-right,quote]
1124 \relative \new Voice = "lahlah" {
1125 \set Staff.autoBeaming = ##f
1131 \new Lyrics \lyricsto "lahlah" {
1134 \new Lyrics \lyricsto "lahlah" {
1135 \set ignoreMelismata = ##t % applies to "fas"
1137 \unset ignoreMelismata
1145 The @code{ignoreMelismata} applies to the syllable @q{fas}, so it
1146 should be entered before @q{go}.
1148 The reverse is also possible: making a lyric line slower than the
1149 standard. This can be achieved by insert @code{\skip}s into the
1150 lyrics. For every @code{\skip}, the text will be delayed another note.
1153 @lilypond[verbatim,ragged-right,quote]
1154 \relative { c c g' }
1163 @subsubsection Divisi lyrics
1165 You can display alternate (or divisi) lyrics by naming voice
1166 contexts and attaching lyrics to those specific contexts.
1168 @lilypond[verbatim,ragged-right,quote]
1170 \new Voice = "melody" {
1175 \new Voice = "splitpart" { \voiceTwo c4 }
1180 \new Lyrics \lyricsto "melody" { we shall not o- ver- come }
1181 \new Lyrics \lyricsto "splitpart" { will }
1186 You can use this trick to display different lyrics for a repeated
1189 @lilypond[verbatim,ragged-right,quote]
1191 \new Voice = "melody" \relative c' {
1193 \new Voice = "verse" \repeat volta 2 {c4 d e f | g1 | }
1195 \new Lyrics = "mainlyrics" \lyricsto melody \lyricmode {
1198 \context Lyrics = "mainlyrics" \lyricsto verse \lyricmode {
1200 \new Lyrics = "repeatlyrics" \lyricsto verse \lyricmode {
1201 dodo rere mimi fafa solsol }
1208 @node Switching the melody associated with a lyrics line
1209 @subsubsection Switching the melody associated with a lyrics line
1211 More complex variations in text underlay are possible. It is possible
1212 to switch the melody for a line of lyrics during the text. This is
1213 done by setting the @code{associatedVoice} property. In the example
1215 @lilypond[ragged-right,quote]
1217 \relative \new Voice = "lahlah" {
1218 \set Staff.autoBeaming = ##f
1221 \new Voice = "alternative" {
1224 % show associations clearly.
1225 \override NoteColumn #'force-hshift = #-3
1236 \new Lyrics \lyricsto "lahlah" {
1237 Ju -- ras -- sic Park
1239 \new Lyrics \lyricsto "lahlah" {
1240 % Tricky: need to set associatedVoice
1241 % one syllable too soon!
1242 \set associatedVoice = alternative % applies to "ran"
1246 \set associatedVoice = lahlah % applies to "rus"
1252 the text for the first stanza is set to a melody called @q{lahlah},
1255 \new Lyrics \lyricsto "lahlah" @{
1256 Ju -- ras -- sic Park
1261 The second stanza initially is set to the @code{lahlah} context, but
1262 for the syllable @q{ran}, it switches to a different melody.
1263 This is achieved with
1265 \set associatedVoice = alternative
1269 Here, @code{alternative} is the name of the @code{Voice} context
1270 containing the triplet.
1272 Again, the command must be one syllable too early, before @q{Ty} in
1276 \new Lyrics \lyricsto "lahlah" @{
1277 \set associatedVoice = alternative % applies to "ran"
1281 \set associatedVoice = lahlah % applies to "rus"
1287 The underlay is switched back to the starting situation by assigning
1288 @code{lahlah} to @code{associatedVoice}.
1291 @node Specifying melismata within the lyrics
1292 @subsubsection Specifying melismata within the lyrics
1294 It is also possible to define melismata entirely in the lyrics. This
1295 can be done by entering @code{_} for every note that is part of the
1298 @lilypond[relative=1,verbatim,fragment,quote]
1299 { \set melismaBusyProperties = #'()
1300 c d( e) f f( e) e e }
1302 { Ky -- _ _ ri __ _ _ _ e }
1305 In this case, you can also have ties and slurs in the melody if you
1306 set @code{melismaBusyProperties}, as is done in the example above.
1309 @node Lyrics independent of notes
1310 @subsubsection Lyrics independent of notes
1312 In some complex vocal music, it may be desirable to place
1313 lyrics completely independently of notes. Music defined
1314 inside @code{lyricrhythm} disappears into the
1315 @code{Devnull} context, but the rhythms can still be used
1316 to place the lyrics.
1318 @lilypond[quote,verbatim,ragged-right]
1321 \tag #'music { c''2 }
1322 \tag #'lyricrhythm { c''4. c''8 }
1326 lyr = \lyricmode { I like my cat! }
1329 \new Staff \keepWithTag #'music \voice
1330 \new Devnull="nowhere" \keepWithTag #'lyricrhythm \voice
1331 \new Lyrics \lyricsto "nowhere" \lyr
1332 \new Staff { c'8 c' c' c' c' c' c' c'
1333 c' c' c' c' c' c' c' c' }
1338 @node Spacing lyrics
1339 @subsection Spacing lyrics
1341 @cindex Spacing lyrics
1342 @cindex Lyrics, increasing space between
1344 To increase the spacing between lyrics, set the minimum-distance property of
1347 @lilypond[relative,verbatim,fragment,quote,ragged-right]
1350 \override Lyrics.LyricSpace #'minimum-distance = #1.0
1354 longtext longtext longtext longtext
1355 longtext longtext longtext longtext
1359 To make this change for all lyrics in the score, set the property in the
1362 @lilypond[relative,verbatim,quote,ragged-right]
1369 longtext longtext longtext longtext
1370 longtext longtext longtext longtext
1375 \override LyricSpace #'minimum-distance = #1.0
1382 @node More about stanzas
1383 @subsection More about stanzas
1385 @c what's this doing here?
1386 @cindex phrasing, in lyrics
1388 @cindex stanza number
1389 @subsubsection Adding stanza numbers
1391 Stanza numbers can be added by setting @code{stanza}, e.g.,
1393 @lilypond[quote,ragged-right,verbatim,relative=2,fragment]
1395 \time 3/4 g2 e4 a2 f4 g2.
1398 Hi, my name is Bert.
1401 Oh, che -- ri, je t'aime
1406 These numbers are put just before the start of the first syllable.
1409 @subsubsection Adding dynamics marks
1411 Stanzas differing in loudness may be indicated by putting a
1412 dynamics mark before each stanza. In Lilypond, everthing coming in
1413 front of a stanza goes into the @code{StanzaNumber} object; dynamics marks
1414 are no different. For technical reasons, you have to set the stanza
1415 outside @code{\lyricmode}:
1417 @lilypond[quote,ragged-right,verbatim]
1419 \set stanza = \markup { \dynamic "ff" "1. " }
1426 \new Voice = "tune" {
1430 \new Lyrics \lyricsto "tune" \text
1435 @cindex name of singer
1436 @subsubsection Adding singer names
1438 Names of singers can also be added. They are printed at the start of
1439 the line, just like instrument names. They are created by setting
1440 @code{vocalName}. A short version may be entered as @code{shortVocalName}.
1442 @lilypond[fragment,ragged-right,quote,verbatim,relative=2]
1444 \time 3/4 g2 e4 a2 f4 g2.
1446 \set vocalName = "Bert "
1447 Hi, my name is Bert.
1449 \set vocalName = "Ernie "
1450 Oh, che -- ri, je t'aime
1455 @subsubsection Printing stanzas at the end
1457 Sometimes it is appropriate to have one stanza set
1458 to the music, and the rest added in verse form at
1459 the end of the piece. This can be accomplished by adding
1460 the extra verses into a @code{\markup} section outside
1461 of the main score block. Notice that there are two
1462 different ways to force linebreaks when using
1465 @lilypond[ragged-right,verbatim,quote]
1466 melody = \relative c' {
1472 \set stanza = "1." Ma- ry had a lit- tle lamb,
1473 its fleece was white as snow.
1478 \new Voice = "one" { \melody }
1479 \new Lyrics \lyricsto "one" \text
1485 \line{ All the children laughed and played }
1486 \line{ To see a lamb at school. }
1493 Mary took it home again,
1495 It was against the rule."
1501 @subsubsection Printing stanzas at the end in multiple columns
1503 When a piece of music has many verses, they are often printed in
1504 multiple columns across the page. An outdented verse number often
1505 introduces each verse. The following example shows how to produce such
1508 @lilypond[ragged-right,quote,verbatim]
1509 melody = \relative c' {
1514 \set stanza = "1." This is verse one.
1519 \new Voice = "one" { \melody }
1520 \new Lyrics \lyricsto "one" \text
1527 \hspace #0.1 % moves the column off the left margin; can be removed if
1528 % space on the page is tight
1532 "This is verse two."
1536 \hspace #0.1 % adds vertical spacing between verses
1539 "This is verse three."
1544 \hspace #0.1 % adds horizontal spacing between columns; if they are
1545 % still too close, add more " " pairs until the result
1550 "This is verse four."
1554 \hspace #0.1 % adds vertical spacing between verses
1557 "This is verse five."
1562 \hspace #0.1 % gives some extra space on the right margin; can
1563 % be removed if page space is tight
1571 Program reference: @internalsref{LyricText}, @internalsref{StanzaNumber},
1572 @internalsref{VocalName}.
1580 The term @emph{ambitus} denotes a range of pitches for a given voice
1581 in a part of music. It may also denote the pitch range that a musical
1582 instrument is capable of playing. Ambits are printed on vocal parts,
1583 so performers can easily determine it meets their capabilities.
1585 Ambits are denoted at the beginning of a piece near the initial clef.
1586 The range is graphically specified by two note heads that represent the
1587 minimum and maximum pitch. To print such ambits, add the
1588 @internalsref{Ambitus_engraver} to the @internalsref{Voice} context,
1595 \consists Ambitus_engraver
1600 This results in the following output
1602 @lilypond[quote,ragged-right]
1606 \consists Ambitus_engraver
1610 \relative \new Staff {
1615 If you have multiple voices in a single staff and you want a single
1616 ambitus per staff rather than per each voice, add the
1617 @internalsref{Ambitus_engraver} to the @internalsref{Staff} context
1618 rather than to the @internalsref{Voice} context. Here is an example,
1620 @lilypond[verbatim,ragged-right,quote]
1622 \consists "Ambitus_engraver"
1626 \remove "Ambitus_engraver"
1628 \override Ambitus #'X-offset = #-1.0
1633 \remove "Ambitus_engraver"
1642 This example uses one advanced feature,
1645 \override Ambitus #'X-offset = #-1.0
1649 This code moves the ambitus to the left. The same effect could have
1650 been achieved with @code{extra-offset}, but then the formatting system
1651 would not reserve space for the moved object.
1655 Program reference: @internalsref{Ambitus},
1656 @internalsref{AmbitusLine}, @internalsref{AmbitusNoteHead},
1657 @internalsref{AmbitusAccidental}.
1660 @lsr{vocal,ambitus@/.ly}.
1664 There is no collision handling in the case of multiple per-voice
1668 @node Other vocal issues
1669 @subsection Other vocal issues
1672 yeah, I'm giving up somewhat by stuffing a bunch of things in
1673 here. But at least they're in the manual now; it's easier to
1674 move them around in the manual once they're already here.
1676 Besides, if users complain about everything stuffed in here, I
1677 can ask them for specific instructions about where to move these
1678 examples, and that might get them more involved in the docs. -gp
1681 @q{Parlato} is spoken without pitch but still with rhythm; it is
1682 notated by cross noteheads. This is demonstrated in
1683 @ref{Special noteheads}.
1689 @node Rhythmic music
1690 @section Rhythmic music
1692 Rhythmic music is primarily used for percussion and drum notation, but it can
1693 also be used to show the rhythms of melodies.
1696 * Showing melody rhythms::
1697 * Entering percussion::
1698 * Percussion staves::
1703 @node Showing melody rhythms
1704 @subsection Showing melody rhythms
1706 Sometimes you might want to show only the rhythm of a melody. This
1707 can be done with the rhythmic staff. All pitches of notes on such a
1708 staff are squashed, and the staff itself has a single line
1710 @lilypond[quote,ragged-right,fragment,relative=1,verbatim]
1711 \new RhythmicStaff {
1713 c4 e8 f g2 | r4 g r2 | g1:32 | r1 |
1719 Program reference: @internalsref{RhythmicStaff}.
1722 @node Entering percussion
1723 @subsection Entering percussion
1729 Percussion notes may be entered in @code{\drummode} mode, which is
1730 similar to the standard mode for entering notes. Each piece of
1731 percussion has a full name and an abbreviated name, and both can be used
1734 @lilypond[quote,ragged-right,verbatim]
1736 hihat hh bassdrum bd
1740 The complete list of drum names is in the init file
1741 @file{ly/@/drumpitch@/-init@/.ly}.
1742 @c TODO: properly document this.
1746 Program reference: @internalsref{note-event}.
1748 @node Percussion staves
1749 @subsection Percussion staves
1753 A percussion part for more than one instrument typically uses a
1754 multiline staff where each position in the staff refers to one piece
1758 To typeset the music, the notes must be interpreted in a
1759 @internalsref{DrumStaff} and @internalsref{DrumVoice} contexts
1761 @lilypond[quote,ragged-right,verbatim]
1762 up = \drummode { crashcymbal4 hihat8 halfopenhihat hh hh hh openhihat }
1763 down = \drummode { bassdrum4 snare8 bd r bd sn4 }
1765 \new DrumVoice { \voiceOne \up }
1766 \new DrumVoice { \voiceTwo \down }
1770 The above example shows verbose polyphonic notation. The short
1771 polyphonic notation, described in @ref{Basic polyphony}, can also be used if
1772 the @internalsref{DrumVoice}s are instantiated by hand first. For example,
1774 @lilypond[quote,ragged-right,fragment,verbatim]
1776 \new DrumVoice = "1" { s1 *2 }
1777 \new DrumVoice = "2" { s1 *2 }
1781 { \repeat unfold 16 hh16 }
1790 There are also other layout possibilities. To use these, set the
1791 property @code{drumStyleTable} in context @internalsref{DrumVoice}.
1792 The following variables have been predefined
1796 This is the default. It typesets a typical drum kit on a five-line staff
1798 @lilypond[quote,line-width=10.0\cm]
1800 cymc cyms cymr hh hhc hho hhho hhp
1801 cb hc bd sn ss tomh tommh tomml toml tomfh tomfl }
1803 cymc cyms cymr hh hhc hho hhho hhp \break
1804 cb hc bd sn ss tomh tommh tomml toml tomfh tomfl s16 }
1806 << \new DrumStaff \with {
1807 \remove Bar_engraver
1808 \remove Time_signature_engraver
1809 \override Stem #'transparent = ##t
1810 \override Stem #'Y-extent-callback = ##f
1811 \override VerticalAxisGroup #'minimum-Y-extent = #'(-4.0 . 5.0)
1818 \override LyricText #'font-family = #'typewriter
1819 \override BarNumber #'transparent =##T
1825 The drum scheme supports six different toms. When there are fewer toms,
1826 simply select the toms that produce the desired result, i.e., to get toms
1827 on the three middle lines you use @code{tommh}, @code{tomml}, and
1830 @item timbales-style
1831 This typesets timbales on a two line staff
1833 @lilypond[quote,ragged-right]
1834 nam = \lyricmode { timh ssh timl ssl cb }
1835 mus = \drummode { timh ssh timl ssl cb s16 }
1838 \new DrumStaff \with {
1839 \remove Bar_engraver
1840 \remove Time_signature_engraver
1841 \override Stem #'transparent = ##t
1842 \override Stem #'Y-extent-callback = ##f
1843 \override StaffSymbol #'line-count = #2
1844 \override StaffSymbol #'staff-space = #2
1845 \override VerticalAxisGroup #'minimum-Y-extent = #'(-3.0 . 4.0)
1846 drumStyleTable = #timbales-style
1849 \override LyricText #'font-family = #'typewriter
1856 This typesets congas on a two line staff
1858 @lilypond[quote,ragged-right]
1859 nam = \lyricmode { cgh cgho cghm ssh cgl cglo cglm ssl }
1860 mus = \drummode { cgh cgho cghm ssh cgl cglo cglm ssl s16 }
1863 \new DrumStaff \with {
1864 \remove Bar_engraver
1865 \remove Time_signature_engraver
1866 drumStyleTable = #congas-style
1867 \override StaffSymbol #'line-count = #2
1869 %% this sucks; it will lengthen stems.
1870 \override StaffSymbol #'staff-space = #2
1871 \override Stem #'transparent = ##t
1872 \override Stem #'Y-extent-callback = ##f
1875 \override LyricText #'font-family = #'typewriter
1882 This typesets bongos on a two line staff
1884 @lilypond[quote,ragged-right]
1885 nam = \lyricmode { boh boho bohm ssh bol bolo bolm ssl }
1886 mus = \drummode { boh boho bohm ssh bol bolo bolm ssl s16 }
1889 \new DrumStaff \with {
1890 \remove Bar_engraver
1891 \remove Time_signature_engraver
1892 \override StaffSymbol #'line-count = #2
1893 drumStyleTable = #bongos-style
1895 %% this sucks; it will lengthen stems.
1896 \override StaffSymbol #'staff-space = #2
1897 \override Stem #'transparent = ##t
1898 \override Stem #'Y-extent-callback = ##f
1901 \override LyricText #'font-family = #'typewriter
1907 @item percussion-style
1908 To typeset all kinds of simple percussion on one line staves.
1910 @lilypond[quote,ragged-right]
1911 nam = \lyricmode { tri trio trim gui guis guil cb cl tamb cab mar hc }
1912 mus = \drummode { tri trio trim gui guis guil cb cl tamb cab mar hc s16 }
1915 \new DrumStaff \with{
1916 \remove Bar_engraver
1917 drumStyleTable = #percussion-style
1918 \override StaffSymbol #'line-count = #1
1919 \remove Time_signature_engraver
1920 \override Stem #'transparent = ##t
1921 \override Stem #'Y-extent-callback = ##f
1924 \override LyricText #'font-family = #'typewriter
1931 If you do not like any of the predefined lists you can define your own
1932 list at the top of your file
1934 @lilypond[quote,ragged-right,verbatim]
1936 (bassdrum default #f -1)
1937 (snare default #f 0)
1939 (pedalhihat xcircle "stopped" 2)
1940 (lowtom diamond #f 3)))
1941 up = \drummode { hh8 hh hh hh hhp4 hhp }
1942 down = \drummode { bd4 sn bd toml8 toml }
1945 \set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)
1946 \new DrumVoice { \voiceOne \up }
1947 \new DrumVoice { \voiceTwo \down }
1954 Init files: @file{ly/@/drumpitch@/-init@/.ly}.
1956 Program reference: @internalsref{DrumStaff}, @internalsref{DrumVoice}.
1960 Because general MIDI does not contain rim shots, the sidestick is used
1961 for this purpose instead.
1964 @c FIXME: check name -gp
1966 @subsection Ghost notes
1968 Ghost notes for drums and percussion may be created using the
1969 @code{\parenthesize} command detailed in @ref{Parentheses}. However,
1970 the default @code{\drummode} does
1971 not include the @code{Parenthesis_engraver} plugin which allows
1973 must add the plugin explicitly in the context definition as
1974 detailed in @ref{Changing context properties on the fly}.
1976 @lilypond[quote,ragged-right,verbatim,fragment]
1977 \new DrumStaff \with {
1978 \consists "Parenthesis_engraver"
1980 \context DrumVoice = "1" { s1 *2 }
1981 \context DrumVoice = "2" { s1 *2 }
1985 hh8[ hh] <hh sn> hh16
1986 < \parenthesize sn > hh < \parenthesize
1997 Also note that you must add chords (@code{< >} brackets)
1998 around each @code{\parenthesize} statement.
2005 @cindex guitar tablature
2008 * String number indications::
2009 * Tablatures basic::
2010 * Non-guitar tablatures::
2011 * Banjo tablatures::
2013 * Right hand fingerings::
2014 * Other guitar issues::
2017 @node String number indications
2018 @subsection String number indications
2020 @cindex String numbers
2022 String numbers can be added to chords, by indicating the string number
2023 with @code{\}@var{number},
2025 @lilypond[relative,relative=1,ragged-right,fragment]
2032 Program reference: @internalsref{StringNumber},
2033 @lsr{guitar/,string-number.ly}.
2036 @node Tablatures basic
2037 @subsection Tablatures basic
2038 @cindex Tablatures basic
2040 Tablature notation is used for notating music for plucked string
2041 instruments. Pitches are not denoted with note heads, but by
2042 numbers indicating on which string and fret a note must be played. LilyPond
2043 offers limited support for tablature.
2045 The string number associated to a note is given as a backslash
2046 followed by a number, e.g., @code{c4\3} for a C quarter on the third
2047 string. By default, string 1 is the highest one, and the tuning
2048 defaults to the standard guitar tuning (with 6 strings). The notes
2049 are printed as tablature, by using @internalsref{TabStaff} and
2050 @internalsref{TabVoice} contexts
2052 @lilypond[quote,ragged-right,fragment,verbatim]
2059 @funindex minimumFret
2062 When no string is specified, the first string that does not give a
2063 fret number less than @code{minimumFret} is selected. The default
2064 value for @code{minimumFret} is 0
2069 \set TabStaff.minimumFret = #8
2072 @lilypond[quote,ragged-right]
2076 \set TabStaff.minimumFret = #8
2080 \new Staff { \clef "G_8" \frag }
2081 \new TabStaff { \frag }
2088 To print tablatures with stems down and horizontal beams,
2089 initialize the @code{TabStaff} with this code:
2093 \override Beam #'damping = #100000
2098 Program reference: @internalsref{TabStaff}, @internalsref{TabVoice}.
2102 Chords are not handled in a special way, and hence the automatic
2103 string selector may easily select the same string to two notes in a
2107 @node Non-guitar tablatures
2108 @subsection Non-guitar tablatures
2109 @cindex Non-guitar tablatures
2111 You can change the tuning of the strings. A string tuning is given as
2112 a Scheme list with one integer number for each string, the number
2113 being the pitch (measured in semitones relative to middle C) of an
2114 open string. The numbers specified for @code{stringTuning} are the
2115 numbers of semitones to subtract or add, starting the specified pitch
2116 by default middle C, in string order. LilyPond automatically calculates
2117 the number of strings by looking at @code{stringTuning}.
2119 In the next example,
2120 @code{stringTunings} is set for the pitches e, a, d, and g
2122 @lilypond[quote,ragged-right,fragment,verbatim]
2124 \set TabStaff.stringTunings = #'(-5 -10 -15 -20)
2126 a,4 c' a e' e c' a e'
2131 LilyPond comes with predefined string tunings for banjo, mandolin, guitar
2135 \set TabStaff.stringTunings = #bass-tuning
2138 The default string tuning is @code{guitar-tuning} (the standard EADGBE
2140 Some other predefined tunings are @code{guitar-open-g-tuning},
2141 @code{mandolin-tuning} and @code{banjo-open-g-tuning}.
2145 The file @file{scm/@/output@/-lib@/.scm} contains the predefined string
2147 Program reference: @internalsref{Tab_note_heads_engraver}.
2151 No guitar special effects have been implemented.
2155 @node Banjo tablatures
2156 @subsection Banjo tablatures
2157 @cindex Banjo tablatures
2159 LilyPond has basic support for five stringed banjo. When making tablatures
2160 for five stringed banjo, use the banjo tablature format function to get
2162 fret numbers for the fifth string:
2164 @lilypond[quote,ragged-right,fragment,verbatim]
2166 \set TabStaff.tablatureFormat = #fret-number-tablature-format-banjo
2167 \set TabStaff.stringTunings = #banjo-open-g-tuning
2170 g8 d' g'\5 a b g e d' |
2171 g4 d''8\5 b' a'\2 g'\5 e'\2 d' |
2177 A number of common tunings for banjo are predefined in LilyPond:
2178 @code{banjo-c-tuning} (gCGBD), @code{banjo-modal-tuning} (gDGCD),
2179 @code{banjo-open-d-tuning} (aDF#AD) and @code{banjo-open-dm-tuning}
2182 These tunings may be converted to four string banjo tunings using the
2183 @code{four-string-banjo} function:
2186 \set TabStaff.stringTunings = #(four-string-banjo banjo-c-tuning)
2191 The file @file{scm/@/output@/-lib@/.scm} contains predefined banjo tunings.
2195 @subsection Fret diagrams
2196 @cindex fret diagrams
2197 @cindex chord diagrams
2199 Fret diagrams can be added to music as a markup to the desired note. The
2200 markup contains information about the desired fret diagram, as shown in the
2203 @lilypond[verbatim, ragged-right, quote]
2205 d'^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
2207 fis'^\markup \override #'(size . 0.75) {
2208 \override #'(finger-code . below-string) {
2209 \fret-diagram-verbose #'((place-fret 6 2 1) (barre 6 1 2)
2210 (place-fret 5 4 3) (place-fret 4 4 4)
2211 (place-fret 3 3 2) (place-fret 2 2 1)
2216 c'^\markup \override #'(dot-radius . 0.35) {
2217 \override #'(finger-code . in-dot) {
2218 \override #'(dot-color . white) {
2219 \fret-diagram-terse #"x;3-1-(;5-2;5-3;5-4;3-1-);"
2228 There are three different fret-diagram markup interfaces: standard, terse,
2229 and verbose. The three interfaces produce equivalent markups, but have
2230 varying amounts of information in the markup string. Details about the
2231 markup interfaces are found at @ref{Overview of text markup commands}.
2233 You can set a number of graphical properties according to your preference.
2234 Details about the property interface to fret diagrams are found at
2235 @internalsref{fret-diagram-interface}.
2240 Examples: @inputfileref{input/@/test,fret@/-diagram@/.ly}
2243 @node Right hand fingerings
2244 @subsection Right hand fingerings
2246 Right hand fingerings in chords can be entered using
2247 @code{@var{note}-\rightHandFinger @var{finger}}
2249 @lilypond[verbatim,fragment,relative=2]
2250 <c-\rightHandFinger #1 e-\rightHandFinger #2 >
2253 for brevity, you can abbreviate @code{\rightHandFinger} to something
2254 short, for example @code{RH},
2257 #(define RH rightHandFinger)
2260 @cindex fingerings, right hand, for guitar
2261 @cindex right hand fingerings for guitar
2265 You may exercise greater control over right handing fingerings by
2266 setting @code{strokeFingerOrientations},
2268 @lilypond[quote,verbatim,ragged-right,fragment,relative=1]
2269 #(define RH rightHandFinger)
2271 \set strokeFingerOrientations = #'(up down)
2272 <c-\RH #1 es-\RH #2 g-\RH #4 > 4
2273 \set strokeFingerOrientations = #'(up right down)
2274 <c-\RH #1 es-\RH #2 g-\RH #4 > 4
2278 The letters used for the fingerings are contained in the property
2279 @code{digit-names}, but they can also be set individually by supplying
2280 @code{\rightHandFinger} with a string argument, as in the following example
2283 @lilypond[quote,verbatim,ragged-right,fragment,relative=1]
2284 #(define RH rightHandFinger)
2286 \set strokeFingerOrientations = #'(right)
2287 \override StrokeFinger #'digit-names = ##("x" "y" "z" "!" "@")
2295 Internalls: @internalsref{StrokeFinger}
2299 @node Other guitar issues
2300 @subsection Other guitar issues
2302 This example demonstrates how to include guitar position and
2303 barring indications.
2305 @lilypond[quote,ragged-right,fragment,verbatim,relative=0]
2309 \override TextSpanner #'bound-details #'left #'text = "XII "
2311 b16 e16 g16 e16 b16 g16\stopTextSpan
2316 Stopped (X) note heads are used in guitar music to signal a place where the
2317 guitarist must play a certain note or chord, with its fingers just
2318 touching the strings instead of fully pressing them. This gives the sound a
2319 percussive noise-like sound that still maintains part of the original
2320 pitch. It is notated with cross noteheads; this is
2321 demonstrated in @ref{Special noteheads}.
2330 * Bagpipe definitions::
2335 @node Bagpipe definitions
2336 @subsection Bagpipe definitions
2338 LilyPond contains special definitions for music for the Scottish
2339 highland bagpipe; to use them, add
2342 \include "bagpipe.ly"
2346 at the top of your input file. This lets you add the special gracenotes
2347 common to bagpipe music with short commands. For example, you could
2348 write @code{\taor} instead of
2351 \grace @{ \small G32[ d G e] @}
2354 @code{bagpipe.ly} also contains pitch definitions for the bagpipe
2355 notes in the appropiate octaves, so you do not need to worry about
2356 @code{\relative} or @code{\transpose}.
2358 @lilypond[ragged-right,verbatim,quote,notime]
2359 \include "bagpipe.ly"
2360 { \grg G4 \grg a \grg b \grg c \grg d \grg e \grg f \grA g A }
2363 Bagpipe music nominally uses the key of D Major (even though that
2364 isn't really true). However, since that is the only key that can be used,
2365 the key signature is normally not written out. To set this up correctly,
2366 always start your music with @code{\hideKeySignature}. If you for some
2367 reason want to show the key signature, you can use @code{\showKeySignature}
2370 Some modern music use cross fingering on c and f to flatten those notes.
2371 This can be indicated by @code{cflat} or @code{fflat}. Similarly, the
2372 piobaireachd high g can be written @code{gflat} when it occurs in light
2376 @node Bagpipe example
2377 @subsection Bagpipe example
2379 This is what the well known tune Amazing Grace looks like in bagpipe
2382 @lilypond[verbatim,quote]
2383 \include "bagpipe.ly"
2386 \context { \Score \remove "Bar_number_engraver" }
2390 title = "Amazing Grace"
2392 arranger = "Trad. arr."
2398 \grg \partial 4 a8. d16
2399 \slurd d2 \grg f8[ e32 d16.]
2402 \grG a2 \grg a8. d16
2403 \slurd d2 \grg f8[ e32 d16.]
2404 \grg f2 \grg e8. f16
2407 \grg A2 \hdblf f8[ e32 d16.]
2410 \grG a2 \grg a8. d16
2411 \slurd d2 \grg f8[ e32 d16.]
2420 @node Ancient notation
2421 @section Ancient notation
2423 @cindex Vaticana, Editio
2424 @cindex Medicaea, Editio
2429 Support for ancient notation includes features for mensural notation
2430 and Gregorian Chant notation. There is also limited support for
2431 figured bass notation.
2433 Many graphical objects provide a @code{style} property, see
2436 @ref{Ancient note heads},
2438 @ref{Ancient accidentals},
2440 @ref{Ancient rests},
2442 @ref{Ancient clefs},
2444 @ref{Ancient flags},
2446 @ref{Ancient time signatures}.
2449 By manipulating such a grob property, the typographical appearance of
2450 the affected graphical objects can be accommodated for a specific
2451 notation flavor without the need for introducing any new notational
2454 In addition to the standard articulation signs described in section
2455 @ref{Articulations}, specific articulation signs for ancient notation
2460 @ref{Ancient articulations}
2463 Other aspects of ancient notation can not that easily be expressed
2464 in terms of just changing a style property of a graphical object or
2465 adding articulation signs. Some notational concepts are introduced
2466 specifically for ancient notation,
2477 If this all is too much of documentation for you, and you just want to
2478 dive into typesetting without worrying too much about the details on
2479 how to customize a context, you may have a look at the predefined
2480 contexts. Use them to set up predefined style-specific voice and
2481 staff contexts, and directly go ahead with the note entry,
2485 @ref{Gregorian Chant contexts},
2487 @ref{Mensural contexts}.
2490 There is limited support for figured bass notation which came
2491 up during the baroque period.
2498 Here are all suptopics at a glance:
2501 * Ancient note heads::
2502 * Ancient accidentals::
2506 * Ancient time signatures::
2507 * Ancient articulations::
2511 * Gregorian Chant contexts::
2512 * Mensural contexts::
2513 * Musica ficta accidentals::
2519 @node Ancient note heads
2520 @subsection Ancient note heads
2522 @cindex note heads, ancient
2524 For ancient notation, a note head style other than the @code{default}
2525 style may be chosen. This is accomplished by setting the @code{style}
2526 property of the @internalsref{NoteHead} object to @code{baroque},
2527 @code{neomensural}, @code{mensural} or @code{petrucci}. The
2528 @code{baroque} style differs from the @code{default} style only in
2529 using a square shape for @code{\breve} note heads. The
2530 @code{neomensural} style differs from the @code{baroque} style in that
2531 it uses rhomboidal heads for whole notes and all smaller durations.
2532 Stems are centered on the note heads. This style is particularly
2533 useful when transcribing mensural music, e.g., for the incipit. The
2534 @code{mensural} style produces note heads that mimic the look of note
2535 heads in historic printings of the 16th century. Finally, the
2536 @code{petrucci} style also mimicks historic printings, but uses bigger
2539 The following example demonstrates the @code{neomensural} style
2541 @lilypond[quote,fragment,ragged-right,verbatim]
2542 \set Score.skipBars = ##t
2543 \override NoteHead #'style = #'neomensural
2544 a'\longa a'\breve a'1 a'2 a'4 a'8 a'16
2547 When typesetting a piece in Gregorian Chant notation, the
2548 @internalsref{Gregorian_ligature_engraver} will automatically select
2549 the proper note heads, so there is no need to explicitly set the
2550 note head style. Still, the note head style can be set, e.g., to
2551 @code{vaticana_punctum} to produce punctum neumes. Similarly, a
2552 @internalsref{Mensural_ligature_engraver} is used to automatically
2553 assemble mensural ligatures. See @ref{Ligatures} for how ligature
2558 @ref{Note head styles} gives an overview over all available note head styles.
2561 @node Ancient accidentals
2562 @subsection Ancient accidentals
2567 Use the @code{glyph-name-alist} property of grob
2568 @internalsref{Accidental} and @internalsref{KeySignature} to select
2569 ancient accidentals.
2571 @lilypond[quote,ragged-right,staffsize=26]
2578 \line { " " \musicglyph #"accidentals.vaticana-1"
2579 " " \musicglyph #"accidentals.vaticana0" }
2583 \line { " " \musicglyph #"accidentals.medicaea-1" }
2587 \line { " " \musicglyph #"accidentals.hufnagel-1" }
2591 \line { " " \musicglyph #"accidentals.mensural-1"
2592 " " \musicglyph #"accidentals.mensural1" }
2598 \context { \Score \remove "Bar_number_engraver" }
2600 \remove "Clef_engraver"
2601 \remove "Key_engraver"
2602 \remove "Time_signature_engraver"
2603 \remove "Staff_symbol_engraver"
2604 \override VerticalAxisGroup #'minimum-Y-extent = ##f
2610 As shown, not all accidentals are supported by each style. When
2611 trying to access an unsupported accidental, LilyPond will switch to a
2612 different style, as demonstrated in
2613 @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
2615 Similarly to local accidentals, the style of the key signature can be
2616 controlled by the @code{glyph-name-alist} property of the
2617 @internalsref{KeySignature} grob.
2621 In this manual: @ref{Pitches}, @ref{Cautionary accidentals} and
2622 @ref{Automatic accidentals} give a general introduction of the use of
2623 accidentals. @ref{Key signature} gives a general introduction of
2624 the use of key signatures.
2626 Program reference: @internalsref{KeySignature}.
2628 Examples: @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
2631 @subsection Ancient rests
2633 @cindex rests, ancient
2636 Use the @code{style} property of grob @internalsref{Rest} to select
2637 ancient rests. Supported styles are @code{classical},
2638 @code{neomensural}, and @code{mensural}. @code{classical} differs
2639 from the @code{default} style only in that the quarter rest looks like
2640 a horizontally mirrored 8th rest. The @code{neomensural} style suits
2641 well for, e.g., the incipit of a transcribed mensural piece of music.
2642 The @code{mensural} style finally mimics the appearance of rests as
2643 in historic prints of the 16th century.
2645 The following example demonstrates the @code{neomensural} style
2647 @lilypond[quote,fragment,ragged-right,verbatim]
2648 \set Score.skipBars = ##t
2649 \override Rest #'style = #'neomensural
2650 r\longa r\breve r1 r2 r4 r8 r16
2653 There are no 32th and 64th rests specifically for the mensural or
2654 neo-mensural style. Instead, the rests from the default style will be
2655 taken. See @inputfileref{input/@/test,rests@/.ly} for a chart of all
2658 There are no rests in Gregorian Chant notation; instead, it uses
2663 In this manual: @ref{Rests} gives a general introduction into the use of
2668 @subsection Ancient clefs
2673 LilyPond supports a variety of clefs, many of them ancient.
2675 The following table shows all ancient clefs that are supported via the
2676 @code{\clef} command. Some of the clefs use the same glyph, but
2677 differ only with respect to the line they are printed on. In such
2678 cases, a trailing number in the name is used to enumerate these clefs.
2679 Still, you can manually force a clef glyph to be typeset on an
2680 arbitrary line, as described in @ref{Clef}. The note printed to the
2681 right side of each clef in the example column denotes the @code{c'}
2682 with respect to that clef.
2684 @multitable @columnfractions .4 .4 .2
2693 modern style mensural C clef
2695 @code{neomensural-c1}, @code{neomensural-c2},@*
2696 @code{neomensural-c3}, @code{neomensural-c4}
2698 @lilypond[fragment,relative=1,notime]
2699 \clef "neomensural-c2" c
2703 petrucci style mensural C clefs, for use on different staff lines
2704 (the examples show the 2nd staff line C clef)
2706 @code{petrucci-c1}, @code{petrucci-c2},@*
2707 @code{petrucci-c3}, @code{petrucci-c4},@*
2710 @lilypond[fragment,relative=1,notime]
2712 \override NoteHead #'style = #'mensural
2717 petrucci style mensural F clef
2721 @lilypond[fragment,relative=1,notime]
2723 \override NoteHead #'style = #'mensural
2728 petrucci style mensural G clef
2732 @lilypond[fragment,relative=1,notime]
2734 \override NoteHead #'style = #'mensural
2739 historic style mensural C clef
2741 @code{mensural-c1}, @code{mensural-c2},@*
2742 @code{mensural-c3}, @code{mensural-c4}
2744 @lilypond[fragment,relative=1,notime]
2746 \override NoteHead #'style = #'mensural
2751 historic style mensural F clef
2755 @lilypond[fragment,relative=1,notime]
2757 \override NoteHead #'style = #'mensural
2762 historic style mensural G clef
2766 @lilypond[fragment,relative=1,notime]
2768 \override NoteHead #'style = #'mensural
2773 Editio Vaticana style do clef
2775 @code{vaticana-do1}, @code{vaticana-do2},@*
2778 @lilypond[fragment,relative=1,notime]
2779 \override Staff.StaffSymbol #'line-count = #4
2780 \override Staff.StaffSymbol #'color = #red
2781 \override Staff.LedgerLineSpanner #'color = #red
2782 \override Voice.Stem #'transparent = ##t
2783 \override NoteHead #'style = #'vaticana.punctum
2784 \clef "vaticana-do2"
2789 Editio Vaticana style fa clef
2791 @code{vaticana-fa1}, @code{vaticana-fa2}
2793 @lilypond[fragment,relative=1,notime]
2794 \override Staff.StaffSymbol #'line-count = #4
2795 \override Staff.StaffSymbol #'color = #red
2796 \override Staff.LedgerLineSpanner #'color = #red
2797 \override Voice.Stem #'transparent = ##t
2798 \override NoteHead #'style = #'vaticana.punctum
2799 \clef "vaticana-fa2"
2804 Editio Medicaea style do clef
2806 @code{medicaea-do1}, @code{medicaea-do2},@*
2809 @lilypond[fragment,relative=1,notime]
2810 \override Staff.StaffSymbol #'line-count = #4
2811 \override Staff.StaffSymbol #'color = #red
2812 \override Staff.LedgerLineSpanner #'color = #red
2813 \override Voice.Stem #'transparent = ##t
2814 \override NoteHead #'style = #'medicaea.punctum
2815 \clef "medicaea-do2"
2820 Editio Medicaea style fa clef
2822 @code{medicaea-fa1}, @code{medicaea-fa2}
2824 @lilypond[fragment,relative=1,notime]
2825 \override Staff.StaffSymbol #'line-count = #4
2826 \override Staff.StaffSymbol #'color = #red
2827 \override Staff.LedgerLineSpanner #'color = #red
2828 \override Voice.Stem #'transparent = ##t
2829 \override NoteHead #'style = #'medicaea.punctum
2830 \clef "medicaea-fa2"
2835 historic style hufnagel do clef
2837 @code{hufnagel-do1}, @code{hufnagel-do2},@*
2840 @lilypond[fragment,relative=1,notime]
2841 \override Staff.StaffSymbol #'line-count = #4
2842 \override Staff.StaffSymbol #'color = #red
2843 \override Staff.LedgerLineSpanner #'color = #red
2844 \override Voice.Stem #'transparent = ##t
2845 \override NoteHead #'style = #'hufnagel.punctum
2846 \clef "hufnagel-do2"
2851 historic style hufnagel fa clef
2853 @code{hufnagel-fa1}, @code{hufnagel-fa2}
2855 @lilypond[fragment,relative=1,notime]
2856 \override Staff.StaffSymbol #'line-count = #4
2857 \override Staff.StaffSymbol #'color = #red
2858 \override Staff.LedgerLineSpanner #'color = #red
2859 \override Voice.Stem #'transparent = ##t
2860 \override NoteHead #'style = #'hufnagel.punctum
2861 \clef "hufnagel-fa2"
2866 historic style hufnagel combined do/fa clef
2868 @code{hufnagel-do-fa}
2870 @lilypond[fragment,relative=1,notime]
2871 \override Staff.StaffSymbol #'color = #red
2872 \override Staff.LedgerLineSpanner #'color = #red
2873 \override Voice.Stem #'transparent = ##t
2874 \override NoteHead #'style = #'hufnagel.punctum
2875 \clef "hufnagel-do-fa"
2882 @emph{Modern style} means @qq{as is typeset in contemporary editions of
2883 transcribed mensural music.}
2885 @emph{Petrucci style} means @qq{inspired by printings published by the
2886 famous engraver Petrucci (1466-1539).}
2888 @emph{Historic style} means @qq{as was typeset or written in historic
2889 editions (other than those of Petrucci).}
2891 @emph{Editio XXX style} means @qq{as is/was printed in Editio XXX.}
2893 Petrucci used C clefs with differently balanced left-side vertical
2894 beams, depending on which staff line it is printed.
2898 In this manual: see @ref{Clef}.
2902 The mensural g clef is mapped to the Petrucci g clef.
2907 @subsection Ancient flags
2912 Use the @code{flag-style} property of grob @internalsref{Stem} to
2913 select ancient flags. Besides the @code{default} flag style,
2914 only the @code{mensural} style is supported
2916 @lilypond[quote,fragment,ragged-right,verbatim]
2917 \override Stem #'flag-style = #'mensural
2918 \override Stem #'thickness = #1.0
2919 \override NoteHead #'style = #'mensural
2921 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
2922 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
2925 Note that the innermost flare of each mensural flag always is
2926 vertically aligned with a staff line.
2928 There is no particular flag style for neo-mensural notation. Hence,
2929 when typesetting the incipit of a transcribed piece of mensural
2930 music, the default flag style should be used. There are no flags in
2931 Gregorian Chant notation.
2935 The attachment of ancient flags to stems is slightly off due to a
2936 change in early 2.3.x.
2938 Vertically aligning each flag with a staff line assumes that stems
2939 always end either exactly on or exactly in the middle between two
2940 staff lines. This may not always be true when using advanced layout
2941 features of classical notation (which however are typically out of
2942 scope for mensural notation).
2944 @node Ancient time signatures
2945 @subsection Ancient time signatures
2947 @cindex time signatures
2950 There is limited support for mensural time signatures. The
2951 glyphs are hard-wired to particular time fractions. In other words,
2952 to get a particular mensural signature glyph with the @code{\time n/m}
2953 command, @code{n} and @code{m} have to be chosen according to the
2956 @lilypond[quote,ragged-right]
2961 \remove Staff_symbol_engraver
2962 \remove Clef_engraver
2963 \remove Time_signature_engraver
2967 \set Score.timing = ##f
2968 \set Score.barAlways = ##t
2969 s_\markup { "\\time 4/4" }^\markup { " " \musicglyph
2970 #"timesig.neomensural44" }
2972 s_\markup { "\\time 2/2" }^\markup { " " \musicglyph
2973 #"timesig.neomensural22" }
2975 s_\markup { "\\time 6/4" }^\markup { " " \musicglyph
2976 #"timesig.neomensural64" }
2978 s_\markup { "\\time 6/8" }^\markup { " " \musicglyph
2979 #"timesig.neomensural68" }
2981 s_\markup { "\\time 3/2" }^\markup { " " \musicglyph
2982 #"timesig.neomensural32" }
2984 s_\markup { "\\time 3/4" }^\markup { " " \musicglyph
2985 #"timesig.neomensural34" }
2987 s_\markup { "\\time 9/4" }^\markup { " " \musicglyph
2988 #"timesig.neomensural94" }
2990 s_\markup { "\\time 9/8" }^\markup { " " \musicglyph
2991 #"timesig.neomensural98" }
2993 s_\markup { "\\time 4/8" }^\markup { " " \musicglyph
2994 #"timesig.neomensural48" }
2996 s_\markup { "\\time 2/4" }^\markup { " " \musicglyph
2997 #"timesig.neomensural24" }
3001 Use the @code{style} property of grob @internalsref{TimeSignature} to
3002 select ancient time signatures. Supported styles are
3003 @code{neomensural} and @code{mensural}. The above table uses the
3004 @code{neomensural} style. This style is appropriate for the
3005 incipit of transcriptions of mensural pieces. The @code{mensural}
3006 style mimics the look of historical printings of the 16th century.
3008 The following examples show the differences in style,
3010 @lilypond[ragged-right,fragment,relative=1,quote]
3015 c1^\markup { \hspace #-2.0 \typewriter default }
3017 \override Staff.TimeSignature #'style = #'numbered
3019 c1^\markup { \hspace #-2.0 \typewriter numbered }
3021 \override Staff.TimeSignature #'style = #'mensural
3023 c1^\markup { \hspace #-2.0 \typewriter mensural }
3025 \override Staff.TimeSignature #'style = #'neomensural
3027 c1^\markup { \hspace #-2.0 \typewriter neomensural }
3028 \override Staff.TimeSignature #'style = #'single-digit
3030 c1^\markup { \hspace #-2.0 \typewriter single-digit }
3036 This manual: @ref{Time signature} gives a general introduction to
3037 the use of time signatures.
3041 Ratios of note durations do not change with the time signature. For
3042 example, the ratio of 1 brevis = 3 semibrevis (tempus perfectum) must
3043 be made by hand, by setting
3046 breveTP = #(ly:make-duration -1 0 3 2)
3052 This sets @code{breveTP} to 3/2 times 2 = 3 times a whole note.
3054 The @code{old6/8alt} symbol (an alternate symbol for 6/8) is not
3055 addressable with @code{\time}. Use a @code{\markup} instead
3057 @node Ancient articulations
3058 @subsection Ancient articulations
3060 @cindex articulations
3062 In addition to the standard articulation signs described in section
3063 @ref{Articulations}, articulation signs for ancient notation are
3064 provided. These are specifically designed for use with notation in
3065 Editio Vaticana style.
3067 @lilypond[quote,ragged-right,verbatim]
3068 \include "gregorian-init.ly"
3070 \new VaticanaVoice {
3071 \override TextScript #'font-family = #'typewriter
3072 \override TextScript #'font-shape = #'upright
3073 \override Script #'padding = #-0.1
3074 a\ictus_"ictus" \break
3075 a\circulus_"circulus" \break
3076 a\semicirculus_"semicirculus" \break
3077 a\accentus_"accentus" \break
3078 \[ a_"episem" \episemInitium \pes b \flexa a b \episemFinis \flexa a \]
3085 Some articulations are vertically placed too closely to the
3086 correpsonding note heads.
3088 The episem line is not displayed in many cases. If it is displayed,
3089 the right end of the episem line is often too far to the right.
3092 @subsection Custodes
3097 A @emph{custos} (plural: @emph{custodes}; Latin word for @q{guard}) is a
3098 symbol that appears at the end of a staff. It anticipates the pitch
3099 of the first note(s) of the following line thus helping the performer
3100 to manage line breaks during performance.
3102 Custodes were frequently used in music notation until the 17th
3103 century. Nowadays, they have survived only in a few particular forms
3104 of musical notation such as contemporary editions of Gregorian chant
3105 like the @emph{editio vaticana}. There are different custos glyphs
3106 used in different flavors of notational style.
3108 For typesetting custodes, just put a @internalsref{Custos_engraver} into the
3109 @internalsref{Staff} context when declaring the @code{\layout} block,
3110 as shown in the following example
3116 \consists Custos_engraver
3117 Custos \override #'style = #'mensural
3122 The result looks like this
3124 @lilypond[quote,ragged-right]
3128 \override Staff.Custos #'style = #'mensural
3133 \context { \Staff \consists Custos_engraver }
3138 The custos glyph is selected by the @code{style} property. The styles
3139 supported are @code{vaticana}, @code{medicaea}, @code{hufnagel}, and
3140 @code{mensural}. They are demonstrated in the following fragment
3142 @lilypond[quote,ragged-right,fragment]
3143 \new Lyrics \lyricmode {
3145 \typewriter "vaticana"
3146 \line { " " \musicglyph #"custodes.vaticana.u0" }
3149 \typewriter "medicaea"
3150 \line { " " \musicglyph #"custodes.medicaea.u0" }
3153 \typewriter "hufnagel"
3154 \line { " " \musicglyph #"custodes.hufnagel.u0" }
3157 \typewriter "mensural"
3158 \line { " " \musicglyph #"custodes.mensural.u0" }
3165 Program reference: @internalsref{Custos}.
3168 @lsr{ancient,custodes@/.ly}.
3172 @subsection Divisiones
3178 A @emph{divisio} (plural: @emph{divisiones}; Latin word for
3179 @q{division}) is a staff context symbol that is used to structure
3180 Gregorian music into phrases and sections. The musical meaning of
3181 @emph{divisio minima}, @emph{divisio maior}, and @emph{divisio maxima}
3182 can be characterized as short, medium, and long pause, somewhat like
3183 the breathmarks from @ref{Breath marks}. The @emph{finalis} sign not
3184 only marks the end of a chant, but is also frequently used within a
3185 single antiphonal/responsorial chant to mark the end of each section.
3188 To use divisiones, include the file @file{gregorian@/-init@/.ly}. It
3189 contains definitions that you can apply by just inserting
3190 @code{\divisioMinima}, @code{\divisioMaior}, @code{\divisioMaxima},
3191 and @code{\finalis} at proper places in the input. Some editions use
3192 @emph{virgula} or @emph{caesura} instead of divisio minima.
3193 Therefore, @file{gregorian@/-init@/.ly} also defines @code{\virgula} and
3196 @lilypondfile[quote,ragged-right]{divisiones.ly}
3204 @funindex \divisioMinima
3205 @code{\divisioMinima},
3206 @funindex \divisioMaior
3207 @code{\divisioMaior},
3208 @funindex \divisioMaxima
3209 @code{\divisioMaxima},
3215 In this manual: @ref{Breath marks}.
3217 Program reference: @internalsref{BreathingSign}.
3219 Examples: @inputfileref{input/@/test,divisiones@/.ly}.
3222 @subsection Ligatures
3226 @c TODO: Should double check if I recalled things correctly when I wrote
3227 @c down the following paragraph by heart.
3229 A ligature is a graphical symbol that represents at least two distinct
3230 notes. Ligatures originally appeared in the manuscripts of Gregorian
3231 chant notation to denote ascending or descending sequences of notes.
3233 Ligatures are entered by enclosing them in @code{\[} and @code{\]}.
3234 Some ligature styles may need additional input syntax specific for
3235 this particular type of ligature. By default, the
3236 @internalsref{LigatureBracket} engraver just puts a square bracket
3239 @lilypond[quote,ragged-right,verbatim]
3247 To select a specific style of ligatures, a proper ligature engraver
3248 has to be added to the @internalsref{Voice} context, as explained in
3249 the following subsections. Only white mensural ligatures
3250 are supported with certain limitations.
3256 Ligatures need special spacing that has not yet been implemented. As
3257 a result, there is too much space between ligatures most of the time,
3258 and line breaking often is unsatisfactory. Also, lyrics do not
3259 correctly align with ligatures.
3261 Accidentals must not be printed within a ligature, but instead need to
3262 be collected and printed in front of it.
3264 The syntax still uses the deprecated infix style @code{\[ music expr
3265 \]}. For consistency reasons, it will eventually be changed to
3266 postfix style @code{note\[ ... note\]}. Alternatively, the file
3267 @file{gregorian@/-init@/.ly} can be included; it provides a scheme
3270 \ligature @var{music expr}
3272 with the same effect and is believed to be stable.
3275 * White mensural ligatures::
3276 * Gregorian square neumes ligatures::
3279 @node White mensural ligatures
3280 @subsubsection White mensural ligatures
3282 @cindex Mensural ligatures
3283 @cindex White mensural ligatures
3285 There is limited support for white mensural ligatures.
3287 To engrave white mensural ligatures, in the layout block put the
3288 @internalsref{Mensural_ligature_engraver} into the
3289 @internalsref{Voice} context, and remove the
3290 @internalsref{Ligature_bracket_engraver}, like this
3296 \remove Ligature_bracket_engraver
3297 \consists Mensural_ligature_engraver
3302 There is no additional input language to describe the shape of a
3303 white mensural ligature. The shape is rather determined solely from
3304 the pitch and duration of the enclosed notes. While this approach may
3305 take a new user a while to get accustomed to, it has the great advantage
3306 that the full musical information of the ligature is known internally.
3307 This is not only required for correct MIDI output, but also allows for
3308 automatic transcription of the ligatures.
3313 \set Score.timing = ##f
3314 \set Score.defaultBarType = "empty"
3315 \override NoteHead #'style = #'neomensural
3316 \override Staff.TimeSignature #'style = #'neomensural
3319 \[ d\longa c\breve f e d \]
3320 \[ c'\maxima d'\longa \]
3323 @lilypond[quote,ragged-right]
3326 \set Score.timing = ##f
3327 \set Score.defaultBarType = "empty"
3328 \override NoteHead #'style = #'neomensural
3329 \override Staff.TimeSignature #'style = #'neomensural
3332 \[ d\longa c\breve f e d \]
3333 \[ c'\maxima d'\longa \]
3339 \remove Ligature_bracket_engraver
3340 \consists Mensural_ligature_engraver
3346 Without replacing @internalsref{Ligature_bracket_engraver} with
3347 @internalsref{Mensural_ligature_engraver}, the same music transcribes
3350 @lilypond[quote,ragged-right]
3352 \set Score.timing = ##f
3353 \set Score.defaultBarType = "empty"
3354 \override NoteHead #'style = #'neomensural
3355 \override Staff.TimeSignature #'style = #'neomensural
3358 \[ d\longa c\breve f e d \]
3359 \[ c'\maxima d'\longa \]
3366 Horizontal spacing is poor.
3368 @node Gregorian square neumes ligatures
3369 @subsubsection Gregorian square neumes ligatures
3371 @cindex Square neumes ligatures
3372 @cindex Gregorian square neumes ligatures
3374 There is limited support for Gregorian square neumes notation
3375 (following the style of the Editio Vaticana). Core ligatures can
3376 already be typeset, but essential issues for serious typesetting are
3377 still lacking, such as (among others) horizontal alignment of multiple
3378 ligatures, lyrics alignment and proper handling of accidentals.
3381 The following table contains the extended neumes table of the 2nd
3382 volume of the Antiphonale Romanum (@emph{Liber Hymnarius}), published
3383 1983 by the monks of Solesmes.
3385 @multitable @columnfractions .4 .2 .2 .2
3402 @c TODO: \layout block is identical in all of the below examples.
3403 @c Therefore, it should somehow be included rather than duplicated all
3406 @c why not make identifiers in ly/engraver-init.ly? --hwn
3408 @c Because it's just used to typeset plain notes without
3409 @c a staff for demonstration purposes rather than something
3410 @c special of Gregorian chant notation. --jr
3415 @lilypond[staffsize=26,line-width=1.5\cm]
3416 \include "gregorian-init.ly"
3421 \noBreak s^\markup {"a"} \noBreak
3423 % Punctum Inclinatum
3425 \noBreak s^\markup {"b"}
3427 \layout { \neumeDemoLayout }}
3430 @lilypond[staffsize=26,line-width=2.5\cm]
3431 \include "gregorian-init.ly"
3434 % Punctum Auctum Ascendens
3435 \[ \auctum \ascendens b \]
3436 \noBreak s^\markup {"c"} \noBreak
3438 % Punctum Auctum Descendens
3439 \[ \auctum \descendens b \]
3440 \noBreak s^\markup {"d"} \noBreak
3442 % Punctum Inclinatum Auctum
3443 \[ \inclinatum \auctum b \]
3444 \noBreak s^\markup {"e"}
3446 \layout { \neumeDemoLayout }}
3449 @lilypond[staffsize=26,line-width=1.0\cm]
3450 \include "gregorian-init.ly"
3453 % Punctum Inclinatum Parvum
3454 \[ \inclinatum \deminutum b \]
3455 \noBreak s^\markup {"f"}
3457 \layout { \neumeDemoLayout }}
3463 @lilypond[staffsize=26,line-width=1.0\cm]
3464 \include "gregorian-init.ly"
3469 \noBreak s^\markup {"g"}
3471 \layout { \neumeDemoLayout }}
3477 @code{3. Apostropha vel Stropha}
3479 @lilypond[staffsize=26,line-width=1.0\cm]
3480 \include "gregorian-init.ly"
3485 \noBreak s^\markup {"h"}
3487 \layout { \neumeDemoLayout }}
3490 @lilypond[staffsize=26,line-width=1.0\cm]
3491 \include "gregorian-init.ly"
3495 \[ \stropha \auctum b \]
3496 \noBreak s^\markup {"i"}
3498 \layout { \neumeDemoLayout }}
3505 @lilypond[staffsize=26,line-width=1.0\cm]
3506 \include "gregorian-init.ly"
3511 \noBreak s^\markup {"j"}
3513 \layout { \neumeDemoLayout }}
3519 @code{5. Clivis vel Flexa}
3521 @lilypond[staffsize=26,line-width=1.0\cm]
3522 \include "gregorian-init.ly"
3529 \layout { \neumeDemoLayout }}
3532 @lilypond[staffsize=26,line-width=2.0\cm]
3533 \include "gregorian-init.ly"
3536 % Clivis Aucta Descendens
3537 \[ b \flexa \auctum \descendens g \]
3538 \noBreak s^\markup {"l"} \noBreak
3540 % Clivis Aucta Ascendens
3541 \[ b \flexa \auctum \ascendens g \]
3542 \noBreak s^\markup {"m"}
3544 \layout { \neumeDemoLayout }}
3547 @lilypond[staffsize=26,line-width=1.0\cm]
3548 \include "gregorian-init.ly"
3552 \[ b \flexa \deminutum g \]
3555 \layout { \neumeDemoLayout }}
3559 @code{6. Podatus vel Pes}
3561 @lilypond[staffsize=26,line-width=1.0\cm]
3562 \include "gregorian-init.ly"
3569 \layout { \neumeDemoLayout }}
3572 @lilypond[staffsize=26,line-width=2.0\cm]
3573 \include "gregorian-init.ly"
3576 % Pes Auctus Descendens
3577 \[ g \pes \auctum \descendens b \]
3578 \noBreak s^\markup {"p"} \noBreak
3580 % Pes Auctus Ascendens
3581 \[ g \pes \auctum \ascendens b \]
3582 \noBreak s^\markup {"q"}
3584 \layout { \neumeDemoLayout }}
3587 @lilypond[staffsize=26,line-width=1.0\cm]
3588 \include "gregorian-init.ly"
3592 \[ g \pes \deminutum b \]
3595 \layout { \neumeDemoLayout }}
3599 @code{7. Pes Quassus}
3601 @lilypond[staffsize=26,line-width=1.0\cm]
3602 \include "gregorian-init.ly"
3606 \[ \oriscus g \pes \virga b \]
3609 \layout { \neumeDemoLayout }}
3612 @lilypond[staffsize=26,line-width=1.0\cm]
3613 \include "gregorian-init.ly"
3616 % Pes Quassus Auctus Descendens
3617 \[ \oriscus g \pes \auctum \descendens b \]
3620 \layout { \neumeDemoLayout }}
3625 @code{8. Quilisma Pes}
3627 @lilypond[staffsize=26,line-width=1.0\cm]
3628 \include "gregorian-init.ly"
3632 \[ \quilisma g \pes b \]
3635 \layout { \neumeDemoLayout }}
3638 @lilypond[staffsize=26,line-width=1.0\cm]
3639 \include "gregorian-init.ly"
3642 % Quilisma Pes Auctus Descendens
3643 \[ \quilisma g \pes \auctum \descendens b \]
3646 \layout { \neumeDemoLayout }}
3651 @code{9. Podatus Initio Debilis}
3653 @lilypond[staffsize=26,line-width=1.0\cm]
3654 \include "gregorian-init.ly"
3657 % Pes Initio Debilis
3658 \[ \deminutum g \pes b \]
3661 \layout { \neumeDemoLayout }}
3664 @lilypond[staffsize=26,line-width=1.0\cm]
3665 \include "gregorian-init.ly"
3668 % Pes Auctus Descendens Initio Debilis
3669 \[ \deminutum g \pes \auctum \descendens b \]
3672 \layout { \neumeDemoLayout }}
3679 @lilypond[staffsize=26,line-width=1.0\cm]
3680 \include "gregorian-init.ly"
3684 \[ a \pes b \flexa g \]
3687 \layout { \neumeDemoLayout }}
3690 @lilypond[staffsize=26,line-width=1.0\cm]
3691 \include "gregorian-init.ly"
3694 % Torculus Auctus Descendens
3695 \[ a \pes b \flexa \auctum \descendens g \]
3698 \layout { \neumeDemoLayout }}
3701 @lilypond[staffsize=26,line-width=1.0\cm]
3702 \include "gregorian-init.ly"
3705 % Torculus Deminutus
3706 \[ a \pes b \flexa \deminutum g \]
3709 \layout { \neumeDemoLayout }}
3713 @code{11. Torculus Initio Debilis}
3715 @lilypond[staffsize=26,line-width=1.0\cm]
3716 \include "gregorian-init.ly"
3719 % Torculus Initio Debilis
3720 \[ \deminutum a \pes b \flexa g \]
3723 \layout { \neumeDemoLayout }}
3726 @lilypond[staffsize=26,line-width=1.0\cm]
3727 \include "gregorian-init.ly"
3730 % Torculus Auctus Descendens Initio Debilis
3731 \[ \deminutum a \pes b \flexa \auctum \descendens g \]
3734 \layout { \neumeDemoLayout }}
3737 @lilypond[staffsize=26,line-width=1.0\cm]
3738 \include "gregorian-init.ly"
3741 % Torculus Deminutus Initio Debilis
3742 \[ \deminutum a \pes b \flexa \deminutum g \]
3745 \layout { \neumeDemoLayout }}
3749 @code{12. Porrectus}
3751 @lilypond[staffsize=26,line-width=1.0\cm]
3752 \include "gregorian-init.ly"
3756 \[ a \flexa g \pes b \]
3759 \layout { \neumeDemoLayout }}
3762 @lilypond[staffsize=26,line-width=1.0\cm]
3763 \include "gregorian-init.ly"
3766 % Porrectus Auctus Descendens
3767 \[ a \flexa g \pes \auctum \descendens b \]
3770 \layout { \neumeDemoLayout }}
3773 @lilypond[staffsize=26,line-width=1.0\cm]
3774 \include "gregorian-init.ly"
3777 % Porrectus Deminutus
3778 \[ a \flexa g \pes \deminutum b \]
3781 \layout { \neumeDemoLayout }}
3787 @lilypond[staffsize=26,line-width=1.0\cm]
3788 \include "gregorian-init.ly"
3792 \[ \virga b \inclinatum a \inclinatum g \]
3795 \layout { \neumeDemoLayout }
3799 @lilypond[staffsize=26,line-width=1.0\cm]
3800 \include "gregorian-init.ly"
3804 \[ \virga b \inclinatum a \inclinatum \auctum g \]
3807 \layout { \neumeDemoLayout }}
3810 @lilypond[staffsize=26,line-width=1.0\cm]
3811 \include "gregorian-init.ly"
3814 % Climacus Deminutus
3815 \[ \virga b \inclinatum a \inclinatum \deminutum g \]
3818 \layout { \neumeDemoLayout }}
3822 @code{14. Scandicus}
3824 @lilypond[staffsize=26,line-width=1.0\cm]
3825 \include "gregorian-init.ly"
3829 \[ g \pes a \virga b \]
3832 \layout { \neumeDemoLayout }}
3835 @lilypond[staffsize=26,line-width=1.0\cm]
3836 \include "gregorian-init.ly"
3839 % Scandicus Auctus Descendens
3840 \[ g \pes a \pes \auctum \descendens b \]
3843 \layout { \neumeDemoLayout }}
3846 @lilypond[staffsize=26,line-width=1.0\cm]
3847 \include "gregorian-init.ly"
3850 % Scandicus Deminutus
3851 \[ g \pes a \pes \deminutum b \]
3854 \layout { \neumeDemoLayout }}
3860 @lilypond[staffsize=26,line-width=1.0\cm]
3861 \include "gregorian-init.ly"
3865 \[ g \oriscus a \pes \virga b \]
3868 \layout { \neumeDemoLayout }}
3871 @lilypond[staffsize=26,line-width=1.0\cm]
3872 \include "gregorian-init.ly"
3875 % Salicus Auctus Descendens
3876 \[ g \oriscus a \pes \auctum \descendens b \]
3879 \layout { \neumeDemoLayout }}
3886 @lilypond[staffsize=26,line-width=1.0\cm]
3887 \include "gregorian-init.ly"
3891 \[ \stropha b \stropha b \stropha a \]
3894 \layout { \neumeDemoLayout }
3903 Unlike most other neumes notation systems, the input language for
3904 neumes does not reflect the typographical appearance, but is designed
3905 to focus on musical meaning. For example, @code{\[ a \pes b
3906 \flexa g \]} produces a Torculus consisting of three Punctum heads,
3907 while @code{\[ a \flexa g \pes b \]} produces a Porrectus with a
3908 curved flexa shape and only a single Punctum head. There is no
3909 command to explicitly typeset the curved flexa shape; the decision of
3910 when to typeset a curved flexa shape is based on the musical
3911 input. The idea of this approach is to separate the musical aspects
3912 of the input from the notation style of the output. This way, the
3913 same input can be reused to typeset the same music in a different
3914 style of Gregorian chant notation.
3916 The following table shows the code fragments that produce the
3917 ligatures in the above neumes table. The letter in the first column
3918 in each line of the below table indicates to which ligature in the
3919 above table it refers. The second column gives the name of the
3920 ligature. The third column shows the code fragment that produces this
3921 ligature, using @code{g}, @code{a}, and @code{b} as example pitches.
3923 @multitable @columnfractions .02 .31 .67
3943 @code{\[ \inclinatum b \]}
3951 @code{\[ \auctum \ascendens b \]}
3959 @code{\[ \auctum \descendens b \]}
3964 Punctum Inclinatum@*
3967 @code{\[ \inclinatum \auctum b \]}
3972 Punctum Inclinatum@*
3974 @code{\[ \inclinatum \deminutum b \]}
3981 @code{\[ \virga b \]}
3988 @code{\[ \stropha b \]}
3995 @code{\[ \stropha \auctum b \]}
4002 @code{\[ \oriscus b \]}
4009 @code{\[ b \flexa g \]}
4017 @code{\[ b \flexa \auctum \descendens g \]}
4025 @code{\[ b \flexa \auctum \ascendens g \]}
4032 @code{\[ b \flexa \deminutum g \]}
4039 @code{\[ g \pes b \]}
4047 @code{\[ g \pes \auctum \descendens b \]}
4055 @code{\[ g \pes \auctum \ascendens b \]}
4062 @code{\[ g \pes \deminutum b \]}
4069 @code{\[ \oriscus g \pes \virga b \]}
4075 Auctus Descendens @tab
4076 @code{\[ \oriscus g \pes \auctum \descendens b \]}
4083 @code{\[ \quilisma g \pes b \]}
4091 @code{\[ \quilisma g \pes \auctum \descendens b \]}
4098 @code{\[ \deminutum g \pes b \]}
4103 Pes Auctus Descendens@*
4106 @code{\[ \deminutum g \pes \auctum \descendens b \]}
4113 @code{\[ a \pes b \flexa g \]}
4121 @code{\[ a \pes b \flexa \auctum \descendens g \]}
4128 @code{\[ a \pes b \flexa \deminutum g \]}
4133 Torculus Initio Debilis
4135 @code{\[ \deminutum a \pes b \flexa g \]}
4141 Descendens Initio Debilis
4143 @code{\[ \deminutum a \pes b \flexa \auctum \descendens g \]}
4148 Torculus Deminutus@*
4151 @code{\[ \deminutum a \pes b \flexa \deminutum g \]}
4158 @code{\[ a \flexa g \pes b \]}
4166 @code{\[ a \flexa g \pes \auctum \descendens b \]}
4173 @code{\[ a \flexa g \pes \deminutum b \]}
4180 @code{\[ \virga b \inclinatum a \inclinatum g \]}
4187 @code{\[ \virga b \inclinatum a \inclinatum \auctum g \]}
4194 @code{\[ \virga b \inclinatum a \inclinatum \deminutum g \]}
4201 @code{\[ g \pes a \virga b \]}
4209 @code{\[ g \pes a \pes \auctum \descendens b \]}
4216 @code{\[ g \pes a \pes \deminutum b \]}
4223 @code{\[ g \oriscus a \pes \virga b \]}
4228 Salicus Auctus Descendens
4230 @code{\[ g \oriscus a \pes \auctum \descendens b \]}
4237 @code{\[ \stropha b \stropha b \stropha a \]}
4240 The ligatures listed above mainly serve as a limited, but still
4241 representative pool of Gregorian ligature examples. Virtually, within
4242 the ligature delimiters @code{\[} and @code{\]}, any number of heads
4243 may be accumulated to form a single ligature, and head prefixes like
4244 @code{\pes}, @code{\flexa}, @code{\virga}, @code{\inclinatum},
4245 etc. may be mixed in as desired. The use of the set of rules that
4246 underlies the construction of the ligatures in the above table is
4247 accordingly extrapolated. This way, infinitely many different
4248 ligatures can be created.
4250 Augmentum dots, also called @emph{morae}, are added with the music
4251 function @code{\augmentum}. Note that @code{\augmentum} is
4252 implemented as a unary music function rather than as head prefix. It
4253 applies to the immediately following music expression only. That is,
4254 @code{\augmentum \virga c} will have no visible effect. Instead, say
4255 @code{\virga \augmentum c} or @code{\augmentum @{\virga c@}}. Also
4256 note that you can say @code{\augmentum @{a g@}} as a shortcut for
4257 @code{\augmentum a \augmentum g}.
4259 @lilypond[quote,ragged-right,verbatim]
4260 \include "gregorian-init.ly"
4262 \new VaticanaVoice {
4263 \[ \augmentum a \flexa \augmentum g \]
4271 The following head prefixes are supported
4277 @funindex \inclinatum
4281 @funindex \descendens
4283 @funindex \ascendens
4289 @funindex \deminutum
4296 Head prefixes can be accumulated, though restrictions apply. For
4297 example, either @code{\descendens} or @code{\ascendens} can be applied
4298 to a head, but not both to the same head.
4302 Two adjacent heads can be tied together with the @code{\pes} and
4303 @code{\flexa} infix commands for a rising and falling line of melody,
4306 @funindex \augmentum
4307 Use the unary music function @code{\augmentum} to add augmentum dots.
4311 When an @code{\augmentum} dot appears at the end of the last staff
4312 within a ligature, it is sometimes vertically placed wrong. As a
4313 workaround, add an additional skip note (e.g. @code{s8}) as last note
4316 @code{\augmentum} should be implemented as a head prefix rather than a
4317 unary music function, such that @code{\augmentum} can be intermixed
4318 with head prefixes in arbitrary order.
4320 @node Gregorian Chant contexts
4321 @subsection Gregorian Chant contexts
4323 @cindex VaticanaVoiceContext
4324 @cindex VaticanaStaffContext
4326 The predefined @code{VaticanaVoiceContext} and
4327 @code{VaticanaStaffContext} can be used to engrave a piece of
4328 Gregorian Chant in the style of the Editio Vaticana. These contexts
4329 initialize all relevant context properties and grob properties to
4330 proper values, so you can immediately go ahead entering the chant, as
4331 the following excerpt demonstrates
4333 @lilypond[quote,ragged-right,packed,verbatim]
4334 \include "gregorian-init.ly"
4337 \new VaticanaVoice = "cantus" {
4338 \[ c'\melisma c' \flexa a \]
4339 \[ a \flexa \deminutum g\melismaEnd \]
4341 \[ f\melisma \pes a c' c' \pes d'\melismaEnd \]
4342 c' \divisioMinima \break
4343 \[ c'\melisma c' \flexa a \]
4344 \[ a \flexa \deminutum g\melismaEnd \] f \divisioMinima
4346 \new Lyrics \lyricsto "cantus" {
4347 San- ctus, San- ctus, San- ctus
4354 @node Mensural contexts
4355 @subsection Mensural contexts
4357 @cindex MensuralVoiceContext
4358 @cindex MensuralStaffContext
4360 The predefined @code{MensuralVoiceContext} and
4361 @code{MensuralStaffContext} can be used to engrave a piece in mensural
4362 style. These contexts initialize all relevant context properties and
4363 grob properties to proper values, so you can immediately go ahead
4364 entering the chant, as the following excerpt demonstrates
4366 @lilypond[quote,ragged-right,verbatim]
4369 \new MensuralVoice = "discantus" \transpose c c' {
4370 \override Score.BarNumber #'transparent = ##t {
4371 c'1\melisma bes a g\melismaEnd
4373 \[ f1\melisma a c'\breve d'\melismaEnd \]
4375 c'\breve\melisma a1 g1\melismaEnd
4376 fis\longa^\signumcongruentiae
4379 \new Lyrics \lyricsto "discantus" {
4380 San -- ctus, San -- ctus, San -- ctus
4386 @node Musica ficta accidentals
4387 @subsection Musica ficta accidentals
4389 In European music from before about 1600, singers were often expected
4390 to chromatically alter notes at their own initiative. This is called
4391 @q{Musica Ficta}. In modern transcriptions, these accidentals are
4392 usually printed over the note.
4394 @cindex Accidental, musica ficta
4395 @cindex Musica ficta
4397 Support for such suggested accidentals is included, and can be
4398 switched on by setting @code{suggestAccidentals} to true.
4400 @funindex suggestAccidentals
4402 @lilypond[verbatim,fragment,relative=1]
4404 \set suggestAccidentals = ##t
4410 Program reference: @internalsref{Accidental_engraver} engraver and the
4411 @internalsref{AccidentalSuggestion} object.
4414 @subsection Figured bass
4416 @cindex Basso continuo
4418 @c TODO: musicological blurb about FB
4421 LilyPond has support for figured bass
4423 @lilypond[quote,ragged-right,verbatim,fragment]
4425 \new Voice { \clef bass dis4 c d ais g fis}
4426 \new FiguredBass \figuremode {
4427 < 6 >4 < 7\+ >8 < 6+ [_!] >
4434 The support for figured bass consists of two parts: there is an input
4435 mode, introduced by @code{\figuremode}, where you can enter bass figures
4436 as numbers, and there is a context called @internalsref{FiguredBass} that
4437 takes care of making @internalsref{BassFigure} objects.
4439 In figures input mode, a group of bass figures is delimited by
4440 @code{<} and @code{>}. The duration is entered after the @code{>}
4444 @lilypond[quote,ragged-right,fragment]
4446 \figuremode { <4 6> }
4449 Accidentals are added when you append @code{-}, @code{!}, and @code{+}
4450 to the numbers. A plus sign is added when you append @code{\+}, and
4451 diminished fifths and sevenths can be obtained with @code{5/} and @code{7/}.
4454 <4- 6+ 7!> <5++> <3--> <7/> r <6\+ 5/>
4456 @lilypond[quote,ragged-right,fragment]
4457 \figures { <4- 6+ 7!> <5++> <3--> <7/> r <6\+ 5/> }
4460 Spaces may be inserted by using @code{_}. Brackets are
4461 introduced with @code{[} and @code{]}. You can also include text
4462 strings and text markups, see @ref{Overview of text markup commands}.
4465 < [4 6] 8 [_! 12] > < 5 \markup @{ \number 6 \super (1) @} >
4467 @lilypond[quote,ragged-right,fragment]
4469 \figuremode { < [4 6] 8 [_! 12] > < 5 \markup{ \tiny \number 6 \super (1)} > }
4473 It is also possible to use continuation lines for repeated figures,
4475 @lilypond[verbatim,relative=1]
4482 \set useBassFigureExtenders = ##t
4489 In this case, the extender lines always replace existing figures.
4491 The @code{FiguredBass} context doesn't pay attention to the actual
4492 bass line. As a consequence, you may have to insert extra figures to
4493 get extender lines below all notes, and you may have to add @code{\!}
4494 to avoid getting an extender line, e.g.
4496 @lilypond[relative=1]
4500 \set useBassFigureExtenders = ##t
4501 <6 4->4. <6 4->16. <6 4->32 <5>8. r16 <6>8 <6\! 5->
4505 f16. g32 f16. g32 f16. g32 f16. g32 f8. es16 d8 es
4510 When using continuation lines, common figures are always put in the
4511 same vertical position. When this is unwanted, you can insert a rest
4512 with @code{r}. The rest will clear any previous alignment. For
4513 example, you can write
4525 Accidentals and plus signs can appear before or after the numbers,
4526 depending on the @code{figuredBassAlterationDirection} and
4527 @code{figuredBassPlusDirection}
4533 \set figuredBassAlterationDirection = #1
4535 \set figuredBassPlusDirection = #1
4537 \set figuredBassAlterationDirection = #-1
4543 Although the support for figured bass may superficially resemble chord
4544 support, it is much simpler. The @code{\figuremode} mode simply
4545 stores the numbers and @internalsref{FiguredBass} context prints them
4546 as entered. There is no conversion to pitches and no realizations of
4547 the bass are played in the MIDI file.
4549 Internally, the code produces markup texts. You can use any of the
4550 markup text properties to override formatting. For example, the
4551 vertical spacing of the figures may be set with @code{baseline-skip}.
4554 Figured bass can also be added to @code{Staff} contexts
4555 directly. In this case, their vertical position is adjusted
4558 @lilypond[ragged-right,fragment,quote]
4560 \new Staff = someUniqueName
4565 %% send to existing Staff.
4566 \context Staff = someUniqueName
4570 \set Staff.useBassFigureExtenders = ##t
4579 When using figured bass above the staff with extender lines and
4580 @code{implicitBassFigures} the lines may become swapped around.
4581 Maintaining order consistently will be impossible when multiple figures
4582 have overlapping extender lines. To avoid this problem, plese
4583 use @code{stacking-dir} on @code{BassFigureAlignment}.
4588 Program reference: @internalsref{NewBassFigure},
4589 @internalsref{BassFigureAlignment}, @internalsref{BassFigureLine},
4590 @internalsref{BassFigureBracket}, and
4591 @internalsref{BassFigureContinuation} objects and
4592 @internalsref{FiguredBass} context.
4596 @node Other instrument specific notation
4597 @section Other instrument specific notation
4599 This section includes extra information for writing for instruments.
4602 * Artificial harmonics (strings)::
4605 @node Artificial harmonics (strings)
4606 @subsection Artificial harmonics (strings)
4608 @cindex artificial harmonics
4610 Artificial harmonics are notated with a different notehead style. They
4611 are entered by marking the harmonic pitch with @code{\harmonic}.
4613 @lilypond[ragged-right,verbatim,quote,fragment,relative=1]