On Tue, Jul 22, 2025 at 1:36 AM Thomas Morley
wrote:
> How about:
>
> \version "2.24.4"
>
> \relative {
> \key g \minor
> \clef bass
> \time 12/8
> \set subdivideBeams = ##t
> \tupletDown
> g,4.(~ g8
> \override TupletBracket.shorten-pair = #'(0 . 0) %% default: '(-0.2 .
> -0.2)
>
; > I have a situation where LilyPond doesn't do a good job with tuplet
>> > bracket lengths. To fix this, I was thinking of using \tweak
>> > TupletBracket.X-positions, but when there is more than one bracket, this
>> > tweak affects them all the same. I want
Sometimes the simplest solution is the best! I'll give that a try.
--
Knute Snortum
On Mon, Jul 21, 2025, 5:24 PM Kieren MacMillan
wrote:
> Hi Knute,
>
> > I have a situation where LilyPond doesn't do a good job with tuplet
> bracket lengths. To fix this, I was
Hi Knute,
> I have a situation where LilyPond doesn't do a good job with tuplet bracket
> lengths. To fix this, I was thinking of using \tweak
> TupletBracket.X-positions, but when there is more than one bracket, this
> tweak affects them all the same. I want to find a way
Hello, everyone,
I have a situation where LilyPond doesn't do a good job with tuplet bracket
lengths. To fix this, I was thinking of using \tweak
TupletBracket.X-positions, but when there is more than one bracket, this
tweak affects them all the same. I want to find a way to tell lilyPon
Am 25.02.25 um 14:32 schrieb Robin Bannister:
Thomas Ruedas wrote:
for many years I have used a hack for marking a change of hand in
polyphonic piano music that I had been pointed to some 11 years ago on
this group, and it had worked fine. Unfortunately, no more.
I updated this to the attached
2.20, 2.22, 2.24 and seems OK with 2.25.24.
Cheers,
Robin
\version "2.24.0"
% compatibility changes: u15k0830 u23k0114
%% +thumb bracket
#(define (make-thumb-bracket-props location spec-str settings-alist)
(define (inchar? index)
nly seems to be
unhappy about things like # or ;. Can somebody tell me what is wrong and
how to fix it, or else point me to a different implementation of that
other-hand bracket sign I want to use?
Thomas
(define (make-thumb-bracket-props location spec-str settings-alist)
(define (inchar? in
is the interlude; and E is the coda/ending. I've
managed to write down a functional file and proof-tested it by using
the \unfoldRepeats snippet. However, I do not know a way to remove
this volta bracket. Is there a way to hide the volta bracket?
You can remove volta brackets fr
. I've managed to write down a
functional file and proof-tested it by using the \unfoldRepeats snippet.
However, I do not know a way to remove this volta bracket. Is there a way
to hide the volta bracket?
Best regards,
Lucas
%%Code begins
\version "2.25.20"
music = { \relative c' {
On Thu, Dec 12, 2024 at 8:48 AM Werner LEMBERG wrote:
> > Actually, the descriprion is wrong, imho.
> >
> > (bracket-text ,ly:grob? "The text for an analysis bracket.")
> >
> > should become something at he lines of:
> >
> > (bracket-t
> Actually, the descriprion is wrong, imho.
>
> (bracket-text ,ly:grob? "The text for an analysis bracket.")
>
> should become something at he lines of:
>
> (bracket-text ,ly:grob? "The text-grob for an analysis bracket.")
I plan to change the docstri
property to set the text for HorizontalBracketText.
> > 'bracket-text (as an internal property) is a pointer from
> > HorizontalBracket to its HorizontalBracketText-grob.
>
> OK, thanks. The description misses this information; I will update it
> accordingly.
Actually, the descripri
>> What are these properties good for? What can they do what the
>> `text` property of `HorizontalBracket` or `PianoPedalBracket`
>> cannot?
>
> 'text is a grob-property to set the text for HorizontalBracketText.
> 'bracket-text (as an internal property)
Am Mi., 11. Dez. 2024 um 10:11 Uhr schrieb Werner LEMBERG :
>
>
> It seems to me that the `bracket-text` property (as defined in
> `horizontal-bracket-engraver.cc`) is unused – it gets set (with
> `set_object()`) but never read.
>
> Ditto for `pedal-text` in `piano-pedal-b
It seems to me that the `bracket-text` property (as defined in
`horizontal-bracket-engraver.cc`) is unused – it gets set (with
`set_object()`) but never read.
Ditto for `pedal-text` in `piano-pedal-bracket`.
What are these properties good for? What can they do what the `text`
property of
ing a Scheme function
>> https://lsr.di.unimi.it/LSR/Item?id=902
>>
>> 2/ Using brackets instead of parentheses for \parenthesize
>> https://lsr.di.unimi.it/LSR/Item?id=564
>>
>> Any advice would be appreciated.
>>
>
> Hi Matt,
>
> LSR gives th
%%% LSR 564 %%%
#(define-public (bracket-stencils
grob)
(let ((lp (grob-interpret-markup grob (markup #:fontsize
3.5 #:translate (cons -0.3 -0.5) "[")))
(rp (grob-interpret-markup grob (markup #:fontsize
a group of notes using a Scheme function
> https://lsr.di.unimi.it/LSR/Item?id=902
>
> 2/ Using brackets instead of parentheses for \parenthesize
> https://lsr.di.unimi.it/LSR/Item?id=564
>
> Any advice would be appreciated.
>
Hi Matt,
LSR gives these:
%%% LSR 564 %%%
#(def
Dear LilyPonders,
I've been trying to combine two solutions in the LSR, but I haven't been
able to figure out how. I want *square brackets* for parenthesizing a group
of notes
1/ Parenthesize a group of notes using a Scheme function
https://lsr.di.unimi.it/LSR/Item?id=902
2/ Using brackets inste
Hi Xavier,
> Although using extra-offset gives the desired look, I tend to use another
> property that takes possible collisions into account whenever possible.
> In this case, the padding property sets the spacing between the bracket and
> the bar.
>
> \override SystemSt
On Tue, 10 Sept 2024 at 02:50, Kieren MacMillan
wrote:
>
> Hi Dimitri,
>
> > How can I reduce the space between the bracket and the first barline?
>
> %%% SNIPPET BEGINS
> \version "2.25.11"
>
> \new ChoirStaff
> \with { \override SystemStart
Hi Dimitri,
> How can I reduce the space between the bracket and the first barline?
%%% SNIPPET BEGINS
\version "2.25.11"
\new ChoirStaff
\with { \override SystemStartBracket.extra-offset = #'(0.5 . 0) }
<<
\new Staff c''1
\new Staff c''
How can I reduce the space between the bracket and the first barline?
Thanks
> Thank you Werner for the suggestion. I just submitted the issue.
Thanks.
Werner
Thank you Kieren for the MWE. you're right! :-)
and
Thank you Werner for the suggestion. I just submitted the issue.
Best
Karim
On Thu, Aug 15, 2024 at 03:55:38AM +, Werner LEMBERG wrote:
> > Hi Karim,
> >
> >> I tried with a Minimal example here with the dev. version:
> >
> > The followin
> Hi Karim,
>
>> I tried with a Minimal example here with the dev. version:
>
> The following seems more minimal to me: [...]
Karim, please file an issue in our bug tracker!
Werner
Hi Karim,
> I tried with a Minimal example here with the dev. version:
The following seems more minimal to me:
%%% SNIPPET BEGINS
\version "2.25.1"
\layout {
\context {
\Score
tupletFullLength = ##t
}
}
one = {
r1
}
two = {
r2.
\tuplet 5/4 {
r8.
c'8
}
}
\score
override TupletBracket.bracket-visibility = ##t
tupletFullLength = ##t
}
}
}
%%%
But it seems still not optimal. The end edge of the bracket overlaps the
StaffGroup bar.
Best
--
Karim Haddad
Music Representations Team, IRCAM
Research and development manager.
Hi Fennel,
Not sure why some other incantations I tried didn’t work… but maybe this hack
will help you?
%%% SNIPPET BEGINS
\version "2.24.3"
\layout {
\context {
\Voice
\consists Horizontal_bracket_engraver
}
}
\relative c' {
\alterBroken extra-offset #'((0 . 0) (6 . -1.5)) Hori
I’m using analysis brackets as shown in the snippet below:
\version "2.24.3"
\layout {
\context { \Voice \consists Horizontal_bracket_engraver } }
\relative c' {c1 \startGroup | \break
c1 \stopGroup
}
which produces the following output:
[image.png]
I would like
Hi,
I've been trying to make a bracket to indicate a change of manuals for an
organ piece, and have succeeded in getting Lilypond to generate what I want
(code below) for a particular instance. However, I have three questions:
1) Why does this particular format work? I'm not underst
lt behaviour 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
14:03
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 ba
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 imag
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 improper/
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'' \o
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 no
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"
>
&g
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, M
-
>
> Message: 2
> Date: Sat, 27 May 2023 05:50:24 -0500
> From: Gregory Rowland Evans
> To: Jean Abou Samra
> Cc: Lilypond-User Mailing List
> Subject: Re: Annotated tuplet bracket
> Message-ID:
> Content-Type: text/plain; charset="utf-8"
>
> H
Music for oboe by Mahnkopf?
Hi Jean,
In the attached image, notice the parenthesized note head above some of the
tuplet numbers. If the bracket is down the annotation would be below the tuplet
number. I have been able to override the tuplet number to modify the text to be
whatever I want, however I was looking to automate
> 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 tuplet
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
Le mardi 16 mai 2023 à 16:24 +0100, Paul Hodges a écrit :
> I have a horizontal bracket with lengthened edges. I want the edges to be
> dashed, but I can't see a way to do this without the horizontal part being
> dashed as well. Is there a simple solution, or do I just h
I have a horizontal bracket with lengthened edges. I want the edges to be
dashed, but I can't see a way to do this without the horizontal part being
dashed as well. Is there a simple solution, or do I just have to draw an extra
solid line over the part I don't want dashed?
Thanks,
Paul
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://gi
Am Fr., 3. Juni 2022 um 22:40 Uhr schrieb Aaron Hill :
>
> 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 th
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 TupletNumb
> 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 br
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 in
Hello Michael,
Nothing about the Dynamics context, I just messed up the code for the part if
there is no break (why did I not test this?). The appended file fixes this.
Also if you want this as a general style it is probably better to put it into
a layout or a with block.
Cheers,
Valentin
Am
Thanks, Valentin. That looks great. However, when I use it in a Dynamics
context, I get an error message. Is there something else I would need to do
to transplant this to a Dynamics context? I appreciate the work you did to
make this.
Best,
Michael
\version "2.23.5"
right = \relative c'' {
}
l
Hello Michael,
Could something like this work?
Cheers,
Valentin
Am Donnerstag, 27. Jänner 2022, 23:13:49 CET schrieb Michael Rivers:
> Does anyone know if there was ever an answer to this? I’m re-engraving a
> score that has a piano pedal style with “Ped”, then a solid line, then a
> “*” at the e
Does anyone know if there was ever an answer to this? I’m re-engraving a score that has a piano pedal style with “Ped”, then a solid line, then a “*” at the end. It’s close to “mixed” style but with an added “*” at the end. Thanks in advance,Michael
d GrandStaff inherit from StaffGroup
(PianoStaff
still inherits from GrandStaff) to keep all of them in sync.
StaffGroup gains a bunch of \accepts, so it accepts everything also
accepted by Score.
This fixes a problem occurring when a TabStaff was included in a
ChoirStaff.
The latter
nch of \accepts, so it accepts everything also
accepted by Score.
This fixes a problem occurring when a TabStaff was included in a
ChoirStaff.
The latter did not accept it, causing a StaffGroup to be inserted
in between,
with its own bracket.
Closes: #6094
In summary: your score was relying on buggy behavior.
Fortunately, it's easy to fix it by using the method
that is documented to give the behavior you want.
Hope that helps,
Jean
Op 24-01-2022 om 21:10 schreef Valentin Petzel:
Hello Jogchum,
You have a GrandStaff on the top level (I guess for spanned barlines?). This
will add a brace by default. This brace cannot get arbitrarily large, so it
only spans part of the System.
Two solutions:
Just get rid of the GrandStaff (i
Hello Jogchum,
You have a GrandStaff on the top level (I guess for spanned barlines?). This
will add a brace by default. This brace cannot get arbitrarily large, so it
only spans part of the System.
Two solutions:
Just get rid of the GrandStaff (if you do not in fact want spanned barlines,
whi
\override Staff.Arpeggio.stencil = #ly:arpeggio::brew-chord-bracket
>
> This works for me:
>
> \version "2.22.1"
>
> spanArpeggioBrace =
> \once \override Staff.Arpeggio.stencil =
> #(lambda (grob)
> (let* ((positions (ly:grob-property grob 'po
t; Hallo,
>>>>
>>>> I’d like to replace the arpeggioBracket by a curly bracket / brace.
>>>> Thank your for your help!
>>>
>>> Here's a stencil callback reading the vertical start
>>> and end positions of the arpeggio and
Le 19/01/2022 à 14:47, Thomas Scharkowski a écrit :
This does not work for me (I did change of course PianoStaff to Staff).
To get the „normal“ brackets I use:
\override Staff.Arpeggio.stencil = #ly:arpeggio::brew-chord-bracket
This works for me:
\version "2.22.1"
spanArpeggioBra
Le 19/01/2022 à 13:58, Thomas Scharkowski a écrit :
Am 19.01.2022 um 13:09 schrieb Jean Abou Samra :
Le 19/01/2022 à 09:46, Thomas Scharkowski a écrit :
Hallo,
I’d like to replace the arpeggioBracket by a curly bracket / brace.
Thank your for your help!
Here's a stencil cal
> Am 19.01.2022 um 13:09 schrieb Jean Abou Samra :
>
> Le 19/01/2022 à 09:46, Thomas Scharkowski a écrit :
>> Hallo,
>>
>> I’d like to replace the arpeggioBracket by a curly bracket / brace.
>> Thank your for your help!
>
>
> Here's a stenci
Le 19/01/2022 à 09:46, Thomas Scharkowski a écrit :
Hallo,
I’d like to replace the arpeggioBracket by a curly bracket / brace.
Thank your for your help!
Here's a stencil callback reading the vertical start
and end positions of the arpeggio and printing a bracket
accordingly:
\ve
Hallo,
I’d like to replace the arpeggioBracket by a curly bracket / brace.
Thank your for your help!
Thomas
Hello Aaron;
Thank you so much. It works!
Ken
On Mon, Dec 20, 2021 at 4:00 PM Aaron Hill wrote:
>
> On 2021-12-20 3:48 pm, Kenneth Wolcott wrote:
> > Hi;
> >
> > How to get huge text (ie: "To Coda") above a volta bracket?
>
> Set outside-st
On 2021-12-20 3:48 pm, Kenneth Wolcott wrote:
Hi;
How to get huge text (ie: "To Coda") above a volta bracket?
Set outside-staff-priority as needed. The default for
VoltaBracketSpanner is 600.
\repeat volta 2 { b'4 a' g'2 }
\alternative { { a'4 b&#x
Hi;
How to get huge text (ie: "To Coda") above a volta bracket?
Thanks,
Ken Wolcott
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 incorre
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
outside-staff-inter
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 pat
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 staf
>> 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 sh
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-pr
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 o
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&
gt;> 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&
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
>> 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
k for the
> positions property. How difficult this is probably depends on the
> use case: Werner, how similar are the instances in your score? Can
> we assume a monotonous sequence of pitches? May we assume that the
> bracket should always be above?
I need this to make the staves use
eally 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 { g
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 automati
callback for the
positions property. How difficult this is probably depends on the use
case: Werner, how similar are the instances in your score? Can we assume
a monotonous sequence of pitches? May we assume that the bracket should
always be above?
Lukas
>> 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
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
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
On Sat, Nov 6, 2021 at 2:08 PM Kieren MacMillan
wrote:
>
> p.s.
>
> > Does \afterBreak not work with OttavaBracket.padding?
>
> um… \alterBroken (as in the snippet).
> Sorry! — K
>
> > \relative {
> > \alterBroken #'padding #'(1 7) Staff.OttavaBracket
> > \ottava 1 c1 \break
> > c2 2
> > }
On 11/6/21, 3:24 PM, "lilypond-user on behalf of Lukas-Fabian Moser"
wrote:
> \relative {
>\alterBroken #'padding #'(1 7) Staff.OttavaBracket
>\ottava 1 c1 \break
> c2 2
> }
I continue my lonely crusade against the hash-tick-combinations that I
Hi Lukas,
> I continue my lonely crusade against the hash-tick-combinations
I generally remove them — I’m on the crusade with you! — tho’ on this
“fast-cut-and-paste job”, I didn’t. =(
That being said, there are certain circumstances in which I prefer keeping the
hashes, as they (IMO) help re
On 2021-11-06 2:45 pm, Lukas-Fabian Moser wrote:
Since #'(1 7) is a list of numbers, you could write it this way:
\relative {
\alterBroken padding 1,7 Staff.OttavaBracket
\ottava 1 c1 \break
c2 2
}
Right, thanks! I had a feeling there was a way to do this using dak's
syntax
1 - 100 of 906 matches
Mail list logo
