Skip to main content
Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 1
    You should set Voicemeeter Input/Voicemeeter Output as your default device, and use it to handle where the audio is going to. Under Hardware Out, set A1 to the speakers and A2 to the headphones. If you want to disable the headphones, go to A2 and choose -remove device selection-. Then set the far left column in VoiceMeeter to your microphone, and the column next to it to CABLE-A or CABLE-B (you really only need one).
    – tomysshadow
    Commented Jan 8, 2016 at 4:35
  • Thanks! I think that would solve the issue. I got a blue screen dump when I disconnected the headphones on first attempt on my previous installation! Guess I'll try cable a/b on hardware input instead...
    – mk117
    Commented Jan 8, 2016 at 11:12
  • Make sure you're either using WDM or KS for the hardware inputs/outputs, they are the fastest and will have less latency than MME.
    – tomysshadow
    Commented Jan 9, 2016 at 22:18
  • ok. I was using WDM only, cause I thought the full form stands for "Windows Digital Media", so I was guessing it will be the default + voicemeter also listed it on the top of the list.
    – mk117
    Commented Jan 11, 2016 at 8:21
  • 1
    No, Windows has three different APIs for audio playback. MME is the oldest and slowest but kept around for compatibility reasons. KS stands for Kernel Sound and uses the kernel. WDM is the newest which you should use if possible. There's also ASIO (only on high end professional sound cards) and WASAPI (Windows Vista's API with no advantage over WDM)
    – tomysshadow
    Commented Jan 14, 2016 at 15:36