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}
23 @node Attached to notes
24 @subsection Attached to notes
27 * Articulations and ornamentations::
32 @node Articulations and ornamentations
33 @subsubsection Articulations and ornamentations
43 @cindex organ pedal marks
61 A variety of symbols that denote articulations, ornamentations,
62 and other performance indications can be attached to a note using
69 The possible values for @var{name} are listed in @ref{List of
70 articulations}. For example:
72 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
73 c4\staccato c\mordent b2\turn
85 Some of these articulations have shorthands for easier entry.
86 Shorthands are appended to the note name, and their syntax
87 consists of a dash (@tie{}@code{-}) followed by a symbol
88 signifying the articulation. Predefined shorthands exist for
89 @notation{marcato}, @notation{stopped}, @notation{tenuto},
90 @notation{staccatissimo}, @notation{accent}, @notation{staccato},
91 and @notation{portato}. Their corresponding output appears as
94 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
99 The rules for the default placement of articulations are defined
100 in @file{scm/@/script@/.scm}. Articulations and ornamentations
101 may be manually placed above or below the staff, see
102 @ref{Controlling direction and placement}.
107 @c After next LSR update, this snippet can be used
108 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
109 @c {modifying-default-values-for-articulation-shorthand-notation.ly}
111 The shorthands are defined in @file{ly/@/script@/-init@/.ly},
112 where the variables @code{dashHat}, @code{dashPlus},
113 @code{dashDash}, @code{dashBar}, @code{dashLarger},
114 @code{dashDot}, and @code{dashUnderscore} are assigned default
115 values. The default values for the shorthands can be modified.
116 For example, to associate the @code{-+} (@code{dashPlus})
117 shorthand with the @notation{trill} symbol instead of the default
118 @notation{+} symbol, assign the value @code{trill} to the variable
121 @lilypond[verbatim,quote,ragged-right]
122 \relative c'' { c-+ }
124 \relative c'' { c-+ }
127 @c After next LSR update, this snippet can be used
128 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
129 @c {controlling-the-vertical-ordering-of-scripts.ly}
131 The vertical ordering of scripts is controlled with the
132 @code{script-priority} property. The lower this number, the
133 closer it will be put to the note. In this example, the
134 @code{TextScript} (the sharp symbol) first has the lowest
135 priority, so it is put lowest in the first example. In the
136 second, the @notation{prall trill} (the @code{Script}) has the
137 lowest, so it is on the inside. When two objects have the same
138 priority, the order in which they are entered decides which one
141 @lilypond[verbatim,quote,ragged-right,fragment,relative=3]
142 \once \override TextScript #'script-priority = #-100
143 a4^\prall^\markup { \sharp }
145 \once \override Script #'script-priority = #-100
146 a4^\prall^\markup { \sharp }
159 @ref{Controlling direction and placement}.
162 @file{scm/@/script@/.scm}.
165 @rlsr{Expressive marks}.
169 @rinternals{TextScript}.
174 These signs appear in the printed output but have no effect on the
175 MIDI rendering of the music.
179 @subsubsection Dynamics
181 @cindex absolute dynamics
183 @cindex dynamics, absolute
203 Absolute dynamic marks are specified using a command after a note,
204 such as @code{c4\ff}. The available dynamic marks are
205 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
206 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
207 @code{\ffff}, @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp},
208 @code{\spp}, @code{\sfz}, and @code{\rfz}. The dynamic marks may
209 be manually placed above or below the staff, see @ref{Controlling
210 direction and placement}.
212 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
225 A @notation{crescendo} mark is started with @code{\<} and
226 terminated with @code{\!}, an absolute dynamic, or an additional
227 @notation{crescendo} or @notation{decrescendo} mark. A
228 @notation{decrescendo} mark is started with @code{\>} and is also
229 terminated with @code{\!}, an absolute dynamic, or another
230 @notation{crescendo} or @notation{decrescendo} mark. @code{\cr}
231 and @code{\decr} may be used instead of @code{\<} and @code{\>}.
232 @notation{Hairpins} are engraved by default using this notation.
234 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
244 Spacer notes are needed to engrave multiple marks on one note.
246 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
248 << f1 { s4 s4\< s4\> s4\! } >>
251 @cindex espressivo articulation
253 In some situations the @code{\espressivo} articulation mark may be
254 the appropriate choice to indicate a @notation{crescendo} and
255 @notation{decrescendo} on one note:
257 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
265 @funindex \setTextCresc
266 @funindex \setTextDim
267 @funindex \setTextDecr
268 @funindex \setTextDecresc
269 @funindex \setHairpinCresc
270 @funindex \setHairpinDim
271 @funindex \setHairpinDecresc
273 @notation{Crescendos} and @notation{decrescendos} can be engraved
274 as textual markings instead of hairpins. The built-in commands
275 that enable these text modes are @code{\setTextCresc},
276 @code{\setTextDecresc}, @code{\setTextDecr}, and
277 @code{\setTextDim}. The corresponding @code{\setHairpinCresc},
278 @code{\setHairpinDim}, and @code{\setHairpinDecresc} commands will
279 revert to hairpins again:
281 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
292 To create new absolute dynamic marks or text that should be
293 aligned with dynamics, see @ref{New dynamic marks}.
295 Vertical positioning of dynamics is handled by
296 @rinternals{DynamicLineSpanner}.
303 @funindex \dynamicDown
305 @funindex \dynamicNeutral
306 @code{\dynamicNeutral}.
311 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
312 {setting-hairpin-behavior-at-bar-lines.ly}
314 @c After next LSR update, this snippet can be used
315 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
316 @c {setting-the-minimum-length-of-hairpins.ly}
318 If hairpins are too short, they can be lengthened using the
321 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
323 \override Voice.Hairpin #'minimum-length = #5
324 << f1 { s4 s4\< s4\> s4\! } >>
330 @c After next LSR update, this snippet can be used
331 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
332 @c {printing-hairpins-using-al-niente-notation.ly}
334 Hairpins may be printed with a circled tip (al niente notation):
336 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
337 \override Hairpin #'circled-tip = ##t
342 @c After next LSR update, this snippet can be used
343 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
344 @c {vertically-aligning-dynamics-across-multiple-notes.ly}
346 Dynamics that occur at, begin on, or end on the same note will be
347 vertically aligned. If you want to ensure that dynamics are
348 aligned when they do not occur on the same note, you can increase
349 the @code{staff-padding} property.
352 \override DynamicLineSpanner #'staff-padding = #4
355 @c I can't figure this one out. Consider removing this. -pm
357 @notation{Crescendi} and @notation{decrescendi} that cross a line
358 break will be continued on the second line. If they end on the
359 first note of a new line, nothing will be printed on that line.
360 To change this behavior, use
363 \override Score.Hairpin #'after-line-breaking = ##t
366 @c After next LSR update, this snippet can be used
367 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
368 @c {hiding-the-extender-line-for-text-dynamics.ly}
370 Text style dynamic changes (such as @notation{cresc.} and
371 @notation{dim.}) are printed with a dashed line showing their
372 extent. To suppress printing this line, use
375 \override DynamicTextSpanner #'dash-period = #-1.0
378 @c After next LSR update, this snippet can be used
379 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
380 @c {changing-text-and-spanner-styles-for-text-dynamics.ly}
382 The text used for @notation{crescendos} and
383 @notation{decrescendos} can be changed by modifying the context
384 properties @code{crescendoText} and @code{decrescendoText}. The
385 style of the spanner line can be changed by modifying the context
386 properties @code{crescendoSpanner} and @code{decrescendoSpanner}.
387 Available values for the spanner properties are @code{'hairpin},
388 @code{'line}, @code{'dashed-line}, and @code{'dotted-line}. If
389 unset, a hairpin crescendo is used:
391 @lilypond[verbatim,quote,ragged-right,fragment,relative=1]
392 \set crescendoText = \markup { \italic "cresc. poco" }
393 \set crescendoSpanner = #'dotted-line
394 a'2\< a a a a a a a\mf
400 @c TODO: Add hairpin to glossary.
407 @rlearning{Articulation and dynamics}.
410 @ref{Controlling direction and placement}.
413 @rlsr{Expressive marks}.
416 @rinternals{DynamicText},
417 @rinternals{Hairpin},
418 @rinternals{DynamicLineSpanner}.
421 @node New dynamic marks
422 @subsubsection New dynamic marks
424 It is possible to print new dynamic marks or text that should be
425 aligned with dynamics. Use @code{make-dynamic-script} to create
426 these marks. Note that the dynamic font only contains the
427 characters @code{f,m,p,r,s} and @code{z}.
429 Some situations (such as dynamic marks) have preset font-related
430 properties. If you are creating text in such situations, it is
431 advisable to cancel those properties with @code{normal-text}. See
432 @ref{Text markup commands}, for more details.
434 @cindex make-dynamic-script
436 @lilypond[quote,verbatim,ragged-right]
437 sfzp = #(make-dynamic-script "sfzp")
443 @cindex Dynamics, editorial
444 @cindex Dynamics, parenthesis
446 It is also possible to print dynamics in round parenthesis or
447 square brackets. These are often used for adding editorial
450 @lilypond[quote,verbatim,ragged-right]
451 rndf = \markup{ \center-align {\line { \bold{\italic (}
452 \dynamic f \bold{\italic )} }} }
453 boxf = \markup{ \bracket { \dynamic f } }
454 { c'1_\rndf c'1_\boxf }
460 @rlsr{Expressive marks}.
478 A @notation{slur} indicates that notes are to be played bound or
479 @emph{legato}. They are entered using parentheses:
481 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
482 f( g a) a8 b( a4 g2 f4)
486 Just as with ties, the direction of a slur can be specified with
487 @code{\slur@emph{DIR}}, where @code{@emph{DIR}} is either
488 @code{Up}, @code{Down}, or @code{Neutral} (@code{Neutral} is the
489 default). Slurs may be manually placed above or below the staff,
490 see @ref{Controlling direction and placement}.
492 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
496 Using this method, only one slur can be printed at once. To print
497 a long slur over a few small slurs, see @ref{Phrasing slurs}.
506 @funindex \slurNeutral
508 @funindex \slurDashed
510 @funindex \slurDotted
518 @c After next LSR update, this snippet can be used
519 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
520 @c {using-double-slurs-for-legato-chords.ly}
522 Some composers write two slurs when they want legato chords. This
523 can be achieved in LilyPond by setting @code{doubleSlurs},
525 @lilypond[verbatim,quote,ragged-right,fragment,relative=1]
526 \set doubleSlurs = ##t
527 <c e>4 ( <d f> <c e> <d f> )
537 @ref{Controlling direction and placement}.
540 @rlsr{Expressive marks}.
547 @subsubsection Phrasing slurs
549 @cindex phrasing slurs
550 @cindex phrasing marks
554 A phrasing slur (or phrasing mark) connects notes and is used to
555 indicate a musical sentence. It is written using @code{\(} and
556 @code{\)} respectively:
558 @lilypond[verbatim,quote,ragged-right,fragment,relative=1]
559 \time 6/4 c'\( d( e) f( e) d\)
562 Typographically, the phrasing slur behaves almost exactly like a
563 normal slur. However, they are treated as different objects. A
564 @code{\slurUp} will have no effect on a phrasing slur; instead,
565 use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
566 @code{\phrasingSlurNeutral}. Phrasing slurs may be manually
567 placed above or below the staff, see @ref{Controlling direction
570 You cannot have simultaneous phrasing slurs.
575 @funindex \phrasingSlurUp
576 @code{\phrasingSlurUp},
577 @funindex \phrasingSlurDown
578 @code{\phrasingSlurDown},
579 @funindex \phrasingSlurNeutral
580 @code{\phrasingSlurNeutral}.
586 @ref{Controlling direction and placement}.
589 @rlsr{Expressive marks}.
592 @rinternals{PhrasingSlur}.
596 @subsubsection Breath marks
601 Breath marks are entered using @code{\breathe}:
603 @lilypond[verbatim,quote,ragged-right,fragment,relative=1]
610 @c After next LSR update, this snippet can be used
611 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
612 @c {changing-the-breath-mark-symbol.ly}
614 The glyph of the breath mark can be tuned by overriding the
615 @code{text} property of the @code{BreathingSign} layout object
616 with any markup text. For example,
618 @lilypond[verbatim,quote,ragged-right,fragment,relative=1]
620 \override BreathingSign #'text
621 = #(make-musicglyph-markup "scripts.rvarcomma")
630 @rlsr{Expressive marks}.
631 @c @lsr{expressive,breathing-sign.ly}.
634 @rinternals{BreathingSign}.
637 @node Falls and doits
638 @subsubsection Falls and doits
644 @notation{Falls} and @notation{doits} can be added to notes using
645 the @code{\bendAfter} command:
647 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
654 The dash (@tie{-}) following the note name is @emph{required} when
655 writing @notation{falls} and @notation{doits}.
660 @c After next LSR update, this snippet can be used
661 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
662 @c {adjusting-the-shape-of-falls-and-doits.ly}
664 The @code{shortest-duration-space} property may have to be tweaked
665 to adjust the shape of @notation{falls} and @notation{doits}.
667 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
668 \override Score.SpacingSpanner #'shortest-duration-space = #3.0
676 @c TODO: add falls and doits to glossary.
682 @rlsr{Expressive marks}.
695 @subsubsection Glissando
700 A @notation{glissando} is a smooth change in pitch. It is denoted
701 by a line or a wavy line between two notes. A
702 @notation{glissando} is created by attaching @code{\glissando} to
705 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
707 \override Glissando #'style = #'zigzag
714 @c After next LSR update, this snippet can be used
715 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
716 @c {suppressing-compiler-warnings-when-two-glissandos-intersect.ly}
718 @lilypond[verbatim,quote,ragged-right]
719 I = \once \override NoteColumn #'ignore-collision = ##t
722 { \oneVoice \stemDown f2 \glissando \stemNeutral a } \\
723 { \oneVoice \I c2 \glissando \I d, }
734 @rlsr{Expressive marks}.
736 @c FIXME: I need to figure out what's up with these. -gp
737 @c @lsr{expressive,glissando.ly},
738 @c @lsr{expressive,line-styles.ly}
741 @rinternals{Glissando}.
746 Printing text over the line (such as @emph{gliss.}) is not
751 @subsubsection Arpeggio
756 @c Add documentation for new 'parenthesis' style arpeggio. Maybe
757 @c create a new \arpeggioParen command, or something similar. -pm
759 You can specify an @notation{arpeggio} (also known as a
760 @notation{broken chord}) on a chord by attaching an
761 @code{\arpeggio} to the chord:
763 @lilypond[verbatim,quote,ragged-right,fragment,relative=1]
767 A square bracket on the left, denoted by @code{\arpeggioBracket},
768 is used to indicate that the chord should @emph{not} be
771 @lilypond[verbatim,quote,ragged-right,fragment,relative=1]
776 The direction of the arpeggio can be denoted by adding an
777 arrowhead to the wiggly line. This is done with the commands
778 @code{arpeggioUp} and @code{arpeggioDown}. @code{arpeggioNeutral}
779 reverts to the arrow-less version:
781 @lilypond[verbatim,quote,ragged-right,fragment,relative=1]
792 @notation{Arpeggios} can be explicitly written out using
793 @notation{ties}. For more information, see @ref{Ties}.
799 @funindex \arpeggioUp
801 @funindex \arpeggioDown
802 @code{\arpeggioDown},
803 @funindex \arpeggioNeutral
804 @code{\arpeggioNeutral},
805 @funindex \arpeggioBracket
806 @code{\arpeggioBracket}.
811 @c After next LSR update, this snippet can be used
812 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
813 @c {creating-cross--staff-arpeggios-in-a-piano-staff.ly}
815 In a @code{PianoStaff}, it is possible to let an arpeggio cross
816 between the staves by setting the property
817 @code{PianoStaff}.@code{connectArpeggios}.
819 @lilypond[verbatim,quote,ragged-right,fragment,relative=1]
821 \set PianoStaff.connectArpeggios = ##t
822 \new Staff { <c' e g c>\arpeggio }
823 \new Staff { \clef bass <c,, e g>\arpeggio }
827 @c After next LSR update, this snippet can be used
828 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
829 @c {creating-cross--staff-arpeggios-in-other-contexts.ly}
831 The same can be accomplished in contexts other than
832 @code{PianoStaff} if the @code{Span_arpeggio_engraver} is included
833 in the Score context.
835 @lilypond[verbatim,quote,ragged-right]
838 \set Score.connectArpeggios = ##t
840 \new Voice \relative c' {
843 \new Voice \relative c {
852 \consists "Span_arpeggio_engraver"
858 @c After next LSR update, this snippet can be used
859 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
860 @c {creating-arpeggios-across-notes-in-different-voices.ly}
862 Similarly, an arpeggio can be drawn across notes in different
863 voices on the same staff if the @code{Span_arpeggio_engraver} is
864 moved to the Staff context:
866 @lilypond[verbatim,quote,ragged-right]
869 \consists "Span_arpeggio_engraver"
871 \set Staff.connectArpeggios = ##t
873 {<e' g>4\arpeggio <d f> <d f>2 }
875 {<d, f>2\arpeggio <g b>2 }
883 @c TODO: Add 'broken chord' to glossary.
892 @rlsr{Expressive marks}.
895 @rinternals{Arpeggio},
896 @rinternals{PianoStaff}.
901 It is not possible to mix connected arpeggios and unconnected
902 arpeggios in one @code{PianoStaff} at the same point in
907 @subsubsection Trills
912 Short @notation{trills} are printed with @code{\trill} like normal
913 articulation; see @ref{Articulations and ornamentations}.
915 Long running @notation{trills} are made with
916 @code{\startTrillSpan} and @code{\stopTrillSpan}. In the
917 following example, a long running @notation{trill} is shown
918 combined with grace notes. To achieve precise control of the
919 placement of the grace notes, see @ref{Grace notes}.
921 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
923 d1\startTrillSpan { c16[\stopTrillSpan d] }
927 @cindex pitched trills
929 @notation{Trills} that should be executed on an explicitly
930 specified pitch can be typeset with the command
931 @code{\pitchedTrill} using the following syntax:
934 @code{\pitchedTrill} @var{mainnote} @code{\startTrillSpan}
935 @var{trillnote} @var{endnote} @code{\stopTrillSpan}
938 @lilypond[verbatim,quote,ragged-right,fragment,relative=1]
939 \pitchedTrill e2 \startTrillSpan fis
944 The first argument is the main note. The pitch of the second is
945 printed as a stemless note head in parentheses.
950 @code{\startTrillSpan},
951 @funindex \startTrillSpan
952 @code{\stopTrillSpan}.
953 @funindex \stopTrillSpan
962 @rlsr{Expressive marks}.
965 @rinternals{TrillSpanner}.