Capture Card Elgato 4K60Pro Mk2

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

Capture Card · Elgato 4K60 Pro MK2

AMD compatible — community-tested working. Veyra group members report that the Elgato 4K60 Pro MK.2 can be used on AMD platforms. There is no basis for a blanket “AMD not supported” warning. The archived notes do not specify a separate MK.2 CPU/motherboard/BIOS test configuration; the detailed 9800X3D + X670E case belongs to the 4K Pro, not to this MK.2. Please share the exact hardware and capture mode when reporting results.

---

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") MK2 users: change the frame rate to 59.94 ("nobody writes that the mk2 needs the frame rate changed to 59.94" — Hi)
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. MK2: change the frame rate to 59.94 (the pitfall "nobody writes about", called out by Hi)

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

── Q4 [AMD platform compatibility — community tested] Will the 4K60 Pro MK.2 work on AMD?

Yes. Veyra group members report successful MK.2 use on AMD-based PCs. Do not label AMD processors or AMD motherboards as unsupported for this model.

Evidence note: The archived source material does not provide an MK.2-specific CPU/motherboard/BIOS configuration with the same level of detail as the community's separate 4K Pro AMD test. The 4K Pro test must not be attributed to MK.2. A model-specific test record can be added when the group supplies one.

If detection or frame rate is abnormal, verify available PCIe lanes and slot wiring, try another slot, update BIOS and the capture-card software/driver, and confirm the seller's return policy. These are device-specific troubleshooting checks, not proof that AMD is incompatible.

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

• MK2: 4K60HDR 32ms (Hi: "the mk2's latency is damn near a reference figure, unbelievable, 32ms, 4k 60hdr" "elgato: who else?")

• 4K60 PCIe is about 20ms (Likely7: "they measured it before: for 4K60 capture, 20 milliseconds" "the Elgato mk2")

• Near 0ms (split-screen method): "split-screen testing the 573 and the mk2 can even measure 0 latency" (Aitor)

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

• Only two PCIe cards can max out 4K60HDR: the Elgato MK2 / the AVerMedia GC573 (or the Magewell 20G)

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

• MK2: used 900-1600 ("relax, my 1000-yuan mk2 does 4k60hdr just the same" "around a thousand on Xianyu" "anything under a thousand was probably all bought up by group members")

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

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

• "if you want 4K60HDR maxed out there are basically only two choices: the AVerMedia GC573 or the Elgato 4K60 PRO MK2" (Aitor)

• "the mk2's latency is damn near a reference figure, unbelievable, 32ms, 4k 60hdr" "elgato: who else?" (Hi)

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

Test attribution correction: The archived Ryzen 7 9800X3D / MSI X670E CARBON WIFI / 3840×2160 HDR P010 report tested the new Elgato 4K Pro, not the Elgato 4K60 Pro MK.2. The complete verified hardware configuration and Veyra results are preserved on the 4K Pro page. Community members separately report that the MK.2 works on AMD platforms; an exact MK.2 configuration has not been recorded in these archived notes.

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

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

• 4K60 HDR 32ms, 10bit, the used-market value king; the MK2 is advised to run its frame rate at 59.94 (Hi).

Fixes and reminders

• Then that works, but there are no mk2 bargains to pick up now — wait for a good price on the 4kpro (Taka 10-28)
• Capture Card-Elgato (4K X-4K60ProMK2-4K Pro).txt (the author, 10-06)
• GPU (RTX 5090): occupies the first PCIe 5.0 x16 slot (CPU-connected), running at full speed. U.2 drive (via a PCIe-to-M.2 3.0 x4 card): plugged into PCI_E2 below the GPU (that slot is full-length PCIe x16 in shape, the most... (尚晓阳 10-09)
• The Elgato 4K60 Pro MK.2 and the AVerMedia GC573 both support PCIe x4 (花仁 10-19)
• The 4K60 PRO MK.2 is the one — it does 4K 60 P010 (- 像雾像雨又像风 - 10-22)

Group members' own words

"But someone measured the mk2 at a dozen-odd ms latency before"

—— 风雨兼程 (10-06)

"That said, my mk2 has had obvious banding a few times too; restarting the ps5 fixes it"

—— Hi (10-24)

---

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