Re: [codec] draft test and processing plan for the IETF Codec
Roman Shpount <roman@telurix.com> Wed, 13 April 2011 14:18 UTC
Return-Path: <roman@telurix.com>
X-Original-To: codec@ietfc.amsl.com
Delivered-To: codec@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 4C1DEE06C6 for <codec@ietfc.amsl.com>; Wed, 13 Apr 2011 07:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id USWqhnCbvMQk for <codec@ietfc.amsl.com>; Wed, 13 Apr 2011 07:18:42 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfc.amsl.com (Postfix) with ESMTP id 62F00E0690 for <codec@ietf.org>; Wed, 13 Apr 2011 07:18:42 -0700 (PDT)
Received: by eye13 with SMTP id 13so230074eye.31 for <codec@ietf.org>; Wed, 13 Apr 2011 07:18:41 -0700 (PDT)
Received: by 10.213.8.4 with SMTP id f4mr263125ebf.24.1302704321019; Wed, 13 Apr 2011 07:18:41 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by mx.google.com with ESMTPS id y7sm433753eeh.14.2011.04.13.07.18.40 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 13 Apr 2011 07:18:40 -0700 (PDT)
Received: by ewy19 with SMTP id 19so229426ewy.31 for <codec@ietf.org>; Wed, 13 Apr 2011 07:18:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.213.2.65 with SMTP id 1mr2076736ebi.147.1302704320091; Wed, 13 Apr 2011 07:18:40 -0700 (PDT)
Received: by 10.213.4.14 with HTTP; Wed, 13 Apr 2011 07:18:40 -0700 (PDT)
In-Reply-To: <F5AD4C2E5FBF304ABAE7394E9979AF7C26BC684E@LHREML503-MBX.china.huawei.com>
References: <F5AD4C2E5FBF304ABAE7394E9979AF7C26BC684E@LHREML503-MBX.china.huawei.com>
Date: Wed, 13 Apr 2011 10:18:40 -0400
Message-ID: <BANLkTikS2i2NZW47hZGpHK47cGwOYpOOMA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Anisse Taleb <anisse.taleb@huawei.com>
Content-Type: multipart/alternative; boundary="000e0ce0ed463f18a504a0cd7cef"
Cc: "codec@ietf.org" <codec@ietf.org>
Subject: Re: [codec] draft test and processing plan for the IETF Codec
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Apr 2011 14:18:43 -0000
Anisse, Couple of comments about the plan: 1. You are specifying that Opus should be better then G.722 56Kb, even though the plan calls for no tests against G.722 56 Kb. I would suggest removing the criteria. 2. You are also specifying that Opus should be better then G.722 for wideband. I think it should be relaxed to "no worse then". I am not sure expecting better quality on wideband voice samples is realistic. _____________ Roman Shpount On Wed, Apr 13, 2011 at 3:32 AM, Anisse Taleb <anisse.taleb@huawei.com>wrote: > Hi, > Please find attached a first draft of a test plan of the IETF codec (Opus). > The proposal does not claim to be complete, there are still many missing > things, e.g. tandeming cases, tests with delay jitter, dtx etc. Consider it > as a starting point for discussion where everyone is welcome to contribute > in a constructive manner. Further updates are planned, but let's see first > some initial comments. > > The attachment is a pdf version, please let me know if you would like to > see another format and I would be glad to oblige. > > Comments and additions are welcome! > > Kind regards, > /Anisse > (From La Jolla - San Diego). > > _______________________________________________ > codec mailing list > codec@ietf.org > https://www.ietf.org/mailman/listinfo/codec > >
- [codec] draft test and processing plan for the IE… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Schulz, Edward D (Ed)
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Benjamin M. Schwartz
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Roman Shpount
- Re: [codec] draft test and processing plan for th… Erik Norvell
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Peter Saint-Andre
- Re: [codec] draft test and processing plan for th… Stephan Wenger
- Re: [codec] draft test and processing plan for th… Benjamin M. Schwartz
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Peter Saint-Andre
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Ron
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Gregory Maxwell
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Cullen Jennings
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Cullen Jennings
- Re: [codec] draft test and processing plan for th… Roman Shpount
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Ron
- Re: [codec] draft test and processing plan for th… Ron
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… David Virette
- Re: [codec] draft test and processing plan for th… Ron
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Roman Shpount
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Michael Ramalho (mramalho)
- Re: [codec] draft test and processing plan for th… Roman Shpount
- Re: [codec] draft test and processing plan for th… David Virette
- Re: [codec] draft test and processing plan for th… David Virette
- Re: [codec] draft test and processing plan for th… David Virette
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Ron
- Re: [codec] draft test and processing plan for th… Monty Montgomery
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Cullen Jennings
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Christian Hoene
- Re: [codec] draft test and processing plan for th… Christian Hoene