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
73 A variety of symbols that denote articulations, ornamentations,
74 and other performance indications can be attached to a note using
81 The possible values for @var{name} are listed in @ref{List of
82 articulations}. For example:
84 @lilypond[verbatim,quote,relative=2]
85 c4\staccato c\mordent b2\turn
96 Some of these articulations have shorthands for easier entry.
97 Shorthands are appended to the note name, and their syntax
98 consists of a dash @code{-} followed by a symbol signifying the
99 articulation. Predefined shorthands exist for @notation{marcato},
100 @notation{stopped}, @notation{tenuto}, @notation{staccatissimo},
101 @notation{accent}, @notation{staccato}, and @notation{portato}.
102 Their corresponding output appears as follows:
104 @lilypond[verbatim,quote,relative=2]
109 The rules for the default placement of articulations are defined
110 in @file{scm/@/script@/.scm}. Articulations and ornamentations
111 may be manually placed above or below the staff; see
112 @ref{Direction and placement}.
114 Articulations are @code{Script} objects. Their properties are
115 described more fully in @rinternals{Script}.
117 In addition to articulations, text and markups can be attached to
118 notes. See @ref{Text scripts}.
120 For more information about the ordering of Scripts and TextScripts that
121 are attached to the notes, see @rlearning{Placement of objects}.
125 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
126 {modifying-default-values-for-articulation-shorthand-notation.ly}
128 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
129 {controlling-the-vertical-ordering-of-scripts.ly}
131 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
132 {creating-a-delayed-turn.ly}
142 @rlearning{Placement of objects}.
147 @ref{Direction and placement},
148 @ref{List of articulations},
152 @file{scm/@/script@/.scm}.
155 @rlsr{Expressive marks}.
159 @rinternals{TextScript}.
163 @unnumberedsubsubsec Dynamics
165 @cindex absolute dynamics
167 @cindex dynamics, absolute
208 Absolute dynamic marks are specified using a command after a note,
209 such as @code{c4\ff}. The available dynamic marks are
210 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
211 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
212 @code{\ffff}, @code{\fffff}, @code{\fp}, @code{\sf}, @code{\sff},
213 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}. Dynamic
214 marks may be manually placed above or below the staff; see
215 @ref{Direction and placement}.
217 @lilypond[verbatim,quote,relative=2]
236 A @notation{crescendo} mark is started with @code{\<} and
237 terminated with @code{\!}, an absolute dynamic, or an additional
238 crescendo or decrescendo mark. A @notation{decrescendo} mark is
239 started with @code{\>} and is also terminated with @code{\!}, an
240 absolute dynamic, or another crescendo or decrescendo mark.
241 @code{\cr} and @code{\decr} may be used instead of @code{\<} and
242 @code{\>}. @notation{Hairpins} are engraved by default using this
245 @lilypond[verbatim,quote,relative=2]
255 Spacer rests are needed to engrave multiple marks on one note.
257 @cindex multiple dynamic marks on one note
258 @cindex dynamic marks, multiple on one note
260 @lilypond[verbatim,quote,relative=2]
262 << f1 { s4 s4\< s4\> s4\! } >>
265 @cindex espressivo articulation
267 @funindex \espressivo
270 In some situations the @code{\espressivo} articulation mark may be
271 the appropriate choice to indicate a crescendo and decrescendo on
274 @lilypond[verbatim,quote,relative=2]
280 @funindex \crescTextCresc
281 @funindex crescTextCresc
282 @funindex \dimTextDecresc
283 @funindex dimTextDecresc
284 @funindex \dimTextDecr
285 @funindex dimTextDecr
286 @funindex \dimTextDim
288 @funindex \crescHairpin
289 @funindex crescHairpin
290 @funindex \dimHairpin
293 Crescendos and decrescendos can be engraved as textual markings
294 instead of hairpins. Dashed lines are printed to indicate their
295 extent. The built-in commands @code{\crescTextCresc},
296 @code{\dimTextDecresc}, @code{\dimTextDecr}, and @code{\dimTextDim}
297 will tell LilyPond to use such textual marks instead of hairpins
298 for all subsequent @code{\<} and @code{\>} commands. The corresponding
299 @code{\crescHairpin} and @code{\dimHairpin} commands will revert
302 @lilypond[verbatim,quote,relative=2]
314 To create new absolute dynamic marks or text that should be
315 aligned with dynamics, see @ref{New dynamic marks}.
317 @cindex dynamics, vertical positioning
318 @cindex vertical positioning of dynamics
320 @funindex DynamicLineSpanner
323 Vertical positioning of dynamics is handled by
324 @rinternals{DynamicLineSpanner}.
327 @funindex \dynamicDown
328 @funindex dynamicDown
329 @funindex \dynamicNeutral
330 @funindex dynamicNeutral
336 @code{\dynamicNeutral},
337 @code{\crescTextCresc},
340 @code{\dimTextDecresc},
341 @code{\crescHairpin},
348 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
349 {setting-hairpin-behavior-at-bar-lines.ly}
351 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
352 {setting-the-minimum-length-of-hairpins.ly}
357 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
358 {printing-hairpins-using-al-niente-notation.ly}
360 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
361 {vertically-aligned-dynamics-and-textscripts.ly}
363 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
364 {hiding-the-extender-line-for-text-dynamics.ly}
366 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
367 {changing-text-and-spanner-styles-for-text-dynamics.ly}
378 @rlearning{Articulation and dynamics}.
381 @ref{Direction and placement},
382 @ref{New dynamic marks},
383 @ref{What goes into the MIDI output?},
384 @ref{Controlling MIDI dynamics}.
387 @rlsr{Expressive marks}.
390 @rinternals{DynamicText},
391 @rinternals{Hairpin},
392 @rinternals{DynamicLineSpanner}.
395 @node New dynamic marks
396 @unnumberedsubsubsec New dynamic marks
398 @cindex new dynamic marks
399 @cindex dynamic marks, new
401 The easiest way to create dynamic indications is to use
402 @code{\markup} objects.
404 @lilypond[verbatim,quote]
405 moltoF = \markup { molto \dynamic f }
408 <d e>16_\moltoF <d e>
413 @cindex dynamics, editorial
414 @cindex dynamics, parenthesis
415 @cindex editorial dynamics
421 In markup mode, editorial dynamics (within parentheses or square
422 brackets) can be created. The syntax for markup mode is described
423 in @ref{Formatting text}.
425 @lilypond[verbatim,quote]
426 roundF = \markup { \center-align \concat { \bold { \italic ( }
427 \dynamic f \bold { \italic ) } } }
428 boxF = \markup { \bracket { \dynamic f } }
435 @cindex make-dynamic-script
436 @funindex make-dynamic-script
438 Simple, centered dynamic marks are easily created with the
439 @code{make-dynamic-script} function.
441 @lilypond[verbatim,quote]
442 sfzp = #(make-dynamic-script "sfzp")
448 In general, @code{make-dynamic-script} takes any markup object as its
449 argument. The dynamic font only contains the characters
450 @code{f,m,p,r,s} and @code{z}, so if a dynamic mark that includes
451 plain text or punctuation symbols is desired, markup commands that
452 reverts font family and font encoding to normal text should be used,
453 for example @code{\normal-text}. The interest of using
454 @code{make-dynamic-script} instead of an ordinary markup is ensuring
455 the vertical alignment of markup objects and hairpins that are
456 attached to the same note head.
458 @lilypond[verbatim,quote]
459 roundF = \markup { \center-align \concat {
460 \normal-text { \bold { \italic ( } }
462 \normal-text { \bold { \italic ) } } } }
463 boxF = \markup { \bracket { \dynamic f } }
464 mfEspress = \markup { \center-align \line {
465 \hspace #3.7 mf \normal-text \italic espress. } }
466 roundFdynamic = #(make-dynamic-script roundF)
467 boxFdynamic = #(make-dynamic-script boxF)
468 mfEspressDynamic = #(make-dynamic-script mfEspress)
470 c4_\roundFdynamic\< d e f
478 The Scheme form of markup mode may be used instead. Its syntax is
479 explained in @rextend{Markup construction in Scheme}.
481 @lilypond[verbatim,quote]
482 moltoF = #(make-dynamic-script
483 (markup #:normal-text "molto"
491 Font settings in markup mode are described in
492 @ref{Selecting font and font size}.
497 @ref{Formatting text},
498 @ref{Selecting font and font size},
499 @ref{What goes into the MIDI output?},
500 @ref{Controlling MIDI dynamics}.
503 @rlsr{Expressive marks}.
506 @rextend{Markup construction in Scheme}.
513 This section explains how to create various expressive marks that
514 are curved: normal slurs, phrasing slurs, breath marks, falls, and
525 @unnumberedsubsubsec Slurs
529 @notation{Slurs} are entered using parentheses:
531 @warning{In polyphonic music, a slur must be terminated
532 in the same voice it began.}
534 @lilypond[verbatim,quote,relative=2]
540 @cindex slurs, manual placement
541 @cindex slurs, below notes
542 @cindex slurs, above notes
545 @funindex \slurNeutral
546 @funindex slurNeutral
548 Slurs may be manually placed above or below the staff; see
549 @ref{Direction and placement}.
551 @cindex phrasing slur
552 @cindex multiple slurs
553 @cindex simultaneous slurs
554 @cindex slur, phrasing
555 @cindex slurs, multiple
556 @cindex slurs, simultaneous
558 Simultaneous or overlapping slurs are not permitted, but a phrasing
559 slur can overlap a slur. This permits two slurs to be printed at
560 once. For details, see @ref{Phrasing slurs}.
570 @funindex \slurDashed
572 @funindex \slurDotted
577 Slurs can be solid, dotted, or dashed. Solid is the default slur
580 @lilypond[verbatim,quote,relative=1]
590 @funindex \slurHalfDashed
591 @funindex slurHalfDashed
592 @funindex \slurHalfSolid
593 @funindex slurHalfSolid
594 @cindex slur, half dashed and half solid
596 Slurs can also be made half-dashed (the first half dashed, the
597 second half solid) or half-solid (the first half solid, the second
600 @lilypond[verbatim,quote,relative=1]
610 @funindex \slurDashPattern
611 @funindex slurDashPattern
612 @cindex slur, defining dash patterns
614 Custom dash patterns for slurs can be defined:
616 @lilypond[verbatim,quote,relative=1]
618 \slurDashPattern #0.7 #0.75
620 \slurDashPattern #0.5 #2.0
638 @code{\slurHalfDashed},
639 @code{\slurHalfSolid},
640 @code{\slurDashPattern},
647 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
648 {using-double-slurs-for-legato-chords.ly}
650 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
651 {positioning-text-markups-inside-slurs.ly}
653 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
654 {making-slurs-with-complex-dash-structure.ly}
662 @rlearning{On the un-nestedness of brackets and ties}.
665 @ref{Direction and placement},
666 @ref{Phrasing slurs}.
669 @rlsr{Expressive marks}.
676 @unnumberedsubsubsec Phrasing slurs
678 @cindex phrasing slurs
679 @cindex phrasing marks
680 @cindex slur, phrasing
681 @cindex mark, phrasing
685 @notation{Phrasing slurs} (or phrasing marks) that indicate a
686 musical sentence are written using the commands @code{\(} and
687 @code{\)} respectively:
689 @lilypond[verbatim,quote,relative=2]
694 @funindex \phrasingSlurUp
695 @funindex phrasingSlurUp
696 @funindex \phrasingSlurDown
697 @funindex phrasingSlurDown
698 @funindex \phrasingSlurNeutral
699 @funindex phrasingSlurNeutral
701 Typographically, a phrasing slur behaves almost exactly like a
702 normal slur. However, they are treated as different objects; a
703 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
704 may be manually placed above or below the staff; see
705 @ref{Direction and placement}.
707 @cindex simultaneous phrasing slurs
708 @cindex multiple phrasing slurs
709 @cindex slur, simultaneous phrasing
710 @cindex slur, multiple phrasing
711 @cindex phrasing slur, simultaneous
712 @cindex phrasing slur, multiple
714 Simultaneous or overlapping phrasing slurs are not permitted.
716 @funindex phrasingSlurDashed
717 @funindex \phrasingSlurDashed
718 @funindex \phrasingSlurDotted
719 @funindex phrasingSlurDotted
720 @funindex \phrasingSlurSolid
721 @funindex phrasingSlurSolid
722 @cindex phrasing slur, dashed
723 @cindex dashed phrasing slur
724 @cindex phrasing slur, dotted
725 @cindex dotted phrasing slurs
726 @cindex slur, dashed phrasing
727 @cindex slur, dotted phrasing
729 Phrasing slurs can be solid, dotted, or dashed. Solid is the default
730 style for phrasing slurs:
732 @lilypond[verbatim,quote,relative=1]
742 @funindex phrasingSlurHalfDashed
743 @funindex \phrasingSlurHalfDashed
744 @funindex \phrasingSlurHalfSolid
745 @funindex phrasingSlurHalfSolid
746 @cindex phrasing slur, half solid and half dashed
747 @cindex slur, half solid and half dashed phrasing
749 Phrasing slurs can also be made half-dashed (the first half dashed, the
750 second half solid) or half-solid (the first half solid, the second
753 @lilypond[verbatim,quote,relative=1]
755 \phrasingSlurHalfDashed
757 \phrasingSlurHalfSolid
763 @funindex \phrasingSlurDashPattern
764 @funindex phrasingSlurDashPattern
765 @cindex phrasing slur, defining dash patterns
766 @cindex slur, phrasing, defining dash patterns
767 @cindex slur, definind dash patterns for phrasing
769 Custom dash patterns for phrasing slurs can be defined:
771 @lilypond[verbatim,quote,relative=1]
773 \phrasingSlurDashPattern #0.7 #0.75
775 \phrasingSlurDashPattern #0.5 #2.0
781 Dash pattern definitions for phrasing slurs have the same structure
782 as dash pattern definitions for slurs. For more information about
783 complex dash patterns, see the snippets under @ref{Slurs}.
786 @code{\phrasingSlurUp},
787 @code{\phrasingSlurDown},
788 @code{\phrasingSlurNeutral},
789 @code{\phrasingSlurDashed},
790 @code{\phrasingSlurDotted},
791 @code{\phrasingSlurHalfDashed},
792 @code{\phrasingSlurHalfSolid},
793 @code{\phrasingSlurDashPattern},
794 @code{\phrasingSlurSolid}.
800 @rlearning{On the un-nestedness of brackets and ties}.
803 @ref{Direction and placement},
807 @rlsr{Expressive marks}.
810 @rinternals{PhrasingSlur}.
814 @unnumberedsubsubsec Breath marks
821 Breath marks are entered using @code{\breathe}:
823 @lilypond[verbatim,quote,relative=2]
827 A breath mark will end an automatic beam; to override this behavior, see
830 @lilypond[verbatim,quote,relative=2]
834 Musical indicators for breath marks in ancient notation,
835 divisiones, are supported. For details, see @ref{Divisiones}.
840 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
841 {changing-the-breath-mark-symbol.ly}
844 @cindex railroad tracks
846 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
847 {inserting-a-caesura.ly}
858 @rlsr{Expressive marks}.
861 @rinternals{BreathingEvent},
862 @rinternals{BreathingSign},
863 @rinternals{Breathing_sign_engraver}.
866 @node Falls and doits
867 @unnumberedsubsubsec Falls and doits
874 @notation{Falls} and @notation{doits} can be added to notes using
875 the @code{\bendAfter} command. The direction of the fall or doit
876 is indicated with a plus or minus (up or down). The number
877 indicates the pitch interval that the fall or doit will extend
878 @emph{beyond} the main note.
880 @lilypond[verbatim,quote,relative=2]
887 The dash @code{-} immediately preceding the @code{\bendAfter}
888 command is @emph{required} when writing falls and doits.
893 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
894 {adjusting-the-shape-of-falls-and-doits.ly}
903 @rlsr{Expressive marks}.
909 This section explains how to create various expressive marks that
910 follow a linear path: glissandos, arpeggios, and trills.
919 @unnumberedsubsubsec Glissando
925 A @notation{glissando} is created by attaching @code{\glissando}
928 @lilypond[verbatim,quote,relative=2]
933 Different styles of glissandi can be created. For details, see
938 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
939 {contemporary-glissando.ly}
950 @rlsr{Expressive marks}.
953 @rinternals{Glissando}.
958 Printing text over the line (such as @notation{gliss.}) is not
963 @unnumberedsubsubsec Arpeggio
967 @cindex chord, broken
971 @funindex \arpeggioArrowUp
972 @funindex arpeggioArrowUp
973 @funindex \arpeggioArrowDown
974 @funindex arpeggioArrowDown
975 @funindex \arpeggioNormal
976 @funindex arpeggioNormal
978 An @notation{arpeggio} on a chord (also known as a broken chord)
979 is denoted by appending @code{\arpeggio} to the chord construct:
981 @lilypond[verbatim,quote,relative=1]
985 Different types of arpeggios may be written.
986 @code{\arpeggioNormal} reverts to a normal arpeggio:
988 @lilypond[verbatim,quote,relative=1]
1001 @cindex arpeggio symbols, special
1002 @cindex special arpeggio symbols
1004 @funindex \arpeggioBracket
1005 @funindex arpeggioBracket
1006 @funindex \arpeggioParenthesis
1007 @funindex arpeggioParenthesis
1008 @funindex \arpeggioParenthesisDashed
1009 @funindex arpeggioParenthesisDashed
1011 Special @emph{bracketed} arpeggio symbols can be created:
1013 @lilypond[verbatim,quote,relative=1]
1019 \arpeggioParenthesis
1022 \arpeggioParenthesisDashed
1029 The dash properties of the parenthesis arpeggio are controlled
1030 with the @code{'dash-details} property, which is described at @ref{Slurs}.
1032 Arpeggios can be explicitly written out with ties. For more
1033 information, see @ref{Ties}.
1038 @code{\arpeggioArrowUp},
1039 @code{\arpeggioArrowDown},
1040 @code{\arpeggioNormal},
1041 @code{\arpeggioBracket},
1042 @code{\arpeggioParenthesis}
1043 @code{\arpeggioParenthesisDashed}.
1049 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1050 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
1052 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1053 {creating-cross-staff-arpeggios-in-other-contexts.ly}
1055 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1056 {creating-arpeggios-across-notes-in-different-voices.ly}
1068 @rlsr{Expressive marks}.
1070 Internals Reference:
1071 @rinternals{Arpeggio},
1073 @rinternals{PianoStaff}.
1078 @cindex cross-staff parenthesis-style arpeggio
1079 @cindex arpeggio, parenthesis-style, cross-staff
1080 @cindex arpeggio, cross-staff parenthesis-style
1082 It is not possible to mix connected arpeggios and unconnected
1083 arpeggios in one @code{PianoStaff} at the same point in
1086 The parenthesis-style arpeggio brackets do not work for
1087 cross-staff arpeggios.
1091 @unnumberedsubsubsec Trills
1097 @funindex \startTrillSpan
1098 @funindex startTrillSpan
1099 @funindex \stopTrillSpan
1100 @funindex stopTrillSpan
1102 Short @notation{trills} without an extender line are printed with
1103 @code{\trill}; see @ref{Articulations and ornamentations}.
1105 Longer trills with an extender line are made with
1106 @code{\startTrillSpan} and @code{\stopTrillSpan}:
1108 @lilypond[verbatim,quote,relative=2]
1114 In the following example, a trill is combined with grace notes.
1115 The syntax of this construct and the method to precisely position
1116 the grace notes are described in @ref{Grace notes}.
1118 @lilypond[verbatim,quote,relative=2]
1120 d1\startTrillSpan { c32[ d]\stopTrillSpan }
1124 @cindex pitched trills
1125 @cindex trills, pitched
1126 @funindex \pitchedTrill
1127 @funindex pitchedTrill
1129 Trills that require an auxiliary note with an explicit pitch can
1130 be typeset with the @code{\pitchedTrill} command. The first
1131 argument is the main note, and the second is the @emph{trilled}
1132 note, printed as a stemless note head in parentheses.
1134 @lilypond[verbatim,quote,relative=1]
1135 \pitchedTrill e2\startTrillSpan fis
1139 @cindex pitched trill with forced accidental
1140 @cindex trill, pitched with forced accidental
1141 @cindex accidental, forced for pitched trill
1143 In the following example, the second pitched trill is ambiguous;
1144 the accidental of the trilled note is not printed. As a
1145 workaround, the accidentals of the trilled notes can be forced.
1146 The second measure illustrates this method:
1148 @lilypond[verbatim,quote,relative=2]
1149 \pitchedTrill eis4\startTrillSpan fis
1151 \pitchedTrill eis4\startTrillSpan fis
1153 \pitchedTrill eis4\startTrillSpan fis
1155 \pitchedTrill eis4\startTrillSpan fis!
1161 @code{\startTrillSpan},
1162 @code{\stopTrillSpan}.
1171 @ref{Articulations and ornamentations},
1175 @rlsr{Expressive marks}.
1177 Internals Reference:
1178 @rinternals{TrillSpanner}.