Re: [codec] Conferencing and layering

"Benjamin M. Schwartz" <bmschwar@fas.harvard.edu> Wed, 13 January 2010 13:36 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 20D9F3A69CE for <codec@core3.amsl.com>; Wed, 13 Jan 2010 05:36:18 -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=[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 C2CP1oUcDgwE for <codec@core3.amsl.com>; Wed, 13 Jan 2010 05:36:17 -0800 (PST)
Received: from us12.unix.fas.harvard.edu (us12.unix.fas.harvard.edu [140.247.35.203]) by core3.amsl.com (Postfix) with ESMTP id 0665D3A69B0 for <codec@ietf.org>; Wed, 13 Jan 2010 05:36:17 -0800 (PST)
Received: from us12.unix.fas.harvard.edu (localhost.localdomain [127.0.0.1]) by us12.unix.fas.harvard.edu (Postfix) with ESMTP id EACD1664EA5; Wed, 13 Jan 2010 08:36:13 -0500 (EST)
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=IMJdD7tV4GiEonJ F8k6YMXhUlpxZaOZeZ5Uf5B2LyZ4=; b=VetB6Ga5iYxXF90dRMojL7HFV5qB1Jz a/VgSfni1Kvc+fRvbi1SMcSV466IJeSy/9Pg2IHmrFA7M5xOKMXmIlWK7CxnKtVt +RLAYQp5s3BUiCl//vwXUdl7w+gmQC6NonoqiX5DbcVGHVuO+TDB4du65icVnJgl emzBK7kQd+4s=
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=Oeo9M+Dqh vTPaPywz/A8/nKuuhdDPBXQ2L3lMpqMc4NscrseLMSsqsFHIQPn1BFm1rkfzdIeh OiNsww/RaH7g4rzxIeoy7iCJ7i9nibLaAFx3cKkxFe2RVu1UrVCIzcigYyRzsJ5L dApDrNrPRugl8JjOSrMMpRYN/hrsKrt52o=
Received: from [192.168.1.100] (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 us12.unix.fas.harvard.edu (Postfix) with ESMTPSA id DC9C6664E32; Wed, 13 Jan 2010 08:36:13 -0500 (EST)
Message-ID: <4B4DCC4D.60703@fas.harvard.edu>
Date: Wed, 13 Jan 2010 08:36:13 -0500
From: "Benjamin M. Schwartz" <bmschwar@fas.harvard.edu>
User-Agent: Thunderbird 2.0.0.23 (X11/20091019)
MIME-Version: 1.0
To: Christian Hoene <hoene@uni-tuebingen.de>
References: <20091223171501.7BAE33A697D@core3.amsl.com> <13194D66-2110-4CB2-B130-8807BE57488B@cisco.com> <458913681001111218o3b232e4sd785b3c09809fcbc@mail.gmail.com> <000101ca931e$12ea08f0$38be1ad0$@de> <3d032e5d1001130226s2ca789abva75179ea826c7845@mail.gmail.com> <006901ca943e$fad66c00$f0834400$@de>
In-Reply-To: <006901ca943e$fad66c00$f0834400$@de>
X-Enigmail-Version: 0.95.7
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="------------enig82C4F12AF989F9F10C0DE62A"
Cc: codec@ietf.org
Subject: Re: [codec] Conferencing and layering
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bens@alum.mit.edu
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: Wed, 13 Jan 2010 13:36:18 -0000

Christian Hoene wrote:
> 1) A central conferencing server that serves all clients.
> - a) which does a efficient single changing mixing - still a challenge if you have multiple operational modes in a codec.
> - b) which does a more intelligent mixing using (at least) two channels to support spatial hearing - this increases the quality of conference call significant. Thus, stereo modes must be supported if the codec shall support state of the art conferencing technologies.
> 2) A mesh-like N-to-N transmission conference call. Then you might benefit from layered coding because you have at a client you have to encode only once. But then again, how to support multiple coding modes?
> 3) One client acts as conference server (similar to 1)
> 
> In total, the support of conferencing calls will require:
> - Layered coding
> - Efficient mixing of streams
> - Support of stereo
> - Good (self-)transcoding
> Is this all achievable?

It's obviously not all "required".  Layered coding is irrelevant unless
the network is heterogeneous and supports efficient multicast routing, and
on the internet this is essentially never the case.  The only places on
the internet where efficient multicast routing is supported are very fast
links where the small bandwidth savings of layering are irrelevant.

Similarly, "efficient mixing" is not really required.  Modern audio codecs
typically require so little CPU time that decoding, mixing, and
re-encoding for a large number of channels in real time is perfectly
possible without high-end hardware.  Certainly, conferencing makes encode
and decode efficiency an important consideration.  Codecs capable of
accelerated mixing would be intriguing, but by no means required.

--Ben