On Sun Jul 21, 2024 at 04:58:15PM GMT, Lucas Gabriel Vuotto wrote:
> On Sat, Jul 20, 2024 at 11:32:29AM GMT, Rafael Sadowski wrote:
> > OK to enable VA-API? It only depends on xenocara libva. Since libva
> > builds on almost all arches, I see no reason to restrict it by CPU
> > architectures any further.
> 
> This worked well with mpv but is giving me issues in Firefox:

I can confirm that it works well with mpv(1) but not in ff. In my last
test I only tested WebGL and simple youtube stuff.

I have not noticed taht playing youtube run on my CPU. That's because up
to 1080p60 always runs smoothly. But 2160p60 is the end of the line
here.

What I cannot confirm, any disadvantages with enabling or disabling
VAAPI.

> 
> - Invidious instances (YouTube alternative frontend) give me "No
>   compatible source was found for this media"
> - Twitch gives a similar message
> - Couldn't test in YouTube because it thinks I'm a bot

WTF!

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

> 
> In any case, disabling hardware media decoding didn't help. Rolling back
> to 4.4.4p3 (that's what's in cdn.openbsd.org) makes the issues go away.
> I can try with 4.4.4p4 too (adds --disable-vaapi), if it's needed.
> 
> 	Lucas
> 

Can AMD users play https://www.youtube.com/watch?v=LXb3EKWsInQ in
2160p60 on FF without blowing the CPU?

If so, it is only an Intel problem