If you have an input option for WDM, use MME. ![]() You should hear varying levels of choppiness, and the best advice is just mess around till it works.Īnother thing you can do: Rishi Raj Yadav 2 months ago (edited): If you guys are getting crackling/stuttering sound then go to task manager > details tab > look for audiodg.exe > set affinity > choose only 1 physical processor in it and restart audio engine of voicemeeter.Affinity resets everytime you restart so you can use Bitsum software that will set affinity automatically at every start. I don't know the technical details about it, but try messing around with your mic's buffer sizes and voicemeeter's buffer sizes. The "talking behind a fan" effect is most likely a difference in buffer sizes. It might be different, but here are some suggestions I have that might work: ![]() Hello, I also ran into a similar problem like this. My mic path is currently: Focusrite audio usb interface -> Nvidia Broadcast (Echo reduction) -> Voicemeeter -> AUX or VC -> Discord / other apps Any changes I make in Windows or otherwise do not seem to reflect in the VC control panel and I can't understand why. I can't seem to find a way to get these to match through Voicemeeter or Windows sound settings. ![]() One thing I have noticed in the Virtual Cable Control Panel is that my input sr and output sr are different: 48000 Hz / 44100 Hz. I can output through Voicemeeter Aux just fine but I'm trying to understand why this isn't working through VC and also trying to save on an input. The only way I can describe it is if I were talking from directly behind a fan. I just can't seem to get it to route through Virtual Cable without choppy audio. I have recently purchased an AT2020 XLR and a Focusrite Scarlett 2i2 (3rd gen) I would like to redirect my microphone through Virtual Cable as A2 (after adding a little compression, gate etc).
0 Comments
Leave a Reply. |