Capture Card Elgato 4Kpro

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

Capture Card · Elgato 4K Pro

AMD compatible — verified by a Veyra community member. An AMD Ryzen 7 9800X3D + MSI MPG X670E CARBON WIFI (BIOS 1.S3) system successfully ran the Elgato 4K Pro in PCI_E3, with 4K60 HDR P010/RGB24 capture and Veyra NR + DLSS 2× interpolation. This directly disproves a blanket claim that the 4K Pro cannot work on AMD. Compatibility still depends on the specific PCIe slot, BIOS, and driver configuration. See the detailed test report below.

---

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"; 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, the AVerMedia GC573 or the Elgato 4K60 PRO MK2" (Aitor); "commercial use aside, this thing is the strongest" (Hi, referring to the 4K Pro)

════════════════ 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. The same symptoms show up on the GC573 as "PQ overexposed, HLG red" (Aitor); on the 4K Pro they show up as "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).

Fix for the red HDR tint on the new 4kpro Upgrading Elgato Studio to 2.0 beta 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 verified] Will the 4K Pro work on an AMD motherboard?

Yes. The Elgato 4K Pro has been tested successfully on AMD. A Veyra community member used a Ryzen 7 9800X3D and MSI MPG X670E CARBON WIFI with the 4K Pro installed in PCI_E3. Veyra captured 3840×2160 60fps HDR P010 and RGB24, and NR plus DLSS 2× interpolation worked. The full test record is further down this page.

Older seller/support warnings that broadly characterized AMD as incompatible should not be presented as the compatibility verdict. Some individual systems have shown card-detection or image problems, but those reports do not establish platform-wide incompatibility.

If a particular PC fails to detect the card, check PCIe slot bandwidth and lane sharing, reseat the card, update the BIOS and capture-card driver/firmware, and test another slot. Confirm the return policy as you would for any PCIe expansion card.

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

• Want 4K60HDR + lowest latency + PCIe: MK2 (the "value king" of the thousand-yuan used market) or 4K Pro (new HDMI2.1 + VRR)

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

• "the old mk2 or the new 4kpro" (Hi); "if you want it cheap, buy the old elgato, or the 573" (Hi)

• Note: "the difference between the MK2 and the non-MK2" → "only the MK2 can record HDR" (Aitor)

── Q7 Latency data (group test summary)

• "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)

• MK2/4K Pro are both 10bit (by contrast, the 573/ASUS 4KPRO are 8bit and get called out for it)

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

• 4K Pro: 2700 official / 2600 flagship store / 2699 China-market with two-year warranty / 2083 on JD Amazon Global (600 cheaper than the official store) / used 1350-1600 ("the ones listed at 1K on Xianyu are basically scammers")

• 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")

• Motherboard recognition issue: two cases of the 4K Pro not being recognized (counted by Hi); no firmware-level fix information

════════════════ 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)

• "commercial use aside, this thing is the strongest" "it could even max out the ps6" (Hi, on the 4K Pro)

• "T0 tier" "for the average gamer the 4kpro is already top-level" (蚂蚱儿)

• "nobody writes that the Elgato 4k pro needs hdr-to-sdr turned off in its bundled software" "and nobody writes that the mk2 needs the frame rate changed to 59.94 either" (Hi)

• "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)

Adding a successful test report from a group 4 member with an AMD AM5 + MSI motherboard + the new Elgato 4K Pro, for the group doc's reference. Test date: October 2026.

My configuration:

• CPU: Ryzen 7 9800X3D

• Motherboard: MSI MPG X670E CARBON WIFI

• BIOS: 1.S3, corresponding to 7D70v1S3, the 2026-09-11 version

• GPU: RTX 5080, installed in the topmost PCI_E1

• Capture card: the new HDMI 2.1 Elgato Game Capture 4K Pro, installed in the bottommost PCI_E3 (the chipset-provided PCIe 4.0 ×4 slot)

• Signal source: Nintendo Switch 2

• Software: Elgato Studio, Veyra

Verified so far:

1. The capture card is recognized and outputs a picture normally. Elgato Studio's signal details show both HDMI input and recording output at 2160p60 HDR.

2. Veyra has actually been tested and does receive 3840×2160 60fps HDR P010, and also 3840×2160 60fps RGB24.

3. NR image enhancement and DLSS 2X frame interpolation both run in Veyra. The screenshot shows a source frame rate of 60.00fps and a color path of HDR→HDR10/PQ, with the "skipped source frames" counter at 0 at the time. The interpolation target is 120fps; the actual displayed frame rate needs to be measured separately.

PCIe/MPS was also read:

• The 4K Pro's current link is PCIe Gen2 ×4, which is the capture card's own link ceiling.

• The 4K Pro's Supported MPS = 512B, Current MPS = 128B, MRRS = 512B.

• On the same machine, the RZ616 Wi-Fi is 128B/128B and the Realtek 2.5GbE is 256B/128B.

So my machine ran the capture modes above and Veyra's post-processing with the 4K Pro's Current MPS still at 128B. You can't conclude from a 128B MPS alone that this card can't be used for 4K60.

This feedback can be logged as "X670E CARBON WIFI + 9800X3D + BIOS 1.S3 + bottommost PCI_E3, verified working". The conclusion is limited to this machine and the modes above; it doesn't mean all AMD/MSI motherboards are free of compatibility issues, nor that long-term zero-dropped-frame certification has been completed. And since there was no control test with the old BIOS, this can't be taken as proof that updating the BIOS fixed compatibility.

---

This update (2026-11-05)

• There's a fix for the red HDR tint: "upgrade Elgato Studio to 2.0 beta; it brings a driver update for the capture card, and once that's done it's fine" (热心的猫舌头💡 10-07), and the author said on the spot that he'd write it into the doc.
• Note: earlier that same day the author had said "I tried to fix this thing with no luck, use the OBS warm-up method for now" — so the order is: turn off "Auto HDR to SDR" → upgrade to Studio 2.0 beta → OBS warm-up.

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

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

• There's a fix for the red HDR tint: "upgrade Elgato Studio to 2.0 beta, it brings a capture card driver update, once that's done it's fine" (热心的猫舌头💡 10-07).

New questions & answers

Q1: @宇宙最强采集卡:华硕4KPro how do I download this (🤫 10-23)

A: @宇宙最强采集卡:华硕4KPro @variable try it and see whether the new version is stable (Likely7 10-27)

Fixes and reminders

• Yesterday I was just about to buy a gc573, and today I saw the elgato 4k pro discounted to 1500-something on Amazon Global; if you're okay with cross-border buying, you can get it. (Illidan 10-06)
• I returned both of my 4kpros; my computer couldn't recognize them even with the driver installed (阿莫视觉 10-24)
• Let me give an example: say I'm playing Onimusha, which has a vrr mode, but vrr only works with 120hz enabled. If the capture card doesn't support 4k120hz capture, then you can only enable 1080p120hz to use vrr. The 4kpro can do 4k120hz with vrr, but then you're stuck with nv12, no HDR, and the picture... (A 10-24)
• Mainly it's for face protection @宇宙最强采集卡:华硕4KPro (the author, 10-18)

Group members' own words

"[Video account] Elgato 4K Pro PCIe internal video capture card, 8K4K HDR passthrough, low-latency game streaming recording card, works with PS5XboxSwitch"

—— Illidan (10-06)

"I used the g2 before, and after switching to the 4kpro I feel the 4kpro has lower latency [捂脸]"

—— 蚂蚱儿 (10-06)

"what's the latency of the 4kpro in p010 format"

—— - (10-06)

"if you want low-latency pcie, it's the 573 and the 4kpro"

—— 威猛先生 (10-08)

"I went with the 4k pro; the latency is noticeable, sure, but it's definitely playable, not a big deal"

—— 热心的猫舌头💡 (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)

---

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