• Flatfire@lemmy.ca
      link
      fedilink
      arrow-up
      25
      ·
      11 hours ago

      Nvidia and AMD both have differing APIs for video decoding. The idea in using Vulkan is that not every GPU supports the vendor specific decoding method, but they do all support Vulkan (modern GPUs, anyways). So this way you still get hardware accelerated decoding through a more widely supported means.

    • blobjim [he/him]@hexbear.net
      link
      fedilink
      English
      arrow-up
      5
      ·
      10 hours ago

      The article says

      Firefox on Linux to date has focused on the Video Acceleration API (VA-API) that works well for some vendors but lacks official support from NVIDIA unless using the independent NVIDIA-VAAPI driver project that layers VA-API on NVDEC. There are also various embedded drivers and more not supporting VA-API

      So it’s basically just because the existing video decoder API in Linux doesn’t have support for various hardware devices for various reasons. But those devices still have Vulkan support. Not sure why Vulkan support for those devices wasn’t just added to VA-API, who knows.

    • Snot Flickerman@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      6
      ·
      15 hours ago

      I used one just yesterday when my skybox file was too large and was taking a couple moments to load, and I compressed it a bit with JXL and presto chango goes more quickly now. Although still imperfect because a slightly larger size PNG loads faster. (Kubuntu in respect to the virtual desktop “cube” interface, 32gb of RAM, 8gb video RAM, neither even halfway filled, source files on NVMes)

  • thingsiplay@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    7 hours ago

    As an AMD user, is it expected to work and behave exactly as it did before or are any differences expected to be noticeable in the end user front?