>> 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
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
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
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
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
> 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
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.
> 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 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
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.
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
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
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
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
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
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
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
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
```
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
> {
>
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
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
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.
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
>
"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
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
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
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.
27 matches
Mail list logo
