Likely7/Veyra-NRVideo
Bring PS5 GTA6 to 120FPS with DLSS 5. An advanced Windows video player and capture enhancement tool featuring real-time preview for videos, images, and capture card sources. Combine AI-powered Super Resolution, DLSS5 image enhancement, and
Read original source
Source record
Recorded metrics
daily_stars · 245 stars today
2026-11-13 14:53:15.571Z
GitHub daily Trending window; attention only
Project analysis
Problem & scenario
The supplied evidence describes Veyra, a Windows GPU video-enhancement tool. Its relationship to WeWorkBuddy is unspecified. Veyra addresses users processing local video, capture cards or game streams through one real-time enhancement pipeline. Representative example, inferred from the documented workflow, is a console player bringing capture-card video into a Windows PC. Before, the player selects a capture mode and watches the source feed. With Veyra, they verify picture and audio, then enable super resolution, denoising or frame generation and save settings. This brings enhancement controls into the viewing workflow, but adds GPU/VRAM demand and device-compatibility setup. Windows 11 x64 and DirectX 12 are required.
Features & advantages
Veyra combines multiple source types with layered enhancement and an executable node editor. Users can configure independent NR and colour parameters, place supported effects before or after super resolution, and retain separate List and Node settings. This gives users control over processing order when tuning a picture. The trade-off is constrained execution and workflow switching. Nodes need a valid input-to-output path, the graph has limited branching, and the documented Node workflow lacks offline export and List mode’s global NR protection region. S2 names Moonlight/Sunshine compatibility but supplies no same-task feature comparison with a named alternative, so a competitive advantage remains unestablished.
Technical approach
Veyra documents a C++/DirectX 12 application with executable processing chains. A node-editing path starts when a user connects input, effect and output nodes. A valid connected path determines which effects execute. NR and colour nodes carry independent parameters, optical flow is shared after input, and RTX Video HDR precedes final frame generation. Switching modes rebuilds processing and can briefly pause the picture. Deployment requires the matching NVIDIA or AMD portable package, a writable folder and separately installed GPU/capture drivers. Layered effects increase GPU/VRAM demand. These are README-level mechanisms. No commit-pinned code was supplied to verify functions, validation logic or persistence internals.
Business model & buyers
The documented delivery model is a downloadable, GPL-3.0 open-source Windows application. S2 gives installation and upgrade instructions but provides no price, payment method, subscription or paid entitlement terms. Likely users include console/capture enthusiasts and people enhancing local video or PC streams. A plausible purchase trigger, if a paid offer exists, would be needing reliable enhancement on an existing capture or viewing setup. That buyer hypothesis is unverified. Hardware compatibility and setup effort shape the value proposition because users must supply supported GPUs and drivers. Revenue, paying customers and commercial licensing terms cannot be established from the supplied material.
Growth & distribution
GitHub Releases is a documented acquisition entry point with measurable download activity. S2 reports 79,332 portable-package downloads as of 2026-11-08 and 103,337 downloads across all release assets, explicitly counting events. S1 records a GitHub Trending discovery source without an observation date. The likely activation path is to download the matching GPU package, open a source, verify playback, then enable an effect to see its result. Saved presets and sessions could support repeated use, but retention is unmeasured. Hardware requirements, capture configuration and upgrade migration create adoption friction. Downloads establish distribution activity, while user conversion, acquisition attribution and sustained usage remain unknown.