You are not logged in.

Pages: 1

#1 2023-02-06 15:21:54

Noitibmar
Member
Registered: 2023-02-06
Posts: 1

Elgato HD60 X Game Capture Card sends a single image then hangs

I've used the Camlink 4k many times in the past on this same computer and it works just fine as a UVC device,
so I was not expecting to have troubles with the HD60 X as it's also listed as working as a UVC device and people online seem to have said it's fairly plug and play.

But when I try to access the device from OBS or Discord, it sends a single image through and then nothing else until I reboot the machine.

dmesg | grep 'usb 4.1.3' I think should have all the relevant info

[    4.595084] usb 4-1.3: new SuperSpeed USB device number 3 using xhci_hcd
[    4.616715] usb 4-1.3: LPM exit latency is zeroed, disabling LPM.
[    4.620972] usb 4-1.3: config 1 has an invalid interface number: 7 but max is 4
[    4.620977] usb 4-1.3: config 1 has no interface number 4
[    4.620981] usb 4-1.3: Int endpoint with wBytesPerInterval of 1024 in config 1 interface 7 altsetting 0 ep 135: setting to 512
[    4.622973] usb 4-1.3: New USB device found, idVendor=0fd9, idProduct=0082, bcdDevice= 1.00
[    4.622976] usb 4-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.622978] usb 4-1.3: Product: Game Capture HD60 X
[    4.622979] usb 4-1.3: Manufacturer: Elgato
[    4.622981] usb 4-1.3: SerialNumber: MX20L1A23665    
[    5.341780] usb 4-1.3: Found UVC 1.10 device Game Capture HD60 X (0fd9:0082)
[   29.471325] usb 4-1.3: Failed to query (GET_RES) UVC control 2 on unit 2: 1 (exp. 2).
[   29.473324] usb 4-1.3: Failed to query (GET_RES) UVC control 3 on unit 2: 1 (exp. 2).
[   29.475332] usb 4-1.3: Failed to query (GET_RES) UVC control 7 on unit 2: 1 (exp. 2).
[   29.477298] usb 4-1.3: Failed to query (GET_RES) UVC control 6 on unit 2: 1 (exp. 2).

From this it looks to me like it's not reporting a resolution? but I have no idea if that's the real problem or where to go from this.

Offline

#2 2023-07-27 17:05:04

dbb
Member
From: New York City
Registered: 2008-12-14
Posts: 31
Website

Re: Elgato HD60 X Game Capture Card sends a single image then hangs

I was experiencing the same issue with a recently acquired Elgato HD60 X, with the following symptoms:

dmesg messages like:

[ 6148.929665] usb 5-1: Failed to query (GET_RES) UVC control 2 on unit 2: 1 (exp. 2).
[ 6148.943666] usb 5-1: Failed to query (GET_RES) UVC control 2 on unit 2: 1 (exp. 2).
[ 6148.960664] usb 5-1: Failed to query (GET_RES) UVC control 2 on unit 2: 1 (exp. 2).
[ 6148.976665] usb 5-1: Failed to query (GET_RES) UVC control 2 on unit 2: 1 (exp. 2).
[ 6149.014663] usb 5-1: Failed to query (GET_RES) UVC control 2 on unit 2: 1 (exp. 2).

Output from v4l2-ctl --list-formats-ext:

ioctl: VIDIOC_ENUM_FMT
        Type: Video Capture

        [0]: 'YUYV' (YUYV 4:2:2)
                Size: Discrete 720x576
                        Interval: Discrete 0.017s (60.000 fps)
                Size: Discrete 720x480
                        Interval: Discrete 0.017s (60.000 fps)
                Size: Discrete 640x480
                        Interval: Discrete 0.017s (60.000 fps)
        [1]: 'NV12' (Y/UV 4:2:0)
                Size: Discrete 1280x720
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 720x576
                        Interval: Discrete 0.017s (60.000 fps)
                Size: Discrete 720x480
                        Interval: Discrete 0.017s (60.000 fps)
                Size: Discrete 640x480
                        Interval: Discrete 0.017s (60.000 fps)

And the red LED initially flashing blue and then blinking red.

I have an Asus ProArt X670E-CREATOR WIFI motherboard and after a bunch of experimenting what I discovered was:

  • It does work as normal when plugged into any of the rear USB 3 Type A or Type C ports.

  • It does not work as normal when plugged into the (only) rear USB 2 Type A port.

  • It does not work as normal when plugged into any of the USB 3 Type A ports or the Type C port on the front panel (which are connected directly to motherboard headers).

  • However, it does work as normal when plugged into a powered USB hub which is then plugged into one of the USB 3 Type A ports on the front panel.

  • The behavior is the same between Windows 10 and Arch.

When working there are no GET_RES failures in dmesg, the output of v4l2-ctl --list-formats-ext is significantly more comprehensive:

ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

	[0]: 'YUYV' (YUYV 4:2:2)
		Size: Discrete 1920x1080
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 1600x1200
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 1280x720
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 720x576
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 720x480
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 640x480
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
	[1]: 'NV12' (Y/UV 4:2:0)
		Size: Discrete 3840x2160
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 2560x1440
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 1920x1080
			Interval: Discrete 0.008s (120.000 fps)
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 1600x1200
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 1280x720
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 720x576
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 720x480
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)
		Size: Discrete 640x480
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.020s (50.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.040s (25.000 fps)

And the LED turns pinkish-white after flashing blue rather than blinking red.

My working theory is that the front panel connectors on my motherboard aren't delivering enough power for it to work correctly when connected to those ports. I find this kind of odd, however, especially the Type C port which is at least able to deliver enough power to trigger the "Charging rapidly" status on my phone.

My recommendations if this is still an issue months later or you're another passerby that happened on this topic when searching like I did are to:

  • Try different ports.

  • Try different cables (my initial testing with Type C cables actually failed, because I unintentionally used a "charging" cable only specified for USB 2.0).

  • Try a powered USB hub.

Last edited by dbb (2023-07-27 17:05:43)

Offline

Pages: 1

Board footer

Powered by FluxBB