Re: [codec] A concrete proposal for requirements and testing

Jean-Marc Valin <jean-marc.valin@octasic.com> Tue, 05 April 2011 18:14 UTC

Return-Path: <jean-marc.valin@octasic.com>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 22E743A685A for <codec@core3.amsl.com>; Tue, 5 Apr 2011 11:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level:
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P1Qoqh5fFoHD for <codec@core3.amsl.com>; Tue, 5 Apr 2011 11:14:18 -0700 (PDT)
Received: from toroondcbmts08-srv.bellnexxia.net (toroondcbmts08-srv.bellnexxia.net [207.236.237.42]) by core3.amsl.com (Postfix) with ESMTP id 27C573A67A6 for <codec@ietf.org>; Tue, 5 Apr 2011 11:14:17 -0700 (PDT)
Received: from toip55-bus.srvr.bell.ca ([67.69.240.141]) by toroondcbmts08-srv.bellnexxia.net (InterMail vM.8.00.01.00 201-2244-105-20090324) with ESMTP id <20110405181600.GFHF12818.toroondcbmts08-srv.bellnexxia.net@toip55-bus.srvr.bell.ca>; Tue, 5 Apr 2011 14:16:00 -0400
Received: from toip53-bus.srvr.bell.ca ([67.69.240.54]) by toip55-bus.srvr.bell.ca with ESMTP; 05 Apr 2011 14:15:51 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvIAAM9Ym03PPaAN/2dsb2JhbACYIY1Id8M+hWwEkQAG
Received: from mail.octasic.com ([207.61.160.13]) by toip53-bus.srvr.bell.ca with ESMTP; 05 Apr 2011 14:15:51 -0400
Received: from [10.100.50.90] (10.100.50.90) by MAIL2.octasic.com (10.100.10.44) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 5 Apr 2011 14:15:51 -0400
Message-ID: <4D9B5C57.3050807@octasic.com>
Date: Tue, 05 Apr 2011 14:15:51 -0400
From: Jean-Marc Valin <jean-marc.valin@octasic.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
References: <64212FE1AE068044AD567CCB214073F123A10234@MAIL2.octasic.com> <4d9b578f.8290d80a.3048.202f@mx.google.com>
In-Reply-To: <4d9b578f.8290d80a.3048.202f@mx.google.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.100.50.90]
Cc: codec@ietf.org
Subject: Re: [codec] A concrete proposal for requirements and testing
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2011 18:14:19 -0000

Hi Roni,

Sorry if this sounded like a call for consensus since that's not what it 
was meant to be. Rather, it was merely a *proposal* to get the discussion 
started. More precisely, this is about what needs to be answered. This is 
why we listed these 7 questions in the original email. Taking just the 
first one: "Does anyone disagree that this is sufficient to meet the Sec 
4.2 requirement of out-performing Speex in narrowband mode?", I'm fine if 
you disagree, but if that's the case I'd at least know what test it would 
take to convince you.

Cheers,

	Jean-Marc


On 11-04-05 01:54 PM, Roni Even wrote:
> I would expect that a message that in my view calls for consensus, to come
> from the WG chairs.
>
> As for your question, saying that a presentation by one tester addresses
> the requirements is not sufficient in my view. I would expect to see a
> document that summarized all tests done based on a common test plan by more
> than one tester. The problem is that if there is no plan to comment on and
> to use you cannot compare between different results.
>
> I think that Paul sent an example of how to draft a plan that can be used.
>
> As for removing GSM-FR, G.722 and Speex-UWB I am OK. As far as I remember
> the meeting there was no consensus on the reference codecs.
>
> Roni Even
>
> *From:*codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] *On Behalf Of
> *Jean-Marc Valin
> *Sent:* Thursday, March 31, 2011 4:54 PM
> *To:* codec@ietf.org
> *Subject:* [codec] A concrete proposal for requirements and testing
>
> Hi,
>
> Following the meeting and post-meeting discussions about requirements and
> testing, we would like to make the following proposal which addresses the
> opposing views which prevented consensus in the meeting today.
>
> First, we propose to remove the following codecs from the requirements:
>
> - GSM-FR, based on consensus from the list
> - G.722, based on being clearly out-performed by G.722.1
> - Speex-UWB, based on the fact that the author himself does not recommend
> it being used :-)
>
> We can keep the other reference codecs as minimum quality requirement and
> include being no worse than AMR-NB and AMR-WB as "objectives" that are
> "nice to have", but not hard requirements.
>
>  From there and based on the listening tests presented by Jan Skoglund
> today, let's see what we can already conclude and what still needs more
> testing:
>
> 1) The narrowband test showed that Opus had higher quality than Speex at 11
> kb/s. Does anyone disagree that this is sufficient to meet the Sec 4.2
> requirement of out-performing Speex in narrowband mode?
>
> 2) The narrowband test showed that Opus had higher quality at 11 kb/s than
> iLBC at 15 kb/s. Does anyone disagree that this is sufficient to meet the
> Sec 4.2 requirement of out-performing iLBC.
>
> 3) There have been no formal comparison with AMR-NB yet. What do you think
> would be sufficient to assess the quality of Opus compared to AMR-NB?
>
> 4) The wideband test showed that Opus at 19.85 kb/s had higher quality than
> Speex-WB at 24 kb/s. Does anyone disagree that this is sufficient to meet
> the Sec 4.2 requirement of out-performing Speex in wideband mode?
>
> 5) The wideband test showed that Opus at 19.85 kb/s had higher quality than
> G.722.1 at 24 kb/s. Does anyone disagree that this is sufficient to meet
> the Sec 4.2 requirement of out-performing G.722.1?
>
> 6) The wideband test showed that Opus at 19.85 kb/s had higher quality than
> AMR-WB at 19.85 kb/s. Does anyone disagree that this is sufficient to
> concluded that the proposed "nice to have" objective of "no worse than
> AMR-WB" is met?
>
> 7) The fullband test showed that Opus at 32 kb/s had higher quality than
> G.719 at 32 kb/s. Does anyone disagree that this is sufficient to meet the
> Sec 4.2 requirement of out-performing G.722.1C, considering that G.719 has
> already been shown to out-perform G.722.1C
>
> If you disagree with any of the points above -- as may very well be the
> case -- please do provide a concrete test proposal that would be sufficient
> to convince you.
>
> Cheers,
>
> Jean-Marc and Koen
>