[chuck-users] More on what Envelope.time does.
signal.automatique at gmail.com
Wed Sep 13 20:50:33 EDT 2006
On 9/14/06, Jukka Akkanen <jakkanen at mac.com> wrote:
> Looks like .time is taken as the length of time in seconds for the
> value to go from 0.0 to 1.0. Based on the ChucK manual, I, too, would
> have expected this to be the desired time to go from the current
> value to the target value. Care to report this as a bug, http://
> wiki.cs.princeton.edu/index.php/ChucK/Bugs/Reports seems to be the
> place for that?
I'd be delighted to report it "officially" but it just might be badly
documented correct behaviour?
What I wanted is admittedly totally different from what it's intended to do.
I wanted a "free" interpolating glide. My plan was to feed it a .target in
Hz, set time to something dependant on BPM and just feed it a new "target"
every note, chuck env.last() to osc.freq every few ms for some cheap
Well.... no cigar.
I think you are right about how it works; in that case "time" would define
the slope of the ramp. That'd be valid if somewhat odd.
So; the documentation is mistaken or the code has a problem.... Personally I
suspect Envelope wasn't expected to have .target be set to something along
the lines of 500 so it might be cool to talk about what it's supposed to do
and how in ChucK. I'll submit the bug to the official page for reference and
use a rather elaborate way of "manual" interpolation for now.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chuck-users