Re: [codec] A concrete proposal for requirements and testing
Paul Coverdale <coverdale@sympatico.ca> Wed, 06 April 2011 22:40 UTC
Return-Path: <coverdale@sympatico.ca>
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 DB5573A67EB for <codec@core3.amsl.com>; Wed, 6 Apr 2011 15:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.796
X-Spam-Level:
X-Spam-Status: No, score=-1.796 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803]
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 hZeUdZgbTQf3 for <codec@core3.amsl.com>; Wed, 6 Apr 2011 15:40:10 -0700 (PDT)
Received: from blu0-omc2-s2.blu0.hotmail.com (blu0-omc2-s2.blu0.hotmail.com [65.55.111.77]) by core3.amsl.com (Postfix) with ESMTP id 296E13A67D8 for <codec@ietf.org>; Wed, 6 Apr 2011 15:40:10 -0700 (PDT)
Received: from BLU0-SMTP62 ([65.55.111.71]) by blu0-omc2-s2.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 6 Apr 2011 15:41:54 -0700
X-Originating-IP: [70.48.50.205]
X-Originating-Email: [coverdale@sympatico.ca]
Message-ID: <BLU0-SMTP62BA6C70DCFE9EAC0B522ED0A50@phx.gbl>
Received: from PaulNewPC ([70.48.50.205]) by BLU0-SMTP62.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 6 Apr 2011 15:41:52 -0700
From: Paul Coverdale <coverdale@sympatico.ca>
To: 'Jean-Marc Valin' <jean-marc.valin@octasic.com>, 'Anisse Taleb' <anisse.taleb@huawei.com>
References: <64212FE1AE068044AD567CCB214073F123A10234@MAIL2.octasic.com> <F5AD4C2E5FBF304ABAE7394E9979AF7C26BC47FA@LHREML503-MBX.china.huawei.com> <4D9CB1AA.3050101@octasic.com>
In-Reply-To: <4D9CB1AA.3050101@octasic.com>
Date: Wed, 06 Apr 2011 18:41:48 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: en-us
Thread-index: Acv0iQraL+gbfZQXTpi8Fin2r4JLRwAFze1w
X-OriginalArrivalTime: 06 Apr 2011 22:41:52.0914 (UTC) FILETIME=[D3242F20:01CBF4AB]
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: Wed, 06 Apr 2011 22:40:11 -0000
Hi Jean-Marc, Just to clarify a couple of points. When I mentioned 40-60 listeners for an MOS test, this was the number that we used to try to use in tests in Nortel. Of course, more listeners are better, but often there are constraints on time and money. The ITU examples I sent earlier specify 32 listeners for the NB/WB test and 24 for the SWB test. I would suggest 24 listeners as a minimum. I (and others) suggested the use of objectives ("nice to have") as well as requirements ("must have") in the requirements document, but I didn't specifically propose "no worse than AMR-NB" (or AMR-WB) as an objective. In fact, my preference would be to include AMR-NB and AMR-WB as requirements in section 4.2, since there is not much else of substance there. Regards, ...Paul -----Original Message----- From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On Behalf Of Jean-Marc Valin Sent: Wednesday, April 06, 2011 2:32 PM To: Anisse Taleb Cc: codec@ietf.org Subject: Re: [codec] A concrete proposal for requirements and testing Hi Anisse, On 11-04-06 04:11 AM, Anisse Taleb wrote: >>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. > > The tests conducted by Jan were performed with clean speech only (to the > best of my knowledge), in addition the methodology used (MUSHRA) is > admittedly limited when it comes to testing narrowband signals and > especially speech. Moreover, I am not sure as to the use of different > native language listeners. The test is useful in itself, however, more > is needed in order to reach the conclusion you claim. Thank you for answering my questions. So I understand that what you would like to see is a MOS-type listening test with 40-60 listeners (from memory, number quoted by Paul Coverdale at the codec dinner) in both English and (I assume) Chinese. Is that correct? Other things that should be included for narrowband in your opinion? >>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? > > Not sure what the question means, as was discussed during the meeting, I > think the inclusion and comparison to state of the art codecs, including > AMR-NB, is a must in order to fully assess the quality of Opus. In the original email, Koen and I were proposing to include "no worse than AMB-NB" as a desirable *objective* (rather than a hard requirement), as proposed by Paul Coverdale during the meeting. >>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? > > Same comment as for 1) and 2), higher quality cannot be concluded on a > such a restrictive test set. So for wideband, my understanding is that you'd also like to see a MOS-type listening test with 40-60 listeners in both English and Chinese. Is that correct? Anything else on your list? >>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 > > Not strongly against taking such shortcuts, however, please consider > that G.719 has been tested with many signals including reverberant > speech, background noise conditions etc. OK. So I understand that the main issues you have are with narrowband and wideband, right? Cheers, Jean-Marc _______________________________________________ codec mailing list codec@ietf.org https://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