Re: [rtcweb] Conclusion statement for Recommended Audio Codecs call

["Cullen Jennings (fluffy)" <[e-mail]>]

I've never understood why G.722 was disabled in the builds. Does anyone have any insight into that? 


On Feb 21, 2013, at 10:45 AM, Roman Shpount <[e-mail]> wrote:

> If we follow the logic in this document, I would suggest that G.722 MUST be implemented in all cases. For all practical purposes G.722 is always available. It might not be provided by the platform, but the complexity of implementing it is extremely low, and there is no IPR cost. G.722 is already part of the current WebRTC code base in both Chromium and Firefox, but it is disabled during compilation from being included in the web browser build. Adding support for G.722 in two current major implementations would require one change in defines.
> _____________
> Roman Shpount
> 
> 
> On Thu, Feb 21, 2013 at 12:28 PM, Xavier Marjou <[e-mail]> wrote:
> As suggested by the chairs, here is a draft indicating the motivations, as well as a proposed way-forward, regarding "additional relevant audio codecs" : http://tools.ietf.org/html/draft-marjou-rtcweb-audio-codecs-for-interop-00
> 
> I would like to present it during the IETF-86.
> 
> Cheers,
> Xavier
> 
> 
> On Mon, Jan 28, 2013 at 9:12 AM, Magnus Westerlund <[e-mail]> wrote:
> Hi,
> 
> We chairs was considering inclusion in draft-ietf-webrtc-audio, but we
> didn't have any strong opinions on this. Based on that several WG
> participants thinks this should be an independent document, I thus
> decided that we will start out with an independent document. If the WG
> feels differently later we can always fold the text into the audio codec
> and processing requirements document.
> 
> I would recommend that the individuals interested in contributing a
> codec writes an independent submission with focus on the codec
> considerations around the codec(s) they are interested in. Then we can
> merge this into a common WG document.
> 
> Cheers
> 
> Magnus
> 
> 
> On 2013-01-27 10:14, Romascanu, Dan (Dan) wrote:
> > Hi WG chairs,
> >
> > Clarification question:
> >
> >> In lieu of additional normative text, we believe the WG discussion
> >> supports the inclusion of a new section on "Additional Relevant Codecs".
> >
> > Inclusion where?
> >
> > Thanks and Regards,
> >
> > Dan
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: [e-mail] [mailto:[e-mail]] On Behalf
> >> Of Cullen Jennings (fluffy)
> >> Sent: Thursday, January 24, 2013 6:47 PM
> >> To: [e-mail]
> >> Subject: Re: [rtcweb] Conclusion statement for Recommended Audio Codecs
> >> call
> >>
> >>
> >> We have been running a call for consensus regarding Selecting
> >> Recommended Audio Codecs.
> >>
> >> At this point the chairs are calling this as "no WG consensus".
> >>
> >> We can however note a strong interest in a non-normative listing of
> >> potentially important codecs including a description why they should be
> >> considered to be supported in WebRTC implementations.
> >>
> >> In lieu of additional normative text, we believe the WG discussion
> >> supports the inclusion of a new section on "Additional Relevant Codecs".
> >> That can contain a list of codecs which are relevant in specific
> >> contexts, along with a short description of the context for each.
> >> Specifically there seems to be interest in understanding the advantages
> >> and costs of G.722, AMR, and AMR-WB. We hope that text would broaden
> >> understanding of the WebRTC use case contexts.
> >>
> >> The WG chairs
> >> Magnus, Ted and Cullen
> >>
> >>
> >> _______________________________________________
> >> rtcweb mailing list
> >> [e-mail]
> >> https://www.ietf.org/mailman/listinfo/rtcweb
> > _______________________________________________
> > rtcweb mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/rtcweb
> >
> >
> 
> 
> --
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  [phone]
> Färögatan 6                | Mobile [phone]
> SE-164 80 Stockholm, Sweden| mailto: [e-mail]
> ----------------------------------------------------------------------
> 
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> 
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> 
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb