Audio popping/crackling with Hesuvi HRIR filters & Voicemeeter Banana
A system-wide equalizer for Windows 7 / 8 / 8.1 / 10 / 11
Brought to you by:
jthedering
Menu
▾
▴
Anyone have any ideas on how to fix the audio popping/crackling?
Seems like increasing the Voicemeeter buffer for WDM devices to multiples of 384 samples helps (doesn't seem guaranteed, need to test more).
Running latest drivers on Windows 11 with Realtek audio from a MSI Z690 Unify-X.
Thanks!
I've had these cracklings myself. And increasing the buffer helped indeed a bit. On this forum there's a solution saying that by starting the Equalizer APO VoiceMeeter client not at computer start up but later on, the crackling disappeared. The solution was to introduce a delay in the starting of the client.
Also, it may be an issue of sample frequencies not matching. Or the issue of using convolution. HeSuVi uses GraphicEQ which is convolution. Unfortunately GraphicEQ does sometimes have crackling issues too, nothing to do with HeSuVi. It's either an issue in Equalizer APO. But as you're using VoiceMeeter my guess is it's this known VoiceMeeter-Equalizer APO issue.
Thanks for the response.
Yeah, I did some more testing and even when I disable filters ("Deactivate Everything" under HeSuVi), the artifacts still occur at times so it might just be a Voicemeeter and Windows / driver thing.
I don't know much about how all this is implemented but I'll try posting in Voicemeeter support.
This seems very odd that I can consistently introduce / reproduce major artifacts by selecting any WDM buffer in Voicemeeter that is not a multiple of 192.
There are also some artifacts at say at the 384 sample buffer but I think they're just not as frequent.
So at least GraphicEQ is working fine on your computer.
And this is all happening after installing Equalizer APO on one or more virtual devices known in Equalizer APO as VoiceMeeter, Output A1 to A5?
Interesting that a multiple of 192 is better. This value is like a sample frequency of 192 kHz. Could be a coincidence. Anyway, are there still (minor) issues using a multiple of 192?