of a \tuplet that can be seen with this code:
>
> {\clef alto \tuplet 3/2 {a8-3( g-2 f-1)}}
>
> to be compared with the same without the slur
>
> {\clef alto \tuplet 3/2 {a8-3 g-2 f-1}}
>
> for which there is no collision between fingering and tuplet number.
>
>
Hello,
I've got into a strange behavior of a \tuplet that can be seen with this
code:
{\clef alto \tuplet 3/2 {a8-3( g-2 f-1)}}
to be compared with the same without the slur
{\clef alto \tuplet 3/2 {a8-3 g-2 f-1}}
for which there is no collision between fingering and tuplet number.
Sorry. I am guilty of using imprecise language. I use custom notehead
stencils to achieve the look of the notes we want. Not a replacement
custom font such as yours. [It's very successful but I confess I have
never been able to make good breve noteheads.]
This sort of thing:
% for unfilled no
.
>
> How can I get access to the font used in tuplet numbers for the notes
> when you use them, as per the non-default tuplet number examples?
Sorry, not a direct answer to your question, but how are you using a custom
font for the notes? I’ve not had the problem with my fonts you are
de
use them, as per the non-default tuplet number examples?
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
> padding (for TupletNumber) only comes into effect for Y-offset when
> considering kneed beams:
>
>
> \version "2.19.82"
> {
> \tuplet 5/2 { b8[ b'' b b'' b] }
> \once \override TupletNumber.padding = #1
> \tuplet 5/2 { b8[ b'' b b'' b] }
> }
>
>
> Otherwise, the computation is
On 2019-04-01 1:16 pm, Werner LEMBERG wrote:
Folks,
if I use `\magnifyStaff', the tuplet number is too far away from the
beam. How can I move it nearer to the beam? Looking into
`tuplet-number.cc' I see a `padding' property with a default value of
0.5 (and which is appare
>> if I use `\magnifyStaff', the tuplet number is too far away from
>> the beam. How can I move it nearer to the beam? Looking into
>> `tuplet-number.cc' I see a `padding' property with a default value
>> of 0.5 (and which is apparently completely undocu
On 4/1/2019 4:16 PM, Werner LEMBERG wrote:
Folks,
if I use `\magnifyStaff', the tuplet number is too far away from the
beam. How can I move it nearer to the beam? Looking into
`tuplet-number.cc' I see a `padding' property with a default value of
0.5 (and which is appare
Folks,
if I use `\magnifyStaff', the tuplet number is too far away from the
beam. How can I move it nearer to the beam? Looking into
`tuplet-number.cc' I see a `padding' property with a default value of
0.5 (and which is apparently completely undocumented). However, doing
Dear community,
I have a problem with the spacing between the piano staff for the left hand
and the violin staff.
I would like to increase the distance.
Off course, I could do it generally, but I would like to do it for just a
few measures.
I tried it by changing the minimun-Y-extent for tupletnumb
On 1/27/2018 10:29 AM, Thomas Morley wrote:
2018-01-27 15:26 GMT+01:00 Ben :
On 1/26/2018 11:32 PM, Tiago Pereira wrote:
Hi, everybody!
In the example below, the tuplet number is moved upwards when the
articulation is added. How to prevent this from happening?
\relative c' {
\s
2018-01-27 15:26 GMT+01:00 Ben :
> On 1/26/2018 11:32 PM, Tiago Pereira wrote:
>
> Hi, everybody!
>
> In the example below, the tuplet number is moved upwards when the
> articulation is added. How to prevent this from happening?
>
> \relative c' {
> \stemUp
>
On 1/26/2018 11:32 PM, Tiago Pereira wrote:
Hi, everybody!
In the example below, the tuplet number is moved upwards when the
articulation is added. How to prevent this from happening?
\relative c' {
\stemUp
\tuplet 3/2 4 {
c8 d e f g a b c d e f g
c,,8^> d e f^> g
On 1/26/2018 11:32 PM, Tiago Pereira wrote:
Hi, everybody!
In the example below, the tuplet number is moved upwards when the
articulation is added. How to prevent this from happening?
\relative c' {
\stemUp
\tuplet 3/2 4 {
c8 d e f g a b c d e f g
c,,8^> d e f^> g
Hi, everybody!
In the example below, the tuplet number is moved upwards when the articulation
is added. How to prevent this from happening?
\relative c' {
\stemUp
\tuplet 3/2 4 {
c8 d e f g a b c d e f g
c,,8^> d e f^> g a b^> c d e^> f g
Hi David,
Thank you for clarifying. This is all good to know.
Interestingly I uniformly set horizontal tuplet brackets so the vertical
offset for slanting brackets never occurred to me in my small utility
function.
Andrew
On 18 April 2017 at 22:33, David Nalesnik wrote:
>
> No, I didn't say
ust, but you can lengthen the broken bracket:
>>
>
> This is a function I use all the time, and it seems to work for me.
>
> tupletNumberShift =
> #(define-music-function (offset)
>(number?)
>" Move tuplet number across.
>Offset is from left of tu
it seems to work for me.
tupletNumberShift =
#(define-music-function (offset)
(number?)
" Move tuplet number across.
Offset is from left of tuplet bracket.
"
#{
\once \override TupletNumber.whiteout = ##t
\once \override Score.TupletNumber.layer = #3
\once \
nd right
> side of a broken tuplet (something similar to broken-left and broken right in
> a TextSpanner).In the example provided, the innermost tuplet number of the
> first bar needs to be shifted in order to be displayed correctly.
>
> Here are two possible solutions to the placemen
>
>
> Sorry if I was not very clear describing what I’m looking for.
> I wonder if there is a way of modifying the properties of the left and
> right side of a broken tuplet (something similar to broken-left and broken
> right in a TextSpanner).In the example provided, the innermost
left and right
side of a broken tuplet (something similar to broken-left and broken right in a
TextSpanner).In the example provided, the innermost tuplet number of the first
bar needs to be shifted in order to be displayed correctly.
Here are two possible solutions to the placement problem
poser has written. I see no issue with the tuplet
over a barline (with us since Ives at least). The placement of the tuplet
number and the left side form of the bracket however are not ideal.
> Can you post a sketch of what is actually required? I half see what you are
> getting at, b
Hello Juan,
I have various ways of doing this, but with all respect, this is really
very illegible engraving from the point of view of a player. Is this truly
what you want? Can you post a sketch of what is actually required? I half
see what you are getting at, but why do you need to split across
2017-04-11 21:26 GMT+02:00 Juan Cristóbal Cerrillo :
> Hello,
>
> Is there a way of changing the position of tuplet numbers in broken tuplets?
> In the following example I would like to be able to displace the lower three
> in the first bar to the right.
> Any suggestions?
It's not clear to me wh
Hello,
Is there a way of changing the position of tuplet numbers in broken tuplets?
In the following example I would like to be able to displace the lower three in
the first bar to the right.
Any suggestions?
all best,
jc
\version "2.19.57"
\layout {
ragged-right = ##t
\context {\Voice
n for this is that it's the tuplet *bracket* that is responsible
> for the direction, so you can't override the tuplet *number*'s direction
> independently.
>
> Instead of the explicit override you could probably also use the shorthand
> \tupletUp (optionally prepended with \o
That works, thanks!
---
Knute Snortum
(via Gmail)
On Sat, Feb 25, 2017 at 1:45 PM, Jeffery Shivers
wrote:
> On Sat, Feb 25, 2017 at 4:18 PM, Knute Snortum wrote:
> > I am trying to get both tuplet numbers above the notes in the following
> > code. I've tried \override TupletNumber.direction
On Sat, Feb 25, 2017 at 4:18 PM, Knute Snortum wrote:
> I am trying to get both tuplet numbers above the notes in the following
> code. I've tried \override TupletNumber.direction = #UP, but evidently this
> does not work. What's the correct way to do this?
>
> \version "2.19.55"
> \language "en
I am trying to get both tuplet numbers above the notes in the following
code. I've tried \override TupletNumber.direction = #UP, but evidently
this does not work. What's the correct way to do this?
\version "2.19.55"
\language "english"
\relative {
\omit TupletBracket
\override TupletNumber
\version "2.19.47"
{
\omit TupletBracket
\voiceOne
\partial 4
\tuplet 3/2 { bes'4 a'8 }
d''4
}
%%
the tuplet number is positioned as if there were still a bracket.
Is it possible to ‘drop’ it
016-09-28 16:39 GMT+02:00 Simon Albrecht :
> Hello,
>
> in this snippet
>
> %%
> \version "2.19.47"
> {
> \omit TupletBracket
> \voiceOne
> \partial 4
> \tuplet 3/2 { bes'4 a'8 }
> d''4
> }
> %%
On 28.09.2016 18:05, Karlin High wrote:
On 9/28/2016 9:49 AM, Simon Albrecht wrote:
Also, I’m sure I’ve already seen a solution with ‘slur-style’ tuplets,
or tuplet indication and slur merged. But I’m terribly bad at finding
such stuff from the archives or LSR. Can anyone please give a hint?
TI
n
There was a discussion somewhere around here:
http://lists.gnu.org/archive/html/lilypond-user/2016-04/msg00321.html
April 15, 2016 or thereabouts. Subject is "Tuplet number direction." I'm
not sure where it concludes.
--
Karlin High
Missouri, USA
___
> TIA, Simon
>
> On 28.09.2016 16:39, Simon Albrecht wrote:
> > Hello,
> >
> > in this snippet
> >
> > %%
> > \version "2.19.47"
> > {
> > \omit TupletBracket
> > \voiceOne
> > \partial 4
> > \tuple
Hi, if I understand your question, this moves the tuplet number:
\version "2.19.47"
{
\omit TupletBracket
\voiceOne
\partial 4
\override TupletNumber #'Y-offset = #1.4
\tuplet 3/2 { bes'4 a'8 }
d''4
}
Increase the number to position it higher, d
%%
\version "2.19.47"
{
\omit TupletBracket
\voiceOne
\partial 4
\tuplet 3/2 { bes'4 a'8 }
d''4
}
%%
the tuplet number is positioned as if there were still a bracket.
Is it possible to ‘drop’ it into the gap, outside staff or maybe even
Hello,
in this snippet
%%
\version "2.19.47"
{
\omit TupletBracket
\voiceOne
\partial 4
\tuplet 3/2 { bes'4 a'8 }
d''4
}
%%
the tuplet number is positioned as if there were still a bracket.
Is it possible to ‘drop’ it into the gap, out
David Wright writes:
> On Fri 15 Apr 2016 at 10:23:55 (+0200), David Kastrup wrote:
>>
>> Which would usually involve triplet brackets rather than hacking this
>> into partial note values at measure boundaries. Which is how it was
>> done in the score I have been singing this from.
>
> Surely o
On Fri 15 Apr 2016 at 10:23:55 (+0200), David Kastrup wrote:
> "Phil Holmes" writes:
> > - Original Message -
> > From: "David Kastrup"
> > Sent: Friday, April 15, 2016 8:04 AM
> >> Simon Albrecht writes:
> >>> On 15.04.2016 00:51, Thomas Morley wrote:
> (1) The TupletNumbers are a
2016-04-16 16:30 GMT+02:00 Trevor Daniels :
>
> Thomas Morley wrote Friday, April 15, 2016 11:25 PM
>
>> Agreed. I never considered to disallow tuplets over line-break.
>> Gould has nothing to say about it? (I still don't own the book...)
>
> She has a complete chapter devoted to tuplets. She talk
Thomas Morley wrote Friday, April 15, 2016 11:25 PM
> Agreed. I never considered to disallow tuplets over line-break.
> Gould has nothing to say about it? (I still don't own the book...)
She has a complete chapter devoted to tuplets. She talks of tuplets
across barlines (can be sub-divided with
>> Nice! One minor thing: If space allows, I would move the `3' a bit
>> nearer to the center to reduce the curvature of the slur.
>
> You mean move the `3' nearer to the staff, right?
Yep.
Werner
___
lilypond-user mailing list
lilypond-user@gn
2016-04-15 19:07 GMT+02:00 David Nalesnik :
> Even if it is unlikely that an era of music which favors bow notation would
> require tuplets across bars or line breaks, it still makes sense to allow
> them for consistency.
Agreed. I never considered to disallow tuplets over line-break.
Gould has n
2016-04-15 7:25 GMT+02:00 Werner LEMBERG :
>
>> Meanwhile I recoded it (using make-bow-stencil which is not
>> available in 2.18.2) making things way easier.
>
> Nice! One minor thing: If space allows, I would move the `3' a bit
> nearer to the center to reduce the curvature of the slur.
You mean
On Fri, Apr 15, 2016 at 11:53 AM, Simon Albrecht
wrote:
> On 15.04.2016 10:23, David Kastrup wrote:
>
>> Josquin des Prez? I've sung some Missa from him with wildly augmented
triplets crossing a number of bars. Timing them accurately took some
math because at that speed there was no n
On 15.04.2016 10:23, David Kastrup wrote:
Josquin des Prez? I've sung some Missa from him with wildly augmented
triplets crossing a number of bars. Timing them accurately took some
math because at that speed there was no natural flow any more really.
That would be early 16th century.
Wouldn't
David Kastrup writes:
[...]
> "Phil Holmes" writes:
>
>> So to notate it for singers today, you could do it any way that you
>> choose to make it look sensible.
>
> Which would usually involve triplet brackets rather than hacking this
> into partial note values at measure boundaries. Which is
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To: "Simon Albrecht"
> Cc: "Thomas Morley" ;
> Sent: Friday, April 15, 2016 8:04 AM
> Subject: Re: Tuplet number direction
>
>
>> Simon Albr
- Original Message -
From: "David Kastrup"
To: "Simon Albrecht"
Cc: "Thomas Morley" ;
Sent: Friday, April 15, 2016 8:04 AM
Subject: Re: Tuplet number direction
Simon Albrecht writes:
On 15.04.2016 00:51, Thomas Morley wrote:
(1) The TupletNumber
Simon Albrecht writes:
> On 15.04.2016 00:51, Thomas Morley wrote:
>> (1) The TupletNumbers are always inside the bow, I coded no
>> possibility to print the Number cutting the bow.
>> I maybe add it later.
>> (2) What to do at line-break?
>
> Wouldn’t it better do disallow line-breaks during tup
> Meanwhile I recoded it (using make-bow-stencil which is not
> available in 2.18.2) making things way easier.
Nice! One minor thing: If space allows, I would move the `3' a bit
nearer to the center to reduce the curvature of the slur. Would that
be possible?
Werner
_
On 15.04.2016 00:51, Thomas Morley wrote:
(1) The TupletNumbers are always inside the bow, I coded no
possibility to print the Number cutting the bow.
I maybe add it later.
(2) What to do at line-break?
Wouldn’t it better do disallow line-breaks during tuplets (i.e.
\override TupletBracket.bre
2016-04-13 23:28 GMT+02:00 Thomas Morley :
> 2016-04-13 15:06 GMT+02:00 Richard Shann :
>> Thanks Abraham, that's most informative.
>> Thinking about it, I wonder if I've missed something: is there a way to
>> say typeset the tuplet bracket like a slur, with the tupl
ative.
> > > > Thinking about it, I wonder if I've missed something: is
> > there a way to
> > > > say typeset the tuplet bracket like a slur, with the
> > tuplet number
> > > > inside?
> > &
e missed something: is
> there a way to
> > > say typeset the tuplet bracket like a slur, with the
> tuplet number
> > > inside?
> >
> > I once made the attached code.
> > Maybe you can ada
?type=node&node=189594&i=0>>:
> > > Thanks Abraham, that's most informative.
> > > Thinking about it, I wonder if I've missed something: is there a way
> to
> > > say typeset the tuplet bracket like a slur, with the tuplet number
> > >
On Wed, 2016-04-13 at 23:28 +0200, Thomas Morley wrote:
> 2016-04-13 15:06 GMT+02:00 Richard Shann :
> > Thanks Abraham, that's most informative.
> > Thinking about it, I wonder if I've missed something: is there a way to
> > say typeset the tuplet bracket like
On 14.04.2016 06:19, Werner LEMBERG wrote:
is there a way to say typeset the tuplet bracket like a slur, with
the tuplet number inside?
I once made the attached code.
Very nice! LSR?
Actually, I would even like to see this directly in lilypond! Such
triplet slurs are used very often in the
>>> is there a way to say typeset the tuplet bracket like a slur, with
>>> the tuplet number inside?
>>
>> I once made the attached code.
>
> Very nice! LSR?
Actually, I would even like to see this directly in lilypond! Such
triplet slurs are used very o
is there a way to
>>> say typeset the tuplet bracket like a slur, with the tuplet number
>>> inside?
>>
>> I once made the attached code.
>> Maybe you can adapt it to fit your needs.
>
>
> Very nice! LSR?
>
> Best, Simon
Sometimes I have the impressi
On 13.04.2016 23:28, Thomas Morley wrote:
2016-04-13 15:06 GMT+02:00 Richard Shann:
Thanks Abraham, that's most informative.
Thinking about it, I wonder if I've missed something: is there a way to
say typeset the tuplet bracket like a slur, with the tuplet number
inside?
I onc
2016-04-13 15:06 GMT+02:00 Richard Shann :
> Thanks Abraham, that's most informative.
> Thinking about it, I wonder if I've missed something: is there a way to
> say typeset the tuplet bracket like a slur, with the tuplet number
> inside?
I once made the attached code.
May
Hi,
perhaps this goes into the right direction:
https://lists.gnu.org/archive/html/lilypond-user/2011-10/msg00325.html
I thought I've seen more of this in the snippets, but I couldn't find
anything.
HTH,
Joram
___
lilypond-user mailing list
lilypond-
On 13.04.2016 15:06, Richard Shann wrote:
Thinking about it, I wonder if I've missed something: is there a way to
say typeset the tuplet bracket like a slur, with the tuplet number
inside?
That would be great to have, and I think has been requested some times
already. But I assume this
Thanks Abraham, that's most informative.
Thinking about it, I wonder if I've missed something: is there a way to
say typeset the tuplet bracket like a slur, with the tuplet number
inside?
The reason I ask is that I came to this section of the manual because
when typesetting 18th c.
Richard, et al,
Many grob properties are given a function (like
tuplet-number::calc-direction) rather than a static value (like UP) when
the property depends on many factors. In other words, by default, it's as
if the 'direction property was set with
\override TupletNumber.direction
>
> Andrew
>
>
>
> On 13/04/2016, 19:37, "lilypond-user on behalf of Richard Shann"
> rich...@rshann.plus.com> wrote:
>
>
> put the tuplet number above rather than below
___
lilypond-user mailing li
On Wed, 2016-04-13 at 11:00 +0100, Phil Holmes wrote:
> - Original Message -
> From: "Richard Shann"
> To:
> Sent: Wednesday, April 13, 2016 10:37 AM
> Subject: Tuplet number direction
>
>
> >I wonder if someone could illuminate the tuplet directi
- Original Message -
From: "Richard Shann"
To:
Sent: Wednesday, April 13, 2016 10:37 AM
Subject: Tuplet number direction
I wonder if someone could illuminate the tuplet direction property - I
wanted to put the tuplet number above rather than below and looked up:
http://li
Above or below what object?
Andrew
On 13/04/2016, 19:37, "lilypond-user on behalf of Richard Shann"
wrote:
put the tuplet number above rather than below
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailma
I wonder if someone could illuminate the tuplet direction property - I
wanted to put the tuplet number above rather than below and looked up:
http://lilypond.org/doc/v2.18/Documentation/internals/tupletnumber
direction (direction):
tuplet-number::calc-direction
If side-axis is 0 (or X
38.n5.nabble.com/Grace-note-kicks-tuplet-number-away-tp184567p186671.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Stanton Sanderson writes:
>> On Jan 18, 2016, at 5:07 PM, Malte Meyn wrote:
>>
>>
>>
>>> Am 18.01.2016 um 23:52 schrieb Mark Stephen Mrotek:
>>> In 2.18,
>>>
>>> Tuplet - no number\override TupletNumber #'stencil = ##f
>>
>> Setting the stencil to ##f is exactly what \omit does ;) (\omi
Stanton Sanderson writes:
> How does one revert \omit TupletNumber to allow the number to appear for a
> specific tuplet? In the following example, I would like to show the tupet
> number in the second measure. Thanks in advance.
>
> Stan
>
> \version "2.19.35"
> \relative c'' {
> c
> On Jan 18, 2016, at 5:07 PM, Malte Meyn wrote:
>
>
>
>> Am 18.01.2016 um 23:52 schrieb Mark Stephen Mrotek:
>> In 2.18,
>>
>> Tuplet - no number\override TupletNumber #'stencil = ##f
>
> Setting the stencil to ##f is exactly what \omit does ;) (\omit already
> exists in 2.18).
A third
Am 18.01.2016 um 23:52 schrieb Mark Stephen Mrotek:
> In 2.18,
>
> Tuplet - no number\override TupletNumber #'stencil = ##f
Setting the stencil to ##f is exactly what \omit does ;) (\omit already
exists in 2.18)
___
lilypond-user mailing list
lil
pletBracket #'bracket-visibility = ##f
> Tuplet - no number\override TupletNumber #'stencil = ##f
> Tuplet - number \revert TupletNumber #'stencil
>
> Mark
>
> -Original Message-
> From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
> [mailto:l
Am 18.01.2016 um 23:46 schrieb Stanton Sanderson:
> How does one revert \omit TupletNumber to allow the number to appear for a
> specific tuplet?
There are two options:
1. If you want to omit only one TupletNumber you can use \once:
… \once \omit TupletNumber \tuplet …
2. Revert the \
Stan,
In 2.18,
Tuplet - no bracket \override TupletBracket #'bracket-visibility = ##f
Tuplet - no number \override TupletNumber #'stencil = ##f
Tuplet - number \revert TupletNumber #'stencil
Mark
-Original Message-
From: lilypond-user-bounces+carsonmark=ca
How does one revert \omit TupletNumber to allow the number to appear for a
specific tuplet? In the following example, I would like to show the tupet
number in the second measure. Thanks in advance.
Stan
\version "2.19.35"
\relative c'' {
c \omit TupletNumber \tuplet 3/2 {c4 b8} c4
isn't taking grace notes
into consideration. I added this information mentioned here, as well as a
link to this discussion, to the issue tracker, but my post is pending
moderation.
Cheers,
Gilberto
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Grace-note-kicks-tupl
ilyissues/issues/3831/>.
Yours, Simon
On 07.12.2015 21:08, Gilberto Agostinho wrote:
Hi all,
When cross staffing, I found that sometimes a grace note in the middle of
the beam causes the tuplet number to move absurdly higher or lower:
\version "2.19.32"
\markup{"ugly"}
\autoc
Hi all,
When cross staffing, I found that sometimes a grace note in the middle of
the beam causes the tuplet number to move absurdly higher or lower:
\version "2.19.32"
\markup{"ugly"}
\autochange {
\tuplet 7/4 { c,32[ c, c, \grace{ c,8 } c,32 c, c''' c,]
Gentlemen, Thank You!
Here’s a simplified example of the horizontal shift of the tuplet number that I
want to achieve. The key to it is the understanding of the use of the X-extent
property. Thank you so much for your help.
\version "2.19.17"
bass = \relative c {
\time 1/4
you could just make One
\relative c''{
% make sure they are the same size
\once\override TupletNumber.X-offset = #(lambda (grob) (+ 5
(ly:tuplet-number::calc-y-offset grob)))
\once\override TupletNumber.Y-offset = #(lambda (grob) (+ -1.2
(ly:tuplet-number::calc-y-offset grob)))
\tuplet 3/2 {c
Hi Harm, Andrew--
On Mon, Mar 30, 2015 at 10:45 AM, Thomas Morley
wrote:
> Hi Andrew,
>
> 2015-03-30 17:06 GMT+02:00 David Nalesnik :
> > Hi Andrew,
> >
> > On Mon, Mar 30, 2015 at 9:11 AM, Andrew Bernard <
> andrew.bern...@gmail.com>
> > wrote:
>
Hi Andrew,
2015-03-30 17:06 GMT+02:00 David Nalesnik :
> Hi Andrew,
>
> On Mon, Mar 30, 2015 at 9:11 AM, Andrew Bernard
> wrote:
>>
>> How can you move a tuplet number to a different position relative to the
>> centre of the bracket, say 75% along rather than 50%
Hi Andrew,
On Mon, Mar 30, 2015 at 9:11 AM, Andrew Bernard
wrote:
> How can you move a tuplet number to a different position relative to the
> centre of the bracket, say 75% along rather than 50%?
>
> I can use X-offset for the TupletNumber, but this reveals the gap in the
> brac
How can you move a tuplet number to a different position relative to the centre
of the bracket, say 75% along rather than 50%?
I can use X-offset for the TupletNumber, but this reveals the gap in the
bracket that is the room for the number. How does one move that as well?
Andrew
Hi Abraham,
2014-10-13 21:03 GMT+02:00 Abraham Lee :
> P.S. Can anyone tell us why TupletNumber supports the 'direction property
> at all? I tried them all (UP, DOWN, CENTER, RIGHT, LEFT) and it did nothing.
>
I can't tell. Probably for historical reasons.
Actually, tuplet numbers are always pl
On Mon, Oct 13, 2014 at 12:24 PM, Urs Liska wrote:
The point of this is you don't want the tuplet *number* down but the
whole thing.
Knute,
In other words, instead of "TupletNumber", use "TupletBracket". You can
also use the shortcut "\tupletDown" :)
Reg
The point of this is you don't want the tuplet *number* down but the whole
thing.
Am 13. Oktober 2014 20:13:01 MESZ, schrieb Pierre Perol-Schneider
:
>2014-10-13 20:08 GMT+02:00 Knute Snortum :
>
>> I want the tuplet number to be below the notes. I am evidently doing
&
2014-10-13 20:08 GMT+02:00 Knute Snortum :
> I want the tuplet number to be below the notes. I am evidently doing
> something wrong.
>
Try :
\version "2.18.2"
\language "english"
\relative c' {
\tweak direction #DOWN
\tuplet 3/
I want the tuplet number to be below the notes. I am evidently doing
something wrong.
\version "2.18.2"
\language "english"
\relative c' {
\override TupletNumber.direction = #DOWN
\tuplet 3/2 { c8 d c } c4 c c
}
}
I really should remember to always answer to the list ...
Original Message
Subject: Re: Capped tuplet number
Date: Thu, 03 Jul 2014 18:03:53 +0200
From: Malte Meyn
To: Javier Ruiz-Alma
Of course it is. I don’t have an exact solution but I think one could
change the
Is it possible to add these caps to tuplet numbers?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
oops--forgot to change the version statement back to 2.16.2.
--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On Tue, Jul 9, 2013 at 4:05 PM, David Nalesnik wrote:
>
>
> I've got a newer version of this which allows you to make adjustments to
> the position of the tuplet number along the beam from the default centered
> position. (This sometimes proves necessary when there's a
2013/7/9 David Nalesnik :
> Too much clutter on this computer.
I know _exactly_ what your're talking about.
:D
-Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
1 - 100 of 141 matches
Mail list logo
