Closed Bug 1138629 Opened 11 years ago Closed 4 years ago

VP9 support in signaling and conduit/pipeline code (more complete)

Categories

(Core :: WebRTC: Signaling, defect, P4)

Product:
Core
Component:
WebRTC: Signaling
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: jesup, Unassigned)

References

(Blocks 1 open bug)

Details

+++ This bug was initially created as a clone of Bug #1137474 +++ +++ This bug was initially created as a clone of Bug #1090742 +++ This bug covers the upstream (webrtc.org) basic portions of vp9 support; it also doesn't cover things about *when* VP9 should be preferred or switched to/from (which may require allowing accepting multiple codecs, which we don't do yet) Note that webrtc branch 40 has vp9 codec support, but it's incomplete and does not include any packetization, and many codepaths don't account for vp9 as a possibility. This is the followup bug to basic initial support in bug 1137474 (which has no packetization,etc).
backlog: --- → webRTC+
Rank: 35
Priority: -- → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4

FYI, perhaps close

Assignee: rjesup → nobody
Flags: needinfo?(apehrson)

We have basic VP9 support.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(apehrson)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.