WINDOWS AUDIO / A CLEAR PATH

Windows audio routing helper.
Discord, OBS & VB-CABLE.

Choose what you want to connect. Get the device names and steps for Discord, OBS, or a browser microphone test.

Privacy-first & local-only: This Windows routing planner runs strictly inside your browser—it never inspects your devices, requests microphone access, or retains anything on our server (shareable links only encode your chosen goal in your local URL). No accounts or ads; cookieless site stats count only anonymous page visits and tool starts. Website privacy details →

Where should the audio go?

These instructions target Windows 11. This helper explains the settings; it does not change your devices or request microphone access.

Phone microphone → Discord

  1. Phone microphoneMicDrop: Send microphone enabled.
  2. CABLE Input → CABLE OutputWindows MicDrop sends into the cable; Discord receives from it.
  3. DiscordInput Device: CABLE Output. Output Device: your headphones.
  1. Install VB-CABLE separately on Windows and restart if its installer requests it. Confirm that both CABLE Input (playback) and CABLE Output (recording) appear in Windows Sound settings.
  2. Stop the MicDrop host. Under Audio, choose CABLE Input for Phone microphone destination. Keep Desktop audio source on your normal speakers or headphones, then start the host.
  3. Connect and approve your phone in MicDrop, grant microphone permission on the phone, and enable Send microphone.
  4. In Discord, open User Settings → Voice & Video. Choose CABLE Output as Input Device and your physical headphones as Output Device.
  5. Run Discord's microphone test, speak, and toggle Send microphone off in MicDrop. The input should stop when muted. Turn it on again after checking.

Keep call playback on physical headphones. Sending Discord's output into the same cable can feed the call back into its own microphone.

Showing the phone microphone to Discord setup.

Why are the cable names backwards?

Think from the cable's perspective: sound enters through CABLE Input, a Windows playback device. Another app receives that sound through CABLE Output, a recording device. They are two ends of one virtual connection.

Check one step at a time

If no meter moves, first confirm that the source is producing audio. Then check the receiving app's selected input. A browser microphone test can help verify the cable, but browser processing may differ from Discord or OBS. With OBS, avoid capturing the same input both globally and as a scene source.

For a desktop app in OBS, Application Audio Capture may be a simpler option without a virtual cable. The cable recipe is useful when you specifically need to route through a recording device. A single VB-CABLE mixes everything sent to it; use a separate route if you need independent sources.

Keep your listening output separate

If an app is routed into VB-CABLE, it may stop playing through your speakers. Do not fix that by sending the receiving app back into the same cable. If you enable OBS monitoring, choose physical headphones as the monitoring device.

For Mac and Linux playback to your phone, use the Mac or Linux guide; the Windows endpoint names in this helper do not apply there.

Common VB-CABLE, Discord & OBS routing questions

Do I choose CABLE Input or CABLE Output as my Discord or OBS microphone?

Choose CABLE Output as the Input/Mic device inside Discord, OBS, or a browser test. The sending app (such as MicDrop’s phone microphone return) writes audio into CABLE Input, and receiving apps read that signal from CABLE Output.

Why did my PC speakers go silent after installing VB-CABLE?

The VB-CABLE installer often switches Windows’ default playback device to CABLE Input upon installation. Press Win + Ctrl + V (or open Settings → System → Sound) and set your physical headphones or speakers back as your Windows default Output.

How do I stop hearing a doubled or echoed voice in OBS or Discord?

Make sure Discord’s Output Device and OBS’s Monitoring Device point to your physical headphones—never back into CABLE Input—and avoid adding the same mic both under OBS Global Audio Devices and as a scene source. See fixing microphone echo.