Skip to content

Guide 01 Troubleshooting

Jump to bottom
Likely7 edited this page Nov 9, 2026 · 2 revisions

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 — 01 — FAQ & Troubleshooting Manual

Compiled from real Q&A in Veyra community groups 1–7, 2026-09-13 to 2026-11-05

[Tag legend] [Software] = a bug/limitation in the software itself; you usually just wait for a new version to fix it [Settings] = a user configuration problem, not a software bug (the biggest share in the groups) [Hardware] = a hardware or environment cause such as the capture card / motherboard / cable / console

Contents A. Startup, crashes and freezes B. The captured picture (black screen / no signal / not detected / frozen) C. Color and HDR (gray, reddish, banding, overexposure, stripes) D. Audio (no sound, silence, A/V desync, hissing) E. Frame interpolation / frame generation / performance (can't keep up, limited, stutter, dropped frames) F. Latency (high latency, sluggish, unresponsive) G. Export H. Streaming I. Interface and controls J. "This is not a software problem" — typical cases (important)

A. Startup, crashes and freezes

A1. Crash or no response when opening the app / clicking capture [Symptoms] The app opens, flashes a few times and exits; with AI interpolation on, clicking capture crashes it; it crashes while adjusting settings; clicking the subtitle mini-window crashes it [Cause] By the groups' tally, more than 90% of this is background software conflict (2026-10-03, the author: "if it isn't responding, chances are Afterburner is running"):

  1. Monitoring software such as MSI Afterburner / GamePP

  2. NVIDIA App image plug-in injection (RTX HDR / Smooth Motion / RTX Dynamic Vibrance) [Solution] [Settings]

  3. Close Afterburner/GamePP. Tip: "Close Afterburner first, wait until the picture comes in, then turn Afterburner back on — perfect" (风雨兼程)

  4. NVIDIA App → Graphics → Program Settings → find Veyra → turn off RTX HDR / Smooth Motion / RTX Dynamic Vibrance

  5. Version 2.0.2 already fixed the Afterburner-related no-response (the author)

  6. If it still crashes: fully restart the PC (leftover background processes) [Note] [Software] In the 1.4 era there were "freezes and crashes when dragging across screens" and "a crash when clicking the subtitle mini-window"; both are fixed in newer versions.

A2. DLSS won't turn on / the interpolation switch turns itself off / "NR initialization failed" [Symptoms] It switches itself off after being enabled; 6x frame generation can't be selected; initialization failure is shown [Cause] Mostly NVIDIA App's DLSS override (the frame generation model preset being overridden globally); next is a GPU driver fault [Solution] [Settings]

  1. In NVIDIA App, restore Veyra's DLSS override to "Use application settings" (especially the frame generation model preset), and check whether it is inheriting a global override, then fully quit Veyra and start it again (the author's words, 2026-09-19)

  2. In the NVIDIA Control Panel, set "Model Presets" to "Application-decided"

  3. "Waiting for valid interpolation" → check the NVIDIA App model preset and set it back to Recommended / 3D mode

  4. If it persists: the NVIDIA driver is faulty — do a clean reinstall of the GPU driver (several cases in the groups, and the reinstall always fixed it); the tell: "the can't-enable-NR problem happened on 大力喜鹊 too" → nothing to do with Veyra [Note] [Software] "Frame generation has no effect" involves a compatibility bug with some capture cards; submit logs and wait for the fix.

A3. Issues with 30-series GPUs [Symptoms] Frame generation won't turn on with a 3060; on 30-series DLSS frame generation switches itself off; a 3070 can't interpolate with XESS [Solution] [Settings/Software]

  • 30-series officially doesn't support DLSS frame interpolation; use "in-app XESS frame generation + AMD optical flow" (the author's recommendation, on the order of 1.1 ms)

  • On 30-series, enabling DLSS frame generation requires a GPU driver update

  • If it switches itself off, launch it a few more times / restart (a cache issue)

  • Since 1.4.1, "DLSS 6x is unlocked on both 30-series and 40-series, though a 3060 probably can't keep up" (the author)

A4. On launch it says runtime libraries are missing / it gets blocked by antivirus [Solution] [Settings] Turn off Windows Security or add the folder to the whitelist; if the download itself is blocked, use another cloud-drive channel

A5. Nothing happens when double-clicking after extraction [Solution] Make sure you downloaded the win64 portable archive; there was one case in the groups that was ultimately fixed by reinstalling Windows (rare)

B. The captured picture

B1. No picture / black screen / stuck on "No signal" or "Sampling frame rate" [Cause] In order of case frequency in the groups:

  1. A console such as the PS5 still has HDCP on ("turning HDCP off is critical — with it on, the frame rate gets locked / you get a black screen")

  2. The capture card is taken by OBS or another app ("a capture card can only be captured by one device")

  3. HDMI cable connected the wrong way round: the console goes into the capture card's IN port, while the OUT port is the pass-through to the monitor

  4. Wrong capture format (e.g. 4K60 MJPEG gives a black screen; 4K30 HDR paired with an unsupported format)

  5. The capture card itself is faulty (e.g. a UGREEN CM701 with "something over the picture"; all three apps misbehaved, and replacing the card fixed it) [Solution] [Settings mainly]

  6. PS5: Settings → System → HDMI → turn off HDCP; the same for XSX

  7. Stop the capture / virtual camera in OBS

  8. Check the IN/OUT wiring (on 2026-10-02 the author gave the full steps: "in is the one plugged into the cable coming out of the ps5… from the OUT port you go on to the monitor / that one is the pass-through")

  9. Change the format: try NV12 first; for HDR use P010

  10. Cross-check with OBS / PotPlayer: if both are black it's most likely the capture card; if only Veyra is black, look at the settings again [Typical case] "The AVerMedia GC553 shows nothing above 1080p" → a cable problem; "swapping in a portable SSD's cable fixed it"

B2. It keeps saying "An error occurred" [Solution] [Settings] "Is OBS holding it? You have to stop capture elsewhere" (the author)

B3. After the capture card is connected, the picture shows for a moment and then it crashes [Case] 4070 Super + GC573: HDR was selected by default; switching to a non-HDR format fixed it. [Experience] "Set everything up before you capture, otherwise the app crashes wherever it first hits trouble" (a user's own conclusion)

B4. Black picture, but the app says capture is actually working [Cause] Usually the console isn't outputting a signal / the HDMI handshake failed [Solution] [Hardware] Try the original PS5 2.1 cable; reseat it; on the PS5 side "drop the color setting one notch" and "set the output rate to -1"; For ASUS 4KPRO users, a blinking yellow light = console handshake failure: turn off HDCP → reset the pass-through source to defaults → turn off HDMI enhanced mode / 60Hz low latency / VRR

B5. "Input frame rate insufficient" / capture only reaches 53, 33 or 15 fps [Cause] [Hardware] Motherboard PCIe lane/bandwidth problems; the two most frequent cases in the groups:

  1. MSI AMD motherboard: a GC573 RGB at 4K60 outputs only 53 fps → fix: in BIOS "select bt only for the second option, i.e. keep Bluetooth only, and leave the lan one alone"; after going from 256/128 to 256/256 it reached full frame rate (cxh's hands-on)

  2. A capture card in a southbridge PCIe slot dragged down by the Wi-Fi card until max payload size is only 128bit → disable the Wi-Fi card or move it to another slot (heilmittel2034's hands-on); users on wired Ethernet are unaffected Other: not enough bandwidth in the capture card's slot (the second slot, PCIe 3.0 x1, gives only 15 fps); try switching PCIe to Gen2/Gen3 in BIOS [How to tell] Measure the real capture frame rate with OBS: OBS low too = capture card/motherboard problem; OBS normal = software problem (send logs)

B6. The app can't open the capture card, but OBS is fine [Cause] [Settings] The capture card is held by OBS; or in the app "you have to click Connect before you get a picture"

B7. Picture freezes (yellow light) [Case] ASUS 4KPRO: "yellow light and it freezes"; a yellow light indicates the HDMI signal dropped / the handshake failed [Solution] Check the HDMI cable, lower the PS5 transfer rate, reset the pass-through source to defaults

B8. It drops every few seconds and the picture jumps [Solution] [Settings] Restart the app; with a USB card, check the cable and the USB port (try a 10G port / a C port)

B9. 4K60 NV12 can't be selected / only 4K30 is available [Cause] [Hardware] Not enough USB port bandwidth: before buying a card, check whether the motherboard has USB 3.2 Gen2 (10Gbps); "white is 2.0, blue 3.0, orange 3.2" (a group mnemonic); a G2 / ASUS 4KPRO must go into a 10G port (case: on a 5G port there was "no 4K60 option", and moving to a 10G port fixed it; plugging Type-C straight in is most stable; an A-port adapter has to be a 10G one) An old GC553 doesn't recognize 2K, and a 4K30 card can only capture 1080: that's the card's own spec, so read the "capture parameters" before buying (important: a seller's advertised 4K60 HDR may be the "pass-through parameters"; "pass-through parameters are no use to us — you have to look at the capture ones" — the author)

C. Color and HDR

★C0. [Overview] HDR colors wrong? Start with this complete cross-card troubleshooting chain (it applies to every capture card) [Four symptom types] Gray/washed out; reddish; overexposed (highlights blown out); "weird colors" (the tone mapping is still SDR) [Standard troubleshooting order (compiled from successful cases in the groups; work through it in order)] Step 1: get all three basic settings right (most problems are solved here): (1) The capture format must be P010 ("only p010 and p016 carry hdr" — the author); Note: it's normal for P010 to show "SDR" after it — "p010 is itself an sdr format, but it's special: it carries HDR data, so what comes out looks like HDR" (咖喱) (2) In Veyra, set "Input color / Manual" to PQ hdr10 (PS5/almost all consoles use PQ for HDR10; HLG is only for HLG sources); "do it manually — auto has problems" (the author, answering about the XSX mixed format); if you don't set it, it "outputs sdr colors, and then the colors look weird" (Hi) (3) Windows HDR must be on (several cases turned out to be exactly this in the end) Step 2: check the console side (PS5): Settings → Screen and Video → HDR on; resolution 2160p/60Hz (not Auto/120Hz) Step 3: still wrong? Move on to the "warm-up method" (for the compatibility problem where DirectShow doesn't pass HDR/WCG metadata): ★OBS warm-up method (30 seconds; once after each boot; verified on several cards including the 573, and the author agrees it "may include other capture cards too"): Open OBS → capture source properties → click "Custom" first (without that, P010 is grayed out and can't be selected) → set Color Format to P010, Color Space to REC.2100 PQ → close OBS → reopen Veyra → the colors are back to normal. Aitor's full quote: "the first time I open veyra after booting: HDR colors are abnormal; then I open OBS and 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" ★Official-software warm-up: open the capture card's official software once first (works for AVerMedia/Elgato; "open the AVerMedia official software once and it's normal") Step 4: Elgato users only: turn off "Auto HDR to SDR" in the official software (on by default and well hidden: "you have to turn it off, otherwise it sometimes goes reddish" "it should be off anyway" — Hi) Step 5: still wrong → troubleshoot by symptom under C1-C7 below; zip the logs in the root directory and send them to the author (the author has logged this compatibility issue: "there used to be cases of some capture cards going reddish in HDR — I need to look into that") [Rule of thumb] "The official software/OBS is fine and only Veyra is wrong" = the typical metadata compatibility problem, go to Step 3; "the official software is wrong too" = a setting/hardware problem on the capture card itself, so check the HDR settings in the card's official software first

C1. The picture is gray / washed out [Cause + solution]

  • [Settings] HDR not matched: the console has HDR on, but the app is set to an SDR format or isn't set manually → see C0 Step 1

  • [Settings] MJPEG format is in use: "mjpeg just puts a gray layer over everything, and it's blurry on top"

  • [Settings] when NS2 doesn't support HDR, HDR is switched off automatically and the picture goes dark (not a fault): turn HDR off in the Switch settings or enable P010 (a photographer user's test: "turn it off and the picture is normal")

  • [Software] old-version bug: in 1.3.0 "the picture isn't gray anymore"; if p010 suddenly goes gray, restart the app / check the HDR switch (case: 落雨 "the picture suddenly went gray in p010 format" → "turning on the PC's hdr" brought it back)

C2. HDR goes reddish [Cause] [Hardware] HDR/WCG metadata passing on some capture cards; the root cause in his own words (quoted by Aitor): "the GC573 can output HDR P010 pixel data, but the DirectShow source filter doesn't pass the HDR/WCG metadata correctly, so the downstream renderer doesn't know how to interpret the picture" [Solution] (in order; the first two are the most-verified fixes in the groups)

  1. ★OBS warm-up method (see C0 Step 3), once after each boot; 573 users: "this method fixed it" "there are a few in the group who went red as well"

  2. Official-software warm-up: "someone in the neighboring group also said that opening the AVerMedia official software once made it normal"

  3. Elgato users turn off "Auto HDR to SDR" in the official software ("turn it off, otherwise it sometimes goes reddish" — Hi)

  4. Try unplugging the pass-through cable once (Han: "I unplugged the pass-through cable and it was fixed instantly")

  5. In general: cross-check with OBS/PotPlayer; if both are reddish it's a capture card setting problem (the author)

  6. Fine-tune "Tone adjustment" in the app (the author's suggestion; a 573 user reports "pulling red down makes banding appear, so it's barely usable" — this only treats the symptom, so use the warm-up method first)

  7. Open-source tool (for the 573 issue specifically, from Aitor): https://github.com/defl/directshow_metadata_injector_filter

  8. Still no good: zip the logs and send them to the author (this kind of problem is in his "BUG notebook")

C3. Color banding [Cause] Several layers stack up, so first work out which layer it is:

  1. [Hardware] The capture card is only 8bit: the GC573/ASUS 4KPRO are confirmed to be "8bit HDR", while the GC553G2/G2 are 10bit with no banding. En tierra: "I compared on my two oleds; the 573's color banding is because it only supports 8bit"

  2. [Hardware] The monitor itself: HVA panels, miniled and 8-bit-plus-FRC 10-bit panels get misdiagnosed as capture card problems ("an Elgato user in Group 1 also reported banding, and it turned out to be the hva panel's fault")

  3. [Settings] "Dark area enhancement" turned on in the monitor causes banding

  4. [Settings] NVIDIA Control Panel: changing color depth from the default to 12bit and "don't use monitor control" can improve it (Deathwing)

  5. [Hardware] p010/nv12 is 4:2:0 sampling and may inherently show vertical texture ("p010 is 8bit pretending to be 10bit" — a complaint) [Conclusion] "The capture card physically can't do it; software can't fix it"; if banding bothers you, pick a 10bit card (G2/mk2/4K Pro)

C4. HDR overexposed / highlights blown out [Solution] [Settings] "The highlights are overexposed; you need to bring them down" (color page); confirm whether the source is PQ or HLG (the XSX has a mixed format, and the app doesn't fully auto-detect it yet — "do it manually, auto has problems" — the author); "dlss5 will pull the highlights down"

C5. Vertical stripes in bright areas (GC573 + PS5) [Solution] [Settings] PS5 → Display Settings → change the HDMI transfer speed to "-2" (forcing YUV420) and it's fixed (Aitor) Cause: the 573 outputs YUV420 by default in HDR and the PS5 outputs YUV422 by default, and the conversion produces the vertical stripes

C6. Green tint / corrupted picture / flipped image

  • Corrupted picture: an Elgato 4K Pro user had "no picture in the PCIe slot / or a corrupted picture" (a platform compatibility issue)

  • [Software] upside-down picture in RGB format: fixed in 1.3.2, which also adds a "Flip" button; in the meantime switch formats

C7. HDR hardware/settings recommendations

  • "Only HDR1000 is good enough — you can see an obvious difference"; HDR400 "looks so bad you're better off leaving it off"

  • Turn it on at all three ends: console + Windows + monitor (when going through RTX HDR, the console end can stay off)

  • On HDR, as they put it: "only p010 and p016 carry hdr" (the author); "if you want to see hdr on a capture card, look at the p010 format" (Hi)

  • Steps to turn on HDR in Windows: turn on HDR on the screen → launch and run the app → confirm RTX HDR is recognized in the GPU settings

D. Audio

D1. No sound [Solution] [Settings] Check in order:

  1. In Windows sound output, select "the device with the same name as the capture card" (not the headphones, not the monitor)

  2. In the app, set the audio source to the capture card ("select the capture card you want to capture"; NS2 case: select "hdmi Kuhaomi / audio input / the capture card")

  3. You have to turn on "Listen" in the sound settings before you can hear it

  4. Try turning off "Latency optimization" in the audio section

  5. No sound but the PS5 picture is fine: toggle HDCP in the PS5 settings and the sound comes back (James' experience)

  6. Make sure the capture card appears in the audio device list (GC573 users need the AVerMedia official plug-in/controller installed)

  7. Choosing the default audio device causes a black screen: select the capture card instead (case: "if I pick the default audio the app just goes black" → selecting the capture card fixed it)

D2. 5.1 / Dolby Atmos [Current state]

  • Apart from AVerMedia, capture cards on the market can basically only capture stereo (Hi's summary: "among the retail capture cards, only AVerMedia put out a few models that can capture multichannel" "AVerMedia only supports the oldest version of Dolby Digital 5.1 (AC3) — the patent expired, so they're skirting the edge")

  • GC553G2: outputs a 5.1 track (AC3) once Dolby is enabled; 7.1/Atmos not supported

  • OBS needs the AVerMedia plug-in (AVerMediaMultichannelAudio) to recognize Dolby multichannel [For full-fat Dolby Atmos]: use an HDMI audio extractor/splitter: Setup: PS5 → audio extractor → one HDMI to the AV receiver (Atmos), one to the capture card and on to the monitor (LJY's test) Buying notes: "the 200-something ones can only extract the old Dolby 5.1, not Atmos" "you have to set the dial to 110 to extract Dolby Atmos; the built-in 111 only extracts dd+"; "go for the 380 audio extractor and you get full-fat Dolby Atmos straight away" (Hi) Veyra 1.4.0+ already supports Dolby Atmos

D3. Audio and video out of sync [Solution] [Settings] The app has an "A/V sync" switch plus manual adjustment (audio compensation); "On my side it's normal with compensation off; with auto sync on the sound is sometimes 1-2 seconds late" (风雨兼程) The author explains: "auto sync exists because everyone has a different GPU and different processing times"

D4. Hissing / popping / distortion / mains hum

  • [Software] 1.3.0 fixed "audio hissing" ("I finally found the audio hissing problem")

  • [Hardware] cheap UGREEN-class devices occasionally hum: "it's probably interference" "either take the audio straight from the ps5, or change the capture card"; some people ease it with "audio compensation" in pro mode

  • Popping under PCM was an early-version issue and has been improved

D5. Volume is very low / the soundbar only lights up its volume bar

  • Quiet voices with a normal background: usually the capture card / speakers / headphones (the author)

  • Rear surrounds on a soundbar not working: you need an audio/video extractor (Hi: "an audio/video extractor is a must")

E. Frame interpolation / frame generation / performance

E1. Interpolation limited / can't keep up / scheduler downshift [Cause] Not enough performance, or a pipeline problem [Solution] [Settings]

  1. Lower the "NR render resolution" (1080P/1440P) and the super-resolution level (the author stresses this repeatedly)

  2. Use either in-app interpolation or NVIDIA App AI interpolation, not both (without good performance, having both on is guaranteed to hit the limit)

  3. Set the capture card input to 30 fps + use the "60→30 content cadence" to cut the cost, or just capture at 30

  4. Since 1.4.1, "interpolation limited" (the pipeline traffic jam) has been greatly improved; update the version

  5. Still no good → ask the author for the logs ("interpolation scheduler downshift: turn the earlier stages down a bit and leave some compute for frame generation")

E2. GPU usage / power draw / temperature [Shared data]

  • DLSS5 (NR) is the biggest performance hog: "one NR layer adds 20ms or more of latency" (Snicer); "DLSS5 doesn't eat VRAM" (牛腩盖饭)

  • 5090: two NR layers + frame generation 450~550W; 8K super-resolution 550-600W; "honestly you can just power-limit it"

  • Ways to cut power: process internally at 1080P, render NR at 1080P/1440P, lower the super-resolution level

  • Temperature: 70 °C on the GPU is normal, up to 80 °C is no problem; for two layers on a 5080/5090, good cooling or a power limit is recommended to bring it down

E3. Flickering game picture (characters flicker / hats flicker / stamina bars flicker) [Solution]

  1. Turn on optical flow: "a lot of picture flicker is just optical flow not being enabled in NR rendering" (牛腩盖饭); NVIDIA optical flow flickers the least; AMD optical flow uses less but may flicker

  2. Set video super-resolution to "Medium" ("if you have super-resolution on and see flicker, setting video super-resolution to medium helps" — the author)

  3. Work out the source: flicker from NR or flicker from frame generation — try switching to XESS

  4. 老黄鸭 (NVIDIA AI interpolation) flickers badly on a low base frame rate; switch to in-app XESS interpolation

E4. Jelly effect / ghosting / tearing [Solution]

  • Interpolating 30 to 60 fps gives severe jelly: "with a 30 fps source, interpolation just doesn't feel responsive — the source frame rate is too low"; "60 to 120 is very smooth"

  • "60 doesn't jelly; it looks good" (Aitor); if you can capture 60, capture 60 and then interpolate

  • Easing jelly: switch to XESS interpolation, turn on optical flow, "sharpening seems to reduce artifacts and jelly"

  • Tearing: set the monitor to 120Hz; turn on V-Sync (the author: "it's just frame sync — turn V-Sync on and you're fine"); 2.0.3 has feedback of worse ghosting on NS2; you can roll back to 2.0.2

  • The source timestamp mode affects DLSS interpolation quality: "with source timestamps DLSS is fine too; picking the bottom one doesn't work"

E5. "Output below target"

  • "It means it can't interpolate up to the target frame rate"; check whether V-Sync / a frame rate limit is on; lower the settings;

  • In one case the root cause was "the console output was set to 1080P instead of native 4K" → changing the console setting fixed it

E6. XESS interpolation power draw jumping around / native 4K power draw going up and down

  • Author A: "native 4K power draw going up and down is an aging issue; usage never goes above 70%, and the picture suddenly hitches"

  • XESS power-draw jumping has already been through one round of fixes; if it still happens, update the version + send logs

E7. The game gets stuttery/sluggish after enabling NR

  • Core principle (Snicer): "if you're going to run nr, 1080 latency is definitely lower than 4k" "with nr on, always lock to 1080"; whether the capture card feeds 4K or 1080 doesn't itself affect latency, but with NR on, 1080 is optimal

  • Unresponsive after super-resolution: "drop DLSS5 rendering down one level" (牛腩盖饭)

F. Latency

F1. How to bring high latency down [The priority the groups agree on]

  1. Set the capture frame rate to 60 (capturing at 30 roughly doubles latency: "capturing at 30 is around 90ms, at 60 it's around 40ms" — Hi's test)

  2. Use NV12 (not MJPEG; RGB/YUY2 need more bandwidth and are relatively unstable)

  3. Use a 10G/20G USB port ("white is 2.0, blue 3.0, orange 3.2"; Magewell needs a 20G C port)

  4. For anything lower you have to go to a direct PCIe card ("if you need lower latency, usb can't satisfy you anymore — you have to do pcie" — the author)

  5. The lower the resolution, the lower the latency; lock NR rendering to 1080

  6. On the software side: the app's own playback pipeline is 20-30ms lower than OBS [Latency reference values (group measurements)] 2K60 NV12 USB card: 10-16ms (the latest from the channel owner's showcase: 27P 10-12ms, T800 12-15ms) 4K60 NV12 USB card: 35-45ms 4K30 HDR: 90-100ms (capturing HDR for gaming is not recommended) Direct PCIe (GC573/mk2): about 20ms for raw capture, as low as 5ms in a strict same-screen test, 16ms in a Bilibili test Magewell 4K Pro: the channel owner says 5-10ms; another user re-measured around 55ms (disputed; the test method matters a lot) Software processing (NR + interpolation) adds: 15-30ms (one NR layer +20~30ms) Full-chain subjective reference: "if the capture card is fine it's usually around 50ms, the software latency is generally 15-20ms, so about 70ms all in"

F2. How latency is perceived

  • "You only feel latency above 10ms" isn't absolute; perception varies a lot: "some people don't mind 100ms, some can't accept 50ms"

  • "For non-competitive games, even around 100ms of input latency is acceptable" (Snicer)

  • A 30 fps game already carries 33ms of render latency, and interpolation can't change the base responsiveness: "interpolation is the icing on the cake, not a rescue"

F3. How to measure latency (the groups' standard method)

  1. Two-screen pass-through comparison: connect the capture card's OUT to a monitor and photograph the same stopwatch on that screen and in the capture preview

  2. Stricter: duplicate the display in the same window on one screen (Aitor, average of 10 runs; the 573 averaged 5ms)

  3. A millisecond stopwatch on your phone or a web stopwatch https://miaobiao.r239.com/ (the Apple stopwatch is only accurate to 10ms — don't use it)

  4. Lock both monitors to 60 fps during the test for better accuracy; remember OBS has its own latency, so don't draw conclusions from the OBS image

G. Export

G1. Export fails (fails halfway / fails on the last frame / errors at 99%)

  • [Software] since 1.3.2, "export failing on the video's last frame is fixed"; most export problems in the 2.0 series are fixed

  • [Settings] Chinese file names aren't supported (the export will fail) → use an English file name

  • [Settings] 8K VR HEVC export errors out almost 100% of the time (on the last few frames): the app now has "auto-restart on export crash + resume rendering", with a configurable retry limit (a user suggests 100); upgrade to 2.0.2+

  • For export, MKV container is recommended: "even if it errors out and exits, you can still open it in editing software" "if the power goes out, MKV can still be salvaged" G2. Export bitrate is wrong

  • "Keep the bitrate the same as the source video's" (the author); 2.0 has feedback of the bitrate input being reset, so don't touch other options after entering the bitrate G3. Red-screen flicker on export (8K video)

  • An old problem; submit the export-worker log to the author; newer versions have improved it G4. Can't find the export button

  • The location changed in the new 2.0: "too well hidden"; later versions will adjust it

H. Streaming

H1. The stream looks blurry / the bitrate is low

  • PS5 is officially limited to 1080P: "you can't stream 4k — official limit; anyone who says 4k is doing 1080 + super-resolution" (the author); "the app asks the ps5 for 100, but the ps5 only gives 20"

  • Fix: enable super-resolution in the app; have a good network (streaming eats bandwidth); "low resolution for streaming, high resolution for the capture card" (牛腩盖饭) H2. Streaming won't connect / black screen / "PS5 has ended or refused the stream (termination code 12 / error 2012)"

  • The 1.3.0 streaming bug is fixed; check the network stability on the PS5 and the PC; "test with H264SDR first"; a jailbroken PS5 can't stream H3. No sound when streaming

  • Fixed in 2.0.4 ("fixed it for you — try the new version in a bit, the no-sound-in-streaming issue"); the silent Xbox stream was fixed in the same version H4. Playing with the controller while streaming (the two-PSN-account method, the author's words)

  • "When you stream from a ps5 at close range, you can leave the controller connected to the ps5 — you don't need to connect it to the pc. You need two psn accounts: use account B to establish the stream with the app, and after it connects press the ps button to switch to account A; then press the ps button once more and go to the home page, and you can play with account A. That way the controller stays connected to the ps5" H5. Two-machine streaming (2.0)

  • PC↔PC streaming, up to 500M bitrate, about 16ms latency at 4K; good for "one machine running the game, one running Veyra"

I. Interface and controls

I1. Window/progress bar overlapping in fullscreen: "the new version will have a lock toggle"; switching to the small window makes it fly off: reopen the app I4. Presets: saving a preset doesn't save "content cadence (60→30)" with it → the author has noted "I'll add it next time"; presets can be exported and shared ("presets can be exported now, you can share them straight with a group member") I5. The V shortcut for comparing picture quality stopped working (2.0 feedback); "left/right comparison" is in the display settings I6. The performance ball is inaccurate: "the load is maxed out; right now this performance ball is inaccurate — turn the effects down" (the author) I8. Missing features (the groups' wishlist, not implemented): phone screen mirroring, AI subtitle translation, batch export/import of presets, a keyboard shortcut for the on/off switch

J. "This is not a software problem" — typical cases (important)

Here is the troubleshooting list of things most often mistaken for "software bugs" that are actually user-settings / hardware-environment problems:

  1. [Crashes] Afterburner/GamePP/NVIDIA App plug-ins → turn them off (the most common cause, and the vast majority of crash reports)

  2. [Black screen] PS5 HDCP not turned off, cable the wrong way round (IN/OUT), held by OBS → check each one

  3. [Gray picture] HDR format not matched (needs P010 + PQ HDR10) → specify HDR manually

  4. [Reddish] Pass-through cable interference / the capture card's HDR conversion switch left on → try unplugging the pass-through cable / turn off "Auto HDR to SDR"

  5. [Banding] 8bit capture card + HVA monitor + dark area enhancement on → work out which layer is the problem

  6. [No sound] Windows output not set to the capture card / the app's audio not selected correctly / "Listen" not enabled

  7. [High latency] Capture set to 30 fps or MJPEG, USB port plugged in wrong (5G/2.0), a cheap card that's just slow

  8. [Can't keep up] Not enough performance — lower NR/super-resolution; or in-app interpolation fighting NV App interpolation

  9. [Capture frame rate short] Motherboard PCIe bandwidth / MSI motherboard settings / a southbridge Wi-Fi card stealing bandwidth

  10. [4K60 NV12 unavailable] The motherboard has no USB3.2 Gen2 port; or you bought a card that "passes through 4K60 but captures 4K30"

  11. [Stutter/sluggish] NR rendering at native 4K (should be locked to 1080/1440); console output resolution set wrong

  12. [Can't stream] A jailbroken console can't stream; unstable network; the official 1080P limit

  13. [Laptop users] Can't install a PCIe card (USB cards only); power limits are severe

  14. [30-series/20-series] Don't force features that aren't supported (20-series: don't enable frame generation; 30-series: use XESS)

  15. [AMD platform] Elgato 4K Pro is community-verified working on Ryzen 7 9800X3D + MSI X670E, and the 4K60 Pro MK.2 is reported working by group testers on AMD. Do not treat AMD motherboards as categorically unsupported; check the specific PCIe slot/BIOS/driver if recognition fails. Veyra NR/DLSS support on AMD GPUs is a separate software question.

Appendix: how to report a bug to the author properly (the groups' standard)

  1. Be clear: which GPU, which capture card, which version, which game/console, the exact symptom

  2. Zip the whole logs folder under the app's root directory and send it to the author ("just zip the whole folder for me and I'll investigate and fix it")

  3. For a crash include the dmp file; for interpolation problems the fg-probe log; for export problems the export-worker log

  4. @ the author in the group ("@ me — sometimes there's a lot of traffic and I'll miss it")

  5. Cross-check with OBS first: OBS normal = Veyra problem; OBS also bad = capture card/hardware problem (an important diagnostic step)

Addendum: entries added after 2026-10-06 (each with its source)

Three entries that were already fixed in the original — I2 (auto-pause in fullscreen / the output stabilizer freezing), I3 (no sound when opening from history / having to reselect the card every time), I7 (freezing when toggling NR during playback) — have been removed.

Category A additions

  • A-A1: the Afterburner-caused crashes were fixed in 2.0.2; but GamePP and RTSS injection mode still conflict — handle them the same as A1 (turn them off → the three NVIDIA App injection toggles → a full restart) (the author, 10-03 tally).
  • A-A3: RX7000 (AMD) black screen when enabling NR: in multi-GPU setups it picked up the integrated GPU; fixed in 2.1.2 by LUID; as a workaround you can disable the iGPU in BIOS (the author, 11-03).
  • A-A4: 40-series (especially the 4070S) GPU hangs after ten-odd minutes of play: reopen the app; the mitigation is to drop NR rendering to 1080P.
  • A-A5: installing the wrong package causes all kinds of odd behavior: "there are two packages now, one AMD package and one NVIDIA package" (the author, 10-10).

Category B additions

  • B-B4: for picture flicker, upgrade to 2.1.1 first (it fixed the constant first-frame delay in screen capture); flickering only once while loading is just a mode switch.
  • B-B7: 8K super-resolution blows up the instant you click it (月光疾风 10-12, owen 10-12) — VRAM instantly maxes out; don't touch it on an ordinary card.

Category C additions

  • C-C2 (important): when an Elgato 4K Pro goes red in HDR and the OBS warm-up doesn't save it — "upgrade Elgato Studio to the 2.0 beta; it comes with a driver update for the capture card, and once that's done it's fine" (热心的猫舌头💡 10-07). The author said on the spot that he'd put this in the docs.
  • C-C7: with HDR on, every screenshot comes out overexposed (🦍 10-07) — switch to SDR before the screenshot, or take it with OBS.
  • C addition: the 27P can't capture HDR — only its pass-through has it (the author, 10-10).

Category D additions

  • D-D6: the capture has "only sound effects, no background music" (北风之刃 10-09) — change the console audio from Dolby/bitstream to PCM.
  • D addition: the T911 / G50 have no 5.1; for an Atmos extractor pick the 380 tier + dial 110 (Hi, 10-09).

Category E additions

  • E-E2: interpolation "scheduler downshift" despite a strong GPU: first check whether 60→30 was turned on by mistake, then change the capture frame rate to 59.94 (the author, 10-12).
  • E-E5: NVIDIA Low Latency: under high load choose "On", not "On + Boost" (you wait 4-18ms longer and get 8-21% less interpolation) (the author, 11-02).
  • E-E6: capturing at 30 and interpolating gives ghosting, most obvious in hair (黑猫警长 10-08) → if you can capture 60, capture 60.
  • E-E9: after the update there's an extra "Progressive" option; pick the first one (the author, 10-07).

Category F additions

  • F addition: 4K30 capture alone is 60–80ms; the author suggests "capture 4K60 and the latency is halved" (Shuuichi / the author, 10-08).
  • F addition: one NR layer is about 3.x ms (5090) to 10ms (5060), +1.7ms per layer (继续吹 10-12 / 拔筷四顾心茫然 10-22).
  • F addition: to test the chain yourself: two screens on one screen + 120/240fps slow motion, then count frame by frame how many frames apart the two sides are (the author, 10-12).

Category G additions

  • G-G3: old interlaced material (DVD / old arcade machines) displays and exports incorrectly (ygyl2 raised it on 10-15); a known limitation.

Category H additions

  • H-H3 (new): for streaming stutter, check the network card first — "my motherboard NIC seems to be 1G bandwidth, and it stutters as soon as there's load"; after switching to a discrete NIC the latency was 52ms (牛腩盖饭 10-07).

Category I additions

  • I addition: shortcuts "hold V for a quick before/after comparison; in fullscreen, Home brings up the menu" (the author, 10-12).
  • I addition: if you just want a clean picture: "turn on OBS compatibility mode in the settings, then pick Game Capture in OBS" (the author, 10-10).
  • I addition: volume adjustments not being saved → fixed in 2.1.x (reported by Snicer, 10-12).

Chapter 01 addendum: new questions from the group chats (10-06 to 11-05)

Sifted from the records of 7 community groups between 2026-10-06 and 11-05: 4033 relevant messages in total.

Highlights of this round

  • 3 fixed entries removed: I2 auto-pause in fullscreen / I3 no sound when opening from history / I7 freezing when toggling NR during playback (fixed in 2.0.2).
  • RX7000 (AMD) black screen when enabling NR: in multi-GPU setups it picked up the iGPU; fixed in 2.1.2 by LUID (the author, 11-03); as a workaround you can disable the iGPU in BIOS.
  • 40-series (especially the 4070S) GPU hangs after ten-odd minutes of play: reopen the app; the mitigation is dropping NR rendering to 1080P.
  • Elgato 4K Pro goes red in HDR: when the OBS warm-up doesn't help, "upgrade Elgato Studio to the 2.0 beta; it comes with a driver update, and once that's done it's fine" (热心的猫舌头💡 10-07).
  • 8K super-resolution blows up the instant you click it (月光疾风 10-12 / owen 10-12) — VRAM instantly maxes out; don't touch it on an ordinary card.
  • With HDR on, every screenshot is overexposed (🦍 10-07): switch to SDR before the screenshot, or take it with OBS.
  • Only sound effects, no background music: change the console audio from Dolby/bitstream to PCM (北风之刃 10-09).
  • Interpolation scheduler downshift: first check whether 60→30 is on by mistake, then change the capture frame rate to 59.94 (the author, 10-12).
  • NVIDIA Low Latency: under high load choose "On", not "On + Boost" (you wait 4-18ms longer and get 8-21% less interpolation) (the author, 11-02).
  • Capturing at 30 and interpolating gives ghosting, most obvious in hair (黑猫警长 10-08) → if you can capture 60, capture 60.
  • For streaming stutter, check the NIC first: a 1G NIC stutters as soon as there's load; after switching to a discrete NIC the latency was 52ms (牛腩盖饭 10-07).

Quotes from group members (with dates)

"@Likely7 the xsx stream freezing after enabling interpolation hasn't shown up yet; everything's normal for now except the NR black screen"

— Snicer 9070xt (10-06)

"AVerMedia can capture 5.1, and the latency is most likely the same; both support 4k30hdr"

— Focus (10-06)

"I'm planning to drop to 2k60 capture and then upscale with veyra [旺柴]; ps5 games aren't native 4k anyway, so the result shouldn't be much worse, but I get lower latency for it"

— Focus (10-06)

"I found super-resolution latency is pretty big — upscaling 2k to 4k is about 15ms of latency"

— Minions (10-06)

"So how much would full-chain latency go up if I capture gta6 at 30 fps and then interpolate?"

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

"the advantage of pcie is that the card can be bigger with less cooling pressure and more bandwidth; if it's a pcie lane directly connected to the CPU, the transmission latency can be lower"

— Snicer 9070xt (10-06)

"because I see on this chart that 4k60 has lower latency than 4k30"

— 。。。 (10-06)

"[Video Channel] Elgato 4K Pro PCIe internal video capture card, 8K/4K HDR pass-through, low-latency game streaming and recording card, works with PS5/Xbox/Switch"

— Illidan (10-06)

Veyra community documentation · November 5, 2026 snapshot · Home · Report a problem

📖 Veyra English Wiki

📷 Capture Cards

🔧 Additional Guides

🔗 Project

Clone this wiki locally