ASUS TUF Gaming Capture Box CU4K30 (4K, 1080p60, Low Latency Passthrough, Certified for OBS Studio, Plug & Play, USB Type-C, Record and Stream with PC, PS5, Xbox)

don't even hesitate when it comes to choosing this over the elgato. easy to connects/setup, no latency and it looks very cool. it gets very hot tho but all capture cards do, so u might need a small laptop cooler pad underneath. 10\10 product!

I have a late 2019 (fourth-generation) MacBook Pro running macOS 12.0.1 that only has USB-C thunderbolt ports. Connecting directly to various external 4K HDMI displays using Apple's "USB-C Digital AV Multiport Adapter" - surely the most official way to get HDMI output from these laptops - has always been rock solid.Unfortunately, if I route the HDMI output from the adapter through this capture card, the capturing lasts only a few seconds before the card's status light turns solid red ("HDCP/Upscaling or downscaling failure") and the capturing stops. (For what it's worth, whenever a display was connected to the card's HDMI output, passthrough to the connected display would continue to work uninterrupted even after capturing failed.) I tried capturing to a Fedora Linux 35 desktop and then to a Windows laptop, but capture failed with the same behavior for both. Both have USB-C 3.2 ports, as required.Messing around in the macOS display settings I **very** occasionally got capturing to work when the built-in display was set as the main display, the output was set as optimized for the MacBook Pro (as opposed to the capture card), and the output was 4K. Never for any other settings, and it was so rare it's almost not worth mentioning. In practice it seems this card simply can't be used to capture from a USB-C only MacBook Pro. (Actually an older MacBook Pro with macOS and and an actuall HDMI port 10.12 didn't even recognize the card.)ASUS, please provide a firmware update to fix the issue with Apple's adapter! (I have the latest firmware installed - USB firmware 01.04.05.02.0001 and MCU firmware 06.19.00.)I should also mention that I tried a different USB-C thunderbolt to HDMI adapter but the behavior was the same.Ironically, macOS was the only OS to recognize the card out of the box. Up to date Windows 10 and Fedora Linux 35 both failed to recognize it at all until I updated the firmware on the card. Note that the firmware updater only runs on Windows, so Linux users may find that problematic!Capturing from Windows 10, from Linux and from a Panasonic camera, all worked, albeit at a limited number of **capture** resolutions. Initially I thought that when capturing from the Linux computer the capture card only worked when Linux was **outputting** the following resolutions:3840 x 2160 (16:9)1920 x 1200 (16:10)1600 x 1200 (4:3)Changing the Linux display settings to output any other resolution would cause the card's status light to turn solid red and output a stream with the text "Not support".However, it seems that the issue is that the card just requires the resolution that the **capturing** software asks for is compatible with its upscaling/downscaling logic for the resolution being captured. In my case, the Windows Camera app simply wasn't automatically adjusting to request a compatible resolutions that the card can output when the Linux display resolution was changed. (When reversing the capturing so that I was capturing Windows from the Linux computer, the Linux Cheese app would automatically adjust just fine. OBS would not, however, and needed to have the resolution it captured at explicitly set to a supported resolution.)The resolutions that the card can output appear to be:3840 x 2160 (16:9) - 30fps only, and not as YUYV 4:2:22560 x 1440 (16:9)1920 x 1080 (16:9)1280 x 720 (16:9)720 x 576 (4:3)40 x 480 (4:3)Finally, it's worth noting that the output resolution from the captured computers could successfully be changed on the fly (so long as the capturing software automatically - or was manually - adjusted to capture at a supported resolution) and capturing would continue without needing to unplug and replug the card.