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.
10 @section Expressive marks
12 @lilypondfile[quote,ragged-right,line-width=16\cm,staffsize=16]
13 {expressive-headword.ly}
22 @node Attached to notes
23 @subsection Attached to notes
27 * Articulations and ornamentations::
31 @node Articulations and ornamentations
32 @unnumberedsubsubsec Articulations and ornamentations
38 A variety of symbols can appear above and below notes to indicate
39 different characteristics of the performance. All these symbols
40 can be attached to a note using the syntax @var{note}@code{\}@var{name}.
42 The possible values for @var{name} are listed in @ref{List of
45 Some of these articulations have shorthands for easier entry. They
46 are used by adding a dash and the character signifying
47 the articulation to the note name. The available shorthands and
50 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
55 The marks are automatically placed, but the direction can be
56 forced as well. Like other pieces of LilyPond code, @code{_} will
57 place them below the staff, and @code{^} will place them above.
58 This applies both to the shorthands and the fully named
59 articulations. For the shorthands, the dash itself should be
60 omitted; the shorthand signs replace it:
62 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
64 c\fermata c^\fermata c_\fermata
80 @cindex organ pedal marks
101 The meanings of the shorthands can be changed. They are defined
102 in @file{ly/@/script@/-init@/.ly}, where the variables
103 @code{DashDot}, @code{DashDash}, @code{DashPlus}, @code{DashBar},
104 @code{DashLarger}, @code{DashHat}, and @code{DashUnderscore}
105 are associated with the default articulation marks. If you want,
106 e.g., @code{-+} to produce a trill instead of a "+", you can
107 redefine the variable in your document:
109 @lilypond[quote,ragged-right,verbatim]
110 \relative c'' { c-+ }
112 \relative c'' { c-+ }
115 The vertical ordering of scripts is controlled with the
116 @code{script-priority} property. The lower this number, the
117 closer it will be put to the note. In this example, the
118 @internalsref{TextScript} (the sharp symbol) first has the lowest
119 priority, so it is put lowest in the first example. In the
120 second, the prall trill (the @internalsref{Script}) has the
121 lowest, so it is on the inside. When two objects have the same
122 priority, the order in which they are entered decides which one
128 The meanings of the shorthands can be changed. They are defined
129 in @file{ly/@/script@/-init@/.ly}, where the variables
130 @code{DashDot}, @code{DashDash}, @code{DashPlus}, @code{DashBar},
131 @code{DashLarger}, @code{DashHat}, and @code{DashUnderscore}
132 are associated with the default articulation marks. If you want,
133 e.g., @code{-+} to produce a trill instead of a "+", you can
134 redefine the variable in your document:
136 @lilypond[quote,ragged-right,verbatim]
137 \relative c'' { c-+ }
139 \relative c'' { c-+ }
142 The vertical ordering of scripts is controlled with the
143 @code{script-priority} property. The lower this number, the
144 closer it will be put to the note. In this example, the
145 @internalsref{TextScript} (the sharp symbol) first has the lowest
146 priority, so it is put lowest in the first example. In the
147 second, the prall trill (the @internalsref{Script}) has the
148 lowest, so it is on the inside. When two objects have the same
149 priority, the order in which they are entered decides which one
152 @lilypond[verbatim,relative=3,ragged-right,fragment,quote]
153 \once \override TextScript #'script-priority = #-100
154 a4^\prall^\markup { \sharp }
156 \once \override Script #'script-priority = #-100
157 a4^\prall^\markup { \sharp }
163 Snippets: @lsrdir{expressive}
165 Internals Reference: @internalsref{Script}.
170 These signs appear in the printed output but have no effect on the
171 MIDI rendering of the music.
175 @unnumberedsubsubsec Dynamics
196 Absolute dynamic marks are specified using a command after a note
197 @code{c4\ff}. The available dynamic marks are @code{\ppppp},
198 @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p}, @code{\mp},
199 @code{\mf}, @code{\f}, @code{\ff}, @code{\fff}, @code{\ffff},
200 @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp}, @code{\spp},
201 @code{\sfz}, and @code{\rfz}. The dynamic marks can be placed
202 above or below the staff with @code{_} and @code{^}, just like
205 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
208 c_\spp c_\staccato^\ff
215 A crescendo mark is started with @code{\<} and terminated with
216 @code{\!} or an absolute dynamic. A decrescendo is started with
217 @code{\>} and is also terminated with @code{\!} or an absolute
218 dynamic. @code{\cr} and @code{\decr} may be used instead of
219 @code{\<} and @code{\>}. They can be engraved either using a
220 graphical sign (a @q{hairpin}), or with textual signs.
222 Because these marks are bound to notes, you must use spacer notes
223 if multiple marks are needed during one note.
225 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
227 << f1 { s4 s4\< s4\! \> s4\! } >>
230 This may give rise to very short hairpins. Use
231 @code{minimum-length} in
232 @internalsref{Voice}.@internalsref{Hairpin} to lengthen them, for
236 \override Voice.Hairpin #'minimum-length = #5
240 A hairpin normally starts at the left edge of the beginning note
241 and ends on the right edge of the ending note. If the ending note
242 falls on the downbeat, the hairpin ends on the immediately
243 preceding bar line. This may be modified by setting the
244 @code{hairpinToBar line} property,
247 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
249 \set hairpinToBarline = ##f
253 @cindex espressivo, articulation
254 In some situations the @code{\espressivo} articulation mark may be
255 suitable to indicate a crescendo and decrescendo on the one note:
257 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
258 c2 b4 a g1\espressivo
264 Hairpins may be printed with a circled tip (al niente notation) by
265 setting the @code{circled-tip} property:
267 @lilypond[quote,ragged-right,fragment,relative=2,verbatim]
268 \override Hairpin #'circled-tip = ##t
278 You can use text saying @emph{cresc.}, @emph{decr.}, or
279 @emph{dim.} instead of hairpins with the commands \setTextCresc,
280 \setTextDim, and \setTextDecresc. The corresponding
281 \setHairpinCresc, \setHairpinDim, and \setHairpinDecresc will
282 revert to hairpins again:
284 @lilypond[quote,ragged-right,fragment,relative=2,verbatim]
291 % FIXME: uncomment after 2.11.36
298 You can also supply your own texts and change the style of the
299 spanner line with the properties @code{\crescendoText},
300 @code{\crescendoSpanner}, @code{\decrescendoText}, and
301 @code{\decrescendoSpanner}. Available values for the spanner
302 properties are @code{hairpin}, @code{line}, @code{dashed-line},
303 and @code{dotted-line}. If unset, a hairpin crescendo is used:
305 @lilypond[quote,ragged-right,fragment,relative=1,verbatim]
306 \set crescendoText = \markup { \italic "cresc. poco" }
307 \set crescendoSpanner = #'dotted-line
308 a'2\< a a a a a a a\!\mf
312 To create new dynamic marks or text that should be aligned with
313 dynamics, see @ref{New dynamic marks}.
315 Vertical positioning of dynamics is handled by
316 @internalsref{DynamicLineSpanner}.
321 Dynamics that occur at, begin on, or end on the same note will be
322 vertically aligned. If you want to ensure that dynamics are
323 aligned when they do not occur on the same note, you can increase
324 the @code{staff-padding} property.
327 \override DynamicLineSpanner #'staff-padding = #4
330 You may also use this property if the dynamics are colliding with
333 Crescendi and decrescendi that cross a line break will be
334 continued on the second line. If they end on the first note of a
335 new line, nothing will be printed on that line. To change this
339 \override Score.Hairpin #'after-line-breaking = ##t
342 Text style dynamic changes (such as @emph{cresc.} and @emph{dim.})
343 are printed with a dashed line showing their extent. To surpress
344 printing this line, use
347 \override DynamicTextSpanner #'dash-period = #-1.0
355 @funindex \dynamicDown
357 @funindex \dynamicNeutral
358 @code{\dynamicNeutral}.
363 Snippets: @lsrdir{expressive}
365 Internals Reference: @internalsref{DynamicText},
366 @internalsref{Hairpin}. Vertical positioning of these symbols is
367 handled by @internalsref{DynamicLineSpanner}.
368 Glossary: @rglos{Hairpin}, @rglos{crescendo}, @rglos{decrescendo}
370 @c TODO: add link to LM directions
384 @unnumberedsubsubsec Slurs
388 A slur indicates that notes are to be played bound or
389 @emph{legato}. They are entered using parentheses:
391 @lilypond[quote,ragged-right,relative=2,fragment,verbatim]
392 f( g a) a8 b( a4 g2 f4)
396 Just as with ties, the direction of a slur can be specified with
397 @code{\slur@emph{DIR}}, where @code{@emph{DIR}} is either
398 @code{Up}, @code{Down}, or @code{Neutral} (automatically
399 selected). The shorthands are also available: by adding
400 @code{_} or @code{^} before the opening parentheses, the direction
403 @lilypond[relative=2,ragged-right,quote,verbatim,fragment]
407 Only one slur can be printed at once. If you need to print a long
408 slur over a few small slurs, please see @ref{Phrasing slurs}.
413 Some composers write two slurs when they want legato chords. This
414 can be achieved in LilyPond by setting @code{doubleSlurs},
416 @lilypond[verbatim,ragged-right,relative,fragment,quote]
417 \set doubleSlurs = ##t
418 <c e>4 ( <d f> <c e> <d f> )
428 @funindex \slurNeutral
430 @funindex \slurDashed
432 @funindex \slurDotted
439 Snippets: @lsrdir{expressive}
441 Internals Reference: @internalsref{Slur}.
445 @unnumberedsubsubsec Phrasing slurs
447 @cindex phrasing slurs
448 @cindex phrasing marks
450 A phrasing slur (or phrasing mark) connects notes and is used to
451 indicate a musical sentence. It is written using @code{\(} and
452 @code{\)} respectively:
454 @lilypond[quote,ragged-right,fragment,verbatim,relative=1]
455 \time 6/4 c'\( d( e) f( e) d\)
458 Typographically, the phrasing slur behaves almost exactly like a
459 normal slur. However, they are treated as different objects. A
460 @code{\slurUp} will have no effect on a phrasing slur; instead,
461 use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
462 @code{\phrasingSlurNeutral}, or use the shorthands @code{_} and
465 You cannot have simultaneous phrasing slurs.
470 @funindex \phrasingSlurUp
471 @code{\phrasingSlurUp},
472 @funindex \phrasingSlurDown
473 @code{\phrasingSlurDown},
474 @funindex \phrasingSlurNeutral
475 @code{\phrasingSlurNeutral}.
480 Snippets: @lsrdir{expressive}
482 Internals Reference: @internalsref{PhrasingSlur}.
486 @unnumberedsubsubsec Breath marks
488 Breath marks are entered using @code{\breathe}
490 @lilypond[quote,ragged-right,fragment,relative=1,verbatim]
497 The glyph of the breath mark can be tuned by overriding the
498 @code{text} property of the @code{BreathingSign} layout object
499 with any markup text. For example,
501 @lilypond[quote,ragged-right,fragment,verbatim,relative=1]
503 \override BreathingSign #'text
504 = #(make-musicglyph-markup "scripts.rvarcomma")
511 Snippets: @lsrdir{expressive}
513 Internals Reference: @internalsref{BreathingSign}.
515 Examples: @lsr{expressive,breathing-sign.ly}
518 @node Falls and doits
519 @unnumberedsubsubsec Falls and doits
521 Falls and doits can be added to notes using the @code{\bendAfter}
524 @lilypond[fragment,ragged-right,relative=2]
525 \override Score.SpacingSpanner #'shortest-duration-space = #3.0
540 @unnumberedsubsubsec Glissando
545 A glissando is a smooth change in pitch. It is denoted by a line
546 or a wavy line between two notes. It is requested by attaching
547 @code{\glissando} to a note
549 @lilypond[quote,ragged-right,fragment,relative=2,verbatim]
551 \override Glissando #'style = #'zigzag
558 @lilypond[quote,ragged-right,verbatim]
559 I = \once \override NoteColumn #'ignore-collision = ##t
562 { \oneVoice \stemDown f2 \glissando \stemNeutral a } \\
563 { \oneVoice \I c2 \glissando \I d, }
571 Snippets: @lsrdir{expressive}
573 Internals Reference: @internalsref{Glissando}.
575 Glossary: @rglos{falls}, @rglos{doits}
577 @lsr{expressive,glissando.ly}, @lsr{expressive,line-styles.ly}
582 Printing text over the line (such as @emph{gliss.}) is not
587 @unnumberedsubsubsec Arpeggio
593 You can specify an arpeggio sign (also known as broken chord) on a
594 chord by attaching an @code{\arpeggio} to the chord:
596 @lilypond[quote,ragged-right,fragment,relative=1,verbatim]
600 A square bracket on the left is used to indicate that the chord should
601 @emph{not} be arpeggiated:
603 @lilypond[quote,ragged-right,fragment,relative=1,verbatim]
608 The direction of the arpeggio can be denoted by adding an
609 arrowhead to the wiggly line. This is done with the commands
610 @code{arpeggioUp} and @code{arpeggioDown}. @code{arpeggioNeutral}
611 reverts to the arrow-less version:
613 @lilypond[quote,ragged-right,fragment,relative=1,verbatim]
627 In a @code{PianoStaff}, it is possible to let an arpeggio cross
628 between the staves by setting the property
629 @internalsref{PianoStaff}.@code{connectArpeggios}.
631 @lilypond[quote,ragged-right,fragment,relative=1,verbatim]
633 \set PianoStaff.connectArpeggios = ##t
634 \new Staff { <c' e g c>\arpeggio }
635 \new Staff { \clef bass <c,, e g>\arpeggio }
639 The same can be accomplished in contexts other than
640 @code{PianoStaff} if the @code{Span_arpeggio_engraver} is included
641 in the Score context.
643 @lilypond[quote,ragged-right,verbatim]
646 \set Score.connectArpeggios = ##t
648 \new Voice \relative c' {
651 \new Voice \relative c {
660 \consists "Span_arpeggio_engraver"
666 Similarly, an arpeggio can be drawn across notes in
667 different voices on the same staff if the Span_arpeggio_engraver
668 is moved to the Staff context:
670 @lilypond[quote,ragged-right,verbatim]
673 \consists "Span_arpeggio_engraver"
675 \set Staff.connectArpeggios = ##t
677 {<e' g>4\arpeggio <d f> <d f>2 }
679 {<d, f>2\arpeggio <g b>2 }
689 @funindex \arpeggioUp
691 @funindex \arpeggioDown
692 @code{\arpeggioDown},
693 @funindex \arpeggioNeutral
694 @code{\arpeggioNeutral},
695 @funindex \arpeggioBracket
696 @code{\arpeggioBracket}.
701 Notation manual: @ref{Ties}, for writing out arpeggios.
703 Snippets: @lsrdir{expressive}
705 Internals Reference: @internalsref{Arpeggio}.
710 It is not possible to mix connected arpeggios and unconnected
711 arpeggios in one @internalsref{PianoStaff} at the same point in
716 @unnumberedsubsubsec Trills
718 Short trills are printed with @code{\trill} like normal
719 articulation; see @ref{Articulations and ornamentations}.
721 Long running trills are made with @code{\startTrillSpan} and
722 @code{\stopTrillSpan}. In the following example, it is shown in
723 the common combination with grace notes. If a more precise
724 control of the placement of the grace notes is needed, see
727 @lilypond[verbatim,ragged-right,relative=2,quote,fragment]
730 d1\startTrillSpan { c16[\stopTrillSpan d] }
734 @cindex Pitched trills
736 Trills that should be executed on an explicitly specified pitch
737 can be typeset with the command @code{pitchedTrill}, and the
738 syntax @code{\pitchedTrill} @var{mainnote}@code{\startTrillSpan}
739 @var{trillnote} @var{endnote} @code{\stopTrillSpan}.
741 @lilypond[ragged-right,verbatim,fragment,relative=1,quote]
742 \pitchedTrill e2 \startTrillSpan fis
748 The first argument is the main note. The pitch of the second is
749 printed as a stemless note head in parentheses.
754 @code{\startTrillSpan},
755 @funindex \startTrillSpan
756 @code{\stopTrillSpan}.
757 @funindex \stopTrillSpan
762 Snippets: @lsrdir{expressive}
764 Internals Reference: @internalsref{TrillSpanner}.