On Fri, Jun 15, 2007 at 10:55:13AM +0200, Tim Goetze wrote:
However, when Ardour calls activate(), the control
inputs point at
uninitialized memory (ie. garbage data). A plugin with 10 control
inputs like Eq thus stands a fair chance of running into a value of
nan or inf, causing all sorts of computational mayhem including the
problems described above.
So what to do about this? ladspa.h says nothing about the value of
control inputs at plugin activation time. What it does say is that
plugins should be able to operate on invalid input data without a
glitch, and I'm working on making CAPS resolve the issue gracefully.
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.
--
FA
Follie! Follie! Delirio vano รจ questo !