Re: [codec] A concrete proposal for requirements and testing
Stephen Botzko <stephen.botzko@gmail.com> Thu, 07 April 2011 01:42 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 618A828C0D9 for <codec@core3.amsl.com>; Wed, 6 Apr 2011 18:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.265
X-Spam-Level:
X-Spam-Status: No, score=-3.265 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 IwVPy8enpF17 for <codec@core3.amsl.com>; Wed, 6 Apr 2011 18:42:43 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 5079B3A682C for <codec@ietf.org>; Wed, 6 Apr 2011 18:42:43 -0700 (PDT)
Received: by vws12 with SMTP id 12so1947478vws.31 for <codec@ietf.org>; Wed, 06 Apr 2011 18:44:27 -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=LG0m2ocrhnYMFHyFTOT8eZatR+d/ExL9bJb6N0TcL5Q=; b=qrzECZNXa4zjjsy8ud8rPI0NWNOb3PULBNuCs1ZAQUYrFpnBva5SYDbiYDks2KYMkn 2FvkzMbJUWVR1HZxR1ulUqNtBYwFkn+q8awP8CQLVRi/G/6PAxksCWWnPVdN+MrDaSqi jEcuF99TZ68XuUGDOkdDOEGTpgS016RCSJBmw=
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=BZq5D5TBgq5IqKGXoAWtcRjG0q36ODuzK6tTmlSYfZHmFFVD+9S4YkTYNEBXHd7mhg ZaiCSMbSWhpzlY4dYAA3ymsd5exh5nYgBQgJ3sZ9Jwq5b/1qbba0OsvYVoa3RAmfOr+n HIGXKvmRHcmACz0+ktPCOMKQ37+QPw76ojQwc=
MIME-Version: 1.0
Received: by 10.220.180.9 with SMTP id bs9mr85373vcb.158.1302140666898; Wed, 06 Apr 2011 18:44:26 -0700 (PDT)
Received: by 10.220.81.18 with HTTP; Wed, 6 Apr 2011 18:44:26 -0700 (PDT)
In-Reply-To: <4D9CD3C9.2070004@gmail.com>
References: <64212FE1AE068044AD567CCB214073F123A10234@MAIL2.octasic.com> <4d9b578f.8290d80a.3048.202f@mx.google.com> <BANLkTikAFsq5Y_9DS7L5kbMoa8R5EfpQ0A@mail.gmail.com> <4D9CD3C9.2070004@gmail.com>
Date: Wed, 06 Apr 2011 21:44:26 -0400
Message-ID: <BANLkTi=hAOCA=KfPD25tHBfCU5rKK7FvDA@mail.gmail.com>
From: Stephen Botzko <stephen.botzko@gmail.com>
To: Jean-Marc Valin <jmvalin@gmail.com>
Content-Type: multipart/alternative; boundary="90e6ba53b1d0e5e89204a04a3f79"
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: Thu, 07 Apr 2011 01:42:45 -0000
In-line- BR, Stephen On Wed, Apr 6, 2011 at 4:57 PM, Jean-Marc Valin <jmvalin@gmail.com> wrote: > On 11-04-05 02:00 PM, Stephen Botzko wrote: > > 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. > > > What's your suggestion for this? Making one set of tests on clean > conditions and one on noisy+reverberant? > > Yes. > > Sometimes multiple speakers are also tested. > > > What do you mean by "multiple speakers". All the tests we've done so far > have used a different speaker for each sample. Or do you mean something > else? > > I was meaning a test with an interfering talker (as shown on page 13 of the "Quality Assessment Characterisation/Optimisation step1 Test Plan for the ITU-T G.729 based ..." document that Paul Coverdale posted). Though the other background noise conditions on that page are also worth testing I think. > > I would also suggest at least one tandeming test. > > > What form do you see this taking? > > You could test OPUS -> AMR-NB with G.711 -> AMR->NB as the anchor (or G.729 -> AMR-NB) with (for instance) noisy speech. and/or a similar test using OPUS -> AMR-WB, perhaps with G.719-> AMR-WB as the anchor. > Jean-Marc > > > > 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 >> >> > > _______________________________________________ > codec mailing listcodec@ietf.orghttps://www.ietf.org/mailman/listinfo/codec > > >
- [codec] A concrete proposal for requirements and … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Benjamin M. Schwartz
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Jan Skoglund
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Erik Norvell
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Benjamin M. Schwartz
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Peter Saint-Andre
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Benjamin M. Schwartz
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Peter Saint-Andre
- Re: [codec] A concrete proposal for requirements … Timothy B. Terriberry
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Monty Montgomery
- Re: [codec] A concrete proposal for requirements … Timothy B. Terriberry
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Gregory Maxwell
- Re: [codec] A concrete proposal for requirements … Monty Montgomery
- Re: [codec] A concrete proposal for requirements … Koen Vos
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Koen Vos
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Gregory Maxwell
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Koen Vos
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Kavan Seggie
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Kat Walsh
- Re: [codec] A concrete proposal for requirements … Stefan Hacker
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Serge Smirnoff
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- [codec] Chairs and consensus Cullen Jennings