[codec] Transparency or intelligibility?

Gregory Maxwell <gmaxwell@juniper.net> Tue, 10 November 2009 14:48 UTC

Return-Path: <gmaxwell@juniper.net>
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 D77B128C1E3 for <codec@core3.amsl.com>; Tue, 10 Nov 2009 06:48:59 -0800 (PST)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5MByzH6EMYUQ for <codec@core3.amsl.com>; Tue, 10 Nov 2009 06:48:59 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by core3.amsl.com (Postfix) with ESMTP id E4FB528C1C2 for <codec@ietf.org>; Tue, 10 Nov 2009 06:48:58 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKSvl9dU9Q5MixyYmcfjPCFH5hkHw6ntSK@postini.com; Tue, 10 Nov 2009 06:49:26 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Tue, 10 Nov 2009 06:45:43 -0800
From: Gregory Maxwell <gmaxwell@juniper.net>
To: "codec@ietf.org" <codec@ietf.org>
Date: Tue, 10 Nov 2009 06:45:42 -0800
Thread-Topic: Transparency or intelligibility?
Thread-Index: AQHKYhR6PzU0AKhjpU26DD37PS5ZAA==
Message-ID: <BCB3F026FAC4C145A4A3330806FEFDA93A468988FC@EMBX01-HQ.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [codec] Transparency or intelligibility?
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Should the IETF standardize wideband Internet codec\(s\)? " <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: Tue, 10 Nov 2009 14:48:59 -0000

One source of disagreement over requirements which I've seen crop up with respect to audio
codecs arises out of what appears to be a lack of agreement on the end goal: Is the expectation 
that the result will be transparent, or that it will be merely intelligible and/or 'good sounding'?

By transparent I mean something roughly like "an experienced listener is unable to distinguish in a
blind listening test even with material selected to be especially challenging for the codec".

While it's is not possible to deliver transparency without intelligibility, it is possible to deliver excellent
intelligibility without a hope of transparency.   So optimizing for one vs the other can lead to different
engineering trade-offs.

For example,  a 7kHz low-pass will produce speech with perfect intelligibility but at the same time
would have absolutely no hope of being transparent.  If you had a goal of even near transparency
you would probably not even consider a codec with a low-pass lower than about 18kHz or so.
(For general audio— for pure speech and adult listeners you could possibly go a bit lower but 7kHz is
far too low)

It was my thought that for the transmission of sound typical Internet bandwidths are high enough that
we really have little excuse but to provide transparency under good operating conditions.

Of course, during levels of high loss or congestion transparency will not be possible and in that case
a codec should maintain intelligibility under adverse conditions and that should be an absolute
requirement too, but in the normal case transparency should be expected.

Is this thinking consistent with the thoughts of other working group participants?