Intermittent USB Capture Card Detection and Video Loss in OBS Studio on Linux

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.

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.
2. Second capture card – FIFINE Video Capture

  • 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.
An important observation: even when the video disappears in OBS, the FIFINE capture card can remain visible in <span>lsusb</span>. This suggests that the entire USB device is not necessarily disconnecting.

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.
The extension cable seems to improve connection reliability, but it does not explain the intermittent video loss inside OBS.

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.
 
First i think maybe my back panel and USB port is damaged because when i connect first cheaper card to USB in back panel device show many connect and disconnect message. But on second card was same. In front panel all work but only when i use another cable USB A in to USB A out connected to front panel and then OBS is more stable showing both cards and i can setup all correctly, if i use orginal cable without extended usb cable then problem back and OBS see card 2 secound then disapear again and i see only device name like here:
Error detect card.
OBS Error.png
Or good like on screen below.

But still not perfect becouse sometime i must change resolution or restart obs to see image from switch 2 in dock.
or i see one frame then i know image is freeze after mix setting all back to normal.

This fifinie can stream with FHD and 50 fps, and display image in QHD on monitor.
but now im rly dont know this is OBS problem with V4L2 or my pc usb :( but i think not mouse keyboard and mic also i have in back panel and all work normal. Only this 2 capture card not.

This is all what i can tell now. If You need more info please tell me. I rly want make OBS Perfect becouse this is rly anoing problem. If i not use that usb extension cable i never can use any device in obs normal becouse thiw 2 cards will be visable only fiew secound and then disconect and connect again.

Cheers from Poland :)
 

Attachments

  • Zrzut ekranu_20261115_093722.png
    Zrzut ekranu_20261115_093722.png
    197.7 KB · Views: 6
Last edited:

Update – FIFINE capture card on Linux / OBS​

I have moved the capture card to a different USB port on the rear I/O panel of my motherboard. It is now connected directly, using the original USB cable, without any USB extension cable.

The card is detected and works in this port, but I am still experiencing some issues:

  1. No video after switching on the Nintendo Switch 2: Every time I turn on the Switch 2, I have to open the capture card's properties in OBS and change the resolution to make the image appear. For example, I switch from 1920×1080 to 1280×720 and then back to 1920×1080. After doing this, the video works normally.
  2. Intermittent audio problems: Sometimes there is no audio from the capture card. After several attempts, such as restarting OBS or restarting the Nintendo Switch 2, the audio eventually comes back.
  3. The problem is not completely resolved: Changing the USB port and removing the extension cable has improved the connection situation, but the video and audio initialization problems remain.
It seems that OBS may not be initializing the capture card correctly when the Nintendo Switch 2 is powered on or its HDMI signal becomes active.

Could this be related to how OBS handles UVC capture devices or HDMI signal re-detection? Would it be possible to improve this behaviour so that users do not have to manually change the capture resolution every time they turn on their console?

Additional diagnostic information from the OBS log​

I have attached an OBS log showing several capture errors.

The log confirms that OBS correctly detects the FIFINE capture card and configures it for MJPEG at 1920×1080, 50 FPS. However, the initial capture attempts fail with:

  • <span>decoder: failed to send frame to codec</span>
  • <span>failed to unpack jpeg or h264</span>
  • <span>Stopped capture after 0 frames</span>
Switching the capture resolution to 1280×720 at 60 FPS allows the device to capture frames successfully. Switching back to 1920×1080 at 50 FPS also temporarily restores video.

However, the problem can occur again during operation. The log later shows repeated <span>select timed out</span> errors, followed by PipeWire stream errors and another JPEG decoding failure. Capture eventually stops after 1290 frames.

This suggests that the issue may involve MJPEG frame delivery, decoding, or V4L2 capture recovery when the HDMI signal is interrupted or re-detected.

The capture card's audio device is detected, but I still occasionally experience missing audio. The attached log does not clearly identify the cause of the audio issue.

System information:

  • OBS Studio 33.0.1 (Flatpak)
  • Nobara Linux 44
  • KDE Plasma / Wayland
  • Linux kernel 7.3.1
  • AMD Radeon RX 9060 XT
  • FIFINE Video Capture (MacroSilicon UVC device)

    The full OBS log file is attached for further investigation.
    i add log to Attach files.

    Thats all what i can do, i also try fifne with Cheese app and work normal without any problem and config i instant see image from switch2 only using video mode.
 

Attachments

My Final Question is:

FIFINE AmpliGame V3 – 1080p60 unavailable on Linux (Nobara KDE)​

I'm trying to use a FIFINE AmpliGame V3 capture card with OBS Studio on Nobara Linux 44 (KDE Plasma, Wayland).

The manufacturer advertises USB 3.0 connectivity and 1080p60 capture. However, on my Linux system, the device is detected as USB 2.0 and does not expose 1080p60 as an available capture mode.

System information:

  • OS: Nobara Linux 44
  • Kernel: Linux 7.3.1-202.nobara.fc44.x86_64
  • Desktop: KDE Plasma / Wayland
  • OBS Studio: Flatpak
  • Capture device: FIFINE Video Capture
  • USB ID: <span>3142:0003</span>
  • Graphics: AMD Radeon RX 9060 XT
USB diagnostics:

The device is detected at High Speed (480 Mbps), rather than SuperSpeed (USB 3.x).

The USB device descriptor also reports <span>bcdUSB 2.00</span>.

V4L2 capture modes:

Running:

<span>v4l2-ctl -d /dev/video1 --list-formats-ext</span>

shows the following maximum frame rates:

  • MJPEG 1920×1080: 50 FPS
  • MJPEG 1280×720: 60 FPS
  • MJPEG 1360×768: 60 FPS
There is no 1920×1080 at 60 FPS in the list of modes exposed by the device.

I also created a completely new Video Capture Device source in OBS and selected the actual FIFINE capture device. The available Full HD frame rate was still limited to 50 FPS.

My questions:

  1. Could this be related to the Linux UVC (<span>uvcvideo</span>) driver or V4L2 compatibility?
  2. Is there anything OBS can do to improve compatibility with this capture card?
  3. Could OBS developers help determine whether the device is incorrectly reporting its supported USB speed or video modes to Linux?
I understand that the manufacturer does not officially list Linux support, but the device uses USB Video Class (UVC), so I would appreciate any advice on whether this can be investigated or improved on the Linux side.

I can provide the complete USB descriptor output and OBS logs if needed.

Thank you for your time.
 
Back
Top