Phil, Jeremy -----Original Message----- From: Phil Holmes <[email protected]> Date: Wed, 9 Mar 2011 18:35:07 +0000 To: bug-lilypond <[email protected]> Subject: Re: \pitchedTrill causes warning when used with tie
>"Jeremy Crabtree" <[email protected]> wrote in message >news:[email protected]... >> 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, 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. James However, more importantly I can't understand the point of a tie while trilling. :) > _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
