Re: [rtcweb] Query Regarding Mandatory audio codecs draft

No.  G.711 uses more network bandwidth than OPUS, but OPUS is more complex.

The main benefit of using G.711 is that it can avoid the use of transcoding
in some scenarios.

My view is that the approach in the current text is correct - there is no
need to specify a SHOULD on which codec is offered first.

Stephen

On Mon, Apr 28, 2014 at 5:25 AM, Steev James <steev.a.james@gmail.com>wrote:

> Means you say that G.711 uses less bandwidth than Opus at the expense of
> complexity.
>
> Am I right ?
>
>
> On Mon, Apr 28, 2014 at 11:23 AM, Jean-Marc Valin <jmvalin@mozilla.com>wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> So, if the other endpoint only supports G.711 (legacy), then it
>> doesn't matter which codec you offer first. The the other endpoint
>> supports both Opus and G.711, but only at 8 kHz, then it comes down to
>> which of complexity or bandwidth is more important. On a corporate LAN
>> you'd likely want to use G.711 while for chatting from your home,
>> you'd usually want Opus. This is why the draft makes has no SHOULD
>> when it comes to narrowband.
>>
>>         Jean-Marc
>>
>> On 28/04/14 12:40 AM, Steev James wrote:
>> > Paul, What do you say, if another end point is using both G.711 and
>> > Opus at 8kHz and why ?
>> >
>> > Steev.
>>
>> >
>> >
>> >
>> >>> Is that means spec is recommending G.711 (PCMA/PCMU) for
>> >>> sampling
>> > rate
>> >>> less than or equal to 8 kHz?
>> >>
>> >> No. Opus is still a good idea for 8 kHz, but it's not 2119
>> >> RECOMMENDED since there are valid (mostly complexity-related)
>> >> reasons to use G.711 despite the higher bit-rate.
>> >>
>> >> Jean-Marc
>> >
>> > Opus isn't a good idea for 8 KHz if you are trying to inter-operate
>> > with another end-point using G.711.
>> >
>> > ...Paul
>> >
>> >
>> >
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>
>> iQEcBAEBAgAGBQJTXezkAAoJEJ6/8sItn9q9DfEIAKy6ZPCE7o/dyBFhpt5tGpds
>> XRDUiR++S89H4blgJOsR5nzzmkGwN+onN4cwBfz4Tbvi0Q7Q/UyzdlBePekC4gwL
>> wrQL2/fwxfTnB0T6yfn2rrCd+i7jVWf2xJz0xJIY2qYAxYVg469PzeGMHTJK1+1x
>> S1BDRZHZp4X/nSShthdthHvkfHrVPq5pDzexCfBc2h56+9Z3K1COdQlVZD/UJwQy
>> twp8p6755LzucV4KdvN5NM5w9rjySBTAaUElU0WkyMPfRppowAkFhJunoJCTeIW9
>> 8Stsm5yrAeasQhe9mlubceIYsTyjGfKkoO1RVkQUB2YwzctqyMnK14ZYJQbg8Us=
>> =Ys9g
>> -----END PGP SIGNATURE-----
>>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>