Re: [codec] Audio tests: Further steps
Ron <ron@debian.org> Tue, 23 April 2013 19:31 UTC
Return-Path: <ron@debian.org>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E455F21F9766 for <codec@ietfa.amsl.com>; Tue, 23 Apr 2013 12:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.423
X-Spam-Level:
X-Spam-Status: No, score=-1.423 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_MISMATCH_NET=0.311, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FLl1K3VrN8Yr for <codec@ietfa.amsl.com>; Tue, 23 Apr 2013 12:31:11 -0700 (PDT)
Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:6]) by ietfa.amsl.com (Postfix) with ESMTP id 0B54E21F9759 for <codec@ietf.org>; Tue, 23 Apr 2013 12:31:10 -0700 (PDT)
Received: from ppp121-45-66-70.lns20.adl6.internode.on.net (HELO audi.shelbyville.oz) ([121.45.66.70]) by ipmail06.adl6.internode.on.net with ESMTP; 24 Apr 2013 05:01:02 +0930
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id 4689D4F8F3; Wed, 24 Apr 2013 05:01:01 +0930 (CST)
X-Virus-Scanned: Debian amavisd-new at audi.shelbyville.oz
Received: from audi.shelbyville.oz ([127.0.0.1]) by localhost (audi.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id CWfKf1aIyWlc; Wed, 24 Apr 2013 05:01:00 +0930 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id 54F854F902; Wed, 24 Apr 2013 05:01:00 +0930 (CST)
Date: Wed, 24 Apr 2013 05:01:00 +0930
From: Ron <ron@debian.org>
To: codec@ietf.org
Message-ID: <20130423193100.GA29460@audi.shelbyville.oz>
References: <00f801ce3ff7$354e29b0$9fea7d10$@uni-tuebingen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <00f801ce3ff7$354e29b0$9fea7d10$@uni-tuebingen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: cs.wg2.qualinet@listes.epfl.ch
Subject: Re: [codec] Audio tests: Further steps
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: Tue, 23 Apr 2013 19:31:12 -0000
On Tue, Apr 23, 2013 at 09:50:16AM +0200, Christian Hoene wrote: > Hi, > > currently, the codec comparison tests are running. Because of the request of > many codec developers, we plan to extend those tests: We might add audio > tests in which the content is varied to a large extend. For that, we need > sample that cannot be compressed well by Opus or AAC-eLD. For me, it is easy > to get those difficult samples for Opus. It is much challenging to get those > for AAC-eLD. Thus, if somebody had to time to study the weaknesses of > AAC-eLD, please forward me the samples. Uhm, so ... while I'm certain that the codec developers will be delighted if you can point out any new killer samples that they aren't yet aware of (since significant work has already been made to improve the encoder for the known ones, and that work is still ongoing) -- I'm also pretty certain that going out of your way to deliberately select such samples immediately disqualifies this from being characterised as a "comparison test", or at least claiming that it's even remotely representative of what people will observe over a general corpus of their own audio, given the degree to which such samples really are outliers. > I cannot start fair tests if I do not have challenging samples for both > codecs. While such a test might have some novelty value to show "here are some non-exhaustive results for the worst samples that we could find in a few days of searching", I'm pretty sure words like "fair" and "scientific rigour" don't really belong in the same sentence. Not in the least when you also say "we have the established list for one codec, but the known killers for the other is at present entirely unknown to us". If you want to spend your time doing that, that's fine, and the results may well be 'interesting'. But mischaracterising them as a "comparison" test would just be somewhere on the spectrum from "mildly amusing" to "a sad day for Modern Science". It's your reputation though, and I can't tell you how to spend it. But you might want to think this through a little better if you are going to paint this with the brush of Being Science. This isn't the cosmetics industry, other people can measure these things too, and will continue to for some time to come. Cheers, Ron
- Re: [codec] Audio tests: Further steps Ron
- [codec] Audio tests: Further steps Christian Hoene
- Re: [codec] Audio tests: Further steps Paul Coverdale
- Re: [codec] Audio tests: Further steps Jean-Marc Valin
- Re: [codec] Audio tests: Further steps Timothy B. Terriberry
- Re: [codec] Audio tests: Further steps Paul Coverdale
- Re: [codec] Audio tests: Further steps Ron
- Re: [codec] Audio tests: Further steps Christian Hoene