ur has changed recently, so
> it's well worth checking the current beta.
>
> Paul
>
>
> * From: * Gregory Evans
> * To: * Lilypond-User Mailing List
> * Sent: * 24/12/2023 14:03
> * Subject: * Tuplet bracket padding at system ending
>
> Hello,
> I need some he
Subject: Tuplet bracket padding at system ending
Hello,
I need some help constructing a function. Lilypond seems to be relatively
consistently applying less right padding to tuplet brackets at the end of a
system. This causes tuplets in voices below the top of a score to collide with
the barline
Hello,
I need some help constructing a function. Lilypond seems to be relatively
consistently applying less right padding to tuplet brackets at the end of a
system. This causes tuplets in voices below the top of a score to collide
with the barline at the end of every system. I have attached an
Werner LEMBERG writes:
>> \new Staff {
>> \key c \minor
>> < es' g' > < bes' d''~ >2. |
>> \tuplet 3/2 \voices "",2 << { \voiceOne d''4 c'' es'' \oneVoice } \\
>>{ g'4 as'2 } >>
>> < f' as' >4 |
>> }
>
> Looks like a bug, so please file a report.
The problem
> \new Staff {
> \key c \minor
> < es' g' > < bes' d''~ >2. |
> \tuplet 3/2 \voices "",2 << { \voiceOne d''4 c'' es'' \oneVoice } \\
> { g'4 as'2 } >>
> < f' as' >4 |
> }
Looks like a bug, so please file a report.
Werner
William Rehwinkel writes:
>> On 10/16/23 19:09, David Kastrup wrote:
>>> William Rehwinkel writes:
>>>
Dear David,
This seems like an improper/unintended use of \tuplet.
>>> How so?
>>> How is
>>>\tuplet 3/2 \voices "",2 << { \voiceOne d''4 c'' es'' \oneVoice }
>>> \\
>>>
I don't know, but what I meant to say is that this use of \tuplet
outside of \voices or a split into multiple voices seems to me to be
"undefined behavior" ("unspecified"?).
-William
On 10/16/23 19:09, David Kastrup wrote:
William Rehwinkel writes:
Dear David,
This seems like an
William Rehwinkel writes:
> Dear David,
>
> This seems like an improper/unintended use of \tuplet.
How so?
How is
\tuplet 3/2 \voices "",2 << { \voiceOne d''4 c'' es'' \oneVoice } \\
{ g'4 as'2 } >>
improper while
\tuplet 3/2 << { \voiceOne d''4 c'' es''
Dear David,
This seems like an improper/unintended use of \tuplet. I would have used
\scaleDurations instead.
However, if you slightly modify the mwe as shown below, the tuplet
bracket is shown.
Thanks,
-William
\version "2.25.7"
\new Staff {
\key c \minor
< es' g' >
\new Staff {
\key c \minor
< es' g' > < bes' d''~ >2. |
\tuplet 3/2 \voices "",2 << { \voiceOne d''4 c'' es'' \oneVoice } \\
{ g'4 as'2 } >>
< f' as' >4 |
}
Admittedly, this is still better than the warning and crash an earlier
version rather than current master puts out.
But
rim, your override is a good step in the right direction for me.
>
> So now I guess what I'm looking for is a way to query the tuplet bracket
> for its direction while tweaking the tuplet number.
>
> Something like this?
>
> \version "2.25.5"
>
> #(
Le samedi 27 mai 2023 à 17:17 -0400, Gregory Evans a écrit :
> Hi Everyone,
> Yes Andrew, that excerpt is from Mahnkopf: good eye!
>
> Thanks Karim, your override is a good step in the right direction for me.
>
> So now I guess what I'm looking for is a way to query
Hi Everyone,
Yes Andrew, that excerpt is from Mahnkopf: good eye!
Thanks Karim, your override is a good step in the right direction for me.
So now I guess what I'm looking for is a way to query the tuplet bracket
for its direction while tweaking the tuplet number.
regards,
greg
On Sat, May 27
s
> To: Jean Abou Samra
> Cc: Lilypond-User Mailing List
> Subject: Re: Annotated tuplet bracket
> Message-ID:
> Content-Type: text/plain; charset="utf-8"
>
> Hi Jean,
> In the attached image, notice the parenthesized note head above some of the
> tuplet numbers.
Music for oboe by Mahnkopf?
t is sometimes found in scores where
>> tuplets are of uncommon duration (I can provide an incipt if necessary). I
>> have seen the ratio of a tuplet bracket annotated with a parenthesized note
>> head *above* the tuplet number when the bracket is up and *below* when the
&g
> Le 27 mai 2023 à 01:43, Gregory Evans a écrit
> :
>
>
> Hello,
> I am trying to imitate a notation that is sometimes found in scores where
> tuplets are of uncommon duration (I can provide an incipt if necessary). I
> have seen the ratio of a
Hello,
I am trying to imitate a notation that is sometimes found in scores where
tuplets are of uncommon duration (I can provide an incipt if necessary). I
have seen the ratio of a tuplet bracket annotated with a parenthesized note
head *above* the tuplet number when the bracket is up and *below
From: Aaron Hill
You would want to adjust the X-positions, so that the TupletNumber is
centered properly. See the difference:
Thanks for the correction; I used shorten-pair, because in the internals it is
clear that the effect is relative to the situation without it, which was easy
to
>> I find that even using shorten-pair (with a negative first value)
>> fails to do this as I expected. So now I don't know any way to
>> print the bracket with the preferred layout...
>
> This looks like a bug. Please file an issue at
>
> https://gitlab.com/lilypond/lilypond/-/issues
extent, so this is not a true replacement/fix.
>
>
> -- Aaron Hill
>
Hi Aaron,
I had a similar idea, though, not ignoring
`ly:tuplet-bracket::calc-x-positions', but calculating correction
values.
Ofcourse it's more complicated. At least it works for broken
TupletBracket as well:
On 2022-06-03 10:10 am, Paul Hodges wrote:
I find that even using shorten-pair (with a negative first value)
fails to do this as I expected. So now I don't know any way to print
the bracket with the preferred layout...
You would want to adjust the X-positions, so that the TupletNumber is
> I find that even using shorten-pair (with a negative first value)
> fails to do this as I expected. So now I don't know any way to
> print the bracket with the preferred layout...
This looks like a bug. Please file an issue at
https://gitlab.com/lilypond/lilypond/-/issues
Werner
I find that even using shorten-pair (with a negative first value) fails to do
this as I expected. So now I don't know any way to print the bracket with the
preferred layout...
Paul
From: Paul Hodges
To:
Sent: 02/06/2022 0:05
Subject: Left-hand end of tuplet bracket
Dorico does this 'correctly', that is, according to those texts. See
picture.
Andrew
Paul Hodges wrote on 2/06/2022 9:05 AM
However, LilyPond doesn't always do this - instead, if the first note
has an up-stem, the bracket is aligned with the stem instead.
Both Ross (p161) and Gould (p195) are completely clear when they say that the
left hand end of a tuplet bracket aligns with the left-hand side of the first
note.
However, LilyPond doesn't always do this - instead, if the first note has an
up-stem, the bracket is aligned with the stem instead
Kieren MacMillan writes:
> Hi David,
>
>> I admit that I went for another dive into the IR for TupletBracket when
>> outside-staff-priority failed to do the trick. Turns out that
>> outside-staff-interface should be #f by default anyway?
>
> Please elaborate:
> You believe the default is
Le 26/11/2021 à 16:19, Lukas-Fabian Moser a écrit :
I never really understood the outside-staff behaviour, to be honest.
If it seems complicated, that's because it is. There
are two mechanisms for general collision avoidance,
incarnated in the side-position-interface and the
Hi David,
> I admit that I went for another dive into the IR for TupletBracket when
> outside-staff-priority failed to do the trick. Turns out that
> outside-staff-interface should be #f by default anyway?
Please elaborate:
You believe the default is incorrect (in which case I will work up a
Kieren MacMillan writes:
> Hi all,
>
>>> I never really understood the outside-staff behaviour, to be
>>> honest. It's well possible that there's an elegant solution that just
>>> tells LilyPond to go ahead and put the tuplet bracket into the staff.
>>
>> Well, you got the wrong property here. outside-staff-priority
>> tells how to stack outside-staff objects with one another. What
>> you need here is
>>
>> \override CueVoice.TupletBracket.staff-padding = ##f
Aah, I only tried `padding` to no avail. Thanks a lot!
> So, Werner, this
Hi all,
>> I never really understood the outside-staff behaviour, to be
>> honest. It's well possible that there's an elegant solution that just
>> tells LilyPond to go ahead and put the tuplet bracket into the staff.
> Uh, that's what setting outside-staff-pri
Well, you got the wrong property here. outside-staff-priority tells how
to stack outside-staff objects with one another. What you need here is
\override CueVoice.TupletBracket.staff-padding = ##f
to stop TupletBracket from being shy of the staff itself, never mind
other outside-staff
Lukas-Fabian Moser writes:
>>> I never really understood the outside-staff behaviour, to be
>>> honest. It's well possible that there's an elegant solution that just
>>> tells LilyPond to go ahead and put the tuplet bracket into the staff.
>> Uh, that's what set
t;> few minutes of not finding the right incantation…
>
> I never really understood the outside-staff behaviour, to be
> honest. It's well possible that there's an elegant solution that just
> tells LilyPond to go ahead and put the tuplet bracket into the staff.
Uh, that's what setting
I never really understood the outside-staff behaviour, to be
honest. It's well possible that there's an elegant solution that just
tells LilyPond to go ahead and put the tuplet bracket into the staff.
Uh, that's what setting outside-staff-priority to #f does.
Did I mention I never really
>> For a general solution, one could probably write a callback for the
>> positions property.
>
> I was hoping to use #'outside-staff-priority to try to allow the
> tuplet to float into the staff automatically, [...]
Me too.
Werner
>>\override CueVoice.TupletBracket.direction = #DOWN
>>\override CueVoice.TupletBracket.edge-height = #'(-0.7 . -0.7)
>>\override CueVoice.TupletBracket.extra-offset = #'(0 . 4.75)
>>\override CueVoice.TupletNumber.extra-offset = #'(0 . 4.75)
>
> Hold the heavy machinery :-). You
understood the outside-staff behaviour, to be honest.
It's well possible that there's an elegant solution that just tells
LilyPond to go ahead and put the tuplet bracket into the staff.
A poor man's automated solution might be:
\version "2.23.4"
x = { r2 \tuplet 3/2 { g4 a b } r2 \tuplet
Hi Lukas,
> Hold the heavy machinery :-)
LOL
> You can just set the positions directly:
Nice.
> For a general solution, one could probably write a callback for the positions
> property.
I was hoping to use #'outside-staff-priority to try to allow the tuplet to
float into the staff
Hi Kieren & Werner,
There's surely a more elegant way… but if you're stuck, you can always hack it:
x = { r2 \tuplet 3/2 { g4 a b } }
\addQuote "qx" \x
{
r2 \cueDuring #"qx" #DOWN {
\override CueVoice.TupletBracket.direction = #DOWN
\override CueVoice.TupletBracket.edge-height =
>> What must I do to make the tuplet bracket be positioned within the
>> staff, that is, below the rest?
>
> There's surely a more elegant way… but if you're stuck, you can
> always hack it: [...]
Thanks a lot! Of course I would like to have a solution that avoids
`ex
Hi Werner,
> What must I do to make the tuplet bracket be positioned
> within the staff, that is, below the rest?
There's surely a more elegant way… but if you're stuck, you can always hack it:
x = { r2 \tuplet 3/2 { g4 a b } }
\addQuote "qx" \x
{
r2 \cueDuring #"qx
Folks,
plesae consider the following example.
x = { r2 \tuplet 3/2 { g4 a b } }
\addQuote "qx" \x
{
r2 \cueDuring #"qx" #DOWN {
\override CueVoice.TupletBracket.direction = #UP
r2 }
}
What must I do to make the tuplet b
Thanks - that sorts out a lot (and exposes another issue I'll write
about separately!).
In my many decades of programming I always had reservations about
"syntactic sugar" - different ways of expressing the same thing. When
the alternatives do not have the same behaviour at all times, they
The reason for it breaking is that in the code you posted there are vertical
lines ” || " instead of backslashes ” \\ ” separating the voices.
The bracket issue is that the override needs to go in a context where the
tuples sees it. By default it goes into the Voice context here, and the << …
In the following code, the first expression does more or less what I
want; but I also want tuplet brackets. However, specifying that they
are wanted, as in the second expression, seems to break stuff, and I
have no idea why.
In fact, it is simply the presence of the override which causes the
Thanks guys, it looks like \scaleDurations is going to do what I want.
--
Knute Snortum
On Sun, Jun 27, 2021 at 8:57 AM Timothy Lanfear wrote:
> On 27/06/2021 16:17, Knute Snortum wrote:
> >
> > My problem with it is it seems unnecessarily verbose. Also, this bass
> > line continues for
On 27/06/2021 16:17, Knute Snortum wrote:
My problem with it is it seems unnecessarily verbose. Also, this bass
line continues for dozens of measures, so I'd like to wrap it all in a
\tuplet construct. Do I have to break up the tuplet in dozens of
places just to avoid errors? Is there a better
me 4/4
\clef bass
\omit TupletNumber
\tuplet 3/2 4 {
ef,8 ef'' g,
<<
{ df4 s8 ff4 s8 ef4 s8 }
\\
{ df8 ff' af, ff df' af ef df' g, }
>> |
}
}
%%%
This will produce three "omitting tuplet bracket with neither left nor
right bound&
4 {
ef,8 ef'' g,
<<
{ df4 s8 ff4 s8 ef4 s8 }
\\
{ df8 ff' af, ff df' af ef df' g, }
>> |
}
}
%%%
This will produce three "omitting tuplet bracket with neither left nor
right bound" warnings. So, first question: should it? Is that code
imprope
Andrew,
So it does. I wonder why. I don't really mind if invisible objects are grouped
or not :)
Thanks.
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Wednesday, November 13, 2019, 11:05:28 AM, Andrew Bernard wrote:
> Hi Peter,
> If you leave out the
Hi Peter,
If you leave out the 8 in the \tuplet 3/2 specification there is no
issue. Would that be acceptable to you?
Andrew
%
\language "english"
{
\omit TupletBracket
\omit TupletNumber
\clef "treble"
\tuplet 3/2 { \repeat percent 4 {c'16 16 16 } }
}
{
\omit
Tuesday, November 12, 2019, 8:37:13 PM, Thomas Morley wrote:
> Am Di., 12. Nov. 2019 um 20:09 Uhr schrieb
> Peter Toye :
>> The following MWEs both give errors saying that a tuplet bracket has neither
>> a beginning nor an end. IN the first one this is presumably because
Am Di., 12. Nov. 2019 um 20:09 Uhr schrieb Peter Toye :
>
> The following MWEs both give errors saying that a tuplet bracket has neither
> a beginning nor an end. IN the first one this is presumably because of the
> percent repeat sign, and in the second because of the
The following MWEs both give errors saying that a tuplet bracket has neither a
beginning nor an end. IN the first one this is presumably because of the
percent repeat sign, and in the second because of the silent notes.
But the brackets are explicitly omitted so IMO the warning message should
uplet 4/3 {
s4 g'4
}
}
\new Voice {
\voiceFour
\tuplet 4/3 {
r4 g'8 d'8
}
}
>>
On Sun, Nov 18, 2018 at 8:33 PM Ryan Michael
wrote:
> hello lilypond community,
> I am trying to have sustained voices across a 4/3 eighth note tuplet
> bracket. My desire is to simply have one tupl
hello lilypond community,
I am trying to have sustained voices across a 4/3 eighth note tuplet
bracket. My desire is to simply have one tuplet bracket which encloses each
of the four voices as a single entity. Lilypond seems to discretize /
assign tuplet brackets for each voice given the following
: Aaron Hill
> To: lilypond-user@gnu.org
> Subject: Re: warning: omitting tuplet bracket with neither left nor
> right bound
> Message-ID: <1e8a607c124931c608654bb162c79...@hillvisions.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> On 2018-06-09 1
On 2018-06-09 13:32, Karim Haddad wrote:
Dear List,
I have warnings when used along with a skip secondary voice used for
dynamics and including tuplets.
here is a minimal example :
%%
\version "2.19.80"
one = { r4 c'2.~ | c'1 | c'2 r2 | }
dyn = { s4 s2. \< | s4 \tuplet 3/2 {s4
Dear List,
I have warnings when used along with a skip secondary voice used for dynamics
and including tuplets.
here is a minimal example :
%%
\version "2.19.80"
one = { r4 c'2.~ | c'1 | c'2 r2 | }
dyn = { s4 s2. \< | s4 \tuplet 3/2 {s4 \! \> s8} s2 | s2 s2 \! |}
\score {
I also agree with the suggestions, you should place two 8th rests instead.
But in case you wished to know the solution for your initial layout problem,
you could just put
"\set tupletFullLength = ##t" before the lower tuplet!
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
On 04.05.2018 16:18, Aaron Hill wrote:
On 2018-05-04 13:47, Chris Yate wrote:
The following might be the tidiest solution (i.e. just remove the number
and brace). Other opinions welcome!
If you wanted the keep the lower tuplet bracket, you could write two
explicit eighth rests to line up
On 2018-05-04 13:47, Chris Yate wrote:
The following might be the tidiest solution (i.e. just remove the
number
and brace). Other opinions welcome!
If you wanted the keep the lower tuplet bracket, you could write two
explicit eighth rests to line up with the eighth notes above instead
et 3/2 { c8-. r4 }
R1 }>> } }
[image: image.png]
On Fri, 4 May 2018 at 14:33 Chris Yate <chrisy...@gmail.com> wrote:
> Hi guys,
>
> This passage is a little tricky to write tidily on one staff, and I might
> change the way this is done. But the placing of the low
Hi guys,
This passage is a little tricky to write tidily on one staff, and I might
change the way this is done. But the placing of the lower tuplet bracket
(covereing the quaver and crotchet rest) doesn't seem to help...
\transpose f g { \relative c'{
<<
{ r2 r4 \tuplet 3/2 { c8-.
his makes sense.
In any case, it is connected to the default direction of the tuplets.
The padding is only effective if the tuplet bracket is placed on the
opposite side (not on the side of the beam as usual).
\version "2.19.80"
{
\override TupletBracket.outside-staff-priorit
Thank you both! I appreciate the quick turnaround. If the difference in
opinion persists I'll return with a minimal example, but in light of what
you've told me I think we can just proceed as we are.
On Wed, May 2, 2018 at 9:40 AM, Simon Albrecht
wrote:
> On 02.05.2018
On 02.05.2018 18:24, Reilly Farrell wrote:
Hi All,
I'm editing a short score with tuplets and I could use a spacing
solution that would keep all tuplet brackets at a fixed minimum
distance above the staff. (Feedback I've received so far is that the
tuplet indications look messy when printed
Reilly Farrell writes:
> Hi All,
>
> I'm editing a short score with tuplets and I could use a spacing solution
> that would keep all tuplet brackets at a fixed minimum distance above the
> staff. (Feedback I've received so far is that the tuplet indications look
>
Hi All,
I'm editing a short score with tuplets and I could use a spacing solution
that would keep all tuplet brackets at a fixed minimum distance above the
staff. (Feedback I've received so far is that the tuplet indications look
messy when printed inside the staff rather than above it.) My
is that, what you
would naturally expect when telling the tuplet bracket to avoid the slur is
that it should actually, ah, avoid the slur, yet it manifestly does not.
So is this a bug or a defect or just bad behaviour in lilypond? What is
really going here? I confess I have not done thorough searches
Sry, this was wrong, you wanted it the other way round.
\version "2.19.48"
{
\override TupletBracket.avoid-slur = #'outside
\shape #'((0 . -1.5) (0 . -1.5) (0 . -1.5) (0 . -1.5)) Slur
\tuplet 5/4 { c''( bes' fis' d' ges') }
}
Greetings,
Manuela
2017-04-25 8:17 GMT+02:00 Manuela Gößnitzer
Hi Andrew,
the code you posted doesn't produce a bracket at all entered to lilybin.com
Try this
\version "2.19.48"
{
\override TupletBracket.avoid-slur = #'outside
\shape #'((0 . 2) (0 . 2) (0 . 2) (0 . 2)) Slur
\tuplet 5/4 { c''( bes' fis' d' ges') }
}
Greeting,
Manuela
2017-04-25 7:25
H Manuela,
I did, naturally. The slur intersects the bracket, and commenting out the
override you show produces the same result as having it. So I don't think
this is the answer.
Andrew
On 25 April 2017 at 15:06, Manuela wrote:
> Try this code:
>
> \version
Try this code:
\version "2.19.48"
{
\override TupletBracket.avoid-slur = #'outside
\tuplet 5/4 { c''( bes' fis' d' ges') }
}
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Slur-inside-tuplet-bracket-tp202613p202618.html
Sent from the User mailing li
Why does this mess up?
\version "2.19.59"
{
\override TupletNumber.avoid-slur = #'outside
\tuplet 5/4 { c''( bes' fis' d' ges') }
}
How do you get a slur to go inside a tuplet bracket?
Andrew
___
lilypond-user mailing list
lilypond-us
nard:
>> > 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.
) 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.
>
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 {
>
Hi Michiel,
Use shorten-pait to taste.
%\once \override TupletBracket.positions = #'(3.1 . 3.4)
\once \override TupletBracket.shorten-pair = #'(0 . 0.5)
\tuplet 3/2 {
r32 \clef treble
\once \override Slur.positions = #'(-1 . 1)
Hi there,
I've got some code here: http://lilybin.com/i5sop1/1
I'm wondering if anyone knows of a way to get the second and third tuplet
brackets in LH to be a bit further apart? They're very close together, I'd
like to inject a tiny little space, but I haven't been able to figure out
how.
I
amazing how this makes an argument for kneed beams, so shunned by
> most modern typesetters!
I don't think I understand why this makes an argument for kneed beams, can't
one can have the same slope for both a kneed beam and a non-kneed beam?
Cheers!
Gilberto
--
View this message in co
On 09.07.2016 17:14, Gilberto Agostinho wrote:
Andrew Bernard wrote
What nonsense Gould writes here. I perceive duration in notation on any
angle. The book is not always right in its justifications.
I think what Gould means is that duration is notated in the x-axis of a
staff, and so keeping
s, right?
Anyway, I think I will bring this issue of tuplet angles to the bug squad as
I think it's pretty clear we should have a max slope pre-defined.
Cheers!
Gilberto
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/tuplet-bracket-slope-tp192294p192444.html
Sent from
Hi Gilberto,
On 7 July 2016 at 3:07:25 AM, Gilberto Agostinho wrote:
> Beam angles should not deviate far from the horizontal because the eye
> perceives duration on the horizontal plane.
What nonsense Gould writes here. I perceive duration in notation on any
angle. The book is not always
ute
anyway. Also, it would be great to have some way of forcing the brackets to
be always horizontal, similar to what can be achieved with beams by using
\override Beam.damping = #+inf.0
Cheers,
Gilberto
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/tuplet-bracket-slo
Hi all,
I am wondering if the way LilyPond's tuplet bracket algorithm works is
really ideal. It seems to me that the algorithm does not specify a maximum
slope for the brackets, and can produce things like this:
\version "2.19.37"
{
\tuplet 5/4 { <f'' c'''>16 d'4 }
st say \tupletAngles 1 0 or similar and that's
>>> all you need. Put it is a file tuplet-angles.ily and include it. Using
>>> \tupletAngles 0 0 is very handy for straigthening up tuplets when you
>>> don't want lilypond to angle them.
>>>
>>> Here it is. [
gt; \tupletAngles 0 0 is very handy for straigthening up tuplets when you
>> don't want lilypond to angle them.
>>
>> Here it is. [Surprised this is not more well known.]
>>
>> Andrew
>
> Looking in the archives:
> http://lilypond.1069038.n5.nabble.com/a
s not more well known.]
>>
>> Andrew
>
> Looking in the archives:
> http://lilypond.1069038.n5.nabble.com/angle-of-a-tuplet-bracket-td55019.html#a55023
> :)
>
> Reading it up gives some additional informations...
>
> Cheers,
> Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
is. [Surprised this is not more well known.]
>
> Andrew
Looking in the archives:
http://lilypond.1069038.n5.nabble.com/angle-of-a-tuplet-bracket-td55019.html#a55023
:)
Reading it up gives some additional informations...
Cheers,
Harm
___
lilypo
Hi Matteo,
I have a tuplet angle function that somebody (I cannot recall who)
sent me some time ago. I use it heavily and extensively and I can say
it has been tested by me to the limit - it works well.
Using this code you just say \tupletAngles 1 0 or similar and that's
all you need. Put it is
On Sat, Jun 25, 2016 at 5:15 PM, Simon Albrecht wrote:
> On 25.06.2016 20:22, David Nalesnik wrote:
>>
>> On Sat, Jun 25, 2016 at 1:19 PM, David Nalesnik
>> wrote:
>>>
>>> Hi,
>>>
>>> On Sat, Jun 25, 2016 at 11:50 AM, matpen3@gmail
On Sat, Jun 25, 2016 at 1:19 PM, David Nalesnik
wrote:
> Hi,
>
> On Sat, Jun 25, 2016 at 11:50 AM, matpen3@gmail wrote:
>> Hi Stephen,
>>
>> I’m using now
>>
>> \once \override TupletBracket.rotation = #'(0.1 -120 0.1)
But it is strange that the
Hi,
On Sat, Jun 25, 2016 at 11:50 AM, matpen3@gmail wrote:
> Hi Stephen,
>
> I’m using now
>
> \once \override TupletBracket.rotation = #'(0.1 -120 0.1)
> \offset Y-offset 1.5 TupletNumber
>
If you adjust the positions property of the TupletBracket, the number
will follow
Hi Stephen,
I’m using now
\once \override TupletBracket.rotation = #'(0.1 -120 0.1)
\offset Y-offset 1.5 TupletNumber
Thanks, also to David
> Il giorno 25 giu 2016, alle ore 18:20, Stephen MacNeil
> ha scritto:
>
> can you share?
>
> Stephen
can you share?
Stephen
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
good to know
Thanks
Stephen
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi,
On Sat, Jun 25, 2016 at 10:49 AM, Stephen MacNeil
wrote:
>
> \override TupletNumber.Y-offset = #(lambda (grob) (+ 1.5
> (ly:tuplet-number::calc-y-offset grob)))
>
\offset Y-offset 1.5 TupletNumber
is equivalent
-David
1 - 100 of 216 matches
Mail list logo