Quoth Andres Cabrera , on 2008-02-26 08:44:23 -0500: > Hi Steven, > > That's a subtle but interesting question. It would make sense to have > the value be reached on the last kperiod affected to avoid missing > values like you mention, but this would mean the duration of the line > segment would be dur - 1/kr > > I'm not sure what to suggest, as changing the behaviour would make the > opcode more predictable and usable, but it would diminish in > precision... Using fully closed intervals for values like that creates subtle semantic problems because they don't stack on top of each other properly. (This is related to one of the reasons people index arrays from 0.) I don't think that would be more predictable, per se, especially since the actual slope of the line would depend on the value of ksmps (!). The stacking is the case where a line from 0 to 1 over 1 second followed by a line from 1 to 2 over 1 second doesn't connect together as a line but rather has a weird 1/kr hold period in between. I would vote to make it take a half-open interval and clarify that in the documentation; if you need the closed interval at k-rate, subtract 1/kr from the duration (or add 1/kr to the duration of everything else). ---> Drake Wilson ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net