Re: what's the error?

2018-02-19 Thread David Kastrup 
"Mark Stephen Mrotek"  writes:

> David Kastrup [mailto:d...@gnu.org]  wrote:
>>
>>
>> \once \set sets tieWaitForNote once at the current point of time.
>> That means it will be active for the first grace note but not for the
>> others.  Consequently it's inactive for d~ which is still followed by
>> another grace note before the ties are resolved.
>
>
> David,
>
> Thank you for the explanation.

Well, as noticed elsewhere in this thread, this does not fully explain
the whole behavior.  It would appear that tieWaitForNote has to stay set
until the tie is resolved or the tie will get flushed out.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: what's the error?

2018-02-19 Thread Mark Stephen Mrotek 
David,

Thank you for the explanation.

Mark

-Original Message-
From: David Kastrup [mailto:d...@gnu.org] 
Sent: Monday, February 19, 2018 12:38 AM
To: Mark Stephen Mrotek <carsonm...@ca.rr.com>
Cc: 'lilypond-user' <lilypond-user@gnu.org>
Subject: Re: what's the error?

"Mark Stephen Mrotek" <carsonm...@ca.rr.com> writes:

> Hello,
>
>  
>
> See the attachment for what I want.
>
>  
>
> This is what I code:
>
>  
>
> \relative c'' {
>
> <<{bes8 [a]}\\{
>
> \once \set tieWaitForNote = ##t
>
> \grace {c,8~ d~ fis~} 4}>>
>
> }
>
>  
>
> The error message is "unterminated tie."
>
>  
>
> Someone have a keener eye than I?

\once \set sets tieWaitForNote once at the current point of time.  That
means it will be active for the first grace note but not for the others.
Consequently it's inactive for d~ which is still followed by another grace
note before the ties are resolved.

--
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: what's the error?

2018-02-19 Thread David Kastrup 
Mats Bengtsson  writes:

> On 2018-02-19 09:38, David Kastrup wrote:
>>
>> \once \set sets tieWaitForNote once at the current point of time.  That
>> means it will be active for the first grace note but not for the
>> others.  Consequently it's inactive for d~ which is still followed by
>> another grace note before the ties are resolved.
> Just curious, why doesn't tieWaitForNote apply even for the first
> grace note? The warning is issued both for c8~ and d~ in this example
>
> \version "2.19.80"
>
> \relative c' \new Voice {
>   \once \set tieWaitForNote = ##t
>   \grace {c8~ d~ fis~} 4
> }

Tie_engraver consults tieWaitForNote in two places: at
start_translation_timestep when it otherwise flushes out and warns about
unterminated ties from notes having exceeded their duration, and in
process_acknowledged where it uses it several times.  It doesn't buffer
it in any way, and it also warns and flushes stuff in the
process_acknowledged routine.  So it's entirely possible that you need
tieWaitForNote set until the tie has been finally connected or it will
get flushed out.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Re: what's the error?

2018-02-19 Thread Mats Bengtsson 



On 2018-02-19 09:38, David Kastrup wrote:


\once \set sets tieWaitForNote once at the current point of time.  That
means it will be active for the first grace note but not for the
others.  Consequently it's inactive for d~ which is still followed by
another grace note before the ties are resolved.
Just curious, why doesn't tieWaitForNote apply even for the first grace 
note? The warning is issued both for c8~ and d~ in this example


\version "2.19.80"

\relative c' \new Voice {
  \once \set tieWaitForNote = ##t
  \grace {c8~ d~ fis~} 4
}

    /Mats


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: what's the error?

2018-02-19 Thread David Kastrup 
"Mark Stephen Mrotek"  writes:

> Hello,
>
>  
>
> See the attachment for what I want.
>
>  
>
> This is what I code:
>
>  
>
> \relative c'' {
>
> <<{bes8 [a]}\\{
>
> \once \set tieWaitForNote = ##t
>
> \grace {c,8~ d~ fis~} 4}>>
>
> }
>
>  
>
> The error message is "unterminated tie."
>
>  
>
> Someone have a keener eye than I?

\once \set sets tieWaitForNote once at the current point of time.  That
means it will be active for the first grace note but not for the
others.  Consequently it's inactive for d~ which is still followed by
another grace note before the ties are resolved.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: what's the error?

2018-02-18 Thread Mark Stephen Mrotek 
Ben,

 

Thanks for the solution!

 

Mark

 

From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] 
On Behalf Of Ben
Sent: Sunday, February 18, 2018 7:38 PM
To: lilypond-user@gnu.org
Subject: Re: what's the error?

 

On 2/18/2018 10:28 PM, Mark Stephen Mrotek wrote:



Hello,

 

See the attachment for what I want.

 

This is what I code:

 

\relative c'' {

<<{bes8 [a]}\\{

\once \set tieWaitForNote = ##t

\grace {c,8~ d~ fis~} 4}>>

}

 

The error message is “unterminated tie.”

 

Someone have a keener eye than I?

 

Thank you.

 

Mark

 


Hi Mark,

Try this -
Your code compiles if you remove the \once:

\version "2.19.80"

\relative c'' {

<<{bes8 [a]}\\{

   \set tieWaitForNote = ##t

\grace {c,8~ d~ fis~} 4}>>

}

Otherwise you'd have to rework a bit...

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: what's the error?

2018-02-18 Thread Ben 

On 2/18/2018 10:28 PM, Mark Stephen Mrotek wrote:


Hello,

See the attachment for what I want.

This is what I code:

\relative c'' {

<<{bes8 [a]}\\{

    \once \set tieWaitForNote = ##t

    \grace {c,8~ d~ fis~} 4}>>

}

The error message is “unterminated tie.”

Someone have a keener eye than I?

Thank you.

Mark




Hi Mark,

Try this -
Your code compiles if you remove the \once:

\version "2.19.80"

\relative c'' {

<<{bes8 [a]}\\{

   \set tieWaitForNote = ##t

    \grace {c,8~ d~ fis~} 4}>>

}

Otherwise you'd have to rework a bit...
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user