Oversampling on convolution reverb
-
BTW, what does the "multithread option" do on the Convolution reverb ?
Its not available on the Scriptnode Convolution so just wondering. -
It moves the convolution calculation into a background thread. It's not faster in anyway, but it won't increase the CPU usage of your audio thread, so if your main goal is to keep the CPU meter down, this is the key.
-
@lalalandsynth Any progress on the aliasing? I'm experiencing the same issue. Setting the FFTType to 3 fixes it mostly, but also crashes my plugin and removes the reverb when MultiThread is active, which defeats the whole purpose. This is really making the convolution almost unusable.
How have other people achieved good results with the convolution module so far? It seems almost too whack for production-ready plugins.
-
@Lunacy-Audio I have it working in Scriptnode wrapped in oversampling, no multithread option though.
Just using a delay with no feedback as the predelay.However , you cannot switch impulses without major clicks and pops.
So yeah , not ready for plugins in my opinion.
-
Hmm bummer. Convolution is SO important!
I just noticed that if I disable IPP in the HISE build, the artifacts go away and you can keep MultiThread active. I might try this option with my test users and see if any performance issues arise. -
@Casey-Kolb Just to follow up, are you able to fix this convolution issue?
Is disabling IPP helped?As I see, for this issue, the IR length doesn't matters.
-
@orange We ended up just disabling IPP completely and that fixed the issue. No serious issues in terms of performance so far, but it would be nice to have IPP at some point without this issue.
-
@Casey-Kolb I really don't want to disable IPP, but if I'll have to, I can live with it.
-
@orange Are you noticing the artifacts with IPP active?
-
@Casey-Kolb Yes, when IPP is deactive the artifacts are gone
