Hello Patrick,
first thing: _Please_ mind the advice given with every single digest and
edit the subject line so the e-mail may be correctly sorted into the
thread where it belongs. I also find it quite annoying to receive
e-mails with such cryptic subjects as this.
Am 14.02.2015 18:18, schrieb Patrick Karl:
I have run into a couple of anomalies with the \articulate command and the abbreviation
"rit."
First,
\version "2.19.15"
\include "articulate.ly"
\score{
\unfoldRepeats \articulate
\new ChoirStaff <<
\new Staff c-"rit."
Does
@code{ \new Staff { \tempo %{\markup\normal-text%} "rit." }
produce the same warnings? Unlike text scripts, as in your example,
MetronomeMarks (created by the \tempo command) are collected and
displayed only once at the top of the score. I don’t know how this
interacts with articulate.ly, though.
\new Staff c-"rit."
>>
\layout { }
\midi { }
}
throws a warning: warning: Two simultaneous tempo-change events, junking
this one
warning: Previous tempo-change event here
If "rit." is replaced with "\markup { "rit." }, no warning is thrown. Section "1.8.1
Writing text" pretty much implies that those two ways of generating text are equivalent.
I don't think this warning should occur. Isn't it a common thing to place such
a notation in all staves so that if parts are generated, each part will have
the notation.
Second,
\version "2.19.15"
\include "articulate.ly"
music = \relative c'' { \repeat unfold 21 { c d e f} c-"rit." d e f \repeat
unfold 6 { c d e f }}
\score { {
\unfoldRepeats \articulate
\new Staff \music
}
\layout { }
\midi { }
}
generates a midi file that begins with the tempo "4=60" (the default) and then changes to "4=36" at
measure 22 and remains there for the remainder of the midi file. if "rit." is replaced with \markup {
"rit." } the tempo is a constant 4=60 for the whole midi file.
I think the most disturbiing thing is that \articulate is interpreting "rit." to mean "ritenuto"
rather than "ritardando", which I think is the most common interpretation of "rit.".
There are different opinions on this.
It would be great if the tempo would ramp down gradually to "4=36" at the
end.
…which would actually require a specification on where the ritardando is
supposed to end, which might be done either by a new \tempo indication
or by a “tempo spanner”, which can be found on the wishlist:
<https://code.google.com/p/lilypond/issues/detail?id=3176>. So currently
there is no method to do this.
HTH, Simon
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user