HTML5test VS nvidia-vaapi-driver

I just don't know what else I can do. I compared Chromium and Firefox in html5test.com, got same result. All browsers says they doesn't support H.265. I turned off HW acceleration, nothing changes. I installed ffmpeg-libs and other codecs from Fedora wiki. Nothing changes. Videos are same vp9 in browsers. I spent all day googling but nothing helpful.

What does https://html5test.com/ say for h.264, VP8, VP9 and Theora support? What does it say for aac, Opus, Vorbis and mp3 support?

You can use this website also https://html5test.com is really helpful with more datails

If I go on html5test.com, no matter which browser I use, H265 support is not enabled and I couldn't find any article online that explains why -- what am I missing here?

When I install Opera via flatpak and do html 5 test it says h264 is not supported, what can I do?

What does https://html5test.com/ say for h.264 and aac support?

The h264 test page shows the same output in both chromium and chrome, and i can play the same formats from this page

For anyone wondering, I got hardware acceleration working (NVIDIA 1660 Super: h264, vp8, vp9, don't know why I can't get HEVC support currently) using the nvidia-driver-545 using the steps from nvidia-vaapi-driver to build from source (version: 0.0.11)

I don't think it's your fault and I don't think you're using the wrong browser.

> I should be working out the dependency story and compiling some driver from Github myself.

no, nvidia _should_ make it easier for people using the 3rd most popular desktop OS to use their hardware. It would make them more competitive against AMD and Intel, which both support hardware video decoding.

That's probably not going to happen, so the next best option is to install a package from the package manager [0]. There might be some kind of compilation needed, but in my experience that's rarely an issue (aside from time), especially if it's coming out of the package manager for a popular distribution.

> It's just not a real option for maybe 99% of PC users.

well, 99% of PC users with Nvidia hardware. It's an important distinction since this problem is specific to Nvidia. If the solution is to installing a package from the package manager, it's only as difficult as installing the browser in the first place.

I do agree there's some extra questions that may make things difficult, or unfamiliar for the vast majority of people, though. Like how is someone supposed to know they need the nvidia-vaapi-driver package anyway?

[0] - https://github.com/elFarto/nvidia-vaapi-driver#package-manag...

to be honest, pop os solved most of my problems except the hardware acceleration problem which seems like an issue with Nvidia. I am planning to try this soon. https://github.com/elFarto/nvidia-vaapi-driver/ as mentioned in the comments

RpmFusion only has v0.0.9 of nvidia-vaapi-driver although release v0.0.10 adds support for Nvidia drivers v535. https://github.com/elFarto/nvidia-vaapi-driver/releases/tag/v0.0.10

I do have one machine with the Firefox PPA rather than the snap, and that's because I've got an NVIDIA card in it and want to use an experimental library.

Note that as an nvidia gpu owner you need to do some extra backflips to make firefox use hardware decoding such as installing a custom vaapi-to-nvdec translation driver: https://github.com/elFarto/nvidia-vaapi-driver

General VDPAU vs VA-API video acceleration pains. Needing a community driver for imperfect VA-API support, that nvidia updates have broken multiple times.

Don't use VDPAU, this driver is much better: https://github.com/elFarto/nvidia-vaapi-driver