bug-lilypond
[Top][All Lists]
Advanced

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

Re: \pitchedTrill causes warning when used with tie


From: Jeremy Crabtree
Subject: Re: \pitchedTrill causes warning when used with tie
Date: Wed, 9 Mar 2011 16:33:46 -0600

On Wed, Mar 9, 2011 at 2:05 PM, James Lowe <address@hidden> wrote:
> Phil, Jeremy
>
> -----Original Message-----
> From: Phil Holmes <address@hidden>
> Date: Wed, 9 Mar 2011 18:35:07 +0000
> To: bug-lilypond <address@hidden>
> Subject: Re: \pitchedTrill causes warning when used with tie
>
>>"Jeremy Crabtree" <address@hidden> wrote in message
>>news:address@hidden
>>> This code
>>>
>>> \relative c''
>>> {
>>> \pitchedTrill b1~\startTrillSpan c | b2.~ b8\stopTrillSpan r8
>>> }
>>>
>>> \version "2.13.51"
>>>
>>>
>>> Will result in:
>>>
>>> pitchedtrillbug.ly:3:17: warning: unterminated tie
>>> \pitchedTrill b1~
>>>                 \startTrillSpan c | b2.~ b8\stopTrillSpan r8
>>
>>Looks like you're trying to tie a b to a c, which you can't do.  Hence
>>the
>>error.  I've not tested this, but I'd guess the trill is irrelevant.

No, I'm trying to tie a b to another b to another b.  I'm also trying
to specify a whole-step trill between b and c.

>>
>
> No, but yes but no but..
>
> :)
>
> The 'pitched' trill (which is kinda like a 'grace' in parenthesis) is not
> considered 'part' of the tie so I guess you'd 'expect' this to work.
>
> So I can understand why this might confuse and the error is misleading.
>
> I could not get a tie to compile cleanly but I could get a slur to compile
> (and I think it looks better anyway as it rises above the pitch trill
> rather than clip the glyph - as the tie does).
>
> So if it helps to be rid of the warning
>
> \relative c''
> {
> \override TrillPitchAccidental #'avoid-slur = #'inside
> \pitchedTrill
> b1( \startTrillSpan c | b2.)~ b8\stopTrillSpan r8
> }
>
>
> Will do what you need. If you try using a slur instead of a tie the
> compile message is actually helpful (and even gives you the grob to use).
>
> I don't know how to tell LilyPond that the 'c' is not what you want to tie
> the 'b' to but tie it to the *next* note. I am not sure that is trivial.

I hadn't picked up that Lilypond was trying to tie to the c.  I was
thinking of the c as merely the second argument to \pitchedTrill. to
me it would make sense to have something like \pitchedTrillSpan that
would work like the \startTrillSpan, but allow specifying the pitch,
so my example would become

b1~\pitchedTrillSpan c | b2.~ b8\stopTrillSpan r8

To my mind the second pitch, c, is a decoration/markup applied to the
first.  I first looked for a simple way to just \markup the note into
the part, but I found \pitchedTrill and thought that might be the more
proper approach


> However, more importantly I can't understand the point of a tie while
> trilling. :)

Well, given that I'm playing a wind instrument (Saxophone), there is a
distinct difference between tonguing the second b and not.  It would
be a very audible pulse in the middle of the note.



reply via email to

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