Re: [webrtc-pc] Handling of simulcast errors

Right, so it's a slightly different meaning. But it would go in the 
same place (`RTCRtpCodecCapability`).

Does this need to be a per-codec property though? Is there a practical
 example where a browser would support X encodings for codec A and Y 
encodings for codec B?

GitHub Notification of comment by taylor-b
Please view or discuss this issue at 
using your GitHub account

Received on Thursday, 26 January 2017 22:26:23 UTC