@unnumberedsubsubsec Spoken music
@cindex parlato
@cindex Sprechgesang
-Such effects as @q{parlato} or @q{Sprechgesang} require perfomers to speak
+Such effects as @q{parlato} or @q{Sprechgesang} require performers to speak
without pitch but still with rhythm; these are notated by cross
note heads, as demonstrated in @ref{Special note heads}.
@cindex spaces, in lyrics
@cindex quotes, in lyrics
-@c FIXME: this section is to be rewritten.
+@c TODO: this section is to be rewritten.
Since LilyPond input files are text, there is at least one
issue to consider when working with vocal music:
song texts must be interpreted as text, not notes. For example, the
@rinternals{LyricSpace}.
-@c FIXME: this title has to be changed (possible confusion with LM) -vv
+@c TODO: this title has to be changed (possible confusion with LM) -vv
@node Setting simple songs
@unnumberedsubsubsec Setting simple songs
@end example
@ignore
-@c FIXME
+@c TODO
http://code.google.com/p/lilypond/issues/detail?id=329
The problem cannot be reproduced.
The following has no sense, because the issue seems to be fixed.
Be careful when defining a variable with lyrics that creates a new
-context, for example, using the deprecated @code{\lyrics} command. See
+context, for example, using the deprecated @code{\lyrics} command. See
the next erroneous example:
@example
@funindex \addlyrics
@funindex \lyricsto
-@c FIXME: this stuff is to be rewritten. -vv
+@c TODO: this stuff is to be rewritten. -vv
Aligning of text with melodies can be made automatically, but if you
specify the durations of the syllables it can also be made manually.
You can define melismata entirely in the lyrics, by entering @code{_}
for every extra note that has to be added to the melisma.
-@c FIXME: clarify: __ is used to crate a lyric extender,
+@c TODO: clarify: __ is used to crate a lyric extender,
@c _ is used to add a note to a melisma, so both __ and _ are needed.
@c verbose! --FV
@c duplicated: TODO fix
-Additionaly, you can make an extender line to be typeset to indicate
+Additionally, you can make an extender line to be typeset to indicate
the melisma in the score, writing a double underscore next to the
-first syllable of the melisma. This example shows the three elements
+first syllable of the melisma. This example shows the three elements
that are used for this purpose (all of them surrounded by spaces):
double hyphens to separate syllables in a word, underscores to add
notes to a melisma, and a double underscore to put an extender line.
-@c wrong: extender line only on last syllable of a word. Change example
+@c wrong: extender line only on last syllable of a word. Change example
@lilypond[relative=1,verbatim,fragment,quote]
{ \set melismaBusyProperties = #'()
c d( e) f f( e) e e }
>>
@end lilypond
-@c FIXME: this now links to LM -vv
+@c TODO: this now links to LM -vv
+@c umm, yeah... so what? -gp
@cindex SATB
@cindex choral score
@node Specific uses of lyrics
@subsection Specific uses of lyrics
-@c FIXME This whole section is to be reorganized. -vv
+@c TODO This whole section is to be reorganized. -vv
Often, different stanzas of one song are put to one melody in slightly
differing ways. Such variations can still be captured with
This method is recommended only if the music in the @code{Devnull}
context does not contain melismata. Melismata are defined by the
-@code{Voice} context. Connecting lyrics to a @code{Devnull} context
+@code{Voice} context. Connecting lyrics to a @code{Devnull} context
makes the voice/lyrics links to get lost, and so does the info on
melismata. Therefore, if you link lyrics to a @code{Devnull} context,
the implicit melismata get ignored.
@code{\set} and @code{\unset} to bracket the lyrics where melismata
are to be ignored.
+@subsubheading Adding syllables to grace notes
+
+By default, grace notes (e.g. via @code{\grace}) do not get assigned
+syllables when using @code{\lyricsto}, but this behavior can be
+changed:
+
+@lilypond[verbatim,ragged-right,quote]
+\relative c' {
+ f4 \appoggiatura a32 b4
+ \grace { f16[ a16] } b2
+ \afterGrace b2 { f16[ a16] }
+ \appoggiatura a32 b4
+ \acciaccatura a8 b4
+}
+\addlyrics {
+ normal
+ \set includeGraceNotes = ##t
+ case,
+ gra -- ce case,
+ after -- grace case,
+ \set ignoreMelismata = ##t
+ app. case,
+ acc. case.
+}
+@end lilypond
+
+@knownissues
+Like for @code{associatedVoice}, @code{includeGraceNotes} needs to be
+set at latest one syllable before the one which is to be put under a
+grace note. For the case of a grace note at the very beginning of a
+piece of music, consider using a @code{\with} or @code{\context}
+block:
+
+@lilypond[verbatim,ragged-right,quote]
+<<
+ \new Voice = melody \relative c' {
+ \grace { c16[( d e f] }
+ g1) f
+ }
+ \new Lyrics \with { includeGraceNotes = ##t }
+ \lyricsto melody {
+ Ah __ fa
+ }
+>>
+@end lilypond
+
@subsubheading Switching to an alternative melody
More complex variations in text underlay are possible. It is possible
Here, @code{alternative} is the name of the @code{Voice} context
containing the triplet.
-@c FIXME: make this easier to understand -vv
+@c TODO: make this easier to understand -vv
This command must be one syllable too early, before @q{Ty} in this
case. In other words, changing the associatedVoice happens one step
later than expected. This is for technical reasons, and it is not a
projects / lilypond.git / blobdiff