- From: Sherwin Sim <sherwin.sim@temasys.com.sg>
- Date: Sat, 16 Apr 2016 09:43:38 -0400
- To: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Cc: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, "public-ortc@w3.org" <public-ortc@w3.org>
+1 on clarifying this in the specification And I assume the clarification should be independent of media type (audio/video) ~Sherwin > On Apr 16, 2016, at 9:32 AM, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote: > > There are several potential scenarios: > > 1. Switching between Opus and PCMA. This is accomplished by including both Opus and PCMA in the codecs[] sequence, and changing the order to switch between one and the other. > This is supported in both WebRTC 1.0 and ORTC, and has been implemented in Edge and ORTC Lib. > > 2. Utilizing RED to encapsulate both Opus and PCMA. This is also possible in both WebRTC 1.0 and ORTC. Currently I believe this is accomplished by including RED, Opus and PCMA in the codecs[] sequence (in that order?), then setting parameters.encodings[].fec.method to "red". This is supported in Edge (and ORTC lib?) > > 3. Attempting to send both Opus and PCMA simultaneously. In theory, this should be supportable in WebRTC 1.0 (and ORTC) using simulcast and RIDs. In practice, we do not support this in Edge (only the first codec in the codecs[] sequence will be sent). > ________________________________________ > From: Sergio Garcia Murillo [sergio.garcia.murillo@gmail.com] > Sent: Friday, April 15, 2016 12:49 PM > To: public-ortc@w3.org > Subject: Is sending multiple audio codecs on same RTCRtpSender supported? > > Hi all, > > Imagine the following (crazy) scenario, where you want to send OPUS and PCMA on the same RTCRtpSender (obviously on different ssrcs as they have different clock rates). > > Is it assumed that this SHALL be supported by all browsers implementing ORTC? > > I think we should explicitly set it in the spec if this shall be supported or it is forbidden. If I have this kind of doubt in the SDP O/A world I have tons of RFCs I can search for the answer, but with the ortc params there is no other source of information I can look for. > > Best regards > Sergio > -- ------------------------------ This email and any files transmitted with it are for the sole use of the intended recipient and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply email and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this email is strictly prohibited and may be unlawful. Thank you for your cooperation. ------------------------------ 2016, Temasys Communications Pte Ltd, 80 Amoy Street 02-02, Singapore 069899 (www.temasys.com.sg)
Received on Saturday, 16 April 2016 13:44:09 UTC