- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Mar 2017 02:08:53 +0000
- To: public-webrtc@w3.org
aboba has just created a new issue for https://github.com/w3c/webrtc-pc: == setCodecPreferences() can't handle codecs supporting multiple clock rates/packetization-mode == void setCodecPreferences(sequence<RTCRtpCodecCapability> codecs); dictionary RTCRtpCodecCapability { DOMString mimeType; }; What happens if a codec supports multiple clock rates or encoding types? Examples: - CN or SILK with clock rates of 8000 and 16000 - H.264/AVC implementation supporting packetization-mode of 0 or 1 Questions: 1. Are there multiple entries in the codecs[] sequence? 2. If so, how are they differentiated? (since mimeType is the only attribute) Do we need to add attributes? If so, which can setCodecPreferences() set? Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1040 using your GitHub account
Received on Wednesday, 1 March 2017 02:09:01 UTC