El mié, 24 jul 2024 a la(s) 11:17 a.m., Lucas Gabriel Vuotto
(lucas@sexy.is) escribió:
>
> > > - Some meme pages show webms just fine
> >
> > I don't see it, I'll test it with a new profile. Can you give me a test
> > example?
>
> https://9gag.com/gag/avynegn
> https://9gag.com/gag/amoz10j
>
> Raw media links:
>
> https://img-9gag-fun.9cache.com/photo/amoz10j_460svvp9.webm (VP9)
> https://img-9gag-fun.9cache.com/photo/avynegn_460svav1.mp4 (AV1)
>
> According to about:support, both VP9 and AV1 decoding are supported
> (tried with the Tiger Lake, i7-1165G7, Intel iRIS Xe-LP).
>
> Downloading the video and playing it with MPV works wonders. Playing it
> in Firefox makes the CPU usage raise. Enabling
> media.ffmpeg.vaapi.enabled made no difference, even after a restart.
>

In your case, what tell you Firefox about:support page over HW Decode?

In my case: https://imgur.com/a/RUFD7N7

> Basically, it seems that having an VA-API enabled ffmpeg doesn't make
> a difference in Firefox right now.
>

The other thing to check is the VAAPI support within Firefox itself.

For example: is ffvpx (Firefox's internal copy of ffmpeg) being built
with VAAPI support?

Why ffvpx is the preferred tool to use for playback within Firefox.
Maybe trying the options:

media.ffmpeg.vaapi.enabled = true
media.ffvpx.enabled = false

Try these options and using MOZ_LOG=PlatformDecoderModule:5 to see the
log of the decoding tasks within Firefox.

**Info ffvpx and VAAPI in-tree:**

https://github.com/mozilla/gecko-dev/tree/master/media/mozva/va

-- 
"Dios en su Cielo, todo bien en la Tierra"
***********************************************