Skip to content
Voicemeeter software mark

Signal path / troubleshooting

Trace the path, then fix the break

Symptom-first fixes for crackle and stutter, Discord and OBS routing, microphone tone with Intellipan and Audibility, ASIO interfaces, device hotplug and antivirus false positives. Work one section at a time.

New install? Start on the download page. Need bus vocabulary first? Read the features tour.

Symptom index

Case 01

No audio after install

Virtual devices exist in Windows but you hear silence, or apps cannot see Voicemeeter Input. This is usually missing reboot, wrong default device, or A1 not assigned.

  1. Install as administrator and reboot. Extract the ZIP from the download page, run setup as administrator, then restart Windows before opening any mixer.
  2. Confirm virtual devices in Sound settings. Open Windows Sound. Playback should list Voicemeeter Input and Voicemeeter Aux Input (Banana/Potato). Recording should list Voicemeeter Output and Voicemeeter Aux Output.
  3. Assign A1 inside Voicemeeter. Pick the physical device you actually listen on (headset, speakers or interface). Until A1 is set, the engine has no master clock path.
  4. Route a test source. Play music to Voicemeeter Input in Windows. In the mixer, press B1 on the VAIO strip and confirm meters move. Set an app to Voicemeeter Output only after you see level on the strip.
  5. Disable exclusive mode on A1 temporarily. In Windows advanced device properties for A1 hardware, turn off "Allow applications to take exclusive control" while you verify routing, then re-enable if your DAW needs it.
  6. Check Windows volume and mute. Voicemeeter hardware out faders, strip mutes and the A1 mute button must be up. Windows master volume for the A1 device must not be zero.

Still silent? See device hotplug and reinstall or the FAQ.

Case 02

Crackling, stutter and robot voice

Buffer underruns, mismatched sample rates and the wrong driver mode on A1 are the usual causes. Fix A1 first before you chase every strip.

  1. Set A1 to your main playback device. A1 sets the master sample rate for the whole engine. Use the device you actually hear during tests.
  2. Match Windows and Voicemeeter sample rate. Open Windows Sound for the A1 hardware and set the same rate Voicemeeter shows (often 48000 Hz). Mismatch causes crackling and pitch shifts.
  3. Try WDM or MME on A1. Click the A1 device label and switch driver mode. Start with WDM. If crackling continues, try MME on A1 only. Avoid forcing WDM on every strip if the interface struggles.
  4. Increase buffer size. Menu System Settings / Options. Raise Buffering MME, Buffering WDM or Buffering KS in small steps (for example 512 to 1024). Apply and test after each change.
  5. Restart the audio engine. Menu Restart Audio Engine. If robot voice or stutter remains, close Voicemeeter, reboot Windows, then open the mixer before other apps.
  6. Reduce load on the same device. Close unused apps that hold the mic or playback device exclusively. One aggressive Discord or OBS filter chain plus low buffer can still crackle on weak USB controllers.

Related: ASIO setup if your interface provides its own driver.

Case 03

Routing and echo feedback

Echo happens when the same signal loops: chat hears itself, or your mic reaches speakers that the mic picks up again. Bus A is hardware out. Bus B is virtual out for apps.

  1. Learn the bus split. Send music and games to A1 so you hear them. Send your processed mic to B1 so OBS or Discord capture Voicemeeter Output, not the raw mic twice.
  2. Stop double monitoring. If Discord input is Voicemeeter Output and you also send B1 to A1 with chat audio on the same path, you create a loop. Mute the strip that returns chat to your ears while testing.
  3. Use headphones for tests. Speakers plus an open mic almost always cause room echo. Verify routing on headphones first, then move to speakers with gate and lower speaker level.
  4. Separate playback and capture apps. Windows default playback: Voicemeeter Input. Windows default recording: your physical mic or Voicemeeter Output depending on the goal. Change one default at a time.
  5. Check OBS monitoring. OBS "Monitor and Output" on a source that already routes through Voicemeeter can stack paths. Prefer monitoring inside Voicemeeter on A1 only.
  6. Draw a one-line map. Mic strip to B1 only. Game VAIO to A1 and B2. Confirm no strip sends both your mic and remote chat back to B1 without intent.

Bus details: features page. Streaming desk: Discord and OBS section.

Case 04

Discord and OBS routing

Banana and Potato give two or three VAIO strips so you can split game, Discord and browser audio. OBS reads Voicemeeter Output while you listen on A1.

Discord desk

  1. Windows playback default: Voicemeeter Input for general audio, or route Discord alone to Voicemeeter Aux Input on Banana.
  2. Hardware mic on strip 1. Gate and EQ on the strip. Send mic to B1 only for chat capture.
  3. Discord input device: Voicemeeter Output. Discord output: your A1 headphones so you hear the mix.
  4. Send game VAIO to A1 and optionally B2 if OBS needs a separate game track.
  5. Disable Discord input sensitivity auto-adjust while tuning levels in Voicemeeter.

OBS desk

  1. OBS audio input capture: Voicemeeter Output for mixed mic, or Voicemeeter Aux Output for a second bus.
  2. Add separate sources for Voicemeeter Aux Output and Voicemeeter VAIO3 Output on Potato for isolated tracks.
  3. OBS monitoring: disable duplicate monitor paths that also send to Voicemeeter Input unless you intend a loop.
  4. Sample rate in OBS advanced audio: match Voicemeeter (typically 48 kHz).
  5. Test with OBS stats and Voicemeeter meters before going live.

Crackling on stream? Run the crackling fix steps with OBS closed first, then add apps back one at a time.

Case 05

Microphone quality: Intellipan and Audibility

Cheap USB mics benefit from strip gain staging, Intellipan positioning, Audibility enhancement and a light gate on Banana or Potato. Turn off conflicting Windows voice enhancements first.

  1. Disable Windows mic enhancements. Recording device properties, Advanced or Enhancements tab depending on driver. Let Voicemeeter handle EQ and dynamics.
  2. Set hardware input and trim gain. Peak near yellow on loud speech, not pinned red. Leave headroom for Audibility and compressor on Banana.
  3. Intellipan for tone and space. Use the color knob for warmth or clarity. The 2D pan field adjusts stereo width for headsets without harsh fake reverb.
  4. Audibility for presence. Raise Audibility slowly until speech cuts through game noise. Back off if sibilance spikes or noise floor rises.
  5. Gate on Banana or Potato. Open gate threshold so keyboard between words is reduced. Pair with compressor threshold so level stays even for Discord and OBS.
  6. Send processed mic to B1. Chat and stream apps should read Voicemeeter Output, not the raw Windows mic, so processing is consistent everywhere.

FX overview: Intellipan and dynamics on the features page.

Case 06

ASIO interface setup

Voicemeeter exposes Voicemeeter Virtual ASIO for DAWs. Your hardware interface can also sit on A1 if you prefer one clock source. Do not run two ASIO hosts on the same device at the same buffer without planning.

  1. Pick one master clock. Either assign A1 to your interface on WDM and use Voicemeeter Virtual ASIO in the DAW, or use the interface ASIO driver as A1 if the vendor recommends it.
  2. Install the latest interface driver. Generic Windows USB audio plus low ASIO buffer often crackles. Vendor ASIO or stable WDM first, then tune Voicemeeter buffers.
  3. Open DAW on Voicemeeter Virtual ASIO. Select Voicemeeter Virtual ASIO as the DAW device. Inputs map to Voicemeeter strips; outputs map to hardware and virtual buses per the manual routing table.
  4. Match sample rate before opening projects. Set DAW project rate to the same value as A1. Restart Audio Engine after changing rate.
  5. Avoid dual ASIO contention. Close other apps that hold the interface ASIO exclusively while testing Voicemeeter Virtual ASIO, or route the interface through WDM on A1 instead.
  6. Latency check. Increase ASIO buffer in the DAW if you hear clicks. Small hardware buffers plus heavy Voicemeeter FX raise CPU load.

Case 07

Devices, hotplug and clean reinstall

USB headsets and interfaces that appear or vanish can leave Voicemeeter pointing at a missing A1. Leftover driver entries after a partial uninstall cause ghost devices in Windows.

  1. After hotplug, reselect A1. Unplug and replug USB audio, open Voicemeeter, confirm A1 still lists the correct device name, then Menu Restart Audio Engine.
  2. Do not change five devices at once. Plug one new mic or interface, set strip input and A1, test meters, then move to the next device.
  3. Remove ghost devices in Windows. Device Manager, View show hidden devices. Uninstall grayed duplicate Voicemeeter or VB-Audio entries only when Voicemeeter is closed and you are ready to reboot.
  4. Full uninstall order. Run the Voicemeeter uninstaller from Apps, reboot, remove leftover VB-Audio Cable entries if you no longer need them, reboot again.
  5. Reinstall from a fresh package. Download current builds from the download page, install as administrator, reboot, then configure from no audio steps.
  6. Save a working XML snapshot. Menu Save Settings after a known-good routing pass so you can reload after driver updates.

Case 08

Antivirus false positive

Virtual audio drivers install kernel-level components. Some security tools flag new audio drivers before reputation builds. This is a known pattern with virtual cable and mixer software on Windows.

  1. Use the package from this site. Fetch the ZIP from the download page rather than unknown mirrors.
  2. Run setup as administrator once. Allow the installer to complete. Do not quarantine mid-install or you can leave half-registered drivers.
  3. If flagged, check quarantine. Restore the blocked VB-Audio or Voicemeeter driver file only when you trust the source, then rerun install.
  4. Add an allow rule after verification. Exclude the Voicemeeter install folder from real-time scan if your vendor supports path exclusions and you accept the tradeoff.
  5. Reboot after allow. Restart Windows so virtual playback and recording devices register cleanly.
  6. Read trust notes. See trust and security for install behavior and offline use.

Case 09

Best practices

Stable Voicemeeter desks change one variable at a time, keep A1 sample rate as the single clock reference, and document routing before adding stream overlays or heavy FX chains.

  1. One change, one test. Move a single fader, bus button or buffer value, then listen for thirty seconds before the next edit.
  2. Keep A1 as clock master. Set sample rate on A1 hardware first, then match Windows, OBS, Discord and your DAW.
  3. Label strips in your head or on paper. Strip 1 mic, VAIO game, Aux Discord. Mislabeled mental maps cause most "routing bugs."
  4. Save Settings XML after milestones. After first clean stream or call, store the file somewhere safe before driver updates.
  5. Restart Audio Engine before reboot. Menu restart fixes many glitches; full reboot fixes driver registration after install or uninstall.
  6. Use FAQ for quick answers. Licensing, editions and Windows 11 support live on the FAQ page when you need a short answer without a full walkthrough.

Next step

Install or update Voicemeeter

Standard, Banana or Potato packages. Install as admin, reboot, then return to Case 01 if devices are missing.

Open download console
Download
Privacy PolicyTerms & Conditions