There's a $380 bounty for this [1]. If you fixed this, please collect this. You deserve it. I hope this doesn't get lost just because it got fixed in a different ticket number.<p>[1] <a href="https://www.bountysource.com/issues/55506502-add-va-api-hardware-decoding-support-on-linux" rel="nofollow">https://www.bountysource.com/issues/55506502-add-va-api-hard...</a>
for linux users, this is the best Firefox news in a loooong long time. having to copy paste links from youtube to smplayer for mpv hardware accelerated video can be a PITA.
Relevant comment for X11:<p>> (In reply to lilydjwg from comment #30)<p>>> I'm glad to here that, but what about support for Firefox on X11? Is it given up?<p>> Hardware decoding is platform independent so it generally works under X11 as it's implemented as Bug 1616185.<p>> For whole playback chain see Bug 1610199 what's needed to be done fox X11.<p>> I was closing this one as it refers to HW decode only, not the playback.<p>> The overall video playback is tracked at Bug 1210726.<p><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1210727#c31" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=1210727#c31</a>
What's missing so far is VAAPI support for WebRTC. Apparently, Firefox is using same libwebrtc as Chrome does, and it still doesn't support hardware acceleration.<p>This results in some ugly behavior of WebEx for instance, which blocks video in its WebRTC calls, since it assumes that "CPU is too weak" to handle it. Cisco never fixed this issue.
The mention of DMA-BUF makes me suspect that it involves rendered video being copied from the GPU to the main RAM and back to the GPU, which wastes energy. Does someone have details about how the integration works?