Re: simultaneous tempo-change events

[James]

On 07/06/14 11:36, Federico Bruni wrote:
> 2014-06-02 15:56 GMT+02:00 Knute Snortum <address@hidden>:
>
>> That's fine.  It just took me a couple of minutes to figure out that it was
>> the compile last measures feature making the warning.  Maybe a note in the
>> documents saying that the feature can produce oddities.
>>
> In NR 3.4.2:
>
> "This property is also used to control output to the MIDI file. Note that
> it skips all events, including tempo and instrument changes. You have been
> warned."
>
> Well, this sentence is about the property Score.skipTypesetting (not
> showLastLength).
> It seems that it doesn't actually skips the tempo changes. In the example
> below, the last bar is compiled, but the first tempo is printed and I get
> the warning we are discussing here. I get the same result if I comment
> skipTypesetting and uncomment showLastLength.
>
> \version "2.19.7"
>
> %showLastLength = R1
>
> \relative c' {
>   \set Score.skipTypesetting = ##t
>   \tempo 4 = 80
>   c4 c c c
>
>   \set Score.skipTypesetting = ##f
>   \tempo 4 = 90
>   d4 d d d
>
> }
>
> Documentation should be changed, I guess... Another example:
>
> \version "2.19.7"
>
> \relative c' {
>   c1
>   \set Score.skipTypesetting = ##t
>   \tempo 4 = 80
>   c4 c c c
>
>   \set Score.skipTypesetting = ##f
>   d4 d d d
> }
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
http://code.google.com/p/lilypond/issues/detail?id=3953

James