Open Bug 1210175 Opened 9 years ago Updated 2 days ago

simulcast support for H264

Categories

(Core :: WebRTC: Audio/Video, enhancement, P3)

Product:
Core
Component:
WebRTC: Audio/Video
Type:
enhancement

Tracking

()

Status:
ASSIGNED
Tracking Flags:
Tracking Status
firefox44 --- affected

People

(Reporter: bwc, Assigned: pehrsons)

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.
Simulcast is a P1, but h264 in simulcast could follow the initial release if need be.
Rank: 23
Priority: -- → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
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?

^

Flags: needinfo?(dminor)

Agreed.

Type: defect → enhancement
Rank: 23
Depends on: 1607238
Flags: needinfo?(dminor)
See Also: → https://github.com/jitsi/jitsi-meet/issues/4758
Whiteboard: [jitsi-meet]

More accurate dependency: Bug 1654112.

Depends on: 1654112
No longer depends on: 1607238
No longer blocks: 1716090
Severity: normal → S3

"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.

Any update on this?
Thank you

Assignee: nobody → apehrson
Status: NEW → ASSIGNED
You need to log in before you can comment on or make changes to this bug.