Re: [codec] USAC as reference?

David Virette <david.virette@huawei.com> Mon, 18 April 2011 20:24 UTC

Return-Path: <david.virette@huawei.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 0A49DE07B2 for <codec@ietfc.amsl.com>; Mon, 18 Apr 2011 13:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 hBedZ0BeZueE for <codec@ietfc.amsl.com>; Mon, 18 Apr 2011 13:24:54 -0700 (PDT)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by ietfc.amsl.com (Postfix) with ESMTP id 6C29CE0713 for <codec@ietf.org>; Mon, 18 Apr 2011 13:24:54 -0700 (PDT)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LJV00KZV7DIFR@usaga03-in.huawei.com> for codec@ietf.org; Mon, 18 Apr 2011 15:24:54 -0500 (CDT)
Received: from d009000303 (dslb-178-002-018-084.pools.arcor-ip.net [178.2.18.84]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LJV00LS97DG4K@usaga03-in.huawei.com> for codec@ietf.org; Mon, 18 Apr 2011 15:24:54 -0500 (CDT)
Date: Mon, 18 Apr 2011 22:24:51 +0200
From: David Virette <david.virette@huawei.com>
In-reply-to: <4DA86938.7080407@octasic.com>
To: 'Jean-Marc Valin' <jean-marc.valin@octasic.com>
Message-id: <036201cbfe06$ad28eb30$077ac190$%virette@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="us-ascii"
Content-language: fr
Content-transfer-encoding: 7bit
Thread-index: Acv7hTiozlXy9LQ0R32EREWilnZmMgCgECVQ
References: <000301cbfabc$9e6584c0$db308e40$@uni-tuebingen.de> <016201cbfb75$b22bc730$16835590$%virette@huawei.com> <4DA86938.7080407@octasic.com>
Cc: codec@ietf.org
Subject: Re: [codec] USAC as reference?
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: Mon, 18 Apr 2011 20:24:55 -0000

Hi Jean-Marc,
Of course IETF can liaise with MPEG asking to include OPUS in USAC
verification tests, but I am a bit skeptical that OPUS will be included in
their extensive testing if a sufficient testing effort is not done in IETF
before.
By extensive listening tests, I mean a verification test where more than 15
listening labs will take part to the first round of listening to conduct
between 1 and 3 experiments each.
Best regards,
David


-----Original Message-----
From: Jean-Marc Valin [mailto:jean-marc.valin@octasic.com] 
Sent: vendredi 15 avril 2011 17:50
To: David Virette
Cc: 'Christian Hoene'; 'Anisse Taleb'; codec@ietf.org
Subject: Re: [codec] USAC as reference?

Hi David,

On 11-04-15 10:02 AM, David Virette wrote:
> The only reference quality implementation of USAC is owned by the initial
> proponents of the codec. If the group wants to test OPUS vs USAC, the best
> way is probably to inform MPEG that IETF would like to conduct some tests
> comparing those two codecs. Regarding the inclusion of OPUS in the USAC
> verification tests, the test plan and accompanying workplan have already
> been agreed and the first round of testing will occur in June. However, it
> is foreseen to have a second round of testing by the end of the year. It
> could be proposed to include OPUS in this second phase. As Anisse said,
> there will be an MPEG meeting in July, this leaves enough time to liaise
> with MPEG before the next meeting. But I think that only a standardized
> codec could be included in the USAC verification tests.

I think it's indeed a good idea to liaise with MPEG before the next meeting 
to get Opus included in the second round of USAC testing. I think the 
condition that only standardized codecs can be included again supports the 
idea of first publishing Opus as a proposed standard to facilitate further 
testing.

Cheers,

	Jean-Marc