lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tuplet bracket


From: Andrew Bernard
Subject: Re: Tuplet bracket
Date: Fri, 14 Apr 2017 18:08:30 +1000

Hi Malte,

Sure, depends which side you want to adjust of course, I am merely indicating a possible technique.

Michiel, speaking as a player myself, your example score seems fairly cramped and lacking what I call 'air', making it a bit hard to read. And there is definitely something wrong with the second line - the break is in the wrong spot. Looking at my Henle Verlag edition, they get more space on the first line by not having so many 32's on the end. Also of possible interest is that they use triplets with curved brackets not rectangular, which seems to make the cramping less severe. There was discussion about how to do these on the list fairly recently.

I am not suggesting you have to copy Henle, but it is very readable/playable edition in my opinion.

Andrew


On 14 April 2017 at 17:55, Malte Meyn <address@hidden> wrote:


Am 14.04.2017 um 06:45 schrieb Andrew Bernard:
> Hi Michiel,
>
> Use shorten-pait to taste.
>
>           %\once \override TupletBracket.positions = #'(3.1 . 3.4)
>           \once \override TupletBracket.shorten-pair = #'(0 . 0.5)

Shouldn’t this be #'(0.2 . 0) or similar but not #'(0 . 0.5) if you want
to shorten it at the left edge?

Alternatively, instead of shortening the tuplet bracket, you could move
the notes by inserting

        \once \override Score.NoteColumn.X-offset = 0.6

(try different values) at this place.

>           \tuplet 3/2 {
>             r32 \clef treble
>             \once \override Slur.positions = #'(-1 . 1)
>             f'^(-[ f')]
>           }
>           %\once \override TupletBracket.positions = #'(3.4 . 3.4)
>           \tuplet 3/2 { r32 r \clef bass \stemNeutral <f,,,,_~ f'^~> }
>
> Andrew

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user


reply via email to

[Prev in Thread] Current Thread [Next in Thread]