VM works flawless whenever I Uninstall the Oculus software but as soon as it's installed it just freaks out windows and refuses it to control any audio. I just would love to know a fix so I can properly send my audio outwards, and it seems to me, that it is from the Occulus software interfering in some way and I am completely unsure of how to go about fixing whatever they broke. You should now see the ‘Desktop’ virtual input monitoring your audio and should be able to see the blue and green monitoring line going up and down. Also set VoiceMeeter as the default device and communication device in the Playback devices and Recording devices in Windows own sound settings. Play some audio on your system and open up VoiceMeeter. It makes it easier to keep track of where everyone goes. That way 1 program is driving your audio. So put your mic on Hardware Input 1 then route out from there. I/O (VAIO) supports all possible Audio Interfaces and allows. And 1 more suggestion would be to use Voicemeeter for all your audio. Despite this, it is sending to Voicemeeter VAIO no matter what. Make sure VoiceMeeter Aux Input (VB-Audio Voicemeeter AUX VAIO) is selected. Voicemeeter offers Virtual Audio Point on Input 3 and on BUS B (Output B). My issue is simply this, Windows is sending all audio to Voicemeeter VAIO despite having Virtual Cable-D as default and having Chrome send audio to Virtual Cable-C and Discord set to Virtual Cable-B.

I cannot get windows nor Occulus to send my audio out to any of my virtual Cable's through Voicemeeter and I would like to do so, just so all my audio for streaming is actually seperated and I can ensure a good quality stream for viewers while having full control of audio on my end. Missing Vocemeeter VAIO device (AUX and VAIO3 are OK) by smallfreak » Fri 2:23 pm I installed the Potato 3.0.1.3 and it seems that I lost 'Voicemeeter VAIO' along the road.

Voicemeeter vaio