Urs Liska <lilyli...@googlemail.com> writes:
> Am 24.09.2014 22:11, schrieb David Kastrup:
>> Urs Liska <lilyli...@googlemail.com> writes:
>>
>>> -------- Original-Nachricht --------
>>> Betreff: Isolated durations and \pageBreak
>>> Datum: Wed, 24 Sep 2014 19:50:33 +0200
>>> Von: Davide Liessi <davide.lie...@gmail.com>
>>> An: lilypond-u...@gnu.org <lilypond-u...@gnu.org>
>>>
>>>
>>>
>>> Hi all.
>>>
>>> Isolated durations don't behave well with \pageBreak.
>>> The following example gives a failed barcheck warning and wrong output.
>>>
>>> %%%%%
>>> \version "2.19.13"
>>> \score {
>>> \new RhythmicStaff {
>>> R1 |
>>> \pageBreak
>>> 1~ |
>>> 8 r r4 r2 |
>>> }
>>> }
>>> %%%%%
>> This example is actually problematic since there is no pitched note
>> anywhere before 1~. The visuals will likely be ok but Midi, if any,
>> will have no pitch to go by.
>
> OK, I can understand that it is a similar situation as with the
> ambiguous midi volume warnings. But then I'd expect a warning (or a
> misbehaviour) in that domain and not a change in the timing structure.
Well, "the visuals will likely be ok" was supposed to mean "the visuals
would likely be ok in spite of this, once the error I acknowledge below
is fixed". Not easy to decipher, I admit, but otherwise the rest I
wrote would not have made a lot of sense.
>> However, \pagebreak indeed disrupts the pitch/chord copying when one
>> corrects this, for example by replacing R1 with c1.
>>
>>> Either commenting \pageBreak, adding an explicit pitch to 1~ or adding
>>> an explicitly pitched note *after* the \pageBreak result in no
>>> barcheck warnings and correct output.
>>> Adding an explicitly pitched note *before* the \pageBreak still gives
>>> the barcheck warning and wrong output.
>> Yup.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
