Re: Beam breaking

[Andrew Bernard]

Ah, is it to do with the tuplet not being breakable?

On Sun, 2 Aug 2020 at 14:00, Andrew Bernard <andrew.bernard@gmail.com> wrote:
>
> Sorry, but if you remove the explicit beam the same issue remains. I
> am stumped. I am unable to understand your comment about 'at note
> heads. Surely the break can only occur between notes?
>
> On Sun, 2 Aug 2020 at 13:37, Urs Liska <lists@openlilylib.org> wrote:
> >
> > Ah no, much simpler: If you ask LilyPond to print an explicit beam it
> > will print an explicit beam ;-)
> >
> > Am Sonntag, den 02.08.2020, 05:35 +0200 schrieb Urs Liska:
> > > Am Sonntag, den 02.08.2020, 13:32 +1000 schrieb Andrew Bernard:
> > > > \version "2.21.4"
> > > >
> > > >
> > > >
> > > > {
> > > >
> > > >   \time 7/8
> > > >
> > > >   \set Timing.measureLength = #(ly:make-moment 1/4)
> > > >
> > > >   \override Beam.breakable = ##t
> > > >
> > > >   \tuplet 7/8 {
> > > >
> > > >     b'16[ b' b' b'
> > > >
> > > >     \break
> > > >
> > > >     c'' c'' c'']
> > > >
> > > >   } |
> > > >
> > > > }
> > >
> > > I'm not sure, but I'd suppose that even "breakable" will only let you
> > > break beams *at* note heads and not as some point between two notes.
> > >
> > > Urs
> > >
> > >
> >