I am testing the latest "deken" version of freeverb~ to see if an old issue regarding dividing by 0 was fixed.

years ago, freeverb~ would just continue to overload until the audio dropped, this was due to the fact that it processed 0 signal and created conflict (I found this out in an email thread years ago -can't find it now). the simple solution was to have freeverb~ always process a noise~ signal in extremely low amplitude.

the latest version in deken does not reach the point of overloading the CPU, but whenever it has 0 signal to process it still spikes the CPU usage.

I wanted to ask who was in charge of this object to see if there is interest in getting this fixed.

ps. it is very easy to reproduce, just use the example in the help file and watch the CPU usage while it has some signal to process and when it doesn't.

a small video to show the issue: