@cindex articulations
@cindex scripts
@cindex ornaments
+@cindex espressivo
+@cindex fermata
+@cindex upbow
+@cindex downbow
+@cindex foot marks
+@cindex organ pedal marks
+@cindex turn
+@cindex open
+@cindex stopped
+@cindex flageolet
+@cindex reverseturn
+@cindex trill
+@cindex prall
+@cindex mordent
+@cindex prallprall
+@cindex prallmordent
+@cindex prall, up
+@cindex prall, down
+@cindex thumb marking
+@cindex segno
+@cindex coda
+@cindex varcoda
A variety of symbols that denote articulations, ornamentations,
and other performance indications can be attached to a note using
The possible values for @var{name} are listed in @ref{List of
articulations}. For example:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c4\staccato c\mordent b2\turn
c1\fermata
@end lilypond
and @notation{portato}. Their corresponding output appears as
follows:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c4-^ c-+ c-- c-|
-c-> c-. c-_
+c4-> c-. c-_
@end lilypond
The rules for the default placement of articulations are defined
in @file{scm/@/script@/.scm}. Articulations and ornamentations
may be manually placed above or below the staff, see
-@ref{Controlling direction and placement}.
-
-@cindex espressivo
-@cindex fermata
-@cindex upbow
-@cindex downbow
-@cindex foot marks
-@cindex organ pedal marks
-@cindex turn
-@cindex open
-@cindex stopped
-@cindex flageolet
-@cindex reverseturn
-@cindex trill
-@cindex prall
-@cindex mordent
-@cindex prallprall
-@cindex prallmordent
-@cindex prall, up
-@cindex prall, down
-@cindex thumb marking
-@cindex segno
-@cindex coda
-@cindex varcoda
+@ref{Direction and placement}.
@snippets
-@c Once revised, add to LSR.
-
-The shorthands are defined in @file{ly/@/script@/-init@/.ly},
-where the variables @code{dashHat}, @code{dashPlus},
-@code{dashDash}, @code{dashBar}, @code{dashLarger},
-@code{dashDot}, and @code{dashUnderscore} are assigned default
-values. The default values for the shorthands can be modified.
-For example, to associate the @code{-+} (@code{dashPlus})
-shorthand with the @notation{trill} symbol instead of the default
-@notation{+} symbol, assign the value @code{trill} to the variable
-@code{dashPlus}:
-
-@lilypond[verbatim,quote,ragged-right]
-\relative c'' { c-+ }
-dashPlus = "trill"
-\relative c'' { c-+ }
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{modifying-default-values-for-articulation-shorthand-notation.ly}
-The vertical ordering of scripts is controlled with the
-@code{script-priority} property. The lower this number, the
-closer it will be put to the note. In this example, the
-@code{TextScript} (the sharp symbol) first has the lowest
-priority, so it is put lowest in the first example. In the
-second, the @notation{prall trill} (the @code{Script}) has the
-lowest, so it is on the inside. When two objects have the same
-priority, the order in which they are entered decides which one
-comes first.
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=3]
-\once \override TextScript #'script-priority = #-100
-a4^\prall^\markup { \sharp }
-
-\once \override Script #'script-priority = #-100
-a4^\prall^\markup { \sharp }
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{controlling-the-vertical-ordering-of-scripts.ly}
@seealso
@rglos{portato}.
Notation Reference:
-@ref{Controlling direction and placement}.
+@ref{Direction and placement}.
Installed Files:
@file{scm/@/script@/.scm}.
@code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
@code{\ffff}, @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp},
@code{\spp}, @code{\sfz}, and @code{\rfz}. The dynamic marks may
-be manually placed above or below the staff, see @ref{Controlling
-direction and placement}.
+be manually placed above or below the staff, see
+@ref{Direction and placement}.
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c2\ppp c\mp
-c\rfz c^\mf
-c_\spp c^\ff
+c2\rfz c^\mf
+c2_\spp c^\ff
@end lilypond
@cindex hairpin
and @code{\decr} may be used instead of @code{\<} and @code{\>}.
@notation{Hairpins} are engraved by default using this notation.
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c2\< c\!
d2\< d\f
e2\< e\>
Spacer notes are needed to engrave multiple marks on one note.
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c4\< c\! d\> e\!
<< f1 { s4 s4\< s4\> s4\! } >>
@end lilypond
the appropriate choice to indicate a @notation{crescendo} and
@notation{decrescendo} on one note:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c2 b4 a
g1\espressivo
@end lilypond
@code{\setHairpinDim}, and @code{\setHairpinDecresc} commands will
revert to hairpins again:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-c\< d e f\!
-e\> d c b\!
+@lilypond[verbatim,quote,relative=2]
+c4\< d e f\!
+e4\> d c b\!
\setTextCresc
-c\< d e f\!
+c4\< d e f\!
\setTextDecresc
-e\> d c b\!
+e4\> d c b\!
\setHairpinCresc
-c\< d e f\!
-@end lilypond
-
-The text used for @notation{crescendos} and
-@notation{decrescendos} can be changed by modifying the context
-properties @code{crescendoText} and @code{decrescendoText}. The
-style of the spanner line can be changed by modifying the context
-properties @code{crescendoSpanner} and @code{decrescendoSpanner}.
-Available values for the spanner properties are @code{'hairpin},
-@code{'line}, @code{'dashed-line}, and @code{'dotted-line}. If
-unset, a hairpin crescendo is used:
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\set crescendoText = \markup { \italic "cresc. poco" }
-\set crescendoSpanner = #'dotted-line
-a'2\< a a a a a a a\mf
+c4\< d e f\!
@end lilypond
To create new absolute dynamic marks or text that should be
@snippets
-@c Add LilyPond examples to these snippets. -pm
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{setting-hairpin-behavior-at-bar-lines.ly}
-@c A @notation{hairpin} normally starts at the left edge of the
-@c beginning note and ends on the right edge of the ending note. If
-@c the ending note falls on the downbeat, the @notation{hairpin} ends
-@c on the immediately preceding bar line. The following example
-@c illustrates this behavior:
-@c
-@c TODO: Add link to new snippet for #'to-barline
-
-If hairpins are too short, they can be lengthened using the
-following method:
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-c4\< c\! d\> e\!
-\override Voice.Hairpin #'minimum-length = #5
-<< f1 { s4 s4\< s4\> s4\! } >>
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{setting-the-minimum-length-of-hairpins.ly}
@cindex al niente
@cindex niente, al
-Hairpins may be printed with a circled tip (al niente notation):
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{printing-hairpins-using-al-niente-notation.ly}
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-\override Hairpin #'circled-tip = ##t
-c2\< c\!
-c4\> c\< c2\!
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{vertically-aligning-dynamics-across-multiple-notes.ly}
-Dynamics that occur at, begin on, or end on the same note will be
-vertically aligned. If you want to ensure that dynamics are
-aligned when they do not occur on the same note, you can increase
-the @code{staff-padding} property.
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{hiding-the-extender-line-for-text-dynamics.ly}
-@example
-\override DynamicLineSpanner #'staff-padding = #4
-@end example
-
-@notation{Crescendi} and @notation{decrescendi} that cross a line
-break will be continued on the second line. If they end on the
-first note of a new line, nothing will be printed on that line.
-To change this behavior, use
-
-@example
-\override Score.Hairpin #'after-line-breaking = ##t
-@end example
-
-Text style dynamic changes (such as @notation{cresc.} and
-@notation{dim.}) are printed with a dashed line showing their
-extent. To suppress printing this line, use
-
-@example
-\override DynamicTextSpanner #'dash-period = #-1.0
-@end example
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{changing-text-and-spanner-styles-for-text-dynamics.ly}
@seealso
@rlearning{Articulation and dynamics}.
Notation Reference:
-@ref{Controlling direction and placement}.
+@ref{Direction and placement}.
Snippets:
@rlsr{Expressive marks}.
@node New dynamic marks
@subsubsection New dynamic marks
-It is possible to print new dynamic marks or text that should be
-aligned with dynamics. Use @code{make-dynamic-script} to create
-these marks. Note that the dynamic font only contains the
-characters @code{f,m,p,r,s} and @code{z}.
+@cindex new dynamic marks
+@cindex dynamic marks, new
+
+The easiest way to create dynamic indications is to use
+@code{\markup} objects.
+
+@lilypond[verbatim,quote]
+moltoF = \markup { molto \dynamic f }
+
+\relative c' {
+ <d e>16 <d e>
+ <d e>2.._\moltoF
+}
+@end lilypond
+
+@cindex dynamics, editorial
+@cindex dynamics, parenthesis
+
+Markup mode makes possible, for instance, to add
+editorial dynamics, printed in round parenthesis or square
+brackets. Its syntax is described in @ref{Formatting text}.
+
+@lilypond[verbatim,quote]
+roundf = \markup { \center-align { \line { \bold { \italic ( }
+ \dynamic f \bold { \italic ) } } } }
+boxf = \markup { \bracket { \dynamic f } }
+\relative c' {
+ c1_\roundf
+ c1_\boxf
+}
+@end lilypond
-Some situations (such as dynamic marks) have preset font-related
-properties. If you are creating text in such situations, it is
-advisable to cancel those properties with @code{normal-text}. See
-@ref{Text markup commands}, for more details.
+Markup objects are treated differently from authentic dynamic marks.
+Defining dynamic objects that will be entered and printed exactly like
+standard dynamic marks is also possible, using the following function:
@cindex make-dynamic-script
-@lilypond[quote,verbatim,ragged-right]
+@lilypond[verbatim,quote]
sfzp = #(make-dynamic-script "sfzp")
\relative c' {
c4 c c\sfzp c
}
@end lilypond
-@cindex Dynamics, editorial
-@cindex Dynamics, parenthesis
+@noindent
+Note that the dynamic font only contains the characters
+@code{f,m,p,r,s} and @code{z}. To switch to other font families,
+it is necessary to use markup mode in its Scheme form, as
+explained in @ref{Markup construction in Scheme}.
+
+@lilypond[verbatim,quote]
+moltoF = #(make-dynamic-script (markup
+ #:normal-text "molto"
+ #:dynamic "f"))
+\relative c' {
+ <d e>16 <d e>
+ <d e>2..\moltoF
+}
+@end lilypond
-It is also possible to print dynamics in round parenthesis or
-square brackets. These are often used for adding editorial
-dynamics.
+@noindent
+Font settings in markup mode are described in
+@ref{Common markup commands}.
-@lilypond[quote,verbatim,ragged-right]
-rndf = \markup{ \center-align {\line { \bold{\italic (}
- \dynamic f \bold{\italic )} }} }
-boxf = \markup{ \bracket { \dynamic f } }
-{ c'1_\rndf c'1_\boxf }
-@end lilypond
@seealso
+Notation Reference:
+@ref{Formatting text},
+@ref{Common markup commands},
+@ref{Markup construction in Scheme}.
+
Snippets:
@rlsr{Expressive marks}.
@cindex slurs
-A @notation{slur} indicates that notes are to be played bound or
-@emph{legato}. They are entered using parentheses:
+@notation{Slurs} are entered using parentheses:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-f( g a) a8 b( a4 g2 f4)
+@lilypond[verbatim,quote,relative=2]
+f4( g a) a8 b(
+a4 g2 f4)
<c e>2( <b d>2)
@end lilypond
-Just as with ties, the direction of a slur can be specified with
-@code{\slur@emph{DIR}}, where @code{@emph{DIR}} is either
-@code{Up}, @code{Down}, or @code{Neutral} (@code{Neutral} is the
-default). Slurs may be manually placed above or below the staff,
-see @ref{Controlling direction and placement}.
+The direction of a @notation{slur} can be specified with
+@code{\slurUp} or @code{\slurDown}. The @code{\slurNeutral}
+command reverts back to the default slur direction.
+@notation{Slurs} may be manually placed above or below the staff,
+see @ref{Direction and placement}.
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-c4_( c) c^( c)
+@lilypond[verbatim,quote,relative=2]
+c2( d)
+\slurDown
+c2( d)
+\slurNeutral
+c2( d)
@end lilypond
-Using this method, only one slur can be printed at once. To print
-a long slur over a few small slurs, see @ref{Phrasing slurs}.
+Different styles of @notation{slurs} may be created with the
+commands @code{\slurDashed} and @code{slurDotted};
+@code{\slurSolid} reverts back to the default @notation{slur}
+style:
+
+@lilypond[verbatim,quote,relative=1]
+c4( e g2)
+\slurDashed
+g4( e c2)
+\slurDotted
+c4( e g2)
+\slurSolid
+g4( e c2)
+@end lilypond
+
+Using this method, only one slur can be printed at once.
+@notation{Phrasing slurs} must be used to print a long slur over
+one or more small slurs. For details, see @ref{Phrasing slurs}.
@predefined
@snippets
-Some composers write two slurs when they want legato chords. This
-can be achieved in LilyPond by setting @code{doubleSlurs},
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\set doubleSlurs = ##t
-<c e>4 ( <d f> <c e> <d f> )
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{using-double-slurs-for-legato-chords.ly}
@seealso
@rglos{slur}.
Notation Reference:
-@ref{Controlling direction and placement}.
+@ref{Direction and placement}.
Snippets:
@rlsr{Expressive marks}.
@funindex \(
@funindex \)
-A phrasing slur (or phrasing mark) connects notes and is used to
-indicate a musical sentence. It is written using @code{\(} and
-@code{\)} respectively:
+@notation{Phrasing slurs} (or @notation{phrasing marks}) that
+indicate a musical sentence are written using the commands
+@code{\(} and @code{\)} respectively:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\time 6/4 c'\( d( e) f( e) d\)
+@lilypond[verbatim,quote,relative=2]
+c4\( d( e) f(
+e2) d\)
@end lilypond
-Typographically, the phrasing slur behaves almost exactly like a
-normal slur. However, they are treated as different objects. A
-@code{\slurUp} will have no effect on a phrasing slur; instead,
-use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
-@code{\phrasingSlurNeutral}. Phrasing slurs may be manually
-placed above or below the staff, see @ref{Controlling direction
-and placement}.
+Typographically, a @notation{phrasing slur} behaves almost exactly
+like a normal @notation{slur}. However, they are treated as
+different objects; a @code{\slurUp} will have no effect on a
+@notation{phrasing slur}. The commands @code{\phrasingSlurUp},
+@code{\phrasingSlurDown}, and @code{\phrasingSlurNeutral} are used
+instead. Phrasing slurs may be manually placed above or below the
+staff, see @ref{Direction and placement}.
-You cannot have simultaneous phrasing slurs.
+@lilypond[verbatim,quote,relative=1]
+c4\( g' c,( b) | c1\)
+\phrasingSlurUp
+c4\( g' c,( b) | c1\)
+@end lilypond
+
+Simultaneous phrasing slurs are not permitted.
@predefined
@seealso
Notation Reference:
-@ref{Controlling direction and placement}.
+@ref{Direction and placement}.
Snippets:
@rlsr{Expressive marks}.
Breath marks are entered using @code{\breathe}:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-c'4 \breathe d4
+@lilypond[verbatim,quote,relative=2]
+c2. \breathe d4
@end lilypond
@snippets
-The glyph of the breath mark can be tuned by overriding the
-@code{text} property of the @code{BreathingSign} layout object
-with any markup text. For example,
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-c'4
-\override BreathingSign #'text
- = #(make-musicglyph-markup "scripts.rvarcomma")
-\breathe
-d4
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{changing-the-breath-mark-symbol.ly}
@seealso
@notation{Falls} and @notation{doits} can be added to notes using
the @code{\bendAfter} command:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c2-\bendAfter #+4
-c-\bendAfter #-4
-c-\bendAfter #+8
-c-\bendAfter #-8
+c2-\bendAfter #-4
+c2-\bendAfter #+8
+c2-\bendAfter #-8
@end lilypond
-The dash (@tie{-}) following the note name is @emph{required} when
-writing @notation{falls} and @notation{doits}.
+The dash (@tie{-}) immediately preceding the @code{\bendAfter}
+command is @emph{required} when writing @notation{falls} and
+@notation{doits}.
@snippets
-The @code{shortest-duration-space} property may have to be tweaked
-to adjust the shape of @notation{falls} and @notation{doits}.
-
-@c Fix this snippet. The tweak does not work. -pm
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-\override Score.SpacingSpanner #'shortest-duration-space = #3.0
-c4-\bendAfter #+5
-c4-\bendAfter #-3
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{adjusting-the-shape-of-falls-and-doits.ly}
@seealso
@cindex glissando
@funindex \glissando
-A @notation{glissando} is a smooth change in pitch. It is denoted
-by a line or a wavy line between two notes. A
-@notation{glissando} is created by attaching @code{\glissando} to
-a note:
+A @notation{glissando} is created by attaching @code{\glissando}
+to a note:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c2\glissando c'
\override Glissando #'style = #'zigzag
c2\glissando c,
@snippets
-@lilypond[verbatim,quote,ragged-right]
+@c Modify, add description, and put in input/new/
+@c @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@c {suppressing-warnings-for-clashing-note-columns.ly}
+
+@lilypond[verbatim,quote]
I = \once \override NoteColumn #'ignore-collision = ##t
\relative c' <<
@cindex arpeggio
@cindex broken chord
+@cindex chord, broken
+
+An @notation{arpeggio} on a chord (also known as a
+@notation{broken chord}) is denoted by appending @code{\arpeggio}
+to the chord construct:
-@c Add documentation for new 'parenthesis' style arpeggio. Maybe
-@c create a new \arpeggioParen command, or something similar. -pm
+@lilypond[verbatim,quote,relative=1]
+<c e g c>1\arpeggio
+@end lilypond
-You can specify an @notation{arpeggio} (also known as a
-@notation{broken chord}) on a chord by attaching an
-@code{\arpeggio} to the chord:
+The direction of an @notation{arpeggio} is indicated by adding an
+arrowhead to the wiggly line. The commands @code{\arpeggioUp} and
+@code{\arpeggioDown} are used for this task.
+@code{\arpeggioNeutral} reverts back to an arrow-less
+@notation{arpeggio}:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-<c e g c>\arpeggio
+@lilypond[verbatim,quote,relative=1]
+\arpeggioUp
+<c e g c>2\arpeggio
+\arpeggioDown
+<c e g c>2\arpeggio
+\arpeggioNeutral
+<c e g c>1\arpeggio
@end lilypond
-A square bracket on the left, denoted by @code{\arpeggioBracket},
-is used to indicate that the chord should @emph{not} be
-arpeggiated:
+The command @code{\arpeggioBracket} can be used to create a square
+bracket on the left of a chord, indicating that the chord should
+@emph{not} be arpeggiated. @code{\arpeggioNeutral} reverts back
+to a regular arpeggio:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
+@lilypond[verbatim,quote,relative=1]
+<c e g c>2
\arpeggioBracket
-<c e g c>\arpeggio
+<c e g c>2\arpeggio
+\arpeggioNeutral
+<c e g c>1\arpeggio
@end lilypond
-The direction of the arpeggio can be denoted by adding an
-arrowhead to the wiggly line. This is done with the commands
-@code{arpeggioUp} and @code{arpeggioDown}. @code{arpeggioNeutral}
-reverts to the arrow-less version:
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\new Voice {
- \arpeggioUp
- <c e g c>\arpeggio
- \arpeggioDown
- <c e g c>\arpeggio
- \arpeggioNeutral
- <c e g c>\arpeggio
-}
+A @emph{parenthesis} style bracket may be attached to an
+@notation{arpeggio} instead of a square bracket.
+
+@c Maybe create a new \arpeggioParen command, or something
+@c like that. -pm
+
+@lilypond[verbatim,quote,relative=1]
+<c e g c>2
+\override Arpeggio #'stencil = #ly:arpeggio::brew-chord-slur
+\override Arpeggio #'X-extent = #ly:grob::stencil-width
+<c e g c>2\arpeggio
+\arpeggioNeutral
+<c e g c>1\arpeggio
@end lilypond
+@notation{Arpeggios} can be explicitly written out with
+@notation{ties}. For more information, see @ref{Ties}.
@predefined
@snippets
-In a @code{PianoStaff}, it is possible to let an arpeggio cross
-between the staves by setting the property
-@code{PianoStaff}.@code{connectArpeggios}.
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{creating-cross-staff-arpeggios-in-a-piano-staff.ly}
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\new PianoStaff <<
- \set PianoStaff.connectArpeggios = ##t
- \new Staff { <c' e g c>\arpeggio }
- \new Staff { \clef bass <c,, e g>\arpeggio }
->>
-@end lilypond
-
-The same can be accomplished in contexts other than
-@code{PianoStaff} if the @code{Span_arpeggio_engraver} is included
-in the Score context.
-
-@lilypond[verbatim,quote,ragged-right]
-\score {
- \new StaffGroup {
- \set Score.connectArpeggios = ##t
- <<
- \new Voice \relative c' {
- <e g>4\arpeggio
- }
- \new Voice \relative c {
- \clef bass
- <c e>4\arpeggio
- }
- >>
- }
- \layout {
- \context {
- \Score
- \consists "Span_arpeggio_engraver"
- }
- }
-}
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{creating-cross-staff-arpeggios-in-other-contexts.ly}
-Similarly, an arpeggio can be drawn across notes in different
-voices on the same staff if the @code{Span_arpeggio_engraver} is
-moved to the Staff context:
-
-@lilypond[verbatim,quote,ragged-right]
-\new Staff
-\with {
- \consists "Span_arpeggio_engraver"
-} \relative c' {
- \set Staff.connectArpeggios = ##t
- <<
- {<e' g>4\arpeggio <d f> <d f>2 }
- \\
- {<d, f>2\arpeggio <g b>2 }
- >>
-}
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{creating-arpeggios-across-notes-in-different-voices.ly}
@seealso
@rglos{arpeggio}.
Notation Reference:
-@ref{Ties}, for writing out arpeggios.
+@ref{Ties}.
Snippets:
@rlsr{Expressive marks}.
combined with grace notes. To achieve precise control of the
placement of the grace notes, see @ref{Grace notes}.
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c1 \afterGrace
d1\startTrillSpan { c16[\stopTrillSpan d] }
c4
@end lilypond
@cindex pitched trills
+@cindex trills, pitched
@notation{Trills} that should be executed on an explicitly
specified pitch can be typeset with the command
@var{trillnote} @var{endnote} @code{\stopTrillSpan}
@end example
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
+@lilypond[verbatim,quote,relative=1]
\pitchedTrill e2 \startTrillSpan fis
d\stopTrillSpan
@end lilypond
projects / lilypond.git / blobdiff