lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Maybe a bug with slurs


From: Павел
Subject: Re: Maybe a bug with slurs
Date: Sun, 7 Jun 2020 14:27:25 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1

Small clause: you said "e'4) is essentially the same as <e'>4)". But according to your explanation it is essentially the different as <e'>4), but in most practical cases they behave same.

07.06.2020 14:16, Павел пишет:
Thank you for deep explanation!

Yes, this is complicated way but it can be useful in some cases.

07.06.2020 12:25, David Kastrup пишет:
Павел <budanov.pavel@gmail.com> writes:

See these two examples. They are almost same except angle brackets. In
first example slur behaves correctly, but in second does not.

\version "2.20.0"
{
     \new Voice = "first" { g'8 f'( }
     \context Voice = "first" << <e')>4 <b b'> >>
     \new Voice = "second" { g'8 f'( }
     \context Voice = "second" << e'4) <b b'> >>
}
I disagree with that assessment.  Yours is just a complicated way of
writing

\version "2.20.0"
{
     \new Voice = "first" { g'8 f'( <e') b b'>4 }
     \new Voice = "second" { g'8 f'( <e' b b'>4) }
}

<< >> places constructs in parallel, here into the same Voice.  The
first line uses an in-chord slur ending which is drawn to a specific
note head, the second line uses a per-Voice slur ending which is drawn
to the whole chord.  e'4) is essentially the same as <e'>4) .




reply via email to

[Prev in Thread] Current Thread [Next in Thread]