Hi,

is there a reverb that is less cpu heavy than freeverb, with equal or better quality? Two-three freeverbs eats half or more of my cpu. :/

Thanks!

@cfry @katjav made a vanilla abstraction to replace [freeverb~] that might help........ https://github.com/derekxkwan/pd-vfreeverb
I use [reverb282~] which registers no load in my task manager, but it is not vanilla....... R282.zip
But [freeverb~] doesn't cause any cpu issues for me either.
Reverb is a load of recycled delays and some filters so reducing any complexity is going to reduce quality...... there will be a trade-off.
David.

Freeverb should be one of the cpu-cheaper reverbs.

I can't reproduce any high CPU usage with it... < 1% here.

What's your OS and hardware?

hjh

@cfry This sounds suspiciously like a known bug in older versions of freeverb, see here:

https://lists.puredata.info/pipermail/pd-list/2009-11/074142.html

I had the same problem years ago when I added an older version of freeverb to my patch, namely that this denormals bug would cause the CPU to grow out of control if the input to [freeverb~] fell silent. The readme in my current version says "Recent changes (1.2.2): fixed the NaN/denormal check", but I haven't actually tested to see if the problem remains. I still have my original workaround in place just to be safe, which is to add a tiny amount of noise to the input signal:

[noise~]
|
[*~ 0.00000001]
|
[freeverb~]

What OS are you using? Linux installs generally use "ondemand" or some other CPU governance setting by default.

It has a HUGE impact on DSP load...

@beep.beep "I had the same problem years ago when I added an older version of freeverb to my patch, namely that this denormals bug would cause the CPU to grow out of control if the input to [freeverb~] fell silent. The readme in my current version says 'Recent changes (1.2.2): fixed the NaN/denormal check'"...

That's exactly what I suspected, and tested this morning, but I couldn't reproduce denormal performance problems. So I think it's really fixed.

Definitely worth updating, then. If the older version is not flushing denormal floats to zero, that would entirely account for out-of-control CPU usage.

hjh

@ddw_music said:

Freeverb should be one of the cpu-cheaper reverbs.

I can't reproduce any high CPU usage with it... < 1% here.

What's your OS and hardware?

hjh

I run a 2011 Mac Book Pro, hybrid hard drive, 16 gig ram. It is not in great condition, the fans runs often at max speed. I use OSX High Sierra.

I get error messages, the graphical objects stop responding. Sometimes Pd crashes, sometimes the whole computer crashes, and often I have to force quit Pd. This has not to do with freeverb I think. But when I use freeverb the processor start working for sure.

Anyway, I have 1 1/2 hour till I go onstage, and I just have t0 hope for the best. ;/ Maybe I will try to swap to [vFreeverb~]
.

@whale-av said:

@cfry @katjav made a vanilla abstraction to replace [freeverb~] that might help........ https://github.com/derekxkwan/pd-vfreeverb

It seems to me that the scale for the reverb parameter settings are not the same as in [freeverb~]. Especially the "damp" setting? Previous it was all 0-1. And is it still possible to get the freeze function? All in all I think it sounds really good as a general reverb.

Thanks a lot!