On Mar 17, 2011, at 9:27 AM, Han-Wen Nienhuys wrote:

> On Thu, Mar 17, 2011 at 9:46 AM,  <mts...@gmail.com> wrote:
>>> this still supposes that there is just one fixed amount of
>> 
>> featheriness?
>> 
>> You're right.
>> I'm honestly not sure exactly how feathering effects this function.  All
>> of the tests I'm running seem to pass just fine, so I'm not sure if this
>> function needs detailed feathering info.  Can you think of a case where
>> this function will fail given the new feathering?  I've been running
>> stuff like this:
>> 
> 
> See beam.cc-
> 
>  /*
>    feather dir = 1 , relx 0->1 : factor 0 -> 1
>    feather dir = 0 , relx 0->1 : factor 1 -> 1
>    feather dir = -1, relx 0->1 : factor 1 -> 0
>   */
>  Real feather_factor = 1;
>  if (feather_dir > 0)
>    feather_factor = relx;
>  else if (feather_dir < 0)
>    feather_factor = 1 - relx;
> 
> it assumes the feathering is fulll across the x range.  I suspect that
> the stem lengths mismatch the beams in broken beam cases.  Try setting
> beam-thickness really small and see if the stems reach up to the
> beams.

I don't see any difference...

\new Staff <<
  \relative c' {
    \cadenzaOn
    \override Staff . TimeSignature #'stencil = ##f
    \override Voice . Beam #'breakable = ##t
    \override Voice . Beam #'beam-thickness = #0.1
    \override Beam #'breakable = ##t
    \once \override Voice . Beam #'feather-direction = #'(1.0 . 0.0)
    a32[ b c d e f g a ]
    \once \override Voice . Beam #'feather-direction = #'(0.75 . 0.0)
    a,32[ b c d e f8 g a ]
    \once \override Voice . Beam #'feather-direction = #'(0.5 . 0.1)
    a32[ b c d e f g a ]
    \once \override Voice . Beam #'feather-direction = #'(0.5 . 0.1)
    a32[ b c d e \bar "" \break f g a ]
    \once \override Voice . Beam #'feather-direction = #'(1.0 . 0.5)
    a32[ b c d e \bar "" \break f g a ]
} >>


<<inline: endpoint-test.png>>

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to