i'm having problems with the good ol' freeverb~. the problem is, with couple of my patches the cpu usage suddenly goes throught the roof. like after running the patch for 5-30minutes. i finally narrowed it down to freeverb~ freaking out. i switched to similar reverb in hardoff's DIY-package but still wonder what's the problem...

i'm on osx 10.6.6, pd-ext 0.42.5, intel macbook. fiddling with the buffer size doesn't seem to make any difference.

[freeverb~] suffers from denormal issues. You can remedy this by constantly sending very quite noise through it.

ok. thanks!

Maelstorm, could you please tell what "very quite noise" is? I'm using the nice omniverb freeware reverb (from jeroen breebaert). When my patch generates sound, it goes into the reverb and cpu goes up and comes down again when there's no sound anymore. However, after a while it starts using cpu again even though the patch is not generating sound anymore. When i bypass the plugin, all cpu is released, but when turned on again it eats free cpu again. I've tried to send this

[noise~]
|
[*~ 0.00001]

to it, but this doesn't help. But maybe it has to do with the plugin itself or the vst~ object, i'm not sure.

I usually just send [1( through [dbtorms] and use that value. It comes out to about .000012202, which seems to do the trick, at least with [freeverb~]. I'm sure you could get away with larger values. Listening through headphones from my laptop with the system volume cranked, I can barely hear the difference between [1( and [10(.