> Thanks for your contributions. They inspired me to an easy bypass:
> ties may not work between staves, but slurs do, and the difference
> is not really conspicuous. [...]
By the way, the original problem is an ooold bug:
https://gitlab.com/lilypond/lilypond/-/issues/555
Werner
On Thu, May 9, 2024 at 6:27 AM Kris Van Bruwaene wrote:
> Thanks for your contributions. They inspired me to an easy bypass: ties
> may not work between staves, but slurs do, and the difference is not really
> conspicuous. Result attached.
>
That's great! I'd change one thing -- not related to
Thanks for your contributions. They inspired me to an easy bypass: ties may not
work between staves, but slurs do, and the difference is not really
conspicuous. Result attached.
On Wednesday, 8 May 2024 at 18:44:10 CEST, David Wright
wrote:
On Wed 08 May 2024 at 13:40:23 (+), Kris
On Wed 08 May 2024 at 13:40:23 (+), Kris Van Bruwaene wrote:
> Is there a simple solution for putting a tie between staves of a pianostaff?
> I need to tie a note of the lower voice on the upper staff to a note of the
> upper voice on the lower staff. I found this on StackExchange:
> https:/
On Wed, May 8, 2024 at 6:41 AM Kris Van Bruwaene wrote:
> Is there a simple solution for putting a tie between staves of a
> pianostaff? I need to tie a note of the lower voice on the upper staff to a
> note of the upper voice on the lower staff. I found this on StackExchange:
> https://music.sta
On Fri, Mar 22, 2024 at 8:38 AM Aaron Hill wrote:
>
>
> \version "2.25.13"
>
> \relative {
>\afterGrace c''4\trill { b16 \set tieWaitForNote = ##t c~ } c4
> }
>
>
Works great! Thanks.
--
Knute Snortum
On 2024-03-22 8:24 am, Knute Snortum wrote:
Hi all,
I am trying to tie an afterGrace note to the next note and I get a
warning. This code:
\version "2.25.13"
\relative {
\afterGrace c''4\trill { b16 c~ } c4
}
...produces this warning:
/tmp/frescobaldi-ieh3nrny/tmpq4qpjmjp/document.ly:4:33
Jean Abou Samra writes:
> Check \repeatTie.
Thanks Jean, that's it!
-David
Check \repeatTie.
On 31/01/2023 23:06, Steve Carlock wrote:
> Jean,
>
> Thank you for approving my email - I did subscribe using the website and
> confirmed the email (and have logged into my account page successfully) prior
> to sending my email to the list. Maybe I was impatient and needed to wait a
> day for
Jean,
Thank you for approving my email - I did subscribe using the website and
confirmed the email (and have logged into my account page successfully)
prior to sending my email to the list. Maybe I was impatient and needed to
wait a day for the account setup to completely process.
Thank you all f
The tie ~ and number 1 in measure 3 are in the wrong order, the tie should
come after the number.
What happens is that Lilypond, when it sees a pitch or duration alone
interprets it as a new note, with the missing pitch or duration carried over
from the previous note. So g~1 becomes a g with
Hi Steve,
welcome to the group!
In your third measure, Instead of
g~1
you should write
g1~
Your sequence means the following:
- g without a duration uses the last duration specified, i.e. whole note
from the measure before.
- ~ produces a tie to the following note.
- 1 without a pitch p
Hello,
Welcome to this list. I had to approve your message manually
because you are not subscribed to the list yet. Please fix this
by subscribing on https://lists.gnu.org/mailman/listinfo/lilypond-user
On 31/01/2023 22:04, Steve Carlock wrote:
> New Lilypond user here. The following code is no
You may try:
\markup \concat {
\tied-lyric "he~yo"
}
El mié, 18 ene 2023 a las 17:50, David Kastrup () escribió:
> Stephan Schöll writes:
>
> > Hi everybody
> >
> > I have stanzas 2..n put as markup below the score. In one stanza there
> > are two syllables on one note. In lyricmode I'd writ
Stephan Schöll writes:
> Hi everybody
>
> I have stanzas 2..n put as markup below the score. In one stanza there
> are two syllables on one note. In lyricmode I'd write the ~, but this
> doesn't work in regular markup. Is there a way to add that kind of text
> syllable tie to markup as well? Or s
Hi Jean,
Le jeu. 10 nov. 2022 à 11:23, Jean Abou Samra a écrit :
...
> This is nice! Just a thought: why use after-line-breaking
> here?
...
Bad habit? Respond without thinking long enough? Too proud it'd worked?
Missing knowledge? All?... Yeah, probably all...
> This is the sort of thing th
Le 10/11/2022 à 04:31, Pierre Perol-Schneider a écrit :
How about:
\version "2.22.0"
oldTie = \once \override Tie.after-line-breaking =
#(lambda (grob)
(let*
((stencil (ly:tie::print grob))
(dir (ly:grob-property grob 'direction))
(markup-stencil
Perol-Schneider
Sent: Wednesday, November 9, 2022 9:31 PM
To: Andrew Bernard
Cc: lilypond-user@gnu.org
Subject: Re: Tie with slash (caesura) on the curve
Hi Andrew, Hi Dirck,
Le jeu. 10 nov. 2022 à 02:40, Andrew Bernard
mailto:andrew.bern...@mailbox.org>> a écrit :
Never say anyth
Hi Andrew, Hi Dirck,
Le jeu. 10 nov. 2022 à 02:40, Andrew Bernard a
écrit :
> Never say anything is technically unplayable for pianists. Some of the
> technical ability of contemporary players leaves me breathless.
>
...
Actually it's for guitarists ;)
On 10/11/2022 12:02 pm, Dirck Nagy wrote:
Never say anything is technically unplayable for pianists. Some of the
technical ability of contemporary players leaves me breathless.
What you are after perhaps is an editorial tie. Dorico has them, with a
single bar through the middle. I know its not exactly the same. I'm sure
I have come a
On Sat, Sep 17, 2022 at 11:30 AM Jean Abou Samra wrote:
>
>
>
> Le 17/09/2022 à 20:24, Knute Snortum a écrit :
[snip]
> > Is this a bug? Is there a better way to deal with it?
> >
> > --
> > Knute Snortum
>
>
> Yeah, known long-standing issue.
>
> https://gitlab.com/lilypond/lilypond/-/issues/298
Le 17/09/2022 à 20:24, Knute Snortum a écrit :
I have run into a situation that may be a bug or it may be I'm not
doing something correctly. I have a \voiceOne note at a line break
where the tie becomes nearly invisible.
%%%
\version "2.23.12"
\paper {
ragged-right = ##t
indent = 0
}
Hi Christel,
> If you think of a way: I'm definitely interested!
I do this kind of thing all the time: just use an arrow markup, disconnect it
from the spacing engine (there are a number of ways of doing this), and tack it
on to the repeat barline!
If you need more than that hint, I can whip u
Le 19/05/2022 à 17:43, Christel le Pair a écrit :
Hello David,
Thank you for the quick response!
I'm working on a tablet, so I'm always on one page.
Indeed that would not be possible -> could give an error, like it more
often does ;-)
If you think of a way: I'm definitely interested!
Hi Ch
Hello David,
Thank you for the quick response!
I'm working on a tablet, so I'm always on one page.
Indeed that would not be possible -> could give an error, like it more
often does ;-)
If you think of a way: I'm definitely interested!
Thanks again,
Christel
On Thu, May 19, 2022 at 4:03 PM Davi
Christel le Pair writes:
> Hello Lilypond,
>
> I'm so happy with your tool.
> Just using it for my own use, have all b and # notes in red.
> But here is my question... or actually I have 2:
>
> Question 1:
> \repeat volta 2 { c1 *(* }
> \alternative
> {
> { e1*)* }
> { d1*)* }
> }
Hello Adrian,
as Aaron said there are some arguments to defining functions to give access to
the parser and the layout that have been made optional since 2.20. That being
said, 2.18.2 is now nearly 8 years old. Unless there is a good reason for the
old version consider switching to a recent ver
On 2021-12-17 12:37 am, Adrian Oehm wrote:
I’ve tried the code you supplied, but unfortunately I keep getting the
following error:
"ly-syntax-constructors.scm:56:23: Wrong number of arguments to
#"
I get this trying to compile both with the code in my document and
also trying to compile yours.
Hi Valentin
Thanks for your reply.
I’ve tried the code you supplied, but unfortunately I keep getting the
following error:
"ly-syntax-constructors.scm:56:23: Wrong number of arguments to #"
I get this trying to compile both with the code in my document and also trying
to compile yours. One i
That line at the bottom came from testing, so it should be ignored.
signature.asc
Description: This is a digitally signed message part.
Hello Adrian,
How about this?
Cheers,
Valentin
Am Donnerstag, 16. Dezember 2021, 05:10:21 CET schrieb Adrian Oehm:
> Hi
>
> Can anyone point me in the right direction to solve this:
>
> I have the below, using a lyric tie,
>
>
> but what i really want is what looks like a tie between notes t
Great, I think I understand. Thank you very much.
-Tom
On Fri, Dec 3, 2021 at 12:48 PM Lukas-Fabian Moser wrote:
> Hi Tom,
>
> Am 03.12.21 um 16:02 schrieb Tom Sgouros:
> > Thanks, but I'm not sure I completely understand. What you're saying
> > is that if you don't define a voice immediately,
Hi Tom,
Am 03.12.21 um 16:02 schrieb Tom Sgouros:
Thanks, but I'm not sure I completely understand. What you're saying
is that if you don't define a voice immediately, you still get one,
but its name is nothing ("")? So in my multi-voice segment I can
explicitly reference the voice-with-no-nam
Hi Akikazu,
It seems that grob directions are not set implicitly in non-number ID
context.
Yes, that's true - I forgot to mention that. Thanks for your examples,
both of which I'd recommend as "good practice".
Lukas
Thanks, but I'm not sure I completely understand. What you're saying is
that if you don't define a voice immediately, you still get one, but
its name is nothing ("")? So in my multi-voice segment I can explicitly
reference the voice-with-no-name as you are showing with the \voices
construct? That m
Hi Lukas,
It seems that grob directions are not set implicitly in non-number ID context.
See:
%%
\new Staff {
a'1
\voices "",2 <<
{ d''4 e'' d''2~ } \\
{ g'2 g' }
>>
d''2 c''
}
%%
In that case, the direction of Voice "" should be specified, and restored with
\oneVoice.
%
Hi Tom,
This does not work: << { d1~ } \\ {g1} >> | d1 | No tie appears
and I don't see anything like an error or warning that I can do
anything with. I can rewrite to have an empty second voice in that
second measure, but maybe it's feasible to do it some other way?
If the un-named impl
Thank you very much, Aaron ! It works.
Cheers,
Claire
On Sat, Sep 12, 2020 at 12:35 AM Aaron Hill
wrote:
> On 2020-09-11 3:25 pm, Claire Meyer wrote:
> > Hi,
> >
> > I've got a problem with a tie not appearing. My problematic bar is as
> > follows :
> >
> > upperHighB = \relative c'' {
> > d8
On 2020-09-11 3:25 pm, Claire Meyer wrote:
Hi,
I've got a problem with a tie not appearing. My problematic bar is as
follows :
upperHighB = \relative c'' {
d8 bes |
}
Try forcing the Tie downwards:
... ...
-- Aaron Hill
On 2020-07-23 4:38 pm, Aaron Hill wrote:
On 2020-07-23 3:14 pm, Lukas-Fabian Moser wrote:
Hi,
consider:
\version "2.21.0"
\relative {
g'1~ \break
g^"normal tie"
}
\relative {
ges'1~ \break
ges^"low tie"
}
\relative {
gis'1~ \break
gis^"low tie"
}
I understand why the tie at
On 2020-07-23 3:14 pm, Lukas-Fabian Moser wrote:
Hi,
consider:
\version "2.21.0"
\relative {
g'1~ \break
g^"normal tie"
}
\relative {
ges'1~ \break
ges^"low tie"
}
\relative {
gis'1~ \break
gis^"low tie"
}
I understand why the tie at the beginning of the second system of eac
Hi Andrew,
did it help?
Cheers,
Har,
Am So., 19. Juli 2020 um 11:12 Uhr schrieb Thomas Morley
:
>
> Am So., 19. Juli 2020 um 10:38 Uhr schrieb Kevin Barry :
> >
> > On Sun, 2020-07-19 at 18:08 +1000, Andrew Bernard wrote:
> > > What is this error really about? Is there any way to perform a
> >
Am So., 19. Juli 2020 um 10:38 Uhr schrieb Kevin Barry :
>
> On Sun, 2020-07-19 at 18:08 +1000, Andrew Bernard wrote:
> > What is this error really about? Is there any way to perform a
> > textual
> > search to pin it down?
>
> The error occurs when LilyPond tries to find the points to attach a tie
On Sun, 2020-07-19 at 18:08 +1000, Andrew Bernard wrote:
> What is this error really about? Is there any way to perform a
> textual
> search to pin it down?
The error occurs when LilyPond tries to find the points to attach a tie
to and can't find a notehead. The two situations in which this might
Yes. The binary chop. Will take a week. A disappointing outcome.
Why can't lilypond report the (even approximate) location?
What is this error really about? Is there any way to perform a textual
search to pin it down?
Andrew
On 19/07/2020 5:28 pm, Kevin Barry wrote:
I think you will unfor
> Any clues on how to find out the source location of this error?
>
I think you will unfortunately have to try finding it the old fashioned
way: comment out half your score or so and rerun and see if the error
still appears. Repeat until you've narrowed it down sufficiently to find
the ties in the
Yes it does, thank you Kevin!
Cheers,
Pierre
Le ven. 22 mai 2020 à 09:21, Kevin Barry a écrit :
> On Fri, 2020-05-22 at 07:16 +0200, Pierre Perol-Schneider wrote:
> > Hi,
> > I'm using Abraham's function: http://lsr.di.unimi.it/LSR/Item?id=1028
> > However, the overrides are killed by the shape
On Fri, 2020-05-22 at 07:16 +0200, Pierre Perol-Schneider wrote:
> Hi,
> I'm using Abraham's function: http://lsr.di.unimi.it/LSR/Item?id=1028
> However, the overrides are killed by the shape adjustment:
>
> Any idea how to avoid that?
> TIA, cheers,
> Pierre
Hi Pierre,
Does this solve the probl
Dear Aaron, you wrote:
[]
> \pushToTag and \appendToTag only work on things that have an elements
> property. So that means this expression is valid but useless:
>
> \pushToTag #'here c' \tag #'here g'
I tried to search "Element property" and I found this:
http://lilypond.org/doc/v2
Dear Aaron...
> A \tag is not a location per se, but rather it marks the following bit
> of music with some identifier.
[.]
Thanks a lot for your examples, now it's perfectly clear!
I post here some other examples inspired by your code. I did my best to
write the easiest as possible examp
On 2019-11-22 12:49 pm, Gianmaria Lari wrote:
Your code surprise me, so probably I didn't understand how tag do work.
I thought that this
\pushToTag #'here c' \tag #'here { g' }
would be 'converted' to
c' { g' }
[ . . . ]
Could you please give me some hints?
In part, I think the \tag being n
On Fri, 22 Nov 2019 at 18:53, Aaron Hill wrote:
> On 2019-11-22 7:49 am, Gianmaria Lari wrote:
> > I tried (again) with PushToTag with no success. And I don't understand
> > why
> > it doesn't work. Here it is the code:
>
> \pushToTag and \appendToTag only work on things that have an elements
> p
On 2019-11-22 7:49 am, Gianmaria Lari wrote:
I tried (again) with PushToTag with no success. And I don't understand
why
it doesn't work. Here it is the code:
\pushToTag and \appendToTag only work on things that have an elements
property. So that means this expression is valid but useless:
I tried (again) with PushToTag with no success. And I don't understand why
it doesn't work. Here it is the code:
\version "2.21.00"
\tagGroup #'(screenOut midiOut)
nc = {\tag #'midiOut\tag #'tieTag {} \tag #'screenOut c' }
myScore = {\pushToTag #'tieTag ~ \nc \nc}
\keepWithTag #'screenOut \myS
Hello Aaron,
made some tests and I discovered where are the issues.
Here is our working code (just a bit simplified):
\version "2.21.0"
\tagGroup #'(screenOut midiOut)
nc = {\tag #'midiOut\tag #'screenOut c' }
myScore = {\nc << \nc <>~ >> \nc}
\keepWithTag #'screenOut \myScore
\keepWithTag #'
Ciao Aaron, you wrote:
> > Here's something you can do in 2.19.83:
> >
> >
> > \version "2.19.83"
> >
> > \tagGroup #'(screenOut midiOut)
> > nc = {\tag #'midiOut \tag #'screenOut c' }
> > nd = {\tag #'midiOut \tag #'screenOut d' }
> > myScore = {\nc \nd \nc << \nd s~ >> \nd}
> >
On 2019-11-21 3:58 pm, Aaron Hill wrote:
Here's something you can do in 2.19.83:
\version "2.19.83"
\tagGroup #'(screenOut midiOut)
nc = {\tag #'midiOut \tag #'screenOut c' }
nd = {\tag #'midiOut \tag #'screenOut d' }
myScore = {\nc \nd \nc << \nd s~ >> \nd}
\score {\keepWithTa
On 2019-11-21 3:11 pm, Gianmaria Lari wrote:
Consider this situation:
\version "2.21.00"
\tagGroup #'(screenOut midiOut)
nc = {\tag #'midiOut \tag #'screenOut c' }
nd = {\tag #'midiOut \tag #'screenOut d' }
myScore = {\nc \nd \nc \nd~\nd}
\score {\keepWithTag #'screenOut \myScore \la
Consider this situation:
\version "2.21.00"
\tagGroup #'(screenOut midiOut)
nc = {\tag #'midiOut \tag #'screenOut c' }
nd = {\tag #'midiOut \tag #'screenOut d' }
myScore = {\nc \nd \nc \nd~\nd}
\score {\keepWithTag #'screenOut \myScore \layout{}}
\score {\keepWithTag #'midiOut \mySco
On Thu, Nov 21, 2019, 5:35 PM David Kastrup wrote:
> Gianmaria Lari writes:
>
> > I would expect this code
> >
> >
> > \version "2.21.00"
> > test = {\tag #'first c'
> > \tag #'second e'}
> > \keepWithTag #'first {\test~\test}
> > \keepWithTag #'second {\test~\test}
> >
> > ... generates
Gianmaria Lari writes:
> I would expect this code
>
>
> \version "2.21.00"
> test = {\tag #'first c'
> \tag #'second e'}
> \keepWithTag #'first {\test~\test}
> \keepWithTag #'second {\test~\test}
>
> ... generates two scores
>
> c~c
>
> and
>
> e~e
>
> but it doesn't! It generates
>
> c c
On 2019-11-13 3:37 am, Gianmaria Lari wrote:
Ciao Aaron,
[]
And you can use tags if you need the tie to be conditional:
\version "2.19.83"
multipleVoiceConditionalTie = \fixed c' {
<< { g4 \tag #'tie a~ \tag #'noTie a } \\ { e2 } >>
}
Yes, I didn't forget tags; but to me they
Ciao Aaron,
[]
> And you can use tags if you need the tie to be conditional:
>
>
> \version "2.19.83"
>
> multipleVoiceConditionalTie = \fixed c' {
><< { g4 \tag #'tie a~ \tag #'noTie a } \\ { e2 } >>
> }
>
Yes, I didn't forget tags; but to me they are syntactically difficult to
use
Ciao Harm,
P.S. My apologies if I included the images in the email and not attached it
> it's for clarity. Please let me know if you lilypond email users always
> prefer to attach images at the end of the messages.
>
> Please always attach and use plain text ;)
>
Well, I saw my beard well grown
On 2019-11-13 2:37 am, Aaron Hill wrote:
On 2019-11-13 2:16 am, Gianmaria Lari wrote:
Probably it doesn't exist a simple solution and the best would to keep
the last measure outside the variable.
Embedding the tie within the variable seems to work:
\version "2.19.83"
multipleVoiceWithUn
Am Mi., 13. Nov. 2019 um 11:17 Uhr schrieb Gianmaria Lari <
gianmarial...@gmail.com>:
P.S. My apologies if I included the images in the email and not attached it
it's for clarity. Please let me know if you lilypond email users always
prefer to attach images at the end of the messages.
Please alway
On 2019-11-13 2:16 am, Gianmaria Lari wrote:
Probably it doesn't exist a simple solution and the best would to keep
the last measure outside the variable.
Embedding the tie within the variable seems to work:
\version "2.19.83"
multipleVoiceWithUnterimnatedTie = \fixed c' {
<< { g4 a~ }
Michael you gave me the solution! Or at least you gave me the solution for
my simple example. The following works!
\version "2.21.0"
pa = {<< {e'1*~*}\\{c'1*~*}>>}
{ \pa \pa }
Now I have to try in my real file code but I don't see any reason why it
should not work
Thank you!
g.
On Wed, 13
On Wed, 13 Nov 2019 at 10:01, Michael Käppler wrote:
> Hi Gianmaria,
> Interesting, for me running 2.19.80 the first example does not compile,
> either.
>
Yes, I vaguely remember that version 2.21 manage differently ties/variable.
And probably that was the reason why I decided to use it :)
> W
Hi Gianmaria,
Interesting, for me running 2.19.80 the first example does not compile,
either.
Was there a recent change regarding post-event handling?
The problem is that the tie is not a separate expression that you could
concatenate with other
musical expressions like
bla = { e'1 }
foo = { ~
Stefano & Andrew:
Thank you for the solution and explanation.
Thanks,Ming.
On Saturday, May 18, 2019, 11:00:41 a.m. EDT, Stefano Troncaro
wrote:
Hi Ming, it depends on the music you are working with and your preference. I
personally have it set to ##t as my personal default. I don't s
Hi Ming, it depends on the music you are working with and your preference.
I personally have it set to ##t as my personal default. I don't see the
downside to having it turned on: if this happens often in your music it's
cumbersome to keep setting and resetting it, and I also find that it helps
to
Andrew:
Thank you very much.
Once the tieWaitForNote = ##t is set, it continues to work. Is this the
intention? Is it necessary to reset to it's default?
Thanks,Ming
On Thursday, May 16, 2019, 7:41:14 p.m. EDT, Andrew Bernard
wrote:
Hi Ming,
\set tieWaitForNote = ##t
It's in the Nota
Hi Ming,
\set tieWaitForNote = ##t
It's in the Notation Reference manual.
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On 1/21/19, Gianmaria Lari wrote:
> Is there any simple way to tie the last note contained in a variable?
> Here it is an example (that doesn't work).
It doesn’t work _yet_, but it will with the upcoming 2.21 release.
(You may already build a pre-release from the source code, but it’s a
bit techn
David Kastrup writes:
> Andrew Bernard writes:
[...]
>> Is this a mistake in the manual for the name?
>
> Yes and no.
>
> dak@lola:/usr/local/tmp/lilypond$ git grep min-length
> Documentation/included/font-table.ly: (define (min-length lst n)
> Documentation/included/font-table.ly:(1+ (m
Andrew, you wrote 18/01/2019 14:19:08
Subject: Tie minimum length
The NR for 2.19.82 in section 3.2.128 'tie interface' states:
I think you mean the IR.
min-length
If the tie is shorter than this amount (in staff-spaces) an
increasingly large length penalty is incurred.
But if I use thi
Andrew Bernard writes:
> The NR for 2.19.82 in section 3.2.128 'tie interface' states:
>
> min-length
> If the tie is shorter than this amount (in staff-spaces) an increasingly
> large length penalty is incurred.
>
> But if I use this an error is thrown. Using minimum-length works fine.
>
> warni
Timothy,
Thank you, exactly what I wanted.
Mark
-Original Message-
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Timothy Lanfear
Sent: Sunday, December 23, 2018 2:07 PM
To: lilypond-user@gnu.org
Subject: Re: tie across voices
On 23/12/2018
Jay,
Beautiful, and it preserves the voice leading!
Thank you!
Mark
From: Jay Anderson [mailto:horndud...@gmail.com]
Sent: Sunday, December 23, 2018 3:11 PM
To: Mark Stephen Mrotek
Cc: lilypond-user
Subject: Re: tie across voices
On Sun, Dec 23, 2018 at 2:40 PM Mark Stephen
On Sun, Dec 23, 2018 at 2:40 PM Mark Stephen Mrotek
wrote:
> Please see attached snippet.
>
> In measure 3 the two e flats should be tied.
>
> I have looked at using transparent as given in
>
> http://lsr.di.unimi.it/LSR/Snippet?id=8
>
> yet that would “collide” with the quarter rest.
>
My favor
On 23/12/2018 21:35, Mark Stephen Mrotek wrote:
Hello,
Please see attached snippet.
In measure 3 the two e flats should be tied.
I have looked at using transparent as given in
http://lsr.di.unimi.it/LSR/Snippet?id=8
yet that would “collide” with the quarter rest.
Any suggestions would be g
On 2018-12-23 1:35 pm, Mark Stephen Mrotek wrote:
In measure 3 the two e flats should be tied.
I have looked at using transparent as given in
http://lsr.di.unimi.it/LSR/Snippet?id=8
yet that would "collide" with the quarter rest.
Any suggestions would be greatly appreciated.
It's not perfec
Ethan Sue
Suggestion here
http://lilypond.org/doc/v2.19/Documentation/notation/expressive-marks-attached-to-notes
Scroll down to “delayed turn.”
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of Ethan Sue
Sent: Monday, November 19, 2018
A simple image could also help...
Cheers,
Pierre
Le lun. 19 nov. 2018 à 23:46, Andrew Bernard a
écrit :
> Hi, MWE please. Then much easier to demonstrate in your context.
>
> Andrew
>
>
> On Tue, 20 Nov 2018 at 08:40, Ethan Sue wrote:
>
>> I am trying to write something in lilypond and came acr
Hi, MWE please. Then much easier to demonstrate in your context.
Andrew
On Tue, 20 Nov 2018 at 08:40, Ethan Sue wrote:
> I am trying to write something in lilypond and came across this part that
> I can't figure out how to notate.
> What I would like to make is D1 with a prallmordent and then
Great! Thank you very much Harm,
Cheers,
Pierre
Le ven. 26 oct. 2018 à 16:13, Thomas Morley a
écrit :
> Am Fr., 26. Okt. 2018 um 15:41 Uhr schrieb Pierre Perol-Schneider
> :
> >
> > Hi,
> > Please consider the following example:
> >
> > %%
> > \version "2.19.82"
> > music =
> > \fixed c' {
> >
Am Fr., 26. Okt. 2018 um 15:41 Uhr schrieb Pierre Perol-Schneider
:
>
> Hi,
> Please consider the following example:
>
> %%
> \version "2.19.82"
> music =
> \fixed c' {
> \time 3/8
> \voiceOne
> 4. q
> }
> { \music } { \music } { \music }
> %%
>
> After trying several compilation, sometimes t
It works! Thank you Aaron!
g.
On Fri, 5 Oct 2018 at 11:08, Aaron Hill wrote:
> On 2018-10-05 2:03 am, Gianmaria Lari wrote:
> > I have the following code
> >
> > \version "2.19.82"
> > \fixed c' {
> > a1~
> > \set Score.repeatCommands = #'((volta "1")) a2 b2 \set
> > Score.repeatCommands = #
On 2018-10-05 2:03 am, Gianmaria Lari wrote:
I have the following code
\version "2.19.82"
\fixed c' {
a1~
\set Score.repeatCommands = #'((volta "1")) a2 b2 \set
Score.repeatCommands = #'((volta #f))
\set Score.repeatCommands = #'((volta "2")) a1^"Fine" \set
Score.repeatCommands = #'((volta
David Kastrup wrote
> Can be a memory-order thing. When two things compare equal, their final
> order of decisions can depend just on which choice happened to get a
> location lower in memory. In that case, the results need not even be
> deterministic given identical scores on the same platform w
Torsten Hämmerle writes:
> Thomas Morley-2 wrote
>> I already thought creating a function for setting tie-direction, _iff_
>> the notes are on the middle line, probably taking stem-direction into
>> account. It would give me more flexibility, though ofcourse the
>> considerations mentioned above
Thomas Morley-2 wrote
> I already thought creating a function for setting tie-direction, _iff_
> the notes are on the middle line, probably taking stem-direction into
> account. It would give me more flexibility, though ofcourse the
> considerations mentioned above are still valid.
Actually, the C
2018-07-27 1:02 GMT+02:00 Torsten Hämmerle :
> Simon Albrecht-2 wrote
>> The most sensible solution to me seems to be for Tie to use the
>> neutral-direction property and heed it in such cases, overriding the
>> direction if it is set.
>
> Using Harm's example, setting Tie.neutral-direction to #DOW
Simon Albrecht-2 wrote
> The most sensible solution to me seems to be for Tie to use the
> neutral-direction property and heed it in such cases, overriding the
> direction if it is set.
Using Harm's example, setting Tie.neutral-direction to #DOWN will just flip
everything around.
Then, the first
The most sensible solution to me seems to be for Tie to use the
neutral-direction property and heed it in such cases, overriding the
direction if it is set.
Best, Simon
On 26.07.2018 13:34, Robert Schmaus wrote:
Might be the same thing as here:
http://lilypond.1069038.n5.nabble.com/Curious-
Might be the same thing as here:
http://lilypond.1069038.n5.nabble.com/Curious-thing-about-ties-td196616.html
> On 26 Jul 2018, at 12:37, Thomas Morley wrote:
>
> Hi,
>
> please consider the following example:
>
> \version "2.19.82"
>
> \relative c'' {
> f,1
> r4 b~ b8 a b4~
> b8 a b2.
>
David Sumbler writes:
> The automatic creation of contexts is obviously very useful, especially
> when one is just a beginner at Lilypond. But I almost wish that there
> were an option to turn it off, which would be useful for forcing
> oneself to understand how this all actually works!
If ther
On Fri, 2018-05-04 at 23:55 +0200, Simon Albrecht wrote:
> On 04.05.2018 19:23, David Sumbler wrote:
> >
> > It seems that if, in a
> > <<{\musicA} {\musicB}>>
> > passage, \musicA does not specify a new Voice, then the music
> > before
> > the << >> passage and, importantly, also the music afterw
1 - 100 of 405 matches
Mail list logo
