

The program crashes or hangs periodically/frequently.The program is not compatible with other installed applications.These are the main reasons why Virtual Audio Cable is uninstalled by users: Some experience issues during uninstallation, whereas other encounter problems after the program is removed. It seems that there are many users who have difficulty uninstalling programs like Virtual Audio Cable from their systems. What usually makes people to uninstall Virtual Audio Cable You came to the right place, and you will be able to uninstall Virtual Audio Cable without any difficulty. I haven't tried these myself, just because I'm fine with doing the workaround, but I have a couple suggestions: I have had the same experience with games.Virtual Audio Cable is a multimedia driver designed to connect one or more audio applications in order to transfer audio streams between them.ĭo you have trouble completely uninstalling Virtual Audio Cable from your system?Īre you looking for an effective solution to thoroughly get rid of it off the computer? Do not worry! Have you tried capturing CABLE Output (the recording / input device that you have windows Listen to) rather than Input? The sound is going through Input okay because you can hear it, so maybe if you set it to record Output OBS will always hear it. Have you tried voicemeeter? Usually I hate the damn thing for a bunch of reasons and I hate how people on this sub recommended it for use-case scenarios that don't require it (which is 9 times out of 10), but I believe there's a chance that if the virtual cable goes through VM rather than just the windows Listen feature, and OBS picks up VM audio (set to the virtual output which only broadcasts Cable Input) then it might not break the chain. Be sure to adjust your sample rates for the devices in Windows Sound Control Panel and the Cable's own control panel exe and VM to all be the same to minimise latency, and VM might require you to restrict its usage to certain CPU cores to eliminate buzz (one of the main reasons I hate it). Try it out for a couple days, starting with the first suggestion. I don't know what actually causes the bug, like if it's a shutdown that causes it or set period of time.
