Guide 05 Console and Streaming

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 — 05 — Console Setup and Dual-PC Streaming

---

Veyra User Guide - 05 - Console Setup and Dual-PC Streaming

Covers: PS5 / Switch 2 / Xbox setup templates, streaming, dual-machine (dual-PC) setups, audio setups

Compiled from group discussions, 2026-09 to 2026-10

1. Standard PS5 Setup Template (a group member's "阿莫视觉" version, copy it verbatim)

[1. PS5 console settings (set up the console first!)] Settings → Screen and Video → Video Output

• Resolution: 2160p (4K)

• Refresh rate: 60Hz (not auto / 120Hz)

• HDR: off during tuning, then enable as needed once stable

• RGB range: auto Settings → System → HDMI

• Turn off HDCP (critical — leaving it on locks the frame rate / causes a black screen)

• Audio output: HDMI, sample rate 48kHz [2. Capture card settings]

• Capture card input: 2K60 or 4K60 (depending on the card); set the HDMI input to the matching resolution

• Audio: DirectShow / capture card audio [3. Veyra settings]

• Capture card input: 2K60 NV12 SDR (or 4K60 NV12)

• Input color: auto detect (or manual P010 + PQ HDR10)

• Motion section: AMD optical flow + XESS 2x generation

• Content cadence: for PS5 30 fps games choose "capture 60→30"

• Set the monitor to 120Hz (avoids major tearing after frame generation) [PS5 quick troubleshooting]

• Black screen / no signal → turn off HDCP first

• Vertical stripes in bright areas (GC573) → display settings → set HDMI transfer speed to "-2"

• Sound but no picture / picture but no sound → toggle HDCP / check the audio output

• Washed-out picture → match the HDR format (P010 + PQ); if the system UI looks fine but the game is washed out, restart the game

• 4K HDR RGB passthrough freezes → lower the transfer speed

• Streaming: officially limited to 1080P (see the streaming chapter)

2. Switch 2 (NS2) Setup and Experience

[Basics]

• NS2 in its dock outputs HDMI → capture card (the NS2 doesn't output video over USB, so forget about connecting it directly)

• On a 2K screen: T800/27P/G50 are enough; "for ns2 games, 1080p capture might even be enough"

• VRR: only cards that support VRR, such as the G50, can take advantage of it [Known issues]

• A capture card without HDR support makes the NS2 turn HDR off automatically → the picture gets noticeably darker (not a fault): Fix: "turn hdr off on the switch, or set the capture format to P010" (if the card supports HDR)

• No sound from capture → in the app, "pick hdmi Kuhaomi / audio input / the capture card entry" (the path the author gave)

• Results for reference: "ns2 2k60 goes straight up to 4k120" "the ns is perfectly adapted now — the icons used to tear, in the new version there's none of that" "playing ns2 through capture is much smoother than ps5"

• 2.0.3 has reports of worse ghosting on NS2 → roll back to 2.0.2 [Recommended recipe] Capture 2K60 → NR 1080P → upscale 2K/4K → XESS 2x (Zelda can reach 120 fps)

3. Xbox (XSX/XSS)

• Basically the same as PS5: turn off HDCP, set the HDMI output to the matching resolution

• Xbox streaming: Veyra's streaming feature currently only covers PS5; users are already asking for an XSX streaming mode (per the author's notes)

• The no-audio issue with Xbox streaming was fixed in 2.0.4 ("I fixed it for you — try the new version in a bit")

• Xbox HDR formats: XSX games mix PQ and HLG → the app can't fully auto-detect it, so "go manual, auto has issues" (the author)

4. Streaming (PS5)

[Official PS5 streaming (built into the app, chiaki NG core)]

• Resolution limit: 1080P officially ("the app asks ps5 for 100 bucks, but ps5 only gives 20")

• Quality: it blurs once things move (low bitrate); 1080P streaming latency can be as low as 5-10ms (on a good network)

• Conclusion: low resolutions (1080/2K) are fine for streaming; use a capture card for 4K ("low resolution for streaming, high resolution for capture cards") [Streaming with two PSN accounts (confirmed workable by the author, no controller hassle)] The author's own words: "when streaming to a ps5 nearby, you can keep the controller connected to the ps5 instead of connecting it to the pc. Simply put, use two psn accounts: establish the stream with account B, and once connected press the ps button to switch to account A, then press the ps button once more and go to the home screen, and you can play with account A. That way the controller stays connected to the ps5." [Streaming controller] When connected to the PC, "it has to be usb" "bluetooth doesn't work" [Common issues]

• Can't connect / black screen: check the network (connect both the PS5 and the PC to the router or by cable), "test with H264SDR first"

• Jailbroken PS5: can't stream ("it says the session has ended or been refused")

• One case where the app stopped working after chaining streaming + Moonlight: an NVIDIA driver fault, solved by a clean driver reinstall [Dual-PC streaming (new in 2.0)]

• PC↔PC streaming, "the max bitrate is 500m now", about 16ms of latency at 4K

• "run the streamed picture through the capture card channel and the controller protocol through the streaming channel" (an advanced trick; a feature request has been filed)

5. Dual-Machine (Two-PC) Setups

[Why two machines]

• "one machine renders native quality, the other runs DLSS5" (七迷)

• Typical (9070 + 5060 Ti): "the 9070 runs the game with one layer of dlss5 locked at 60, then feeds the capture to the 5060 Ti for another layer" (牛腩盖饭)

• "the old build becomes the gaming side, the strong build becomes the compute side, and one decent capture card gives it a second life" (牛腩盖饭)

• "the 5070 Ti runs one layer itself, the 5060 Ti adds a layer on capture — two PCs" (蚂蚱儿) [How to set it up]

1. Capture card approach: gaming machine → capture card → processing machine (recommended for 4K) "2k streaming is okay, but I need 4K" "if you want 4k from dual PCs you still have to go through a capture card"

2. Streaming approach: streaming over the LAN (latency as low as single-digit ms to 16ms); suitable for 1K/2K

3. 2.0 dual-machine streaming: built into the app, 500M bitrate [Dual-machine streaming for live broadcasts] "for the card doing the encoding, it's still best to use a capture card to capture the main card's desktop picture again" [Caveats]

• Running DLSS5 across two machines requires both sides to be strong enough; "even a 3060 chokes, let alone a 10 series" (about a streaming machine that's too weak)

• For users with a single monitor: "you don't need two computers, you need two display devices" (the other school of thought — with the capture card approach a single machine can do it too)

• Dual-GPU (two graphics cards in one machine) setups: demanding on the motherboard, PSU, and case; the group generally recommends two machines instead

6. Audio Setups (console scenarios)

[Basic needs]

• PS5 audio output → HDMI (captured by the capture card); on the PC, select the capture card audio + monitoring in the app

• Remember to select the "device with the same name as the capture card" in the Windows sound output [Dolby 5.1]

• Only AVerMedia capture cards support it (AC3 5.1); OBS needs the AVerMedia plug-in (AVerMediaMultichannelAudio)

• Switch the PS5 audio output to "Dolby" [Dolby Atmos (full-fat setup)]

• Requires an HDMI audio extractor/splitter: Setup: PS5 → splitter → one HDMI to the AV receiver (Atmos), one to the capture card and on to the monitor (verified working by LJY) Buying note: "the 200-something ones can only extract old-school Dolby 5.1" "you have to set the dial to 110 to extract Dolby Atmos, the built-in 111 only extracts dd+"; "get a 380 audio extractor and you can have full-fat Dolby Atmos straight away" (Hi)

• Simpler option (no splitter needed, from XH): "just connect the passthrough output to a Dolby Atmos AV receiver"

• Soundbar users can do: passthrough → soundbar, capture card takes the picture [Veyra support] Dolby Atmos supported since 1.4.0

7. Live Streaming Configuration Reference

• Standard dual-display setup: passthrough to your own monitor (play directly), and the captured picture goes into the PC for OBS streaming/broadcasting

• "obs captures the 5.1 audio track, this (Veyra) mirrors the picture, with no latency" (the standard split-the-work solution)

• Capturing Veyra's picture in OBS: choose "game capture" (no UI); window capture of Veyra is a known limitation

• For streamers: don't use the app's "local window capture" with online games (ban risk)

• Douyin live streaming can use Veyra's output: "Douyin live takes the frame-generated picture, and the stream looks much smoother"

• OBS recording stutters → turn on "obs compatible" (in settings; the author is still working on it)

8. Managing Latency Expectations (console player edition)

• A 30 fps console game comes with 33ms of render latency; frame generation only fixes smoothness, not responsiveness ("icing on the cake")

• 30 → 60 vs 60 → 120: the former feels "sticky", the latter "feels close to a native high refresh rate" (北风之刃)

• End-to-end reference: "if the capture card is fine it's usually around 50ms, the app's latency is generally 15-20ms, so about 70ms in total" (翼)

• The perceptual threshold varies by person: "some people think 100ms is fine, others can't accept 50ms" ================================================================

---

9. This Update: More Streaming and Console Measurements (with dates)

Stuttering streams? Check the network card first

• 牛腩盖饭 (10-07) had intermittent stutter at 4K60 streaming; in their own words: "my motherboard network card seems to have 1G bandwidth, theoretically 105–118MB/s, and it stutters once there's load"; after switching to a dedicated network card it was fine, with 52ms of latency.
• The same person, another message: "just found out that with NR 1440p and 4K60 streaming, latency is only 50".
• 1080P streaming really is blurry: "forget streaming, 1080P is too blurry" (Milk 10-07); "streaming is unplayable" (Allen丶丶 10-07).

PS5 quality mode is often 2K in practice

• The author (10-12): "many games run at 2k in quality mode — that doesn't matter much" "it depends on whether you want native HDR".

HDR and hard limits of capture cards

• The 27P can't capture HDR, it's only available on passthrough (the author 10-10) — to enable HDR on NS2 you have to switch to a P010 card.
• The T911 / G50 have no 5.1; for surround sound choose an AVerMedia card or use a splitter.

Audio

• Sound effects but no background music: change the console audio from "Dolby/bitstream" to PCM (asked by 北风之刃 10-09, the group provided the solution).
• Atmos splitter: "the 200-something ones only extract old-school Dolby 5.1, the 380 one gives full-fat Atmos, with the dial set to 110" (Hi 10-09).

Latency

• 4K30 capture alone costs 60–80ms; the author suggests "capture 4K60 and latency drops by half" (Shuuichi / the author 10-08).
• One NR layer costs about 3.x ms (5090) to 10ms (5060), plus roughly 1.7ms per layer (继续吹 10-12 / 拔筷四顾心茫然 10-22).

Chapter 05 Addendum: New Console and Streaming Q&A (10-06 to 11-05)

Filtered from the records of 7 chat groups, 2026-10-06 to 11-05, 2324 relevant messages in total.

Highlights of This Round

• Stuttering streams? Check the network card first: a 1G network card stutters once load builds up; after switching to a dedicated card the latency was 52ms (牛腩盖饭 10-07).
• PS5 quality mode is often 2K: "many games run at 2k in quality mode" (the author 10-12), "it depends on whether you want native HDR".
• The 27P can't capture HDR (the author 10-10) — to enable HDR on NS2 you have to switch to a P010 card.
• Sound effects but no background music: change the console audio to PCM (北风之刃 10-09).
• Atmos splitter: the 200-something models only reach 5.1; you need the 380 tier + dial 110 for the full experience (Hi 10-09).
• 1080P streaming really is blurry: "forget streaming, 1080P is too blurry" (Milk 10-07).
• 4K30 capture alone costs 60-80ms; the author suggests "capture 4K60 and latency drops by half" (Shuuichi / the author 10-08).
• The T911 / G50 have no 5.1; for surround sound choose an AVerMedia card or use a splitter.

Group Members' Own Words (with dates)

"@Likely7 the issue where the picture freezes after turning on frame generation on xsx streaming hasn't shown up so far — everything is normal except the NR black screen"

— Snicer 9070xt (10-06)

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

— Focus (10-06)

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

— Illidan (10-06)

"low frame rate and high latency are not the same thing — low frame rate means the picture doesn't look smooth, high latency means the character only reacts a second after you press the controller"

— Focus (10-06)

"xsx streaming is all OK, picture latency and responsiveness are pretty OK"

— Snicer 9070xt (10-06)

"damn, veyra's latency is over 100ms lower than the passthrough hdmi"

— 张敏轩 (10-06)

"I only just found out that with NR1440p and 4k60 streaming, latency is only 50"

— 牛腩盖饭 (10-07)

"honestly this looks less sharp than qssr in my ps5 performance mode"

— W (10-07)

---