- From: Cullen Jennings (fluffy) <fluffy@cisco.com>
- Date: Thu, 22 Aug 2013 18:59:57 +0000
- To: Roman Shpount <roman@telurix.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Aug 11, 2013, at 6:57 PM, Roman Shpount <roman@telurix.com> wrote: > An example would be browser which implements both VP8 and H.264 and remote party which implements both codecs, but it is known to have much better quality for one vs another. If the offer lists VP8 first, answering party, if it follows RFC3264, it should pick VP8. If application wants to control, codec order will need to be changed. It seems to me that when their is more than one codec that will work, the browsers will do a fine job of picking the optimal. I'll point at G.711 and Opus as an example of that. So for me this falls into a use case that would only happen with a narrow set of applications and ones with pretty deep understanding of exactly how they want to manipulate the RTP. I feel similarly about changing ptime and I will point out the maxptime might be a limitation of the hardware so it pretty much has to be set by the browser.
Received on Thursday, 22 August 2013 19:00:44 UTC