- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Jan 2017 22:26:17 +0000
- To: public-webrtc-logs@w3.org
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 https://github.com/w3c/webrtc-pc/issues/763#issuecomment-275533671 using your GitHub account
Received on Thursday, 26 January 2017 22:26:23 UTC