On Lilypond 2.1.16 (self compiled). Originally noticed on 2.0.1
Not sure whether these are interrelated or should be reported
separately. The attached .ly and .pdf/.dvi) are the original test
case(s). Hopefully I've put in slightly more concise test cases in line
here.
1: Chorded polyphony wit
[EMAIL PROTECTED] writes:
> 2: Collision avoidance is different in non-chorded vs chorded polyphony
> ( shown in bars (6 vs 7) compared to (9 vs 10)). I believe the chord
> case should use the same decision as the single-note case.
No. The chord with the dots should always go to the right in thes
[EMAIL PROTECTED] writes:
> 1: Chorded polyphony with dotted notes in voice 1 misplaces dots (as
> shown in attached output bar 7)
Fixed.
> 3: Starting a score with polyphony seems to generate unnecessary new
> contexts. (I discovererd this while eliminating the 'r1' at the
> beginning of each s
Hans Forbrich wrote:
On Lilypond 2.1.16 (self compiled). Originally noticed on 2.0.1
3: Starting a score with polyphony seems to generate unnecessary new
contexts. (I discovererd this while eliminating the 'r1' at the
beginning of each system, trying to simplify the test cases - not
bothering m
Using the 2.1.20 release:
Han-Wen Nienhuys wrote:
>
> [EMAIL PROTECTED] writes:
> > 1: Chorded polyphony with dotted notes in voice 1 misplaces dots (as
> > shown in attached output bar 7)
>
> Fixed.
>
Original test case now works. Thanks.
But the actual from my score doesn't, so I've attach
Using the 2.1.20 release:
Han-Wen Nienhuys wrote:
>
> [EMAIL PROTECTED] writes:
> > 1: Chorded polyphony with dotted notes in voice 1 misplaces dots (as
> > shown in attached output bar 7)
>
> Fixed.
>
Original test case now works. Thanks.
But the actual from my score doesn't, so I've attach
[EMAIL PROTECTED] writes:
>
> But the actual from my score doesn't, so I've attached the minimum
> snippet with several test cases. Each test case is on a staff by
> itself:
>
> 1) the original problem;
> 2) swap the two voices - better, but stems in wrong direction
> (obviously);
> 3) try for
