Re: [codec] A concrete proposal for requirements and testing
Paul Coverdale <coverdale@sympatico.ca> Thu, 07 April 2011 13:32 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 5CA953A6916 for <codec@core3.amsl.com>; Thu, 7 Apr 2011 06:32:01 -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 uOnC3mANDOGo for <codec@core3.amsl.com>; Thu, 7 Apr 2011 06:31:59 -0700 (PDT)
Received: from blu0-omc2-s3.blu0.hotmail.com (blu0-omc2-s3.blu0.hotmail.com [65.55.111.78]) by core3.amsl.com (Postfix) with ESMTP id 4E9113A690F for <codec@ietf.org>; Thu, 7 Apr 2011 06:31:59 -0700 (PDT)
Received: from BLU0-SMTP25 ([65.55.111.71]) by blu0-omc2-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 7 Apr 2011 06:33:43 -0700
X-Originating-IP: [67.70.131.179]
X-Originating-Email: [coverdale@sympatico.ca]
Message-ID: <BLU0-SMTP25FDDFB5058944E6068236D0A40@phx.gbl>
Received: from PaulNewPC ([67.70.131.179]) by BLU0-SMTP25.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 7 Apr 2011 06:33:42 -0700
From: Paul Coverdale <coverdale@sympatico.ca>
To: 'Jean-Marc Valin' <jean-marc.valin@octasic.com>
References: <64212FE1AE068044AD567CCB214073F123A10234@MAIL2.octasic.com> <F5AD4C2E5FBF304ABAE7394E9979AF7C26BC47FA@LHREML503-MBX.china.huawei.com> <4D9CB1AA.3050101@octasic.com> <BLU0-SMTP62BA6C70DCFE9EAC0B522ED0A50@phx.gbl> <4D9D1546.7010901@octasic.com>
In-Reply-To: <4D9D1546.7010901@octasic.com>
Date: Thu, 07 Apr 2011 09:33:37 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acv0xGGxXhfzzSALRAaSAjqqFdpIhwAWKRMg
Content-Language: en-us
X-OriginalArrivalTime: 07 Apr 2011 13:33:42.0301 (UTC) FILETIME=[6938ACD0:01CBF528]
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 13:32:01 -0000
Hi Marc, I think that the issues of performance requirements and encumbered technologies are separate. In fact, the WG charter states "The working group cannot explicitly rule out the possibility of adopting encumbered technologies". At the end of the day, people will make their own trade-off between Opus performance and whether it is encumbered or not. So the requirements need to include some reasonable performance targets, and AMR-NB and AMR-WB provide those. In any case, the test plans that I sent out earlier are examples, and need to be viewed in relation to the terms of reference that were agreed for G.729EV. The intention at the time was to provide scalable wideband on top of G.729, so for NB the main comparison was with G.729A. For WB, the chosen comparison was primarily G.722, with some G.722.2. Regards, ...Paul -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@octasic.com] Sent: Wednesday, April 06, 2011 9:37 PM To: Paul Coverdale Cc: 'Anisse Taleb'; codec@ietf.org Subject: Re: [codec] A concrete proposal for requirements and testing I strongly disagree with including AMR-NB and AMR-WB as strict requirements for several reasons. Those codecs are not credible alternatives to Opus within the charter of this WG, to "try to avoid encumbered technologies." Also, I note from the ITU test plan for G.729.1 (then G.729EV) you sent that it does not even mention AMR-NB. As for AMR-WB (G.722.2), it is only included at a bit-rate of 8.85 kb/s even though the lowest G.729.1 bit-rate is (AFAIK) 14 kb/s. Looking at this paper from Nokia: http://research.nokia.com/files/public/%5B11%5D_ICASSP2010_Voice%20Quality%2 0Evaluation%20of%20Various%20Codecs.pdf we see that G.729.1 is clearly worse than AMR-WB. Despite that, it seems like the ITU-T has seen the value of this codec, which supports both narrowband and wideband at multiple rates. The codec we're designing here is meant to do not only narrowband and wideband, but also super-wideband and fullband, for both speech and music and for mono and stereo. This is something which -- to the best of my knowledge -- has not been done before for an interactive codec. Requiring Opus to also beat all codecs out there in all circumstances is thus totally unreasonable (despite the fact that the tests we did so far indicate we may be close to that). Cheers, Jean-Marc
- [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