{"id":51189,"date":"2026-05-12T11:47:20","date_gmt":"2026-05-12T11:47:20","guid":{"rendered":"https:\/\/ubuntuhandbook.org\/?p=51189"},"modified":"2026-05-12T11:47:20","modified_gmt":"2026-05-12T11:47:20","slug":"nvidia-va-api-driver-0-0-17","status":"publish","type":"post","link":"https:\/\/ubuntuhandbook.org\/index.php\/2026\/05\/nvidia-va-api-driver-0-0-17\/","title":{"rendered":"NVIDIA VA-API Driver 0.0.17 Added JPEG Decoding & DGX Spark Support"},"content":{"rendered":"

\"\"<\/p>\n

NVIDIA VA-API driver, the VA-API hardware acceleration implemention using NVIDIA GPU, released new 0.0.17 version a few days ago.<\/p>\n

The new version of this free open-source library fixed only two but important bugs for JPEG decoding and NVIDIA DGX Spark memory systems.<\/p>\n

<\/p>\n

\"\"

Firefox Web Content acceleration through NVIDIA GPU<\/p><\/div>\n

As you may know, Linux has several ways (VA-API, VDPAU, AMF, NVDEC, or Vulkan Video) for decoding video content with GPU hardware acceleration. Firefox, the most popular and default browser in many Linux Distributions, however only supports VA-API so far in Linux.<\/p>\n

Both Intel and AMD GPUs support VA-API, but NVIDIA does NOT. If you’re Firefox user but running Linux on computer with NVIDIA GPU, then the web content will be always decoded by your CPU by default.<\/p>\n

To workaround the issue, the free open-source NVIDIA VA-API driver<\/a> was born.<\/p>\n

JPEG Decoding support<\/h3>\n

The driver previously supports for decoding AV1, H.264, HEVC, VP8, VP9, MPEG-2, VC-1 codecs. With the new 0.0.17, JPEG decoding is also supported<\/b>.<\/p>\n

The JPEG codec was previously unusable due to a structural mismatch. VI-API outputs decoded data as separate buffers (e.g., picture params, quantization tables, Huffman tables, slice params\/data), but NVIDIA NVDEC expects a fully formed JPEG bitstream.<\/p>\n

To fix this mismatch, NVIDIA VA-API driver since 0.0.17 now creates smallest valid JPEG file that conforms to the JFIF standard, directly from the VA-API buffers, before handing it off to NVDEC.<\/p>\n

According to the feature request<\/a>, the results are exactly identical at the byte level and hash-verified compare to the decoding outputs using the native NVDEC (CUDA). Though there are few limitations (see the previous link).<\/p>\n

Fix for DGX Spark<\/h3>\n

NVIDIA DGX Spark, the desktop AI supercomputer, uses unified system memory shared between the CPU and GPU rather than discrete VRAM.<\/p>\n

NVIDIA VA-API driver will now check twice during initialization to make sure it’s running on NVIDIA device with discrete VRAM or unified memory.<\/p>\n

When unified memory is detected, it will remember the detection result, add required dependencies from open-gpu-kernel-modules, and use the correct new method to allocate memory. Thus, it will work properly on DGX Spark with Firefox.<\/p>\n

\"\"<\/p>\n

Get NVIDIA VA-API Driver 0.0.17<\/h3>\n

The source tarball as well as the release note is available in Github page via the link below:<\/p>\n

\n
NVIDIA VAAPI Driver<\/a><\/div>\n<\/div>\n

For Ubuntu users who want to try it out without building by yourself, I’ve made the new version into this unofficial PPA<\/a> for Ubuntu 22.04, Ubuntu 24.04, Ubuntu 25.10 and Ubuntu 26.04.<\/p>\n

If you don’t know how to get it work, see either the official README<\/a> or follow this step by step guide<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"

NVIDIA VA-API driver, the VA-API hardware acceleration implemention using NVIDIA GPU, released new 0.0.17 version a few days ago. The new version of this free open-source library fixed only two but important bugs for JPEG decoding and NVIDIA DGX Spark memory systems.<\/p>\n","protected":false},"author":1,"featured_media":38385,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[656],"class_list":["post-51189","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-nvidia"],"_links":{"self":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/posts\/51189","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/comments?post=51189"}],"version-history":[{"count":0,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/posts\/51189\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/media\/38385"}],"wp:attachment":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/media?parent=51189"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/categories?post=51189"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/tags?post=51189"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}