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. For details, see the Contributors'
7 Guide, node Updating translation committishes..
14 @section Chord notation
16 @lilypondfile[quote]{chords-headword.ly}
18 Chords can be entered either as normal notes or in chord mode and displayed
19 using a variety of traditional European chord naming conventions. Chord
20 names and figured bass notation can also be displayed.
30 @subsection Chord mode
34 Chord mode is used to enter chords using an indicator of the chord
35 structure, rather than the chord pitches.
38 * Chord mode overview::
40 * Extended and altered chords::
43 @node Chord mode overview
44 @unnumberedsubsubsec Chord mode overview
49 Chords can be entered as simultaneous music, as discussed in
52 Chords can also be entered in @qq{chord mode}, which is an input
53 mode that focuses on the structures of chords in traditional
54 European music, rather than on specific pitches. This is
55 convenient for those who are familiar with using chord names to
56 describe chords. More information on different input modes can be
57 found at @ref{Input modes}.
59 @lilypond[verbatim,quote,ragged-right]
60 \chordmode { c1 g a g c }
63 Chords entered using chord mode are music elements, and can be
64 transposed just like chords entered using simultaneous music.
65 @code{\chordmode} is absolute, as @code{\relative} has no effect
66 on @code{chordmode} blocks. However, in @code{\chordmode} the
67 absolute pitches are one octave higher than in note mode.
69 Chord mode and note mode can be mixed in sequential music:
71 @lilypond[verbatim,quote,ragged-right,relative=1]
90 Predefined shorthands for articulations and ornaments cannot be used
91 on notes in chord mode, see @ref{Articulations and ornamentations}.
93 When chord mode and note mode are mixed in sequential music, and
94 chord mode comes first, the note mode will create a new @code{Staff}
97 @lilypond[verbatim,quote,ragged-right,relative=1]
103 To avoid this behavior, explicitly create the @code{Staff} context:
105 @lilypond[verbatim,quote,ragged-right,relative=1]
114 @unnumberedsubsubsec Common chords
117 @cindex seventh chords
118 @cindex root of chord
119 @cindex modifiers, in chords.
120 @cindex chord quality
122 Major triads are entered by including the root and an
125 @lilypond[verbatim,quote,ragged-right]
126 \chordmode { c2 f4 g }
129 Minor, augmented, and diminished triads are entered by placing
130 @code{:} and a quality modifier string after the duration:
132 @lilypond[verbatim,quote,ragged-right]
133 \chordmode { c2:m f4:aug g:dim }
136 Seventh chords can be created:
138 @lilypond[quote,ragged-right,verbatim]
139 \chordmode { c1:7 c:m7 c:maj7 c:dim7 c:aug7 }
147 The table below shows the actions of the quality modifiers on
148 triads and seventh chords. The default seventh step added to
149 chords is a minor or flatted seventh, which makes the dominant
150 seventh the basic seventh chord. All alterations are relative to
151 the dominant seventh. A more complete table of modifier usage
152 is found at @ref{Common chord modifiers}.
155 @multitable @columnfractions .2 .4 .3
167 The default action; produces a major triad.
169 @lilypond[line-width=4\cm, noragged-right]
171 \omit Staff.TimeSignature
179 The minor chord. This modifier lowers the 3rd.
181 @lilypond[line-width=4\cm, noragged-right]
183 \omit Staff.TimeSignature
192 The diminished chord. This modifier lowers the 3rd, 5th and (if
193 present) the 7th step.
195 @lilypond[line-width=4\cm, noragged-right]
197 \omit Staff.TimeSignature
205 The augmented chord. This modifier raises the 5th step.
207 @lilypond[line-width=4\cm, noragged-right]
209 \omit Staff.TimeSignature
217 The major 7th chord. This modifier adds a raised 7th step. The
218 @code{7} following @code{maj} is optional. Do NOT use this modifier
219 to create a major triad.
221 @lilypond[line-width=4\cm, noragged-right]
223 \omit Staff.TimeSignature
232 @ref{Common chord modifiers},
233 @ref{Extended and altered chords}.
239 Only one quality modifier should be used per chord, typically on the
240 highest step present in the chord. Chords with more than quality
241 modifier will be parsed without an error or warning, but the results
242 are unpredictable. Chords that cannot be achieved with a single
243 quality modifier should be altered by individual pitches, as described
244 in @ref{Extended and altered chords}.
247 @node Extended and altered chords
248 @unnumberedsubsubsec Extended and altered chords
250 @cindex extended chords
251 @cindex altered chords
253 Chord structures of arbitrary complexity can be created in chord
254 mode. The modifier string can be used to extend a chord, add or
255 remove chord steps, raise or lower chord steps, and add a bass note
256 or create an inversion.
258 The first number following the @code{:} is taken to be the extent
259 of the chord. The chord is constructed by sequentially adding
260 thirds to the root until the specified number has been reached.
261 Note that the seventh step added as part of an extended chord will be the
262 minor or flatted seventh, not the major seventh.
263 If the extent is not a third (e.g., 6), thirds are added up to the
264 highest third below the extent, and then the step of the extent is
265 added. The largest possible value for the extent is 13. Any
266 larger value is interpreted as 13.
268 @lilypond[quote,ragged-right,verbatim]
278 Note that both @code{c:5} and @code{c} produce a C major triad.
280 Since an unaltered 11 does not sound good when combined with an
281 unaltered 13, the 11 is removed from a @code{:13} chord (unless it
282 is added explicitly).
284 @lilypond[quote,ragged-right,verbatim]
290 @cindex additions, in chords
292 Individual steps can be added to a chord. Additions follow the
293 extent and are prefixed by a dot (@code{.}). The basic seventh
294 step added to a chord is the minor or flatted seventh, rather than
297 @lilypond[quote,verbatim]
299 c1:5.6 c:3.7.8 c:3.6.13
303 Added steps can be as high as desired.
305 @lilypond[quote,verbatim]
307 c4:5.15 c:5.20 c:5.25 c:5.30
311 @cindex chord steps, altering
313 Added chord steps can be altered by suffixing a @code{-} or @code{+}
314 sign to the number. To alter a step that is automatically included
315 as part of the basic chord structure, add it as an altered step.
317 @lilypond[quote,verbatim]
319 c1:7+ c:5+.3- c:3-.5-.7-
323 @cindex removals, in chords
327 Following any steps to be added, a series of steps to be removed
328 is introduced in a modifier string with a prefix of @code{^}.
329 If more than one step is to be removed, the steps to be
330 removed are separated by @code{.} following the
333 @lilypond[quote,verbatim]
335 c1^3 c:7^5 c:9^3 c:9^3.5 c:13.11^3.7
341 The modifier @code{sus} can be added to the modifier string to
342 create suspended chords. This removes the 3rd step from the chord.
343 Append either @code{2} or @code{4} to add the 2nd or 4th step to the
344 chord. @code{sus} is equivalent to @code{^3}; @code{sus4} is
345 equivalent to @code{.4^3}.
347 @lilypond[quote,ragged-right,verbatim]
349 c1:sus c:sus2 c:sus4 c:5.4^3
354 @cindex chord inversions
355 @cindex bass note, for chords
357 Inversions (putting a pitch other than the root on the bottom of the
358 chord) and added bass notes can be specified by appending
359 @code{/}@var{pitch} to the chord.
361 @lilypond[quote,ragged-right,verbatim]
369 A bass note that is part of the chord can be added, instead of
370 moved as part of an inversion, by using @code{/+}@var{pitch}.
372 @lilypond[quote,ragged-right,verbatim]
378 Chord modifiers that can be used to produce a variety of
379 standard chords are shown in
380 @ref{Common chord modifiers}.
384 @ref{Common chord modifiers}.
390 Each step can only be present in a chord once. The following
391 simply produces the augmented chord, since @code{5+} is
394 @lilypond[quote,ragged-right,verbatim]
395 \chordmode { c1:5.5-.5+ }
398 Only the second inversion can be created by adding a bass
399 note. The first inversion requires changing the root of
402 @lilypond[quote,ragged-right,verbatim]
404 c'1: c':/g e:6-3-^5 e:m6-^5
409 @node Displaying chords
410 @subsection Displaying chords
412 Chords can be displayed by name, in addition to the standard display
416 * Printing chord names::
417 * Customizing chord names::
420 @node Printing chord names
421 @unnumberedsubsubsec Printing chord names
423 @cindex printing chord names
427 Chord names are printed in the @code{ChordNames} context:
429 @lilypond[verbatim,quote,ragged-right]
437 Chords can be entered as simultaneous notes or through the use of
438 chord mode. The displayed chord name will be the same, regardless
439 of the mode of entry, unless there are inversions or added bass notes:
441 @lilypond[verbatim,quote]
442 chordmusic = \relative c' {
459 @cindex no chord symbol
461 @cindex indicating No Chord in ChordNames
463 Rests passed to a @code{ChordNames} context will cause the
464 @code{noChordSymbol} markup to be displayed.
466 @lilypond[verbatim, quote, relative=1]
468 \new ChordNames \chordmode {
485 @code{\chords @{ @dots{} @}} is a shortcut notation for
486 @code{\new ChordNames @{ \chordmode @{ @dots{} @} @}}.
488 @lilypond[verbatim,quote,ragged-right]
494 @lilypond[verbatim,quote,ragged-right]
504 @c Keep index entries with following snippet
505 @cindex chords, suppressing repeated
506 @funindex chordChanges
508 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
509 {showing-chords-at-changes.ly}
511 @c @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
512 @c {adding-bar-lines-to-chordnames-context.ly}
514 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
515 {simple-lead-sheet.ly}
522 @ref{Writing music in parallel}.
528 @rinternals{ChordNames},
529 @rinternals{ChordName},
530 @rinternals{Chord_name_engraver},
531 @rinternals{Volta_engraver},
532 @rinternals{Bar_engraver}.
535 Chords containing inversions or altered bass notes are not named
536 properly if entered using simultaneous music.
539 @node Customizing chord names
540 @unnumberedsubsubsec Customizing chord names
542 @cindex customizing chord names
544 There is no unique system for naming chords. Different musical
545 traditions use different names for the same set of chords. There
546 are also different symbols displayed for a given chord name. The
547 names and symbols displayed for chord names are customizable.
552 The basic chord name layout is a system for Jazz music, proposed
553 by Klaus Ignatzek (see @ressay{Literature list}). The chord naming
554 system can be modified as described below. An alternate jazz
555 chord system has been developed using these modifications.
556 The Ignatzek and alternate
557 Jazz notation are shown on the chart in @ref{Chord name chart}.
559 @c TODO -- Change this so we don't have a non-verbatim example.
560 @c Make short example in docs, then move longer example to
561 @c appendix, where the length of the snippet won't matter.
563 In addition to the different naming systems, different note names
564 are used for the root in different languages. The predefined
565 commands @code{\germanChords}, @code{\semiGermanChords},
566 @code{\italianChords} and @code{\frenchChords} set these variables.
567 The effect is demonstrated here:
569 @lilypondfile[ragged-right]{chord-names-languages.ly}
572 @funindex chordNameLowercaseMinor
574 German songbooks may indicate minor chords as lowercase letters,
575 without any @var{m} suffix. This can be obtained by setting the
576 @code{chordNameLowercaseMinor} property:
578 @lilypond[verbatim,quote,ragged-right]
580 \set chordNameLowercaseMinor = ##t
585 If none of the existing settings give the desired output, the chord
586 name display can be tuned through the following properties.
590 @funindex chordRootNamer
594 The chord name is usually printed as a letter for the root with an
595 optional alteration. The transformation from pitch to letter is
596 done by this function. Special note names (for example, the German
597 @q{H} for a B-chord) can be produced by storing a new function in
600 @funindex majorSevenSymbol
602 @item majorSevenSymbol
604 This property contains the markup object used to follow the output
605 of @code{chordRootNamer} to identify a major 7 chord. Predefined
606 options are @code{whiteTriangleMarkup} and
607 @code{blackTriangleMarkup}.
609 @funindex additionalPitchPrefix
611 @item additionalPitchPrefix
613 When the chord name contains additional pitches, they can optionally
614 be prefixed with some text. The default is no prefix, in order to
615 avoid too much visual clutter, but for small numbers of additional
616 pitches this can be visually effective.
618 @lilypond[verbatim,quote,ragged-right]
621 \set additionalPitchPrefix = #"add"
626 @funindex chordNoteNamer
630 When the chord name contains additional pitches other than the root
631 (e.g., an added bass note), this function is used to print the
632 additional pitch. By default the pitch is printed using
633 @code{chordRootNamer}. The @code{chordNoteNamer} property can be set
634 to a specialized function to change this behavior. For example, the
635 bass note can be printed in lower case.
637 @funindex chordNameSeparator
639 @item chordNameSeparator
641 Different parts of a chord name are normally separated by a small
642 amount of horizontal space. By setting @code{chordNameSeparator}, you
643 can use any desired markup for a separator. This does not affect the
644 separator between a chord and its bass note; to customize that, use
645 @code{slashChordSeparator}.
647 @lilypond[verbatim,quote,ragged-right]
650 \set chordNameSeparator = \markup { "/" }
656 @funindex slashChordSeparator
658 @item slashChordSeparator
660 Chords can be played over a bass note other than the conventional root
661 of the chord. These are known as ``inversions'' or ``slash chords'',
662 because the default way of notating them is with a forward slash
663 between the main chord and the bass note. Therefore the value of
664 @code{slashChordSeparator} defaults to a forward slash, but you can
665 change it to any markup you choose.
667 @lilypond[verbatim,quote,ragged-right]
670 \set slashChordSeparator = \markup { " over " }
676 @funindex chordNameExceptions
678 @item chordNameExceptions
680 This property is a list of pairs. The first item in each pair
681 is a set of pitches used to identify the steps present in the chord.
682 The second item is a markup that will follow the @code{chordRootNamer}
683 output to create the chord name.
685 @funindex minorChordModifier
687 @item minorChordModifier
689 Minor chords are often denoted via a @q{m} suffix to the right of the
690 root of the chord. However some idioms prefer other suffices, such as
693 @lilypond[verbatim,quote,ragged-right]
696 \set minorChordModifier = \markup { "-" }
702 @funindex chordPrefixSpacer
704 @item chordPrefixSpacer
706 The modifier for minor chords as determined by
707 @code{minorChordModifier} is usually printed immediately to the right
708 of the root of the chord. A spacer can be placed between the root and
709 the modifier by setting @code{chordPrefixSpacer}. The spacer is not
710 used when the root is altered.
716 @funindex major seven symbols
717 @code{\whiteTriangleMarkup},
718 @code{\blackTriangleMarkup},
719 @funindex \germanChords
720 @code{\germanChords},
721 @funindex \semiGermanChords
722 @code{\semiGermanChords},
723 @funindex \italianChords
724 @code{\italianChords},
725 @funindex \frenchChords
726 @code{\frenchChords}.
732 @cindex exceptions, chord names.
733 @lilypondfile[verbatim,quote,texidoc,doctitle]
734 {chord-name-exceptions.ly}
736 @c TODO - tweak snippet to use \blackTriangleMarkup as well
737 @lilypondfile[verbatim,quote,texidoc,doctitle]
738 {chord-name-major7.ly}
740 @lilypondfile[verbatim,quote,texidoc,doctitle]
741 {adding-bar-lines-to-chordnames-context.ly}
743 @lilypondfile[verbatim,quote,texidoc,doctitle]
744 {volta-below-chords.ly}
746 @lilypondfile[verbatim,quote,texidoc,doctitle]
747 {changing-chord-separator.ly}
751 @ref{Chord name chart},
752 @ref{Common chord modifiers}.
754 Essay on automated music engraving:
755 @ressay{Literature list}.
758 @file{scm/chords-ignatzek.scm},
759 @file{scm/chord-entry.scm},
760 @file{ly/chord-modifier-init.ly}.
766 Chord names are determined from both the pitches that are present
767 in the chord and the information on the chord structure that may
768 have been entered in @code{\chordmode}. If the simultaneous pitches
769 method of entering chords is used, undesired names result from
770 inversions or bass notes.
772 @lilypond[quote,ragged-right,verbatim]
773 myChords = \relative c' {
774 \chordmode { c1 c/g c/f }
775 <c e g>1 <g c e> <f c' e g>
778 \new ChordNames { \myChords }
779 \new Staff { \myChords }
785 @subsection Figured bass
787 @c Line width hack because of instrument names
788 @lilypondfile[quote,staffsize=18,line-width=14.5\cm]{figured-bass-headword.ly}
790 Figured bass notation can be displayed.
793 * Introduction to figured bass::
794 * Entering figured bass::
795 * Displaying figured bass::
798 @node Introduction to figured bass
799 @unnumberedsubsubsec Introduction to figured bass
801 @cindex Basso continuo
802 @cindex Thorough bass
804 @cindex Bass, thorough
805 @cindex Bass, figured
807 @c TODO: musicological blurb about FB
810 LilyPond has support for figured bass, also called thorough bass
813 @lilypond[quote,ragged-right,verbatim]
815 \new Voice { \clef bass dis4 c d ais g fis}
818 < 6 >4 < 7\+ >8 < 6+ [_!] >
826 The support for figured bass consists of two parts: there is an
827 input mode, introduced by @code{\figuremode}, that accepts
828 entry of bass figures, and there is a context named
829 @code{FiguredBass} that takes care of displaying
830 @code{BassFigure} objects. Figured bass can also be displayed
831 in @code{Staff} contexts.
833 @code{\figures@{ @dots{} @}} is a shortcut notation for
834 @code{\new FiguredBass @{ \figuremode @{ @dots{} @} @}}.
837 Although the support for figured bass may superficially resemble chord
838 support, it is much simpler. @code{\figuremode} mode simply
839 stores the figures and the @code{FiguredBass} context prints them
840 as entered. There is no conversion to pitches.
843 Figures are created as markup texts. Any of the standard markup
844 properties can be used to modify the display of figures. For
845 example, the vertical spacing of the figures may be set with
846 @code{baseline-skip}.
851 @rglos{figured bass}.
857 @node Entering figured bass
858 @unnumberedsubsubsec Entering figured bass
860 @code{\figuremode} is used to switch the input mode to figure mode.
861 More information on different input modes can be
862 found at @ref{Input modes}.
864 In figure mode, a group of bass figures is delimited by
865 @code{<} and @code{>}. The duration is entered after the @code{>}.
867 @lilypond[verbatim,quote,ragged-right]
876 Accidentals (including naturals) can be added to figures:
878 @lilypond[verbatim,quote,ragged-right]
880 <7! 6+ 4-> <5++> <3-->
884 Augmented and diminished steps can be indicated:
886 @lilypond[verbatim,quote,ragged-right]
892 A backward slash through a figure (typically used for raised
893 sixth steps) can be created:
895 @lilypond[verbatim,quote,ragged-right]
901 Vertical spaces and brackets can be included in figures:
903 @lilypond[verbatim,quote,ragged-right]
909 Any text markup can be inserted as a figure:
911 @lilypond[verbatim,quote,ragged-right]
913 <\markup { \tiny \number 6 \super (1) } 5>
917 @c NOTE: We need to include notes any time we use extenders to
918 @c avoid extraneous staff creation due to Staff.use... in
919 @c \bassFigureExtendersOn
921 Continuation lines can be used to indicate repeated figures:
923 @lilypond[verbatim,quote,ragged-right]
931 \bassFigureExtendersOn
932 <6 4>4 <6 3> <7 3> <7 3>
933 \bassFigureExtendersOff
934 <6 4>4 <6 3> <7 3> <7 3>
940 In this case, the extender lines replace existing figures,
941 unless the continuation lines have been explicitly terminated.
943 @lilypond[verbatim,quote,ragged-right]
946 \bassFigureExtendersOn
947 <6 4>4 <6 4> <6\! 4\!> <6 4>
956 The table below summarizes the figure modifiers available.
958 @multitable @columnfractions .1 .5 .4
972 @lilypond[line-width=4\cm]
974 <7! 6+ 4-> <5++> <3-->
981 Augmented and diminished steps
983 @lilypond[line-width=4\cm]
994 @lilypond[line-width=4\cm]
1003 End of continuation line
1005 @lilypond[line-width=4\cm]
1008 \bassFigureExtendersOn
1009 <6 4> <6 4> <6\! 4\!> <6 4>
1022 @cindex figured bass extender lines
1023 @code{\bassFigureExtendersOn},
1024 @code{\bassFigureExtendersOff}.
1029 @lilypondfile[verbatim,quote,texidoc,doctitle]
1030 {changing-the-positions-of-figured-bass-alterations.ly}
1036 Internals Reference:
1037 @rinternals{BassFigure},
1038 @rinternals{BassFigureAlignment},
1039 @rinternals{BassFigureLine},
1040 @rinternals{BassFigureBracket},
1041 @rinternals{BassFigureContinuation},
1042 @rinternals{FiguredBass}.
1045 @node Displaying figured bass
1046 @unnumberedsubsubsec Displaying figured bass
1048 Figured bass can be displayed using the @code{FiguredBass} context,
1049 or in most staff contexts.
1051 When displayed in a @code{FiguredBass} context, the vertical location
1052 of the figures is independent of the notes on the staff.
1054 @lilypond[verbatim,ragged-right,quote]
1069 In the example above, the @code{FiguredBass} context must be
1070 explicitly instantiated to avoid creating a second (empty) staff.
1073 Figured bass can also be added to @code{Staff} contexts
1074 directly. In this case, the vertical position of the
1075 figures is adjusted automatically.
1077 @lilypond[verbatim,ragged-right,quote]
1079 \new Staff = "myStaff"
1084 %% Put notes on same Staff as figures
1085 \context Staff = "myStaff"
1094 When added in a @code{Staff} context, figured bass can be displayed above
1097 @lilypond[verbatim,ragged-right,quote]
1099 \new Staff = "myStaff"
1102 \bassFigureStaffAlignmentDown
1105 %% Put notes on same Staff as figures
1106 \context Staff = "myStaff"
1115 @cindex figured bass alignment
1116 @code{\bassFigureStaffAlignmentDown},
1117 @code{\bassFigureStaffAlignmentUp},
1118 @code{\bassFigureStaffAlignmentNeutral}.
1125 Internals Reference:
1126 @rinternals{BassFigure},
1127 @rinternals{BassFigureAlignment},
1128 @rinternals{BassFigureLine},
1129 @rinternals{BassFigureBracket},
1130 @rinternals{BassFigureContinuation},
1131 @rinternals{FiguredBass}.
1134 To ensure that continuation lines work properly, it is
1135 safest to use the same rhythm in the figure line as in
1138 @lilypond[verbatim,ragged-right,quote]
1142 \repeat unfold 4 { f16. g32 } f8. es16 d8 es
1145 \bassFigureExtendersOn
1146 % The extenders are correct here, with the same rhythm as the bass
1147 \repeat unfold 4 { <6 4->16. <6 4->32 }
1148 <5>8. r16 <6>8 <6\! 5->
1154 \repeat unfold 4 { f16. g32 } f8. es16 d8 es
1157 \bassFigureExtendersOn
1158 % The extenders are incorrect here, even though the timing is the same
1160 <5>8. r16 <6>8 <6\! 5->