Re: [rtcweb] Query Regarding Mandatory audio codecs draft

Stephen Botzko <stephen.botzko@gmail.com> Mon, 28 April 2014 18:23 UTC

Return-Path: <stephen.botzko@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D2B1A6FB5 for <rtcweb@ietfa.amsl.com>; Mon, 28 Apr 2014 11:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 75jJDs9qY0te for <rtcweb@ietfa.amsl.com>; Mon, 28 Apr 2014 11:23:25 -0700 (PDT)
Received: from mail-vc0-x229.google.com (mail-vc0-x229.google.com [IPv6:2607:f8b0:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 13BB51A6FB2 for <rtcweb@ietf.org>; Mon, 28 Apr 2014 11:23:24 -0700 (PDT)
Received: by mail-vc0-f169.google.com with SMTP id im17so8823745vcb.0 for <rtcweb@ietf.org>; Mon, 28 Apr 2014 11:23:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DsZ3USRSOTrTfD+7kkkcPnnJ3SqDHWr1QVwLnSo6p+Q=; b=njMIz3jwHLpvSERKuDCX8FztnB9H5RLl0B2S5BXSyzKkJ97EfECNcI1+IRwADZX5o2 OAp4QMOa9aunznwTDrXu2ewSSVY73tyXFMuEfbdT015SSwHR12ewJ5cG+xSWgw6UxnA2 3SaH0vG4rlghimdxjP7JATy9Oikbx4/pbxRmCwlMPDQa8nw0WGuEj+MyRtlA9qhOf79f wmcE7+4GsuWVCXHIt0q5uYjUCIu3uTrjpVN1nyVzjCyX5tU1bAzeQMk/DWJrXBsbWVZQ YgnlsuSeCh6M28Bx6MFLfLQ2tOW22fWzM/hTcdjjZ2yD4BIsbbj7ZP7qo0HwxVu1bMrJ F29w==
MIME-Version: 1.0
X-Received: by 10.221.34.7 with SMTP id sq7mr24904344vcb.5.1398709404173; Mon, 28 Apr 2014 11:23:24 -0700 (PDT)
Received: by 10.221.40.135 with HTTP; Mon, 28 Apr 2014 11:23:24 -0700 (PDT)
In-Reply-To: <535E7197.3040905@getjive.com>
References: <CAB1_PA7n64TzN4RPM27P0dQ=fMZNnueQ+kc_P6=2CWsioOq+7w@mail.gmail.com> <535E461E.8080803@alvestrand.no> <535E7197.3040905@getjive.com>
Date: Mon, 28 Apr 2014 14:23:24 -0400
Message-ID: <CAMC7SJ46xq87=zh91TC=JTzaVEr5Zm3bfO7kOmZk=KLKFupZxg@mail.gmail.com>
From: Stephen Botzko <stephen.botzko@gmail.com>
To: Jessie Morris <jmorris@getjive.com>
Content-Type: multipart/alternative; boundary="001a1136526a2e0a2604f81e69b7"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/TcnCC7TISOd_43HZBoEpSu9o1ec
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Query Regarding Mandatory audio codecs draft
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 18:23:27 -0000

The mandatory codec question for audio is long settled, and personally I am
thinking we really don't want to reopen that discussion.

The original poster was wanting to know if G.711 was preferred over OPUS
for narrow band.  The answer given was "no".  Is there really a need to
discuss this more?

Stephen


On Mon, Apr 28, 2014 at 11:19 AM, Jessie Morris <jmorris@getjive.com> wrote:

> The only situation that it would make sense to use G.711 and video is on a
> weak platform that happens to have hardware decoding capabilities for H.264
> or VP8 or whatever the video codec is. I don't think there are a lot of
> these currently, but it is possible.
>
>
> On 2014-04-28, 06:14, Harald Alvestrand wrote:
>
>> On 04/28/2014 11:25 AM, Steev James wrote:
>>
>>> Means you say that G.711 uses less bandwidth than Opus at the expense of
>>> complexity.
>>>
>>
>> G.711 gives very low audio quality. The larger complexity of Opus means
>> that it is able to give a much better quality at the same bandwidth.
>>
>> Personal opinion: The only time I'd be wanting to use G.711 if Opus is
>> available is when I'm on a severely underpowered mobile phone. That
>> platform is likely also so weak that I couldn't even imagine using video on
>> it (video is order-of-magnitude more complex to encode/decode than Opus).
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
> --
> Jessie A. Morris
> Jive Communications, Inc.
> jmorris@getjive.com
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>