So, before trying to tweak Firefox, it is my understanding that first I should be able to see AV1 on the above list. Can anyone share any tips on how to get this fixed?
Yes, that seems to be the most likely. If vainfodoesn’t report it, then the vaapi driver wasn’t built with support for it (not possible in this case, since @ocosta is using the rpmfusion version), or the hardware simply doesn’t have that functionality.
Thanks guys, I guess you nailed it. It sounds stupid, but that hadn’t even crossed my mind. It makes total sense. My processor is a Ryzen 7 4800H, I couldn’t find detailed specs on AMD’s official product page, but I did find one for the Ryzen 7 Pro 6850U, which doesn’t support AV1, so I can’t see why an older and inferior (non-Pro) processor would do.
Just for the record: Firefox allows you to completely disable AV1 via the media.av1.enable flag. Chrome doesn’t have a similar configuration AFAICS Only some extensions for Youtube.
I will probably install windows just to see what can be HW accelerated on current R7 8840HS vs. what I have on linux now (same as Renoir on Win minus VP8 HW)
Indeed… @samik4184 could you please compare some data from the about:support output so that we can compare yours with mine? If you click on the “Copy raw data to the clipboard” button on the top of the page you can paste the original JSON data.
Mine puts only “SW” next to AV1 on the codecSupportInfo field, while H264 and VP9 both have “SW HW”. And the features field has