Hi list,
Any idea why, when compiling this code, the first nested triplet displays
with the custom bracket of tuplet on the top level? I would like the
bracket of the first nested tuplet to just display as a normal triplet. I
was not able to find this addressed in the archive, but please point me to
relevant documentation if this has already been covered.
Thank you,
Kyle
\version "2.21.2"
\score {
<<
\new Staff {
\time 3/4
\set subdivideBeams = ##t
\set strictBeatBeaming = ##t
\override TupletBracket.bracket-visibility = ##t
\once \override TupletNumber.text =
#(tuplet-number::append-note-wrapper
(tuplet-number::non-default-tuplet-fraction-text
7 6) (ly:make-duration 3 0))
\times 6/7 {
\times 2/3 { e8([ f8 e8]}
\times 2/3 {f8 e8 f8)}
<< f4 {s16 s16 s8} >>
\times 2/3 {e8[e16~]}
}
|
}
>>
}
On Tue, Nov 3, 2020 at 12:04 PM <lilypond-user-requ...@gnu.org> wrote:
> Send lilypond-user mailing list submissions to
> lilypond-user@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> or, via email, send a message with subject or body 'help' to
> lilypond-user-requ...@gnu.org
>
> You can reach the person managing the list at
> lilypond-user-ow...@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lilypond-user digest..."
> Today's Topics:
>
> 1. Re: Key change at the end of a piece (Pierre Perol-Schneider)
> 2. Re: Key change at the end of a piece (Jean Bréfort)
> 3. Re: piece starting with acciaccatura problem (Marc Shepherd)
>
>
>
> ---------- Forwarded message ----------
> From: Pierre Perol-Schneider <pierre.schneider.pa...@gmail.com>
> To: Ralph Palmer <palmer.r.vio...@gmail.com>
> Cc: lilypond-user Mailinglist <lilypond-user@gnu.org>
> Bcc:
> Date: Tue, 3 Nov 2020 16:30:54 +0100
> Subject: Re: Key change at the end of a piece
> Hi Ralph,
> See:
> http://lilypond.1069038.n5.nabble.com/key-change-at-end-of-snippet-td227745.html
> Cheers,
> Pierre
>
> Le mar. 3 nov. 2020 à 16:13, Ralph Palmer <palmer.r.vio...@gmail.com> a
> écrit :
>
>> Hi -
>>
>> I'm trying to add a clef change at the end of a fiddle tune, to show that
>> the first section is in a different key than the second section (see
>> attached photo). I've searched the Notation Reference, the Snippet
>> Repository, and the User List archive, with no luck.
>>
>> I'd appreciate any help.
>>
>> All the best,
>>
>> Ralph
>>
>> --
>> Ralph Palmer
>> Brattleboro, VT
>> USA
>> (he, him, his)
>> palmer.r.vio...@gmail.com
>>
>
>
>
> ---------- Forwarded message ----------
> From: "Jean Bréfort" <jean.bref...@free.fr>
> To: Ralph Palmer <palmer.r.vio...@gmail.com>, lilypond-user Mailinglist <
> lilypond-user@gnu.org>
> Cc:
> Bcc:
> Date: Tue, 03 Nov 2020 16:41:45 +0100
> Subject: Re: Key change at the end of a piece
> Hi,
>
> You might test something like "\key a\major s32" at the end of the
> score.
>
> Hope this helps,
> Jean
>
> Le mardi 03 novembre 2020 à 09:42 -0500, Ralph Palmer a écrit :
> > Hi -
> >
> > I'm trying to add a clef change at the end of a fiddle tune, to show
> that the first section is in a different key than the second section (see
> attached photo). I've searched the Notation Reference, the Snippet
> Repository, and the User List archive, with no luck.
> >
> > I'd appreciate any help.
> >
> > All the best,
> >
> > Ralph
> >
>
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Marc Shepherd <oakapp...@gmail.com>
> To: Lilypond-User Mailing List <lilypond-user@gnu.org>
> Cc:
> Bcc:
> Date: Tue, 3 Nov 2020 10:49:14 -0500
> Subject: Re: piece starting with acciaccatura problem
> A 300-page quartet? Is this piece as long as *Parsifal?*
>
> On Tue, Nov 3, 2020 at 5:35 AM Andrew Bernard <andrew.bern...@gmail.com>
> wrote:
>
>> It's the infamous Issue 34. It is certainly the most commonly asked
>> question on the list. I hold out hope it will one day be solved. I
>> have a 300 page string quartet with hundreds of grace notes and I have
>> to spend a lot of time adding spacers in three other voices to get it
>> to work. Needless effort that affects everybody. We had a technical
>> discussion on the list recently as to why this is so difficult for
>> lilypond to fix, but I still wish it could be solved.
>>
>
>
> --
> Marc Shepherd
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
