Re: synchronization of feathered beams

[Thomas Morley]

Am Fr., 21. Dez. 2018 um 17:18 Uhr schrieb Reggie <address@hidden>:
>
> Thomas Morley-2 wrote
> > Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie &lt;
>
> > reegistoop@
>
> > &gt;:
> >
> >> It's impossible to have feather
> >> beams cross barlines and look correect why is this?
> >
> > ??
> >
> > What's wrong with:
> >
> > \version "2.19.82"
> >
> > {
> >   r2..
> >   \override Beam.grow-direction = #RIGHT
> >   c'32[ \repeat unfold 6 c'' c'] r2..
> > }
> >
> > Cheers,
> >   Harm
> >
> > _______________________________________________
> > lilypond-user mailing list
>
> > lilypond-user@
>
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> Also, as I earlier mentioned over and over, the bar lines fail. Your example
> does not work unless you ignore bar checks. Why needing to be this way is
> silly to me :)

Well, repeating the same over and over again, although several people
declared not to know exactly what you're, after is not likely
increasing the chance to be understood.

Meanwhile I think you didn't understand that feathered beams, done with
\override Beam.grow-direction = #RIGHT
and
\featherDurations
are _independant_ from each other. See:

\version "2.19.82"

{
  r2..
  \featherDurations #(ly:make-moment 1 2)
  { c''32[ 32 32 32 32 32 32 32] } r2..
}

The old message you quoted previously, explains already that
\featherDurations changes the durations of the notes.
With those changed durations LilyPonds spacing engine may insert
different spacings between those notes.
Ofcourse things like barchecks fail if applied to the _unchanged_ notes.

So it seems to me your problem has _nothing_ to do with feathered
Beams but with featherDurations and it's consequences.

Probably don't use featherDurations at all, but use a custom function
to space the note-columns, only for the visible output, without
changing their durations (midi would not reflect any
accelerando/rallentando then ofcourse).


Cheers,
  Harm