Skip to content

av1gpu v0.7.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 08:34
· 136 commits to main since this release

Linux x86_64 and Windows x64 binaries for NVIDIA GPUs from Turing (RTX 20, T4) to Blackwell (RTX 50). Linux needs only the NVIDIA driver (525 or newer); Windows needs the driver (528 or newer) and the nvjpeg64_12.dll that comes in the zip. See the README for usage.

New: crop and resize on the GPU

Contributed by @pickae (#47, from discussion #16). All of it is opt-in. Without the new options every output is byte-identical to v0.6.0's: 29 test runs, 1,748 files.

  • --crop WxH+X+Y (or X,Y,W,H): crops the decoded image at any pixel offset. A crop outside the image is an error, or a skip in batch mode. With --lossless the crop is exact.
  • --max-size WxH / --max-height H: shrinks to fit inside a box and never enlarges. It uses ImageMagick's -resize 'WxH>' geometry and Lanczos filter, on the GPU, with no intermediate file and no second round of JPEG loss.
    • Transparent images are filtered with alpha-weighted colour, so there are no dark fringes.
    • From the same source, the planes are within about 0.2 of a 10-bit step of magick -resize (67 dB).
  • --max-mp MP / --max-input-mp MP: allow pictures above the 35.6 MP default (written with AV1 level 31), or decode a bigger source that a crop or --max-size brings under the limit.
  • Batch lists: a line may add TAB-separated crop= and max-size= options for its image.
  • Speed: shrinking 3840 × 5586 pages to 2960 rows runs at 169 MP/s of output on an L4, against 195 MP/s for pages shrunk beforehand.

Details.

Fixed

  • Grayscale JPEGs with sampling factors other than 1×1 (2×2, 2×1, 1×2 on their single component) came out scrambled on the hardware JPEG path, with no error. The factors are legal and libjpeg-turbo ignores them; nvJPEG doesn't. Such files now decode exactly like libjpeg-turbo on every path, in batch and single-file mode. A regression test covers them. (#44, #48)
  • compute-sanitizer racecheck no longer reports a hazard in the reconstruction kernel (since v0.6.0). The value involved was never used, so no output changes. (#43)

Known limitations

  • Windows: its speed was measured with v0.5.0 (67–83 % of Linux) and hasn't been re-run. CPU limits set by job objects or containers aren't read (the thread count follows the process's CPU affinity), and the tests run on Linux only.
  • PNG and WebP metadata: their ICC profiles and EXIF orientation are not read yet. JPEG profiles are kept, and JPEG orientation is signalled in the AVIF (irot / imir).