Thanks for this info, Matt.

Indeed, you still have to add the two zeroes for "e" to work; it has not 
been fixed.

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.

None of this involves any backward incompatibility.

Andres:
In order to make the event docs correspond to the *current* coding, I 
suggest the following sentence be added following "scorechar" or at the end 
of the Performance section:
In the case of scorechar "e", the required syntax is: event "e", 0, 0

Art Hunkins

----- Original Message ----- 
From: "Matt J. Ingalls" 
To: 
Sent: Tuesday, February 05, 2008 8:47 PM
Subject: [Csnd] Re: Re: "Abort" Command?


>
> oh i should mention it used to be that you had to add some time/duration 
> params for this -- i don't know if it's been fixed yet, but if you do get 
> an error message this should work:
>
>  event "e", 0, 0
>
>
> On Tue, 5 Feb 2008, Matt J. Ingalls wrote:
>
>>
>>
>> event "e"
>>
>>
>> On Tue, 5 Feb 2008, Art Hunkins wrote:
>>
>>> Is there any facility in Csound that will permit a conditional abort 
>>> during orchestra initialization?
>>>
>>> In realtime situations, I often require performers to specify the values 
>>> of certain macros, and I'm looking for an abort capability if the macro 
>>> specified is out of range.
>>>
>>> Here's a simple example:
>>>
>>> #define FREQ #25000#
>>>
>>> if  $FREQ >= (SR * .5) then
>>> printf "$FREQ needs to be less than %d\\n", SR * .5
>>> abort
>>> endif
>>>
>>> I suppose the latter segment might need to be within an instrument 
>>> definition - which would be no problem in my case.
>>>
>>> I know this could be done by forcing some kind of error - but I'm 
>>> looking for something "clean".
>>>
>>> Art Hunkins 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" 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

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.