Dear JPFF,

Are (or will be) 'schedule' and 'schedwhen' compatible with the 'kargc' family of opcodes,
which allow k-rate and a-rate argument passing and returning? There is a difference in
behaviour beetween 'schedule' and 'icall' & company?

Gab


jpff@maths.bath.ac.uk wrote:
> 
> Message written at 18 Nov 1998 11:07:11 +0000
> --- Copy of mail to gelida@intercom.es ---
> 
> >>>>> "J" == Josep M Comajuncosas  writes:
> 
>  J> Im afraid I cannot understand the way your opcodes
> 
>  J>   schedule        inst, iwhen, idur, ....
>  J>   schedwhen       ktrigger, kinst, kwhen, kdur, ....
> 
>  J> are supposed to work.
>  J> schedule always triggers the instrument when it is called, no matter the
>  J> iwhen parameter. Also, if  I put a schedule opcode inside a timout/reinit
>  J> statement to trigger an instrument several times strange things happen: it
>  J> seems that from the third activated event they are not turn off after idur.
>  J> Schedwhen seems even more strange to me, as it hangs Csound when ktrigger >
>  J> 0 , no matter kwhen.
>  J> Any help would be greatly welcome!! Im very excited with these new opcodes!
> 
> Bugs apart, schedule adds a new score event so
>    schedule        inst, iwhen, idur, ....
> 
> is like adding
> 
>    i instr when+p2 idur ...
> 
> to the score
> 
> schedwhen is sort of the same except at k-rate the value of ktrigger
> is tested and the first time it is zero (if ever) and event is added.
> 
> I will admit that although I had tested them when i attempted to use
> one of these in a composition last weekend something broke, but i was
> so excited by the music that I did not check the program.  It is on
> the list of things to do.
> 
> wrt reinit I have not thought about that at all.  I must think about
> it; I suspect i wrote it on the assumption that they could only kick
> in once.  Humm...
> 
> ==John ffitch

-- 
Gabriel Maldonado