X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fnotation%2Fexpressive.itely;h=9ab9fdcb5cb0bb1c5fe84c6ff9476ee1d0f2382d;hb=0129dea8eff59c10ba6e295f6f2cd48083fc5296;hp=0d86f3e639dd7b1344726ce61b11e680dd37e088;hpb=9a73c67a79a21b889d67f8d28f2c106de830d936;p=lilypond.git diff --git a/Documentation/notation/expressive.itely b/Documentation/notation/expressive.itely index 0d86f3e639..9ab9fdcb5c 100644 --- a/Documentation/notation/expressive.itely +++ b/Documentation/notation/expressive.itely @@ -7,7 +7,7 @@ Guide, node Updating translation committishes.. @end ignore -@c \version "2.14.0" +@c \version "2.18.0" @node Expressive marks @section Expressive marks @@ -148,7 +148,7 @@ articulation. Predefined shorthands exist for @notation{marcato}, Their corresponding output appears as follows: @lilypond[verbatim,quote,relative=2] -c4-^ c-+ c-- c-| +c4-^ c-+ c-- c-! c4-> c-. c2-_ @end lilypond @@ -167,8 +167,8 @@ to a multi-measure rest (and only a multi-measure rest). This creates a @code{MultiMeasureRestText} object. @lilypond[verbatim,quote,relative=2] -\override Script #'color = #red -\override MultiMeasureRestText #'color = #blue +\override Script.color = #red +\override MultiMeasureRestText.color = #blue a2\fermata r\fermata R1\fermataMarkup @end lilypond @@ -472,6 +472,16 @@ items such as text scripts, text spanners, and piano pedal marks. @lilypondfile[verbatim,quote,texidoc,doctitle] {printing-hairpins-using-al-niente-notation.ly} +@cindex Ferneyhough hairpins +@cindex hairpins, Ferneyhough +@cindex flared hairpins +@cindex hairpins, flared +@cindex constante hairpins +@cindex hairpins, constante + +@lilypondfile[verbatim,quote,texidoc,doctitle] +{printing-hairpins-in-various-styles.ly} + @lilypondfile[verbatim,quote,texidoc,doctitle] {vertically-aligned-dynamics-and-textscripts.ly} @@ -494,7 +504,7 @@ Learning Manual: Notation Reference: @ref{Direction and placement}, @ref{New dynamic marks}, -@ref{What goes into the MIDI output?}, +@ref{Enhancing MIDI output}, @ref{Controlling MIDI dynamics}. Snippets: @@ -604,6 +614,20 @@ moltoF = #(make-dynamic-script } @end lilypond +To left-align the dynamic text rather than centering it on a note +use a @code{\tweak}: + +@lilypond[verbatim,quote] +moltoF = \tweak DynamicText.self-alignment-X #LEFT + #(make-dynamic-script + (markup #:normal-text "molto" + #:dynamic "f")) +\relative c' { + 16 + 2..\moltoF 1 +} +@end lilypond + Font settings in markup mode are described in @ref{Selecting font and font size}. @@ -611,7 +635,7 @@ Font settings in markup mode are described in Notation Reference: @ref{Formatting text}, @ref{Selecting font and font size}, -@ref{What goes into the MIDI output?}, +@ref{Enhancing MIDI output}, @ref{Controlling MIDI dynamics}. Extending LilyPond: @@ -936,6 +960,12 @@ Breath marks are entered using @code{\breathe}: c2. \breathe d4 @end lilypond +Unlike other expressive marks, a breath mark is not associated with +the preceding note but is a separate music event. So all the +expressive marks which are attached to the preceding note, any square +brackets indicating manual beams, and any brackets indicating slurs +and phrasing slurs must be placed before @code{\breathe}. + A breath mark will end an automatic beam; to override this behavior, see @ref{Manual beams}. @@ -952,6 +982,11 @@ divisiones, are supported. For details, see @ref{Divisiones}. @lilypondfile[verbatim,quote,texidoc,doctitle] {changing-the-breath-mark-symbol.ly} +@cindex tick mark + +@lilypondfile[verbatim,quote,texidoc,doctitle] +{using-a-tick-as-the-breath-mark-symbol.ly} + @cindex caesura @cindex railroad tracks @@ -989,18 +1024,14 @@ indicates the pitch interval that the fall or doit will extend @emph{beyond} the main note. @lilypond[verbatim,quote,relative=2] -c2-\bendAfter #+4 -c2-\bendAfter #-4 -c2-\bendAfter #+6.5 -c2-\bendAfter #-6.5 -c2-\bendAfter #+8 -c2-\bendAfter #-8 +c2\bendAfter #+4 +c2\bendAfter #-4 +c2\bendAfter #+6.5 +c2\bendAfter #-6.5 +c2\bendAfter #+8 +c2\bendAfter #-8 @end lilypond -The dash @code{-} immediately preceding the @code{\bendAfter} -command is @emph{required} when writing falls and doits. - - @snippets @lilypondfile[verbatim,quote,texidoc,doctitle] @@ -1034,24 +1065,72 @@ follow a linear path: glissandos, arpeggios, and trills. @funindex \glissando @funindex glissando -A @notation{glissando} is created by attaching @code{\glissando} +A @notation{glissando} is created by appending @code{\glissando} to a note: @lilypond[verbatim,quote,relative=2] g2\glissando g' c2\glissando c, +\afterGrace f,1\glissando f'16 +@end lilypond + +A glissando can connect notes across staves: + +@lilypond[verbatim,quote] +\new PianoStaff << + \new Staff = "right" { + e'''2\glissando + \change Staff = "left" + a,,4\glissando + \change Staff = "right" + b''8 r | + } + \new Staff = "left" { + \clef bass + s1 + } +>> +@end lilypond + +A glissando can connect notes in chords. If anything other than a +direct one-to-one pairing of the notes in the two chords is required +the connections between the notes are defined by setting +@code{\glissandoMap}, where the notes of a chord are assumed to be +numbered from zero in the order in which they appear in the input +@file{.ly} file. + +@lilypond[verbatim,quote,relative=2] +1\glissando g' | +1\glissando | + | +\break +\set glissandoMap = #'((0 . 1) (1 . 0)) +1\glissando | + | +\set glissandoMap = #'((0 . 0) (0 . 1) (0 . 2)) +c1\glissando | + | +\set glissandoMap = #'((2 . 0) (1 . 0) (0 . 1)) +1\glissando | + | @end lilypond Different styles of glissandi can be created. For details, see @ref{Line styles}. + @snippets +@lilypondfile[verbatim,quote,texidoc,doctitle] +{contemporary-glissando.ly} @lilypondfile[verbatim,quote,texidoc,doctitle] -{glissandi-can-skip-grobs.ly} +{adding-timing-marks-to-long-glissandi.ly} @lilypondfile[verbatim,quote,texidoc,doctitle] -{contemporary-glissando.ly} +{making-glissandi-breakable.ly} + +@lilypondfile[verbatim,quote,texidoc,doctitle] +{extending-glissandi-across-repeats.ly} @seealso Music Glossary: @@ -1139,7 +1218,8 @@ Special @emph{bracketed} arpeggio symbols can be created: @end lilypond The dash properties of the parenthesis arpeggio are controlled -with the @code{'dash-details} property, which is described at @ref{Slurs}. +with the @code{'dash-definition} property, which is described at +@ref{Slurs}. Arpeggios can be explicitly written out with ties. For more information, see @ref{Ties}. @@ -1192,8 +1272,8 @@ It is not possible to mix connected arpeggios and unconnected arpeggios in one @code{PianoStaff} at the same point in time. -The parenthesis-style arpeggio brackets do not work for -cross-staff arpeggios. +The simple way of setting parenthesis-style arpeggio brackets does not work for +cross-staff arpeggios; see @ref{Cross-staff stems}. @node Trills