Is it possible to use Beam.skip-quanting, but only when no beam touches
the staff symbol?
I have found a setting that seems to give pretty good results with
\override Stem.details.beamed-minimum-free-lengths = #'(2 2.5 2.5)
\override Beam.damping = 10
However, by default that can produce oversize stems outside the staff:
Using \override Beam.skip-quanting = ##t on top of that gives a
different result:
The first beam (with shorter stems) is definitely more to my liking in
the second rendering while the last one should really have been
quantized so not to interfere like that with the staff symbol.
I have not seen anything that makes me think of an
skip-quanting-if-outside-staff. Would I have to use a callback (which?)
where I can set skip-quanting depending on the currently set
Stem.length? Of course I don't want to calculate Stem.length myself
because that would mean I'd do that part of the layout on my own ;-)
Best
Urs
Am 19.03.19 um 15:22 schrieb Urs Liska:
Hi all,
in a project with 600+ short scores (mostly single systems) I have an
issue with the beam/stem formatting, in so far as the stems tend to be
too short when multiple beams are present (at least that's what the
commissioners complained about). When looking at the documentation of
Beam I am (as usual) intimidated by the relation of presumably
powerful properties (especially the #'details) to the utter
uselessness of the docstrings.
Could someone please point me to useful examples or explain to me in
plain and sufficiently verbose language what the following
Beam.details properties do (with about what value ranges)? I have the
impression these could be very useful for my issue, but I can't
imagine starting to find something by trial-and-error (it's too many
properties, and I have hundreds of examples to apply them to):
* |stem-length-demerit-factor|||
* |secondary-beam-demerit|
* |stem-length-limit-penalty|
as well as Stem.details:
* |beamed-lengths|
* |beamed-minimum-free-lengths|
* |beamed-extreme-minimum-free-length|
* |lengths|
I first tried #'beamed-lengths, but that is totally too static to
serve as a global override. So I think the "demerit" properties of
Beam look promising but I don't have any idea how to start with them.
Thanks
Urs
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
