On Sat, Jun 29, 2024 at 6:42 PM Flaming Hakama by Elaine < ela...@flaminghakama.com> wrote:
> >> Hi list, >> >> I'm hoping someone can give me insight into how to lengthen stems in >> beamed groups globally. >> >> LilyPond usually makes good assumptions and has great defaults, but in >> this situation it fails to create good stem lengths in beamed groups. I've >> attached some sample code that illustrates the problem. With the following >> line commented out, you can see that the stems are too short >> (stem-too-short.png): >> >> \override Stem.details.beamed-lengths = #'(3.5 4.1) >> >> With the above line uncommented, the stem lengths are better, except the >> second measure, right hand, third beat (stem-lengths-better.png). >> >> My questions are these: How do I tell LilyPond what length the shortest >> stem in a beamed group should be? (I tried playing >> with Stem.details.beamed-minimum-free-lengths, but its behavior seemed >> chaotic.) And is there a better way to control stem lengths in beamed >> groups? >> >> -- >> Knute Snortum >> > > > This may be too broad of a brush, since it also affects non-beamed stems. > > \override Stem.length-fraction = #(magstep 1.2) > > But this is what I use, and I don't mind the extra-long non-breamed stems. > Yes, that has its advantages, thanks! It's weird that even \override Stem.length-fraction = #(magstep 1.0) makes the non-beamed stems too long and that 1.1 seems the same as 1.2. -- Knute Snortum
