>> 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.
Csound mailing list
[log in to unmask]
Send bugs reports to
Discussions of bugs and features can be posted here