IETF Logo Mail Archive

Re: [codec] possible issues to track

"Benjamin M. Schwartz" <bmschwar@fas.harvard.edu> Fri, 26 March 2010 00:58 UTC

Return-Path: <bmschwar@fas.harvard.edu>
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 BA7BA3A684D for <codec@core3.amsl.com>; Thu, 25 Mar 2010 17:58:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.469
X-Spam-Level:
X-Spam-Status: No, score=-5.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 UCqBjVsnArVW for <codec@core3.amsl.com>; Thu, 25 Mar 2010 17:58:21 -0700 (PDT)
Received: from us25.unix.fas.harvard.edu (us25.unix.fas.harvard.edu [140.247.35.201]) by core3.amsl.com (Postfix) with ESMTP id 9775A3A67FC for <codec@ietf.org>; Thu, 25 Mar 2010 17:58:21 -0700 (PDT)
Received: from us25.unix.fas.harvard.edu (localhost.localdomain [127.0.0.1]) by us25.unix.fas.harvard.edu (Postfix) with ESMTP id 7B9831D72DA; Thu, 25 Mar 2010 20:58:43 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=fas.harvard.edu; h= message-id:date:from:reply-to:mime-version:to:cc:subject :references:in-reply-to:content-type; s=mail; bh=W8OV5iO3OF5j+xc U1icxXNY/ZALiTpeGYzsoOylrJEo=; b=W4UYvLNm73PXhlNGv1/2QpPNQgZW2Ug MKkqFOj6yNgzk70qw9SxF754Krx1TZPIRnt+Z3YYHJ8GK09YW4mU2SKss2YOYIdx Ir7m0211t1SVYEGUWoNlsl18oHrQ6SxhgKROVULutTz66Lqy29y0fMAd/Hip89Rz o167cKMEbXhs=
DomainKey-Signature: a=rsa-sha1; c=simple; d=fas.harvard.edu; h= message-id:date:from:reply-to:mime-version:to:cc:subject :references:in-reply-to:content-type; q=dns; s=mail; b=egz3dk22T eWkV0DnticqZx0yVpwO3yN1JJAlaFaU7ZPqjxDq7eC4YH6s2UV/X0ccT6pInBkmL iW8Xy+3VHswDpdVxQjsAyDQFNC8jzpmXLJM3sjE7RlzAPa55z1s1H6HGo///OJwJ cl1DkzOJbL1GTMPF/6KGtk3OGoS6D+r+fM=
Received: from [192.168.1.101] (c-71-192-160-188.hsd1.nh.comcast.net [71.192.160.188]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: bmschwar@fas) by us25.unix.fas.harvard.edu (Postfix) with ESMTPSA id 6B6F31D7253; Thu, 25 Mar 2010 20:58:43 -0400 (EDT)
Message-ID: <4BAC06BD.8080309@fas.harvard.edu>
Date: Thu, 25 Mar 2010 20:58:37 -0400
From: "Benjamin M. Schwartz" <bmschwar@fas.harvard.edu>
User-Agent: Thunderbird 2.0.0.23 (X11/20091019)
MIME-Version: 1.0
To: Michael Knappe <mknappe@juniper.net>
References: <05542EC42316164383B5180707A489EE1D0AA5F542@EMBX02-HQ.jnpr.net>
In-Reply-To: <05542EC42316164383B5180707A489EE1D0AA5F542@EMBX02-HQ.jnpr.net>
X-Enigmail-Version: 0.95.7
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="------------enig05A50182819FD812EF9E42B7"
Cc: "codec@ietf.org" <codec@ietf.org>
Subject: Re: [codec] possible issues to track
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bens@alum.mit.edu
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: Fri, 26 Mar 2010 00:58:22 -0000

> ----- Original Message -----
>> 3. The format should provide a way to specify N named output channels
as linear combinations of the
>> coded channels.

Michael Knappe wrote:
> Just to clarify, is #3 what's sometimes called a fold-down scheme? (DVD-Audio for instance could generate stereo mixdowns from multi-channel content on the fly)

That would be one good use of it.  It could also be used to increase
efficiency by statically decoupling surround-sound channels.  For example,
a "7.1" channel mix could be transmitted as just two stereo pairs, with an
8x4 mixing matrix to produce the 8 output channels.  This obviously
wouldn't make full use of the speakers, but it would be allowable, and
maybe useful.  Even if the number of channels in and out is the same
(square mixing matrix), decorrelating the channels could improve compression.

Another possibility is to specify a number of different mixing matrices,
so that a single stream could have defined mixes for different output systems.

The biggest problem I see with this system is agreeing on channel names.
I wonder if there's an existing multichannel mapping or mixing
specification somewhere that we could borrow.

--Ben

v2.23.0 | Report a Bug | By Email