Open
Bug 1210175
Opened 9 years ago
Updated 1 year ago
simulcast support for H264
Categories
(Core :: WebRTC: Audio/Video, enhancement, P3)
Core
WebRTC: Audio/Video
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox44 | --- | affected |
People
(Reporter: bwc, Unassigned)
References
Details
(Whiteboard: [jitsi-meet])
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.
Comment 1•9 years ago
|
||
Simulcast is a P1, but h264 in simulcast could follow the initial release if need be.
Rank: 23
Priority: -- → P2
Updated•9 years ago
|
Comment 2•7 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•6 years 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
Depends on bug 1607238?
Comment hidden (advocacy) |
Comment 8•5 years ago
|
||
Agreed.
See Also: → https://github.com/jitsi/jitsi-meet/issues/4758
Whiteboard: [jitsi-meet]
Comment 10•4 years ago
|
||
More accurate dependency: Bug 1654112.
Reporter | ||
Updated•3 years ago
|
Updated•2 years ago
|
Severity: normal → S3
Comment 11•1 year ago
|
||
"We have implemented to reject all Firefox from the conference, only Chrome and Safari allowed, and since then we had no problems."
What can I say? Sic transit gloria mundi.
Comment 12•1 year ago
|
||
Any update on this?
Thank you
You need to log in
before you can comment on or make changes to this bug.
Description
•