Hi Alex,

Sorry this is very late reply!  I was out of town the past weekend and
am backlogged on emails and I just noticed I never replied to this.

> There's just one thing I don't unterstand: Why do izakstart and izakend have
> to be i-rate?

They don't really, but if you do want to use k-rate, I'd recommend
passing in a izakmax or something so that you always run max number of
opcodes deep into the recursion.  That way, each opcode is always
being called during each run and delayed values will not get stopped
up and truncated because that opcode did not get called that k-pass.
(I do have to say I'm not quite sure how the memory is allocated and
the UDO stuff is ticked during performance, but I'm pretty sure you'll
have problems if you don't tick every opcode every k-pass)

> Oh, and I stumbled across another problem: Let's say I want to output the
> last nchnls a-rate signals of my zak array (i.e. the last two for nchnls=2).
> Obviously, I could simply get all the signals needed (using zar) and output
> them. However, this would require changing the code everytime nchnls
> changes. Is there a way simplify the process, so that no code changes are
> required? At first, I thought that outz would do what I want, but apparently
> it doesn't (I have yet to find out what _exactly_ it does, since the manual
> remains _very_ unspecific).

I'm not really sure what outz does either!  As for outputting x number
of signals to x nchnls, I'm looking and I don't happen to see any
"out" style opcode that allows writing a particular channel num.  It'd
be nice to find something like:

outnum kchannelNum, asig

but I'm not seeing anything like that.  I'm not sure there's going to
be a simple way to do this unfortunately.

steven