On Tue, Jan 08, 2019 at 07:00:08AM +0000, Victor Lazzarini wrote:
> That is because you are not reading point 16, but point 15. The table opcode will never overflow, it either limits or wraps around.

OK, thanks.  It seems to limit (in both directions).  Is there any state
in which it will wrap?  So I guess there is no way of seeing the guard
point?

I still don't understand what the normalization is doing, though.
The docs say it rescales so the maximum is 1.0.  So if the maximum
is already 1.0 shouldn't it leave all the values alone?  Why is the
value at index o raised?  And the maximum reduced if the table
is longer than the points supplied?

> 
> > ......
> > The result is:
> > 
> > 16 points table -- no guard:
> > 0:    0.210526
> > 15:    1.000000
> > 16:    1.000000
> > 16 points table -- with guard:
> > 0:    0.200000
> > 15:    0.950000
> > 16:    0.950000
> > 

Thanks,

	-- 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