ZuziaXx
New Member
Hello,
I want tell all video recorder grabber card is total new, i use it to stream on YT and play on nintendo switch2 using obs full screen becouse i can use hdmi port 2 in monitor but i dont want becouse i can use pc discord and play on swith or stream from my ps5 to one monitor without change anything more.
Im from Poland my english is not perfect then AI help me write this post using all my observation tests on my Nobara linux OS.
I would like to report an intermittent problem with USB HDMI capture cards in OBS Studio on Linux. I have tested two different capture cards, and both exhibit very similar behaviour.
Once the capture source is successfully initialized and all settings are configured, the capture can work correctly. However, the detection and initialization process is inconsistent.
I would like to know whether this could be related to OBS Studio's V4L2 device initialization, capability detection, or handling of capture devices when reopening a source.
Could the OBS developers help investigate this behaviour? If this is an OBS-side issue, I would appreciate a fix in a future release.
Thank you for your time and help.
I want tell all video recorder grabber card is total new, i use it to stream on YT and play on nintendo switch2 using obs full screen becouse i can use hdmi port 2 in monitor but i dont want becouse i can use pc discord and play on swith or stream from my ps5 to one monitor without change anything more.
Im from Poland my english is not perfect then AI help me write this post using all my observation tests on my Nobara linux OS.
I would like to report an intermittent problem with USB HDMI capture cards in OBS Studio on Linux. I have tested two different capture cards, and both exhibit very similar behaviour.
System configuration
- OS: Nobara Linux 44
- Desktop environment: KDE Plasma 6 (Wayland)
- OBS Studio: 32.2.1 (Flatpak)
- Hardware: AMD Radeon RX 9060 XT
- Capture driver: Linux UVC / V4L2
Capture cards tested
1. First capture card – MacroSilicon MS2109- USB ID: <span>534d:2109</span>
- Video device: <span>/dev/video1</span>
- Supports MJPEG capture.
- Tested with different USB ports and a USB extension cable.
- USB ID: <span>3142:0003</span>
- Identified by Linux as: <span>MACROSILICON fifine Video Capture</span>
- Uses the standard <span>uvcvideo</span> driver.
- Video and audio interfaces are detected correctly.
- USB connection speed: 480 Mbps (USB 2.0).
Problems observed
Both capture cards show very similar symptoms:- Linux detects the capture card, and it appears in <span>lsusb</span>.
- When OBS tries to access the capture device, the video feed may disappear.
- Sometimes the video returns automatically, but sometimes the device does not reappear correctly in OBS.
- The capture source settings (video format, resolution, FPS) sometimes disappear and are displayed as empty fields.
- The problem appears to occur when OBS initializes or accesses the capture device.
USB connection tests
I tested the FIFINE card in different configurations:- Front USB port without an extension: the device was sometimes not detected.
- Front USB port with a short USB 3.0 extension: the device was detected and appeared more stable.
- Rear USB port with the extension: the device was detected.
- Rear USB port without the extension: the device was also detected.
Additional observations
The issue is particularly frustrating because I have now tested two different capture cards, including a new FIFINE device, and both behave similarly.Once the capture source is successfully initialized and all settings are configured, the capture can work correctly. However, the detection and initialization process is inconsistent.
I would like to know whether this could be related to OBS Studio's V4L2 device initialization, capability detection, or handling of capture devices when reopening a source.
Could the OBS developers help investigate this behaviour? If this is an OBS-side issue, I would appreciate a fix in a future release.
Thank you for your time and help.