Ah yes remembering to count from zero and letting csound process algorithm.
seems to have worked well. 

I've used this statement with the longer sample too:

i 101 0 10 [5*(1/130)]. 

I guess inaccuracies would only occur due to the sample length when values
begin to exceed the precision of 64-bit floats?

Instead of writing algorithms in the score for each i statement can I assign
1/130 (for example) to a variable that can be used instead?



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
[log in to unmask]
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