IPP and convolution questions
-
I am getting some occasional pops and crackles in my exported plugin. The debug txt document from Hise is giving me this:
NoteOn CI:
386ID:1822TS:208V1:G2, V2:80, Ch:1
NoteOff CI:392ID:1822TS:88V1:G2, V2:80, Ch:1
NoteOn CI:397ID:1823TS:432V1:G2, V2:73, Ch:1PerformanceWarning
- Time: 4.35 / CallbackIndex: 408
- Location:
Reverb1::ConvolutionRendering - Voice Amount: 110
- Limit:
10.0%Avg:1.78%, Peak:10.0%
Is this something installing with IPP could fix? At a certain point I stopped including it in my builds cause I wasn't noticing much of a performance difference, and I try to avoid things I have no idea about :)
-
-
Does anyone have any tips about how to get better performance out of the convolution module? I hate to give it up but I am scared of using anything that might cause a playback glitch.
-
@crd How long is the impulse? And have you checked whether multithreading solves it? Also if you're on Windows, using IPP is pretty much obligatory if you want to use the convolution reverb - on macOS the performance difference is negligible (which is why I'll probably remove it altogether on macOS).
-
@christoph-hart thought you told me long ago that multithreading does nothing? Sorry if I'm wrong…
-
@ustk No that's a misunderstanding. It actually works and shifts the convolution of the tail to a background thread which takes some load off the audio thread (however it's not a real performance gain, it just might be able to distribute it better on multiple cores if they are available and idle).
-
I have only been working so far on macOS.
The longest impulse is 2.5 seconds.
I have not been using the multithread option. I'm only noticing the glitch when I export the plugin so I will reexport a version with the multithreading engaged and see if that helps.
-
@crd Hmm, 2.5 seconds is nothing and shouldn't cause dropouts. What machine do you use for testing and how is the buffer size / sample rate?
-
6 core Mac Pro 2013, Reaper, and 512 buffer size, 24 bit 48k.
I'll put everything through it's paces more properly tomorrow. If I don't go do xmas stuff now my family will disown me. :) -
@christoph-hart Okay I am getting the same sort of playback issue with multithreading engaged. The errors in the debug log have changed. The log is here:
https://www.dropbox.com/s/jaj299oc4o7swa9/Debuglog(2).txt?dl=0
The issues go away entirely when I replace the convolution reverb with the algo reverb.
-
Bump to see if anyone has any ideas about why the convolution module would be giving me these pops and clicks? Here is a wav of what is happening:
https://www.dropbox.com/s/q4nt5w9wc4ct9x6/pnoTextures_popsandclicks.wav?dl=0
The wav file corresponds to the debug files I linked earlier.
The issue goes away when I replace the convolution reverb with the algorithmic one.
-
@crd Does the problem occur with any other convo reverbs?
-
@d-healey I am going to test now with some of the IR you posted on the forum a while ago and see. It seems to only happen with my largest IR (which isn't very large 2.5 sec).
-
@crd said in IPP and convolution questions:
some of the IR you posted on the forum a while ago and see
No I meant have you tried the same IRs in a different convolution reverb effect?
-
@d-healey I have not. I am borrowing these IR from altiverb before I make my own but will throw them into ReaVerb later today to double check it isn't an issue with the IRs.
-
I am still having these performance issues with the convolution reverb.
Is anyone else getting pops and clicks like this?
-
@crd Did you get the same issue in another convolution reverb effect? Did you post the problem IRs in this thread?
-
@d-healey It doesn't seem to be the IR's. It seems to be a performance issue with the convolution reverb module.
-
@crd I wanted to know if you'd posted the IRs in this thread so I can test them. I've been using the convolution for years in several projects and haven't noticed any issues.
-
@d-healey I haven't posted them. I'd rather not share the specific IR's. I've tested using your hall IR and gotten the same results. It doesn't seem to be about the IR but the voice count. The issue is only happening in the compiled vst.
The pops and clicks disappear when I limit the voice count using the settings comobox, Max Voices, which is strange since my sampler's are already set to Amount, 30 and Soft Limit, 29. Good news, setting the Max Voices to 128, 64 or 32 fixes it. I'm not sure what the exact relationship is between voices and the convolution engine or the max voice setting but it's working.
