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

Stephen Botzko <stephen.botzko@gmail.com> Tue, 05 April 2011 17:59 UTC

Return-Path: <stephen.botzko@gmail.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 00A363A68D4 for <codec@core3.amsl.com>; Tue, 5 Apr 2011 10:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.78
X-Spam-Level:
X-Spam-Status: No, score=-2.78 tagged_above=-999 required=5 tests=[AWL=-0.182, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 WaY0srL280gb for <codec@core3.amsl.com>; Tue, 5 Apr 2011 10:59:11 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 7FE623A6960 for <codec@ietf.org>; Tue, 5 Apr 2011 10:59:11 -0700 (PDT)
Received: by vxg33 with SMTP id 33so602741vxg.31 for <codec@ietf.org>; Tue, 05 Apr 2011 11:00:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=t7XRIdoD5JEBB8oVKt3eR3EJyviEGrctXiDMHqcpoyA=; b=UL/hOIGe725CWqVD1+sH4y1VTANl2NmMnxdYbzZuxc9cg/LmzzjsddoiGRgXc+llFX f2jqZ9CVucLJiFpcCmlSYvmszHLU781n4U3cxifIGE5WOeWlfnGo/J+RnUxo8MLm4jQ+ RQ6QGkTCSOu5j+fuYaLO1bvQoz0M5M4F36CHI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Vflt0Qx9fu8dkSDH7Im9HckHDLafbtlDp3Bvu0ZIm3BXwKCsFNXKX+EJGc6TOB6cPS aPi9x1gg/e+xu4IIHCwk+BmP2b67A/0zUIV3LZITWaMaAAxc2O6c9lS3wnFpvmpfXg5M m3vTXvPsdGp+1mC2qvtsxnytZpaggA8W+8Cac=
MIME-Version: 1.0
Received: by 10.220.128.205 with SMTP id l13mr599088vcs.193.1302026454145; Tue, 05 Apr 2011 11:00:54 -0700 (PDT)
Received: by 10.220.81.18 with HTTP; Tue, 5 Apr 2011 11:00:54 -0700 (PDT)
In-Reply-To: <4d9b578f.8290d80a.3048.202f@mx.google.com>
References: <64212FE1AE068044AD567CCB214073F123A10234@MAIL2.octasic.com> <4d9b578f.8290d80a.3048.202f@mx.google.com>
Date: Tue, 05 Apr 2011 14:00:54 -0400
Message-ID: <BANLkTikAFsq5Y_9DS7L5kbMoa8R5EfpQ0A@mail.gmail.com>
From: Stephen Botzko <stephen.botzko@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
Content-Type: multipart/alternative; boundary="e0cb4e887849499a1f04a02fa86d"
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 17:59:13 -0000

My recollection was that everyone supported removing GSM-FR.  All other
removals had strong hums on both sides, so there was clearly no consensus.

Although the anchor codecs matter, I think another topic that needs closure
are the speech conditions.  Usually there is some clean speech, but also
samples with noisy or reverberant speech.  Sometimes multiple speakers are
also tested.

I would also suggest at least one tandeming test.

Steve B.

On Tue, Apr 5, 2011 at 1:54 PM, Roni Even <ron.even.tlv@gmail.com> wrote:

> Hi,
>
> 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
>
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec
>
>