This was so simple, and just works as required, except for one thing.
Using priority 2000 puts the brackets above tempo indications and other
markup; I used Leo's value of 750 which did it exactly right. Leo's
additional "avoid-scripts" and "avoid-slur" overrides were not needed,
in my case at lea
On 28/09/2021 10:18:30, "Lukas-Fabian Moser" wrote:
>Please try and give an example of your LilyPond code, if possible. This
>enables people to help with your concrete situation.
I understand that; but I wanted to see clean-page suggestions, as I felt
the code I already had was way over the top
In this case, I'm not sure what Harm did to ensure horizontal position
of tuplet brackets. In the following solution, I'm doing a bit of a
hack: I ask LilyPond to place the tuplet bracket outside everything
else (that's the value of outside-staff-priority), and then I force
them to be hori
I can’t tell for sure without seeing the code, but I think you may not need
very advanced code to force the brackets horizontal in your case, and that
something like this is what you’re after:
\version "2.22.1"
\fixed c'' {
\override TupletBracket.direction = #UP
\override Tuple
Hi Paul,
Am 28.09.21 um 10:46 schrieb Paul Hodges:
I am at present being asked to put a lot of tuplet brackets on the same
side of the staff (above) as slurs, and this is leading to a lot of
collisions. I could deal with them individually (a lot of work), but is
there something I can do to to f
I am at present being asked to put a lot of tuplet brackets on the same
side of the staff (above) as slurs, and this is leading to a lot of
collisions. I could deal with them individually (a lot of work), but is
there something I can do to to force tuplet brackets away from slurs
(outside them
