Hi Paul, I'm sure you know of the override pair:
\override Stem.stemlet-length = #0.5 \override Stem.details.beamed-lengths = #'(4.75) ( music with beamed rests here ) \revert Stem.stemlet-length \revert Stem.details.beamed-lengths I'm not aware of any way to set this globally. Well, the first one can be set once. You'll still have to use "[" and "]" to force beaming, and you should, for the sake of Best Practices™, set the stemlet length manually for each one. But this is the way I've had to do it; and while it's tedious to do that for every affected beam, it ensures that they look good and work properly. Cheers, A On Tue, Sep 28, 2021 at 11:08 AM Paul Hodges <p...@cassland.org> wrote: > The composer I'm working on is very fond of having beams over rests - > and indeed it helps a lot in reading his more complex rhythms. However, > LilyPond is treating rests differently from notes, in that beam > positions are adjusted to suit the notes, whereas rests are then > adjusted to suit the beams. So I get this kind of layout: > However, the publisher wants rests to remain in their standard position, > like this: > > with occasional compromises to this extent: > > > I can obviously force this in individual cases, but again, is there a > global adjustment I can make to get nearer to what I'm being asked for? > > Thanks, > Paul
