The primary advantage of dedicated hardware accelerators for the past ~15 years been power efficiency, rather than performance. Not much of a problem on a desktop, but very noticeable on mobile devices.

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.

Considering Intel has vulkan video disabled in Mesa for recent chips, I’m guessing very little.

https://www.phoronix.com/news/Intel-Vulkan-Video-Disable-New

Yup, it's pointing to https://github.com/search

Here's the Bugzilla link which was closed last month: https://bugzilla.mozilla.org/show_bug.cgi?id=2021722

VA API has some caveats and also requires one to disable sandboxing of the media process.

Sorry my comment was related to the nvidia vaapi driver

> 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?

8K decoding needs HW acceleration, unless having 8-16 cores with AVX-512.

I expect it's the https://github.com/search?q=repo%3Amozilla-firefox%2Ffirefox... link that phoronix used in lieu of linking to an actual github issue.

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.

Yeah, Chromium even blacklists perfectly ordinary 2020s "choose this for a quiet life" Intel igpus that work fine in Firefox (and, weirdly, Chrome itself).

First thing to do with Chromium has always been adding various flags to force-enable things, followed by changing a bunch of chrome://gpu settings. Not sure why Chrome does better, but it's closed source so no reasonable way of knowing what it was up to.

Firefox did go through a rough patch 4-5 years ago where it needed various things in about:config to get hw decode when running under Wayland, but it's gone back to working out of the box for me in whatever ESR version has come with the last couple of Debian releases.

I could also imagine the decoded output being pluggable into Vulkan-based filters (mpv uses https://code.videolan.org/videolan/libplacebo) without slow device->host copying.

Interesting.

through, from a pure power POV you probably would want to exclusively use the integrated graphics most CPUs have (1) with the external GPU powered down for most "daily/office-style" usage (browser, news, email, coding (not gamedev,etc.)) and only switch to external GPUs for Gaming, GPGPU, and I guess some edge cases like too many monitors or insisting on running a coding IDE at >240Hz ;)

EDIT, forgot the food note (1): Even the very very minimal GPU recent (non APU) AMD processors have are good enough for many peoples daily "office" needs.

i am bit confused, what does it mean by vulkan video decoding? does it mean that it will be done via gpu or via hardware accelerator sepcific to decoder via some vulkan extension? if it is via extension gpu would be free to do gpu specific things?

Are you using nvidia-vaapi-driver? If so, you'll need to set `CUDA_DISABLE_PERF_BOOST` in your environment.

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.

Nvidia drivers on Linux are not really display quality. The effort goes towards CUDA for headless rigs. They work great for AI and that's it. Pair them with an AMD and Intel card for display, graphics and video acceleration. Otherwise you end up with too many cases of booting into a black screen, random software breaking, games not working, bad performance and just jank in general.

Yes, but that's way out of budget for most consumers.

Blacklist of what? I don't understand what a blacklist would be used for in this context. Specific unsupported hardware?

Interesting, I've personally had the exact opposite experience: Chromium hardware decoding was always half-broken for me and nearly impossible to get working, whereas in Firefox, I had to modify a single setting in "about:config" 5 years ago and it's worked perfectly ever since.

I haven't been able to get Firefox GPU acceleration to work on Linux in forever.

It's a Vulkan extension to use dedicated video decoders like QuickSync, NVDEC and VCN. It's not using shaders.

No iGPU on my CPU (5800x3d). So was straight software decode (well maybe AVX2?) against GPU decode. GPU route was 80W more.

joebonrichie's comment was excellent though - there is a new nvidia tweak that eliminates the GPU going to a high power state the second it sniffs video. So now GPU & CPU get me the same draw.

>enough for many peoples daily "office" needs

Yeah been considering using my mac air for when not gaming / messing with LLMs, but frankly struggling with it on UX.

"All" really isn't true, most AM4 Ryzen chips don't have iGPU (unless they are specificly APUs), and a lot of Intel chips have popular 'F' SKUs without an iGPU.

That's not the final release, that's an RC and tech blogs should stop reporting this as final. There were instances in the past where the RC had critical bugs.

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!

> booting into a black screen, random software breaking, games not working, bad performance and just jank in general.

That has not been my experience at all, using either the old closed source drivers or the newer "open" drivers. (Note: I am referring to the open source Nvidia kernel drivers, not Nouveau.)

Neither of the last two processors I've purchased in the last few years had any iGPU.

I assumed the OP/comment means "software vs. hardware accelerated rendering" when they say "it uses the CPU. And iGPU is still hardware accelerated rendering.

But some modern video codecs are designed to work quite okay with software rendering, especially if it's lower resolutions, and modern higher end dGPUs often have a pretty high "power overhead" on low utilization. To add to it the driver might keep it in a more high power state then strictly needed due to "expecting" more utilization, or similar.

Not all, most desktop have two options with or without igpu.

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.

I guess my caveat always is that I use Fedora (which does not include hw codecs by default due to licensing) and have to manage mesa/ffmpeg stuff myself. Adds a bit to the frustration (though it's self-inflicted so I don't usually complain :)

Actually not really, Lunar Lake chips with Xe2 graphics have VVC decoding in hardware which can do 8K.

https://en.wikipedia.org/wiki/Versatile_Video_Coding

Yes.

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.

Works out of the box for me on CachyOS, both amd and nvidia

Bonus discovery I just learned. Under nvtop -> F2 -> Processes -> Fields -> there you can make it show encode/decode. It's disabled by default

An RC justifies the "merges" title (compare "releases")

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

I'm on Fedora too, so I probably should have said "getting hardware decoding to work in Firefox is no harder than getting it to work with any other Fedora program" rather than claiming that it's actually easy :)

They were likely saying that 8K displays are way out of budget for most consumers.

Well, supposedly. But in my experience, there was no consequence disabling the blacklist in order to enable hardware video encoding and decoding.

Yeah but not the Phoronix one ("Firefox 153 Available", "Mozilla has uploaded the Firefox 153.0 release binaries today"). Shame because Phoronix was kinda good in the past.

And in my experience, there was.

One person's lived experience is another person's “supposedly”.

My assumption would be, when there is a large corpus of crash reports for a certain configuration of hardware, knowing if it's a hardware failure, driver bug, or software incompatibly, is pretty hard. So it's probably easier to catch false positives and not get blamed for a faulty product, even if you aren't the cause. Drivers crash under the hood in windows all the time, even today, but once MS did a better job of just restarting the offending drivers where possible instead of BSODing, people thought windows was an unstable product. Which is technically true from the users perspective, even though it wasn't Microsoft's fault directly. You may have had a good combo that simply shouldn't have been on the list/was later patched/or your system is more stable that the average persons.

There was nothing special about my setup. Standard intel processor with i915 driver which I would imagine covers a fairly large chunk of installs out there.