4 ms·

VLC also has blocklists, e.g. https://code.videolan.org/videolan/vlc/-/blob/master/modules/codec/avcodec/dxva_blocklist.c https://code.videolan.org/videolan/vlc

VLC also has blocklists, e.g. https://code.videolan.org/videolan/vlc/-/blob/master/modules/codec/avcodec/dxva_blocklist.c https://code.videolan.org/videolan/vlc/-/blob/master/modules... https://code.videolan.org/videolan/vlc/-/blob/master/modules/video_output/opengl/interop_vaapi.c#L323 https://code.videolan.org/videolan/vlc/-/blob/master/modules... As does gstreamer (used by Totem): https://blogs.igalia.com/vjaquez/2018/03/28/gstreamer-va-api-troubleshooting/ https://blogs.igalia.com/vjaquez/2018/03/28/gstreamer-va-api...

Delk 6y ago
It still seems, at least based on anecdata and a hunch, that decode acceleration through VA-API works more often in VLC than in Firefox. VLC on Linux systematically hardware decodes H.264 on my aging integrated GPU, but I haven't got it to work on Firefox ever. (Most web video nowadays is probably VP9 or something, which my GPU doesn't decode, unless you coerce YouTube et al. to serve H.264 using a browser extension, but that's another story; even if I do that, it still doesn't get decoded in hardware.) I'm sure the browser developers have reasons for being conservative about enabling VA-API acceleration, ranging from possible issue with their codebase to buggy drivers, but it does seem like there are way more problems than e.g. in VLC.