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..
12 @node Expressive marks
13 @section Expressive marks
15 @lilypondfile[quote]{expressive-headword.ly}
17 This section lists various expressive marks that can be
27 @node Attached to notes
28 @subsection Attached to notes
30 This section explains how to create expressive marks that are
31 attached to notes: articulations, ornamentations, and dynamics.
32 Methods to create new dynamic markings are also discussed.
35 * Articulations and ornamentations::
40 @node Articulations and ornamentations
41 @unnumberedsubsubsec Articulations and ornamentations
52 @cindex organ pedal marks
53 @cindex pedal marks, organ
75 @funindex \staccatissimo
91 @funindex \snappizzicato
93 @funindex \reverseturn
98 @funindex \prallmordent
102 @funindex \downmordent
106 @funindex \signumcongruentiae
107 @funindex \shortfermata
109 @funindex \longfermata
110 @funindex \verylongfermata
118 A variety of symbols that denote articulations, ornamentations,
119 and other performance indications can be attached to a note using
123 @var{note}\@var{name}
126 The possible values for @var{name} are listed in @ref{List of
127 articulations}. For example:
129 @lilypond[verbatim,quote,relative=2]
130 c4\staccato c\mordent b2\turn
136 @cindex staccatissimo
141 Some of these articulations have shorthands for easier entry.
142 Shorthands are appended to the note name, and their syntax
143 consists of a dash @code{-} followed by a symbol signifying the
144 articulation. Predefined shorthands exist for @notation{marcato},
145 @notation{stopped}, @notation{tenuto}, @notation{staccatissimo},
146 @notation{accent}, @notation{staccato}, and @notation{portato}.
147 Their corresponding output appears as follows:
149 @lilypond[verbatim,quote,relative=2]
154 The rules for the default placement of articulations are defined
155 in @file{scm/@/script@/.scm}. Articulations and ornamentations
156 may be manually placed above or below the staff; see
157 @ref{Direction and placement}.
159 Articulations are @code{Script} objects. Their properties are
160 described more fully in @rinternals{Script}.
162 In addition to articulations, text and markups can be attached to
163 notes. See @ref{Text scripts}.
165 For more information about the ordering of Scripts and TextScripts that
166 are attached to the notes, see @rlearning{Placement of objects}.
170 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
171 {modifying-default-values-for-articulation-shorthand-notation.ly}
173 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
174 {controlling-the-vertical-ordering-of-scripts.ly}
176 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
177 {creating-a-delayed-turn.ly}
187 @rlearning{Placement of objects}.
192 @ref{Direction and placement},
193 @ref{List of articulations},
197 @file{scm/@/script@/.scm}.
200 @rlsr{Expressive marks}.
204 @rinternals{TextScript}.
208 @unnumberedsubsubsec Dynamics
210 @cindex absolute dynamics
212 @cindex dynamics, absolute
253 Absolute dynamic marks are specified using a command after a note,
254 such as @code{c4\ff}. The available dynamic marks are
255 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
256 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
257 @code{\ffff}, @code{\fffff}, @code{\fp}, @code{\sf}, @code{\sff},
258 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}. Dynamic
259 marks may be manually placed above or below the staff; see
260 @ref{Direction and placement}.
262 @lilypond[verbatim,quote,relative=2]
281 A @notation{crescendo} mark is started with @code{\<} and
282 terminated with @code{\!}, an absolute dynamic, or an additional
283 crescendo or decrescendo mark. A @notation{decrescendo} mark is
284 started with @code{\>} and is also terminated with @code{\!}, an
285 absolute dynamic, or another crescendo or decrescendo mark.
286 @code{\cr} and @code{\decr} may be used instead of @code{\<} and
287 @code{\>}. @notation{Hairpins} are engraved by default using this
290 @lilypond[verbatim,quote,relative=2]
300 Spacer rests are needed to engrave multiple marks on one note.
302 @cindex multiple dynamic marks on one note
303 @cindex dynamic marks, multiple on one note
305 @lilypond[verbatim,quote,relative=2]
307 << f1 { s4 s4\< s4\> s4\! } >>
310 @cindex espressivo articulation
312 @funindex \espressivo
315 In some situations the @code{\espressivo} articulation mark may be
316 the appropriate choice to indicate a crescendo and decrescendo on
319 @lilypond[verbatim,quote,relative=2]
325 @funindex \crescTextCresc
326 @funindex crescTextCresc
327 @funindex \dimTextDecresc
328 @funindex dimTextDecresc
329 @funindex \dimTextDecr
330 @funindex dimTextDecr
331 @funindex \dimTextDim
333 @funindex \crescHairpin
334 @funindex crescHairpin
335 @funindex \dimHairpin
338 Crescendos and decrescendos can be engraved as textual markings
339 instead of hairpins. Dashed lines are printed to indicate their
340 extent. The built-in commands @code{\crescTextCresc},
341 @code{\dimTextDecresc}, @code{\dimTextDecr}, and @code{\dimTextDim}
342 will tell LilyPond to use such textual marks instead of hairpins
343 for all subsequent @code{\<} and @code{\>} commands. The corresponding
344 @code{\crescHairpin} and @code{\dimHairpin} commands will revert
347 @lilypond[verbatim,quote,relative=2]
359 To create new absolute dynamic marks or text that should be
360 aligned with dynamics, see @ref{New dynamic marks}.
362 @cindex dynamics, vertical positioning
363 @cindex vertical positioning of dynamics
365 @funindex DynamicLineSpanner
368 Vertical positioning of dynamics is handled by
369 @rinternals{DynamicLineSpanner}.
372 @funindex \dynamicDown
373 @funindex dynamicDown
374 @funindex \dynamicNeutral
375 @funindex dynamicNeutral
381 @code{\dynamicNeutral},
382 @code{\crescTextCresc},
385 @code{\dimTextDecresc},
386 @code{\crescHairpin},
393 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
394 {setting-hairpin-behavior-at-bar-lines.ly}
396 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
397 {setting-the-minimum-length-of-hairpins.ly}
402 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
403 {printing-hairpins-using-al-niente-notation.ly}
405 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
406 {vertically-aligned-dynamics-and-textscripts.ly}
408 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
409 {hiding-the-extender-line-for-text-dynamics.ly}
411 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
412 {changing-text-and-spanner-styles-for-text-dynamics.ly}
423 @rlearning{Articulation and dynamics}.
426 @ref{Direction and placement},
427 @ref{New dynamic marks},
428 @ref{What goes into the MIDI output?},
429 @ref{Controlling MIDI dynamics}.
432 @rlsr{Expressive marks}.
435 @rinternals{DynamicText},
436 @rinternals{Hairpin},
437 @rinternals{DynamicLineSpanner}.
440 @node New dynamic marks
441 @unnumberedsubsubsec New dynamic marks
443 @cindex new dynamic marks
444 @cindex dynamic marks, new
446 The easiest way to create dynamic indications is to use
447 @code{\markup} objects.
449 @lilypond[verbatim,quote]
450 moltoF = \markup { molto \dynamic f }
453 <d e>16_\moltoF <d e>
458 @cindex dynamics, editorial
459 @cindex dynamics, parenthesis
460 @cindex editorial dynamics
466 In markup mode, editorial dynamics (within parentheses or square
467 brackets) can be created. The syntax for markup mode is described
468 in @ref{Formatting text}.
470 @lilypond[verbatim,quote]
472 \center-align \concat { \bold { \italic ( }
473 \dynamic f \bold { \italic ) } } }
474 boxF = \markup { \bracket { \dynamic f } }
481 @cindex make-dynamic-script
482 @funindex make-dynamic-script
484 Simple, centered dynamic marks are easily created with the
485 @code{make-dynamic-script} function.
487 @lilypond[verbatim,quote]
488 sfzp = #(make-dynamic-script "sfzp")
494 In general, @code{make-dynamic-script} takes any markup object as its
495 argument. The dynamic font only contains the characters
496 @code{f,m,p,r,s} and @code{z}, so if a dynamic mark that includes
497 plain text or punctuation symbols is desired, markup commands that
498 reverts font family and font encoding to normal text should be used,
499 for example @code{\normal-text}. The interest of using
500 @code{make-dynamic-script} instead of an ordinary markup is ensuring
501 the vertical alignment of markup objects and hairpins that are
502 attached to the same note head.
504 @lilypond[verbatim,quote]
505 roundF = \markup { \center-align \concat {
506 \normal-text { \bold { \italic ( } }
508 \normal-text { \bold { \italic ) } } } }
509 boxF = \markup { \bracket { \dynamic f } }
510 mfEspress = \markup { \center-align \line {
511 \hspace #3.7 mf \normal-text \italic espress. } }
512 roundFdynamic = #(make-dynamic-script roundF)
513 boxFdynamic = #(make-dynamic-script boxF)
514 mfEspressDynamic = #(make-dynamic-script mfEspress)
516 c4_\roundFdynamic\< d e f
519 g'1~\mfEspressDynamic
524 The Scheme form of markup mode may be used instead. Its syntax is
525 explained in @rextend{Markup construction in Scheme}.
527 @lilypond[verbatim,quote]
528 moltoF = #(make-dynamic-script
529 (markup #:normal-text "molto"
537 Font settings in markup mode are described in
538 @ref{Selecting font and font size}.
543 @ref{Formatting text},
544 @ref{Selecting font and font size},
545 @ref{What goes into the MIDI output?},
546 @ref{Controlling MIDI dynamics}.
549 @rlsr{Expressive marks}.
552 @rextend{Markup construction in Scheme}.
559 This section explains how to create various expressive marks that
560 are curved: normal slurs, phrasing slurs, breath marks, falls, and
571 @unnumberedsubsubsec Slurs
575 @notation{Slurs} are entered using parentheses:
577 @warning{In polyphonic music, a slur must be terminated
578 in the same voice it began.}
580 @lilypond[verbatim,quote,relative=2]
586 @cindex slurs, manual placement
587 @cindex slurs, below notes
588 @cindex slurs, above notes
591 @funindex \slurNeutral
592 @funindex slurNeutral
594 Slurs may be manually placed above or below the staff; see
595 @ref{Direction and placement}.
597 @cindex phrasing slur
598 @cindex multiple slurs
599 @cindex simultaneous slurs
600 @cindex slur, phrasing
601 @cindex slurs, multiple
602 @cindex slurs, simultaneous
604 Simultaneous or overlapping slurs are not permitted, but a phrasing
605 slur can overlap a slur. This permits two slurs to be printed at
606 once. For details, see @ref{Phrasing slurs}.
616 @funindex \slurDashed
618 @funindex \slurDotted
623 Slurs can be solid, dotted, or dashed. Solid is the default slur
626 @lilypond[verbatim,quote,relative=1]
636 @funindex \slurHalfDashed
637 @funindex slurHalfDashed
638 @funindex \slurHalfSolid
639 @funindex slurHalfSolid
640 @cindex slur, half dashed and half solid
642 Slurs can also be made half-dashed (the first half dashed, the
643 second half solid) or half-solid (the first half solid, the second
646 @lilypond[verbatim,quote,relative=1]
656 @funindex \slurDashPattern
657 @funindex slurDashPattern
658 @cindex slur, defining dash patterns
660 Custom dash patterns for slurs can be defined:
662 @lilypond[verbatim,quote,relative=1]
664 \slurDashPattern #0.7 #0.75
666 \slurDashPattern #0.5 #2.0
684 @code{\slurHalfDashed},
685 @code{\slurHalfSolid},
686 @code{\slurDashPattern},
693 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
694 {using-double-slurs-for-legato-chords.ly}
696 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
697 {positioning-text-markups-inside-slurs.ly}
699 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
700 {making-slurs-with-complex-dash-structure.ly}
708 @rlearning{On the un-nestedness of brackets and ties}.
711 @ref{Direction and placement},
712 @ref{Phrasing slurs}.
715 @rlsr{Expressive marks}.
722 @unnumberedsubsubsec Phrasing slurs
724 @cindex phrasing slurs
725 @cindex phrasing marks
726 @cindex slur, phrasing
727 @cindex mark, phrasing
731 @notation{Phrasing slurs} (or phrasing marks) that indicate a
732 musical sentence are written using the commands @code{\(} and
733 @code{\)} respectively:
735 @lilypond[verbatim,quote,relative=2]
740 @funindex \phrasingSlurUp
741 @funindex phrasingSlurUp
742 @funindex \phrasingSlurDown
743 @funindex phrasingSlurDown
744 @funindex \phrasingSlurNeutral
745 @funindex phrasingSlurNeutral
747 Typographically, a phrasing slur behaves almost exactly like a
748 normal slur. However, they are treated as different objects; a
749 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
750 may be manually placed above or below the staff; see
751 @ref{Direction and placement}.
753 @cindex simultaneous phrasing slurs
754 @cindex multiple phrasing slurs
755 @cindex slur, simultaneous phrasing
756 @cindex slur, multiple phrasing
757 @cindex phrasing slur, simultaneous
758 @cindex phrasing slur, multiple
760 Simultaneous or overlapping phrasing slurs are not permitted.
762 @funindex phrasingSlurDashed
763 @funindex \phrasingSlurDashed
764 @funindex \phrasingSlurDotted
765 @funindex phrasingSlurDotted
766 @funindex \phrasingSlurSolid
767 @funindex phrasingSlurSolid
768 @cindex phrasing slur, dashed
769 @cindex dashed phrasing slur
770 @cindex phrasing slur, dotted
771 @cindex dotted phrasing slurs
772 @cindex slur, dashed phrasing
773 @cindex slur, dotted phrasing
775 Phrasing slurs can be solid, dotted, or dashed. Solid is the default
776 style for phrasing slurs:
778 @lilypond[verbatim,quote,relative=1]
788 @funindex phrasingSlurHalfDashed
789 @funindex \phrasingSlurHalfDashed
790 @funindex \phrasingSlurHalfSolid
791 @funindex phrasingSlurHalfSolid
792 @cindex phrasing slur, half solid and half dashed
793 @cindex slur, half solid and half dashed phrasing
795 Phrasing slurs can also be made half-dashed (the first half dashed, the
796 second half solid) or half-solid (the first half solid, the second
799 @lilypond[verbatim,quote,relative=1]
801 \phrasingSlurHalfDashed
803 \phrasingSlurHalfSolid
809 @funindex \phrasingSlurDashPattern
810 @funindex phrasingSlurDashPattern
811 @cindex phrasing slur, defining dash patterns
812 @cindex slur, phrasing, defining dash patterns
813 @cindex slur, definind dash patterns for phrasing
815 Custom dash patterns for phrasing slurs can be defined:
817 @lilypond[verbatim,quote,relative=1]
819 \phrasingSlurDashPattern #0.7 #0.75
821 \phrasingSlurDashPattern #0.5 #2.0
827 Dash pattern definitions for phrasing slurs have the same structure
828 as dash pattern definitions for slurs. For more information about
829 complex dash patterns, see the snippets under @ref{Slurs}.
832 @code{\phrasingSlurUp},
833 @code{\phrasingSlurDown},
834 @code{\phrasingSlurNeutral},
835 @code{\phrasingSlurDashed},
836 @code{\phrasingSlurDotted},
837 @code{\phrasingSlurHalfDashed},
838 @code{\phrasingSlurHalfSolid},
839 @code{\phrasingSlurDashPattern},
840 @code{\phrasingSlurSolid}.
846 @rlearning{On the un-nestedness of brackets and ties}.
849 @ref{Direction and placement},
853 @rlsr{Expressive marks}.
856 @rinternals{PhrasingSlur}.
860 @unnumberedsubsubsec Breath marks
867 Breath marks are entered using @code{\breathe}:
869 @lilypond[verbatim,quote,relative=2]
873 A breath mark will end an automatic beam; to override this behavior, see
876 @lilypond[verbatim,quote,relative=2]
880 Musical indicators for breath marks in ancient notation,
881 divisiones, are supported. For details, see @ref{Divisiones}.
886 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
887 {changing-the-breath-mark-symbol.ly}
890 @cindex railroad tracks
892 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
893 {inserting-a-caesura.ly}
904 @rlsr{Expressive marks}.
907 @rinternals{BreathingEvent},
908 @rinternals{BreathingSign},
909 @rinternals{Breathing_sign_engraver}.
912 @node Falls and doits
913 @unnumberedsubsubsec Falls and doits
920 @notation{Falls} and @notation{doits} can be added to notes using
921 the @code{\bendAfter} command. The direction of the fall or doit
922 is indicated with a plus or minus (up or down). The number
923 indicates the pitch interval that the fall or doit will extend
924 @emph{beyond} the main note.
926 @lilypond[verbatim,quote,relative=2]
935 The dash @code{-} immediately preceding the @code{\bendAfter}
936 command is @emph{required} when writing falls and doits.
941 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
942 {adjusting-the-shape-of-falls-and-doits.ly}
951 @rlsr{Expressive marks}.
957 This section explains how to create various expressive marks that
958 follow a linear path: glissandos, arpeggios, and trills.
967 @unnumberedsubsubsec Glissando
973 A @notation{glissando} is created by attaching @code{\glissando}
976 @lilypond[verbatim,quote,relative=2]
981 Different styles of glissandi can be created. For details, see
986 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
987 {contemporary-glissando.ly}
998 @rlsr{Expressive marks}.
1000 Internals Reference:
1001 @rinternals{Glissando}.
1006 Printing text over the line (such as @notation{gliss.}) is not
1011 @unnumberedsubsubsec Arpeggio
1014 @cindex broken chord
1015 @cindex chord, broken
1019 @funindex \arpeggioArrowUp
1020 @funindex arpeggioArrowUp
1021 @funindex \arpeggioArrowDown
1022 @funindex arpeggioArrowDown
1023 @funindex \arpeggioNormal
1024 @funindex arpeggioNormal
1026 An @notation{arpeggio} on a chord (also known as a broken chord)
1027 is denoted by appending @code{\arpeggio} to the chord construct:
1029 @lilypond[verbatim,quote,relative=1]
1033 Different types of arpeggios may be written.
1034 @code{\arpeggioNormal} reverts to a normal arpeggio:
1036 @lilypond[verbatim,quote,relative=1]
1049 @cindex arpeggio symbols, special
1050 @cindex special arpeggio symbols
1052 @funindex \arpeggioBracket
1053 @funindex arpeggioBracket
1054 @funindex \arpeggioParenthesis
1055 @funindex arpeggioParenthesis
1056 @funindex \arpeggioParenthesisDashed
1057 @funindex arpeggioParenthesisDashed
1059 Special @emph{bracketed} arpeggio symbols can be created:
1061 @lilypond[verbatim,quote,relative=1]
1067 \arpeggioParenthesis
1070 \arpeggioParenthesisDashed
1077 The dash properties of the parenthesis arpeggio are controlled
1078 with the @code{'dash-details} property, which is described at @ref{Slurs}.
1080 Arpeggios can be explicitly written out with ties. For more
1081 information, see @ref{Ties}.
1086 @code{\arpeggioArrowUp},
1087 @code{\arpeggioArrowDown},
1088 @code{\arpeggioNormal},
1089 @code{\arpeggioBracket},
1090 @code{\arpeggioParenthesis}
1091 @code{\arpeggioParenthesisDashed}.
1097 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1098 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
1100 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1101 {creating-cross-staff-arpeggios-in-other-contexts.ly}
1103 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1104 {creating-arpeggios-across-notes-in-different-voices.ly}
1116 @rlsr{Expressive marks}.
1118 Internals Reference:
1119 @rinternals{Arpeggio},
1121 @rinternals{PianoStaff}.
1126 @cindex cross-staff parenthesis-style arpeggio
1127 @cindex arpeggio, parenthesis-style, cross-staff
1128 @cindex arpeggio, cross-staff parenthesis-style
1130 It is not possible to mix connected arpeggios and unconnected
1131 arpeggios in one @code{PianoStaff} at the same point in
1134 The parenthesis-style arpeggio brackets do not work for
1135 cross-staff arpeggios.
1139 @unnumberedsubsubsec Trills
1145 @funindex \startTrillSpan
1146 @funindex startTrillSpan
1147 @funindex \stopTrillSpan
1148 @funindex stopTrillSpan
1150 Short @notation{trills} without an extender line are printed with
1151 @code{\trill}; see @ref{Articulations and ornamentations}.
1153 Longer trills with an extender line are made with
1154 @code{\startTrillSpan} and @code{\stopTrillSpan}:
1156 @lilypond[verbatim,quote,relative=2]
1162 In the following example, a trill is combined with grace notes.
1163 The syntax of this construct and the method to precisely position
1164 the grace notes are described in @ref{Grace notes}.
1166 @lilypond[verbatim,quote,relative=2]
1168 d1\startTrillSpan { c32[ d]\stopTrillSpan }
1172 @cindex pitched trills
1173 @cindex trills, pitched
1174 @funindex \pitchedTrill
1175 @funindex pitchedTrill
1177 Trills that require an auxiliary note with an explicit pitch can
1178 be typeset with the @code{\pitchedTrill} command. The first
1179 argument is the main note, and the second is the @emph{trilled}
1180 note, printed as a stemless note head in parentheses.
1182 @lilypond[verbatim,quote,relative=1]
1183 \pitchedTrill e2\startTrillSpan fis
1187 @cindex pitched trill with forced accidental
1188 @cindex trill, pitched with forced accidental
1189 @cindex accidental, forced for pitched trill
1191 In the following example, the second pitched trill is ambiguous;
1192 the accidental of the trilled note is not printed. As a
1193 workaround, the accidentals of the trilled notes can be forced.
1194 The second measure illustrates this method:
1196 @lilypond[verbatim,quote,relative=2]
1197 \pitchedTrill eis4\startTrillSpan fis
1199 \pitchedTrill eis4\startTrillSpan fis
1201 \pitchedTrill eis4\startTrillSpan fis
1203 \pitchedTrill eis4\startTrillSpan fis!
1209 @code{\startTrillSpan},
1210 @code{\stopTrillSpan}.
1219 @ref{Articulations and ornamentations},
1223 @rlsr{Expressive marks}.
1225 Internals Reference:
1226 @rinternals{TrillSpanner}.