> David Boothe wrote:
> 
> how is this different from schedwhen 

Ah, but this *is* schedwhen, except I changed the arguments and the 
functionality a little, and the name and the internal implementation 
completely. 

I thought the new name is more informative than "sched"-something, 
but this is of course the simplest part to change.

Richard Bowers concurred:
>
> I think schedule/when should be fixed because they're simpler to use 

Of course I did look at them, but they were done in such a way that I 
couldn't really use the code. 
So the present sched* opcodes should anyway be rewritten from scratch, 
and should probably best use the new "realtime event" that is described 
in the code post. (May even be implemented as triginstr calls.)
(Realtime events are the internal Csound mechanism for adding events 
in any manner except from a predefined score file; ie through live text 
input, live MIDI, MIDI files, or - if included - orchestra events.) 

> PS. With the sched* opcodes I find that the triggered instruments 
> are held indefinitely. 

That's one of the bugs I mentioned in my rant last week.
You can get around it only by having real score events (or midi 
input etc) between sched triggering and intended turnoff time. 


Regards,