- From: Robin Raymond via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Mar 2016 23:59:33 +0000
- To: public-ortc@w3.org
robin-raymond has just created a new issue for https://github.com/openpeer/ortc: == RTX APT capability? == Since we don't have a capability for RTX APT, a single RTX codec gets listed allocating a single preferredPayloadType. The trouble is that payload type is not relevant because an RTX codec is needed per media codec that supports RTX. Likewise, there's no guarantee the engine supports RTX for each media codec. Currently a developer would need to disregard the RTX codec, and allocate their own payload per RTX codec per media codec they wish to use with RTX. This is certainly doable but problematic. There is currently no way for the developer to know which media codecs support RTX or not. I suspect this issue may exist for RED + ULPFEC, FlexFec too possibly. Although there's an advantage that each of those only need to allocate a single codec per clock rate (as the payload contains the original media codec) whereas that's not true of RTX payloads. Please view or discuss this issue at https://github.com/openpeer/ortc/issues/444 using your GitHub account
Received on Tuesday, 29 March 2016 23:59:34 UTC