OBS Advanced Audio Monitoring and VB Cables all work. They don't work together.

[Objurgate]

My problem is this: I can set an audio device other than a VB Audio Cable/Cable A/Cable B as my Advanced Monitoring Device, and it works (the other end of the virtual cable is connected to Zoom). I can output audio from a source other than OBS to one of the VB Cables, and it works (I'm using a Firefox plugin in this case).

What doesn't work is OBS, after my last update, using one of the VB Cables as either its Advanced Monitoring Device or set up through the Audio Monitor plugin.

Also, I have Voicemeeter Potato X64 installed; I can set one of its built-in virtual cables as the OBS Advance Monitoring Device, and that works.

Reinstalling the VB Cables did not help. Wondering if anyone has had a similar experience.

Log file

 

[Objurgate]

My problem was that OBS input to the VB Audio cables was muted in the Windows Volume Mixer. I did come across this article, but didn't read it carefully enough:OBS Audio Not Working? Check These Easy Methods! (I can't believe how many hours I wasted. Thanks for this fantastic stealth muting feature, Microsoft.)
So, it turns out that not only can the cables be muted in the Sound Control Panel but OBS can be muted as an input to the cables . Although the Volume Mixer seems to have independent settings for each audio source cable, unmuting OBS for one appears to do them all.

 

[Objurgate]

Seems to be an ongoing issue with OBS input to VB Cables being muted in the Volume Mixer after OBS upgrades. Note that to access the Volume Mixer you right click the speaker icon in the task bar or type sndvol in the search field