Re: Left-hand end of tuplet bracket sometimes wrong
>> 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 Never mind, I did it by myself right now :-) https://gitlab.com/lilypond/lilypond/-/issues/6360 Werner
Re: Ties between voices
Complete coincidence. Andrew Kevin Cole wrote on 4/06/2022 4:28 AM: On Fri, Jun 3, 2022 at 2:10 PM Andrew Bernard mailto:andrew.bern...@mailbox.org>> wrote: I've been away from LilyPond for a long time. Can we now make ties and or/slurs between notes in different voices? I can't seem to find any documentation on this. Was this prompted by my thread from 21 hours ago? Or did you just coincidentally find a need to do the same thing? (Or am I completely misunderstanding your question? Probably the most likely answer.)
Re: Ties between voices
Thanks Jean, I recall this now. A pity this hit a brick wall. In my scores I need it a lot. Dorico does it with ease, so I am going to have to go back to that. Sigh. Jean Abou Samra wrote on 4/06/2022 5:49 AM: See the recent thread https://lists.gnu.org/archive/html/lilypond-devel/2022-05/msg00175.html
Re: Left-hand end of tuplet bracket sometimes wrong
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 the preferred layout...
>
> You would want to adjust the X-positions, so that the TupletNumber is
> centered properly. See the difference:
>
>
> \version "2.22.0"
>
> {
>\offset shorten-pair #'(-1 . 0)
>\tuplet 3/2 \relative { f'4 g a }
>
>\offset X-positions #'(-1 . 0)
>\tuplet 3/2 \relative { f'4 g a }
> }
>
>
> Since an offset of one staff space is only approximate, you would need
> to consult the bounds of the NoteColumns directly:
>
>
> {
>\override TupletBracket.X-positions =
>#(lambda (grob)
> ;; NOTE: The logic here does not fully replace
> ;; ly:tuplet-bracket::calc-x-positions
> (let* ((nc (ly:grob-object grob 'note-columns))
> (xref (ly:grob-common-refpoint-of-array grob nc X))
> (lb (ly:spanner-bound grob LEFT))
> (lbex (ly:generic-bound-extent lb xref))
> (lbrc (ly:grob-relative-coordinate lb xref X))
> (rb (ly:spanner-bound grob RIGHT))
> (rbex (ly:generic-bound-extent rb xref)))
> (cons (- (car lbex) lbrc) (- (cdr rbex) lbrc
>
>\tuplet 3/2 \relative c' { 4 g }
>\tuplet 3/2 \relative c'' { 4 d }
> }
>
>
> Tuplet_Bracket::calc_x_positions relies on Item::get_x_bound_item, which
> includes the logic to prefer using the Stem of a NoteColumn as the bound
> item if the direction matches.
>
> The code above simply ignores that behavior and computes X-positions
> purely based on the extents of the NoteColumns. Mind you,
> Tuplet_Bracket::calc_x_positions does more work to account for
> properties like connect-to-neighbor, break-overshoot, and
> full-length-to-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:
\version "2.23.9"
#(define tuplet-bracket::wrap-all-note-heads
(grob-transformer 'X-positions
(lambda (grob orig)
;; `orig' is the result of `ly:tuplet-bracket::calc-x-positions'
;; we calculate some left/right corrections adding them to it.
;; Because `orig' places TupletBracket ends not really centered above
;; the stems we need to take TupletBracket and Stem thickness into account
(let* ((thick (ly:grob-property grob 'thickness))
(line-thick (ly:staff-symbol-line-thickness grob))
(used-thick (* thick line-thick))
(right-bound (ly:spanner-bound grob RIGHT))
(left-bound (ly:spanner-bound grob LEFT))
;; Don't change `orig' if left or right bound is not NoteColumn
(add-left
(if (grob::has-interface left-bound 'note-column-interface)
(+ (/ used-thick 2)
(let* ((left-stem (ly:grob-object left-bound 'stem))
(lst-dir (ly:grob-property left-stem 'direction))
(lst-th (ly:grob-property left-stem 'thickness))
(lst-coord
(ly:grob-relative-coordinate
left-stem
left-bound
X))
(lb-X-ext
(ly:grob-property left-bound 'X-extent)))
(if (positive? lst-dir)
(- lst-coord)
(- (car lb-X-ext) (/ (* lst-th line-thick) 2)
0))
(add-right
(if (grob::has-interface right-bound 'note-column-interface)
(let* ((rb-X-ext (ly:grob-property right-bound 'X-extent))
(right-stem (ly:grob-object right-bound 'stem))
(rst-coord
(ly:grob-relative-coordinate
right-stem
right-bound
X)))
(+ (- rst-coord)
(/ used-thick -2)
(cdr rb-X-ext)))
0)))
(cons (+ (car orig) add-left) (+ (cdr orig) add-right))
\relative c'' {
\override TupletBracket.X-positions = #tuplet-bracket::wrap-all-note-heads
%% To get all broken parts visible:
\override TupletBracket.bracket-visibility = ##t
\voiceOne
\times 2/3 { 4 q q }
\voiceTwo
\times 2/3 { q \bar "" \break q }
\voiceOne
\times 2/3 { q \bar "" \break q }
\voiceTwo
\times 2/3 { \bar "" \break q q }
}
Cheers,
Harm
Re: Left-hand end of tuplet bracket sometimes wrong
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
centered properly. See the difference:
\version "2.22.0"
{
\offset shorten-pair #'(-1 . 0)
\tuplet 3/2 \relative { f'4 g a }
\offset X-positions #'(-1 . 0)
\tuplet 3/2 \relative { f'4 g a }
}
Since an offset of one staff space is only approximate, you would need
to consult the bounds of the NoteColumns directly:
{
\override TupletBracket.X-positions =
#(lambda (grob)
;; NOTE: The logic here does not fully replace
;; ly:tuplet-bracket::calc-x-positions
(let* ((nc (ly:grob-object grob 'note-columns))
(xref (ly:grob-common-refpoint-of-array grob nc X))
(lb (ly:spanner-bound grob LEFT))
(lbex (ly:generic-bound-extent lb xref))
(lbrc (ly:grob-relative-coordinate lb xref X))
(rb (ly:spanner-bound grob RIGHT))
(rbex (ly:generic-bound-extent rb xref)))
(cons (- (car lbex) lbrc) (- (cdr rbex) lbrc
\tuplet 3/2 \relative c' { 4 g }
\tuplet 3/2 \relative c'' { 4 d }
}
Tuplet_Bracket::calc_x_positions relies on Item::get_x_bound_item, which
includes the logic to prefer using the Stem of a NoteColumn as the bound
item if the direction matches.
The code above simply ignores that behavior and computes X-positions
purely based on the extents of the NoteColumns. Mind you,
Tuplet_Bracket::calc_x_positions does more work to account for
properties like connect-to-neighbor, break-overshoot, and
full-length-to-extent, so this is not a true replacement/fix.
-- Aaron Hill
Re: Ties between voices
> Le 3 juin 2022 à 20:09, Andrew Bernard a écrit : > > I've been away from LilyPond for a long time. Can we now make ties and > or/slurs between notes in different voices? I can't seem to find any > documentation on this. See the recent thread https://lists.gnu.org/archive/html/lilypond-devel/2022-05/msg00175.html Jean
Ties between voices
I've been away from LilyPond for a long time. Can we now make ties and or/slurs between notes in different voices? I can't seem to find any documentation on this.
Re: Left-hand end of tuplet bracket sometimes wrong
> 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
Re: Key and tie questions
I have gotten to where I can do what I intended to do today and now I may
have the patience to read. Thank you for all your help!
On Fri, Jun 3, 2022 at 10:25 AM Carl Sorensen
wrote:
>
>
> On Fri, Jun 3, 2022 at 11:16 AM Andrew Musselman <
> andrew.mussel...@gmail.com> wrote:
>
>> As for the key signature, I am still seeing nothing about key in the pdf
>> when I do this to remove all complexity:
>>
>> \version "2.22.2"
>> \key d \major
>> {
>> a
>> }
>>
>
> put the first brace before \key and it will give you what you want.
>
> Please work your way carefully through the Learning Manual. It is
> annoying to do so, but it will provide you the basis you need to succeed in
> LilyPond.
>
> A score is a single musical expression.
>
> You have two musical expressions in this file:
>
> A) \key d\major
> B) { a }
>
> Each is wrapped in its own score contect by default. Score A creates no
> output. Score B creates the output of a single note, with no explicit key
> signature, so c major is assumed.
>
> If you do
>
> {
> \key d \major
> a
> }
>
> then you will have a single music expression, and you will get a single
> score that includes both the key signature and the note.
>
> HTH,
>
> Carl
>
Re: Key and tie questions
On Fri, Jun 3, 2022 at 11:16 AM Andrew Musselman
wrote:
> As for the key signature, I am still seeing nothing about key in the pdf
> when I do this to remove all complexity:
>
> \version "2.22.2"
> \key d \major
> {
> a
> }
>
put the first brace before \key and it will give you what you want.
Please work your way carefully through the Learning Manual. It is annoying
to do so, but it will provide you the basis you need to succeed in LilyPond.
A score is a single musical expression.
You have two musical expressions in this file:
A) \key d\major
B) { a }
Each is wrapped in its own score contect by default. Score A creates no
output. Score B creates the output of a single note, with no explicit key
signature, so c major is assumed.
If you do
{
\key d \major
a
}
then you will have a single music expression, and you will get a single
score that includes both the key signature and the note.
HTH,
Carl
Re: Key and tie questions
Okay thank you, I did find this example that worked:
\relative {
\key d \major
cis''4 d e fis
}
On Fri, Jun 3, 2022 at 10:21 AM David Santamauro
wrote:
> Like David said earlier, you actually have 2 implicit scores.
>
>
>
> \version "2.22.2"
>
> % score 1 that yields the warning and prints nothing (hence no key
> signature)
>
> \key d \major
>
>
>
> % score 2
>
> { a }
>
>
>
> This works:
>
>
>
> \version "2.22.2"
>
> \relative {
>
> \key d \major a
>
> }
>
>
>
>
>
> *From: *lilypond-user gmail@gnu.org> on behalf of Andrew Musselman <
> andrew.mussel...@gmail.com>
> *Date: *Friday, June 3, 2022 at 1:16 PM
> *To: *lilypond-user@gnu.org
> *Subject: *Re: Key and tie questions
>
> As for the key signature, I am still seeing nothing about key in the pdf
> when I do this to remove all complexity:
>
>
>
> \version "2.22.2"
> \key d \major
> {
> a
> }
>
>
>
> Log says:
>
>
>
> $ lilypond -f pdf the-mountain.ly
> GNU LilyPond 2.22.2 (running Guile 2.2)
> Processing `the-mountain.ly'
> Parsing...
> Interpreting music...
> the-mountain.ly:2:1: warning: skipping zero-duration score
>
> \key d \major
> the-mountain.ly:2:1: warning: to suppress this, consider adding a spacer
> rest
>
> \key d \major
> Interpreting music...
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Converting to `the-mountain.pdf'...
> Success: compilation successfully completed
>
>
>
> On Fri, Jun 3, 2022 at 10:09 AM Andrew Musselman <
> andrew.mussel...@gmail.com> wrote:
>
> Okay subtle but I do see the difference; thank you
>
>
>
> On Fri, Jun 3, 2022 at 10:07 AM David Kastrup wrote:
>
> Andrew Musselman writes:
>
> > I got a beam by adding `\(` and `\)` around the b and c, looks good.
>
> That's not a beam but a phrasing slur, and at that point in the score, a
> phrasing slur seems like an odd choice: it usually extends over whole
> phrases rather than joining two notes. You probably want a straight
> slur, gotten with `(` and `)`. A beam is a straight line substituting
> for flags on a note stem and connecting several notes of length 1/8 or
> shorter.
>
> --
> David Kastrup
>
>
Re: Key and tie questions
Like David said earlier, you actually have 2 implicit scores.
\version "2.22.2"
% score 1 that yields the warning and prints nothing (hence no key signature)
\key d \major
% score 2
{ a }
This works:
\version "2.22.2"
\relative {
\key d \major a
}
From: lilypond-user
on behalf of Andrew Musselman
Date: Friday, June 3, 2022 at 1:16 PM
To: lilypond-user@gnu.org
Subject: Re: Key and tie questions
As for the key signature, I am still seeing nothing about key in the pdf when I
do this to remove all complexity:
\version "2.22.2"
\key d \major
{
a
}
Log says:
$ lilypond -f pdf the-mountain.ly
GNU LilyPond 2.22.2 (running Guile 2.2)
Processing `the-mountain.ly'
Parsing...
Interpreting music...
the-mountain.ly:2:1: warning: skipping zero-duration score
\key d \major
the-mountain.ly:2:1: warning: to suppress this, consider adding a spacer rest
\key d \major
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Converting to `the-mountain.pdf'...
Success: compilation successfully completed
On Fri, Jun 3, 2022 at 10:09 AM Andrew Musselman
mailto:andrew.mussel...@gmail.com>> wrote:
Okay subtle but I do see the difference; thank you
On Fri, Jun 3, 2022 at 10:07 AM David Kastrup
mailto:d...@gnu.org>> wrote:
Andrew Musselman
mailto:andrew.mussel...@gmail.com>> writes:
> I got a beam by adding `\(` and `\)` around the b and c, looks good.
That's not a beam but a phrasing slur, and at that point in the score, a
phrasing slur seems like an odd choice: it usually extends over whole
phrases rather than joining two notes. You probably want a straight
slur, gotten with `(` and `)`. A beam is a straight line substituting
for flags on a note stem and connecting several notes of length 1/8 or
shorter.
--
David Kastrup
Re: Key and tie questions
As for the key signature, I am still seeing nothing about key in the pdf
when I do this to remove all complexity:
\version "2.22.2"
\key d \major
{
a
}
Log says:
$ lilypond -f pdf the-mountain.ly
GNU LilyPond 2.22.2 (running Guile 2.2)
Processing `the-mountain.ly'
Parsing...
Interpreting music...
the-mountain.ly:2:1: warning: skipping zero-duration score
\key d \major
the-mountain.ly:2:1: warning: to suppress this, consider adding a spacer
rest
\key d \major
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Converting to `the-mountain.pdf'...
Success: compilation successfully completed
On Fri, Jun 3, 2022 at 10:09 AM Andrew Musselman
wrote:
> Okay subtle but I do see the difference; thank you
>
> On Fri, Jun 3, 2022 at 10:07 AM David Kastrup wrote:
>
>> Andrew Musselman writes:
>>
>> > I got a beam by adding `\(` and `\)` around the b and c, looks good.
>>
>> That's not a beam but a phrasing slur, and at that point in the score, a
>> phrasing slur seems like an odd choice: it usually extends over whole
>> phrases rather than joining two notes. You probably want a straight
>> slur, gotten with `(` and `)`. A beam is a straight line substituting
>> for flags on a note stem and connecting several notes of length 1/8 or
>> shorter.
>>
>> --
>> David Kastrup
>>
>
Re: Left-hand end of tuplet bracket sometimes wrong
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 sometimes wrong 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. Is there a reason for this? And is there a way to correct this globally, or do I have to tweak shorten-pair for each affected instance? Paul
Re: Key and tie questions
Okay subtle but I do see the difference; thank you On Fri, Jun 3, 2022 at 10:07 AM David Kastrup wrote: > Andrew Musselman writes: > > > I got a beam by adding `\(` and `\)` around the b and c, looks good. > > That's not a beam but a phrasing slur, and at that point in the score, a > phrasing slur seems like an odd choice: it usually extends over whole > phrases rather than joining two notes. You probably want a straight > slur, gotten with `(` and `)`. A beam is a straight line substituting > for flags on a note stem and connecting several notes of length 1/8 or > shorter. > > -- > David Kastrup >
Re: Key and tie questions
Andrew Musselman writes: > I got a beam by adding `\(` and `\)` around the b and c, looks good. That's not a beam but a phrasing slur, and at that point in the score, a phrasing slur seems like an odd choice: it usually extends over whole phrases rather than joining two notes. You probably want a straight slur, gotten with `(` and `)`. A beam is a straight line substituting for flags on a note stem and connecting several notes of length 1/8 or shorter. -- David Kastrup
Re: Key and tie questions
A tie from the b cannot be terminated because there is no following b!
If you're trying to tie from the c in the middle of the triplet to the c after
it, put the tilde next to it - of course, this will fail by default, but can be
enabled to succeed by using: \set tieWaitForNote = ##t
Paul
From: Andrew Musselman
To:
Sent: 03/06/2022 17:38
Subject: Key and tie questions
Hi all, I'm not seeing a key signature show up when I do this:
```\version "2.22.2"
\relative
\key d \major
{
<<
{
a'8 g'8 \tuplet 3/1 {f' c' b} c'8 c'2
}
>>
}```
and when I try to put a tie between the triplet and the next note and put a
tilde after the `b` in the triplet I get this error:
Interpreting music...
the-mountain.ly:7:45: warning: unterminated tie
a'8 g'8 \tuplet 3/1 {f' c' b
~} c'8 c'2
Any clues how to fix these?
Re: Key and tie questions
Andrew Musselman writes:
> Hi all, I'm not seeing a key signature show up when I do this:
>
> ```\version "2.22.2"
> \relative
> \key d \major
> {
> <<
> {
> a'8 g'8 \tuplet 3/1 {f' c' b} c'8 c'2
> }
> >>
> }```
This consists of _two_ scores. The first score is
```
\relative
\key d \major
```
and LilyPond decides that without any music in it, it is not worth
typesetting. It does warn you about it:
/tmp/baba.ly:2:1: warning: skipping zero-duration score
\relative
/tmp/baba.ly:2:1: warning: to suppress this, consider adding a spacer rest
\relative
Now the second score is what follows within braces.
> and when I try to put a tie between the triplet and the next note and put a
> tilde after the `b` in the triplet I get this error:
>
> Interpreting music...
> the-mountain.ly:7:45: warning: unterminated tie
> a'8 g'8 \tuplet 3/1 {f' c' b
> ~} c'8 c'2
>
> Any clues how to fix these?
You should take a look at the learning manual to understand the
difference between ties (which create longer-duration note values from
several noteheads at the same pitch) and slurs (which indicate a smooth
connection of notes of typically different pitch).
--
David Kastrup
Re: Key and tie questions
I got a beam by adding `\(` and `\)` around the b and c, looks good.
Still curious why key sig is not showing up.
On Fri, Jun 3, 2022 at 9:38 AM Andrew Musselman
wrote:
> Hi all, I'm not seeing a key signature show up when I do this:
>
> ```\version "2.22.2"
> \relative
> \key d \major
> {
> <<
> {
> a'8 g'8 \tuplet 3/1 {f' c' b} c'8 c'2
> }
> >>
> }```
>
> and when I try to put a tie between the triplet and the next note and put
> a tilde after the `b` in the triplet I get this error:
>
> Interpreting music...
> the-mountain.ly:7:45: warning: unterminated tie
> a'8 g'8 \tuplet 3/1 {f' c' b
> ~} c'8 c'2
>
> Any clues how to fix these?
>
Key and tie questions
Hi all, I'm not seeing a key signature show up when I do this:
```\version "2.22.2"
\relative
\key d \major
{
<<
{
a'8 g'8 \tuplet 3/1 {f' c' b} c'8 c'2
}
>>
}```
and when I try to put a tie between the triplet and the next note and put a
tilde after the `b` in the triplet I get this error:
Interpreting music...
the-mountain.ly:7:45: warning: unterminated tie
a'8 g'8 \tuplet 3/1 {f' c' b
~} c'8 c'2
Any clues how to fix these?
Re: make \breath (kind-of) ignore clef change
Kieren MacMillan writes:
> Hi David,
>
>> Try
>>
>> \new Lyrics \lyricmode {
>> \tweak color #red love
>> \propertyTweak color #blue wonderful
>> }
>>
>> And you'll get the error message
>> /tmp/ba.ly:4:1: error: bad grob property path (wonderful color)
>>
>> In general, tweaks that have some chance to be applied to lyrics may
>> become awkward with \propertyTweak .
>
> Thanks for the example.
>
> Is that the only situation you know of where it fails?
> Is it technically possible to fix that (and any other examples) so
> that \propertyTweak works everywhere “as expected”?
I have no idea what you base your expectations for \tweak and/or
\propertyTweak on, and I have no idea what you would consider a "fix"
since clearly there is overlapping syntax that will not magically become
non-overlapping by decree.
There are two different commands since there are syntactically identical
cases that warrant different resolution depending on the purpose of
commands one may assemble from either version.
--
David Kastrup
Most intuitive way to make custom bezier curves paths
I want to experiment more with postscript paths but I find the methods I'm aware of confusing because they are based on absolute? points rather than a mathematical shape if that makes sense. I want to create a multisegment path from 3 cubic bezier curves.
Re: make \breath (kind-of) ignore clef change
Hi David,
> Try
>
> \new Lyrics \lyricmode {
> \tweak color #red love
> \propertyTweak color #blue wonderful
> }
>
> And you'll get the error message
> /tmp/ba.ly:4:1: error: bad grob property path (wonderful color)
>
> In general, tweaks that have some chance to be applied to lyrics may
> become awkward with \propertyTweak .
Thanks for the example.
Is that the only situation you know of where it fails?
Is it technically possible to fix that (and any other examples) so that
\propertyTweak works everywhere “as expected”?
Thanks,
Kieren.
Re: Cannot get clef and time on first measure
"Steven A. Falco" writes: > On 6/2/22 08:08 PM, Jean Abou Samra wrote: >> Le 03/06/2022 à 01:58, Carl Sorensen a écrit : >>> >>> >>> On Thu, Jun 2, 2022 at 5:53 PM Jean Abou Samra wrote: >>> >>> >>> In 2.23.9, you can already do \skip \melody_notes, which >>> skips the duration of \melody_notes. >>> >>> That is way cool! >> Dan (in CC) is the person to thank for it. > > Thanks again for all the "tricks of the trade". I'll play around with > the scheme notation - it is time I learned more about that. > > BTW, the reason the lyrics are self-timed is because there are some > alternate phrasings in the melody. Frankly, I have no beef with self-timed lyrics. It tends to be the most robust against consequences from unrelated changes. It's just not how most people are doing this, so the discussion may be more limited in application than it appears at first sight. And for music-timed lyrics, one has to admit that the idea is tempting that you'll only ever need to enter the lyrics for the Latin Common Mass once and then not touch them ever again, regardless of composition. Though optimistic. -- David Kastrup
Re: Cannot get clef and time on first measure
On 6/2/22 08:08 PM, Jean Abou Samra wrote: Le 03/06/2022 à 01:58, Carl Sorensen a écrit : On Thu, Jun 2, 2022 at 5:53 PM Jean Abou Samra wrote: In 2.23.9, you can already do \skip \melody_notes, which skips the duration of \melody_notes. That is way cool! Dan (in CC) is the person to thank for it. Thanks again for all the "tricks of the trade". I'll play around with the scheme notation - it is time I learned more about that. BTW, the reason the lyrics are self-timed is because there are some alternate phrasings in the melody. Please see measure 14 where we have two extra notes to be used with some of the verses. I don't know how I'd handle that with \addlyrics or \lyricsto. For that matter, the way I added the extra notes is probably a hack, but I haven't found the proper way to do that yet. There is a lot to learn, and that is a big part of what makes it fun for me. Steve
extending tempo
I'm looking for a way to further extend the tempo mark
I know about the simple version
\relative c'' {
\tempo \markup {
\concat {
\bold "Andante appasionata "
"("
\lower #-0.5 \note {4} #UP
" ("
\lower #-0.5 \note {4.} #UP
") = 42)"
}
}
a1
Now this is what I need the tempo to look like
With Swing 2=80 ( two beamed eights = \tuplet 3/2 { 4 2 } )
So how do I create the beamed eights and then create the tuplet (with
tupletbeam -3-)
Thanks for your generous help.
vriendelijke groet, Erik Appeldoorn
Re: Left-hand end of tuplet bracket sometimes wrong
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.
