|
From: | Nick Payne |
Subject: | Re: Beam avoidance of other voices and stem length for beamed notes |
Date: | Thu, 05 May 2011 19:12:51 +1000 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 |
On 05/05/11 13:21, address@hidden wrote:
Yes, that seems to be why, as if I add \once \override NoteColumn #'force-hshift = #1 at the beginning of voice 2, then both beams intersect the rests above. However, if the collision avoidance mechanism does shift the note at the beginning of voice 2 horizontally, why doesn't it shift the note far enough for the stem/beam to avoid the flag on the note in voice 1, given that it manages to do so successfully for the second beat in the bar. Or is that difference due to the notes in the two voices being a third apart on the first beat but only a second apart on the second beat.On May 4, 2011, at 3:16 PM, Nick Payne wrote:Latest LP development version has inconsistency. See below. \version "2.13.61" \relative c'' { \time 3/4 \key d \minor << {<e bes>8 r<e a,> r s } \\ { d, r cis r r4 } \\ { g'8. f16 g8. bes16 a8. g16 } }The disparity in results comes (I think) from the fact that the flag of the stem in the left example ends after the beam begins on the X axis, and thus, the beam collision engraver moves the beam up to avoid the entire stem+flag. In the second example, on the other hand, the flag's rightmost X point falls to the left of the beam's leftmost X point.
Nick
[Prev in Thread] | Current Thread | [Next in Thread] |