Veyra Veyra
☰
VEYRA SUPPORT / TROUBLESHOOTING

Fix the problem.
Get back in the game.

Experiencing a black screen, capture-card connection issue, incorrect HDR colours, missing audio or frame-generation stutter? Use this guide to identify common problems when using Veyra with GTA 6, PS5 Remote Play and external capture cards.

Many issues are caused by Windows settings, GPU drivers, HDMI connections, capture-card limitations or other software using the same device. Work through the checks below before assuming Veyra itself is faulty.
Start here

Quick troubleshooting checklist

Check these common causes first. They account for many reported problems.

Veyra crashes or won't respond

Close MSI Afterburner, GamePP and conflicting monitoring or injection software. Restart your PC if necessary.

Black screen or no signal

Check PS5 HDCP, HDMI IN/OUT connections and whether OBS or another app is using the capture card.

Washed-out or incorrect HDR

Check P010 format, PQ HDR10 input settings and Windows HDR.

No audio

Select the capture card as the audio source in Veyra and check Windows sound output and Listen settings.

Frame generation cannot keep up

Reduce NR rendering resolution and Super Resolution. Avoid running two interpolation systems simultaneously.

High latency or sluggish controls

Check capture frame rate, format and USB bandwidth. Try 60 FPS and NV12 where supported.

01 / Startup

Veyra crashes, freezes or won't open

If the application closes unexpectedly, becomes unresponsive or crashes when you start capture, check for software conflicts first.

Veyra closes immediately or stops responding

Common cause: background software conflicts

Monitoring tools and GPU software overlays can interfere with Veyra's rendering and capture pipeline.

  1. Close MSI Afterburner and GamePP.
  2. Check whether RTSS injection mode or similar overlay tools are running.
  3. Open NVIDIA App → Graphics → Program Settings → Veyra.
  4. Temporarily disable RTX HDR, Smooth Motion and RTX Dynamic Vibrance for Veyra.
  5. Fully exit Veyra and launch it again.
  6. If the problem continues, restart Windows to clear remaining background processes.

Some Afterburner-related issues were addressed in earlier Veyra releases, but other monitoring and injection conflicts may still occur.

DLSS or frame generation switches itself off

Check GPU settings
  • Open NVIDIA App and restore Veyra's DLSS overrides to Use application settings.
  • Check whether a global frame-generation model preset is overriding Veyra.
  • In NVIDIA Control Panel, set Model Presets to Application-decided, where available.
  • Fully close and reopen Veyra.
  • If initialization still fails, consider a clean GPU driver reinstall.

Veyra opens but does nothing after extraction

  • Make sure you downloaded the correct Windows 64-bit portable archive.
  • Extract the complete archive before launching the application.
  • Make sure you installed the correct NVIDIA or AMD package for your GPU.
  • If Windows Security blocks a file, verify that you downloaded it from the official Veyra website before deciding whether to allow it. Do not disable antivirus protection indiscriminately.
02 / Capture

Black screen, no signal or capture card not detected

For a PS5 connected through an HDMI capture card, check the signal path before changing Veyra's processing settings.

Check the HDMI connection direction

PS5 HDMI OUT must connect to the capture card's HDMI IN. The capture card's HDMI OUT is the pass-through connection to your monitor or TV.

PS5 shows a black screen in Veyra

  1. On PS5, open Settings → System → HDMI and turn off HDCP when using a capture card.
  2. Close OBS, virtual camera software and any other application that may be using the capture card.
  3. Check that the PS5 is connected to the capture card's IN port.
  4. Connect the capture card's OUT port to your monitor if you use HDMI pass-through.
  5. In Veyra, try a supported capture format such as NV12.
  6. For HDR capture, try P010 if your capture card supports it.
  7. Disconnect and reconnect the capture card, then restart Veyra.

OBS works, but Veyra cannot access the capture card

A capture device may be held by another application. Many capture cards cannot be opened by two applications at the same time.

  • Stop the capture source in OBS.
  • Close other capture, recording or virtual-camera applications.
  • Reconnect the capture card in Veyra.
  • Make sure you select the device and click Connect if the interface requires it.

Picture appears briefly, then Veyra crashes

  • Check whether HDR was selected automatically.
  • Try a supported non-HDR capture format first.
  • Confirm that the capture card supports the selected resolution, frame rate and format.
  • Reconnect the HDMI cable and verify the console's output mode.

Capture frame rate is lower than expected

Possible hardware or bandwidth limitation
  • Try another USB port, preferably a USB 3.2 Gen 2 (10Gbps) port for compatible USB capture cards.
  • Connect the card directly to the computer rather than through an unpowered hub.
  • Check whether another PCIe device or motherboard slot is limiting bandwidth.
  • Test the same capture card in OBS. If OBS also reports a low frame rate, investigate the card, connection or motherboard bandwidth.

4K60 or NV12 is unavailable

Not every capture card can capture at the resolution and frame rate printed on its packaging. Some cards advertise 4K60 pass-through while only capturing at a lower resolution or frame rate.

  • Check the card's actual capture specifications, not just its pass-through specifications.
  • Verify that your USB port supports the bandwidth required by the selected mode.
  • Try a direct USB-C connection or a suitable high-bandwidth USB port.
  • Check the capture card's official documentation for supported formats.
03 / HDR & Colour

HDR looks gray, red or overexposed

Incorrect HDR usually means the source, capture format, Windows settings and Veyra input colour settings are not aligned.

Start with these three settings

Use P010 where supported, set Veyra's input colour manually to PQ HDR10 for a typical PS5 HDR10 source, and make sure Windows HDR is enabled.

HDR looks washed out or gray

  1. Set the capture format to P010 if supported by the capture card.
  2. In Veyra, open Input Color / Manual and select PQ HDR10 for a PS5 HDR10 source.
  3. Enable HDR in Windows Display settings.
  4. Check that HDR is enabled on the PS5 and your display supports the selected HDR mode.
  5. Restart Veyra and test again.

MJPEG may produce poor-looking or washed-out results in some capture configurations. Do not assume that a format labelled SDR cannot carry HDR metadata; check the capture card's supported formats.

HDR looks reddish or has incorrect colours

Try the capture-card warm-up method
  1. Open OBS.
  2. Open the capture source properties.
  3. Select Custom mode if required to expose the format options.
  4. Set Color Format to P010.
  5. Set Color Space to REC.2100 PQ.
  6. Close OBS completely.
  7. Reopen Veyra and check the image.

The community guide reports that this can help capture cards that do not correctly pass HDR/WCG metadata to applications.

  • Try opening the capture card manufacturer's official software once, then close it and reopen Veyra.
  • For Elgato users, check whether Auto HDR to SDR is enabled in the official software. Turn it off if it is interfering with HDR capture.
  • If you use an Elgato 4K Pro and the issue remains, check for the Elgato Studio 2.0 beta driver update mentioned in the community guide.
  • Try disconnecting the HDMI pass-through cable to check whether it is contributing to the problem.

HDR highlights are too bright

  • Confirm whether the source uses PQ or HLG.
  • For a typical PS5 HDR10 source, try PQ HDR10 as the manual input colour setting.
  • Adjust highlight and tone settings in Veyra's colour controls.
  • For screenshots, switch to SDR first or capture the image through OBS if HDR screenshots appear overexposed.

Colour banding or vertical stripes

  • Check whether the capture card is limited to 8-bit capture. Software cannot restore colour information that the hardware does not capture.
  • Check your monitor's panel capabilities and disable monitor settings such as Dark Area Enhancement while testing.
  • For a PS5 with an AVerMedia GC573 showing vertical stripes in bright HDR areas, the community guide reports that changing PS5 HDMI transfer speed to -2 resolved this on that setup.
  • Test the capture card using its official software or OBS to determine whether the problem exists before Veyra processes the image.
04 / Audio

No sound, distortion or audio delay

If video works but audio does not, check both Windows and Veyra's audio-device selection.

No sound from the PS5 capture

  1. Open Windows sound settings and check the output device associated with your capture card.
  2. In Veyra, select the capture card as the audio source rather than relying on the default device.
  3. Enable Listen in Windows sound settings if your setup requires it.
  4. Check that the capture card appears in the Windows audio-device list.
  5. Try turning off Latency Optimization in Veyra's audio settings.
  6. If you use an AVerMedia card, check whether its official driver or audio component is installed.

Only sound effects play, but background music is missing

The community troubleshooting guide reports this with certain console audio configurations. Try changing the console's audio output from Dolby or bitstream to Linear PCM / PCM, then test the capture again.

Audio and video are out of sync

  • Check the A/V Sync setting in Veyra.
  • Try disabling automatic sync and testing manual audio compensation.
  • Adjust compensation gradually and compare the result.

Hissing, popping or electrical hum

  • Check the capture card's audio connection and power source.
  • Test audio directly from the PS5 to compare the signal.
  • Try another cable or USB port.
  • If the noise is present outside Veyra too, investigate the capture card or electrical interference.

5.1 surround sound or Dolby Atmos is not working

Surround-sound support depends on the capture card and the audio path. Many capture cards only expose stereo audio. Some AVerMedia models support specific multichannel formats, but that does not mean every card supports 5.1, 7.1 or Atmos.

For a full Dolby Atmos setup, the community guide describes using a compatible HDMI audio extractor or splitter to route audio separately to an AV receiver. Check the specifications of every device in the chain before buying additional hardware.

05 / Performance

Frame generation stutters or cannot keep up

Frame generation and neural rendering require GPU processing time. If the processing pipeline is overloaded, Veyra may not reach the selected output target.

Interpolation is limited or cannot reach the target FPS

  1. Lower the NR render resolution to 1080p or 1440p.
  2. Reduce the Super Resolution level.
  3. Use either Veyra's interpolation or NVIDIA App AI interpolation while testing. Avoid enabling both at the same time if your GPU is struggling.
  4. Check whether 60→30 content cadence is enabled accidentally.
  5. If the issue continues, try a supported capture frame rate such as 59.94 FPS.
  6. Update Veyra and your GPU driver before reporting a persistent issue.

Game looks sluggish after enabling Neural Rendering

  • Reduce NR rendering resolution to 1080p or 1440p.
  • Reduce the number or intensity of processing layers.
  • Lower the Super Resolution level.
  • Test the image with NR disabled to identify whether NR is causing the added processing delay.

Characters, hair or HUD elements flicker

  • Enable Optical Flow in NR rendering if available.
  • Try setting Video Super Resolution to Medium.
  • Test a different supported interpolation method, such as XESS.
  • Compare the image with NR and frame generation enabled separately to identify which stage introduces flickering.

Ghosting, jelly effect or tearing

  • Capture at 60 FPS when your source and capture card support it. Interpolating a 30 FPS source can produce more visible artifacts and less responsive motion.
  • Try XESS interpolation and Optical Flow.
  • Test sharpening to see whether it reduces visible interpolation artifacts.
  • Set your display to its intended refresh rate, such as 120Hz when supported.
  • Enable V-Sync if you are experiencing tearing.

Output is below the target frame rate

  • Check whether V-Sync or another frame-rate limit is active.
  • Reduce NR and Super Resolution settings.
  • Check the actual input resolution and frame rate from the console or capture card.
  • Make sure the source is not unintentionally outputting at a lower resolution or frame rate.
Important: frame generation does not increase the game's native rendering FPS.

Veyra processes the video output and can generate additional displayed frames. It does not change the game's internal frame rate or guarantee a particular FPS target on PS5.

06 / Latency

High input delay or sluggish response

Latency comes from the complete chain: console output, capture hardware, USB or PCIe connection, video processing and display.

How to reduce latency

  1. Use a 60 FPS capture mode where supported instead of 30 FPS.
  2. Try NV12 instead of MJPEG, RGB or YUY2 where your card supports it.
  3. Connect USB capture cards to a suitable high-bandwidth USB 3.2 port.
  4. Reduce the NR render resolution to 1080p.
  5. Reduce processing layers and Super Resolution intensity.
  6. If you need very low capture latency, compare a direct PCIe capture card with a USB model.

Why does 30 FPS capture feel less responsive?

A 30 FPS source has a longer interval between original frames than a 60 FPS source. Frame generation can add intermediate frames, but it cannot restore the original input responsiveness of a higher-frame-rate source.

For gaming, use a 60 FPS source whenever your console, capture card and connection can reliably provide it.

How to compare capture latency

One community testing method is to compare the capture-card HDMI pass-through image with the processed preview while displaying the same millisecond stopwatch. Use the same refresh rate on both displays and account for the extra delay introduced by OBS if you use it for comparison.

07 / PS5 Remote Play

Streaming problems with GTA 6

If you are using PS5 Remote Play rather than an HDMI capture card, check the network and streaming configuration.

PS5 stream looks blurry or low resolution

The troubleshooting wiki documents a 1080p limit for the PS5 Remote Play stream. Veyra can apply Super Resolution to process the incoming image, but that does not mean the PS5 is sending a native 4K stream.

  • Enable Super Resolution in Veyra if your GPU can handle it.
  • Check network stability on both the PS5 and Windows PC.
  • Reduce network congestion during streaming.
  • If you need a higher-resolution HDMI input, consider a compatible capture card instead.

PS5 stream will not connect or shows a black screen

  • Check that the PS5 and PC have a stable network connection.
  • Try the H264 SDR streaming mode as a diagnostic test.
  • Restart the console, Veyra and your network equipment if the connection remains stuck.
  • The community guide reports that jailbroken PS5 consoles cannot use the documented streaming method.

Streaming stutters even with a good GPU

  • Check network congestion and packet loss.
  • Check the PC's network adapter and available bandwidth.
  • Test using a wired network connection where possible.
  • Compare performance with a lower streaming resolution or bitrate.
08 / Export

Video export fails or produces incorrect output

For local video processing, check the file name, output format and export logs.

Export fails near the end or at 99%

  • Try using an English file name and a simple output path.
  • For 8K VR HEVC exports, check that you are using a version with the relevant export recovery improvements.
  • Try the MKV container where available. It can be more recoverable if an export is interrupted.
  • Update Veyra before retrying an export that repeatedly fails.

Export bitrate is incorrect

Check the bitrate field before starting the export. The community guide recommends keeping the bitrate aligned with the source video when that is your intended output. Verify the final file's properties after export.

Cannot find the export option

The export control was moved in the 2.0 interface. Check the current export workflow and documentation for your installed version.

09 / More help

Frequently asked troubleshooting questions

Does Veyra make GTA 6 run natively at 120 FPS on PS5?

No. Veyra processes the video output and can generate additional displayed frames. It does not change GTA 6's native rendering frame rate on the console or guarantee a 120 FPS output in every setup.

Why does my capture card work in OBS but not in Veyra?

OBS may be holding the capture device, or Veyra may be using a different capture format or connection setting. Close OBS completely, reconnect the device in Veyra and test again.

Why does my capture card show 4K60 pass-through but only capture 4K30?

Pass-through and capture specifications are different. Check the manufacturer's actual capture-resolution and capture-frame-rate specifications before assuming the card can record or process 4K60.

Can I use HDR with every capture card?

No. HDR capture depends on the card's supported formats, bit depth, drivers and metadata handling. Check the card's capture specifications, not only its HDR pass-through claims.

Why does Veyra add input latency?

Capture hardware, connection bandwidth, resolution, NR processing and frame interpolation all contribute to the total delay. Lower processing resolution and a reliable 60 FPS capture path can help.

What information should I include when reporting a bug?

Include your Veyra version, GPU model, capture-card model, console or video source, exact symptoms and steps to reproduce the issue. Include the relevant application logs and crash files where available.

10 / Bug reports

Still having trouble?

If the steps above do not solve the problem, send a useful bug report instead of simply saying that Veyra does not work.

  1. Identify your setup. Include your GPU, capture-card model, Veyra version, Windows version and whether you are using PS5 Remote Play or HDMI capture.
  2. Describe the exact problem. Explain what you expected, what actually happened and the steps that reproduce it.
  3. Test with OBS. Check whether the same capture problem appears in OBS. If both applications show the issue, investigate the capture card, connection or hardware first.
  4. Collect the logs. Zip the complete logs folder from the Veyra application directory. Include the crash dump for crashes, FG probe log for interpolation problems or export-worker log for export failures, if available.
  5. Submit the report. Include the logs and relevant details when opening a GitHub issue or asking the community for help.
Protect your privacy before sharing logs.

Check log files for personal information, account identifiers, file paths or other sensitive data before uploading them publicly.