WebrtcVideoConduit cannot cope with having more than one H264 recv codec

Assigned to



WebRTC: Audio/Video
3 years ago
6 months ago


(Reporter: bwc, Assigned: bwc)


(Blocks: 1 bug)


Firefox Tracking Flags

(firefox43 affected)




3 years ago
Currently, we can only have one H264 recv codec on a given WebrtcVideoConduit. If there are multiple H264 codecs in an answer, the last one will be what is configured, which is of course not likely to be what is sent. This will need to be fixed before we are able to accept multiple codecs in an answer.

There are a handful of possible fixes, including:

1. Only use the first H264 recv codec (will probably squeak by in most cases, since the other end will probably not actually switch on us).
2. Fix this limitation by having multiple H264 decoders.
3. Only offer one H264 codec in the first place.

Comment 1

3 years ago
What do you think about these options? I have option 1 implemented in my simulcast negotiation work, and it works ok. If this is not enough in the short-term, I'll need to modify the simulcast patch to not put multiple different codecs (per simulcast version) in answers, and only use one recv codec like before.
Flags: needinfo?(rjesup)
backlog: --- → webrtc/webaudio+
Rank: 17
Priority: -- → P1
Let's land option 1, and file a followup for option 2 at a lower priority.  

Byron - are you good with this?  Thanks.
Flags: needinfo?(rjesup) → needinfo?(docfaraday)
Assignee: nobody → docfaraday

Comment 3

2 years ago
We've already landed option 1 in bug 1203246. We can leave this bug for option 2.
Flags: needinfo?(docfaraday)


2 years ago
Rank: 17 → 22
Priority: P1 → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.