1766311 - Consider disabling hardware encoding

Status: RESOLVED FIXED

(Core :: WebRTC: Audio/Video, task)

Description

[Jeff Muizelaar [:jrmuizel]]

See for a list of issues with hardware encoders:
https://github.com/W3C/webrtc-extensions/issues/98#issuecomment-1054005251

https://bugs.chromium.org/p/chromium/issues/detail?id=1295815 also has a bunch of current issues.

Hardware encoding is also not currently compatible with win32k sandboxing and disabling it should make bug 1765898 easier to fix

Comment 1

[Jeff Muizelaar [:jrmuizel]]

Attachment: Bug 1766311. Disable hardware encoders on non-Android.

Chrome has had a variety of issues with hardware encoders:
https://github.com/W3C/webrtc-extensions/issues/98#issuecomment-1054005251

We'll disable hardware encoders for now so that we can get consistent
behaviour everywhere. Once we've updated to a modern libwebrtc we
can reenable them.

This also makes it so that we can get resolution scaling on H264 without having
to cherrypick patches from upstream libwebrtc.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/227d19527c9c
Disable hardware encoders on non-Android. r=jolin

Comment 3

[Andreea Pavel [:apavel]]

https://hg.mozilla.org/mozilla-central/rev/227d19527c9c