Repository navigation
Releases
VideoQuality 0.1.0
First release of VideoQuality: GPU-first VMAF comparison for video encodes, with per-frame scores through libvmaf_cuda, a frame-exact synced viewer, and multi-encode comparison.
Downloads
| Platform | File | Notes |
|---|---|---|
| Windows 10/11 x64 | VideoQuality-0.1.0-win-x64.zip |
Unzip anywhere and run VideoQuality.exe |
| Linux x86-64 | VideoQuality-0.1.0-linux-x64.tar.gz |
glibc 2.35+ (Ubuntu 22.04+, Debian 12+, …). Run ./VideoQuality; ./install-desktop-entry.sh adds it to the app menu |
Both packages are self-contained, with the .NET runtime and FFmpeg 9.0.2 + libvmaf 3.2.1 (CUDA) + dav1d bundled. Nothing else to install. GPU scoring needs an NVIDIA GPU (Turing or newer) and its driver; otherwise scoring runs on the CPU. Verify downloads with SHA256SUMS.txt.
Highlights
- CUDA VMAF, two GPU jobs at a time (900 frames of 1080p in about 1.6 s on an RTX 5060 Ti), with automatic CPU fallback. Scores are identical on Windows and Linux.
- VMAF NEG by default; standard and 4K models in Settings. Mixed models are flagged.
- Viewer: side by side, wipe, flicker, and difference heatmap with synced zoom/pan and fast stepping and scrubbing.
- Drag-and-drop drop zones (Reference / Compare), folders, paste, and Open With. A live job queue with per-row progress.
- Portable. The release folder holds just the app,
settings.json, andffmpeg/,tools/andlicenses/folders. The CLI istools/vq.
Notes
- The first launch after unpacking can be slow while antivirus scans the new files (Windows) and the app unpacks its native libraries. Later starts are quick.
- 10-bit sources are converted to 8-bit on the CUDA path (libvmaf_cuda limitation); choose the CPU backend for full precision.
- Encodes whose resolution differs from the reference are flagged but not scaled yet.
Licenses
VideoQuality is MIT. The bundled FFmpeg is LGPL 2.1+ (built without --enable-gpl/--enable-nonfree); libvmaf, dav1d and the other components keep their own licenses. Details and the FFmpeg source/configure line are in licenses/THIRD-PARTY-NOTICES.txt in each package. The build scripts are in scripts/.