> You may be caught in the ongoig problem of the length of an array and its size
> allocation.  Since 6.06 this has been seriously reworked.   Not sure this is
> any help

> Another thought, possibly totally wrong.  In the arpeggio opcode there are a
> number of if statements that test an i-value, but the contents are k-rate
> assignments. I am not sure tat actually works and the k-rate stuff will not
> be called every k-cycle independent of the if statements.  I think there
> were changes in that region but 6.06 is so long ago!
> 
> You could unwrap the if elsef nests with goto statements?  i hope someone
> with more experience of udos can comment.
> 

Thanks.  Taking a guess, I moved the modulus calculations out of the 'if'
sections, using a temp variable (as the resultant index doesn't change
in there).  This makes it run for an extended period (10-15 minutes usually)
but eventually I get another arpeggiates out-of-range -- this time from
instr 24.

Too much Christmas stuff to be done, so I won't spend any more time
on it right now, but I was able to hear a few cycles of the piece!

	-- Pete --

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