> As a result, does this mean that an extended guard point in a table is 
> required when a (normalized) tab value of 1 is specified, or not?

The extended guard point is not the problem, you can use it or no,
and the bug is indipendent from the GEN16. Your example with v5.15:

size  = 8192
k1    = 4
index = 8192  instead 8191

with size = 8193
k1 = 4
index = 8193  instead 8192

It is not correct, because the index varies between 0 and size-1.
The fix resolves this round off error

tito


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"