Moving things to the staff context fixed both issues. Thanks a lot! --Galen
On Mon, Aug 29, 2022 at 5:10 PM Aaron Hill <[email protected]> wrote: > On 2022-08-29 4:03 pm, Galen Hazelwood wrote: > > I don't see what other event it could be talking about. I don't know if > > this is an actual problem, or my understanding of lilypond isn't good > > enough yet. > > It is an unbreakable beam that is blocking things. Your \override for > Beam.breakable applies only to the current Voice context. When you > create the two new Voices within the << >> construct, neither will see > the overridden property. > > You have a few options. You can move the \override to the inner Voice > that has the problematic beam, or you can make the outer \override apply > to the Staff context instead: > > %%%% > \override Staff.Beam.breakable = ##t > %%%% > > > -- Aaron Hill >
