Question / Help Capture Card Skipping on Loading Screens

F

fullmoon8

New Member
Hello
Recently I have been streaming Nintendo Switch gameplay with a Roxio Gamecap HD Pro using OBS. It works alright for the most part, however I have been having an issue where the video/audio will stutter whenever the screen fades black and enters an in-game loading screen. I am not sure what is causing this issue.

Looking at a log file, I found that a little while after opening OBS, I get a Max Audio Buffering Reached error from my video capture source (the capture card). Does anyone know how to fix this? I do not think the issue is from high CPU usage, because it looks like I'm only using 10%-15% most of the time.

Here is a log file https://obsproject.com/logs/SqUdZXLmYimKW_tS

Thank you
 
Narcogen

Narcogen

Active Member
If it's not CPU then it's likely USB bandwidth. Check there are no other devices on this controller, and if you're getting full speed to the device.

22:52:14.153: adding 626 milliseconds of audio buffering, total audio buffering is now 673 milliseconds (source: Video Capture Device)
22:52:15.899: adding 23 milliseconds of audio buffering, total audio buffering is now 696 milliseconds (source: Video Capture Device)
22:52:16.892: obs-browser: Uncaught (in promise) No response from Twitch. (source: https://v1.warp.bar/v3/js/index.min.js?v=1.65:16)
22:52:26.108: adding 255 milliseconds of audio buffering, total audio buffering is now 952 milliseconds (source: Video Capture Device)
22:52:27.004: Max audio buffering reached!
22:52:27.004: adding 92 milliseconds of audio buffering, total audio buffering is now 1044 milliseconds (source: Video Capture Device)
 
FerretBomb

FerretBomb

Active Member
You can use the USBView utility to easily see which devices are on which USB host controller: https://obsproject.com/downloads/usbview.zip
That does sound like USB bandwidth choke; excessive audio buffering and audio "robotting" is one of the most obvious symptoms. I'm not sure why it would only happen on loading screens though, unless something about the fullscreen gradient-fade is making the capture card need more at that point.
 
F

fullmoon8

New Member
Hi! Thank you very much for the help.

I downloaded a usbViewer, and noticed something that might be wrong with my usb ports. Here is what is shown in usbViewer:
https://i.gyazo.com/aeaae8371bcb53b325e532438da41940.png

I noticed that under "SupportedUsbProtocols," is shows that only usb110 and usb200 are supported. Does this mean that USB 3.0 is not working properly? My usb port should be capable of it, as there is an "SS" printed next to the usb port.
 
Narcogen

Narcogen

Active Member
Yes, that is what that sounds like, and it would definitely cause your issue. Reliable HD capture pretty much requires USB 3.
 
FerretBomb

FerretBomb

Active Member
Sounds like the issue. Some motherboards require turning USB 3 support on in the BIOS; this is usually because the USB 3 host controller shares PCIe lanes with another device (PCIe slot, SATA controller, m.2 SSD slot, wifi, etc) and running in USB 3 mode will cause that other device to not function at all, or with reduced speed/ports/etc. You'll need to check your motherboard's manual to see if that's the case, if it will affect your setup, and where to en/disable USB 3 mode in the system BIOS.
 
carlmmii

carlmmii

Active Member
The "no" that you're looking at there is 100% normal. Not sure of the reasoning why, but checking my own view of the usbtree shows the exact same behavior.

That wouldn't even matter anyway -- the capture card you're using is a USB2.0 capture card, meaning it wouldn't benefit in any way from being connected to a fully functioning USB3.0 port (yours is probably actually fine).

Keep in mind, this is a capture device from 2012, with some very old quirks. I would see of you have the same behavior using the Roxio software that it comes with, if you still have that available. I remember when I used this exact same capture device that it was very finicky using anything other than their own capture "suite".

If it does have the same issues, then that most likely is an indication of something going wrong with the USB bandwidth, or the capture device just isn't able to perform its h264 encoding (possible overheating of the unit, which could be caused by heatsink failure over time).
 
F

fullmoon8

New Member
Hi!
It's been a little while, but I thought I should give an update.
I ended up getting an Elgato hd60 S off ebay instead, and everything is working fine now.
With the other capture card, the issue was happening within it's own software as well, so I believe it was just an issue with the card being older.

Thank you all very much for the help :)
 
You must log in or register to reply here.
Top