> Le 27 juil. 2022 à 10:41, Thomas Morley a écrit :
>
> Am Di., 26. Juli 2022 um 11:48 Uhr schrieb Thomas Morley
> :
>>
>>> Am Sa., 23. Juli 2022 um 19:15 Uhr schrieb Jean Abou Samra
>>> :
>>>
>>>
>>>
>>> Le 23/07/2022 à 12:49, Lukas-Fabian Moser a écrit :
Hi Andrew,
On 2022-07-27 1:41 am, Thomas Morley wrote:
I stumbled across a certain condition. In tie-column::add_tie there is
(> (car (ly:grob-spanned-column-rank-interval
tie-column))
(car (ly:grob-spanned-column-rank-interval
tie-column)))
How could this ever be true?
L
Am Di., 26. Juli 2022 um 11:48 Uhr schrieb Thomas Morley
:
>
> Am Sa., 23. Juli 2022 um 19:15 Uhr schrieb Jean Abou Samra
> :
> >
> >
> >
> > Le 23/07/2022 à 12:49, Lukas-Fabian Moser a écrit :
> > >
> > > Hi Andrew,
> > >
> > > Am 23.07.22 um 03:49 schrieb Andrew Bernard:
> > >> I know that we ca
Am Sa., 23. Juli 2022 um 19:15 Uhr schrieb Jean Abou Samra :
>
>
>
> Le 23/07/2022 à 12:49, Lukas-Fabian Moser a écrit :
> >
> > Hi Andrew,
> >
> > Am 23.07.22 um 03:49 schrieb Andrew Bernard:
> >> I know that we can't natively make ties between notes in different
> >> voices. I know that there was
Andrew, did you get a chance to try Lukas-Fabian's extension yet? Was it
working for you or were there something wrong?
-William
On 7/23/22 18:03, Andrew Bernard wrote:
Gosh. There's no 'smell'. In piano music that has polyphony it is very
common, and indeed necessary to tie across voices. Do
Gosh. There's no 'smell'. In piano music that has polyphony it is very
common, and indeed necessary to tie across voices. Dorico enables it
with ease (and if it did not make sense, I can assure you Dorico which
is heavily rule bound would not allow it). Lilypond cannot do it
natively. This is
This is a good question, Stephan. I think it can be explained that when
talking about keyboard music, even though there are abstract ideas of
things like melody from playing one note after the previous, and other
things such as chords, engraving techniques such as including many
noteheads on on
Le 23/07/2022 à 19:14, Jean Abou Samra a écrit :
to =
#(define-music-function (ctx mus) (symbol? ly:music?)
(make-music 'ContextExclusiveMusic 'target ctx 'element mus))
P.S. With some parser fiddling (and at the cost of making \to a
reserved identifier), it should be possible to give \to a
Hi all
I'm neither a professional engraver nor composer. But I've already tried
to copy scores for my own use.
That's where I got in touch with many "creative" engraving situations.
One might ask how one could engrave something a manual engraver did 100
years ago. And then we have this fantastic
Le 23/07/2022 à 12:49, Lukas-Fabian Moser a écrit :
Hi Andrew,
Am 23.07.22 um 03:49 schrieb Andrew Bernard:
I know that we can't natively make ties between notes in different
voices. I know that there was a Google Summer of Code task that could
not be completed.
A few weeks ago, I sent y
I second Kieren's sentiment, thanks for this extension Lukas-Fabian.
I'll remember this extension if the need for it pops up!
-William
On 7/23/22 06:49, Lukas-Fabian Moser wrote:
Hi Andrew,
Am 23.07.22 um 03:49 schrieb Andrew Bernard:
I know that we can't natively make ties between notes in d
Hi Lukas!
As someone who writes/engraves a LOT of keyboard music: THANK YOU!!
Excited that there might even be a Slur version in the [near] future.
Best,
Kieren.
Hi Andrew,
Am 23.07.22 um 03:49 schrieb Andrew Bernard:
I know that we can't natively make ties between notes in different
voices. I know that there was a Google Summer of Code task that could
not be completed.
A few weeks ago, I sent you the following privately (I was too timid to
post in o
I was just asking. It is possible to do open source to an agreed
roadmap, but that's not how it is for LilyPond, so now I know.
On 23/07/2022 4:42 pm, Jean Abou Samra wrote:
Le 23/07/2022 à 08:11, Andrew Bernard a écrit :
I thought there may be a roadmap that contributors create? Or is
curren
Le 23/07/2022 à 08:11, Andrew Bernard a écrit :
I thought there may be a roadmap that contributors create? Or is
current development just more or less ad hoc?
Like most community-driven free software projects, LilyPond is
developed as a hobby by contributors who do that each for their
own reas
I thought there may be a roadmap that contributors create? Or is current
development just more or less ad hoc?
I am aware that it is currently a difficult problem, as I said.
On 23/07/2022 4:04 pm, Jean Abou Samra wrote:
It's not possible to answer your question, as most
plans to develop fun
Le 23/07/2022 à 03:49, Andrew Bernard a écrit :
I know that we can't natively make ties between notes in different
voices. I know that there was a Google Summer of Code task that could
not be completed.
This is such a critical feature for keyboard music. When there are
hundreds of such ties i
Hey Andrew, this might not help but did you try the technique in this
snippet?
https://lists.gnu.org/archive/html/bug-lilypond/2012-03/msg00663.html
Just found this while looking around for people discussing slurs across
voices previously.
(pasted from url incase website is dead)
Snip
I know that we can't natively make ties between notes in different
voices. I know that there was a Google Summer of Code task that could
not be completed.
This is such a critical feature for keyboard music. When there are
hundreds of such ties in major pieces, it is just too tedious to do all
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 s
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/msg
> 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-d
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.
Hi Carl,
I think you misunderstood. The \voices command does not let slurs go
across voices. Rather, it allows existing voices to go into the << \\
>> polyphony expression.
Previously (and still, if you don't use the \voices command), << \\ >>
created two temporary voices, neither one relat
elinsky
> Sent: Tuesday, June 30, 2020 6:23 PM
> To: lilypond-user@gnu.org
> Subject: Re: ties between voices
>
> David Zelinsky writes:
>
> > I've done some reasonably complicated things in Lilypond, but still
> > have lots to learn. My current conundrum is to typ
David,
Thank you.
Mark
-Original Message-
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
David Zelinsky
Sent: Tuesday, June 30, 2020 7:32 PM
To: lilypond-user@gnu.org
Subject: Re: ties between voices
"Mark Stephen Mrotek" writes
On Tue, Jun 30, 2020 at 8:32 PM David Zelinsky wrote:
>
> Here's where it says "Lyrics and spanners (such as slurs, ties,
> hairpins, etc.) cannot be created *across* voices.":
>
>
http://lilypond.org/doc/v2.20/Documentation/notation/multiple-voices#index-_005cvoices
>
> And here's where it says
"Mark Stephen Mrotek" writes:
> David Zelinsky writes:
>
>> I had seen "\voices" in the manual, but it did not say anything about
>> continuing phrasing or dynamics across voices. I fact it said it can't be
>> done. But after seeing people's responses, I looked further and found where
>> it ex
30, 2020 6:23 PM
To: lilypond-user@gnu.org
Subject: Re: ties between voices
David Zelinsky writes:
> I've done some reasonably complicated things in Lilypond, but still
> have lots to learn. My current conundrum is to typeset the attached
snippet.
> I can't figure out how t
David Zelinsky writes:
> I've done some reasonably complicated things in Lilypond, but still have
> lots to learn. My current conundrum is to typeset the attached snippet.
> I can't figure out how to get the tie between the G's, without breaking
> the double stops in the first measure into two s
On Mon, Jun 29, 2020 at 4:10 PM Trevor wrote:
>
> Hi Carl
>
> >This notation will greatly simplify some of the choral music I set in
> >the past year. I forgot about the discussion on the lists, and so
> >didn't use it even though it was available. Thanks for making it work
> >
> I always use t
Carl Sorensen writes:
> David,
>
> This notation will greatly simplify some of the choral music I set in
> the past year. I forgot about the discussion on the lists, and so
> didn't use it even though it was available. Thanks for making it work
>
> Aaron,
>
> I think this is a useful enough wr
Hi Carl
This notation will greatly simplify some of the choral music I set in
the past year. I forgot about the discussion on the lists, and so
didn't use it even though it was available. Thanks for making it work
I always use the satb.ly template for almost all of my choral music (see
A1 B
On Mon, Jun 29, 2020 at 3:44 PM David Kastrup wrote:
>
> Aaron Hill writes:
>
> > On 2020-06-29 2:17 pm, David Kastrup wrote:
> >> \voices 1,3,4,2 << \soprano \\ \alto \\ \tenor \\ \bass >>
> >> which is ugly enough as it is [...]
> >
> > Does not seem that ugly to me, but I suppose one could enc
Aaron Hill writes:
> On 2020-06-29 2:17 pm, David Kastrup wrote:
>> \voices 1,3,4,2 << \soprano \\ \alto \\ \tenor \\ \bass >>
>> which is ugly enough as it is [...]
>
> Does not seem that ugly to me, but I suppose one could encapsulate it
> via the ever-handy \etc:
>
>
> \version "2.20.0"
>
On 2020-06-29 2:17 pm, David Kastrup wrote:
\voices 1,3,4,2 << \soprano \\ \alto \\ \tenor \\ \bass >>
which is ugly enough as it is [...]
Does not seem that ugly to me, but I suppose one could encapsulate it
via the ever-handy \etc:
\version "2.20.0"
soprano = { c''4 }
alto = { a'4 }
Pierre Perol-Schneider writes:
> Le lun. 29 juin 2020 à 22:31, David Kastrup a écrit :
>
>>
>> Just keep most stuff in the main voice, like
>>
> ...
>
>> \voices "main", 2 << { g4 f\) } \\ a,2 >>
>
> ...
> WTF???
> 'just discovered that \voices is in the 2.20 learning manual...
> One word: bravo
Le lun. 29 juin 2020 à 22:31, David Kastrup a écrit :
>
> Just keep most stuff in the main voice, like
>
...
> \voices "main", 2 << { g4 f\) } \\ a,2 >>
...
WTF???
'just discovered that \voices is in the 2.20 learning manual...
One word: bravo.
Cheers,
Pierre
Sorry, forgot the list...
Lukas-Fabian Moser schrieb am Mo., 29. Juni 2020, 22:08:
> Hi David,
>
> I can't figure out how to get the tie between the G's, without breaking
>> the double stops in the first measure into two separate voices, and so
>> breaking their stems. Can someone show me how t
David Zelinsky writes:
> I've done some reasonably complicated things in Lilypond, but still have
> lots to learn. My current conundrum is to typeset the attached snippet.
> I can't figure out how to get the tie between the G's, without breaking
> the double stops in the first measure into two s
On Mon, 29 Jun 2020 at 21:37, David Zelinsky wrote:
>
> I've done some reasonably complicated things in Lilypond, but still have
> lots to learn. My current conundrum is to typeset the attached snippet.
> I can't figure out how to get the tie between the G's, without breaking
> the double stops i
I've done some reasonably complicated things in Lilypond, but still have
lots to learn. My current conundrum is to typeset the attached snippet.
I can't figure out how to get the tie between the G's, without breaking
the double stops in the first measure into two separate voices, and so
breaking t
On Sat, 07 Oct 2017 23:15:17 +0800 Thomas Morley
wrote
> > You could do \override TieColumn.positioning-done = ##t, but be aware,
> > using it means you are now responsible yourself for the Tie's
> > directions.
> > You tell LilyPond "Don't bother placing the Ties, I'll do"
>
> T
2017-10-07 17:08 GMT+02:00 Thomas Morley :
> 2017-10-07 16:40 GMT+02:00 James Harkins :
>> On Sat, 07 Oct 2017 20:49:31 +0800 Simon Albrecht
>> wrote
>>> On 07.10.2017 13:55, James Harkins wrote:
>>> > But, it's a chord where I want the lower tie to go down, and
>>> > the upper one to
2017-10-07 16:40 GMT+02:00 James Harkins :
> On Sat, 07 Oct 2017 20:49:31 +0800 Simon Albrecht
> wrote
>> On 07.10.2017 13:55, James Harkins wrote:
>> > But, it's a chord where I want the lower tie to go down, and
>> > the upper one to go up...
>>
>> Put the ties inside the chord:
>>
On Sat, 07 Oct 2017 20:49:31 +0800 Simon Albrecht
wrote
> On 07.10.2017 13:55, James Harkins wrote:
> > But, it's a chord where I want the lower tie to go down, and
> > the upper one to go up...
>
> Put the ties inside the chord:
>
Oh... I'm afraid I spoke too soon. The syn
On October 7, 2017 20:49:38 Simon Albrecht wrote:
On 07.10.2017 13:55, James Harkins wrote:
But, it's a chord where I want the lower tie to go down, and
the upper one to go up...
Put the ties inside the chord:
I'm binge watching Rick & Morty season 3, but this blows my mind even more
th
On 07.10.2017 13:55, James Harkins wrote:
But, it's a chord where I want the lower tie to go down, and
the upper one to go up...
Put the ties inside the chord:
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org
On October 7, 2017 14:52:06 Werner LEMBERG wrote:
Without looking at your example: Use `_~' and `^~' instead of `~' to
immediately specify a tie's direction.
Crikey, I knew about that for slurs, didn't think of it for ties.
But, it's a chord where I want the lower tie to go down, and the
> I've got one I can't quite get right. I would like the tie from the
> upper B whole note to be up instead of down. [...]
Without looking at your example: Use `_~' and `^~' instead of `~' to
immediately specify a tie's direction.
Werner
___
li
Continuing with this neat "\context Voice" trick -- quite powerful. I see how
it works: you have two expressions stuffing events into the same Voice context,
and LP merges them into one timed list and does the best it can to make sense
out of the tie properties.
I've got one I can't quite get r
A-ha, got it, it was a combination of Harm's trick plus a hidden note:
\new Score {
\new Staff {
\numericTimeSignature
<<
\new Voice = "a" \relative c' {
\voiceOne
\set tieWaitForNote = ##t
c16 g' ~ 8 ~ q2. ~
q2 ~ 2
}
\context Voice = "a"
> Probably:
>
> \new Score {
> \new Staff {
> \numericTimeSignature \time 2/4 % barline, so E must be tied
> <<
> \new Voice = "xy" \relative c' {
> \set tieWaitForNote = ##t
> 2~
> }
> \context Voice = "xy" \relative c' {
> s4 \voiceTwo f4 ~ 2
On Thu, Oct 5, 2017 at 3:56 AM, James Harkins wrote:
> I need a tie from the e in 2 (voice 1) to the e in 2 (voice 2).
>
> How to restructure this to make it possible?
This reminds me of last year's Google Summer of Code project.
http://lilypondblog.org/2016/08/google-summer-of-code-2016-cross-v
2017-10-05 10:56 GMT+02:00 James Harkins :
> Hi, been away for awhile.
>
> I'm now writing for khaen, a Thai mouth organ. Fascinating instrument.
> Notation is usually single-staff and heavily multi-voiced.
>
> One nut I never cracked in LilyPond: how to tie a note from one Voice to
> another, e.
Am 05.10.2017 um 10:56 schrieb James Harkins:
One nut I never cracked in LilyPond: how to tie a note from one Voice to
another, e.g.
Does LSR snippet 8 (http://lsr.di.unimi.it/LSR/Item?id=8) help?
___
lilypond-user mailing list
lilypond-user@gnu.o
Hi, been away for awhile.
I'm now writing for khaen, a Thai mouth organ. Fascinating instrument. Notation
is usually single-staff and heavily multi-voiced.
One nut I never cracked in LilyPond: how to tie a note from one Voice to
another, e.g.
\new Score {
\new Staff <<
\numericTimeSignat
- Original Message -
From: "Gerard"
To:
Sent: Friday, March 17, 2017 12:51 PM
Subject: How to get ties between voices
Dear All,
maybe you can help solving this problem.
I've attached a code with two examples.
Example 1 is the desired output, except for the missing ti
Dear All,
maybe you can help solving this problem.
I've attached a code with two examples.
Example 1 is the desired output, except for the missing ties in the
right hand of the last quarter.
Example 2 is an alternative. Now the ties are correct, but the beams
between right and left hand are spl
Steve D escreveu:
> As illustrated in Figure 1 (attached PNG), LilyPond's default placement
> of the tie between the top notes of chords 2 and 3 of the illustration
> is so short (to avoid the flat symbol on the 3rd chord) that it is
> invisible, unless the chords (and measures that contain the ch
On Tue, Jan 23, 2007 at 06:21:53PM -0700, Steve D wrote:
>
> Issue 3:
> I tried to manually configure the ties between the second and third
> chords using--
>
> 8~ \once \override Score.TieColumn #'tie-configuration =
> #'( (4 . 1) #t ) 4
>
> --However, as is illustrated in Figure 3 (attache
LilyPond 2.11.13, Linux
This message pertains to ties between single and multiple voice sections
of notation of polyphonic instruments, using a technique suggested by
Joe Neeman of moving the Tie_engraver from the default Voice context to
the Staff context instead.
A Goal
--
Piano (and presum
First, on Wed, Jan 17, 2007 at 08:15:24AM +0200, Joe Neeman wrote:
> We've had a few questions about ties between voices (especially ties from
> polyphony to chords). It seems that you can get this behaviour simply by
> moving the Tie_engraver form the Voice context to the Staff
Steve D escreveu:
> On Wed, Jan 17, 2007 at 08:15:24AM +0200, Joe Neeman wrote:
>> We've had a few questions about ties between voices (especially ties from
>> polyphony to chords). It seems that you can get this behaviour simply by
>> moving the Tie_engraver form the
On Wed, Jan 17, 2007 at 08:15:24AM +0200, Joe Neeman wrote:
> We've had a few questions about ties between voices (especially ties from
> polyphony to chords). It seems that you can get this behaviour simply by
> moving the Tie_engraver form the Voice context to the Staff context. N
On Wed, Jan 17, 2007 at 08:15:24AM +0200, Joe Neeman wrote:
> We've had a few questions about ties between voices (especially ties from
> polyphony to chords). It seems that you can get this behaviour simply by
> moving the Tie_engraver form the Voice context to the Staff context. N
We've had a few questions about ties between voices (especially ties from
polyphony to chords). It seems that you can get this behaviour simply by
moving the Tie_engraver form the Voice context to the Staff context. Note
that the Tie_engraver was probably designed to live in the Voice contex
67 matches
Mail list logo
