W3C home > Mailing lists > Public > public-webrtc@w3.org > September 2012

Re: Opus implementation

From: Alexey Aylarov <alexey@zingaya.com>
Date: Mon, 24 Sep 2012 12:33:00 -0700
To: Ralph Giles <giles@thaumas.net>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Message-ID: <CC86034C.1D968%alexey@zingaya.com>
Thanks, Ralph!

Then it's even more impressive! Hopefully all browser vendors will
implement it in a right way

Best Regards,
Alexey

9/24/12 12:29 PM пользователь "Ralph Giles" <giles@thaumas.net> написал:

>On 12-09-24 11:59 AM, Alexey Aylarov wrote:
>
>> As I understand Opus was only discussed as a solution for wideband audio
>> so farЕ
>
>Opus supports narrowband as well as wideband (and several bandwidth
>steps in-between). The sender side can configure the encoder to use this
>mode. The reference encoder will also switch to narrowband automatically
>when a appropriately low bitrate is requested.
>
>The RTP payload draft[*] defines a maxcodedaudiobandwidth SDP parameter
>the receiver can use to indicate a preference for narrowband. However,
>because all of this is dynamically switchable in Opus, it is recommended
>that receivers always implement fullband unless they have a specific
>hardware limitation which prevents supporting that. In that case they
>can take advantage of higher quality audio when appropriate, while still
>scaling down to narrowband when that's what the sender ends up encoding.
>
> -r
>
>[*] http://tools.ietf.org/html/draft-spittka-payload-rtp-opus
>
>
Received on Monday, 24 September 2012 19:33:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 24 September 2012 19:33:30 GMT