On Apr 22, 2011, at 11:29 PM, Han-Wen Nienhuys wrote:

> On Fri, Apr 22, 2011 at 6:20 PM,  <[email protected]> wrote:
>> 
>> \new Staff {
>>  <<
>>   { \voiceOne s16 fis'' }
>>   \\
>>   { \voiceTwo e4 e }
>>   \\
>>   { \voiceFour
>>   f''8 e'' gis'' gis'' }
>> 
>> }
>> 
>> One interesting thing is that it is the stems, not the noteheads, that
>> are pushing this down.  If you remove stems from the
>> beam-collision-engraver, this problem does not arise.  Why would stems
>> do this but not note heads?
> 
> The problem is that the initial guess for the configuration has two
> choices: over all 'big' collisions, and below the big collisions.  The
> separate high note adds a collision that is impossible to pass from
> the top, so we revert to the bottom.
> 

\new Staff {
 <<
   { \voiceOne s16 \grace fis'' }
   \\
   { \voiceTwo e4 e }
   \\
   { \voiceFour
   f''8 e'' gis'' gis'' }
>>
}

Even with a small high note (see above) the problem kicks in.
If you want, I have some time next week to put in printf's and see what the 
exact numerical cutoff is for picking the lower solution.  My first commitment 
is to have a look @ Janek's flag code, and then I can look over the beam code.

Cheers,
MS
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to