>> Other than the source code, where can I find info like this? 

The simple rule is that one written opcode gives one object.  If the
opcode needs to retain state that changes then it is dangerous/suspect
in a loop.  Personally I think loops in csound are usually a mistake
as they lead to such problems as you have.

It might be necessary to catalogue the state-full opcodes but as far as I
know that as not been done.

==John ffitch

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Could it possibly make sense to use a UDO with recursion in your case?


2016-03-03 0:14 GMT+01:00 Beinan Li :
> Alright, that clarifies a lot of things and at the same time a little
> depressing :(
> This probably means I'll need to write a code generator for similar batch
> processing, e.g., a pycall.
>
> Thanks,
> Beinan
>
>
> On Tue, Mar 1, 2016 at 11:45 AM, jpff  wrote:
>>
>> >> Other than the source code, where can I find info like this?
>>
>> The simple rule is that one written opcode gives one object.  If the
>> opcode needs to retain state that changes then it is dangerous/suspect
>> in a loop.  Personally I think loops in csound are usually a mistake
>> as they lead to such problems as you have.
>>
>> It might be necessary to catalogue the state-full opcodes but as far as I
>> know that as not been done.
>>
>> ==John ffitch
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here