1 @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. See TRANSLATION for details.
13 @section Chord notation
15 @lilypondfile[quote]{chords-headword.ly}
17 Chords can be entered either as normal notes or in chord mode and displayed
18 using a variety of traditional European chord naming conventions. Chord
19 names and figured bass notation can also be displayed.
29 @subsection Chord mode
33 Chord mode is used to enter chords using an indicator of the chord
34 structure, rather than the chord pitches.
37 * Chord mode overview::
39 * Extended and altered chords::
42 @node Chord mode overview
43 @unnumberedsubsubsec Chord mode overview
48 Chords can be entered as simultaneous music, as discussed in
51 Chords can also be entered in @qq{chord mode}, which is an input
52 mode that focuses on the structures of chords in traditional
53 European music, rather than on specific pitches. This is
54 convenient for those who are familiar with using chord names to
55 describe chords. More information on different input modes can be
56 found at @ref{Input modes}.
58 @lilypond[verbatim,quote,ragged-right,relative=1]
59 \chordmode { c1 g a g c }
62 Chords entered using chord mode are music elements, and can be
63 transposed just like chords entered using simultaneous music.
65 Chord mode and note mode can be mixed in sequential music:
67 @lilypond[verbatim,quote,ragged-right,relative=1]
89 When chord mode and note mode are mixed in sequential music, and
90 chord mode comes first, the note mode will create a new @code{Staff}
93 @lilypond[verbatim,quote,ragged-right,relative=1]
98 To avoid this behavior, explicitly create the @code{Staff} context:
100 @lilypond[verbatim,quote,ragged-right,relative=1]
108 @unnumberedsubsubsec Common chords
111 @cindex seventh chords
112 @cindex root of chord
113 @cindex modifiers, in chords.
114 @cindex chord quality
116 Major triads are entered by including the root and an
119 @lilypond[verbatim,quote,relative=1,ragged-right]
120 \chordmode { c2 f4 g }
123 Minor, augmented, and diminished triads are entered by placing
124 @code{:} and a quality modifier string after the duration:
126 @lilypond[verbatim,quote,ragged-right,relative=1]
127 \chordmode { c2:m f4:aug g:dim }
130 Seventh chords can be created:
132 @lilypond[quote,ragged-right,fragment,verbatim,relative=1]
133 \chordmode { c1:7 c:m7 c:maj7 c:dim7 c:aug7 }
141 The table belows shows the actions of the quality modifiers on
142 triads and seventh chords. A more complete table of modifier usage
143 is found at @ref{Common chord modifiers}.
146 @multitable @columnfractions .2 .4 .3
158 The default action; produces a major triad.
160 @lilypond[line-width=4\cm, noragged-right]
162 \override Staff.TimeSignature #'stencil = ##f
170 The minor chord. This modifier lowers the 3rd and (if present) the
173 @lilypond[line-width=4\cm, noragged-right]
175 \override Staff.TimeSignature #'stencil = ##f
184 The diminished chord. This modifier lowers the 3rd, 5th and (if
185 present) the 7th step.
187 @lilypond[line-width=4\cm, noragged-right]
189 \override Staff.TimeSignature #'stencil = ##f
197 The augmented chord. This modifier raises the 5th step.
199 @lilypond[line-width=4\cm, noragged-right]
201 \override Staff.TimeSignature #'stencil = ##f
209 The major 7th chord. This modifier adds a raised 7th step. The
210 @code{7} following @code{maj} is optional. Do NOT use this modifier
211 to create a major triad.
213 @lilypond[line-width=4\cm, noragged-right]
215 \override Staff.TimeSignature #'stencil = ##f
226 @ref{Common chord modifiers}.
231 @node Extended and altered chords
232 @unnumberedsubsubsec Extended and altered chords
234 @cindex extended chords
235 @cindex altered chords
237 Chord structures of arbitrary complexity can be created in chord
238 mode. The modifier string can be used to extend a chord, add or
239 remove chord steps, raise or lower chord steps, and add a bass note
240 or create an inversion.
242 The first number following the @code{:} is taken to be the extent
243 of the chord. The chord is constructed by sequentially adding
244 thirds to the root until the specified number has been reached.
245 If the extent is not a third (e.g., 6), thirds are added up to the
246 highest third below the extent, and then the step of the extent is
247 added. The largest possible value for the extent is 13. Any
248 larger value is interpreted as 13.
250 @lilypond[quote,ragged-right,fragment,verbatim,relative=1]
260 Note that both @code{c:5} and @code{c} produce a C major triad.
262 Since an unaltered 11 does not sound good when combined with an
263 unaltered 13, the 11 is removed from a @code{:13} chord (unless it
264 is added explicitly).
266 @lilypond[quote,ragged-right,fragment,verbatim,relative=1]
272 @cindex additions, in chords
274 Individual steps can be added to a chord. Additions follow the
275 extent and are prefixed by a dot (@code{.}).
277 @lilypond[quote,verbatim,fragment,relative=1]
279 c1:5.6 c:3.7.8 c:3.6.13
283 Added steps can be as high as desired.
285 @lilypond[quote,verbatim,fragment,relative=1]
287 c4:5.15 c:5.20 c:5.25 c:5.30
291 @cindex chord steps, altering
293 Added chord steps can be altered by suffixing a @code{-} or @code{+}
294 sign to the number. To alter a step that is automatically included
295 as part of the basic chord structure, add it as an altered step.
297 @lilypond[quote,verbatim,fragment,relative=1]
299 c1:7+ c:5+.3- c:3-.5-.7-
303 @cindex removals, in chords
307 Following any steps to be added, a series of steps to be removed
308 is introduced in a modifier string with a prefix of @code{^}.
309 If more than one step is to be removed, the steps to be
310 removed are separated by @code{.} following the
313 @lilypond[quote,verbatim,fragment,relative=1]
315 c1^3 c:7^5 c:9^3 c:9^3.5 c:13.11^3.7
321 The modifier @code{sus} can be added to the modifier string to
322 create suspended chords. This removes the 3rd step from the chord.
323 Append either @code{2} or @code{4} to add the 2nd or 4th step to the
324 chord. @code{sus} is equivalent to @code{^3}; @code{sus4} is
325 equivalent to @code{.4^3}.
327 @lilypond[quote,ragged-right,fragment,verbatim]
329 c1:sus c:sus2 c:sus4 c:5.4^3
334 @cindex chord inversions
335 @cindex bass note, for chords
337 Inversions (putting a pitch other than the root on the bottom of the
338 chord) and added bass notes can be specified by appending
339 @code{/}@var{pitch} to the chord.
341 @lilypond[quote,ragged-right,fragment,verbatim, relative=2]
349 A bass note that is part of the chord can be added, instead of
350 moved as part of an inversion, by using @code{/+}@var{pitch}.
352 @lilypond[quote,ragged-right,fragment,verbatim]
358 Chord modifiers that can be used to produce a variety of
359 standard chords are shown in
360 @ref{Common chord modifiers}.
365 @ref{Common chord modifiers}.
372 Each step can only be present in a chord once. The following
373 simply produces the augmented chord, since @code{5+} is
376 @lilypond[quote,ragged-right,verbatim,fragment]
377 \chordmode { c1:5.5-.5+ }
380 Only the second inversion can be created by adding a bass
381 note. The first inversion requires changing the root of
384 @lilypond[quote,ragged-right,verbatim,fragment]
386 c'1: c':/g e:6-3-^5 e:m6-^5
390 @node Displaying chords
391 @subsection Displaying chords
393 Chords can be displayed by name, in addition to the standard display
397 * Printing chord names::
398 * Customizing chord names::
401 @node Printing chord names
402 @unnumberedsubsubsec Printing chord names
404 @cindex printing chord names
408 Chord names are printed in the @code{ChordNames} context:
410 @lilypond[verbatim,quote,relative=1,ragged-right]
418 Chords can be entered as simultaneous notes or through the use of
419 chord mode. The displayed chord name will be the same, regardless
420 of the mode of entry, unless there are inversions or added bass notes:
422 @lilypond[verbatim,quote,relative=1]
443 @code{\chords @{ ... @}} is a shortcut notation for
444 @code{\new ChordNames @{ \chordmode @{ ... @} @}}.
446 @lilypond[verbatim,quote,ragged-right, relative=1]
452 @lilypond[verbatim,quote,ragged-right, relative=1]
462 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
463 {showing-chords-at-changes.ly}
465 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
466 @c {adding-bar-lines-to-chordnames-context.ly}
468 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
469 {simple-lead-sheet.ly}
479 @ref{Writing music in parallel}.
486 @rinternals{ChordNames},
487 @rinternals{ChordName},
488 @rinternals{Chord_name_engraver},
489 @rinternals{Volta_engraver},
490 @rinternals{Bar_engraver}.
494 Chords containing inversions or altered bass notes are not named
495 properly if entered using simultaneous music.
498 @node Customizing chord names
499 @unnumberedsubsubsec Customizing chord names
501 @cindex customizing chord names
503 There is no unique system for naming chords. Different musical
504 traditions use different names for the same set of chords. There
505 are also different symbols displayed for a given chord name. The
506 names and symbols displayed for chord names are customizable.
511 The basic chord name layout is a system for Jazz music, proposed
512 by Klaus Ignatzek (see @ref{Literature list}). The chord naming
513 system can be modified as described below. An alternate jazz
514 chord system has been developed using these modifications.
515 The Ignatzek and alternate
516 Jazz notation are shown on the chart in @ref{Chord
519 @c TODO -- Change this so we don't have a non-verbatim example.
520 @c Make short example in docs, then move longer example to
521 @c appendix, where the length of the snippet won't matter.
523 In addition to the different naming systems, different note names
524 are used for the root in different languages. The predefined
525 variables @code{\germanChords}, @code{\semiGermanChords},
526 @code{\italianChords} and @code{\frenchChords} set these variables.
527 The effect is demonstrated here:
529 @lilypondfile[ragged-right]{chord-names-languages.ly}
531 If none of the existing settings give the desired output, the chord
532 name display can be tuned through the following properties.
536 @funindex chordRootNamer
540 The chord name is usually printed as a letter for the root with an
541 optional alteration. The transformation from pitch to letter is
542 done by this function. Special note names (for example, the German
543 @q{H} for a B-chord) can be produced by storing a new function in
546 @funindex majorSevenSymbol
548 @item majorSevenSymbol
550 This property contains the markup object used to follow the output
551 of @code{chordRootNamer} to identify a major 7 chord. Predefined
552 options are @code{whiteTriangleMarkup} and
553 @code{blackTriangleMarkup}.
555 @funindex chordNoteNamer
559 When the chord name contains additional pitches other than the root
560 (e.g., an added bass note), this function is used to print the
561 additional pitch. By default the pitch is printed using
562 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
563 to a specialized function to change this behavior. For example, the
564 bass note can be printed in lower case.
566 @funindex chordNameSeparator
568 @item chordNameSeparator
570 Different parts of a chord name are normally separated by a slash.
571 By setting @code{chordNameSeparator}, you can use any desired markup
574 @funindex chordNameExceptions
576 @item chordNameExceptions
578 This property is a list of pairs. The first item in each pair
579 is a set of pitches used to identify the steps present in the chord.
580 The second item is a markup that will follow the @code{chordRootNamer}
581 output to create the chord name.
583 @funindex chordPrefixSpacer
584 @item chordPrefixSpacer
586 The @q{m} for minor chords is usually printed immediately to the
587 right of the root of the chord. A spacer can be placed between
588 the root and @q{m} by setting @code{chordPrefixSpacer}.
589 The spacer is not used when the root is altered.
595 @funindex major seven symbols
596 @code{\whiteTriangleMarkup},
597 @code{\blackTriangleMarkup},
598 @funindex \germanChords
599 @code{\germanChords},
600 @funindex \semiGermanChords
601 @code{\semiGermanChords},
602 @funindex \italianChords
603 @code{\italianChords},
604 @funindex \frenchChords
605 @code{\frenchChords}.
611 @cindex exceptions, chord names.
612 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
613 {chord-name-exceptions.ly}
615 @c TODO - tweak snippet to use \blackTriangleMarkup as well
616 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
617 {chord-name-major7.ly}
619 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
620 {adding-bar-lines-to-chordnames-context.ly}
622 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
623 {volta-below-chords.ly}
625 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
626 {changing-chord-separator.ly}
632 @ref{Chord name chart},
633 @ref{Common chord modifiers}.
636 @file{scm/@/chords@/-ignatzek@/.scm},
637 @file{scm/@/chord@/-entry@/.scm},
638 @file{ly/@/chord@/-modifier@/-init@/.ly}.
643 @c Internals Reference:
648 Chord names are determined from both the pitches that are present
649 in the chord and the information on the chord structure that may
650 have been entered in @code{\chordmode}. If the simultaneous pitches
651 method of entering chords is used, undesired names result from
652 inversions or bass notes.
654 @lilypond[quote,ragged-right,verbatim]
655 myChords = \relative c' {
656 \chordmode { c1 c/g c/f }
657 <c e g>1 <g c e> <f c' e g>
660 \new ChordNames { \myChords }
661 \new Staff { \myChords }
667 @subsection Figured bass
669 @lilypondfile[quote]{figured-bass-headword.ly}
671 Figured bass notation can be displayed.
674 * Introduction to figured bass::
675 * Entering figured bass::
676 * Displaying figured bass::
679 @node Introduction to figured bass
680 @unnumberedsubsubsec Introduction to figured bass
682 @cindex Basso continuo
683 @cindex Thorough bass
685 @cindex Bass, thorough
686 @cindex Bass, figured
688 @c TODO: musicological blurb about FB
691 LilyPond has support for figured bass, also called thorough bass
694 @lilypond[quote,ragged-right,verbatim,fragment]
696 \new Voice { \clef bass dis4 c d ais g fis}
699 < 6 >4 < 7\+ >8 < 6+ [_!] >
707 The support for figured bass consists of two parts: there is an
708 input mode, introduced by @code{\figuremode}, that accepts
709 entry of bass figures, and there is a context named
710 @code{FiguredBass} that takes care of displaying
711 @code{BassFigure} objects. Figured bass can also be displayed
712 in @code{Staff} contexts.
714 @code{\figures@{ ... @}} is a shortcut notation for
715 @code{\new FiguredBass @{ \figuremode @{ ... @} @}}.
718 Although the support for figured bass may superficially resemble chord
719 support, it is much simpler. @code{\figuremode} mode simply
720 stores the figures and the @code{FiguredBass} context prints them
721 as entered. There is no conversion to pitches.
724 Figures are created as markup texts. Any of the standard markup
725 properties can be used to modify the display of figures. For
726 example, the vertical spacing of the figures may be set with
727 @code{baseline-skip}.
733 @rglos{figured bass}.
739 @node Entering figured bass
740 @unnumberedsubsubsec Entering figured bass
742 @code{\figuremode} is used to switch the input mode to figure mode.
743 More information on different input modes can be
744 found at @ref{Input modes}.
746 In figure mode, a group of bass figures is delimited by
747 @code{<} and @code{>}. The duration is entered after the @code{>}.
749 @lilypond[verbatim,quote,ragged-right,fragment]
758 Accidentals (including naturals) can be added to figures:
760 @lilypond[verbatim,quote,ragged-right,fragment]
762 <7! 6+ 4-> <5++> <3-->
766 Augmented and diminished steps can be indicated:
768 @lilypond[verbatim,quote,ragged-right,fragment]
774 A backward slash through a figure (typically used for raised
775 sixth steps) can be created:
777 @lilypond[verbatim,quote,ragged-right,fragment]
783 Vertical spaces and brackets can be be included in figures:
785 @lilypond[verbatim,quote,ragged-right,fragment]
791 Any text markup can be inserted as a figure:
793 @lilypond[verbatim,quote,ragged-right,fragment]
795 <\markup { \tiny \number 6 \super (1) } 5>
799 @c NOTE: We need to include notes any time we use extenders to
800 @c avoid extraneous staff creation due to Staff.use... in
801 @c \bassFigureExtendersOn
803 Continuation lines can be used to indicate repeated figures:
805 @lilypond[verbatim,quote,ragged-right,fragment]
813 \bassFigureExtendersOn
814 <6 4>4 <6 3> <7 3> <7 3>
815 \bassFigureExtendersOff
816 <6 4>4 <6 3> <7 3> <7 3>
822 In this case, the extender lines replace existing figures,
823 unless the continuation lines have been explicitly terminated.
825 @lilypond[verbatim,quote,ragged-right,fragment]
828 \bassFigureExtendersOn
829 <6 4>4 <6 4> <6\! 4\!> <6 4>
838 The table below summarizes the figure modifiers available.
840 @multitable @columnfractions .1 .5 .4
854 @lilypond[line-width=4\cm]
856 <7! 6+ 4-> <5++> <3-->
863 Augmented and diminished steps
865 @lilypond[line-width=4\cm]
876 @lilypond[line-width=4\cm]
885 End of continuation line
887 @lilypond[line-width=4\cm]
890 \bassFigureExtendersOn
891 <6 4> <6 4> <6\! 4\!> <6 4>
904 @cindex figured bass extender lines
905 @code{\bassFigureExtendersOn},
906 @code{\bassFigureExtendersOff}.
911 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
912 {changing-the-positions-of-figured-bass-alterations.ly}
921 @c Notation Reference:
924 @c Application Usage:
934 @rinternals{BassFigure},
935 @rinternals{BassFigureAlignment},
936 @rinternals{BassFigureLine},
937 @rinternals{BassFigureBracket},
938 @rinternals{BassFigureContinuation},
939 @rinternals{FiguredBass}.
943 @node Displaying figured bass
944 @unnumberedsubsubsec Displaying figured bass
946 Figured bass can be displayed using the @code{FiguredBass} context,
947 or in most staff contexts.
949 When displayed in a @code{FiguredBass} context, the vertical location
950 of the figures is independent of the notes on the staff.
952 @lilypond[verbatim,ragged-right,fragment,quote]
967 In the example above, the @code{FiguredBass} context must be
968 explicitly instantiated to avoid creating a second (empty) staff.
971 Figured bass can also be added to @code{Staff} contexts
972 directly. In this case, the vertical position of the
973 figures is adjusted automatically.
975 @lilypond[verbatim,ragged-right,fragment,quote]
982 %% Put notes on same Staff as figures
983 \context Staff = myStaff
992 When added in a @code{Staff} context, figured bass can be displayed above
995 @lilypond[verbatim,ragged-right,fragment,quote]
1000 \bassFigureStaffAlignmentDown
1003 %% Put notes on same Staff as figures
1004 \context Staff = myStaff
1014 @cindex figured bass alignment
1015 @code{\bassFigureStaffAlignmentDown},
1016 @code{\bassFigureStaffAlignmentUp},
1017 @code{\bassFigureStaffAlignmentNeutral}.
1030 @c Notation Reference:
1033 @c Application Usage:
1042 Internals Reference:
1043 @rinternals{BassFigure},
1044 @rinternals{BassFigureAlignment},
1045 @rinternals{BassFigureLine},
1046 @rinternals{BassFigureBracket},
1047 @rinternals{BassFigureContinuation},
1048 @rinternals{FiguredBass}.
1052 To ensure that continuation lines work properly, it is
1053 safest to use the same rhythm in the figure line as in
1056 @lilypond[verbatim,ragged-right,fragment,quote]
1060 \repeat unfold 4 { f16. g32 } f8. es16 d8 es
1063 \bassFigureExtendersOn
1064 % The extenders are correct here, with the same rhythm as the bass
1065 \repeat unfold 4 { <6 4->16. <6 4->32 }
1066 <5>8. r16 <6>8 <6\! 5->
1072 \repeat unfold 4 { f16. g32 } f8. es16 d8 es
1075 \bassFigureExtendersOn
1076 % The extenders are incorrect here, even though the timing is the same
1078 <5>8. r16 <6>8 <6\! 5->
1083 When using extender lines, adjacent figures with the same number in
1084 a different figure location can cause the figure positions to invert.
1086 @lilypond[verbatim,ragged-right,fragment,quote,relative=1]
1090 \bassFigureExtendersOn
1091 <6 5>4 <5\! 4> < 5 _!> <6>
1096 To avoid this problem, simply turn on extenders after the figure that
1097 begins the extender line and turn them off at the end of the extender line.
1099 @lilypond[verbatim,ragged-right,fragment,quote,relative=1]
1104 \bassFigureExtendersOn
1106 \bassFigureExtendersOff