Status
()
People
(Reporter: bwc, Unassigned)
Tracking
(Blocks 1 bug)
Firefox Tracking Flags
(firefox44 affected)
Details
Right now, we only get a single H264 encoder per webrtc.org channel. We either need: 1) The ability to have multiple encoders, each associated with a single simulcast stream in the webrtc.org code. or 2) Support for encoding multiple resolutions/framerates/bitrates/etc in the H264 encoder, along with the plumbing necessary to associate these encodings with the corresponding simulcast streams in the webrtc.org code.
Simulcast is a P1, but h264 in simulcast could follow the initial release if need be.
Rank: 23
Priority: -- → P2
|
||
Comment 2•2 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
FYI Chrome will get this soon: https://bugs.chromium.org/p/webrtc/issues/detail?id=5840
|
||
Comment 4•10 months ago
|
||
Hi guys, Is there any plan to implement h264 simulcast in FF too? seems that chrome is almost ready to ship it: https://webrtc-review.googlesource.com/c/src/+/64100
You need to log in
before you can comment on or make changes to this bug.
Description
•