Hm, nice, now just a matter of time to be available in arch repos
https://www.mozilla.org/en-US/firefox/android/98.0/releasenotes/
AV1 (HW) decode
https://bugzilla.mozilla.org/show_bug.cgi?id=1652958
Hm, nice, now just a matter of time to be available in arch repos
https://www.mozilla.org/en-US/firefox/android/98.0/releasenotes/
AV1 (HW) decode
https://bugzilla.mozilla.org/show_bug.cgi?id=1652958
Android?
hmm, how I didn’t see that
But, either way, its a good sign that 98 is coming
I think you missed the link:
Why are the release notes always so bad for Firefox? Always feels like they leave out a lot of interesting stuff.
Who say’s they’re bad?
For example, where is the AV1 stuff mentioned?
Indeed, that is missing in the release notes…
Milestone: 98 Branch
Arch wiki:
Why does it need to be mentioned? There was bug report and it said it was fixed in version 97
AFAIK Firefox was never able to decode AV1 before. This therefore is a new feature just working with this version and beyond. Also this is not the first time they didn’t mention big improvements for Linux based Firefox.
I have no idea if it works or it doesn’t. I just read it. As far as i can see they have reported it as a bug fix. Because it was an enhancement in version 97.
First you need AV1 working in the system, you can test in MPV…
As soon as Firefox 98 hits the repo, I’ll test if its working
Edit: You can download some samples at https://tools.woolyss.com/html5-audio-video-tester/
Well, overall it’s just weird you have to rely on third party sources and bug reports for stuff like this. I find Firefox changelogs to be lacking a lot of detailed informations. Just look at the past 10+ changelogs and see if you can gather anything that leads you to what is documented in the arch wiki about hardware acceleration.
It’s not really that bad in practice, because you have the arch wiki to rely on, but I personally find their changelog to be mostly useless.
Bring it up with them then! I don’t understand what your issue is?
I thought that this was handled by ffmpeg?
My issue is clear. Just making conversation in a thread that starts with the mention of AV1 being available, while not being documented in the changelog.
Like i said i don’t think it’s a change. It was a bug fix.
The sample page works for me. But i’m on amdgpu and not using Gnome Wayland.
I had to do these changes to get VP9 working in Firefox: (AMD RX 6600 XT GPU):
# pacman -S libva-utils
# pacman -S libva-mesa-driver
# pacman -S lib32-libva-mesa-driver (not required as firefox is 64bit)
# pacman -S libvdpau-va-gl (translation layer) - VDPAU driver with OpenGL/VAAPI backend. H.264 only.
# pacman -S libva-vdpau-driver (translation layer) - A VDPAU-based backend for VA-API
# sudo pacman -S mesa-vdpau
# sudo pacman -S lib32-mesa-vdpau
# sudo pacman -S vdpauinfo
add to /etc/environment
VDPAU_DRIVER=radeonsi
set this in firefox: media.ffmpeg.vaapi.enabled to true
Also, if you are running in Wayland, run Firefox with the following environment variable enabled:
MOZ_ENABLE_WAYLAND=1
I didn't test in X11 to see if it works.
Optional:
- Install Vulkan
# sudo pacman -S vulkan-icd-loader
# sudo pacman -S lib32-vulkan-icd-loader
- AMD RADV
# sudo pacman -S vulkan-radeon
# sudo pacman -S lib32-vulkan-radeon
# sudo pacman -S vulkan-tools
Nope. Firefox on Linux couldn’t do it. Title of the entry was “Provide AV1 VA-API playback”, therefore it was not present before. The milestone was set for 98. It’s not mentioned in the changelog (and the bugfix section in the changelog).
And as mentioned, this is not the first time they didn’t mention Linux bugfixes or new features in the changelog.
Well, whatever. I just think they are lacking with their documentation, which makes it hard to follow new Linux specific changes and bugfixes.