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.
11 @node Expressive marks
12 @section Expressive marks
14 @lilypondfile[quote]{expressive-headword.ly}
16 This section lists various expressive marks that can be
26 @node Attached to notes
27 @subsection Attached to notes
29 This section explains how to create expressive marks that are
30 attached to notes: articulations, ornamentations, and dynamics.
31 Methods to create new dynamic markings are also discussed.
34 * Articulations and ornamentations::
39 @node Articulations and ornamentations
40 @unnumberedsubsubsec Articulations and ornamentations
50 @cindex organ pedal marks
68 A variety of symbols that denote articulations, ornamentations,
69 and other performance indications can be attached to a note using
76 The possible values for @var{name} are listed in @ref{List of
77 articulations}. For example:
79 @lilypond[verbatim,quote,relative=2]
80 c4\staccato c\mordent b2\turn
92 Some of these articulations have shorthands for easier entry.
93 Shorthands are appended to the note name, and their syntax
94 consists of a dash (@tie{}@code{-}) followed by a symbol
95 signifying the articulation. Predefined shorthands exist for
96 @notation{marcato}, @notation{stopped}, @notation{tenuto},
97 @notation{staccatissimo}, @notation{accent}, @notation{staccato},
98 and @notation{portato}. Their corresponding output appears as
101 @lilypond[verbatim,quote,relative=2]
106 The rules for the default placement of articulations are defined
107 in @file{scm/@/script@/.scm}. Articulations and ornamentations
108 may be manually placed above or below the staff, see
109 @ref{Direction and placement}.
114 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
115 {modifying-default-values-for-articulation-shorthand-notation.ly}
117 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
118 {controlling-the-vertical-ordering-of-scripts.ly}
130 @ref{Direction and placement},
131 @ref{List of articulations}.
134 @file{scm/@/script@/.scm}.
137 @rlsr{Expressive marks}.
141 @rinternals{TextScript}.
146 These signs appear in the printed output but have no effect on the
147 MIDI rendering of the music.
151 @unnumberedsubsubsec Dynamics
153 @cindex absolute dynamics
155 @cindex dynamics, absolute
175 Absolute dynamic marks are specified using a command after a note,
176 such as @code{c4\ff}. The available dynamic marks are
177 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
178 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
179 @code{\ffff}, @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp},
180 @code{\spp}, @code{\sfz}, and @code{\rfz}. The dynamic marks may
181 be manually placed above or below the staff, see
182 @ref{Direction and placement}.
184 @lilypond[verbatim,quote,relative=2]
197 A @notation{crescendo} mark is started with @code{\<} and
198 terminated with @code{\!}, an absolute dynamic, or an additional
199 crescendo or decrescendo mark. A @notation{decrescendo} mark is
200 started with @code{\>} and is also terminated with @code{\!}, an
201 absolute dynamic, or another crescendo or decrescendo mark.
202 @code{\cr} and @code{\decr} may be used instead of @code{\<} and
203 @code{\>}. @notation{Hairpins} are engraved by default using this
206 @lilypond[verbatim,quote,relative=2]
216 Spacer rests are needed to engrave multiple marks on one note.
218 @lilypond[verbatim,quote,relative=2]
220 << f1 { s4 s4\< s4\> s4\! } >>
223 @cindex espressivo articulation
225 In some situations the @code{\espressivo} articulation mark may be
226 the appropriate choice to indicate a crescendo and decrescendo on
229 @lilypond[verbatim,quote,relative=2]
238 Crescendos and decrescendos can be engraved as textual markings
239 instead of hairpins. The built-in commands that enable these text
240 modes are @code{\crescTextCresc}, @code{\dimTextDecresc},
241 @code{\dimTextDecr}, and @code{\dimTextDim}. The corresponding
242 @code{\crescHairpin}, @code{\setHairpinDim}, and
243 @code{\dimHairpin} commands will revert to hairpins again:
245 @lilypond[verbatim,quote,relative=2]
256 To create new absolute dynamic marks or text that should be
257 aligned with dynamics, see @ref{New dynamic marks}.
259 Vertical positioning of dynamics is handled by
260 @rinternals{DynamicLineSpanner}.
267 @funindex \dynamicDown
269 @funindex \dynamicNeutral
270 @code{\dynamicNeutral},
271 @funindex \crescTextCresc
272 @code{\crescTextCresc},
273 @funindex \dimTextDim
275 @funindex \dimTextDecr
277 @funindex \dimTextDecresc
278 @code{\dimTextDecresc},
279 @funindex \crescHairpin
280 @code{\crescHairpin},
281 @funindex \setHairpinDim
282 @code{\setHairpinDim},
283 @funindex \dimHairpin
289 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
290 {setting-hairpin-behavior-at-bar-lines.ly}
292 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
293 {setting-the-minimum-length-of-hairpins.ly}
298 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
299 {printing-hairpins-using-al-niente-notation.ly}
301 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
302 {vertically-aligning-dynamics-across-multiple-notes.ly}
304 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
305 {hiding-the-extender-line-for-text-dynamics.ly}
307 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
308 {changing-text-and-spanner-styles-for-text-dynamics.ly}
313 @c TODO: Add hairpin to glossary.
320 @rlearning{Articulation and dynamics}.
323 @ref{Direction and placement},
324 @ref{New dynamic marks}.
327 @rlsr{Expressive marks}.
330 @rinternals{DynamicText},
331 @rinternals{Hairpin},
332 @rinternals{DynamicLineSpanner}.
335 @node New dynamic marks
336 @unnumberedsubsubsec New dynamic marks
338 @cindex new dynamic marks
339 @cindex dynamic marks, new
341 The easiest way to create dynamic indications is to use
342 @code{\markup} objects.
344 @lilypond[verbatim,quote]
345 moltoF = \markup { molto \dynamic f }
353 @cindex dynamics, editorial
354 @cindex dynamics, parenthesis
356 Markup mode makes possible, for instance, to add
357 editorial dynamics, printed in round parenthesis or square
358 brackets. Its syntax is described in @ref{Formatting text}.
360 @lilypond[verbatim,quote]
361 roundf = \markup { \center-align { \line { \bold { \italic ( }
362 \dynamic f \bold { \italic ) } } } }
363 boxf = \markup { \bracket { \dynamic f } }
370 Markup objects are treated differently from authentic dynamic marks.
371 Defining dynamic objects that will be entered and printed exactly like
372 standard dynamic marks is also possible, using the following function:
374 @cindex make-dynamic-script
376 @lilypond[verbatim,quote]
377 sfzp = #(make-dynamic-script "sfzp")
384 Note that the dynamic font only contains the characters
385 @code{f,m,p,r,s} and @code{z}. To switch to other font families,
386 it is necessary to use markup mode in its Scheme form, as
387 explained in @ref{Markup construction in Scheme}.
389 @lilypond[verbatim,quote]
390 moltoF = #(make-dynamic-script (markup
391 #:normal-text "molto"
400 Font settings in markup mode are described in
401 @ref{Common markup commands}.
407 @ref{Formatting text},
408 @ref{Common markup commands},
409 @ref{Markup construction in Scheme}.
412 @rlsr{Expressive marks}.
418 This section explains how to create various expressive marks that
419 are curved: normal slurs, phrasing slurs, breath marks, falls, and
430 @unnumberedsubsubsec Slurs
434 @notation{Slurs} are entered using parentheses:
436 @lilypond[verbatim,quote,relative=2]
442 Slurs may be manually placed above or below the notes, see
443 @ref{Direction and placement}.
445 @lilypond[verbatim,quote,relative=2]
453 Phrasing slurs must be used to print more than one slur at once.
454 For details, see @ref{Phrasing slurs}.
456 Slurs can be solid, dotted, or dashed. Solid is the default slur
459 @lilypond[verbatim,quote,relative=1]
476 @funindex \slurNeutral
478 @funindex \slurDashed
480 @funindex \slurDotted
488 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
489 {using-double-slurs-for-legato-chords.ly}
498 @ref{Direction and placement},
499 @ref{Phrasing slurs}.
502 @rlsr{Expressive marks}.
509 @unnumberedsubsubsec Phrasing slurs
511 @cindex phrasing slurs
512 @cindex phrasing marks
516 @notation{Phrasing slurs} (or phrasing marks) that indicate a
517 musical sentence are written using the commands @code{\(} and
518 @code{\)} respectively:
520 @lilypond[verbatim,quote,relative=2]
525 Typographically, a phrasing slur behaves almost exactly like a
526 normal slur. However, they are treated as different objects; a
527 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
528 slurs may be manually placed above or below the notes, see
529 @ref{Direction and placement}.
531 @lilypond[verbatim,quote,relative=1]
532 c4\( g' c,( b) | c1\)
534 c4\( g' c,( b) | c1\)
537 Simultaneous phrasing slurs are not permitted.
542 @funindex \phrasingSlurUp
543 @code{\phrasingSlurUp},
544 @funindex \phrasingSlurDown
545 @code{\phrasingSlurDown},
546 @funindex \phrasingSlurNeutral
547 @code{\phrasingSlurNeutral}.
553 @ref{Direction and placement}.
556 @rlsr{Expressive marks}.
559 @rinternals{PhrasingSlur}.
563 @unnumberedsubsubsec Breath marks
568 Breath marks are entered using @code{\breathe}:
570 @lilypond[verbatim,quote,relative=2]
574 Musical indicators for breath marks in ancient notation,
575 divisiones, are supported. For details, see @ref{Divisiones}.
580 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
581 {changing-the-breath-mark-symbol.ly}
584 @cindex railroad tracks
587 @c @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
588 @c {inserting-a-caesura.ly}
590 Caesura marks can be created by overriding the @code{'text}
591 property of the @code{BreathingSign} object. A curved caesura
592 mark is also available.
594 @lilypond[verbatim,quote,relative=2]
595 \override BreathingSign #'text =
596 #(make-musicglyph-markup "scripts.caesura.straight")
597 c8 e4. \breathe g8. e16 c4
599 \override BreathingSign #'text =
600 #(make-musicglyph-markup "scripts.caesura.curved")
601 g8 e'4. \breathe g8. e16 c4
611 @rlsr{Expressive marks}.
612 @c @lsr{expressive,breathing-sign.ly}.
615 @rinternals{BreathingSign}.
618 @node Falls and doits
619 @unnumberedsubsubsec Falls and doits
625 @notation{Falls} and @notation{doits} can be added to notes using
626 the @code{\bendAfter} command. The direction of the fall or doit
627 is indicated with a plus or minus (up or down). The number
628 indicates the pitch interval that the fall or doit will extend
629 @emph{beyond} the main note.
631 @lilypond[verbatim,quote,relative=2]
638 The dash (@tie{-}) immediately preceding the @code{\bendAfter}
639 command is @emph{required} when writing falls and doits.
644 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
645 {adjusting-the-shape-of-falls-and-doits.ly}
650 @c TODO: add falls and doits to glossary.
656 @rlsr{Expressive marks}.
662 This section explains how to create various expressive marks that
663 follow a linear path: glissandos, arpeggios, and trills.
672 @unnumberedsubsubsec Glissando
677 A @notation{glissando} is created by attaching @code{\glissando}
680 @lilypond[verbatim,quote,relative=2]
685 Different styles of glissandi can be created. For details, see
690 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
691 {contemporary-glissando.ly}
703 @rlsr{Expressive marks}.
705 @c FIXME: I need to figure out what's up with these. -gp
706 @c @lsr{expressive,glissando.ly},
707 @c @lsr{expressive,line-styles.ly}
710 @rinternals{Glissando}.
715 Printing text over the line (such as @emph{gliss.}) is not
720 @unnumberedsubsubsec Arpeggio
724 @cindex chord, broken
726 An @notation{arpeggio} on a chord (also known as a broken chord)
727 is denoted by appending @code{\arpeggio} to the chord construct:
729 @lilypond[verbatim,quote,relative=1]
733 The direction of an arpeggio is indicated by adding an arrowhead
734 to the wiggly line. The commands @code{\arpeggioArrowUp} and
735 @code{\arpeggioArrowDown} are used for this task.
736 @code{\arpeggioNormal} reverts back to an arrow-less arpeggio:
738 @lilypond[verbatim,quote,relative=1]
747 The command @code{\arpeggioBracket} can be used to create a square
748 bracket on the left of a chord, indicating that the chord should
749 @emph{not} be arpeggiated. @code{\arpeggioNormal} reverts back
750 to a regular arpeggio:
752 @lilypond[verbatim,quote,relative=1]
760 A @emph{parenthesis} style bracket may be attached to a chord
761 construct instead of a square bracket.
763 @c Maybe create a new \arpeggioParen command, or something
766 @lilypond[verbatim,quote,relative=1]
768 \override Arpeggio #'stencil = #ly:arpeggio::brew-chord-slur
769 \override Arpeggio #'X-extent = #ly:grob::stencil-width
775 Arpeggios can be explicitly written out with ties. For more
776 information, see @ref{Ties}.
782 @funindex \arpeggioArrowUp
783 @code{\arpeggioArrowUp},
784 @funindex \arpeggioArrowDown
785 @code{\arpeggioArrowDown},
786 @funindex \arpeggioNormal
787 @code{\arpeggioNormal},
788 @funindex \arpeggioBracket
789 @code{\arpeggioBracket}.
794 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
795 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
797 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
798 {creating-cross-staff-arpeggios-in-other-contexts.ly}
800 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
801 {creating-arpeggios-across-notes-in-different-voices.ly}
813 @rlsr{Expressive marks}.
816 @rinternals{Arpeggio},
817 @rinternals{PianoStaff}.
822 It is not possible to mix connected arpeggios and unconnected
823 arpeggios in one @code{PianoStaff} at the same point in
826 The parenthesis-style arpeggio brackets do not work for
827 cross-staff arpeggios.
831 @unnumberedsubsubsec Trills
836 Short @notation{trills} without an extender line are printed with
837 @code{\trill}; see @ref{Articulations and ornamentations}.
839 Long running trills are made with @code{\startTrillSpan} and
840 @code{\stopTrillSpan}. In the following example, a long running
841 trill is shown combined with grace notes. To achieve precise
842 control of the placement of the grace notes, see @ref{Grace
845 @lilypond[verbatim,quote,relative=2]
847 d1\startTrillSpan { c16[\stopTrillSpan d] }
851 @cindex pitched trills
852 @cindex trills, pitched
854 Trills that should be executed on an explicitly specified pitch
855 can be typeset with the command @code{\pitchedTrill} using the
859 @code{\pitchedTrill} @var{mainnote} @code{\startTrillSpan}
860 @var{trillnote} @var{endnote} @code{\stopTrillSpan}
863 @lilypond[verbatim,quote,relative=1]
864 \pitchedTrill e2 \startTrillSpan fis
869 The first argument is the main note. The pitch of the second is
870 printed as a stemless note head in parentheses.
875 @code{\startTrillSpan},
876 @funindex \startTrillSpan
877 @code{\stopTrillSpan}.
878 @funindex \stopTrillSpan
887 @ref{Articulations and ornamentations},
891 @rlsr{Expressive marks}.
894 @rinternals{TrillSpanner}.