1 @c -*- coding: latin-1; mode: texinfo; -*-
2 @c This file is part of lilypond.tely
4 @c A menu is needed before every deeper *section nesting of @node's; run
5 @c M-x texinfo-all-menus-update
6 @c to automatically fill in these menus before saving changes
8 @node Instrument-specific notation
9 @chapter Instrument-specific notation
11 This chapter explains how to use notation for specific instruments.
20 * Other instrument specific notation::
28 Piano staves are two normal staves coupled with a brace. The staves
29 are largely independent, but sometimes voices can cross between the
30 two staves. The same notation is also used for harps and other key
31 instruments. The @internalsref{PianoStaff} is especially built to
32 handle this cross-staffing behavior. In this section we discuss the
33 @internalsref{PianoStaff} and some other pianistic peculiarities.
36 * Automatic staff changes::
37 * Manual staff switches::
39 * Staff switch lines::
46 Dynamics are not centered, but workarounds do exist. See the
47 ``piano centered dynamics'' template in @ref{Piano templates}.
49 @cindex cross staff stem
50 @cindex stem, cross staff
51 @cindex distance between staves in piano music
53 The distance between the two staves is the same for all systems in the
54 score. It is possible to override this per system, but it does require
55 an arcane command incantation. See
56 @inputfileref{input/@/test,piano@/-staff@/-distance@/.ly}.
59 @node Automatic staff changes
60 @subsection Automatic staff changes
61 @cindex Automatic staff changes
63 Voices can be made to switch automatically between the top and the bottom
64 staff. The syntax for this is
68 \autochange @dots{}@var{music}@dots{}
73 This will create two staves inside the current PianoStaff, called
74 @code{up} and @code{down}. The lower staff will be in bass clef by
77 A @code{\relative} section that is outside of @code{\autochange} has
78 no effect on the pitches of @var{music}, so, if necessary, put
79 @code{\relative} inside @code{\autochange} like
83 \autochange \relative @dots{} @dots{}
88 The autochanger switches on basis of the pitch (middle C is the turning
89 point), and it looks ahead skipping over rests to switch in
90 advance. Here is a practical example
92 @lilypond[quote,verbatim,raggedright]
94 \autochange \relative c'
103 In this manual: @ref{Manual staff switches}.
105 Program reference: @internalsref{AutoChangeMusic}.
111 The staff switches may not end up in optimal places. For high
112 quality output, staff switches should be specified manually.
115 @code{\autochange} cannot be inside @code{\times}.
118 @node Manual staff switches
119 @subsection Manual staff switches
121 @cindex manual staff switches
122 @cindex staff switch, manual
124 Voices can be switched between staves manually, using the command
126 \change Staff = @var{staffname} @var{music}
130 The string @var{staffname} is the name of the staff. It switches the
131 current voice from its current staff to the Staff called
132 @var{staffname}. Typically @var{staffname} is @code{"up"} or
133 @code{"down"}. The @context{Staff} referred to must already exist, so
134 usually the setup for a score will start with a setup of the staves,
138 \context Staff = up @{
139 \skip 1 * 10 % @emph{keep staff alive}
141 \context Staff = down @{
142 \skip 1 * 10 % @emph{idem}
148 and the @context{Voice} is inserted afterwards
151 \context Staff = down
152 \new Voice @{ @dots{} \change Staff = up @dots{} @}
160 Pianos have pedals that alter the way sound is produced. Generally, a
161 piano has three pedals, sustain, una corda, and sostenuto.
164 Piano pedal instruction can be expressed by attaching
165 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
166 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
169 @lilypond[quote,raggedright,fragment,verbatim]
170 c'4\sustainDown c'4\sustainUp
173 What is printed can be modified by setting @code{pedal@var{X}Strings},
174 where @var{X} is one of the pedal types: @code{Sustain},
175 @code{Sostenuto} or @code{UnaCorda}. Refer to
176 @internalsref{SustainPedal} in the program reference for more
179 Pedals can also be indicated by a sequence of brackets, by setting the
180 @code{pedalSustainStyle} property to bracket objects
182 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
183 \set Staff.pedalSustainStyle = #'bracket
185 b\sustainUp\sustainDown
186 b g \sustainUp a \sustainDown \bar "|."
189 A third style of pedal notation is a mixture of text and brackets,
190 obtained by setting the @code{pedalSustainStyle} property to
193 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
194 \set Staff.pedalSustainStyle = #'mixed
196 b\sustainUp\sustainDown
197 b g \sustainUp a \sustainDown \bar "|."
200 The default `*Ped.' style for sustain and damper pedals corresponds to
201 style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
204 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
205 c\sostenutoDown d e c, f g a\sostenutoUp
208 For fine-tuning the appearance of a pedal bracket, the properties
209 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
210 @code{PianoPedalBracket} objects (see
211 @internalsref{PianoPedalBracket} in the Program reference) can be
212 modified. For example, the bracket may be extended to the right edge
215 @lilypond[quote,raggedright,fragment,verbatim,relative=2]
216 \override Staff.PianoPedalBracket #'shorten-pair = #'(0 . -1.0)
217 c\sostenutoDown d e c, f g a\sostenutoUp
220 @node Staff switch lines
221 @subsection Staff switch lines
225 @cindex staff switching
228 @cindex @code{followVoice}
230 Whenever a voice switches to another staff, a line connecting the notes
231 can be printed automatically. This is switched on by setting
232 @code{followVoice} to true
234 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
237 \set followVoice = ##t
242 \context Staff=two { \clef bass \skip 1*2 }
248 Program reference: @internalsref{VoiceFollower}.
252 @cindex @code{\showStaffSwitch}
253 @code{\showStaffSwitch},
254 @cindex @code{\hideStaffSwitch}
255 @code{\hideStaffSwitch}.
258 @node Cross staff stems
259 @subsection Cross staff stems
261 Chords that cross staves may be produced by increasing the length
262 of the stem in the lower staff, so it reaches the stem in the upper
263 staff, or vice versa.
265 @lilypond[raggedright,verbatim,quote]
266 stemExtend = \once \override Stem #'length = #22
267 noFlag = \once \override Stem #'flag-style = #'no-flag
268 \context PianoStaff <<
270 \stemDown \stemExtend
288 * Introducing chord names::
290 * Printing chord names::
294 @c awkward name; awkward section name.
295 @c still, the Basic "chords" seems like a good name... :(
296 @node Introducing chord names
297 @subsection Introducing chord names
300 LilyPond has support for printing chord names. Chords may be entered
301 in musical chord notation, i.e., @code{< .. >}, but they can also be
302 entered by name. Internally, the chords are represented as a set of
303 pitches, so they can be transposed
306 @lilypond[quote,raggedright,verbatim,raggedright]
307 twoWays = \transpose c c' {
316 << \context ChordNames \twoWays
317 \context Voice \twoWays >>
320 This example also shows that the chord printing routines do not try to
321 be intelligent. The last chord (@code{f bes d}) is not interpreted as
326 @subsection Chords mode
329 In chord mode sets of pitches (chords) are entered with normal note
330 names. A chord is entered by the root, which is entered like a
333 @lilypond[quote,raggedright,fragment,verbatim]
334 \chordmode { es4. d8 c2 }
338 The mode is introduced by the keyword @code{\chordmode}.
343 Other chords may be entered by suffixing a colon and introducing a
344 modifier (which may include a number if desired)
345 @lilypond[quote,fragment,verbatim]
346 \chordmode { e1:m e1:7 e1:m7 }
348 The first number following the root is taken to be the `type' of the
349 chord, thirds are added to the root until it reaches the specified
351 @lilypond[quote,fragment,verbatim]
352 \chordmode { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 }
355 @cindex root of chord
356 @cindex additions, in chords
357 @cindex removals, in chords
359 More complex chords may also be constructed adding separate steps
360 to a chord. Additions are added after the number following
361 the colon and are separated by dots
362 @lilypond[quote,verbatim,fragment]
363 \chordmode { c:5.6 c:3.7.8 c:3.6.13 }
365 Chord steps can be altered by suffixing a @code{-} or @code{+} sign
367 @lilypond[quote,verbatim,fragment]
368 \chordmode { c:7+ c:5+.3- c:3-.5-.7- }
370 Removals are specified similarly and are introduced by a caret. They
371 must come after the additions
372 @lilypond[quote,verbatim,fragment]
373 \chordmode { c^3 c:7^5 c:9^3.5 }
376 Modifiers can be used to change pitches. The following modifiers are
381 The minor chord. This modifier lowers the 3rd and (if present) the 7th step.
384 The diminished chord. This modifier lowers the 3rd, 5th and (if present)
388 The augmented chord. This modifier raises the 5th step.
391 The major 7th chord. This modifier raises the 7th step if present.
394 The suspended 4th or 2nd. This modifier removes the 3rd
395 step. Append either @code{2} or @code{4} to add the 2nd or 4th step to
399 Modifiers can be mixed with additions
400 @lilypond[quote,verbatim,fragment]
401 \chordmode { c:sus4 c:7sus4 c:dim7 c:m6 }
404 @cindex modifiers, in chords.
411 Since an unaltered 11 does not sound good when combined with an
412 unaltered 3, the 11 is removed in this case (unless it is added
414 @lilypond[quote,raggedright,fragment,verbatim]
415 \chordmode { c:13 c:13.11 c:m13 }
420 An inversion (putting one pitch of the chord on the bottom), as well
421 as bass notes, can be specified by appending
422 @code{/}@var{pitch} to the chord
423 @lilypond[quote,raggedright,fragment,verbatim]
424 \chordmode { c1 c/g c/f }
428 A bass note can be added instead transposed out of the chord,
429 by using @code{/+}@var{pitch}.
431 @lilypond[quote,raggedright,fragment,verbatim]
432 \chordmode { c1 c/+g c/+f }
435 Chords is a mode similar to @code{\lyricmode}, etc. Most
436 of the commands continue to work, for example, @code{r} and
437 @code{\skip} can be used to insert rests and spaces, and property
438 commands may be used to change various settings.
444 Each step can only be present in a chord once. The following
445 simply produces the augmented chord, since @code{5+} is interpreted
448 @lilypond[quote,raggedright,verbatim,fragment]
449 \chordmode { c:5.5-.5+ }
453 @node Printing chord names
454 @subsection Printing chord names
456 @cindex printing chord names
460 For displaying printed chord names, use the @internalsref{ChordNames} context.
461 The chords may be entered either using the notation
462 described above, or directly using @code{<} and @code{>}
464 @lilypond[quote,verbatim,raggedright]
466 \chordmode {a1 b c} <d' f' a'> <e' g' b'>
469 \context ChordNames \harmonies
470 \context Staff \harmonies
474 You can make the chord changes stand out by setting
475 @internalsref{ChordNames}.@code{chordChanges} to true. This will only
476 display chord names when there is a change in the chords scheme and at
477 the start of a new line
479 @lilypond[quote,verbatim,raggedright]
480 harmonies = \chordmode {
481 c1:m c:m \break c:m c:m d
484 \context ChordNames {
485 \set chordChanges = ##t
487 \context Staff \transpose c c' \harmonies
491 The previous examples all show chords over a staff. This is not
492 necessary. Chords may also be printed separately. It may be necessary
493 to add @internalsref{Volta_engraver} and @internalsref{Bar_engraver}
496 @lilypond[raggedright,verbatim]
497 \new ChordNames \with {
498 \override BarLine #'bar-size = #4
499 voltaOnThisStaff = ##t
500 \consists Bar_engraver
501 \consists "Volta_engraver"
503 \repeat volta 2 \chordmode {
512 The default chord name layout is a system for Jazz music, proposed by
513 Klaus Ignatzek (see @ref{Literature list}). It can be tuned through the
517 @cindex @code{chordNameExceptions}
518 @item chordNameExceptions
519 This is a list that contains the chords that have special formatting.
521 The exceptions list should be encoded as
523 @{ <c f g bes>1 \markup @{ \super "7" "wahh" @} @}
526 To get this information into @code{chordNameExceptions} takes a little
527 manoeuvring. The following code transforms @code{chExceptionMusic}
528 (which is a sequential music) into a list of exceptions.
530 (sequential-music-to-chord-exceptions chExceptionMusic #t)
535 (sequential-music-to-chord-exceptions chExceptionMusic #t)
538 adds the new exceptions to the default ones, which are defined in
539 @file{ly/@/chord@/-modifier@/-init@/.ly}.
541 For an example of tuning this property, see also
542 @inputfileref{input/@/regression,chord@/-name@/-exceptions@/.ly}.
543 @cindex exceptions, chord names.
546 @cindex @code{majorSevenSymbol}
547 @item majorSevenSymbol
548 This property contains the markup object used for the 7th step, when
549 it is major. Predefined options are @code{whiteTriangleMarkup} and
550 @code{blackTriangleMarkup}. See
551 @inputfileref{input/@/regression,chord@/-name@/-major7@/.ly} for an example.
553 @cindex @code{chordNameSeparator}
554 @item chordNameSeparator
555 Different parts of a chord name are normally separated by a
556 slash. By setting @code{chordNameSeparator}, you can specify other
558 @lilypond[quote,raggedright,fragment,verbatim]
559 \context ChordNames \chordmode {
561 \set chordNameSeparator
562 = \markup { \typewriter "|" }
567 @cindex @code{chordRootNamer}
569 The root of a chord is usually printed as a letter with an optional
570 alteration. The transformation from pitch to letter is done by this
571 function. Special note names (for example, the German ``H'' for a
572 B-chord) can be produced by storing a new function in this property.
574 @cindex @code{chordNoteNamer}
576 The default is to print single pitch, e.g., the bass note, using the
577 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
578 to a specialized function to change this behavior. For example, the
579 base can be printed in lower case.
581 @cindex @code{chordPrefixSpacer}
582 @item chordPrefixSpacer
583 The ``m'' for minor chords is usually printed right after the root of
584 the chord. By setting @code{chordPrefixSpacer}, you can fix a spacer
585 between the root and ``m''. The spacer is not used when the root
590 The predefined variables @code{\germanChords},
591 @code{\semiGermanChords}, @code{\italianChords} and @code{\frenchChords}
592 set these variables. The effect is
595 @lilypondfile[raggedright]{chord-names-languages.ly}
597 There are also two other chord name schemes implemented: an alternate
598 Jazz chord notation, and a systematic scheme called Banter chords. The
599 alternate Jazz notation is also shown on the chart in @ref{Chord name
600 chart}. Turning on these styles is described in the input file
601 @inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
610 @cindex @code{\germanChords}
611 @code{\germanChords},
612 @cindex @code{\semiGermanChords}
613 @code{\semiGermanChords}.
614 @cindex @code{\italianChords}
615 @code{\italianChords}.
616 @cindex @code{\frenchChords}
617 @code{\frenchChords}.
624 Examples: @inputfileref{input/@/regression,chord@/-name@/-major7@/.ly},
625 @inputfileref{input/@/regression,chord@/-name@/-exceptions@/.ly},
626 @inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
629 Init files: @file{scm/@/chords@/-ignatzek@/.scm}, and
630 @file{scm/@/chord@/-entry@/.scm}.
635 Chord names are determined solely from the list of pitches. Chord
636 inversions are not identified, and neither are added bass notes. This
637 may result in strange chord names when chords are entered with the
638 @code{< .. >} syntax.
645 There are three different issues when printing vocal music
649 Song texts must be entered as text, not notes. For example, the
650 input@tie{}@code{d} should be interpreted as a one letter syllable, not the
654 Song texts must be printed as text, not as notes.
657 Song texts must be aligned with the notes of their melody.
660 The simplest solution for printing music uses the @code{\addlyrics}
661 function to solve all these problems at once. However, these
662 three functions can be controlled separately, which is necessary
663 for complex vocal music.
667 * Setting simple songs::
669 * Hyphens and extenders::
670 * The Lyrics context::
671 * Flexibility in alignment::
674 * Other vocal issues::
677 @node Setting simple songs
678 @subsection Setting simple songs
680 The easiest way to add lyrics to a melody is to append
683 \addlyrics @{ @var{the lyrics} @}
687 to a melody. Here is an example,
689 @lilypond[raggedright,verbatim,fragment,quote]
691 \relative { c2 e4 g2. }
692 \addlyrics { play the game }
695 More stanzas can be added by adding more
696 @code{\addlyrics} sections
698 @lilypond[raggedright,verbatim,fragment,quote]
700 \relative { c2 e4 g2. }
701 \addlyrics { play the game }
702 \addlyrics { speel het spel }
703 \addlyrics { joue le jeu }
706 @c TODO - this isn't such a great place for this note, but I can't
707 @c find a better place without rearranging a lot of lyric stuff.
708 @c It's yet another thing to look at post-3.0.
710 The @code{\addlyrics} command is actually just a convienient way
711 to write a more complicated LilyPond structure that sets up the
712 lyrics. You should use @code{\addlyrics} unless you need to do
713 fancy things, in which case you should investigate
714 @code{\lyricsto} or @code{\lyricmode}.
718 \addlyrics @{ LYRICS @}
725 \context Voice = blah @{ music @}
726 \lyricsto "blah" \new lyrics @{ LYRICS @}
731 @code{\addlyrics} cannot handle polyphony.
734 @node Entering lyrics
735 @subsection Entering lyrics
738 @cindex @code{\lyricmode}
741 Lyrics are entered in a special input mode. This mode is introduced
742 by the keyword @code{\lyricmode}, or by using @code{\addlyrics} or
743 @code{\lyricsto}. In this mode you can enter lyrics,
744 with punctuation and accents, and the input @code{d} is not parsed as
745 a pitch, but rather as a one letter syllable. Syllables are entered
746 like notes, but with pitches replaced by text. For example,
748 \lyricmode @{ Twin-4 kle4 twin- kle litt- le star2 @}
751 There is a difference between @code{\addlyrics} and
752 @code{\lyricmode}. @code{\addlyrics} and @code{\lyricsto}
753 ignore all durations and aligns syllables to notes; @code{\lyricmode}
754 uses the durations specified.
756 A word lyrics mode begins with an alphabetic character, and ends with
757 any space or digit. The following characters can be any character
758 that is not a digit or white space. One important consequence of this
759 is that a word can end with @code{@}}. The following example is
760 usually a mistake in the input file. The syllable includes a @code{@}}, so the
761 opening brace is not balanced
763 \lyricmode @{ twinkle@}
766 @cindex @code{\property}, in @code{\lyricmode}
768 Similarly, a period which follows an alphabetic sequence is included in
769 the resulting string. As a consequence, spaces must be inserted around
772 \override Score . LyricText #'font-shape = #'italic
776 @cindex spaces, in lyrics
777 @cindex quotes, in lyrics
779 Any @code{_} character that appears in an unquoted word is converted
780 to a space. This provides a mechanism for introducing spaces into words
781 without using quotes. Quoted words can also be used in Lyrics mode to
782 specify words that cannot be written with the above rules. The
783 following example incorporates double quotes
786 \lyricmode @{ He said: "\"Let" my peo ple "go\"" @}
789 This example is slightly academic, since it gives better looking
790 results using single quotes, @code{``} and @code{''}
792 \lyricmode @{ He said: ``Let my peo ple go'' @}
796 The full definition of a word start in Lyrics mode is somewhat more
799 A word in Lyrics mode begins with: an alphabetic character, @code{_},
800 @code{?}, @code{!}, @code{:}, @code{'}, the control characters @code{^A}
801 through @code{^F}, @code{^Q} through @code{^W}, @code{^Y}, @code{^^},
802 any 8-bit character with ASCII code over 127, or a two-character
803 combination of a backslash followed by one of @code{`}, @code{'},
804 @code{"}, or @code{^}.
810 Program reference: @internalsref{LyricText}.
814 The definition of lyrics mode is too complex.
816 @node Hyphens and extenders
817 @subsection Hyphens and extenders
821 Centered hyphens are entered as `@code{--}' between syllables.
822 The hyphen will have variable length depending on the space between
823 the syllables and it will be centered between the syllables.
828 When a lyric is sung over many notes (this is called a melisma), this is
829 indicated with a horizontal line centered between a syllable and the
830 next one. Such a line is called an extender line, and it is entered as
833 In tighly engraved music, hyphens can be removed. In some languages
834 (e.g. German and Hungarian), hyphens should not disappear, since
835 spelling depends on hyphenation. For that purpose, hyphens can be
836 forced to remain by overriding @code{minimum-length} of
837 the @code{LyricHyphen} grob.
839 @lilypond[quote,verbatim,raggedright]
842 \new Staff \relative c'' {
843 \time 1/4 c16 c c c c16 c c c c16 c c c
845 \lyricmode { \new Lyrics
847 \override SeparationItem #'padding = #0.0
848 % Otherwise lyrics are so far apart that hyphens don't disappear
851 An -- ti -- cons -- ti --
852 tu -- tion -- nel -- le --
853 \override LyricHyphen #'minimum-length = #0.7
854 \override LyricHyphen #'spacing-procedure =
855 #Hyphen_spanner::set_spacing_rods
856 men -- taire -- ment. ouf~!
864 \Staff \remove "Time_signature_engraver"
872 Program reference: @internalsref{LyricHyphen}, @internalsref{LyricExtender}.
876 @node The Lyrics context
877 @subsection The Lyrics context
880 Lyrics are printed by interpreting them in a @internalsref{Lyrics} context
882 \context Lyrics \lyricmode @dots{}
885 @cindex automatic syllable durations
886 @cindex @code{\lyricsto}
887 @cindex lyrics and melodies
889 This will place the lyrics according to the durations that were
890 entered. The lyrics can also be aligned under a given melody
891 automatically. In this case, it is no longer necessary to enter the
892 correct duration for each syllable. This is achieved by combining the
893 melody and the lyrics with the @code{\lyricsto} expression
895 \lyricsto @var{name} \new Lyrics @dots{}
898 This aligns the lyrics to the
899 notes of the @internalsref{Voice} context called @var{name}, which has
900 to exist. Therefore, normally the @code{Voice} is specified first, and
901 then the lyrics are specified with @code{\lyricsto}. The command
902 @code{\lyricsto} switches to @code{\lyricmode} mode automatically, so the
903 @code{\lyricmode} keyword may be omitted.
905 For different or more complex orderings, the best way is to setup the
906 hierarchy of staves and lyrics first, e.g.,
908 \context ChoirStaff <<
909 \context Lyrics = sopranoLyrics @{ s1 @}
910 \context Voice = soprano @{ @emph{music} @}
911 \context Lyrics = tenorLyrics @{ s1 @}
912 \context Voice = tenor @{ @emph{music} @}
915 and then combine the appropriate melodies and lyric lines
917 \lyricsto "soprano" \context Lyrics = sopranoLyrics
922 The final input would resemble
925 <<\context ChoirStaff << @emph{setup the music} >>
926 \lyricsto "soprano" @emph{etc}
927 \lyricsto "alto" @emph{etc}
933 The @code{\lyricsto} command detects melismata: it only puts one
934 syllable under a tied or slurred group of notes. If you want to force
935 an unslurred group of notes to be a melisma, insert @code{\melisma}
936 after the first note of the group, and @code{\melismaEnd} after the
939 @lilypond[quote,relative=2,raggedright,fragment,verbatim]
941 \context Voice = "lala" {
949 \lyricsto "lala" \new Lyrics {
955 In addition, notes are considered a melisma if they are manually
956 beamed, and automatic beaming (see @ref{Setting automatic beam
957 behavior}) is switched off.
963 The criteria for deciding melismata can
964 be tuned with the property @code{melismaBusyProperties}. See
965 @internalsref{Melisma_translator} in the program reference for more
970 Lyrics can also be entered without @code{\lyricsto}. In this case the
971 duration of each syllable must be entered explicitly, for example,
978 The alignment to a melody can be specified with the
979 @code{associatedVoice} property,
982 \set associatedVoice = #"lala"
986 The value of the property (here: @code{"lala"}) should be the name of
987 a @internalsref{Voice} context. Without this setting, extender lines
988 will not be formatted properly.
990 Here is an example demonstrating manual lyric durations,
992 @lilypond[relative=1,raggedright,verbatim,fragment,quote]
993 << \context Voice = melody {
997 \new Lyrics \lyricmode {
998 \set associatedVoice = #"melody"
1004 @cindex choral score
1006 A complete example of a SATB score setup is in section
1007 @ref{Vocal ensembles}.
1012 @code{\melisma}, @code{\melismaEnd}
1013 @cindex @code{\melismaEnd}
1014 @cindex @code{\melisma}
1018 Program reference: @internalsref{LyricCombineMusic},
1019 @internalsref{Lyrics}, @internalsref{Melisma_translator}.
1022 @inputfileref{input/@/regression,lyric@/-combine@/-new@/.ly}.
1023 @c TODO: make separate section for melismata
1027 Melismata are not detected automatically, and extender lines must be
1031 @c TODO: document \new Staff << Voice \lyricsto >> bug
1033 @node Flexibility in alignment
1034 @subsection Flexibility in alignment
1036 Often, different stanzas of one song are put to one melody in slightly
1037 differing ways. Such variations can still be captured with
1040 @subsubsection Lyrics to multiple notes of a melisma
1043 One possibility is that the text has a melisma in one stanza, but
1044 multiple syllables in another one. One solution is to make the faster
1045 voice ignore the melisma. This is done by setting
1046 @code{ignoreMelismata} in the Lyrics context.
1048 There has one tricky aspect. The setting for @code{ignoreMelismata}
1049 must be set one syllable @emph{before} the non-melismatic syllable
1050 in the text, as shown here,
1052 @lilypond[verbatim,raggedright,quote]
1054 \relative \context Voice = "lahlah" {
1055 \set Staff.autoBeaming = ##f
1061 \new Lyrics \lyricsto "lahlah" {
1064 \new Lyrics \lyricsto "lahlah" {
1065 \set ignoreMelismata = ##t % applies to "fas"
1067 \unset ignoreMelismata
1074 The @code{ignoreMelismata} applies to the syllable ``fas'', so it
1075 should be entered before ``go''.
1077 The reverse is also possible: making a lyric line slower than the
1078 standard. This can be achieved by insert @code{\skip}s into the
1079 lyrics. For every @code{\skip}, the text will be delayed another note.
1082 @lilypond[verbatim,raggedright,quote]
1083 \relative { c c g' }
1091 @subsection Switching the melody associated with a lyrics line
1095 More complex variations in text underlay are possible. It is possible
1096 to switch the melody for a line of lyrics during the text. This is
1097 done by setting the @code{associatedVoice} property. In the example
1099 @lilypond[raggedright,quote]
1101 \relative \context Voice = "lahlah" {
1102 \set Staff.autoBeaming = ##f
1105 \context Voice = alternative {
1108 % show associations clearly.
1109 \override NoteColumn #'force-hshift = #-3
1120 \new Lyrics \lyricsto "lahlah" {
1121 Ju -- ras -- sic Park
1123 \new Lyrics \lyricsto "lahlah" {
1124 % Tricky: need to set associatedVoice
1125 % one syllable too soon!
1126 \set associatedVoice = alternative % applies to "ran"
1130 \set associatedVoice = lahlah % applies to "rus"
1136 the text for the first stanza is set to a melody called ``lahlah'',
1139 \new Lyrics \lyricsto "lahlah" @{
1140 Ju -- ras -- sic Park
1145 The second stanza initially is set to the @code{lahlah} context, but
1146 for the syllable ``ran'', it switches to a different melody.
1147 This is achieved with
1149 \set associatedVoice = alternative
1153 Here, @code{alternative} is the name of the @code{Voice} context
1154 containing the triplet.
1156 Again, the command must be one syllable too early, before ``Ty'' in
1160 \new Lyrics \lyricsto "lahlah" @{
1161 \set associatedVoice = alternative % applies to "ran"
1165 \set associatedVoice = lahlah % applies to "rus"
1171 The underlay is switched back to the starting situation by assigning
1172 @code{lahlah} to @code{associatedVoice}.
1176 @subsection Specifying melismata within the lyrics
1178 It is also possible to define melismata entirely in the lyrics. This
1179 can be done by entering @code{_} for every note that is part of the
1182 @lilypond[relative=1,verbatim,fragment]
1183 { \set melismaBusyProperties = #'()
1184 c d( e) f f( e) e e }
1186 { Ky -- _ _ ri __ _ _ _ e }
1189 In this case, you can also have ties and slurs in the melody, if you
1190 set @code{melismaBusyProperties}, as is done in the example above.
1192 @lilypond[relative=1,verbatim,fragment]
1194 \set melismaBusyProperties = #'()
1198 { Ky -- _ _ ri __ _ _ _ e }
1203 @subsection More stanzas
1205 @cindex phrasing, in lyrics
1208 @cindex stanza number
1209 @cindex singer's names
1210 @cindex name of singer
1212 Stanza numbers can be added by setting @code{stanza}, e.g.,
1214 @lilypond[quote,raggedright,verbatim,relative=2,fragment]
1216 \time 3/4 g2 e4 a2 f4 g2.
1219 Hi, my name is Bert.
1222 Oh, che -- ri, je t'aime
1226 These numbers are put just before the start of first syllable.
1228 Names of singers can also be added. They are printed at the start of
1229 the line, just like instrument names. They are created by setting
1230 @code{vocalName}. A short version may be entered as @code{vocNam}.
1233 @lilypond[fragment,raggedright,quote,verbatim,relative=2]
1235 \time 3/4 g2 e4 a2 f4 g2.
1237 \set vocalName = "Bert "
1238 Hi, my name is Bert.
1240 \set vocalName = "Ernie "
1241 Oh, che -- ri, je t'aime
1245 You can display alternate (or divisi) lyrics by naming voice
1246 contexts and attaching lyrics to those specific contexts.
1248 @lilypond[verbatim,raggedright,quote]
1250 \context Voice = "melody" {
1255 \context Voice = splitpart { \voiceTwo c4 }
1260 \new Lyrics \lyricsto "melody" { we shall not o- ver- come }
1261 \new Lyrics \lyricsto "splitpart" { will }
1266 You can use this trick to display different lyrics for a repeated
1269 @lilypond[verbatim,raggedright,quote]
1271 \context Voice = melody \relative c' {
1273 \context Voice = verse \repeat volta 2 {c4 d e f | g1 | }
1275 \lyricsto melody \context Lyrics = mainlyrics \lyricmode {
1278 \lyricsto verse \context Lyrics = mainlyrics \lyricmode {
1280 \lyricsto verse \context Lyrics = repeatlyrics \lyricmode {
1281 dodo rere mimi fafa solsol }
1289 Program reference: @internalsref{LyricText}, @internalsref{StanzaNumber}, @internalsref{VocalName}.
1297 The term @emph{ambitus} denotes a range of pitches for a given voice
1298 in a part of music. It may also denote the pitch range that a musical
1299 instrument is capable of playing. Ambits are printed on vocal parts,
1300 so performers can easily determine it meets their capabilities.
1302 Ambits are denoted at the beginning of a piece near the initial clef.
1303 The range is graphically specified by two note heads that represent the
1304 minimum and maximum pitch. To print such ambits, add the
1305 @internalsref{Ambitus_engraver} to the @internalsref{Voice} context,
1312 \consists Ambitus_engraver
1317 This results in the following output
1319 @lilypond[quote,raggedright]
1323 \consists Ambitus_engraver
1327 \relative \new Staff {
1332 If you have multiple voices in a single staff and you want a single
1333 ambitus per staff rather than per each voice, add the
1334 @internalsref{Ambitus_engraver} to the @internalsref{Staff} context
1335 rather than to the @internalsref{Voice} context. Here is an example,
1337 @lilypond[verbatim,raggedright,quote]
1339 \consists "Ambitus_engraver"
1343 \remove "Ambitus_engraver"
1345 \override Ambitus #'X-offset-callbacks
1346 = #(list (lambda (grob axis) -1.0))
1351 \remove "Ambitus_engraver"
1360 This example uses one advanced feature,
1363 \override Ambitus #'X-offset-callbacks
1364 = #(list (lambda (grob axis) -1.0))
1368 This code moves the ambitus to the left. The same effect could have
1369 been achieved with @code{extra-offset}, but then the formatting system
1370 would not reserve space for the moved object.
1374 Program reference: @internalsref{Ambitus},
1375 @internalsref{AmbitusLine}, @internalsref{AmbitusNoteHead},
1376 @internalsref{AmbitusAccidental}.
1378 Examples: @inputfileref{input/@/regression,ambitus@/.ly}.
1382 There is no collision handling in the case of multiple per-voice
1386 @node Other vocal issues
1387 @subsection Other vocal issues
1390 yeah, I'm giving up somewhat by stuffing a bunch of things in
1391 here. But at least they're in the manual now; it's easier to
1392 move them around in the manual once they're already here.
1394 Besides, if users complain about everything stuffed in here, I
1395 can ask them for specific instructions about where to move these
1396 examples, and that might get them more involved in the docs. -gp
1399 ``Parlato'' is spoken without pitch but still with rhythm; it is
1400 notated by cross noteheads. This is demonstrated in
1401 @ref{Special noteheads}.
1404 @node Rhythmic music
1405 @section Rhythmic music
1407 Rhythmic music is primarily used for percussion and drum notation, but it can
1408 also be used to show the rhythms of melodies.
1411 * Showing melody rhythms::
1412 * Entering percussion::
1413 * Percussion staves::
1417 @node Showing melody rhythms
1418 @subsection Showing melody rhythms
1420 Sometimes you might want to show only the rhythm of a melody. This
1421 can be done with the rhythmic staff. All pitches of notes on such a
1422 staff are squashed, and the staff itself has a single line
1424 @lilypond[quote,raggedright,fragment,relative=1,verbatim]
1425 \context RhythmicStaff {
1427 c4 e8 f g2 | r4 g r2 | g1:32 | r1 |
1433 Program reference: @internalsref{RhythmicStaff}.
1435 Examples: @inputfileref{input/@/regression,rhythmic@/-staff@/.ly}.
1438 @node Entering percussion
1439 @subsection Entering percussion
1445 Percussion notes may be entered in @code{\drummode} mode, which is
1446 similar to the standard mode for entering notes. Each piece of
1447 percussion has a full name and an abbreviated name, and both can be used
1450 @lilypond[quote,raggedright,verbatim]
1452 hihat hh bassdrum bd
1456 The complete list of drum names is in the init file
1457 @file{ly/@/drumpitch@/-init@/.ly}.
1458 @c TODO: properly document this.
1462 Program reference: @internalsref{note-event}.
1464 @node Percussion staves
1465 @subsection Percussion staves
1469 A percussion part for more than one instrument typically uses a
1470 multiline staff where each position in the staff refers to one piece
1474 To typeset the music, the notes must be interpreted in a
1475 @internalsref{DrumStaff} and @internalsref{DrumVoice} contexts
1477 @lilypond[quote,raggedright,verbatim]
1478 up = \drummode { crashcymbal4 hihat8 halfopenhihat hh hh hh openhihat }
1479 down = \drummode { bassdrum4 snare8 bd r bd sn4 }
1481 \new DrumVoice { \voiceOne \up }
1482 \new DrumVoice { \voiceTwo \down }
1486 The above example shows verbose polyphonic notation. The short
1487 polyphonic notation, described in @ref{Polyphony}, can also be used if
1488 the @internalsref{DrumVoice}s are instantiated by hand first. For example,
1490 @lilypond[quote,raggedright,fragment,verbatim]
1492 \context DrumVoice = "1" { s1 *2 }
1493 \context DrumVoice = "2" { s1 *2 }
1497 { \repeat unfold 16 hh16 }
1506 There are also other layout possibilities. To use these, set the
1507 property @code{drumStyleTable} in context @internalsref{DrumVoice}.
1508 The following variables have been predefined
1512 This is the default. It typesets a typical drum kit on a five-line staff
1514 @lilypond[quote,linewidth=10.0\cm]
1516 cymc cyms cymr hh hhc hho hhho hhp
1517 cb hc bd sn ss tomh tommh tomml toml tomfh tomfl }
1519 cymc cyms cymr hh hhc hho hhho hhp \break
1520 cb hc bd sn ss tomh tommh tomml toml tomfh tomfl s16 }
1522 << \new DrumStaff \with {
1523 \remove Bar_engraver
1524 \remove Time_signature_engraver
1525 \override Stem #'transparent = ##t
1526 \override Stem #'Y-extent-callback = ##f
1527 minimumVerticalExtent = #'(-4.0 . 5.0)
1529 \context Lyrics \nam
1534 \override LyricText #'font-family = #'typewriter
1535 \override BarNumber #'transparent =##T
1541 The drum scheme supports six different toms. When there are fewer toms,
1542 simply select the toms that produce the desired result, i.e., to get toms
1543 on the three middle lines you use @code{tommh}, @code{tomml}, and
1546 @item timbales-style
1547 This typesets timbales on a two line staff
1549 @lilypond[quote,raggedright]
1550 nam = \lyricmode { timh ssh timl ssl cb }
1551 mus = \drummode { timh ssh timl ssl cb s16 }
1554 \context DrumStaff \with {
1555 \remove Bar_engraver
1556 \remove Time_signature_engraver
1557 \override Stem #'transparent = ##t
1558 \override Stem #'Y-extent-callback = ##f
1559 \override StaffSymbol #'line-count = #2
1560 \override StaffSymbol #'staff-space = #2
1561 minimumVerticalExtent = #'(-3.0 . 4.0)
1562 drumStyleTable = #timbales-style
1565 \override LyricText #'font-family = #'typewriter
1572 This typesets congas on a two line staff
1574 @lilypond[quote,raggedright]
1575 nam = \lyricmode { cgh cgho cghm ssh cgl cglo cglm ssl }
1576 mus = \drummode { cgh cgho cghm ssh cgl cglo cglm ssl s16 }
1579 \context DrumStaff \with {
1580 \remove Bar_engraver
1581 \remove Time_signature_engraver
1582 drumStyleTable = #congas-style
1583 \override StaffSymbol #'line-count = #2
1585 %% this sucks; it will lengthen stems.
1586 \override StaffSymbol #'staff-space = #2
1587 \override Stem #'transparent = ##t
1588 \override Stem #'Y-extent-callback = ##f
1591 \override LyricText #'font-family = #'typewriter
1598 This typesets bongos on a two line staff
1600 @lilypond[quote,raggedright]
1601 nam = \lyricmode { boh boho bohm ssh bol bolo bolm ssl }
1602 mus = \drummode { boh boho bohm ssh bol bolo bolm ssl s16 }
1605 \context DrumStaff\with {
1606 \remove Bar_engraver
1607 \remove Time_signature_engraver
1608 \override StaffSymbol #'line-count = #2
1609 drumStyleTable = #bongos-style
1611 %% this sucks; it will lengthen stems.
1612 \override StaffSymbol #'staff-space = #2
1613 \override Stem #'transparent = ##t
1614 \override Stem #'Y-extent-callback = ##f
1617 \override LyricText #'font-family = #'typewriter
1623 @item percussion-style
1624 To typeset all kinds of simple percussion on one line staves.
1626 @lilypond[quote,raggedright]
1627 nam = \lyricmode { tri trio trim gui guis guil cb cl tamb cab mar hc }
1628 mus = \drummode { tri trio trim gui guis guil cb cl tamb cab mar hc s16 }
1631 \context DrumStaff\with{
1632 \remove Bar_engraver
1633 drumStyleTable = #percussion-style
1634 \override StaffSymbol #'line-count = #1
1635 \remove Time_signature_engraver
1636 \override Stem #'transparent = ##t
1637 \override Stem #'Y-extent-callback = ##f
1640 \override LyricText #'font-family = #'typewriter
1647 If you do not like any of the predefined lists you can define your own
1648 list at the top of your file
1650 @lilypond[quote,raggedright,verbatim]
1652 (bassdrum default #f -1)
1653 (snare default #f 0)
1655 (pedalhihat xcircle "stopped" 2)
1656 (lowtom diamond #f 3)))
1657 up = \drummode { hh8 hh hh hh hhp4 hhp }
1658 down = \drummode { bd4 sn bd toml8 toml }
1661 \set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)
1662 \new DrumVoice { \voiceOne \up }
1663 \new DrumVoice { \voiceTwo \down }
1670 Init files: @file{ly/@/drumpitch@/-init@/.ly}.
1672 Program reference: @internalsref{DrumStaff}, @internalsref{DrumVoice}.
1676 Because general MIDI does not contain rim shots, the sidestick is used
1677 for this purpose instead.
1685 @cindex guitar tablature
1688 * String number indications::
1689 * Tablatures basic::
1690 * Non-guitar tablatures::
1692 * Other guitar issues::
1695 @node String number indications
1696 @subsection String number indications
1698 @cindex String numbers
1700 String numbers can be added to chords, by indicating the string number
1701 with @code{\}@var{number},
1703 @lilypond[relative,relative=1,raggedright,fragment]
1707 See also @inputfileref{input/regression,string-number.ly}.
1712 Program reference: @internalsref{StringNumber}.
1715 @node Tablatures basic
1716 @subsection Tablatures basic
1717 @cindex Tablatures basic
1719 Tablature notation is used for notating music for plucked string
1720 instruments. Pitches are not denoted with note heads, but by
1721 numbers indicating on which string and fret a note must be played. LilyPond
1722 offers limited support for tablature.
1724 The string number associated to a note is given as a backslash
1725 followed by a number, e.g., @code{c4\3} for a C quarter on the third
1726 string. By default, string 1 is the highest one, and the tuning
1727 defaults to the standard guitar tuning (with 6 strings). The notes
1728 are printed as tablature, by using @internalsref{TabStaff} and
1729 @internalsref{TabVoice} contexts
1731 @lilypond[quote,raggedright,fragment,verbatim]
1738 @cindex @code{minimumFret}
1741 When no string is specified, the first string that does not give a
1742 fret number less than @code{minimumFret} is selected. The default
1743 value for @code{minimumFret} is 0
1748 \set TabStaff.minimumFret = #8
1751 @lilypond[quote,raggedright]
1755 \set TabStaff.minimumFret = #8
1758 \context StaffGroup <<
1759 \context Staff { \clef "G_8" \frag }
1760 \context TabStaff { \frag }
1766 Program reference: @internalsref{TabStaff}, @internalsref{TabVoice}.
1770 Chords are not handled in a special way, and hence the automatic
1771 string selector may easily select the same string to two notes in a
1775 @node Non-guitar tablatures
1776 @subsection Non-guitar tablatures
1777 @cindex Non-guitar tablatures
1779 You can change the number of strings, by setting the number of lines
1780 in the @internalsref{TabStaff}.
1782 You can change the tuning of the strings. A string tuning is given as
1783 a Scheme list with one integer number for each string, the number
1784 being the pitch (measured in semitones relative to middle C) of an
1785 open string. The numbers specified for @code{stringTuning} are the
1786 numbers of semitones to subtract or add, starting the specified pitch
1787 by default middle C, in string order. In the next example,
1788 @code{stringTunings} is set for the pitches e, a, d, and g
1790 @lilypond[quote,raggedright,fragment,verbatim]
1791 \context TabStaff <<
1792 \set TabStaff.stringTunings = #'(-5 -10 -15 -20)
1794 a,4 c' a e' e c' a e'
1801 No guitar special effects have been implemented.
1805 Program reference: @internalsref{Tab_note_heads_engraver}.
1809 @subsection Fret diagrams
1810 @cindex fret diagrams
1811 @cindex chord diagrams
1813 Fret diagrams can be added to music as a markup to the desired note. The
1814 markup contains information about the desired fret diagram, as shown in the
1817 @lilypond[verbatim, raggedright, quote]
1819 d'^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
1821 fis'^\markup \override #'(size . 0.75) {
1822 \override #'(finger-code . below-string) {
1823 \fret-diagram-verbose #'((place-fret 6 2 1) (barre 6 1 2)
1824 (place-fret 5 4 3) (place-fret 4 4 4)
1825 (place-fret 3 3 2) (place-fret 2 2 1)
1830 c'^\markup \override #'(dot-radius . 0.35) {
1831 \override #'(finger-code . in-dot) {
1832 \override #'(dot-color . white) {
1833 \fret-diagram-terse #"x;3-1-(;5-2;5-3;5-4;3-1-);"
1842 There are three different fret-diagram markup interfaces: standard, terse,
1843 and verbose. The three interfaces produce equivalent markups, but have
1844 varying amounts of information in the markup string. Details about the
1845 markup interfaces are found at @ref{Overview of text markup commands}.
1847 You can set a number of graphical properties according to your preference.
1848 Details about the property interface to fret diagrams are found at
1849 @internalsref{fret-diagram-interface}.
1854 Examples: @inputfileref{input/@/test,fret@/-diagram@/.ly}
1857 @node Other guitar issues
1858 @subsection Other guitar issues
1860 This example demonstrates how to include guitar position and
1861 barring indications.
1863 @lilypond[quote,raggedright,fragment,verbatim,relative=0]
1867 \override TextSpanner #'edge-text = #'("XII " . "")
1869 b16 e16 g16 e16 b16 g16\stopTextSpan
1874 Stopped (X) note heads are used in guitar music to signal a place where the
1875 guitarist must play a certain note or chord, with its fingers just
1876 touching the strings instead of fully pressing them. This gives the sound a
1877 percussive noise-like sound that still maintains part of the original
1878 pitch. It is notated with cross noteheads; this is
1879 demonstrated in @ref{Special noteheads}.
1882 @node Ancient notation
1883 @section Ancient notation
1885 @cindex Vaticana, Editio
1886 @cindex Medicaea, Editio
1891 Support for ancient notation includes features for mensural notation
1892 and Gregorian Chant notation. There is also limited support for
1893 figured bass notation.
1895 Many graphical objects provide a @code{style} property, see
1898 @ref{Ancient note heads},
1900 @ref{Ancient accidentals},
1902 @ref{Ancient rests},
1904 @ref{Ancient clefs},
1906 @ref{Ancient flags},
1908 @ref{Ancient time signatures}.
1911 By manipulating such a grob property, the typographical appearance of
1912 the affected graphical objects can be accommodated for a specific
1913 notation flavor without the need for introducing any new notational
1916 In addition to the standard articulation signs described in section
1917 @ref{Articulations}, specific articulation signs for ancient notation
1922 @ref{Ancient articulations}
1925 Other aspects of ancient notation can not that easily be expressed
1926 in terms of just changing a style property of a graphical object or
1927 adding articulation signs. Some notational concepts are introduced
1928 specifically for ancient notation,
1939 If this all is too much of documentation for you, and you just want to
1940 dive into typesetting without worrying too much about the details on
1941 how to customize a context, you may have a look at the predefined
1942 contexts. Use them to set up predefined style-specific voice and
1943 staff contexts, and directly go ahead with the note entry,
1947 @ref{Gregorian Chant contexts},
1949 @ref{Mensural contexts}.
1952 There is limited support for figured bass notation which came
1953 up during the baroque period.
1960 Here are all suptopics at a glance:
1963 * Ancient note heads::
1964 * Ancient accidentals::
1968 * Ancient time signatures::
1969 * Ancient articulations::
1973 * Gregorian Chant contexts::
1974 * Mensural contexts::
1975 * Musica ficta accidentals::
1981 @node Ancient note heads
1982 @subsection Ancient note heads
1987 For ancient notation, a note head style other than the @code{default}
1988 style may be chosen. This is accomplished by setting the @code{style}
1989 property of the @internalsref{NoteHead} object to @code{baroque},
1990 @code{neomensural}, @code{mensural} or @code{petrucci}. The
1991 @code{baroque} style differs from the @code{default} style only in
1992 using a square shape for @code{\breve} note heads. The
1993 @code{neomensural} style differs from the @code{baroque} style in that
1994 it uses rhomboidal heads for whole notes and all smaller durations.
1995 Stems are centered on the note heads. This style is particularly
1996 useful when transcribing mensural music, e.g., for the incipit. The
1997 @code{mensural} style produces note heads that mimic the look of note
1998 heads in historic printings of the 16th century. Finally, the
1999 @code{petrucci} style also mimicks historic printings, but uses bigger
2002 The following example demonstrates the @code{neomensural} style
2004 @lilypond[quote,fragment,raggedright,verbatim]
2005 \set Score.skipBars = ##t
2006 \override NoteHead #'style = #'neomensural
2007 a'\longa a'\breve a'1 a'2 a'4 a'8 a'16
2010 When typesetting a piece in Gregorian Chant notation, the
2011 @internalsref{Gregorian_ligature_engraver} will automatically select
2012 the proper note heads, so there is no need to explicitly set the
2013 note head style. Still, the note head style can be set, e.g., to
2014 @code{vaticana_punctum} to produce punctum neumes. Similarly, a
2015 @internalsref{Mensural_ligature_engraver} is used to automatically
2016 assemble mensural ligatures. See @ref{Ligatures} for how ligature
2021 Examples: @inputfileref{input/@/regression,note@/-head@/-style@/.ly} gives an
2022 overview over all available note head styles.
2025 @node Ancient accidentals
2026 @subsection Ancient accidentals
2031 Use the @code{style} property of grob @internalsref{Accidental} to
2032 select ancient accidentals. Supported styles are
2033 @code{mensural}, @code{vaticana}, @code{hufnagel}, and @code{medicaea}.
2035 @lilypond[quote,raggedright,staffsize=26]
2042 \line { " " \musicglyph #"accidentals.vaticana-1"
2043 " " \musicglyph #"accidentals.vaticana0" }
2047 \line { " " \musicglyph #"accidentals.medicaea-1" }
2051 \line { " " \musicglyph #"accidentals.hufnagel-1" }
2055 \line { " " \musicglyph #"accidentals.mensural-1"
2056 " " \musicglyph #"accidentals.mensural1" }
2062 \context { \Score \remove "Bar_number_engraver" }
2064 \remove "Clef_engraver"
2065 \remove "Key_engraver"
2066 \remove "Time_signature_engraver"
2067 \remove "Staff_symbol_engraver"
2068 minimumVerticalExtent = ##f
2074 As shown, not all accidentals are supported by each style. When
2075 trying to access an unsupported accidental, LilyPond will switch to a
2076 different style, as demonstrated in
2077 @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
2079 Similarly to local accidentals, the style of the key signature can be
2080 controlled by the @code{style} property of the
2081 @internalsref{KeySignature} grob.
2085 In this manual: @ref{Pitches}, @ref{Cautionary accidentals} and
2086 @ref{Automatic accidentals} give a general introduction of the use of
2087 accidentals. @ref{Key signature} gives a general introduction of
2088 the use of key signatures.
2090 Program reference: @internalsref{KeySignature}.
2092 Examples: @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
2095 @subsection Ancient rests
2097 @cindex rests, ancient
2100 Use the @code{style} property of grob @internalsref{Rest} to select
2101 ancient rests. Supported styles are @code{classical},
2102 @code{neomensural}, and @code{mensural}. @code{classical} differs
2103 from the @code{default} style only in that the quarter rest looks like
2104 a horizontally mirrored 8th rest. The @code{neomensural} style suits
2105 well for, e.g., the incipit of a transcribed mensural piece of music.
2106 The @code{mensural} style finally mimics the appearance of rests as
2107 in historic prints of the 16th century.
2109 The following example demonstrates the @code{neomensural} style
2111 @lilypond[quote,fragment,raggedright,verbatim]
2112 \set Score.skipBars = ##t
2113 \override Rest #'style = #'neomensural
2114 r\longa r\breve r1 r2 r4 r8 r16
2117 There are no 32th and 64th rests specifically for the mensural or
2118 neo-mensural style. Instead, the rests from the default style will be
2119 taken. See @inputfileref{input/@/test,rests@/.ly} for a chart of all
2122 There are no rests in Gregorian Chant notation; instead, it uses
2127 In this manual: @ref{Rests} gives a general introduction into the use of rests.
2131 @subsection Ancient clefs
2136 LilyPond supports a variety of clefs, many of them ancient.
2138 The following table shows all ancient clefs that are supported via the
2139 @code{\clef} command. Some of the clefs use the same glyph, but
2140 differ only with respect to the line they are printed on. In such
2141 cases, a trailing number in the name is used to enumerate these clefs.
2142 Still, you can manually force a clef glyph to be typeset on an
2143 arbitrary line, as described in @ref{Clef}. The note printed to the
2144 right side of each clef in the example column denotes the @code{c'}
2145 with respect to that clef.
2147 @multitable @columnfractions .4 .4 .2
2156 modern style mensural C clef
2158 @code{neomensural-c1}, @code{neomensural-c2},@*
2159 @code{neomensural-c3}, @code{neomensural-c4}
2161 @lilypond[fragment,relative=1,notime]
2162 \clef "neomensural-c2" c
2166 petrucci style mensural C clefs, for use on different staff lines
2167 (the examples show the 2nd staff line C clef)
2169 @code{petrucci-c1}, @code{petrucci-c2},@*
2170 @code{petrucci-c3}, @code{petrucci-c4},@*
2173 @lilypond[fragment,relative=1,notime]
2175 \override NoteHead #'style = #'mensural
2180 petrucci style mensural F clef
2184 @lilypond[fragment,relative=1,notime]
2186 \override NoteHead #'style = #'mensural
2191 petrucci style mensural G clef
2195 @lilypond[fragment,relative=1,notime]
2197 \override NoteHead #'style = #'mensural
2202 historic style mensural C clef
2204 @code{mensural-c1}, @code{mensural-c2},@*
2205 @code{mensural-c3}, @code{mensural-c4}
2207 @lilypond[fragment,relative=1,notime]
2209 \override NoteHead #'style = #'mensural
2214 historic style mensural F clef
2218 @lilypond[fragment,relative=1,notime]
2220 \override NoteHead #'style = #'mensural
2225 historic style mensural G clef
2229 @lilypond[fragment,relative=1,notime]
2231 \override NoteHead #'style = #'mensural
2236 Editio Vaticana style do clef
2238 @code{vaticana-do1}, @code{vaticana-do2},@*
2241 @lilypond[fragment,relative=1,notime]
2242 \override Staff.StaffSymbol #'line-count = #4
2243 \override Staff.StaffSymbol #'color = #red
2244 \override Staff.LedgerLineSpanner #'color = #red
2245 \override Voice.Stem #'transparent = ##t
2246 \override NoteHead #'style = #'vaticana.punctum
2247 \clef "vaticana-do2"
2252 Editio Vaticana style fa clef
2254 @code{vaticana-fa1}, @code{vaticana-fa2}
2256 @lilypond[fragment,relative=1,notime]
2257 \override Staff.StaffSymbol #'line-count = #4
2258 \override Staff.StaffSymbol #'color = #red
2259 \override Staff.LedgerLineSpanner #'color = #red
2260 \override Voice.Stem #'transparent = ##t
2261 \override NoteHead #'style = #'vaticana.punctum
2262 \clef "vaticana-fa2"
2267 Editio Medicaea style do clef
2269 @code{medicaea-do1}, @code{medicaea-do2},@*
2272 @lilypond[fragment,relative=1,notime]
2273 \override Staff.StaffSymbol #'line-count = #4
2274 \override Staff.StaffSymbol #'color = #red
2275 \override Staff.LedgerLineSpanner #'color = #red
2276 \override Voice.Stem #'transparent = ##t
2277 \override NoteHead #'style = #'medicaea.punctum
2278 \clef "medicaea-do2"
2283 Editio Medicaea style fa clef
2285 @code{medicaea-fa1}, @code{medicaea-fa2}
2287 @lilypond[fragment,relative=1,notime]
2288 \override Staff.StaffSymbol #'line-count = #4
2289 \override Staff.StaffSymbol #'color = #red
2290 \override Staff.LedgerLineSpanner #'color = #red
2291 \override Voice.Stem #'transparent = ##t
2292 \override NoteHead #'style = #'medicaea.punctum
2293 \clef "medicaea-fa2"
2298 historic style hufnagel do clef
2300 @code{hufnagel-do1}, @code{hufnagel-do2},@*
2303 @lilypond[fragment,relative=1,notime]
2304 \override Staff.StaffSymbol #'line-count = #4
2305 \override Staff.StaffSymbol #'color = #red
2306 \override Staff.LedgerLineSpanner #'color = #red
2307 \override Voice.Stem #'transparent = ##t
2308 \override NoteHead #'style = #'hufnagel.punctum
2309 \clef "hufnagel-do2"
2314 historic style hufnagel fa clef
2316 @code{hufnagel-fa1}, @code{hufnagel-fa2}
2318 @lilypond[fragment,relative=1,notime]
2319 \override Staff.StaffSymbol #'line-count = #4
2320 \override Staff.StaffSymbol #'color = #red
2321 \override Staff.LedgerLineSpanner #'color = #red
2322 \override Voice.Stem #'transparent = ##t
2323 \override NoteHead #'style = #'hufnagel.punctum
2324 \clef "hufnagel-fa2"
2329 historic style hufnagel combined do/fa clef
2331 @code{hufnagel-do-fa}
2333 @lilypond[fragment,relative=1,notime]
2334 \override Staff.StaffSymbol #'color = #red
2335 \override Staff.LedgerLineSpanner #'color = #red
2336 \override Voice.Stem #'transparent = ##t
2337 \override NoteHead #'style = #'hufnagel.punctum
2338 \clef "hufnagel-do-fa"
2345 @emph{Modern style} means ``as is typeset in contemporary editions of
2346 transcribed mensural music''.
2348 @emph{Petrucci style} means ``inspired by printings published by the
2349 famous engraver Petrucci (1466-1539)''.
2351 @emph{Historic style} means ``as was typeset or written in historic
2352 editions (other than those of Petrucci)''.
2354 @emph{Editio XXX style} means ``as is/was printed in Editio XXX''.
2356 Petrucci used C clefs with differently balanced left-side vertical
2357 beams, depending on which staff line it is printed.
2361 In this manual: see @ref{Clef}.
2365 The mensural g clef is mapped to the Petrucci g clef.
2370 @subsection Ancient flags
2375 Use the @code{flag-style} property of grob @internalsref{Stem} to
2376 select ancient flags. Besides the @code{default} flag style,
2377 only the @code{mensural} style is supported
2379 @lilypond[quote,fragment,raggedright,verbatim]
2380 \override Stem #'flag-style = #'mensural
2381 \override Stem #'thickness = #1.0
2382 \override NoteHead #'style = #'mensural
2384 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
2385 c''8 d''8 e''8 f''8 c''16 d''16 e''16 f''16 c''32 d''32 e''32 f''32
2388 Note that the innermost flare of each mensural flag always is
2389 vertically aligned with a staff line.
2391 There is no particular flag style for neo-mensural notation. Hence,
2392 when typesetting the incipit of a transcribed piece of mensural
2393 music, the default flag style should be used. There are no flags in
2394 Gregorian Chant notation.
2398 The attachment of ancient flags to stems is slightly off due to a
2399 change in early 2.3.x.
2401 Vertically aligning each flag with a staff line assumes that stems
2402 always end either exactly on or exactly in the middle between two
2403 staff lines. This may not always be true when using advanced layout
2404 features of classical notation (which however are typically out of
2405 scope for mensural notation).
2407 @node Ancient time signatures
2408 @subsection Ancient time signatures
2410 @cindex time signatures
2413 There is limited support for mensural time signatures. The
2414 glyphs are hard-wired to particular time fractions. In other words,
2415 to get a particular mensural signature glyph with the @code{\time n/m}
2416 command, @code{n} and @code{m} have to be chosen according to the
2419 @lilypond[quote,raggedright]
2424 \remove Staff_symbol_engraver
2425 \remove Clef_engraver
2426 \remove Time_signature_engraver
2430 \set Score.timing = ##f
2431 \set Score.barAlways = ##t
2432 s_\markup { "\\time 4/4" }^\markup { " " \musicglyph #"timesig.neomensural44" }
2434 s_\markup { "\\time 2/2" }^\markup { " " \musicglyph #"timesig.neomensural22" }
2436 s_\markup { "\\time 6/4" }^\markup { " " \musicglyph #"timesig.neomensural64" }
2438 s_\markup { "\\time 6/8" }^\markup { " " \musicglyph #"timesig.neomensural68" }
2440 s_\markup { "\\time 3/2" }^\markup { " " \musicglyph #"timesig.neomensural32" }
2442 s_\markup { "\\time 3/4" }^\markup { " " \musicglyph #"timesig.neomensural34" }
2444 s_\markup { "\\time 9/4" }^\markup { " " \musicglyph #"timesig.neomensural94" }
2446 s_\markup { "\\time 9/8" }^\markup { " " \musicglyph #"timesig.neomensural98" }
2448 s_\markup { "\\time 4/8" }^\markup { " " \musicglyph #"timesig.neomensural48" }
2450 s_\markup { "\\time 2/4" }^\markup { " " \musicglyph #"timesig.neomensural24" }
2454 Use the @code{style} property of grob @internalsref{TimeSignature} to
2455 select ancient time signatures. Supported styles are
2456 @code{neomensural} and @code{mensural}. The above table uses the
2457 @code{neomensural} style. This style is appropriate for the
2458 incipit of transcriptions of mensural pieces. The @code{mensural}
2459 style mimics the look of historical printings of the 16th century.
2461 The following examples show the differences in style,
2463 @lilypond[raggedright,fragment,relative=1,quote]
2468 c1^\markup { \hspace #-2.0 \typewriter default }
2470 \override Staff.TimeSignature #'style = #'numbered
2472 c1^\markup { \hspace #-2.0 \typewriter numbered }
2474 \override Staff.TimeSignature #'style = #'mensural
2476 c1^\markup { \hspace #-2.0 \typewriter mensural }
2478 \override Staff.TimeSignature #'style = #'neomensural
2480 c1^\markup { \hspace #-2.0 \typewriter neomensural }
2481 \override Staff.TimeSignature #'style = #'single-digit
2483 c1^\markup { \hspace #-2.0 \typewriter single-digit }
2489 This manual: @ref{Time signature} gives a general introduction to
2490 the use of time signatures.
2494 Ratios of note durations do not change with the time signature. For
2495 example, the ratio of 1 brevis = 3 semibrevis (tempus perfectum) must
2496 be made by hand, by setting
2499 breveTP = #(ly:make-duration -1 0 3 2)
2505 This sets @code{breveTP} to 3/2 times 2 = 3 times a whole note.
2507 The @code{old6/8alt} symbol (an alternate symbol for 6/8) is not
2508 addressable with @code{\time}. Use a @code{\markup} instead
2510 @node Ancient articulations
2511 @subsection Ancient articulations
2513 @cindex articulations
2515 In addition to the standard articulation signs described in section
2516 @ref{Articulations}, articulation signs for ancient notation are
2517 provided. These are specifically designed for use with notation in
2518 Editio Vaticana style.
2520 @lilypond[quote,raggedright,verbatim]
2521 \include "gregorian-init.ly"
2523 \context VaticanaVoice {
2524 \override Staff.StaffSymbol #'color = #red
2525 \override Staff.LedgerLineSpanner #'color = #red
2526 \override TextScript #'font-family = #'typewriter
2527 \override TextScript #'font-shape = #'upright
2528 \override Script #'padding = #-0.1
2530 a4\circulus_"circulus" s1
2531 a4\semicirculus_"semicirculus" s1 s
2532 a4\accentus_"accentus" s1
2533 \[ a4_"episem" \episemInitium \pes b \flexa a \episemFinis \]
2540 Some articulations are vertically placed too closely to the
2541 correpsonding note heads.
2544 @subsection Custodes
2549 A @emph{custos} (plural: @emph{custodes}; Latin word for `guard') is a
2550 symbol that appears at the end of a staff. It anticipates the pitch
2551 of the first note(s) of the following line thus helping the performer
2552 to manage line breaks during performance.
2554 Custodes were frequently used in music notation until the 17th
2555 century. Nowadays, they have survived only in a few particular forms
2556 of musical notation such as contemporary editions of Gregorian chant
2557 like the @emph{editio vaticana}. There are different custos glyphs
2558 used in different flavors of notational style.
2560 For typesetting custodes, just put a @internalsref{Custos_engraver} into the
2561 @internalsref{Staff} context when declaring the @code{\layout} block,
2562 as shown in the following example
2568 \consists Custos_engraver
2569 Custos \override #'style = #'mensural
2574 The result looks like this
2576 @lilypond[quote,raggedright]
2580 \override Staff.Custos #'style = #'mensural
2585 \context { \Staff \consists Custos_engraver }
2590 The custos glyph is selected by the @code{style} property. The styles
2591 supported are @code{vaticana}, @code{medicaea}, @code{hufnagel}, and
2592 @code{mensural}. They are demonstrated in the following fragment
2594 @lilypond[quote,raggedright,fragment]
2595 \new Lyrics \lyricmode {
2597 \typewriter "vaticana"
2598 \line { " " \musicglyph #"custodes.vaticana.u0" }
2601 \typewriter "medicaea"
2602 \line { " " \musicglyph #"custodes.medicaea.u0" }
2605 \typewriter "hufnagel"
2606 \line { " " \musicglyph #"custodes.hufnagel.u0" }
2609 \typewriter "mensural"
2610 \line { " " \musicglyph #"custodes.mensural.u0" }
2617 Program reference: @internalsref{Custos}.
2619 Examples: @inputfileref{input/@/regression,custos@/.ly}.
2623 @subsection Divisiones
2629 A @emph{divisio} (plural: @emph{divisiones}; Latin word for
2630 `division') is a staff context symbol that is used to structure
2631 Gregorian music into phrases and sections. The musical meaning of
2632 @emph{divisio minima}, @emph{divisio maior}, and @emph{divisio maxima}
2633 can be characterized as short, medium, and long pause, somewhat like
2634 the breathmarks from @ref{Breath marks}. The @emph{finalis} sign not
2635 only marks the end of a chant, but is also frequently used within a
2636 single antiphonal/responsorial chant to mark the end of each section.
2639 To use divisiones, include the file @file{gregorian@/-init@/.ly}. It
2640 contains definitions that you can apply by just inserting
2641 @code{\divisioMinima}, @code{\divisioMaior}, @code{\divisioMaxima},
2642 and @code{\finalis} at proper places in the input. Some editions use
2643 @emph{virgula} or @emph{caesura} instead of divisio minima.
2644 Therefore, @file{gregorian@/-init@/.ly} also defines @code{\virgula} and
2647 @lilypondfile[quote,raggedright]{divisiones.ly}
2651 @cindex @code{\virgula}
2653 @cindex @code{\caesura}
2655 @cindex @code{\divisioMinima}
2656 @code{\divisioMinima},
2657 @cindex @code{\divisioMaior}
2658 @code{\divisioMaior},
2659 @cindex @code{\divisioMaxima}
2660 @code{\divisioMaxima},
2661 @cindex @code{\finalis}
2666 In this manual: @ref{Breath marks}.
2668 Program reference: @internalsref{BreathingSign}.
2670 Examples: @inputfileref{input/@/test,divisiones@/.ly}.
2673 @subsection Ligatures
2677 @c TODO: Should double check if I recalled things correctly when I wrote
2678 @c down the following paragraph by heart.
2680 A ligature is a graphical symbol that represents at least two distinct
2681 notes. Ligatures originally appeared in the manuscripts of Gregorian
2682 chant notation to denote ascending or descending sequences of notes.
2684 Ligatures are entered by enclosing them in @code{\[} and @code{\]}.
2685 Some ligature styles may need additional input syntax specific for
2686 this particular type of ligature. By default, the
2687 @internalsref{LigatureBracket} engraver just puts a square bracket
2690 @lilypond[quote,raggedright,verbatim]
2698 To select a specific style of ligatures, a proper ligature engraver
2699 has to be added to the @internalsref{Voice} context, as explained in
2700 the following subsections. Only white mensural ligatures
2701 are supported with certain limitations.
2707 Ligatures need special spacing that has not yet been implemented. As
2708 a result, there is too much space between ligatures most of the time,
2709 and line breaking often is unsatisfactory. Also, lyrics do not
2710 correctly align with ligatures.
2712 Accidentals must not be printed within a ligature, but instead need to
2713 be collected and printed in front of it.
2715 Augmentum dots within ligatures are not handled correctly.
2717 The syntax still uses the deprecated infix style @code{\[ music expr
2718 \]}. For consistency reasons, it will eventually be changed to
2719 postfix style @code{note\[ ... note\]}. Alternatively, the file
2720 @file{gregorian@/-init@/.ly} can be included; it provides a scheme
2723 \ligature @var{music expr}
2725 with the same effect and is believed to be stable.
2728 * White mensural ligatures::
2729 * Gregorian square neumes ligatures::
2732 @node White mensural ligatures
2733 @subsubsection White mensural ligatures
2735 @cindex Mensural ligatures
2736 @cindex White mensural ligatures
2738 There is limited support for white mensural ligatures.
2740 To engrave white mensural ligatures, in the layout block put the
2741 @internalsref{Mensural_ligature_engraver} into the
2742 @internalsref{Voice} context, and remove the
2743 @internalsref{Ligature_bracket_engraver}, like this
2749 \remove Ligature_bracket_engraver
2750 \consists Mensural_ligature_engraver
2755 There is no additional input language to describe the shape of a
2756 white mensural ligature. The shape is rather determined solely from
2757 the pitch and duration of the enclosed notes. While this approach may
2758 take a new user a while to get accustomed to, it has the great advantage
2759 that the full musical information of the ligature is known internally.
2760 This is not only required for correct MIDI output, but also allows for
2761 automatic transcription of the ligatures.
2766 \set Score.timing = ##f
2767 \set Score.defaultBarType = "empty"
2768 \override NoteHead #'style = #'neomensural
2769 \override Staff.TimeSignature #'style = #'neomensural
2773 \[ d\longa c\breve f e d \]
2775 \[ c'\maxima d'\longa \]
2779 @lilypond[quote,raggedright]
2782 \set Score.timing = ##f
2783 \set Score.defaultBarType = "empty"
2784 \override NoteHead #'style = #'neomensural
2785 \override Staff.TimeSignature #'style = #'neomensural
2789 \[ d\longa c\breve f e d \]
2791 \[ c'\maxima d'\longa \]
2798 \remove Ligature_bracket_engraver
2799 \consists Mensural_ligature_engraver
2805 Without replacing @internalsref{Ligature_bracket_engraver} with
2806 @internalsref{Mensural_ligature_engraver}, the same music transcribes
2809 @lilypond[quote,raggedright]
2811 \set Score.timing = ##f
2812 \set Score.defaultBarType = "empty"
2813 \override NoteHead #'style = #'neomensural
2814 \override Staff.TimeSignature #'style = #'neomensural
2818 \[ d\longa c\breve f e d \]
2820 \[ c'\maxima d'\longa \]
2828 The invisible rests (@code{s4}) in the example are used to compensate
2829 for the poor horizontal spacing.
2831 @node Gregorian square neumes ligatures
2832 @subsubsection Gregorian square neumes ligatures
2834 @cindex Square neumes ligatures
2835 @cindex Gregorian square neumes ligatures
2837 There is limited support for Gregorian square neumes notation
2838 (following the style of the Editio Vaticana). Core ligatures can
2839 already be typeset, but essential issues for serious typesetting are
2840 still lacking, such as (among others) horizontal alignment of multiple
2841 ligatures, lyrics alignment and proper handling of accidentals.
2844 The following table contains the extended neumes table of the 2nd
2845 volume of the Antiphonale Romanum (@emph{Liber Hymnarius}), published
2846 1983 by the monks of Solesmes.
2848 @multitable @columnfractions .4 .2 .2 .2
2865 @c TODO: \layout block is identical in all of the below examples.
2866 @c Therefore, it should somehow be included rather than duplicated all
2869 @c why not make identifiers in ly/engraver-init.ly? --hwn
2871 @c Because it's just used to typeset plain notes without
2872 @c a staff for demonstration purposes rather than something
2873 @c special of Gregorian chant notation. --jr
2878 @lilypond[staffsize=26,linewidth=1.5\cm]
2879 \include "gregorian-init.ly"
2884 \noBreak s^\markup {"a"} \noBreak
2886 % Punctum Inclinatum
2888 \noBreak s^\markup {"b"}
2890 \layout { \neumeDemoLayout }}
2893 @lilypond[staffsize=26,linewidth=2.5\cm]
2894 \include "gregorian-init.ly"
2897 % Punctum Auctum Ascendens
2898 \[ \auctum \ascendens b \]
2899 \noBreak s^\markup {"c"} \noBreak
2901 % Punctum Auctum Descendens
2902 \[ \auctum \descendens b \]
2903 \noBreak s^\markup {"d"} \noBreak
2905 % Punctum Inclinatum Auctum
2906 \[ \inclinatum \auctum b \]
2907 \noBreak s^\markup {"e"}
2909 \layout { \neumeDemoLayout }}
2912 @lilypond[staffsize=26,linewidth=1.0\cm]
2913 \include "gregorian-init.ly"
2916 % Punctum Inclinatum Parvum
2917 \[ \inclinatum \deminutum b \]
2918 \noBreak s^\markup {"f"}
2920 \layout { \neumeDemoLayout }}
2926 @lilypond[staffsize=26,linewidth=1.0\cm]
2927 \include "gregorian-init.ly"
2932 \noBreak s^\markup {"g"}
2934 \layout { \neumeDemoLayout }}
2940 @code{3. Apostropha vel Stropha}
2942 @lilypond[staffsize=26,linewidth=1.0\cm]
2943 \include "gregorian-init.ly"
2948 \noBreak s^\markup {"h"}
2950 \layout { \neumeDemoLayout }}
2953 @lilypond[staffsize=26,linewidth=1.0\cm]
2954 \include "gregorian-init.ly"
2958 \[ \stropha \auctum b \]
2959 \noBreak s^\markup {"i"}
2961 \layout { \neumeDemoLayout }}
2968 @lilypond[staffsize=26,linewidth=1.0\cm]
2969 \include "gregorian-init.ly"
2974 \noBreak s^\markup {"j"}
2976 \layout { \neumeDemoLayout }}
2982 @code{5. Clivis vel Flexa}
2984 @lilypond[staffsize=26,linewidth=1.0\cm]
2985 \include "gregorian-init.ly"
2992 \layout { \neumeDemoLayout }}
2995 @lilypond[staffsize=26,linewidth=2.0\cm]
2996 \include "gregorian-init.ly"
2999 % Clivis Aucta Descendens
3000 \[ b \flexa \auctum \descendens g \]
3001 \noBreak s^\markup {"l"} \noBreak
3003 % Clivis Aucta Ascendens
3004 \[ b \flexa \auctum \ascendens g \]
3005 \noBreak s^\markup {"m"}
3007 \layout { \neumeDemoLayout }}
3010 @lilypond[staffsize=26,linewidth=1.0\cm]
3011 \include "gregorian-init.ly"
3015 \[ b \flexa \deminutum g \]
3018 \layout { \neumeDemoLayout }}
3022 @code{6. Podatus vel Pes}
3024 @lilypond[staffsize=26,linewidth=1.0\cm]
3025 \include "gregorian-init.ly"
3032 \layout { \neumeDemoLayout }}
3035 @lilypond[staffsize=26,linewidth=2.0\cm]
3036 \include "gregorian-init.ly"
3039 % Pes Auctus Descendens
3040 \[ g \pes \auctum \descendens b \]
3041 \noBreak s^\markup {"p"} \noBreak
3043 % Pes Auctus Ascendens
3044 \[ g \pes \auctum \ascendens b \]
3045 \noBreak s^\markup {"q"}
3047 \layout { \neumeDemoLayout }}
3050 @lilypond[staffsize=26,linewidth=1.0\cm]
3051 \include "gregorian-init.ly"
3055 \[ g \pes \deminutum b \]
3058 \layout { \neumeDemoLayout }}
3062 @code{7. Pes Quassus}
3064 @lilypond[staffsize=26,linewidth=1.0\cm]
3065 \include "gregorian-init.ly"
3069 \[ \oriscus g \pes \virga b \]
3072 \layout { \neumeDemoLayout }}
3075 @lilypond[staffsize=26,linewidth=1.0\cm]
3076 \include "gregorian-init.ly"
3079 % Pes Quassus Auctus Descendens
3080 \[ \oriscus g \pes \auctum \descendens b \]
3083 \layout { \neumeDemoLayout }}
3088 @code{8. Quilisma Pes}
3090 @lilypond[staffsize=26,linewidth=1.0\cm]
3091 \include "gregorian-init.ly"
3095 \[ \quilisma g \pes b \]
3098 \layout { \neumeDemoLayout }}
3101 @lilypond[staffsize=26,linewidth=1.0\cm]
3102 \include "gregorian-init.ly"
3105 % Quilisma Pes Auctus Descendens
3106 \[ \quilisma g \pes \auctum \descendens b \]
3109 \layout { \neumeDemoLayout }}
3114 @code{9. Podatus Initio Debilis}
3116 @lilypond[staffsize=26,linewidth=1.0\cm]
3117 \include "gregorian-init.ly"
3120 % Pes Initio Debilis
3121 \[ \deminutum g \pes b \]
3124 \layout { \neumeDemoLayout }}
3127 @lilypond[staffsize=26,linewidth=1.0\cm]
3128 \include "gregorian-init.ly"
3131 % Pes Auctus Descendens Initio Debilis
3132 \[ \deminutum g \pes \auctum \descendens b \]
3135 \layout { \neumeDemoLayout }}
3142 @lilypond[staffsize=26,linewidth=1.0\cm]
3143 \include "gregorian-init.ly"
3147 \[ a \pes b \flexa g \]
3150 \layout { \neumeDemoLayout }}
3153 @lilypond[staffsize=26,linewidth=1.0\cm]
3154 \include "gregorian-init.ly"
3157 % Torculus Auctus Descendens
3158 \[ a \pes b \flexa \auctum \descendens g \]
3161 \layout { \neumeDemoLayout }}
3164 @lilypond[staffsize=26,linewidth=1.0\cm]
3165 \include "gregorian-init.ly"
3168 % Torculus Deminutus
3169 \[ a \pes b \flexa \deminutum g \]
3172 \layout { \neumeDemoLayout }}
3176 @code{11. Torculus Initio Debilis}
3178 @lilypond[staffsize=26,linewidth=1.0\cm]
3179 \include "gregorian-init.ly"
3182 % Torculus Initio Debilis
3183 \[ \deminutum a \pes b \flexa g \]
3186 \layout { \neumeDemoLayout }}
3189 @lilypond[staffsize=26,linewidth=1.0\cm]
3190 \include "gregorian-init.ly"
3193 % Torculus Auctus Descendens Initio Debilis
3194 \[ \deminutum a \pes b \flexa \auctum \descendens g \]
3197 \layout { \neumeDemoLayout }}
3200 @lilypond[staffsize=26,linewidth=1.0\cm]
3201 \include "gregorian-init.ly"
3204 % Torculus Deminutus Initio Debilis
3205 \[ \deminutum a \pes b \flexa \deminutum g \]
3208 \layout { \neumeDemoLayout }}
3212 @code{12. Porrectus}
3214 @lilypond[staffsize=26,linewidth=1.0\cm]
3215 \include "gregorian-init.ly"
3219 \[ a \flexa g \pes b \]
3222 \layout { \neumeDemoLayout }}
3225 @lilypond[staffsize=26,linewidth=1.0\cm]
3226 \include "gregorian-init.ly"
3229 % Porrectus Auctus Descendens
3230 \[ a \flexa g \pes \auctum \descendens b \]
3233 \layout { \neumeDemoLayout }}
3236 @lilypond[staffsize=26,linewidth=1.0\cm]
3237 \include "gregorian-init.ly"
3240 % Porrectus Deminutus
3241 \[ a \flexa g \pes \deminutum b \]
3244 \layout { \neumeDemoLayout }}
3250 @lilypond[staffsize=26,linewidth=1.0\cm]
3251 \include "gregorian-init.ly"
3255 \[ \virga b \inclinatum a \inclinatum g \]
3258 \layout { \neumeDemoLayout }
3262 @lilypond[staffsize=26,linewidth=1.0\cm]
3263 \include "gregorian-init.ly"
3267 \[ \virga b \inclinatum a \inclinatum \auctum g \]
3270 \layout { \neumeDemoLayout }}
3273 @lilypond[staffsize=26,linewidth=1.0\cm]
3274 \include "gregorian-init.ly"
3277 % Climacus Deminutus
3278 \[ \virga b \inclinatum a \inclinatum \deminutum g \]
3281 \layout { \neumeDemoLayout }}
3285 @code{14. Scandicus}
3287 @lilypond[staffsize=26,linewidth=1.0\cm]
3288 \include "gregorian-init.ly"
3292 \[ g \pes a \virga b \]
3295 \layout { \neumeDemoLayout }}
3298 @lilypond[staffsize=26,linewidth=1.0\cm]
3299 \include "gregorian-init.ly"
3302 % Scandicus Auctus Descendens
3303 \[ g \pes a \pes \auctum \descendens b \]
3306 \layout { \neumeDemoLayout }}
3309 @lilypond[staffsize=26,linewidth=1.0\cm]
3310 \include "gregorian-init.ly"
3313 % Scandicus Deminutus
3314 \[ g \pes a \pes \deminutum b \]
3317 \layout { \neumeDemoLayout }}
3323 @lilypond[staffsize=26,linewidth=1.0\cm]
3324 \include "gregorian-init.ly"
3328 \[ g \oriscus a \pes \virga b \]
3331 \layout { \neumeDemoLayout }}
3334 @lilypond[staffsize=26,linewidth=1.0\cm]
3335 \include "gregorian-init.ly"
3338 % Salicus Auctus Descendens
3339 \[ g \oriscus a \pes \auctum \descendens b \]
3342 \layout { \neumeDemoLayout }}
3349 @lilypond[staffsize=26,linewidth=1.0\cm]
3350 \include "gregorian-init.ly"
3354 \[ \stropha b \stropha b \stropha a \]
3357 \layout { \neumeDemoLayout }
3366 Unlike most other neumes notation systems, the input language for
3367 neumes does not reflect the typographical appearance, but is designed
3368 to focus on musical meaning. For example, @code{\[ a \pes b
3369 \flexa g \]} produces a Torculus consisting of three Punctum heads,
3370 while @code{\[ a \flexa g \pes b \]} produces a Porrectus with a
3371 curved flexa shape and only a single Punctum head. There is no
3372 command to explicitly typeset the curved flexa shape; the decision of
3373 when to typeset a curved flexa shape is based on the musical
3374 input. The idea of this approach is to separate the musical aspects
3375 of the input from the notation style of the output. This way, the
3376 same input can be reused to typeset the same music in a different
3377 style of Gregorian chant notation.
3379 The following table shows the code fragments that produce the
3380 ligatures in the above neumes table. The letter in the first column
3381 in each line of the below table indicates to which ligature in the
3382 above table it refers. The second column gives the name of the
3383 ligature. The third column shows the code fragment that produces this
3384 ligature, using @code{g}, @code{a}, and @code{b} as example pitches.
3386 @multitable @columnfractions .02 .31 .67
3406 @code{\[ \inclinatum b \]}
3414 @code{\[ \auctum \ascendens b \]}
3422 @code{\[ \auctum \descendens b \]}
3427 Punctum Inclinatum@*
3430 @code{\[ \inclinatum \auctum b \]}
3435 Punctum Inclinatum@*
3437 @code{\[ \inclinatum \deminutum b \]}
3444 @code{\[ \virga b \]}
3451 @code{\[ \stropha b \]}
3458 @code{\[ \stropha \auctum b \]}
3465 @code{\[ \oriscus b \]}
3472 @code{\[ b \flexa g \]}
3480 @code{\[ b \flexa \auctum \descendens g \]}
3488 @code{\[ b \flexa \auctum \ascendens g \]}
3495 @code{\[ b \flexa \deminutum g \]}
3502 @code{\[ g \pes b \]}
3510 @code{\[ g \pes \auctum \descendens b \]}
3518 @code{\[ g \pes \auctum \ascendens b \]}
3525 @code{\[ g \pes \deminutum b \]}
3532 @code{\[ \oriscus g \pes \virga b \]}
3538 Auctus Descendens @tab
3539 @code{\[ \oriscus g \pes \auctum \descendens b \]}
3546 @code{\[ \quilisma g \pes b \]}
3554 @code{\[ \quilisma g \pes \auctum \descendens b \]}
3561 @code{\[ \deminutum g \pes b \]}
3566 Pes Auctus Descendens@*
3569 @code{\[ \deminutum g \pes \auctum \descendens b \]}
3576 @code{\[ a \pes b \flexa g \]}
3584 @code{\[ a \pes b \flexa \auctum \descendens g \]}
3591 @code{\[ a \pes b \flexa \deminutum g \]}
3596 Torculus Initio Debilis
3598 @code{\[ \deminutum a \pes b \flexa g \]}
3604 Descendens Initio Debilis
3606 @code{\[ \deminutum a \pes b \flexa \auctum \descendens g \]}
3611 Torculus Deminutus@*
3614 @code{\[ \deminutum a \pes b \flexa \deminutum g \]}
3621 @code{\[ a \flexa g \pes b \]}
3629 @code{\[ a \flexa g \pes \auctum \descendens b \]}
3636 @code{\[ a \flexa g \pes \deminutum b \]}
3643 @code{\[ \virga b \inclinatum a \inclinatum g \]}
3650 @code{\[ \virga b \inclinatum a \inclinatum \auctum g \]}
3657 @code{\[ \virga b \inclinatum a \inclinatum \deminutum g \]}
3664 @code{\[ g \pes a \virga b \]}
3672 @code{\[ g \pes a \pes \auctum \descendens b \]}
3679 @code{\[ g \pes a \pes \deminutum b \]}
3686 @code{\[ g \oriscus a \pes \virga b \]}
3691 Salicus Auctus Descendens
3693 @code{\[ g \oriscus a \pes \auctum \descendens b \]}
3700 @code{\[ \stropha b \stropha b \stropha a \]}
3705 The following head prefixes are supported
3707 @cindex @code{\virga}
3709 @cindex @code{\stropha}
3711 @cindex @code{\inclinatum}
3713 @cindex @code{\auctum}
3715 @cindex @code{\descendens}
3717 @cindex @code{\ascendens}
3719 @cindex @code{\oriscus}
3721 @cindex @code{\quilisma}
3723 @cindex @code{\deminutum}
3726 Head prefixes can be accumulated, though restrictions apply. For
3727 example, either @code{\descendens} or @code{\ascendens} can be applied
3728 to a head, but not both to the same head.
3731 @cindex @code{\flexa}
3732 Two adjacent heads can be tied together with the @code{\pes} and
3733 @code{\flexa} infix commands for a rising and falling line of melody,
3738 @node Gregorian Chant contexts
3739 @subsection Gregorian Chant contexts
3741 @cindex VaticanaVoiceContext
3742 @cindex VaticanaStaffContext
3744 The predefined @code{VaticanaVoiceContext} and
3745 @code{VaticanaStaffContext} can be used to engrave a piece of
3746 Gregorian Chant in the style of the Editio Vaticana. These contexts
3747 initialize all relevant context properties and grob properties to
3748 proper values, so you can immediately go ahead entering the chant, as
3749 the following excerpt demonstrates
3751 @lilypond[quote,raggedright,packed,verbatim]
3752 \include "gregorian-init.ly"
3755 \context VaticanaVoice = "cantus" {
3756 \override Staff.StaffSymbol #'color = #red
3757 \override Staff.LedgerLineSpanner #'color = #red
3758 \override Score.BarNumber #'transparent = ##t {
3759 \[ c'\melisma c' \flexa a \]
3760 \[ a \flexa \deminutum g\melismaEnd \]
3762 \[ f\melisma \pes a c' c' \pes d'\melismaEnd \]
3763 c' \divisioMinima \break
3764 \[ c'\melisma c' \flexa a \]
3765 \[ a \flexa \deminutum g\melismaEnd \] f \divisioMinima
3768 \lyricsto "cantus" \new Lyrics {
3769 San- ctus, San- ctus, San- ctus
3776 @node Mensural contexts
3777 @subsection Mensural contexts
3779 @cindex MensuralVoiceContext
3780 @cindex MensuralStaffContext
3782 The predefined @code{MensuralVoiceContext} and
3783 @code{MensuralStaffContext} can be used to engrave a piece in mensural
3784 style. These contexts initialize all relevant context properties and
3785 grob properties to proper values, so you can immediately go ahead
3786 entering the chant, as the following excerpt demonstrates
3788 @lilypond[quote,raggedright,verbatim]
3791 \context MensuralVoice = "discantus" \transpose c c' {
3792 \override Score.BarNumber #'transparent = ##t {
3793 c'1\melisma bes a g\melismaEnd
3795 \[ f1\melisma a c'\breve d'\melismaEnd \]
3797 c'\breve\melisma a1 g1\melismaEnd
3798 fis\longa^\signumcongruentiae
3801 \lyricsto "discantus" \new Lyrics {
3802 San -- ctus, San -- ctus, San -- ctus
3808 @node Musica ficta accidentals
3809 @subsection Musica ficta accidentals
3811 In European music from before about 1600, singers were often expected
3812 to chromatically alter notes at their own initiative. This is called
3813 ``Musica Ficta''. In modern transcriptions, these accidentals are
3814 usually printed over the note.
3816 @cindex Musica ficta
3818 Support for such suggested accidentals is included, and can be
3819 switched on by setting @code{suggestAccidentals} to true.
3821 @cindex @code{suggestAccidentals}
3823 @lilypond[verbatim,fragment,relative=1]
3825 \set suggestAccidentals = ##t
3831 Program reference: @internalsref{Accidental_engraver} engraver and the
3832 @internalsref{AccidentalSuggestion} object.
3835 @subsection Figured bass
3837 @cindex Basso continuo
3839 @c TODO: musicological blurb about FB
3842 LilyPond has limited support for figured bass
3844 @lilypond[quote,raggedright,verbatim,fragment]
3846 \context Voice { \clef bass dis4 c d ais g fis}
3847 \context FiguredBass \figuremode {
3848 < 6 >4 < 7 >8 < 6+ [_!] >
3855 The support for figured bass consists of two parts: there is an input
3856 mode, introduced by @code{\figuremode}, where you can enter bass figures
3857 as numbers, and there is a context called @internalsref{FiguredBass} that
3858 takes care of making @internalsref{BassFigure} objects.
3860 In figures input mode, a group of bass figures is delimited by
3861 @code{<} and @code{>}. The duration is entered after the @code{>}
3865 @lilypond[quote,raggedright,fragment]
3866 \context FiguredBass
3867 \figuremode { <4 6> }
3870 Accidentals are added when you append @code{-}, @code{!}, and @code{+}
3876 @lilypond[quote,raggedright,fragment]
3877 \context FiguredBass
3878 \figuremode { <4- 6+ 7!> }
3881 Spaces or dashes may be inserted by using @code{_}. Brackets are
3882 introduced with @code{[} and @code{]}. You can also include text
3883 strings and text markups, see @ref{Overview of text markup commands}.
3886 < [4 6] 8 [_! 12] > < 5 \markup @{ + \number 6 @} >
3888 @lilypond[quote,raggedright,fragment]
3889 \context FiguredBass
3890 \figuremode { < [4 6] 8 [_! 12] > < 5 \markup{ + \number 6 } > }
3894 Although the support for figured bass may superficially resemble chord
3895 support, it works much simpler. The @code{\figuremode} mode simply
3896 stores the numbers and @internalsref{FiguredBass} context prints
3897 them as entered. There is no conversion to pitches and no
3898 realizations of the bass are played in the MIDI file.
3900 Internally, the code produces markup texts. You can use any of the
3901 markup text properties to override formatting. For example, the
3902 vertical spacing of the figures may be set with @code{baseline-skip}.
3906 Program reference: @internalsref{BassFigure} object,
3907 @internalsref{FiguredBass} context.
3911 Slash notation for alterations is not supported.
3915 @node Other instrument specific notation
3916 @section Other instrument specific notation
3918 This section includes extra information for writing for instruments.
3921 * Artificial harmonics (strings)::
3924 @node Artificial harmonics (strings)
3925 @subsection Artificial harmonics (strings)
3927 @cindex artificial harmonics
3929 Artificial harmonics are notated with a different notehead style. They
3930 are entered by marking the harmonic pitch with @code{\harmonic}.
3932 @lilypond[raggedright,verbatim,quote,fragment,relative=1]