Capture Card AVerMedia Gc573

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

Capture Card · AVerMedia GC573

---

Capture Card Volume · AVerMedia GC573 (Direct PCIe) [In-Depth Edition]

One-Line Positioning: the only card at the 1k price point that does "4K60 HDR + direct PCIe"; the latency king, but also the card the whole group agrees is

"the one with the most small problems, down to luck" — you have to do your homework before buying. Last updated: 2026-10-06 (in-depth rewrite)

════════════════ 0. 30-Second Verdict ════════════════ [Who it's for] Hands-on users on an Intel / ASUS platform who need 4K60 HDR with a budget of 1000-1500 [Who it's not for] MSI motherboard / AMD platform users, users who do not want to tinker, users who need VRR, users who need multichannel audio [In one line] "The on-paper specs really are strong" (cxh) — but "the 573 has lots of small problems, it is down to luck" (Hi), "Stop buying the 573, buy something else — Groups 1 and 2 are full of problems with it" (the author, 2026-09-26) [Must-read] Three self-checks before buying: (1) does the motherboard have a free PCIe x4 slot (CPU-attached preferred) (2) are you on MSI / AMD (if so, do your BIOS homework) (3) do you need HDR for gaming (if so, you must read Q1 in section 4)

════════════════ 1. Specs and Capabilities (Capture Specs Are What Count) ════════════════

════════════════ 2. Recommended Settings (Follow Step by Step) ════════════════

1. [Install the card] Put it in a CPU-attached PCIe x4 slot (the first slot is best; do not use a southbridge / chipset slot)
2. [Install the driver] Download the GC573 driver from the official site; optionally install Assist Central Pro (RGB control, firmware updates) — "Yes, without the driver it does not work at all" (Aitor)
3. [Check the link yourself] In HWiNFO look at the link: "maximum and current link width" should be 256/256; if it is 256/128 → see Q3
4. [Capture format]

• SDR gaming: NV12 4K60 (lowest latency); for better color: YUY2 / RGB (more bandwidth, slightly higher latency)

• HDR gaming: P010 (the only one that does HDR), and you must solve the color problem in Q1 first

5. [PS5 side] Turn off HDCP; Display Settings → set "HDMI transfer rate" to "-2" (fixes the vertical stripes in P010, see Q2)
6. [Cooling] Add a small 4cm fan (the backplate cools poorly); you can also take the shell off and plug in the bare board (see Q7)
7. [In Veyra] Input color: manually specify PQ HDR10 (PS5); with the XSX the hybrid format has to be switched manually
8. [Audio] In Windows select the capture card device for output; in the software select the capture card and enable monitoring (see Q5)

════════════════ 3. ★Complete Troubleshooting Manual for Common Issues (Copy and Use) ════════════════

── Q1 [Most common] HDR color is wrong: specifying PQ overexposes, specifying HLG gives a red tint (yet the official software / OBS looks normal) [Symptom] The 573's HDR (P010) picture is clearly reddish or overexposed; in a comparison with the 573 on the left and a 553G2 on the right, "the 573 is obviously reddish"; inside Veyra, manually specifying PQ → overexposed, specifying HLG → red tint; but in OBS / the official AVerMedia software the color is completely normal. [Cause] The GC573 can output HDR P010 pixel data, but the DirectShow source filter does not pass HDR/WCG metadata through correctly, so downstream (Veyra) does not know how to interpret the picture. — "The GC573 can output HDR P010 pixel data, but the DirectShow source filter does not correctly pass HDR/WCG metadata, so the downstream renderer does not know how to interpret the picture" (Aitor, verified via GPT, 2026-09-24) [Fix] ★The OBS warm-up method (pinned in the group, verified by several people; it has to be redone after every boot, takes 30 seconds):

1. The first time you open Veyra after booting — the HDR color is wrong, and that is expected;

2. Open OBS, add a capture source, set "capture input color format" to P010 and "color space" to REC.2100 PQ;

3. Close OBS (leave Veyra alone);

4. Reopen Veyra → HDR color is back to normal. In his own words (Aitor, 2026-09-25/26, repeated several times): "I tested it repeatedly and it fixes the HDR color problem on the GC573 (possibly on other capture cards too). It has to be redone after every boot: the first time you open Veyra after booting, the HDR color is wrong; then open OBS, set the capture input color format and color space to P010 and REC.2100 PQ, then close OBS; reopen Veyra and HDR is back to normal." Tip (Aitor): "You only have to set it up the first time; after that, just open OBS after each boot and close it again" [Equivalent workaround] Launch the capture card's official software once ("someone in the other group said opening the AVerMedia official software once makes it normal") [Advanced tool] An open-source metadata injection tool (provided by Aitor, built for exactly this class of problem): https://github.com/defl/directshow_metadata_injector_filter [Status] The author has logged it in the bug book: "There were cases of some capture cards showing a red tint in HDR; I need to look into this" "The 573 HDR problem is being worked on; for now see the pinned message for the temporary fix — it is not a big deal" (Aitor, 09-28) [Pitfall warning] Do not try to brute-force it with the in-app color controls — "pulling red down makes the picture band, and it is practically unusable"; and do not expect manually specifying PQ/HLG to fix it (in testing it is overexposure or red tint, those are the only two paths). [Patience check] If warming it up after every boot is too much hassle: play in SDR (the 573 is rock solid in SDR) or just change cards (see Q12).

── Q2 Vertical stripes / green vertical bars in the bright areas (in P010 mode) [Symptom] In HDR/P010, bright-area detail shows vertical stripes (green vertical bars); not present in RGB mode. [Cause] The 573's default HDR output format is YUV420, while the PS5 outputs YUV422 by default; the conversion causes the stripes. [Fix] PS5 → Display Settings → set "HDMI transfer rate" to "-2" (forces YUV420). In his own words (Aitor, 2026-09-26): "If your eyes are sharp enough to notice vertical stripes in the bright detail, go to the PS5 display settings and set HDMI transfer rate to -2 and it is solved.... Setting the PS5 to -2 forces YUV420, and then the stripes do not appear" Corroboration (Stony): "RGB has none, P010 has it", "after setting -2 they are all gone" [Note] "The 553 does not have it. 2.1 does not have this problem" — this is specific to the 573 + HDMI 2.0; once you have changed it you can forget about it.

── Q3 [Second most common] RGB 4K60 will not hold: only 53fps / 33fps / 15fps, "input frame rate insufficient", link at x2 [Symptom] RGB 4K60 output is only 53fps (OBS hits full frame rate, PotPlayer and Veyra both show 53); or "input frame rate insufficient" with only 33fps; HWiNFO shows the link at x2 instead of x4. Mostly seen on MSI motherboards / AMD platforms. [Cause] A motherboard PCIe slot lane problem plus a max payload size problem: plugged into a southbridge PCIe slot, the capture card gets dragged down by the Wi-Fi card and max payload size only reaches 128bit (it needs 256bit to hold RGB 4K60). [Fix] Work through these in order (independently verified by two group members):

1. Move to a CPU-attached PCIe slot (do not use a southbridge / third slot; the second and third slots may only be 3.0x1 or 4.0x4 and still run through the chipset) — "It is not a software problem, it is a motherboard slot problem" (cxh)

2. Use HWiNFO to check the PCIe "maximum and current link width":

• Normal is 256, 256 → it will hold full frame rate

• A problem machine shows 256, 128 → it will not hold (the 53fps kind)

3. Go into the motherboard BIOS → find the wireless card settings → "choose bt only for the second option, which keeps Bluetooth only, do not touch the LAN one" → with only Wi-Fi disabled, 128 becomes 256 and the 53fps problem goes away (cxh, from actual experience) In his words: "After disabling both, this shows 256, 256 in HWiNFO and there is no problem. By default it is 256, 128, and it will not hold" "So with only Wi-Fi disabled, turning 128 into 256 solves the 53fps problem"

4. If a second M.2 SSD sits in a slot that steals lanes → move it to another slot ("this is most likely what is giving you x2")

5. Change the PCIe generation: one group member switched PCIe to 2.0 in the BIOS and got "Gen3 at 60fps" (黄河润)

6. Last resort: switch to an Intel / ASUS motherboard — "A few guys in the main group do not have this problem; they are on Intel ASUS boards" [Root-cause verdict] "It is a PCIe slot lane problem and a max payload size problem caused by MSI motherboard defaults, and they cannot meet what the capture card needs to run the highest RGB spec" (cxh) "It is a thing called max payload size — plugged into a southbridge PCIe slot, the capture card gets dragged down by the Wi-Fi card and only reaches 128bit; disable the wireless card and it reaches 256bit, and then it holds 60fps" (heilmittel2034, 2026-10-04) [Worst-hit hardware] MSI motherboards + AMD platforms; "the 573 is not worth buying anymore" (YK); confirm what board you have before buying.

── Q4 Small white dots / small blue dots appear on the picture [Symptom] With a PS5 signal (especially P010) small white dots appear at fixed spots on the picture; no white dots on the Switch 2; "you can see them right on the menu". [Cause] Suspected driver / PS5 compatibility issue (a common complaint, but not on every card: "one guy's 573 does not have it") [Mitigation] Roll the driver back to the default version: "no more white dots now, they turned into blue dots" (cxh) — reduced but not eliminated. [Status] "No solution found yet; the cards that have it show it at fixed spots"; "there is a fair amount of feedback about white dots on the 573 in HDR" (Hi) [Recommendation] If white or blue dots bother you, do not pick the 573; this is a hardware-level issue with no fix.

── Q5 No sound after installing / colors look washed out [No sound] 1) Confirm the Windows audio output is set to the "device with the same name as the capture card"; 2) in the software select the capture card for audio and enable monitoring; "mine was detected automatically" (喂我花生) [Washed-out color] "The color is not as good as the original, a bit washed out" → "I maxed out the gray level in settings and it is okay" (喂我花生); or "the color was fine after a restart and refresh" (魏军) — try a restart first, then look at gray level / color adjustment.

── Q6 Does the capture card run hot? Should I change the cooling? [Current situation] "I would suggest adding a little 4cm fan; the backplate cooling is pretty poor" (Aitor) [Options] (1) add a 4cm fan; (2) a 20cm PCIe riser plus a fan strapped around to the backplate; (3) take the shell off and plug in the bare board ("I only got it sorted when I took that crappy 573 shell off and plugged the bare board straight in" — Klaus; "that shell is useless" — 二大爷) [Note] "Too hot and performance degrades" (二大爷); when undoing screws on the shell "put a piece of plastic sheet down, do not scratch it" (Aitor); taking the shell off may affect the warranty / resale value ("would taking it apart void the warranty?" "there is not even a seal"), so weigh it yourself.

── Q7 The PCIe slot is blocked by the GPU / can I use a riser cable? [Blocked slot] A GPU too thick blocking the slot is a common problem (M0ksha, 逆旅, L and Focus all hit it): Solutions: (1) switch to a bigger / ATX board; (2) "just connect the GPU with a riser cable, no need to change the motherboard"; (3) change the case [573 and risers] Officially not supported ("if you want to use a riser with the 573, better ask the official channel — I remember reading somewhere that it is not supported"); but group member Aitor tested a 20cm riser: "it works, a riser has no effect", and that is how he runs it (routed around the backplate plus a fan). Conclusion: it works, but buy a good short cable and avoid it if you can ("it loses speed").

── Q8 It shows a frame or two after connecting and then crashes (4070 Super case) [Case] boom (4070S + 573): "after connecting it shows a frame and then crashes straight away" [Fix] "Solved — it was because HDR was selected by default; switching to [a non-HDR format] fixed it" — "Basically, configure it before capturing, otherwise the moment something breaks the whole app crashes" [Background] The author: "The 4070 Super has issues; these dll files are not well matched to it right now and it blows up easily" (an isolated 40-series compatibility issue)

── Q9 Do I need to install a driver / firmware? [Required]: the driver from the official site (it will not work without it); optional: Assist Central Pro (RGB control + firmware updates) — "The driver alone is enough", "at most grab Assist Central Pro" (Aitor) [Tip] Once the card is plugged in, AVerMedia pops up a prompt to install the controller ("as soon as I plugged in the AVerMedia, a window popped up asking me to download a controller")

── Q10 What is the 573's latency, really? (data comparison) [Reference figures] Aitor's strict same-screen test: 5ms average over ten runs; Bilibili reviews: about 16-43ms at 4K60; one "other isolated 140ms case" in the group (the author replied: "Impossible, they all measure in the teens") [Test method 1 · same screen, same window (most accurate)] "Run one HDMI from the GPU to the capture card and another to the monitor, set the system's multi-display mode to Duplicate, and you get a stopwatch test on a completely identical screen; the two stopwatches need to sit at the same height on screen, because monitors refresh vertically" (Aitor) [Test method 2 · USB drive video] "Put this video on a USB drive, plug the drive into the PS5, play it with the PS5, then watch the passthrough screen and the capture screen at the same time — record a video and you can see the latency" (L, test file lagtest_ps5_1080p60.rar) [Important] The 573 can only capture at 60fps → you never fall into the "capture at 30 and latency doubles" trap (a USB card is 90ms at 30 and 40ms at 60)

── Q11 573, 553G2 or Elgato 4K Pro? (the classic decision paralysis) [Want 4K60 HDR maxed out] Only two PCIe cards: the AVerMedia GC573 or the Elgato 4K60 Pro MK2 (about a thousand used) — "If you want 4K60 HDR fully maxed out there are basically only two choices: the AVerMedia GC573 or the Elgato 4K60 PRO MK2" (Aitor) [Want low hassle / good color / 10-bit] Elgato MK2 / 4K Pro (but watch motherboard compatibility) [USB is enough / need a 5.1 audio track / do not like fiddling] GC553G2 [The author's words, 2026-09-26] "Stop buying the 573, buy something else — Groups 1 and 2 are full of problems with it" [Sober summary] The 573 is a high-ceiling, low-floor card: dial it in and it is the latency king and the cheapest way into 4K60 HDR; get it wrong (MSI board / HDR red tint / white dots) and it is endless fiddling. Read through every Q&A on this page before buying.

════════════════ 4. Known Bugs and Fix Status ════════════════

• HDR red tint (metadata issue): the author has logged it in the "little bug book" and is looking into a software-layer fix; use the OBS warm-up method in the meantime

• Small white dots / blue dots: no fix (suspected driver / compatibility)

• 53fps on MSI / AMD motherboards: the user has to handle it in the BIOS (no software fix)

• 4070S crashes / 40-series dll compatibility: "blows up easily", reopen the app; some users are stable after switching to a non-HDR format

• VRR: not supported (hardware); with a capture plus frame interpolation setup VRR is not needed anyway (fixed 30/60fps is best)

════════════════ 5. Market Prices and Buying Advice ════════════════ [Market prices (late September to early October 2026, everything is climbing)]

• Used: 1100-1400 (1200 is common on Xianyu; "find one with the box, accessories and receipt, it is easier to sell")

• JD: 1300-1600; Taobao: 1300-1590 (it was 1450 with 12 interest-free installments at one point)

• Douyin: 1470; Pinduoduo: 1370

• Price history: "A while back the AVerMedia was 1450 on Taobao with 12 interest-free installments; now it is 1590, and on JD it went from 1500 to over 1600" (r) [Pre-purchase checklist] □ The motherboard has a free CPU-attached PCIe x4 slot (not blocked by the GPU) □ HWiNFO confirms link width 256/256 (if not, do the Q3 homework first) □ It is not an MSI / AMD platform (if it is, prepare yourself) □ You accept: 8-bit (P010 is 10-bit), no VRR, stereo, HDR needs warming up □ For used cards, make sure of the serial number ("warranty is by serial number only, nothing else counts"; individual RMA is supported) [Resale value] "Capture cards do not seem to drop in price — they hold their value well"

════════════════ 6. Selected Quotes from Group Members ════════════════

• "Either way, the 573 is the best-value 4K60 HDR card" (Hi, 09-18)

• "The 573 has lots of small problems; it is down to luck" (Hi, 09-29)

• "Strong on paper, but MSI boards + AMD have a lot of traps; right now I really cannot recommend it" (cxh, 09-20)

• "I never thought I would see it, but here in Group 3 the Elgato is starting to look like good value" (Hi, 09-29, in a comparison context)

• "The 573 HDR problem is being worked on; for now see the pinned message for the temporary fix — it is not a big deal" (Aitor, 09-28)

• "People in other groups who swapped the 573 for an Elgato mostly did it after hitting small problems" (Hi, 10-03) ================================================================ (For the full analysis of why this is the "most problematic" card, see Veyra User Guide - 04 - Analysis of the Most Problematic Capture Card in the Group)

---

This Update (2026-11-05)

• "The 573 goes in a case PCIe slot, has lower latency and adds 4K60 HDR, but compatibility problems are a matter of luck" (YK, 10-10).
• HDR red tint / oversaturation is solvable: "I am on a 573 too and had HDR red tint and oversaturation; then I followed an explanation in the group and fixed it" (迅雷不及掩耳盗铃, 10-10).
• Still 8-bit, so HDR will band; SDR is very stable.

This Update and Expansion (2026-10-06 to 11-05)

Filtered from the records of 7 chat groups, 2026-10-06 to 11-05: 246 relevant messages, with speakers and dates preserved.

• "PCIe gives lower latency and adds 4K60 HDR, but compatibility problems are down to luck" (YK, 10-10).
• HDR red tint is solvable: "I followed an explanation in the group and fixed it" (迅雷不及掩耳盗铃, 10-10).
• 8-bit, HDR bands; SDR is very stable.

Workarounds and Reminders

• I was just about to buy a GC573 yesterday, and today I see the Elgato 4K Pro discounted to 1500-something on Amazon Global — worth buying if you are okay with overseas orders (Illidan, 10-06)
• I also made my choice based on my current board, an MSI X670E Carbon (using HWiNFO and Codex to verify the PCIe setup and pull information); some users claim that on certain MSI boards the third PCIe slot limits the GC573 to only 53fps at 4K60 RGB (possibly the Wi-Fi... (Illidan, 10-06)
• Damn it, the 573's passthrough does not support 4K VRR again — sometimes I want to play something that demands low latency and tight controls and I have to unplug and replug (A, 10-08)
• I will buy one of these 573s and try it too, to see how much better it is than my T900 (阿莫视觉, 10-09)
• Just switch already — that is what I did, moved over from the G2; the G2's latency still is not good enough, and the 573 is a fine swap (chrn, 10-06)
• I have always been on the 573, and a couple of days ago I wanted to finish off the platinum for Prince of Persia: The Lost Crown. It came out really blurry, but when I plugged straight into the monitor it was perfectly sharp — thinking of buying a 4K Pro to try (Stony, 10-06)
• Turning DLSS5 on already adds ten-odd milliseconds. Third, the 573 has its own latency on top of that (Allen Lee Xbox, 10-08)
• 573 + MSI + AMD: in the BIOS set Chipset Gen Switch to Gen3 (Bliz, 10-10)
• I read through the whole list of 573 problems and my head hurts — that is a lot of fiddling. What other good PCIe card gets latency as low as possible? (杨浩然, 10-08)
• The Douyin videos all use USB cards and all talk about the latency problem, so I want to get a 573 and try it (杨浩然, 10-08)

Group Members in Their Own Words

"If you want PCIe low latency, it is the 573 and the 4K Pro"

— 威猛先生 (10-08)

"I returned the 553 and went for the 573"

— 威猛先生 (10-08)

"Damn it, the 573's passthrough does not support 4K VRR again — sometimes I want to play something that demands low latency and tight controls and I have to unplug and replug"

— A (10-08)

"You buy the 573 for the low latency and 4K60 HDR"

— 威猛先生 (10-08)

"I will try the 573; if that still does not work I will give up and stop using DLSS5"

— 威猛先生 (10-08)

"If I plug in the 573, can I still return it?"

— Milk (10-08)

---

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