OBS to VB-Cable to Zoom - stopped working

[David E.]

Hi all, I´m in a bit of panic mode here. I´ve been using the VB-cable and OBS without any issues for a few months now. I treat clients via a platform where I have a license (similar to the zoom interface), but suddenly I have no microphone sound via the cable at all on the platform, even though I can still choose the VB-cable as source (the sound works fine if I choose the microphone directly instead, but of course then the filters are gone). I have the exact same problem in Zoom. Everything still seems to work just fine within OBS though.

I recently upgraded to Windows 11 and figurered that´s the problem, so I tried downgrading to 10 again, but no difference. I´ve also re-installed the VB-cable today, made sure Realtek is updated and the volume is at 100% in the Windows interface. But nothings seems to work.

I have selected "Monitor and Output" for my microphone, and the VB-cable is selected as Monitoring Device. These were the only settings needed before this suddenly happened. I´ll attach a screenshot from the VB-cable Control Panel in case that´s any help (I have no idea what that´s supposed to look like).

My microphone is useless without the VB-cable since I really need the OBS filters because of my environment. What can I do? I´d be so grateful if someone helps me solve this.

 

[David E.]

After abut 14 hours of experimenting with no luck I did a factory reset of my PC and now everything works fine again. I believe something happened when I upgraded to Windows 11. I have no idea what happened, but the Control panel looks different now when everything works.

 

[AaronD]

I recently upgraded to Windows 11 and figurered that´s the problem, so I tried downgrading to 10 again, but no difference.

As I said in the other thread:

As long as Windows 10 is still supported, I'd stick with that. Not because 11 is bad, but because you already have a rig that works, and upgrading the OS is effectively an automated reinstall of everything. And downgrading again doesn't necessarily put it all back, as you found out.

If you have the time and energy to do a complete wipe and manual reinstall anyway, then go ahead. Otherwise, leave it as-is until the support runs out. Then find or make the time to actually rebuild it from scratch (not upgrade in place) based on what you've learned up to that point.

Don't have an outdated system on the internet, 'cause that's an open invitation to get hacked. Keep it updated and patched, but don't change major versions until you have to. Usually, that's when it won't update any more, for whatever reason. And when you do change major versions, consider it to be a fresh install with all of the new-system problems, because the "simple upgrade" concept rarely works.

 

[David E.]

As I said in the other thread:

As long as Windows 10 is still supported, I'd stick with that. Not because 11 is bad, but because you already have a rig that works, and upgrading the OS is effectively an automated reinstall of everything. And downgrading again doesn't necessarily put it all back, as you found out.

If you have the time and energy to do a complete wipe and manual reinstall anyway, then go ahead. Otherwise, leave it as-is until the support runs out. Then find or make the time to actually rebuild it from scratch (not upgrade in place) based on what you've learned up to that point.

Don't have an outdated system on the internet, 'cause that's an open invitation to get hacked. Keep it updated and patched, but don't change major versions until you have to. Usually, that's when it won't update any more, for whatever reason. And when you do change major versions, consider it to be a fresh install with all of the new-system problems, because the "simple upgrade" concept rarely works.

I´ll post my reply to you in this one as well, just in case somone only finds this thread:

Thanks for your reply AaronD! You are probably right, but I couldn´t help myself, I really wanted to get this working with Windows 11 before I could let it go. As mentioned, I did a factory reset with Windows 10 yesterday and after installing everything again OBS/VB-cable worked perfectly in both Zoom and my client platform.

However, today I upgraded to Windows 11 again, knowing that I might have to do the whole thing over again, and yes - the problem was back, just like before. But, since there seemed to be a problem with the virtual cable input (according to the previous check in the VB Control panel), I figured maybe the problem is between OBS and the cable. So instead of resetting my computer again I used IObit Unistaller to wipe any trace of OBS and the cable. I understand this is not an option for some that have a lot of stuff set up in OBS, but so far I only got a couple of scenes set up for my virtual camera. I believe there is an option to reinstall OBS but keeping the settings, but I have no idea if that would work.

Anyhow, now everything works great with Windows 11! Perhaps I could have done this reinstall yesterday instead of the factory reset, but now my PC is fresh as new, as a bonus. I´ve spent a ridiculous amount of hours coming to these conclusions, but maybe it can save someone else the hassle, and hopefully I´m set myself now. At least until the arrival of Windows 12:)