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
270 Absolute dynamic marks are specified using a command after a note,
271 such as @code{c4\ff}. The available dynamic marks are
272 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
273 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
274 @code{\ffff}, @code{\fffff}, @code{\fp}, @code{\sf}, @code{\sff},
275 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}. Dynamic
276 marks may be manually placed above or below the staff; see
277 @ref{Direction and placement}.
279 @lilypond[verbatim,quote]
300 A @notation{crescendo} mark is started with @code{\<} and
301 terminated with @code{\!}, an absolute dynamic, or an additional
302 crescendo or decrescendo mark. A @notation{decrescendo} mark is
303 started with @code{\>} and is also terminated with @code{\!}, an
304 absolute dynamic, or another crescendo or decrescendo mark.
305 @code{\cr} and @code{\decr} may be used instead of @code{\<} and
306 @code{\>}. @notation{Hairpins} are engraved by default using this
309 @lilypond[verbatim,quote]
321 A hairpin that is terminated with @code{\!} will end at the
322 right edge of the note that has the @code{\!} assigned to it. In the
323 case where it is terminated with the start of another @notation{crescendo}
324 or @notation{decrescendo} mark, it will end at the centre of the note
325 that has the next @code{\<} or @code{\>} assigned to it. The next
326 hairpin will then start at the right edge of the same note
327 instead of the usual left edge had it been terminated with @code{\!}
330 @lilypond[verbatim,quote]
332 c''1\< | c4 a c\< a | c4 a c\! a\< | c4 a c a\!
336 Hairpins that are terminated with absolute dynamic marks instead of
337 @code{\!} will also be engraved in a similar way. However, the length
338 of the absolute dynamic itself can alter where the preceding hairpin
341 @lilypond[verbatim,quote]
343 c''1\< | c4 a c\mf a | c1\< | c4 a c\ffff a
347 @cindex multiple dynamic marks on one note
348 @cindex dynamic marks, multiple on one note
349 Spacer rests are needed to engrave multiple marks on one note.
350 This is particularly useful when adding a @notation{crescendo} and
351 @notation{decrescendo} to the same note:
353 @lilypond[verbatim,quote]
356 << f1 { s4 s4\< s4\> s4\! } >>
360 @cindex espressivo articulation
362 @funindex \espressivo
365 The @code{\espressivo} command can be used to indicate a crescendo
366 and decrescendo on the same note. However, be warned that this is
367 implemented as an articulation, not a dynamic.
369 @lilypond[verbatim,quote]
382 Textual crescendo marks begin with @code{\cresc}.
383 Textual decrescendos begin with @code{\decresc} or @code{\dim}.
384 Extender lines are engraved as required.
386 @lilypond[verbatim,quote]
388 g'8\cresc a b c b c d e\mf |
389 f8\decresc e d c e\> d c b |
395 @funindex \crescTextCresc
396 @funindex crescTextCresc
397 @funindex \dimTextDecresc
398 @funindex dimTextDecresc
399 @funindex \dimTextDecr
400 @funindex dimTextDecr
401 @funindex \dimTextDim
403 @funindex \crescHairpin
404 @funindex crescHairpin
405 @funindex \dimHairpin
408 Textual marks for dynamic changes can also replace hairpins:
409 @lilypond[verbatim,quote]
426 To create new absolute dynamic marks or text that should be
427 aligned with dynamics, see @ref{New dynamic marks}.
429 @cindex dynamics, vertical positioning
430 @cindex vertical positioning of dynamics
432 @funindex DynamicLineSpanner
435 Vertical positioning of dynamics is handled by
436 @rinternals{DynamicLineSpanner}.
439 @funindex \dynamicDown
440 @funindex dynamicDown
441 @funindex \dynamicNeutral
442 @funindex dynamicNeutral
444 A @code{Dynamics} context is available to engrave dynamics on
445 their own horizontal line. Use spacer rests to indicate timing.
446 (Notes in a @code{Dynamics} context will also take up
447 musical time, but will not be engraved.)
448 The @code{Dynamics} context can usefully contain some other
449 items such as text scripts, text spanners, and piano pedal marks.
451 @lilypond[verbatim,quote]
453 \new Staff \relative {
471 @code{\dynamicNeutral},
472 @code{\crescTextCresc},
475 @code{\dimTextDecresc},
476 @code{\crescHairpin},
483 @lilypondfile[verbatim,quote,texidoc,doctitle]
484 {setting-hairpin-behavior-at-bar-lines.ly}
486 @lilypondfile[verbatim,quote,texidoc,doctitle]
487 {setting-the-minimum-length-of-hairpins.ly}
492 @lilypondfile[verbatim,quote,texidoc,doctitle]
493 {printing-hairpins-using-al-niente-notation.ly}
495 @cindex Ferneyhough hairpins
496 @cindex hairpins, Ferneyhough
497 @cindex flared hairpins
498 @cindex hairpins, flared
499 @cindex constante hairpins
500 @cindex hairpins, constante
502 @lilypondfile[verbatim,quote,texidoc,doctitle]
503 {printing-hairpins-in-various-styles.ly}
505 @lilypondfile[verbatim,quote,texidoc,doctitle]
506 {vertically-aligned-dynamics-and-textscripts.ly}
508 @lilypondfile[verbatim,quote,texidoc,doctitle]
509 {hiding-the-extender-line-for-text-dynamics.ly}
511 @lilypondfile[verbatim,quote,texidoc,doctitle]
512 {changing-text-and-spanner-styles-for-text-dynamics.ly}
522 @rlearning{Articulation and dynamics}.
525 @ref{Direction and placement},
526 @ref{New dynamic marks},
527 @ref{Enhancing MIDI output},
528 @ref{Controlling MIDI dynamics}.
531 @rlsr{Expressive marks}.
534 @rinternals{DynamicText},
535 @rinternals{Hairpin},
536 @rinternals{DynamicLineSpanner},
537 @rinternals{Dynamics}.
540 @node New dynamic marks
541 @unnumberedsubsubsec New dynamic marks
543 @cindex new dynamic marks
544 @cindex dynamic marks, new
546 The easiest way to create dynamic indications is to use
547 @code{\markup} objects.
549 @lilypond[verbatim,quote]
550 moltoF = \markup { molto \dynamic f }
553 <d' e>16_\moltoF <d e>
558 @cindex dynamics, editorial
559 @cindex dynamics, parenthesis
560 @cindex editorial dynamics
566 In markup mode, editorial dynamics (within parentheses or square
567 brackets) can be created. The syntax for markup mode is described
568 in @ref{Formatting text}.
570 @lilypond[verbatim,quote]
572 \center-align \concat { \bold { \italic ( }
573 \dynamic f \bold { \italic ) } } }
574 boxF = \markup { \bracket { \dynamic f } }
581 @cindex make-dynamic-script
582 @funindex make-dynamic-script
584 Simple, centered dynamic marks are easily created with the
585 @code{make-dynamic-script} function.
587 @lilypond[verbatim,quote]
588 sfzp = #(make-dynamic-script "sfzp")
594 In general, @code{make-dynamic-script} takes any markup object as its
595 argument. The dynamic font only contains the characters
596 @code{f,m,p,r,s} and @code{z}, so if a dynamic mark that includes
597 plain text or punctuation symbols is desired, markup commands that
598 reverts font family and font encoding to normal text should be used,
599 for example @code{\normal-text}. The interest of using
600 @code{make-dynamic-script} instead of an ordinary markup is ensuring
601 the vertical alignment of markup objects and hairpins that are
602 attached to the same note head.
604 @lilypond[verbatim,quote]
605 roundF = \markup { \center-align \concat {
606 \normal-text { \bold { \italic ( } }
608 \normal-text { \bold { \italic ) } } } }
609 boxF = \markup { \bracket { \dynamic f } }
610 mfEspress = \markup { \center-align \line {
611 \hspace #3.7 mf \normal-text \italic espress. } }
612 roundFdynamic = #(make-dynamic-script roundF)
613 boxFdynamic = #(make-dynamic-script boxF)
614 mfEspressDynamic = #(make-dynamic-script mfEspress)
616 c'4_\roundFdynamic\< d e f
619 g'1~\mfEspressDynamic
624 The Scheme form of markup mode may be used instead. Its syntax is
625 explained in @rextend{Markup construction in Scheme}.
627 @lilypond[verbatim,quote]
628 moltoF = #(make-dynamic-script
629 (markup #:normal-text "molto"
637 To left-align the dynamic text rather than centering it on a note
640 @lilypond[verbatim,quote]
641 moltoF = \tweak DynamicText.self-alignment-X #LEFT
642 #(make-dynamic-script
643 (markup #:normal-text "molto"
647 <d e>2..\moltoF <d e>1
651 Font settings in markup mode are described in
652 @ref{Selecting font and font size}.
656 @ref{Formatting text},
657 @ref{Selecting font and font size},
658 @ref{Enhancing MIDI output},
659 @ref{Controlling MIDI dynamics}.
662 @rextend{Markup construction in Scheme}.
665 @rlsr{Expressive marks}.
668 @node Expressive marks as curves
669 @subsection Expressive marks as curves
671 This section explains how to create various expressive marks that
672 are curved: normal slurs, phrasing slurs, breath marks, falls, and
683 @unnumberedsubsubsec Slurs
687 @notation{Slurs} are entered using parentheses:
689 @warning{In polyphonic music, a slur must be terminated
690 in the same voice it began.}
692 @lilypond[verbatim,quote]
700 @cindex slurs, manual placement
701 @cindex slurs, below notes
702 @cindex slurs, above notes
705 @funindex \slurNeutral
706 @funindex slurNeutral
708 Slurs may be manually placed above or below the staff; see
709 @ref{Direction and placement}.
711 @cindex phrasing slur
712 @cindex multiple slurs
713 @cindex simultaneous slurs
714 @cindex slur, phrasing
715 @cindex slurs, multiple
716 @cindex slurs, simultaneous
719 Simultaneous or overlapping slurs require special attention. Most
720 occurences of outer slurs actually indicate phrasing, and phrasing
721 slurs may overlap a regular slur, see @ref{Phrasing slurs}. When
722 multiple regular slurs are needed in a single @code{Voice},
723 matching slur starts and ends need to be labelled by preceding
724 them with @code{\=} followed by an identifying number or string.
726 @lilypond[verbatim,quote]
728 <c~ f\=1( g\=2( >2 <c e\=1) a\=2) >
740 @funindex \slurDashed
742 @funindex \slurDotted
747 Slurs can be solid, dotted, or dashed. Solid is the default slur
750 @lilypond[verbatim,quote]
762 @funindex \slurHalfDashed
763 @funindex slurHalfDashed
764 @funindex \slurHalfSolid
765 @funindex slurHalfSolid
766 @cindex slur, half dashed and half solid
768 Slurs can also be made half-dashed (the first half dashed, the
769 second half solid) or half-solid (the first half solid, the second
772 @lilypond[verbatim,quote]
784 @funindex \slurDashPattern
785 @funindex slurDashPattern
786 @cindex slur, defining dash patterns
788 Custom dash patterns for slurs can be defined:
790 @lilypond[verbatim,quote]
793 \slurDashPattern #0.7 #0.75
795 \slurDashPattern #0.5 #2.0
814 @code{\slurHalfDashed},
815 @code{\slurHalfSolid},
816 @code{\slurDashPattern},
823 @lilypondfile[verbatim,quote,texidoc,doctitle]
824 {using-double-slurs-for-legato-chords.ly}
826 @lilypondfile[verbatim,quote,texidoc,doctitle]
827 {positioning-text-markups-inside-slurs.ly}
829 @lilypondfile[verbatim,quote,texidoc,doctitle]
830 {making-slurs-with-complex-dash-structure.ly}
837 @rlearning{On the un-nestedness of brackets and ties}.
840 @ref{Direction and placement},
841 @ref{Phrasing slurs}.
844 @rlsr{Expressive marks}.
851 @unnumberedsubsubsec Phrasing slurs
853 @cindex phrasing slurs
854 @cindex phrasing marks
855 @cindex slur, phrasing
856 @cindex mark, phrasing
860 @notation{Phrasing slurs} (or phrasing marks) that indicate a
861 musical sentence are written using the commands @code{\(} and
862 @code{\)} respectively:
864 @lilypond[verbatim,quote]
871 @funindex \phrasingSlurUp
872 @funindex phrasingSlurUp
873 @funindex \phrasingSlurDown
874 @funindex phrasingSlurDown
875 @funindex \phrasingSlurNeutral
876 @funindex phrasingSlurNeutral
878 Typographically, a phrasing slur behaves almost exactly like a
879 normal slur. However, they are treated as different objects; a
880 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
881 may be manually placed above or below the staff; see
882 @ref{Direction and placement}.
884 @cindex simultaneous phrasing slurs
885 @cindex multiple phrasing slurs
886 @cindex slur, simultaneous phrasing
887 @cindex slur, multiple phrasing
888 @cindex phrasing slur, simultaneous
889 @cindex phrasing slur, multiple
891 Simultaneous or overlapping phrasing slurs are entered using
892 @code{\=} as with regular slurs, see @ref{Slurs}.
894 @funindex phrasingSlurDashed
895 @funindex \phrasingSlurDashed
896 @funindex \phrasingSlurDotted
897 @funindex phrasingSlurDotted
898 @funindex \phrasingSlurSolid
899 @funindex phrasingSlurSolid
900 @cindex phrasing slur, dashed
901 @cindex dashed phrasing slur
902 @cindex phrasing slur, dotted
903 @cindex dotted phrasing slurs
904 @cindex slur, dashed phrasing
905 @cindex slur, dotted phrasing
907 Phrasing slurs can be solid, dotted, or dashed. Solid is the default
908 style for phrasing slurs:
910 @lilypond[verbatim,quote]
922 @funindex phrasingSlurHalfDashed
923 @funindex \phrasingSlurHalfDashed
924 @funindex \phrasingSlurHalfSolid
925 @funindex phrasingSlurHalfSolid
926 @cindex phrasing slur, half solid and half dashed
927 @cindex slur, half solid and half dashed phrasing
929 Phrasing slurs can also be made half-dashed (the first half dashed, the
930 second half solid) or half-solid (the first half solid, the second
933 @lilypond[verbatim,quote]
936 \phrasingSlurHalfDashed
938 \phrasingSlurHalfSolid
945 @funindex \phrasingSlurDashPattern
946 @funindex phrasingSlurDashPattern
947 @cindex phrasing slur, defining dash patterns
948 @cindex slur, phrasing, defining dash patterns
949 @cindex slur, defining dash patterns for phrasing
951 Custom dash patterns for phrasing slurs can be defined:
953 @lilypond[verbatim,quote]
956 \phrasingSlurDashPattern #0.7 #0.75
958 \phrasingSlurDashPattern #0.5 #2.0
965 Dash pattern definitions for phrasing slurs have the same structure
966 as dash pattern definitions for slurs. For more information about
967 complex dash patterns, see the snippets under @ref{Slurs}.
970 @code{\phrasingSlurUp},
971 @code{\phrasingSlurDown},
972 @code{\phrasingSlurNeutral},
973 @code{\phrasingSlurDashed},
974 @code{\phrasingSlurDotted},
975 @code{\phrasingSlurHalfDashed},
976 @code{\phrasingSlurHalfSolid},
977 @code{\phrasingSlurDashPattern},
978 @code{\phrasingSlurSolid}.
983 @rlearning{On the un-nestedness of brackets and ties}.
986 @ref{Direction and placement},
990 @rlsr{Expressive marks}.
993 @rinternals{PhrasingSlur}.
997 @unnumberedsubsubsec Breath marks
1004 Breath marks are entered using @code{\breathe}:
1006 @lilypond[verbatim,quote]
1007 { c''2. \breathe d''4 }
1010 Unlike other expressive marks, a breath mark is not associated with
1011 the preceding note but is a separate music event. So all the
1012 expressive marks which are attached to the preceding note, any square
1013 brackets indicating manual beams, and any brackets indicating slurs
1014 and phrasing slurs must be placed before @code{\breathe}.
1016 A breath mark will end an automatic beam; to override this behavior, see
1019 @lilypond[verbatim,quote]
1020 \relative { c''8 \breathe d e f g2 }
1023 Musical indicators for breath marks in ancient notation,
1024 divisiones, are supported. For details, see @ref{Divisiones}.
1029 @lilypondfile[verbatim,quote,texidoc,doctitle]
1030 {changing-the-breath-mark-symbol.ly}
1034 @lilypondfile[verbatim,quote,texidoc,doctitle]
1035 {using-a-tick-as-the-breath-mark-symbol.ly}
1038 @cindex railroad tracks
1040 @lilypondfile[verbatim,quote,texidoc,doctitle]
1041 {inserting-a-caesura.ly}
1051 @rlsr{Expressive marks}.
1053 Internals Reference:
1054 @rinternals{BreathingEvent},
1055 @rinternals{BreathingSign},
1056 @rinternals{Breathing_sign_engraver}.
1059 @node Falls and doits
1060 @unnumberedsubsubsec Falls and doits
1064 @funindex \bendAfter
1067 @notation{Falls} and @notation{doits} can be added to notes using
1068 the @code{\bendAfter} command. The direction of the fall or doit
1069 is indicated with a plus or minus (up or down). The number
1070 indicates the pitch interval that the fall or doit will extend
1071 @emph{beyond} the main note.
1073 @lilypond[verbatim,quote]
1086 @lilypondfile[verbatim,quote,texidoc,doctitle]
1087 {adjusting-the-shape-of-falls-and-doits.ly}
1095 @rlsr{Expressive marks}.
1098 @node Expressive marks as lines
1099 @subsection Expressive marks as lines
1101 This section explains how to create various expressive marks that
1102 follow a linear path: glissandos, arpeggios, and trills.
1111 @unnumberedsubsubsec Glissando
1114 @funindex \glissando
1117 A @notation{glissando} is created by appending @code{\glissando}
1120 @lilypond[verbatim,quote]
1124 \afterGrace f,1\glissando f'16
1128 A glissando can connect notes across staves:
1130 @lilypond[verbatim,quote]
1132 \new Staff = "right" {
1134 \change Staff = "left"
1136 \change Staff = "right"
1139 \new Staff = "left" {
1146 A glissando can connect notes in chords. If anything other than a
1147 direct one-to-one pairing of the notes in the two chords is required
1148 the connections between the notes are defined by setting
1149 @code{\glissandoMap}, where the notes of a chord are assumed to be
1150 numbered from zero in the order in which they appear in the input
1153 @lilypond[verbatim,quote]
1155 <c' e>1\glissando g' |
1159 \set glissandoMap = #'((0 . 1) (1 . 0))
1160 <c, g'>1\glissando |
1162 \set glissandoMap = #'((0 . 0) (0 . 1) (0 . 2))
1165 \set glissandoMap = #'((2 . 0) (1 . 0) (0 . 1))
1166 <f d a'>1\glissando |
1171 Different styles of glissandi can be created. For details, see
1176 @lilypondfile[verbatim,quote,texidoc,doctitle]
1177 {contemporary-glissando.ly}
1179 @lilypondfile[verbatim,quote,texidoc,doctitle]
1180 {adding-timing-marks-to-long-glissandi.ly}
1182 @lilypondfile[verbatim,quote,texidoc,doctitle]
1183 {making-glissandi-breakable.ly}
1185 @lilypondfile[verbatim,quote,texidoc,doctitle]
1186 {extending-glissandi-across-repeats.ly}
1196 @rlsr{Expressive marks}.
1198 Internals Reference:
1199 @rinternals{Glissando}.
1202 Printing text over the line (such as @notation{gliss.}) is not
1207 @unnumberedsubsubsec Arpeggio
1210 @cindex broken chord
1211 @cindex chord, broken
1215 @funindex \arpeggioArrowUp
1216 @funindex arpeggioArrowUp
1217 @funindex \arpeggioArrowDown
1218 @funindex arpeggioArrowDown
1219 @funindex \arpeggioNormal
1220 @funindex arpeggioNormal
1222 An @notation{arpeggio} on a chord (also known as a broken chord)
1223 is denoted by appending @code{\arpeggio} to the chord construct:
1225 @lilypond[verbatim,quote]
1226 \relative { <c' e g c>1\arpeggio }
1229 Different types of arpeggios may be written.
1230 @code{\arpeggioNormal} reverts to a normal arpeggio:
1232 @lilypond[verbatim,quote]
1234 <c' e g c>2\arpeggio
1247 @cindex arpeggio symbols, special
1248 @cindex special arpeggio symbols
1250 @funindex \arpeggioBracket
1251 @funindex arpeggioBracket
1252 @funindex \arpeggioParenthesis
1253 @funindex arpeggioParenthesis
1254 @funindex \arpeggioParenthesisDashed
1255 @funindex arpeggioParenthesisDashed
1257 Special @emph{bracketed} arpeggio symbols can be created:
1259 @lilypond[verbatim,quote]
1266 \arpeggioParenthesis
1269 \arpeggioParenthesisDashed
1277 The dash properties of the parenthesis arpeggio are controlled
1278 with the @code{'dash-definition} property, which is described at
1281 Arpeggios can be explicitly written out with ties. For more
1282 information, see @ref{Ties}.
1287 @code{\arpeggioArrowUp},
1288 @code{\arpeggioArrowDown},
1289 @code{\arpeggioNormal},
1290 @code{\arpeggioBracket},
1291 @code{\arpeggioParenthesis}
1292 @code{\arpeggioParenthesisDashed}.
1298 @lilypondfile[verbatim,quote,texidoc,doctitle]
1299 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
1301 @lilypondfile[verbatim,quote,texidoc,doctitle]
1302 {creating-cross-staff-arpeggios-in-other-contexts.ly}
1304 @lilypondfile[verbatim,quote,texidoc,doctitle]
1305 {creating-arpeggios-across-notes-in-different-voices.ly}
1316 @rlsr{Expressive marks}.
1318 Internals Reference:
1319 @rinternals{Arpeggio},
1321 @rinternals{PianoStaff}.
1324 @cindex cross-staff parenthesis-style arpeggio
1325 @cindex arpeggio, parenthesis-style, cross-staff
1326 @cindex arpeggio, cross-staff parenthesis-style
1328 It is not possible to mix connected arpeggios and unconnected
1329 arpeggios in one @code{PianoStaff} at the same point in
1332 The simple way of setting parenthesis-style arpeggio brackets does not work for
1333 cross-staff arpeggios; see @ref{Cross-staff stems}.
1337 @unnumberedsubsubsec Trills
1343 @funindex \startTrillSpan
1344 @funindex startTrillSpan
1345 @funindex \stopTrillSpan
1346 @funindex stopTrillSpan
1348 Short trills without an extender line are printed with
1349 @code{\trill}; see @ref{Articulations and ornamentations}.
1351 Longer trills with an extender line are made with
1352 @code{\startTrillSpan} and @code{\stopTrillSpan}:
1354 @lilypond[verbatim,quote]
1363 A trill spanner crossing a line break will restart exactly above
1364 the first note on the new line.
1366 @lilypond[ragged-right,verbatim,quote]
1376 Consecutive trill spans will work without explicit
1377 @code{\stopTrillSpan} commands, since successive trill spanners will
1378 automatically become the right bound of the previous trill.
1380 @lilypond[verbatim,quote]
1390 Trills can also be combined with grace notes. The syntax of this
1391 construct and the method to precisely position the grace notes are
1392 described in @ref{Grace notes}.
1394 @lilypond[verbatim,quote]
1397 d1\startTrillSpan { c32[ d]\stopTrillSpan }
1402 @cindex pitched trills
1403 @cindex trills, pitched
1404 @funindex \pitchedTrill
1405 @funindex pitchedTrill
1407 Trills that require an auxiliary note with an explicit pitch can
1408 be typeset with the @code{\pitchedTrill} command. The first
1409 argument is the main note, and the second is the @emph{trilled}
1410 note, printed as a stemless note head in parentheses.
1412 @lilypond[verbatim,quote]
1415 d''2\startTrillSpan fis
1422 @cindex pitched trill with accidental
1423 @cindex trill with accidental
1425 Subsequent accidentals of the same note in the same measure will need
1426 to be added manually. Only the accidental of the first pitched trill
1427 in a measure is printed.
1429 @lilypond[verbatim,quote]
1432 eis''4\startTrillSpan fis
1435 eis4\startTrillSpan cis
1438 eis4\startTrillSpan fis
1441 eis4\startTrillSpan fis!
1447 @code{\startTrillSpan},
1448 @code{\stopTrillSpan}.
1456 @ref{Articulations and ornamentations},
1460 @rlsr{Expressive marks}.
1462 Internals Reference:
1463 @rinternals{TrillSpanner}.