Closed Bug 1766311 Opened 3 years ago Closed 3 years ago

Consider disabling hardware encoding

Categories

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

task

Tracking

()

RESOLVED FIXED
101 Branch
Tracking Status
firefox101 --- fixed

People

(Reporter: jrmuizel, Assigned: jrmuizel)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

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

Blocks: teams
Blocks: 1765898

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.

Assignee: nobody → jmuizelaar
Status: NEW → ASSIGNED
Pushed by jmuizelaar@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/227d19527c9c Disable hardware encoders on non-Android. r=jolin
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
Regressions: 1773207
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: