Re: [codec] Suggested summary...

"Christian Hoene" <hoene@uni-tuebingen.de> Fri, 02 July 2010 16:24 UTC

Return-Path: <hoene@uni-tuebingen.de>
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 8DA803A68D6 for <codec@core3.amsl.com>; Fri, 2 Jul 2010 09:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.368
X-Spam-Level:
X-Spam-Status: No, score=-5.368 tagged_above=-999 required=5 tests=[AWL=0.880, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, 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 Nmt9eZ1o4poS for <codec@core3.amsl.com>; Fri, 2 Jul 2010 09:24:18 -0700 (PDT)
Received: from mx06.uni-tuebingen.de (mx06.uni-tuebingen.de [134.2.3.3]) by core3.amsl.com (Postfix) with ESMTP id 967253A67D4 for <codec@ietf.org>; Fri, 2 Jul 2010 09:24:17 -0700 (PDT)
Received: from hoeneT60 (u-173-c044.cs.uni-tuebingen.de [134.2.173.44]) (authenticated bits=0) by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id o62GOLut010187 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Jul 2010 18:24:22 +0200
From: Christian Hoene <hoene@uni-tuebingen.de>
To: 'stephen botzko' <stephen.botzko@gmail.com>
References: <062.7439ee5d5fd36480e73548f37cb10207@tools.ietf.org> <3E1D8AD1-B28F-41C5-81C6-478A15432224@csperkins.org> <D6C2F445-BE4A-4571-A56D-8712C16887F1@americafree.tv> <C0347188-A2A1-4681-9F1E-0D2ECC4BDB3B@csperkins.org> <u2x6e9223711004210733g823b4777y404b02330c49dec1@mail.gmail.com> <000001cae173$dba012f0$92e038d0$@de> <r2q6e9223711004211010gfdee1a70q972e8239fef10435@mail.gmail.com> <001101cae177$e8aa6780$b9ff3680$@de> <t2t6e9223711004211119i6b107798pa01fc4b1d33debf1@mail.gmail.com> <002d01cae188$a330b2c0$e9921840$@de> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3F4A017@IRVEXCHCCR01.corp.ad.broadcom.com> <4BD11C50.2020206@usherbrooke.ca> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3F4A270@IRVEXCHCCR01.corp.ad.broadcom.com> <12151537-165D-426A-B71F-8B3D76BE4854@cisco.com> <CB68DF4CFBEF4942881AD37AE1A7E8C74B901372FE@IRVEXCHCCR01.corp.ad.broadcom.com> <20100430230756.13687lc1s5o89gsc@mail.skype.net> <CB68DF4CFBEF4942881AD37AE1A7E8C74B90345522@IRVEXCHCCR01.corp.ad.broadcom.com> <CB68DF4C! FBEF4942881AD37AE1A7E8C 74B9BE9EDB7@IRVEXCHCCR01.corp.ad.broadcom.com> <20100526151326.2882694zuaeslk3q@mail.skype.net> <CB68DF4CFBEF4942881AD37AE1A7E8C74B9BE9F2E7@IRVEXCHCCR01.corp.ad.broadcom.com> <20100526214255.206532jzf8wjld1r@mail.skype.net> <002901cafd89$acf402e0$06dc08a0$@de> <19367DD02EBD40829869907AEA0CE128@china.huawei.com> <000601cafd9b$148fd850$3daf88f0$@de> <568A92CB079CCF43BA5C8D7B08BCB4AE817DCBA900@SJEXCHCCR02.corp.ad.broadcom.com> <002501cafdb4$09394810$1babd830$@de> <56E363F9-AB88-43A3-8ECC-99A7E9796330@cisco.com> <001901cb19ce$a074d600$e15e8200$@de> <AANLkTik-bei7mg9l28yssj8l49tqGX1gbTB1JJ59eyn-@mail.gmail.com> <6A21D03881734E0AB69220FD6B6CCDCB@china.huawei.com> <003a01cb19e4$ccdb8ed0$6692ac70$@de> <AANLkTikF-5hqOgYh52aJNntrQGZ-ViLJ68ICZIn663lr@mail.gmail.com>
In-Reply-To: <AANLkTikF-5hqOgYh52aJNntrQGZ-ViLJ68ICZIn663lr@mail.gmail.com>
Date: Fri, 02 Jul 2010 18:24:22 +0200
Organization: Universität Tübingen
Message-ID: <000a01cb1a03$07efa100$17cee300$@de>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01CB1A13.CB787100"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsZ6hemFXX4lwD1Rz6VE0H5m1L9bgAFyK5g
Content-Language: de
X-AntiVirus: NOT checked by Avira MailGate (version: 3.0.0-4; host: mx06)
Cc: codec@ietf.org
Subject: Re: [codec] Suggested summary...
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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, 02 Jul 2010 16:24:19 -0000

Hi Stephen,

 

 

From: stephen botzko [mailto:stephen.botzko@gmail.com] 
Sent: Friday, July 02, 2010 3:26 PM
To: Christian Hoene
Cc: Herve Taddei; codec@ietf.org
Subject: Re: [codec] Suggested summary...

 

I understand the 256 sample size (I did the math also!), though it is perfectly straightforward to adapt transforms to other sizes.  G.719 for instance uses a 960 sample DCT transform for 20 ms frame size.  There are many other examples that could be named.  I don't think the sound card argument is all that relevant, since that is a normal place to put a buffer anyway, and there is no reason why that buffer needs to be related to the frame size.

[Christian Hoene] If it comes to ultra low delay, the buffering at the sound card becomes important and must be optimized. Some sound cards (and their DMA controller) have restrictions on the size of blocks (called periods in ALSA). Having “strange” frame sizes will increase the latency because of re-framing.

Perhaps more importantly, I do not think it is appropriate to work backwards from technology contributions to create the requirements.  

[Christian Hoene] You are right. However, the requirements have to be realistic. Looking at existing technologies helps you to know what is possible at the moment.

The normal way in the IETF is to work forward from use cases and problem statements.  IMHO working forward is much more likely to get good results, and it is fair to all (past and future) contributors.

BTW, personally I do not place a very high priority on distributed internet music ensemble performances.  While I am ok if that happens to fall out of the design, it possibly has a lot of other implications beyond delay.  I would happily trade outstanding packet loss performance for music ensembles if it came down to it, and I suspect many other VOIP folks would concur.  Is there a more compelling  (maybe less fun) use case you can reference in the low-delay requirement?



[Christian Hoene] Musical telepresence is a good use case because it is the upper limit of quality. A monaural audio transmissions can hardly be better. It is also a good marketing argument: The IWAC codec provides the best audio quality at lowest latency.  Also, this use-case is unique because  here is not no other standardized audio codec out here supporting it.

Please have a look on the following PhD to understand the requirements of musical telepresence better:
http://www.itm.uni-luebeck.de/users/carot/Docs/dissertation_AC.pdf

Christian