Re: [rtcweb] RTCWEB needs an Internet Codec

Harald Alvestrand <harald@alvestrand.no> Wed, 29 August 2012 12:11 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC97921F8673 for <rtcweb@ietfa.amsl.com>; Wed, 29 Aug 2012 05:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.345
X-Spam-Level:
X-Spam-Status: No, score=-110.345 tagged_above=-999 required=5 tests=[AWL=0.254, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n1EtDlZiMzsA for <rtcweb@ietfa.amsl.com>; Wed, 29 Aug 2012 05:11:22 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 9D73C21F8672 for <rtcweb@ietf.org>; Wed, 29 Aug 2012 05:11:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6C8A539E2A2 for <rtcweb@ietf.org>; Wed, 29 Aug 2012 14:10:51 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wWbp11YN8-gi for <rtcweb@ietf.org>; Wed, 29 Aug 2012 14:10:50 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:be30:5bff:fede:bcdc]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id A7D5039E0F0 for <rtcweb@ietf.org>; Wed, 29 Aug 2012 14:10:50 +0200 (CEST)
Message-ID: <503E06C9.6010901@alvestrand.no>
Date: Wed, 29 Aug 2012 14:10:49 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAKhHsXEW25Z=gaZ2gp5GOaM7upfoL2npt+k7HDNFpn36DcNtnQ@mail.gmail.com> <CAD5OKxuf=PqAYJDze7d7re8A+RBQUn8jUz1azqBBoEQrXPR8sA@mail.gmail.com>
In-Reply-To: <CAD5OKxuf=PqAYJDze7d7re8A+RBQUn8jUz1azqBBoEQrXPR8sA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] RTCWEB needs an Internet Codec
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 29 Aug 2012 12:11:24 -0000

On 08/29/2012 06:13 AM, Roman Shpount wrote:
> Not that I have anything against Opus, but what exactly makes Opus an 
> internet codec? What is internet codec anyway? Makes this all kind of 
> a meaningless argument.
>
> I would argue that for my broadband internet connection G.722 is a 
> perfect internet codec. I do not care about bandwidth savings of Opus, 
> and quality wise, for the voice conversation, I cannot hear any 
> difference.
>
> I would argue G.711 should be the MTI codec. The rest can be left up 
> to browser implementers. We can argue all we want, but the best 
> royalty free low bitrate codec available will be the one everybody 
> supports. We can force it to be Opus, but even if we don't, it will 
> still be Opus on its merit alone. G.722 will probably end up being 
> supported as well, since it is free, pretty good quality, and easy to 
> implement.
>
> P.S. Not that I am arguing for it, I am surprised no one made a case 
> for iSAC, since it is also royalty free, low bit rate, and very high 
> quality. It is event named "internet Speech Audio Codec".

Google, after considering both, would prefer that Opus be the standard.

At high bandwidth / bitrate, Opus is operating in CELT mode, which 
outperforms iSAC.