Skip to content

Capture Card Elgato 4Kx

Likely7 edited this page Nov 9, 2026 · 2 revisions

Community reference (2026-11-05 snapshot). Check the latest drivers, firmware and individual model revision. All capture cards · Troubleshooting

Capture Card · Elgato 4K X


Capture Card-Elgato (4K X-4K60ProMK2-4K Pro)

Capture Card Volume · Elgato (called "伊卡图/伊图卡" in the group) [In-depth Edition]

[Naming note] "伊卡图/伊图卡/一卡图" in the group = a phonetic nickname for Elgato, the same brand as "elgato".

Covers three models: 4K X (USB) / 4K60 Pro MK.2 (older PCIe model) / 4K Pro (new PCIe model) One-line positioning: the two PCIe models are one of the standard answers for "4K60HDR maxed out" and are widely regarded as having "fewer weird little problems"; the USB 4K X is "the lowest latency among USB cards"; but the whole line carries a motherboard compatibility warning — read Chapter 4 Q4 before buying. Last updated: 2026-10-06 (in-depth rewrite)

════════════════ 0. The 30-second verdict ════════════════ [Who it's for] Users who want 4K60 HDR + low latency + 10-bit color, don't want to tinker (versus the GC573), and have a budget of 1000-2700 [Who it's not for] Users who need Dolby 5.1 multichannel (the entire Elgato line is stereo), users who need the 7-day no-questions-asked guarantee but can't buy through official channels [In one sentence] "It seems Elgato has fewer of those weird little problems" (group member r); "if you want 4K60HDR maxed out there are basically only two choices,

════════════════ 1. Models and spec table ════════════════

════════════════ 2. Recommended settings (follow step by step) ════════════════

  1. [Official software (4K Capture Utility)] Install it and open it once; then go into settings: ★Turn off "Auto HDR to SDR" (it's actually on by default, and buried deep — "you have to turn it off, otherwise it sometimes goes red")
  2. [Windows] Turn on system HDR (the first place to check when colors are wrong — the 柯基 case: in the end it turned out Windows HDR had been turned off)
  3. [PS5] Turn off HDCP; resolution 2160p/60Hz; connect to the capture card's IN port, OUT to the monitor
  4. [Capture format] For HDR you can only pick P010 ("only p010 and p016 have hdr"); use NV12 for SDR
  5. [In Veyra] Input color: manually specify PQ hdr10 (don't use auto — "just do it manually, auto has problems")
  6. [Colors still wrong] Work through the six steps in Chapter 4 Q1 one level at a time

════════════════ 3. ★Complete troubleshooting manual for common problems (ready to copy and use) ════════════════

── Q1 [Most frequent · the thing group members ask constantly] 4K60 P010 HDR colors are wrong: specifying PQ manually overexposes, specifying HLG goes red/dark, but capturing in the card's official software is fine — what do I do? [Symptom] Colors are wrong in Veyra with HDR (P010) (overexposed / red tint / tone mapping still SDR); OBS and the Elgato official software are fine. "I open veyra and the colors are still wrong" "why is the tone mapping still SDR" "it feels too bright" (柯基的小面包, 2026-10-03). [Cause] This kind of "fine in the official software, wrong in Veyra" problem is diagnosed in the group as an HDR/WCG metadata transmission compatibility issue between the capture card and the DirectShow pipeline (Aitor's exact words after looking it up with GPT: "the GC573 can output HDR P010 pixel data, but the DirectShow source filter doesn't pass HDR/WCG metadata correctly, so the downstream renderer doesn't know how to interpret the picture"); the author's diagnosis is that "they're all compatibility problems", and he notes "Elgato had this problem before too; later I hooked up an open-source Elgato capture app and it was fine". [Solution] Try these in order (the first four steps cover every case that has worked in the group): Step 1: Open the Elgato official software (4K Capture Utility) → Settings → turn off "Auto HDR to SDR" —— Hi stressed it twice: "remember not to turn on that elgato auto hdr to sdr setting" "you have to turn it off, otherwise it sometimes goes red"; "it should be off to begin with" "it's on automatically, the official app is a bit dumb" "it quietly turns it off for you, and it's even buried in there" Step 2: Open the official software once (the "official software warm-up method") —— The group owner's own words: "seems you have to download the official software"; a similar case in the neighboring group: "open the AVerMedia official software once and it's normal" Step 3: The OBS warm-up method (30 seconds, do it once every boot; most verified by 573 users, and the author agrees it "may also cover other capture cards") ① Open Veyra first and confirm the colors are wrong (optional); ② Open OBS → add a capture source → click "Custom" (if you don't, P010 is greyed out and you can't select it — a group member's documented pitfall) → set Color Format to P010 and Color Space to REC.2100 PQ; ③ Close OBS; ④ Reopen Veyra → HDR colors are back to normal. His exact words (Aitor): "I repeated the test, and it can fix the GC573 (and possibly other capture cards) when HDR colors go wrong. You have to redo it after every boot: the first time you open veyra after booting, the HDR colors are wrong; then open OBS, set the capture input's color format and color space to P010 and REC.2100 PQ, then close OBS; reopen veyra and HDR is back to normal" Step 4: Make sure the three basics are all correct: ① The capture format is P010 ("only p010 and p016 have hdr" — the author) ② In Veyra, input color is manually set to PQ hdr10 ("hdr can only select p010, input color select PQ hdr10" — Aitor; "just do it manually, auto has problems" — the author) ③ Windows system HDR must be on (this is exactly where the 柯基 case failed in the end: "when did I turn it off" → "turned it on and it was fine"; "did you turn on hdr in windows?" — Hi) Step 5: Still not working → the related tool from the group (an open-source DirectShow metadata injection filter, made specifically for the 573 issue): https://github.com/defl/directshow_metadata_injector_filter Step 6: Report the bug to the author: zip up the logs folder in the root directory and @Likely7 ("there used to be cases where some capture cards had a red HDR tint, I need to look into this one" "noted in my little bug book") [PS] The lazy option: skip the software and just play off the passthrough ("playing directly off the capture card doesn't have this problem" — 酱油拌饭); or, if you don't ask much of HDR, go SDR (4K60 NV12 — Elgato is very stable in SDR).

Upgrading Elgato Studio to 2.0 beta also brings a driver update for the capture card; once that's done it's fine.

── Q2 Veyra shows "tone mapping still SDR" / the whole image is overexposed / too dark [Three-step check]

  1. Is the HDR switch in Veyra on (柯基: "oh, got it, the HDR here needs turning on too")

  2. Is Windows HDR on (the most common failure point, see Q1 step 4 ③)

  3. Is the capture format P010 + is the input color set to manual PQ [Note] If the console is already outputting HDR but Windows HDR is off, you get "that overexposed brightness feeling" (柯基's own words)

── Q3 What must be turned off in the Elgato official software?

  1. "Auto HDR to SDR": must be off (on by default, buried deep, several users have been caught out)

  2. Remember to do the official-software warm-up once (one open is enough, see Q1 step 2)

── Q4 [AMD platform compatibility — community feedback] Does the 4K X work on AMD?

Yes, AMD is not categorically unsupported. Veyra members have reported using the Elgato 4K X on AMD systems, including a Ryzen 9 9950X3D + X870E setup and a Ryzen 7 9800X3D setup.

An older second-hand claim about the 4K Pro was incorrect: a documented 4K Pro test on Ryzen 7 9800X3D + MSI X670E confirmed successful operation. The PCIe-specific considerations for that card do not apply directly to this USB capture card.

For a 4K X USB connection issue, check that the card uses a suitable USB 3.2 Gen 2 port/cable, update drivers, and try another controller. Individual issues should be diagnosed by hardware configuration rather than by CPU brand.

── Q5 Elgato 4K X (USB version) specifics

  1. Community members report working 4K X setups with Ryzen 9 9950X3D and Ryzen 7 9800X3D; AMD is not inherently unsupported.

  2. "Veyra tops out at 1080p120, but OBS/the official software can do 4K60" (group member 0932's case, not resolved): check in this order: update Veyra to the latest version → use USB Tree Viewer to see the actual negotiated rate (星's suggestion) → try a direct USB-C connection (they've confirmed it's a 3.2 Gen2/Thunderbolt port) → compare the input properties in OBS → zip the logs and send them to the author

  3. Format ceiling: 4K60 only in SDR (NV12); 4K30 HDR; "a shame HDR capture tops out at 2K60 or 4K30"

  4. VRR: VRR can be enabled in 4K120 SDR mode, with RTX HDR filling in HDR (Eric™'s approach)

  5. "I don't even turn on low-latency mode on the 4kx and I can't feel any latency" (three strikes)

── Q6 How do I choose between the three models? (a frequent dilemma)

  • Want USB + low latency + don't care about HDR capture: 4K X ("the lowest latency / the ceiling among USB cards")

  • "buying the direct-plug one is all about hdr, 4k can hit 60" (Hi)

── Q7 Latency data (group test summary)

  • 4K X: about 35ms (a YouTube review: 4kx ≈ 35ms vs 553g2 ≈ 59ms)

  • "is there a big latency gap between the new Elgato and the 573" → "no difference in latency" (Hi, 2026-09-29)

  • Direct-plug 4K60HDR: 12-32ms (Hi)

── Q8 HDR-related specs

  • "for hdr you can only capture p010" "to judge a capture card's hdr, look at the p010 format" (Hi)

  • 4K X: 4K60 SDR, 4K30 HDR

── Q9 Prices and channels (market at the time of writing)

(600 cheaper than the official store) / used 1350-1600 ("the ones listed at 1K on Xianyu are basically scammers")

  • 4K X: JD 1999 / Amazon 1600-1700 / JD Global 1750

  • Return warning: the domestic distributor is gone, and once opened, incompatibility isn't covered by 7-day no-questions returns (Pythagoras); prefer returnable channels like JD

── Q10 How do I confirm HDR is actually on? ① The HDR switch in Veyra is on; ② Windows HDR is on; ③ capture format is P010; ④ input color is manual PQ hdr10; ⑤ compare with OBS: OBS fine but Veyra not → use the OBS warm-up method from Q1

════════════════ 4. Known bugs and official progress ════════════════

  • HDR color/metadata issue: the author confirms "Elgato had this problem before too" and "they're all compatibility problems"; back then it was solved by "hooking up an open-source Elgato capture app"; still being investigated for the 573 (2026-09-26)

  • The official software having "Auto HDR to SDR" on by default is a known counter-intuitive setting (Hi grumbles that "the official app is a bit dumb")

  • The 4K X capping at 1080p120 in Veyra: an isolated case, not resolved

════════════════ 5. Selected quotes from group members ════════════════

  • "It seems Elgato has fewer of those weird little problems" (r, summing up after a whole round of tinkering)

  • "The Elgato 4K X is probably the lowest-latency usb option, lower than most pcie cards" (有梦想的人不睡觉)

  • "remember not to turn on that elgato auto hdr to sdr setting" "you have to turn it off, otherwise it sometimes goes red" (Hi) ================================================================ (Same root cause as the GC573 HDR issue; for the full procedure see "Capture Card - AVerMedia GC573", Chapter 3 Q1)

Cross-model attribution: A detailed Ryzen 7 9800X3D + MSI X670E CARBON WIFI report in the archived notes refers to the PCIe Elgato 4K Pro, not this USB 4K X. See the 4K Pro community test. The 4K X has its own AMD success reports listed in Q4 above.

This update and expansion (2026-10-06 ~ 11-05)

Filtered from the records of 7 chat groups, 2026-10-06 ~ 11-05; 74 relevant messages in total, with speakers and dates kept.

  • The lowest latency tier among USB cards (about 35ms), supports VRR; Veyra members have reported successful AMD-based setups.
  • The Elgato line has a black screen when capturing RGB issue (YK 10-10); verify with NV12 first.

Fixes and reminders

  • Capture Card-Elgato (4K X-4K60ProMK2-4K Pro).txt (the author, 10-06)
  • I originally wanted to buy the 573, but after finding this problem I switched to the 4KX; I had a friend buy it in Japan, it was cheaper than domestically, but I have to wait for them to bring it back. I saw people saying the USB ones don't work, so I'm asking (Hollowness 10-14)
  • Didn't pay attention to the 4kpro; the 4kx is about 300 more expensive on JD and Amazon (Hollowness 10-15)

Group members' own words

"If it's 30ms latency too, there's no point bothering with the 4k x — all cards are created equal then"

—— Focus (10-06)

"But if the 4k x turns out about the same as the g2 it'll be awkward — 300 more expensive, no warranty, and the overseas version can't be returned either [旺柴]"

—— Focus (10-07)

"My last hope now is that if the Elgato 4k x is clearly lower latency than the g2 and close to pcie, I'll get one — though it's not very likely"

—— Focus (10-08)

"The first one I bought was the 4kx.. 10 minutes later I regretted it and switched plans.. ordered the 4k pro as well, and the first one can't be returned anymore.. overseas version [捂脸]"

—— 杨雷 (10-08)

"My 4kx arrived yesterday, the perceived latency is okay"

—— 无敌Siuuu.... (10-10)

"the latency of the 4kx capturing 4k60nv12"

—— 无敌Siuuu.... (10-10)


Related reading: 03 Capture Card Buying Guide · 04 Capture Card Analysis · 07 M.2 to PCIe · 08 PCIe Riser Cables

Clone this wiki locally