Guide 06 Support Reply Templates

Documentation snapshot: November 5, 2026. Community-reported guidance; GPU drivers, capture card firmware and Veyra versions may have changed. See Home for current links.

Veyra User Guide — 06 — Standard Reply Templates

---

Veyra User Guide-06-Standard Reply Templates for Group Questions

How to use: a group member asks → find the matching entry → copy what's inside the "" and reply with it directly (adjust to the situation as needed).

Covers the high-frequency questions that keep coming up in the group, sourced from solutions already verified there. Last updated: 2026-10-06

[1]HDR colors are wrong (general: red tint / blown out / washed out / tone mapping still SDR) "Work through this order first: ① The capture format must be P010 (it's the only one that carries HDR; seeing "SDR" after P010 is normal); ② In the app, set "input color / manual override" to PQ hdr10 (don't leave it on Auto); ③ Turn on Windows system HDR (very often this is the one that wasn't on); ④ If that doesn't do it, try the warm-up: open OBS → capture source properties → click "Custom" → color format P010, color space REC.2100 PQ → close OBS → reopen Veyra and the colors are correct (once per boot, 30 seconds); or open the capture card's own software once, then open Veyra; ⑤ Still no good: zip the logs folder in the root directory and send it to the author."

[2]Elgato users with wrong colors (official software is fine, Veyra isn't) "Two must-dos: ① Open the Elgato software → Settings → turn off "Auto HDR to SDR" (it's on by default and buried deep — leave it on and you get a red tint); ② After opening the official software once, do the general warm-up: set OBS to P010 + REC.2100 PQ → close OBS → reopen Veyra. Also confirm: capture format P010, input color set manually to PQ, Windows HDR on."

[3]GC573 HDR red tint (manual PQ blows out, manual HLG goes red) "This is a known compatibility issue with the 573 (DirectShow metadata). The fix (once per boot): Boot → open Veyra first (wrong colors at this point are expected) → open OBS, set the capture input color format to P010 and the color space to REC.2100 PQ → close OBS → reopen Veyra and HDR is correct. You only have to set this up the first time; after that it's just "open OBS, close OBS" on each boot. If that's too much hassle, play in SDR for now — SDR on the 573 is rock solid."

[4]No sound (general) "Check these: ① In Windows sound output, pick the device with the same name as the capture card; ② In the app, select the capture card as the audio device and turn on "Listen"; ③ If you have picture but no sound, try toggling HDCP on and off in the PS5 settings; ④ On Dolby: the app side only accepts PCM, and OBS needs the AVerMedia plugin before it will recognize Dolby."

[5]How to get Dolby 5.1 / Atmos out "5.1: only AVerMedia-family cards support it (set the PS5 audio output to Dolby; OBS needs the AVerMedia multichannel plugin). Atmos: capture cards can't do it — you need an HDMI splitter / audio extractor: PS5 → splitter → one leg to the receiver (Atmos), one leg into the capture card; the splitter has to support Atmos (around the 380 tier, set the switch to 110; the 200-something ones only pass 5.1). Easiest of all: run the loop-out straight into the receiver."

[6]Crashes / freezes / not responding "Nine times out of ten it's background software conflict: ① Close MSI Afterburner / GamePP (close Afterburner first, turn it back on once the app's picture is up); ② NVIDIA App → Graphics → Program Settings → for Veyra, turn off: RTX HDR, Smooth Motion, RTX Dynamic Vibrance; ③ If it still crashes with all of those off: reboot; and upgrade the app to 2.0.2+ (that version fixed the Afterburner conflict)."

[7]Can't turn DLSS on / the frame-gen toggle switches itself off / "waiting for valid frame gen" "① In NVIDIA App, restore Veyra's DLSS overrides (especially the frame generation model preset) to "Use the application setting", then fully quit Veyra and start it again; ② In the Control Panel, change "Model Preset" to "Application-controlled"; ③ If it still won't work it's a driver fault: do a clean reinstall of the graphics driver (several people in the group fixed it exactly this way); ④ 30-series owners: use XESS frame generation + AMD optical flow, and update your driver."

[8]Frame gen limited / can't keep up / scheduling drops a tier "Adjust in this order: ① Lower the NR render resolution (1080P/1440P) and the upscaling tier; ② Use either in-app frame gen or NVIDIA App AI frame generation — not both if you don't have the headroom; ③ Switch capture to 30 fps + content pacing 60→30; ④ 1.4.1+ optimized this a lot — update first; ⑤ Still stuck: zip the logs and send them to the author."

[9]High latency / feels laggy "Check the three most common ones first: ① Is the capture frame rate set to 30? Capturing at 30 doubles latency compared with 60 (about 40ms at 60, about 90ms at 30) — switch to 60; ② Is the format MJPEG? Change it to NV12; ③ Are you in the right USB port? You need a 10G port (orange 3.2 or Type-C) — "white 2.0, blue 3.0, orange 3.2". For lower latency than that you have to go to a PCIe slot card. Also, if you're running NR, lock rendering to 1080P."

[10]Can't reach 60 fps / "input frame rate too low" / jitter at 53-56 "Troubleshooting order (from the author): ① Don't use MJPEG as the capture format; ② Turn VRR off for a moment (on both the capture card and the console); ③ Measure the real capture frame rate with OBS: if OBS can't reach it either → capture card / motherboard issue (on MSI AMD boards, check PCIe bandwidth); if OBS is fine → zip the logs in the root directory and send them to the author."

[11]No 4K60 option / only 4K30 "Two causes: ① Wrong USB port — you need a 10G port (Type-C or the orange USB 3.2 port); in a 5G port you only get 4K30; ② The card's own spec ceiling — USB cards generally don't do 4K60 HDR (only 4K30 HDR); for 4K60 HDR you need a PCIe slot card (573 / Elgato MK2) or a Magewell (20G port)."

[12]Capture card not detected / black screen / no signal "In this order: ① Turn HDCP off on the PS5 (Settings → System → HDMI → turn HDCP off; leave it on and you get a black screen and a locked frame rate); ② Cabling: the console goes into the capture card's IN port; the OUT port is the loop-out to your monitor; ③ Close OBS and any other program using the capture card (one card can only be captured by one app); ④ Try another HDMI cable (for some people it was the cable); ⑤ Cross-check with OBS: black in both = the card; black only in Veyra = send the logs to the author."

[13]Picture looks washed out / gray "① Don't use the MJPEG format; ② If the console has HDR on, select P010 + manual PQ; ③ Turn on Windows HDR; ④ NS2 users: when the card doesn't support HDR, the NS2 turns HDR off by itself and the picture goes dark — turn HDR off on the console or switch to P010."

[14]Frame gen tearing / jelly / smearing "① Frame gen on a 30 fps source has obvious jelly; 60 → 120 is much smoother — capture at 60 if you can; ② Set the monitor to 120Hz + turn on V-Sync (frame sync); ③ Try XESS frame gen; turn optical flow on (the flicker issue is almost always optical flow not being enabled in NR rendering); ④ A 30 fps source is stuck at 33ms by nature — that's a physical limit."

[15]Card recommendations (answer according to what they need) · 4K60 (4K screen): Kuhaomi G50 (same solution as AVerMedia, 35-40ms, supports HDR30/VRR) · 4K60 HDR maxed out + low latency: PCIe slot card (AVerMedia GC573 or Elgato 4K60 Pro MK2) · USB ceiling: Magewell 4K Pro (the only USB 4K60HDR, needs a 20G port, expensive) · Budget under 500: Lvjuneng (latency is fine, but no HDR) Note: the ASUS 4KPRO has gone up in price, so it's no longer a top value pick; check your motherboard's USB ports before you buy!"

[17]How to report a bug to the author properly "① Be specific: GPU, capture card, app version, game/console, and exactly what you see; ② Zip the whole logs folder from the app's root directory (crash → include the dmp; frame-gen problems → include fg-probe; export problems → include export-worker); ③ @Likely7 in the group ("give me a ping — with a lot of messages I sometimes miss them"); ④ Cross-check with OBS first: OBS fine = Veyra problem; OBS broken too = capture card / hardware problem."

[18]4070S / 40-series crashes after a while "Some 40-series cards (the 4070S especially) have a known compatibility issue with the NR files that causes a GPU hang — there's no software-level fix for now, just restart the app; to reduce it, set NR input to 1080P, which is more stable. Wait for the DLL update, and if it happens often, send your logs to the author."

[19]USB ports cheat sheet (answer before they buy)

"Read the colors: white = 2.0, blue = 3.0, orange = 3.2; Type-C is the most stable, plug straight in. The G2 / ASUS 4KPRO / G50 need a 10G port to reach 4K60; Magewell needs a 20G Type-C port. Check your motherboard specs before buying (vendor site / look for the orange ports at the back of the case) — don't buy something your machine can't drive."

(For detailed troubleshooting see "Veyra User Guide-01-Common Issue Troubleshooting Manual" and the in-depth version of each capture card page.)

---

This update: prices and models in the scripts (2026-11-05)

• [15]Card recommendations changed to: "· 850 budget, want 4K60: Michensen T911 (same chip as the 553G2, 4K YUY2 60, 4K60 NV12, 30-40ms, ~850 after the 2026 sale discount) — if you don't need 5.1, just buy it; · 2K60: Kuhaomi 27P or Michensen T800, 10-15ms; · Need 5.1: GC553G2 (1100-1385); · 4K60 HDR: PCIe slot card (GC573 / Elgato MK2 / 4K Pro); · USB ceiling: Magewell (needs a 20G Type-C port)."
• New [20]Low-latency tier: "Under heavy load pick "On", not "On + Enhanced" — Enhanced makes the driver wait an extra 4-18ms per frame and costs you 8-21% of the frame gen."
• New [21]AMD card black screen with NR on: "Fixed in 2.1.2 (device selection by LUID); if it's still black, upgrade, or disable the iGPU in BIOS. NR on AMD cards is still experimental."
• New [22]Frame-gen latency budget rejected: "2.1.2 reserves an extra 1.3-2.3GB of VRAM; lower the upscaling, turn off dual upscaling, and close programs that hold VRAM."
• New [23]Dual upscaling vs. upscale then shrink back: "Pick one. Dual upscaling has the most detail but doubles the overhead; on an ordinary setup choose "upscale then shrink back"."

Chapter 06 addendum: new script material (10-06 – 11-05)

Screened from the records of 7 community groups between 2026-10-06 and 11-05 — 1696 relevant messages in total.

Key points this round

• [15]Card recommendations: budget 850 for 4K60 → Michensen T911 (same chip as the 553G2, 4K YUY2 60, 30-40ms, 850 on the 2026 sale); need 5.1 → GC553G2; 4K60 HDR → PCIe.
• [20]Low-latency tier: under heavy load pick "On", not "On + Enhanced" — that costs an extra 4-18ms and 8-21% of the frame gen.
• [21]AMD card black screen with NR on: fixed in 2.1.2 (device selection by LUID); still black → upgrade or disable the iGPU in BIOS.
• [22]Frame-gen latency budget rejected: reserves 1.3-2.3GB more VRAM; lower the upscaling, turn off dual upscaling.
• [23]Dual upscaling vs. upscale then shrink back: pick one; on an ordinary setup choose "shrink back".

What group members actually said (with dates)

"You could buy the one the group owner recommends first, it's only a few dozen yuan — upgrade later if it's good"

—— 威猛先生 (10-06)

"Before this I had it set the way the uploader recommended"

—— 威猛先生 (10-06)

"Recommend a PCIe one that works on an MSI motherboard"

—— 威猛先生 (10-08)

"ROG, Gigabyte and MSI all use Samsung QD panels, so when someone recommends a Samsung monitor, recommending the first three is the same thing [giggle]"

—— Focus (10-10)

"Someone asks you to recommend a specific model and you insist on making the point that they're all the same brand.."

—— Focus (10-10)

"So do you recommend capturing HDR or 2K60 [facepalm]"

—— 杜晓 (10-12)

"You can't go wrong following the uploader's way — he's probably tried all of it while building and upgrading the software"

—— 杜晓 (10-14)

"@Likely7 the capture cards in the official channel give 15% back — it'd be great if the color grading side had a few recommended presets, then you pick one for your situation and fine-tune from there"

—— A (10-21)

---