Re: \beamExeceptions problem

[Richard Shann]

On Mon, 2021-01-04 at 00:45 +0100, David Kastrup wrote:
> Richard Shann <richard@rshann.plus.com> writes:
> 
> > My understanding of the \beamExceptions function in 2.20 was that
> > you
> > should be able to pass it a complete bar beamed as you would wish
> > and
> > expect other bars with the same beat structure to be beamed to
> > match.
> 
> But you did not pass \beamExceptions a bar beamed as you would wish.
> You passed it a bar with beaming depending on a combination of
> automatic
> beaming and beaming exceptions.

ah, I see, thanks.

> 
> That doesn't work since at the current point of time, beaming
> exceptions
> _only_ affect beam ends.
> 
> > In this example barOne and barTwo have the same rhythm but only
> > barOne
> > is beamed as desired.
> > What have I got wrong?
> > 
> > Richard Shann
> > 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
> > \version "2.20"
> > 
> > barOne = {g'16 b' b'[( a'32 g']) d'16[ c''16] c''16[( b'32 a'])}
> 
> Beaming for 1/16 notes ends here after c''16] and nowhere
> else.  Beaming
> for 32nd notes ends after g'32]) and a'32]) and nowhere else.  Those
> are
> the beaming exceptions being generated by
> 
> \beamExceptions \barOne
> 
> as you can verify with
> 
> \void \displayScheme \beamExceptions \barOne
> 

I think I'll need to write a script to place manual beams throughout a
movement to match a sample bar, as thinking about it, it would be too
much to expect LilyPond to do this sort of thing.

Richard Shann