yeah i/we'll add the issue to the tracker. if you'll excuse me, I'll create an additional issue for the compromise gould mentions for 32nd beams, of additional spacing between beams, as a property. the last time I touched c++ was like 6 years ago so I have no idea how complicated this would be to implement but i'll throw it out there
> > a 0.25 staff-space slant also > > doesn't work for 32nd beams. See the top left beam end? yeah it > > doesn't touch the middle staff line: > Such details should also be added to an issue. > not sure that would go in the issue, bc three beams not working with 0.25 staff-space slants is a 32nd beam problem, not a lilypond problem lmao. I also just noticed the first image I attached in my last email broke so here it is again: [image: image.png] hopefully it appears this time and you can see the little wedge :)
