Firefox 153 available with support for Vulkan video decoding, JPEG-XL
11–20 of 80 posts
Re: Firefox 153 available with support for Vulkan video decoding, JPEG-XL
#12Related:
Firefox 153.0 Beta
Re: Firefox 153 available with support for Vulkan video decoding, JPEG-XL
#13Interesting - will see if I can toy with it. Word of caution though. I’ve found that on my machine (Linux/nvidia) unaccelerated video is way more power efficient. The second video is playing it kept the GPU in a high power state and that uses incrementally more power than the cpu doing software decoding I had always assumed gpu would obviously be more efficient until I measured it
I haven't been able to get Firefox GPU acceleration to work on Linux in forever.
Re: Firefox 153 available with support for Vulkan video decoding, JPEG-XL
#14Cool, have been using vulkan video decoding via mpv for a while now and it seems fine with little or no performance hits. Glad it's made its way here as getting hardware decoding to actually work in ff has felt like a house of cards (more options are welcome). Does something need to be done to enable/switch to it?
Re: Firefox 153 available with support for Vulkan video decoding, JPEG-XL
#15Earlier quoted context omitted.
All modern CPUs come with an iGPU, so it's unlikely to be software decoding. Just iGPU driver's decoder being more efficient than dGPU one.
The iGPU's video decoder could even be drastically less efficient than the dGPU's decoder, and it would still be better to use the iGPU, because just powering up the PCIe link and VRAM for the dGPU costs far more power than the video decoding itself.
Exactly, mpv logic causes it to pick up Nvidia for HW video even if renderer is on iGPU. There is special flag to choose device which solves the problem and Nvidia is kept down
Re: Firefox 153 available with support for Vulkan video decoding, JPEG-XL
#16Interesting - will see if I can toy with it. Word of caution though. I’ve found that on my machine (Linux/nvidia) unaccelerated video is way more power efficient. The second video is playing it kept the GPU in a high power state and that uses incrementally more power than the cpu doing software decoding I had always assumed gpu would obviously be more efficient until I measured it
All modern CPUs come with an iGPU, so it's unlikely to be software decoding. Just iGPU driver's decoder being more efficient than dGPU one.
What makes you think the unaccelerated path would use the accelerated iGPU path? Typically hardware decoding is disabled because of driver/reliability issues and thus would switch to software decoding to sidestep these concerns.
Re: Firefox 153 available with support for Vulkan video decoding, JPEG-XL
#17Interesting - will see if I can toy with it. Word of caution though. I’ve found that on my machine (Linux/nvidia) unaccelerated video is way more power efficient. The second video is playing it kept the GPU in a high power state and that uses incrementally more power than the cpu doing software decoding I had always assumed gpu would obviously be more efficient until I measured it
Are you using nvidia-vaapi-driver? If so, you'll need to set `CUDA_DISABLE_PERF_BOOST` in your environment.
Oh that’s interesting. I shall investigate thanks.
edit: very quick test with MPV seems to confirm this works - eliminates the gnarly additional GPU draw. Measuring draw at wall now puts CPU and GPU route on equal footing...both basically the machines idle draw. Tested both 264 and 265...same outcome. 3090.
Thanks!
Re: Firefox 153 available with support for Vulkan video decoding, JPEG-XL
#18Interesting - will see if I can toy with it. Word of caution though. I’ve found that on my machine (Linux/nvidia) unaccelerated video is way more power efficient. The second video is playing it kept the GPU in a high power state and that uses incrementally more power than the cpu doing software decoding I had always assumed gpu would obviously be more efficient until I measured it
the story is kind of complicated, it's impossible to guess the culprit, you must profile. HDR content for example can sometimes incorrectly request a bespoke tonemapping instead of a video engine silicon one, like it does in libavcodec, or you have a privacy setting in your browser that breaks GPU compositing. so many little things can go wrong unfortunately.
Re: Firefox 153 available with support for Vulkan video decoding, JPEG-XL
#19Cool, have been using vulkan video decoding via mpv for a while now and it seems fine with little or no performance hits. Glad it's made its way here as getting hardware decoding to actually work in ff has felt like a house of cards (more options are welcome). Does something need to be done to enable/switch to it?
Yes, while the Chrome/Chromium hardware decoding, or any other uses of the GPU, like WebGL, was always impeccable on Linux, with Firefox that was always an adventure, much more often not working than working (at least with an NVIDIA GPU).
So I also hope that Vulkan decoding might solve this behavior of Firefox on Linux.
Re: Firefox 153 available with support for Vulkan video decoding, JPEG-XL
#20Cool, have been using vulkan video decoding via mpv for a while now and it seems fine with little or no performance hits. Glad it's made its way here as getting hardware decoding to actually work in ff has felt like a house of cards (more options are welcome). Does something need to be done to enable/switch to it?
Yes, while the Chrome/Chromium hardware decoding, or any other uses of the GPU, like WebGL, was always impeccable on Linux, with Firefox that was always an adventure, much more often not working than working (at least with an NVIDIA GPU). So I also hope that Vulkan decoding might solve this behavior of Firefox on Linux.
> Yes, while the Chrome/Chromium hardware decoding, or any other uses of the GPU, like WebGL, was always impeccable on Linux
Have you seen the massive blacklist Chromium maintains?