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 least.
Thanks to you both,
Paul
On 28/09/2021 10:45:39, "Lukas-Fabian Moser" <l...@gmx.de> wrote:
>
>>
>>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 horizontal by
>>letting LilyPond calculate the "usual" slope and afterwards forcing left and
>>right y-position to the average value:
>
>Oh, I'm sorry, I didn't realise that the outside-staff-priority overrides the
>manual setting of positions. Then of course it's much easier:
>
>\version "2.22"
>
>\relative {
> \tupletUp
> \override TupletBracket.bracket-visibility = ##t
> \override TupletBracket.outside-staff-priority = 2000
> \override TupletBracket.positions = #'(0 . 0)
>
> \tuplet 3/2 4 { b''8[(-> c) r] g[(-> fis) r] }
>}
>
>Lukas
>
