Re: [AVT] The RTP payload format for multichannel codecs's signalling problem

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 09 February 2004 12:33 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15426 for <avt-archive@odin.ietf.org>; Mon, 9 Feb 2004 07:33:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqAbC-00030M-QN for avt-archive@odin.ietf.org; Mon, 09 Feb 2004 07:33:14 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i19CXEi7011549 for avt-archive@odin.ietf.org; Mon, 9 Feb 2004 07:33:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqAaz-0002yl-9N; Mon, 09 Feb 2004 07:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqAa1-0002x3-MT for avt@optimus.ietf.org; Mon, 09 Feb 2004 07:32:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15382 for <avt@ietf.org>; Mon, 9 Feb 2004 07:32:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqAa1-000779-00 for avt@ietf.org; Mon, 09 Feb 2004 07:32:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqAZ6-00072N-00 for avt@ietf.org; Mon, 09 Feb 2004 07:31:04 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47]) by ietf-mx with esmtp (Exim 4.12) id 1AqAYE-0006xo-00 for avt@ietf.org; Mon, 09 Feb 2004 07:30:10 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121]) by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i19CU8YG023978 for <avt@ietf.org>; Mon, 9 Feb 2004 13:30:08 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Mon, 9 Feb 2004 13:30:08 +0100
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id 1LJTFHKN; Mon, 9 Feb 2004 13:30:08 +0100
Message-ID: <40277CD1.7030602@ericsson.com>
Date: Mon, 09 Feb 2004 13:28:01 +0100
X-Sybari-Trust: 1a6103c8 6b512624 7e80e808 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: Tom Taylor <taylor@nortelnetworks.com>
CC: avt@ietf.org
Subject: Re: [AVT] The RTP payload format for multichannel codecs's signalling problem
References: b23cbb51 6b512624 6c3547e6 00000138 <40228CEB.3010508@nortelnetworks.com>
In-Reply-To: <40228CEB.3010508@nortelnetworks.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Feb 2004 12:30:08.0392 (UTC) FILETIME=[7425D880:01C3EF08]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Tom,

The problem you describe has what I understand solely to do with what 
you use a established media stream. However the problem I discuss has to 
do more directly with the codecs capabilities. If a encoder has stereo 
and mono capabilities and can switch between them, what is necessary to 
signal. For my problem there are certain configuration information that 
needs to be distributed outside of the encoder to decoder chain, this 
primarily being the receivers playback facilities, so that they are 
capable of handling both outputs from the decoder.

So I don't think the problems are that similar. My problem is in direct 
relation to properties of the codec, while your problem is in relation 
the usage.

Cheers

Magnus

Tom Taylor wrote:

>We have a similar problem with distinguishing between audio, voice-band
>data (high 
>speed and low speed), voice-band text, and voice-band FAX.  Each of
>these requires 
>a different combination of treatments in terms of echo cancellor
>operation, 
>silence suppression, and jitter buffer operation.
>
>  
>
 

Magnus Westerlund 

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com



This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt