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
21 * Expressive marks attached to notes::
22 * Expressive marks as curves::
23 * Expressive marks as lines::
27 @node Expressive marks attached to notes
28 @subsection Expressive marks 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
111 @funindex \fermataMarkup
119 A variety of symbols that denote articulations, ornamentations,
120 and other performance indications can be attached to a note using
124 @var{note}\@var{name}
127 The possible values for @code{@var{name}} are listed in
128 @ref{List of articulations}. For example:
130 @lilypond[verbatim,quote]
132 c''4\staccato c\mordent b2\turn
139 @cindex staccatissimo
144 Some of these articulations have shorthands for easier entry.
145 Shorthands are appended to the note name, and their syntax
146 consists of a dash @code{-} followed by a symbol signifying the
147 articulation. Predefined shorthands exist for @notation{marcato},
148 @notation{stopped}, @notation{tenuto}, @notation{staccatissimo},
149 @notation{accent}, @notation{staccato}, and @notation{portato}.
150 Their corresponding output appears as follows:
152 @lilypond[verbatim,quote]
159 The rules for the default placement of articulations are defined
160 in @file{scm/script.scm}. Articulations and ornamentations
161 may be manually placed above or below the staff; see
162 @ref{Direction and placement}.
164 Articulations are @code{Script} objects. Their properties are
165 described more fully in @rinternals{Script}.
167 Articulations can be attached to rests as well as notes but they
168 cannot be attached to multi-measure rests. A special predefined
169 command, @code{\fermataMarkup}, is available for attaching a fermata
170 to a multi-measure rest (and only a multi-measure rest). This
171 creates a @code{MultiMeasureRestText} object.
173 @lilypond[verbatim,quote,fragment]
174 \override Script.color = #red
175 \override MultiMeasureRestText.color = #blue
176 a'2\fermata r\fermata
180 In addition to articulations, text and markups can be attached to
181 notes. See @ref{Text scripts}.
183 For more information about the ordering of Scripts and TextScripts that
184 are attached to the notes, see @rlearning{Placement of objects}.
188 @lilypondfile[verbatim,quote,texidoc,doctitle]
189 {modifying-default-values-for-articulation-shorthand-notation.ly}
191 @lilypondfile[verbatim,quote,texidoc,doctitle]
192 {controlling-the-vertical-ordering-of-scripts.ly}
194 @lilypondfile[verbatim,quote,texidoc,doctitle]
195 {creating-a-delayed-turn.ly}
205 @rlearning{Placement of objects}.
209 @ref{Direction and placement},
210 @ref{List of articulations},
214 @file{scm/script.scm}.
217 @rlsr{Expressive marks}.
221 @rinternals{TextScript}.
225 @unnumberedsubsubsec Dynamics
227 @cindex absolute dynamics
229 @cindex dynamics, absolute
251 Absolute dynamic marks are specified using a command after a note,
252 such as @code{c4\ff}. The available dynamic marks are
253 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
254 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
255 @code{\ffff}, @code{\fffff}, @code{\fp}, @code{\sf}, @code{\sff},
256 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}. Dynamic
257 marks may be manually placed above or below the staff; see
258 @ref{Direction and placement}.
260 @lilypond[verbatim,quote]
279 A @notation{crescendo} mark is started with @code{\<} and
280 terminated with @code{\!}, an absolute dynamic, or an additional
281 crescendo or decrescendo mark. A @notation{decrescendo} mark is
282 started with @code{\>} and is also terminated with @code{\!}, an
283 absolute dynamic, or another crescendo or decrescendo mark.
284 @code{\cr} and @code{\decr} may be used instead of @code{\<} and
285 @code{\>}. @notation{Hairpins} are engraved by default using this
288 @lilypond[verbatim,quote]
300 A hairpin that is terminated with @code{\!} will end at the
301 right edge of the note that has the @code{\!} assigned to it. In the
302 case where it is terminated with the start of another @notation{crescendo}
303 or @notation{decrescendo} mark, it will end at the centre of the note
304 that has the next @code{\<} or @code{\>} assigned to it. The next
305 hairpin will then start at the right edge of the same note
306 instead of the usual left edge had it been terminated with @code{\!}
307 before. A hairpin ending on a downbeat will stop at the preceding bar line.
309 @lilypond[verbatim,quote]
311 c''1\< | c4 a c\< a | c4 a c\! a\< | c4 a c a\!
315 Hairpins that are terminated with absolute dynamic marks instead of
316 @code{\!} will also be engraved in a similar way. However, the length
317 of the absolute dynamic itself can alter where the preceding hairpin
320 @lilypond[verbatim,quote]
322 c''1\< | c4 a c\mf a | c1\< | c4 a c\ffff a
326 @cindex multiple dynamic marks on one note
327 @cindex dynamic marks, multiple on one note
328 Spacer rests are needed to engrave multiple marks on one note.
329 This is particularly useful when adding a @notation{crescendo} and
330 @notation{decrescendo} to the same note:
332 @lilypond[verbatim,quote]
335 << f1 { s4 s4\< s4\> s4\! } >>
339 @cindex espressivo articulation
341 @funindex \espressivo
343 The @code{\espressivo} command can be used to indicate a crescendo
344 and decrescendo on the same note. However, be warned that this is
345 implemented as an articulation, not a dynamic.
347 @lilypond[verbatim,quote]
357 Textual crescendo marks begin with @code{\cresc}.
358 Textual decrescendos begin with @code{\decresc} or @code{\dim}.
359 Extender lines are engraved as required.
361 @lilypond[verbatim,quote]
363 g'8\cresc a b c b c d e\mf |
364 f8\decresc e d c e\> d c b |
370 @funindex \crescTextCresc
371 @funindex \dimTextDecresc
372 @funindex \dimTextDecr
373 @funindex \dimTextDim
374 @funindex \crescHairpin
375 @funindex \dimHairpin
377 Textual marks for dynamic changes can also replace hairpins:
378 @lilypond[verbatim,quote]
395 To create new absolute dynamic marks or text that should be
396 aligned with dynamics, see @ref{New dynamic marks}.
398 @cindex dynamics, vertical positioning
399 @cindex vertical positioning of dynamics
401 @funindex DynamicLineSpanner
404 Vertical positioning of dynamics is handled by
405 @rinternals{DynamicLineSpanner}.
407 @funindex \dynamicDown
408 @funindex \dynamicNeutral
410 A @code{Dynamics} context is available to engrave dynamics on
411 their own horizontal line. Use spacer rests to indicate timing.
412 (Notes in a @code{Dynamics} context will also take up
413 musical time, but will not be engraved.)
414 The @code{Dynamics} context can usefully contain some other
415 items such as text scripts, text spanners, and piano pedal marks.
417 @lilypond[verbatim,quote]
419 \new Staff \relative {
437 @code{\dynamicNeutral},
438 @code{\crescTextCresc},
441 @code{\dimTextDecresc},
442 @code{\crescHairpin},
449 @cindex hairpins at bar lines
451 @lilypondfile[verbatim,quote,texidoc,doctitle]
452 {setting-hairpin-behavior-at-bar-lines.ly}
454 @lilypondfile[verbatim,quote,texidoc,doctitle]
455 {setting-the-minimum-length-of-hairpins.ly}
457 @lilypondfile[verbatim,quote,texidoc,doctitle]
458 {moving-the-ends-of-hairpins.ly}
463 @lilypondfile[verbatim,quote,texidoc,doctitle]
464 {printing-hairpins-using-al-niente-notation.ly}
466 @cindex Ferneyhough hairpins
467 @cindex hairpins, Ferneyhough
468 @cindex flared hairpins
469 @cindex hairpins, flared
470 @cindex constante hairpins
471 @cindex hairpins, constante
473 @lilypondfile[verbatim,quote,texidoc,doctitle]
474 {printing-hairpins-in-various-styles.ly}
476 @lilypondfile[verbatim,quote,texidoc,doctitle]
477 {vertically-aligned-dynamics-and-textscripts.ly}
479 @lilypondfile[verbatim,quote,texidoc,doctitle]
480 {hiding-the-extender-line-for-text-dynamics.ly}
482 @lilypondfile[verbatim,quote,texidoc,doctitle]
483 {changing-text-and-spanner-styles-for-text-dynamics.ly}
493 @rlearning{Articulation and dynamics}.
496 @ref{Direction and placement},
497 @ref{New dynamic marks},
498 @ref{Enhancing MIDI output},
499 @ref{Controlling MIDI dynamics}.
502 @rlsr{Expressive marks}.
505 @rinternals{DynamicText},
506 @rinternals{Hairpin},
507 @rinternals{DynamicLineSpanner},
508 @rinternals{Dynamics}.
511 @node New dynamic marks
512 @unnumberedsubsubsec New dynamic marks
514 @cindex new dynamic marks
515 @cindex dynamic marks, new
517 The easiest way to create dynamic indications is to use
518 @code{\markup} objects.
520 @lilypond[verbatim,quote]
521 moltoF = \markup { molto \dynamic f }
524 <d' e>16_\moltoF <d e>
529 @cindex dynamics, editorial
530 @cindex dynamics, parenthesis
531 @cindex editorial dynamics
535 In markup mode, editorial dynamics (within parentheses or square
536 brackets) can be created. The syntax for markup mode is described
537 in @ref{Formatting text}.
539 @lilypond[verbatim,quote]
541 \center-align \concat { \bold { \italic ( }
542 \dynamic f \bold { \italic ) } } }
543 boxF = \markup { \bracket { \dynamic f } }
550 @cindex make-dynamic-script
551 @funindex make-dynamic-script
553 Simple, centered dynamic marks are easily created with the
554 @code{make-dynamic-script} function.
556 @lilypond[verbatim,quote]
557 sfzp = #(make-dynamic-script "sfzp")
563 In general, @code{make-dynamic-script} takes any markup object as its
564 argument. The dynamic font only contains the characters
565 @code{f,m,p,r,s} and @code{z}, so if a dynamic mark that includes
566 plain text or punctuation symbols is desired, markup commands that
567 reverts font family and font encoding to normal text should be used,
568 for example @code{\normal-text}. The interest of using
569 @code{make-dynamic-script} instead of an ordinary markup is ensuring
570 the vertical alignment of markup objects and hairpins that are
571 attached to the same note head.
573 @lilypond[verbatim,quote]
574 roundF = \markup { \center-align \concat {
575 \normal-text { \bold { \italic ( } }
577 \normal-text { \bold { \italic ) } } } }
578 boxF = \markup { \bracket { \dynamic f } }
579 mfEspress = \markup { \center-align \line {
580 \hspace #3.7 mf \normal-text \italic espress. } }
581 roundFdynamic = #(make-dynamic-script roundF)
582 boxFdynamic = #(make-dynamic-script boxF)
583 mfEspressDynamic = #(make-dynamic-script mfEspress)
585 c'4_\roundFdynamic\< d e f
588 g'1~\mfEspressDynamic
593 The Scheme form of markup mode may be used instead. Its syntax is
594 explained in @rextend{Markup construction in Scheme}.
596 @lilypond[verbatim,quote]
597 moltoF = #(make-dynamic-script
598 (markup #:normal-text "molto"
606 To left-align the dynamic text rather than centering it on a note
609 @lilypond[verbatim,quote]
610 moltoF = \tweak DynamicText.self-alignment-X #LEFT
611 #(make-dynamic-script
612 (markup #:normal-text "molto"
616 <d e>2..\moltoF <d e>1
620 Font settings in markup mode are described in
621 @ref{Selecting font and font size}.
625 @ref{Formatting text},
626 @ref{Selecting font and font size},
627 @ref{Enhancing MIDI output},
628 @ref{Controlling MIDI dynamics}.
631 @rextend{Markup construction in Scheme}.
634 @rlsr{Expressive marks}.
637 @node Expressive marks as curves
638 @subsection Expressive marks as curves
640 This section explains how to create various expressive marks that
641 are curved: normal slurs, phrasing slurs, breath marks, falls, and
652 @unnumberedsubsubsec Slurs
656 @notation{Slurs} are entered using parentheses:
658 @warning{In polyphonic music, a slur must be terminated
659 in the same voice it began.}
661 @lilypond[verbatim,quote]
669 @cindex slurs, manual placement
670 @cindex slurs, below notes
671 @cindex slurs, above notes
673 @funindex \slurNeutral
675 Slurs may be manually placed above or below the staff; see
676 @ref{Direction and placement}.
678 @cindex phrasing slur
679 @cindex multiple slurs
680 @cindex simultaneous slurs
681 @cindex slur, phrasing
682 @cindex slurs, multiple
683 @cindex slurs, simultaneous
686 Simultaneous or overlapping slurs require special attention. Most
687 occurences of outer slurs actually indicate phrasing, and phrasing
688 slurs may overlap a regular slur, see @ref{Phrasing slurs}. When
689 multiple regular slurs are needed in a single @code{Voice},
690 matching slur starts and ends need to be labelled by preceding
691 them with @code{\=} followed by an identifying key (a symbol or
692 non-negative integer).
694 @lilypond[verbatim,quote]
696 <c~ f\=1( g\=2( >2 <c e\=1) a\=2) >
708 @funindex \slurDashed
709 @funindex \slurDotted
712 Slurs can be solid, dotted, or dashed. Solid is the default slur
715 @lilypond[verbatim,quote]
727 @funindex \slurHalfDashed
728 @funindex \slurHalfSolid
729 @cindex slur, half dashed and half solid
731 Slurs can also be made half-dashed (the first half dashed, the
732 second half solid) or half-solid (the first half solid, the second
735 @lilypond[verbatim,quote]
747 @funindex \slurDashPattern
748 @cindex slur, defining dash patterns
750 Custom dash patterns for slurs can be defined:
752 @lilypond[verbatim,quote]
755 \slurDashPattern #0.7 #0.75
757 \slurDashPattern #0.5 #2.0
775 @code{\slurHalfDashed},
776 @code{\slurHalfSolid},
777 @code{\slurDashPattern},
784 @lilypondfile[verbatim,quote,texidoc,doctitle]
785 {using-double-slurs-for-legato-chords.ly}
787 @lilypondfile[verbatim,quote,texidoc,doctitle]
788 {positioning-text-markups-inside-slurs.ly}
790 @lilypondfile[verbatim,quote,texidoc,doctitle]
791 {making-slurs-with-complex-dash-structure.ly}
798 @rlearning{On the un-nestedness of brackets and ties}.
801 @ref{Direction and placement},
802 @ref{Phrasing slurs}.
805 @rlsr{Expressive marks}.
812 @unnumberedsubsubsec Phrasing slurs
814 @cindex phrasing slurs
815 @cindex phrasing marks
816 @cindex slur, phrasing
817 @cindex mark, phrasing
821 @notation{Phrasing slurs} (or phrasing marks) that indicate a
822 musical sentence are written using the commands @code{\(} and
823 @code{\)} respectively:
825 @lilypond[verbatim,quote]
832 @funindex \phrasingSlurUp
833 @funindex \phrasingSlurDown
834 @funindex \phrasingSlurNeutral
836 Typographically, a phrasing slur behaves almost exactly like a
837 normal slur. However, they are treated as different objects; a
838 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
839 may be manually placed above or below the staff; see
840 @ref{Direction and placement}.
842 @cindex simultaneous phrasing slurs
843 @cindex multiple phrasing slurs
844 @cindex slur, simultaneous phrasing
845 @cindex slur, multiple phrasing
846 @cindex phrasing slur, simultaneous
847 @cindex phrasing slur, multiple
849 Simultaneous or overlapping phrasing slurs are entered using
850 @code{\=} as with regular slurs, see @ref{Slurs}.
852 @funindex \phrasingSlurDashed
853 @funindex \phrasingSlurDotted
854 @funindex \phrasingSlurSolid
855 @cindex phrasing slur, dashed
856 @cindex dashed phrasing slur
857 @cindex phrasing slur, dotted
858 @cindex dotted phrasing slurs
859 @cindex slur, dashed phrasing
860 @cindex slur, dotted phrasing
862 Phrasing slurs can be solid, dotted, or dashed. Solid is the default
863 style for phrasing slurs:
865 @lilypond[verbatim,quote]
877 @funindex \phrasingSlurHalfDashed
878 @funindex \phrasingSlurHalfSolid
879 @cindex phrasing slur, half solid and half dashed
880 @cindex slur, half solid and half dashed phrasing
882 Phrasing slurs can also be made half-dashed (the first half dashed, the
883 second half solid) or half-solid (the first half solid, the second
886 @lilypond[verbatim,quote]
889 \phrasingSlurHalfDashed
891 \phrasingSlurHalfSolid
898 @funindex \phrasingSlurDashPattern
899 @cindex phrasing slur, defining dash patterns
900 @cindex slur, phrasing, defining dash patterns
901 @cindex slur, defining dash patterns for phrasing
903 Custom dash patterns for phrasing slurs can be defined:
905 @lilypond[verbatim,quote]
908 \phrasingSlurDashPattern #0.7 #0.75
910 \phrasingSlurDashPattern #0.5 #2.0
917 Dash pattern definitions for phrasing slurs have the same structure
918 as dash pattern definitions for slurs. For more information about
919 complex dash patterns, see the snippets under @ref{Slurs}.
922 @code{\phrasingSlurUp},
923 @code{\phrasingSlurDown},
924 @code{\phrasingSlurNeutral},
925 @code{\phrasingSlurDashed},
926 @code{\phrasingSlurDotted},
927 @code{\phrasingSlurHalfDashed},
928 @code{\phrasingSlurHalfSolid},
929 @code{\phrasingSlurDashPattern},
930 @code{\phrasingSlurSolid}.
935 @rlearning{On the un-nestedness of brackets and ties}.
938 @ref{Direction and placement},
942 @rlsr{Expressive marks}.
945 @rinternals{PhrasingSlur}.
949 @unnumberedsubsubsec Breath marks
955 Breath marks are entered using @code{\breathe}:
957 @lilypond[verbatim,quote]
958 { c''2. \breathe d''4 }
961 Unlike other expressive marks, a breath mark is not associated with
962 the preceding note but is a separate music event. So all the
963 expressive marks which are attached to the preceding note, any square
964 brackets indicating manual beams, and any brackets indicating slurs
965 and phrasing slurs must be placed before @code{\breathe}.
967 A breath mark will end an automatic beam; to override this behavior, see
970 @lilypond[verbatim,quote]
971 \relative { c''8 \breathe d e f g2 }
974 Musical indicators for breath marks in ancient notation,
975 divisiones, are supported. For details, see @ref{Divisiones}.
980 @lilypondfile[verbatim,quote,texidoc,doctitle]
981 {changing-the-breath-mark-symbol.ly}
985 @lilypondfile[verbatim,quote,texidoc,doctitle]
986 {using-a-tick-as-the-breath-mark-symbol.ly}
989 @cindex railroad tracks
991 @lilypondfile[verbatim,quote,texidoc,doctitle]
992 {inserting-a-caesura.ly}
1002 @rlsr{Expressive marks}.
1004 Internals Reference:
1005 @rinternals{BreathingEvent},
1006 @rinternals{BreathingSign},
1007 @rinternals{Breathing_sign_engraver}.
1010 @node Falls and doits
1011 @unnumberedsubsubsec Falls and doits
1015 @funindex \bendAfter
1017 @notation{Falls} and @notation{doits} can be added to notes using
1018 the @code{\bendAfter} command. The direction of the fall or doit
1019 is indicated with a plus or minus (up or down). The number
1020 indicates the pitch interval that the fall or doit will extend
1021 @emph{beyond} the main note.
1023 @lilypond[verbatim,quote]
1036 @lilypondfile[verbatim,quote,texidoc,doctitle]
1037 {adjusting-the-shape-of-falls-and-doits.ly}
1045 @rlsr{Expressive marks}.
1048 @node Expressive marks as lines
1049 @subsection Expressive marks as lines
1051 This section explains how to create various expressive marks that
1052 follow a linear path: glissandos, arpeggios, and trills.
1061 @unnumberedsubsubsec Glissando
1064 @funindex \glissando
1066 A @notation{glissando} is created by appending @code{\glissando}
1069 @lilypond[verbatim,quote]
1073 \afterGrace f,1\glissando f'16
1077 A glissando can connect notes across staves:
1079 @lilypond[verbatim,quote]
1081 \new Staff = "right" {
1083 \change Staff = "left"
1085 \change Staff = "right"
1088 \new Staff = "left" {
1095 A glissando can connect notes in chords. If anything other than a
1096 direct one-to-one pairing of the notes in the two chords is required
1097 the connections between the notes are defined by setting
1098 @code{\glissandoMap}, where the notes of a chord are assumed to be
1099 numbered from zero in the order in which they appear in the input
1102 @lilypond[verbatim,quote]
1104 <c' e>1\glissando g' |
1108 \set glissandoMap = #'((0 . 1) (1 . 0))
1109 <c, g'>1\glissando |
1111 \set glissandoMap = #'((0 . 0) (0 . 1) (0 . 2))
1114 \set glissandoMap = #'((2 . 0) (1 . 0) (0 . 1))
1115 <f d a'>1\glissando |
1120 Different styles of glissandi can be created. For details, see
1125 @lilypondfile[verbatim,quote,texidoc,doctitle]
1126 {contemporary-glissando.ly}
1128 @lilypondfile[verbatim,quote,texidoc,doctitle]
1129 {adding-timing-marks-to-long-glissandi.ly}
1131 @lilypondfile[verbatim,quote,texidoc,doctitle]
1132 {making-glissandi-breakable.ly}
1134 @lilypondfile[verbatim,quote,texidoc,doctitle]
1135 {extending-glissandi-across-repeats.ly}
1145 @rlsr{Expressive marks}.
1147 Internals Reference:
1148 @rinternals{Glissando}.
1151 Printing text over the line (such as @notation{gliss.}) is not
1156 @unnumberedsubsubsec Arpeggio
1159 @cindex broken chord
1160 @cindex chord, broken
1163 @funindex \arpeggioArrowUp
1164 @funindex \arpeggioArrowDown
1165 @funindex \arpeggioNormal
1167 An @notation{arpeggio} on a chord (also known as a broken chord)
1168 is denoted by appending @code{\arpeggio} to the chord construct:
1170 @lilypond[verbatim,quote]
1171 \relative { <c' e g c>1\arpeggio }
1174 Different types of arpeggios may be written.
1175 @code{\arpeggioNormal} reverts to a normal arpeggio:
1177 @lilypond[verbatim,quote]
1179 <c' e g c>2\arpeggio
1192 @cindex arpeggio symbols, special
1193 @cindex special arpeggio symbols
1195 @funindex \arpeggioBracket
1196 @funindex \arpeggioParenthesis
1197 @funindex \arpeggioParenthesisDashed
1199 Special @emph{bracketed} arpeggio symbols can be created:
1201 @lilypond[verbatim,quote]
1208 \arpeggioParenthesis
1211 \arpeggioParenthesisDashed
1219 The dash properties of the parenthesis arpeggio are controlled
1220 with the @code{'dash-definition} property, which is described at
1223 Arpeggios can be explicitly written out with ties. For more
1224 information, see @ref{Ties}.
1229 @code{\arpeggioArrowUp},
1230 @code{\arpeggioArrowDown},
1231 @code{\arpeggioNormal},
1232 @code{\arpeggioBracket},
1233 @code{\arpeggioParenthesis},
1234 @code{\arpeggioParenthesisDashed}.
1240 @lilypondfile[verbatim,quote,texidoc,doctitle]
1241 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
1243 @lilypondfile[verbatim,quote,texidoc,doctitle]
1244 {creating-cross-staff-arpeggios-in-other-contexts.ly}
1246 @lilypondfile[verbatim,quote,texidoc,doctitle]
1247 {creating-arpeggios-across-notes-in-different-voices.ly}
1258 @rlsr{Expressive marks}.
1260 Internals Reference:
1261 @rinternals{Arpeggio},
1263 @rinternals{PianoStaff}.
1266 @cindex cross-staff parenthesis-style arpeggio
1267 @cindex arpeggio, parenthesis-style, cross-staff
1268 @cindex arpeggio, cross-staff parenthesis-style
1270 It is not possible to mix connected arpeggios and unconnected
1271 arpeggios in one @code{PianoStaff} at the same point in
1274 The simple way of setting parenthesis-style arpeggio brackets does not work for
1275 cross-staff arpeggios; see @ref{Cross-staff stems}.
1279 @unnumberedsubsubsec Trills
1284 @funindex \startTrillSpan
1285 @funindex \stopTrillSpan
1287 Short trills without an extender line are printed with
1288 @code{\trill}; see @ref{Articulations and ornamentations}.
1290 Longer trills with an extender line are made with
1291 @code{\startTrillSpan} and @code{\stopTrillSpan}:
1293 @lilypond[verbatim,quote]
1302 A trill spanner crossing a line break will restart exactly above
1303 the first note on the new line.
1305 @lilypond[ragged-right,verbatim,quote]
1315 Consecutive trill spans will work without explicit
1316 @code{\stopTrillSpan} commands, since successive trill spanners will
1317 automatically become the right bound of the previous trill.
1319 @lilypond[verbatim,quote]
1329 Trills can also be combined with grace notes. The syntax of this
1330 construct and the method to precisely position the grace notes are
1331 described in @ref{Grace notes}.
1333 @lilypond[verbatim,quote]
1336 d1\startTrillSpan { c32[ d]\stopTrillSpan }
1341 @cindex pitched trills
1342 @cindex trills, pitched
1343 @funindex \pitchedTrill
1345 Trills that require an auxiliary note with an explicit pitch can
1346 be typeset with the @code{\pitchedTrill} command. The first
1347 argument is the main note, and the second is the @emph{trilled}
1348 note, printed as a stemless note head in parentheses.
1350 @lilypond[verbatim,quote]
1353 d''2\startTrillSpan fis
1360 @cindex pitched trill with accidental
1361 @cindex trill with accidental
1363 Subsequent accidentals of the same note in the same measure will need
1364 to be added manually. Only the accidental of the first pitched trill
1365 in a measure is printed.
1367 @lilypond[verbatim,quote]
1370 eis''4\startTrillSpan fis
1373 eis4\startTrillSpan cis
1376 eis4\startTrillSpan fis
1379 eis4\startTrillSpan fis!
1385 @code{\startTrillSpan},
1386 @code{\stopTrillSpan}.
1394 @ref{Articulations and ornamentations},
1398 @rlsr{Expressive marks}.
1400 Internals Reference:
1401 @rinternals{TrillSpanner}.