Guide 00 Overview

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 — 00 — Overview and Contents

---

This document was compiled from the chat logs of 7 official community groups (Veyra Dlss Community Groups 1-7). Coverage: 2026-09-13 ~ 2026-11-05 Compiled: 2026-11-05 (previous edition 2026-10-05) Software versions covered: 1.3.0 ~ 2.1.2 (2.1.2 is authoritative; older versions may behave differently)

[Important]

• All conclusions in this guide come from group members' real-world testing and from answers given by the author (the channel owner, Likely7). They are for reference only.

• The software updates quickly. If you hit a new problem, go by the latest version first, and send the logs to the author for diagnosis before anything else.

• The standard procedure when something goes wrong: first check the "Troubleshooting Manual" in this guide, then try the "three switches": turn off MSI Afterburner → disable the NVIDIA App graphics filters for Veyra → update the GPU driver.

I. What Veyra Is

Veyra (GitHub project name: Veyra-NRVideo) is a video-processing app developed by the channel owner, Likely7. Working together with a capture card, it brings in the picture from a console (PS5 / Switch2 / Xbox) or from another PC and does the following in real time on the computer:

Capture → NR (DLSS5 enhancement) → Super-resolution (upscaling / SR) → Frame generation (interpolation) → Output to the screen

Core capabilities (version 2.0):

• NR (neural rendering): DLSS5-based image enhancement that markedly improves faces, materials, and clarity; commonly known as "putting on glasses"

• Super-resolution: 4K/6K/8K target resolutions available, so even a 1080P capture can be upscaled to 4K

• Frame generation (interpolation): 2x/3x/4x/dynamic frames; a 30 fps game can be brought up to 60~120 fps

• Player side: local video playback (MKV, IMAX, subtitles, audio tracks, SRT import) can also go through NR + super-resolution + interpolation

• Streaming side: built-in PS5 streaming (chiaki NG core, officially capped at 1080P); since 2.0, PC-to-PC (dual-machine) streaming is supported, at bitrates up to 500M

• Extras: color-grading page (LR/PS-style, LUT import), capture-card flip, Dolby Atmos support, screenshots, preset import/export

[The author's own words]"Without AI there would be no such software — I wouldn't write a single line of code." The app is developed with AI assistance and updates frequently (at one point, once a day).

---

II. Getting and Updating the Software

• GitHub (updates land here first): https://github.com/Likely7/Veyra-NRVideo (Direct access from mainland China sometimes fails; you can use a mirror — https://gh-proxy.org/ or https://v4.gh-proxy.org/ — prepended to the original address)

• Cloud drive: the Baidu Netdisk link in the group announcement (the author uploads in sync with every release)

• The filename looks like: Veyra-2.0.2-win64-portable.zip

• Download notes: pick the win64 portable archive; "the downloads are split by GPU — NVIDIA cards take the NVIDIA build, AMD cards take the AMD build"; you don't need that dependency package

• Upgrading: just delete the old version and extract the new one (different versions can coexist in separate folders)

• If Windows Security blocks it: turn off Windows Security or add the file to the whitelist

• English documentation: Veyra Wiki

• Capture card index: Capture Card Index

• Capture-card comparison: Prices & Latency

[Version at a glance]

• 1.3.0: capture-card settings persistence, washed-out gray fixed, player improvements, partial Dolby Vision support, AV1 import

• 1.3.1/1.3.2: 6x frame generation on the 30/40/50 series, capture-card flip button, embedded subtitles in MKV, MJPEG latency down 80%

• 1.4.0: color-grading page + LUT, Dolby Atmos, major overhaul of the player pipeline, "30 fps content can get close to 120 fps"

• 1.4.1: fixed saved presets being lost, unlocked 6x frame generation on the 30/40 series, greatly reduced "frame-generation limited"

• 1.4.2: RTX HDR (can enhance the panel), local window capture, automatic config saving

• 1.4.4: original NR (one layer ≈ two layers in 2.0)

• 2.0.0 / 2.0.2 / 2.0.3: front-end rewrite, Afterburner conflict fixed, original NR back, dual-machine streaming, screenshot hotkey

• An example of what 2.0.2 fixed: "Freezing is most likely because Afterburner is running — 2.0.2 fixed that."

---

III. Prerequisites (the points the group keeps repeating)

1. GPU: RTX 30/40/50 series recommended; on the 20 series you can basically "turn it on, but it stutters to death"; AMD cards (9000 series) are experimental support

• The 30 series works but performance is limited ("a 3060 may not be able to interpolate"); with a 4060 8G, lower NR rendering to 1080P or even 900P

1. Capture card: the app can do nothing about the card's own latency — "most of the latency still sits in the capture card" (the author)

• If you want low latency, prefer a PCIe card in a real slot; for 4K60 on a USB card, use the NV12 format

1. Capture format: prefer native formats (NV12 / YUY2 / RGB24 / P010), do not use MJPEG ("MJPEG is a compressed format; it has to go through another stage once it reaches the PC, so latency is high and image quality is poor — better not to choose it." — the author)

2. Common setup steps beforehand:

• Consoles such as the PS5: turn off HDCP (leaving it on locks the frame rate / causes a black screen); set the console's output resolution correctly (don't feed 1080P and let super-resolution fake the rest)

• PC: close monitoring software such as MSI Afterburner / GamePP, or open it only after the app is already showing the picture

• NVIDIA App → Graphics → Program Settings → turn these off for Veyra: RTX HDR / Smooth Motion / RTX Dynamic Vibrance (the built-in warning, verbatim: "NVIDIA App graphics filters (RTX HDR / Smooth Motion / RTX Dynamic Vibrance) have been injected into Veyra. They are known to make the GPU device disappear when capture starts or to crash the program.")

• In NVIDIA App, set Veyra's DLSS overrides (especially the frame-generation model preset) back to "Use application settings"

• Keep the GPU driver up to date (many "can't enable DLSS / error" cases are ultimately solved by reinstalling the driver)

---

IV. Document Directory (every file in this folder)

[Overview]

• 00 Overview and Contents (this document)

• 01 Troubleshooting Manual: look up the fix by symptom (crash / black screen / color cast / no sound / stutter...)

• 02 Features and Settings in Detail: what every option means and how it should be configured

• 03 Capture Card Basics and Buying Guide: formats / bandwidth / latency / motherboards / pitfalls

• 04 Analysis of the Capture Cards That Cause the Most Problems in the Group: which card has the most issues, the evidence, and alternative suggestions

• 05 Console Setup and Dual-PC Streaming: PS5/NS2/Xbox setup templates, streaming, dual-PC setups

Capture Card Model Chapters

• Capture Card - AVerMedia GC553G2 Series (G2)

• Capture Card - AVerMedia GC573

• Capture Card - AVerMedia GC553 (old version) and 553 Pro

• Capture Card - Other AVerMedia Models (575, 535, 551, etc.)

• Capture Card - ASUS 4KPRO

• Capture Card - Kuhaomi G50

• Capture Card - Kuhaomi 26P and 27P

• Capture Card - Michensen T800 and T900

• Capture Card - Elgato (4K X / 4K60 Pro MK2 / 4K Pro)

• Capture Card - Magewell

• Capture Card - Lvjuneng

• Capture Card - Acasis

• Capture Card - UGREEN

• Capture Card - Quick Reference for Other Brands and Budget Cards (Hagibis, Philips, Chuangshi Zhixing, Blackmagic, the 2130s reference design, etc.)

---

V. Top 10 Pitfalls Beginners Fall Into (see manual 01 for details)

1. The app crashes / becomes unresponsive → conflict with MSI Afterburner / GamePP, or NVIDIA App filters being injected

2. No picture / black screen → HDCP was not turned off on the PS5, or the capture card is held by OBS, or the HDMI cable is plugged in backwards (IN/OUT)

3. Washed-out gray / reddish cast / banding → wrong capture format (P010 has to be paired with PQ HDR10), an 8-bit-only capture card, a monitor panel issue

4. No sound → Windows audio output isn't set to the capture card, or in the app you have to pick the audio device named after the capture card and enable monitoring

5. High latency → capture frame rate set to 30 (30 doubles the latency of 60), MJPEG format, a cheap card

6. Frame generation limited / can't keep up → not enough performance; lower the NR resolution / super-resolution; or choose one of the two — in-app interpolation or NV App AI interpolation

7. "Input frame rate too low / only 53 fps" → motherboard PCIe bandwidth problem (especially MSI AMD boards), or the wrong USB port (a 5G port used as 10G)

8. 4K60 NV12 won't work → the motherboard has no USB3.2 Gen2 (10Gbps) port; check the motherboard before buying a card

9. Games stutter / feel sticky with NR on → lower the NR rendering resolution (1080P/1440P), lock the console output to 60

10. Flickering / tearing → enable optical flow, set video super-resolution to medium, a 120Hz monitor, vertical sync / frame cap

---

VI. A Troubleshooting Mantra for Group Members (summarized from the group)

"First close Afterburner, then close the NVIDIA filters, then reinstall the driver once; black screen — turn off HDCP first; no sound — pick the capture card first; gray cast — check the format; red cast — adjust PQ; banding — check the monitor first; capturing at 30 doubles latency; capturing at 60 is the only right way; most of the latency lives in the capture card — don't take the blame for the software layer."

Compilation statement: this guide is a hand-compiled version of group chat content and does not constitute official documentation; the prices quoted are group rates at the time of compilation and will change with the market; some methods are version-dependent, so try them against your own hardware and software setup.

---

What's New in This Edition (2026-11-05)

Item	Previous edition (2026-10-05)	This edition
Chat-log coverage	2026-09-13 ~ 10-05, 4 groups	2026-09-13 ~ 11-05, 7 groups
Applicable versions	1.3.0 ~ 2.0.2	1.3.0 ~ 2.1.2
Chapters	7 chapters + 16 capture-card pages	9 chapters + 25 capture-card pages (one page per card)
Added	—	07 M.2 to PCIe Guide, 08 PCIe Riser Guide
Capture cards	16 models	new in-depth Michensen T911 page; G50 / 27P / 553G2 / 571 and others completed
FAQ	included already-fixed entries	already-fixed entries removed; 20+ new entries with sources

Contents

• 00 Overview and Contents (this document)
• 01 Troubleshooting Manual — A Startup crashes / B Capture picture / C Color and HDR / D Audio / E Frame-generation performance / F Latency / G Export / H Streaming / I Interface / J Not a software problem
• 02 Features and Settings in Detail — pipeline, NR, super-resolution, frame generation, quality page, audio input, performance tiers, scene templates, hotkeys; plus 2.1.x new features at the end
• 03 Capture Card Buying Guide — spec-sheet tricks, format primer, latency baselines, port bandwidth, motherboard compatibility, cooling and power, recommendations by budget; plus the November 2026 market at the end
• 04 Analysis of the Capture Cards That Cause the Most Problems in the Group — GC573 / ASUS 4KPRO / UGREEN / spec flaws / best reputation; plus 7 new cases at the end
• 05 Console Setup and Dual-PC Streaming — PS5 / Switch2 / Xbox, streaming, dual-PC, audio, live streaming; plus streaming and NIC tests at the end
• 06 Standard Reply Templates for Group Questions — 23 copy-and-paste answers
• 07 M.2 to PCIe Guide (new)
• 08 PCIe Riser Guide (new)

Capture card pages (25 articles, one page per card) Michensen T911 / T800 / T900; Kuhaomi G50 / 27P / 26P; AVerMedia GC553G2 / GC573 / GC575 / GC571 / GC551G2 / GC551 / GC553 / GC553 Pro / GC535 / GC550; Elgato 4K X / 4K60 Pro MK2 / 4K Pro; ASUS 4KPRO; Magewell; Acasis; Lvjuneng; UGREEN; other brands and budget cards

Three Conclusions

1. Most of the latency is in the capture card and the capture format, not in Veyra; capturing at 30 doubles the latency of capturing at 60, and MJPEG latency is twice that of NV12 (the author, in several places).
2. A 10G port + NV12 is the pass mark for USB cards; 4K60 HDR is basically PCIe-only (or Magewell 20G).
3. Frame generation is icing on the cake, not a rescue: a 30 fps source carries 33ms of render latency of its own.