3 ms·
And meanwhile Chrome outright refuses to support vaapi outside of intel (and thats only because of chromebooks).
by aaomidi 3y ago
And meanwhile Chrome outright refuses to support vaapi outside of intel (and thats only because of chromebooks).
- Vogtinator 3y agoWith the right Mesa patch (https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26165 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26...) and chromium flags to force enable vaapi, I've got working HW decode with amdgpu here.
- jauntywundrkind 3y agoSeems like with av1, Google had to stop self-sabotaging (turning on va-api has worked for most users for more than half a decade) & kind of had to move (because av1 is too beastly to do on cpu). Sounds like va-api has been turned on for almost a month now, but I haven't confirmed. https://www.phoronix.com/news/Google-Chrome-Wayland-VA-API https://www.phoronix.com/news/Google-Chrome-Wayland-VA-API Maybe I'm missing something, but from what I could dig up it sounds like Firefox only enables va-api on Intel. https://www.phoronix.com/news/Mozilla-Firefox-115 https://www.phoronix.com/news/Mozilla-Firefox-115