Thanks, David. I didn't know about exitnow. (Always a lot to learn.)

Note to Rory:
(Observation perhaps related to your OSC cleanup issue?)
When using exitnow in Lettuce from *commandline*, exit is clean with a 
single instance of this statement:
Early return from csoundPerformKsmps()

When executing as usual within Lettuce, exit is not clean and generates 
*two* instances of the above statement.
Also, closing Lettuce is not allowed; there is a popup informing "Please 
stop Csound first" - even though Csound doesn't *appear* to be running 
(green play icon is still displayed).

Art Hunkins

----- Original Message ----- 
From: "David Akbari" 
To: 
Sent: Wednesday, February 06, 2008 9:56 PM
Subject: [Csnd] Re: Re: Re: Re: Re: Re: "Abort" Command?


> Why don't you just use the "exitnow" opcode in your original if statement?
> http://csounds.com/manual/html/exitnow
>
> -David
>
> On Feb 6, 2008 5:17 AM, Art Hunkins  wrote:
>> Such "extra time before actual abort" is consistent with the performance 
>> of
>> "time" for the e statement:
>> "The first p-field time determines the extra time (in seconds) to be 
>> given
>> to the performance after the actual e statement takes effect."
>>
>> So, IMO, the "time" parameter does make sense with the event opcode 
>> (though
>> not in the context I am working with).
>>
>> Art Hunkins
>>
>> ----- Original Message -----
>> From: "Anthony Kozar" 
>> To: 
>>
>> Sent: Wednesday, February 06, 2008 12:16 AM
>> Subject: [Csnd] Re: Re: Re: Re: "Abort" Command?
>>
>>
>> > Note that the info in the manual about the optional "time" parameter to
>> > "e"
>> > is wrong.  It does not _add_ the specified amount of time to the end of
>> > the
>> > score, it _is_ the time of the end of the score (in beats, assuming 
>> > that
>> > "time" is later than the end of the last event).
>> >
>> > I corrected this for the next edition of the manual.
>> >
>> > Therefore, I am not sure how it makes sense to interpret this parameter
>> > with
>> > the "event" opcode.
>> >
>> > Anthony
>> >
>> > Art Hunkins wrote on 2/5/08 11:19 PM:
>> >
>> >> Developers:
>> >> I'd like to request that someone fix event for the "e" case. The
>> >> parameters
>> >> are different for (score event) e. The single and *optional* parameter
>> >> should be time (as with e). Unfortunately, this parameter (for event 
>> >> "e")
>> >> does not work to delay the "abort", so that currently "abort" is 
>> >> always
>> >> immediate.
>> >
>> >
>> >
>> > Send bugs reports to this list.
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>> > "unsubscribe
>> > csound"
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>> csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 

Thanks Art, I'll take a look...

Rory.


Art Hunkins wrote:
> Thanks, David. I didn't know about exitnow. (Always a lot to learn.)
> 
> Note to Rory:
> (Observation perhaps related to your OSC cleanup issue?)
> When using exitnow in Lettuce from *commandline*, exit is clean with a 
> single instance of this statement:
> Early return from csoundPerformKsmps()
> 
> When executing as usual within Lettuce, exit is not clean and generates 
> *two* instances of the above statement.
> Also, closing Lettuce is not allowed; there is a popup informing "Please 
> stop Csound first" - even though Csound doesn't *appear* to be running 
> (green play icon is still displayed).
> 
> Art Hunkins
> 
> ----- Original Message ----- From: "David Akbari" 
> To: 
> Sent: Wednesday, February 06, 2008 9:56 PM
> Subject: [Csnd] Re: Re: Re: Re: Re: Re: "Abort" Command?
> 
> 
>> Why don't you just use the "exitnow" opcode in your original if 
>> statement?
>> http://csounds.com/manual/html/exitnow
>>
>> -David
>>
>> On Feb 6, 2008 5:17 AM, Art Hunkins  wrote:
>>> Such "extra time before actual abort" is consistent with the 
>>> performance of
>>> "time" for the e statement:
>>> "The first p-field time determines the extra time (in seconds) to be 
>>> given
>>> to the performance after the actual e statement takes effect."
>>>
>>> So, IMO, the "time" parameter does make sense with the event opcode 
>>> (though
>>> not in the context I am working with).
>>>
>>> Art Hunkins
>>>
>>> ----- Original Message -----
>>> From: "Anthony Kozar" 
>>> To: 
>>>
>>> Sent: Wednesday, February 06, 2008 12:16 AM
>>> Subject: [Csnd] Re: Re: Re: Re: "Abort" Command?
>>>
>>>
>>> > Note that the info in the manual about the optional "time" 
>>> parameter to
>>> > "e"
>>> > is wrong.  It does not _add_ the specified amount of time to the 
>>> end of
>>> > the
>>> > score, it _is_ the time of the end of the score (in beats, assuming 
>>> > that
>>> > "time" is later than the end of the last event).
>>> >
>>> > I corrected this for the next edition of the manual.
>>> >
>>> > Therefore, I am not sure how it makes sense to interpret this 
>>> parameter
>>> > with
>>> > the "event" opcode.
>>> >
>>> > Anthony
>>> >
>>> > Art Hunkins wrote on 2/5/08 11:19 PM:
>>> >
>>> >> Developers:
>>> >> I'd like to request that someone fix event for the "e" case. The
>>> >> parameters
>>> >> are different for (score event) e. The single and *optional* 
>>> parameter
>>> >> should be time (as with e). Unfortunately, this parameter (for 
>>> event >> "e")
>>> >> does not work to delay the "abort", so that currently "abort" is 
>>> >> always
>>> >> immediate.
>>> >
>>> >
>>> >
>>> > Send bugs reports to this list.
>>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body > 
>>> "unsubscribe
>>> > csound"
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>> "unsubscribe csound"
>>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>> "unsubscribe csound" 
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound"
>