Keep in mind, digital audio is a highly complex technology, where a lot of elements have to work flawlessly together to get an uninterrupted, undistorted result: hardware quality, audio drivers, the operating system, the audio buffer size and finally the used audio software. Problems can have multiple reasons and sometimes canot be fixed with a simple switch of a button.
All audio Apps should be connected to VOICEMEETER or should not use same audio output device than VOICEMEETER, to avoid audio device conflicts. We strongly recommend to set VOICEMEETER virtual audio I/O as your default playback / recording device.
In all cases you must test it on significant duration to validate your configuration before going on air. If the problem remains, send a screenshot of VOICEMEETER and its system settings dialog box in our forum to let us see your configuration.
Select the best audio device for output A1
Keep your default settings – default buffer size / default engine mode – and select your best audio device as output A1. This gives the most stable device the main audio output.
- an ASIO device if present with 256 or 512 sample buffer size
- WDM or KS with 512 sample buffer size
- MME with 512-1024 sample buffer size (as last choice).
The device selected as output A1 sends the main stream.
The output A1 device is used to generate the master audio stream, all other I/O and streams will be based on it. So this device must work correctly.
A WDM device will be used in EXCLUSIVE mode per default. But the device could refuse in some cases, because it is already in use or because the eclusive mode is disabled. In this case, the device will be used in SHARE mode (a “S” is displayed in System Settings Dialog box – right to the output A1 Device audio format). The stream might be unstable and it could be better to use an existing KS or MME driver.
Avoid audio device conflicts
A typical problem comes when using ASIO Driver as output A1 and selecting the same device with another audio interface (WDM, MME, KS) as hardware input or on another VOICEMEETER BUS.
This creates an Audio Device Conflict. If you select an ASIO device as main audio device (output A1) you must use ASIO routing capabilities (ASIO PATCH in VOICEMEETER system settings) to assign ASIO channels to VOICEMEETER physical input or output BUS.
Keep in mind:
DO NOT SELECT THE SAME AUDIO DEVICE TWICE IN DIFFERENT AUDIO POINTS.
Check your stream with the integrated recorder
The best way to check that your main stream on output A1 device is running stable is the integrated Recorder/Player in Banana/Potato.
Simply play some audio tracks and check that there is no problem, no cuts, no distortions, no crackles … just the sound, that you expect.
Change the buffers for the Virtual Audio Path
Audio on PCs works always with buffers and buffer sizes, which are processed by the CPU and the overall system. Smaller buffer sizes result in lower latency (which everybod wants), but also in higher buffer numbers and a higher CPU load. If buffers are to small or have the wrong size to work with a software, which uses a different buffer size, it can result in crackles or dropouts.
Sometimes the buffer related problem can be located in a virtual audio path, for example from VOICEMEETER virtual output (BUS B1, B2 or B3) to a capture application (Discord, Skype, etc…). You may check the internal latency of the related VAIO (virtual audio I/O).
The default number is 7168 samples, but in some cases it could be not enough to guarantee a stable stream on virtual link (pending on the buffer used by application connected on – for example 7168 sample could no be enough if the capture app use 4096 samples buffer).
Then you may increase internal latency by the VBCABLE_ControlPanel app installed with Voicemeeter (there is one ControlPanel for each virtual audio cable – used as virtual audio I/O by Voicemeeter).
Give your Windows Audio process a higher priority
Assign the process to a single CPU core (see tutorial video below).
Several ongoing software processes with equal priority can disturb the realtime streaming of the main Windows audio process. By giving it a higher priority and/or assigning it to a single CPU core, it can be freed from ressource competion.
(1) Search for the Windows task manager with the Windows search field
(2) Right click the Task Manager app and select: Run as Administrator.
(3) Select the tab “Details”. Sort the proceses by name.
(4) Search for “Audiodg.exe” (if you don´t see this process, you are not use the Task Manager as Administrator).
(5) Right click Audiodg.exe and set priority to high. OK.
(6) Right click Audiodg.exe and set affinity to a single physical CPU core (select only CPU 2, 3, 4 …).
Give your Windows Audio process a higher priority.
+ Assign it to a single CPU core.
De-install and Re-install VOICEMEETER
If nothing helps to get a stable stream, it usually means that one or several audio drivers are not correctly installed.
Don’t forget to REBOOT after the audio driver installation (or de-installation) – this is also true for any new USB audio device that you plug on your computer – even if installation is automatic, it’s better to reboot after.
Recommeded Re-installation step by step:
- Remove all USB audio device + REBOOT.
- De-install VB-CABLE one by one + REBOOT.
- De-install Voicemeeter + REBOOT.
- Check your remaining audio devices are working ok.
- Check there is no presence of our virtual audio driver in Windows Device Manager (in both sections: multimedia controller and audio input output).
- Re-install VB-CABLE and Voicemeeter one by one, REBOOT after each operation, check your device list in Windows Sound Dialog box.
- When all is re-installed, re-plug your USB audio device. check again your default playback and recording device.
- Run Voicemeeter and check systray option. Audio should work again correctly.
Anyway your VB-CABLE or Voicemeeter VAIO’s must appear like on the picture below for Playback and Recording Devices. Otherwise you should re-install them correctly.