But you could also set the Desktop Audio Device to Windows' default communication device in case you have the output for it (in this case any VM input could do). The default device is also used by your browser and by your games. Yes, Desktop Audio Device is generally set to the default audio device of Windows, so every sound Windows will make will go through that device. I just don't understand why I can't select a virtual cable instead. To be clear: Setting the 'Desktop Audio Device' to 'Default' does work (since VM is the default Playback and Recording device).

I must do this for games/apps that doesn't allow specific playback devices to be selected - that way they open the 'default' device (VM's VAIO Input), and I can control it in VM. I've set VM to be the default Playback and Recording devices under Windows. I guess what confuses me the most is why is there a difference in the VB devices listed between the 'Desktop Audio Device' and the Mic input devices? Since (I believe) both are inputs into OBS, why are the VB-cable listings different between them?Īs to VM's A outputs - if they are only hardware outputs, why can I select 'WDM: Cable-A Input' for the device? Seems to me that should allow me to feed Cable-A from, say, VM's A2 output, and then select 'Cable-A Output' in OBS's 'Desktop Audio Device'.

OBS's 'Desktop Audio Device' is suppose to be a device from which OBS receives audio, to be mixed and streamed, yes?

Okay, perhaps I'm mis-understanding the labeling here.

Banana virtual cable