lilypond-user
[Top][All Lists]
Advanced

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

Re: tie problem


From: Mats Bengtsson
Subject: Re: tie problem
Date: Sun, 17 Sep 2006 21:14:39 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20060628 Debian/1.7.8-1sarge7.1

Note that this already is described fairly clearly both in
"Basic Polyphony" and "Explicitly Instantiating Voices".
However, if you have any idea on how to make it even
clearer/easier to find, then they are off course welcome.

Graham Percival wrote:

Hi Rainer,

Fell free to help.  See
http://lilypond.org/web/devel/participating/documentation-adding

- Graham


Rainer Hahnekamp wrote:

Hi Kieren,

thank you very much vor answer. Your snippet solved the problem and btw. it
makes completely sense. Should really be better integrated into the
documentation.

Greetings,
Rainer

Kieren MacMillan wrote:

Hi, Rainer:

I've following code:
<c d g>1\arpeggio ~ | << <c d g>1\fermata \\ {r2 r4 b'32 (c d e f g
a b)} >>

According to the documentation the two "<c d g>" should be tied.
Unfortunately this is not the case. Could you help me please?

Well, you've run into a subtlety of Lilypond that could, perhaps, be
better documented...  ;-)

Consider the following code snippet:

%%% BEGIN SNIPPET %%%

\version "2.9.17"

\paper
{
indent = 0\in
line-width = 3\in
}

theMusic = \relative c'
{
<c d g>1 ~ | << <c d g>1\fermata \\ { s2 c4 c } >>  \break
<c d g>1 ~ | << { <c d g>1\fermata } \new Voice { s2 c4 c } >>
}

\score
{
\theMusic
}

%%% END SNIPPET %%%

Notice that the tie does not work "as expected" in the first example,
but does in the second.

This is because, in the first example, the << \\ >> construct
explicitly instantiates TWO voices, BOTH of which are in addition to
the one which contains the <c d g> that starts the tie -- as a
result, the tie doesn't know where to end, because its Voice doesn't
continue on into the <<>> block.

In the second example, the \\ is replaced by an explicit (manual)
instantiation using \new Voice -- this ensures that anything before
the \new Voice command is considered part of the Voice that existed
before the <<>> block began, and so the tie knows where to terminate.

Does that make sense?
Or, at the very least, does it explain why you're seeing what you're
seeing?  =)

Best regards,
Kieren.





_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user




_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user



--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================





reply via email to

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