HDMI Capture causes OBS audio to sputter out

DrCyanide

DrCyanide

New Member
I'm trying to migrate from one PC (Windows 10) to another (Windows 11). I use OBS primarily for the Virtual Camera, and connect my audio output via VB Cable. On the old PC, everything in OBS works exactly as it should. On Windows 11, when I connect my HDMI Capture device (this USB dongle) the audio starts sputtering, cutting out, and doing a "I'm lagging, better hurry ahead to try and catch up!". At first I thought it might have been some setting I forgot when going from Windows 10 to Windows 11, so I copied my %appdata%/obs-studio folder from Windows 10 to Windows 11, but I'm still having issues.

To make matters even more puzzling, the audio sputter happens even when there's nothing connected on the other end and I'm using a different audio source (in my case, a VLC Video Source). It's like simply connecting the USB device on Windows 11 causes OBS to freak out. I can replicate the issue by plugging in/unplugging the HDMI Capture while VLC Video Source is playing, and hear the sputtering start and stop accordingly. Other applications do not have an issue with the HDMI Capture - for example, Zoom will treat it like a Microphone and the audio will come out flawlessly.

Because VB Cable works flawlessly with the VLC Video Source, and the HDMI Capture works flawlessly when directly plugged into Zoom, I'm left suspecting the issue is with OBS. In the logs, the HDMI Capture shows up as "Digital Audio Interface (2- USB3. 0 capture)"
 

Attachments

my tip is check you USb ports did you use Cam and Capture device in one scene

make a screenshot of this programm please and post it here


use voicemeter to make an mix i read you have voicemeter installed try this config !
1645702111149.png

1645702119233.png
 
Sorry for the late reply.
There is no camera source in this setup - the capture card is for the camera (which outputs it's video as HDMI).
I also don't have Voicemeter. It looks like it's made by the same developers who make the VB Cable, so maybe they mislabeled something in their log output.
 
I switched to using the NDI plug-in instead of VB Cable last night, and that seems like it's working better for audio. I'll have to do more testing to see if there's other drawbacks, but it might be a solution for anyone else having this issue.
 
You must log in or register to reply here.
Back
Top