15 Jun
2007
15 Jun
'07
7:32 a.m.
[Fons Adriaensen]
The simple solution is not to use any control param
values in activate(),
but some defaults that are within range. Then in the first process()
you sweep from these to the ones derived from the actual control params
which must be valid at that time.
But, but ... the sweep during the first block of audio is precisely
what I'm trying to avoid!
One CAPS user complained because his (offline) host processed a few
seconds of audio in one call to run() -- he was not amused when the
resulting unintentional sweep lasted as long.
Cheers, Tim