Re: [AVT] Re: VMR-WB RTP Payload and Storage Formats
Colin Perkins <csp@csperkins.org> Tue, 05 October 2004 08:47 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03775 for <avt-archive@ietf.org>; Tue, 5 Oct 2004 04:47:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEl8Y-0003mE-IO for avt-archive@ietf.org; Tue, 05 Oct 2004 04:57:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEkww-0000gv-8N; Tue, 05 Oct 2004 04:45:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEkqn-0008Kf-E3 for avt@megatron.ietf.org; Tue, 05 Oct 2004 04:39:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03342 for <avt@ietf.org>; Tue, 5 Oct 2004 04:39:11 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEkzz-0001XG-KI for avt@ietf.org; Tue, 05 Oct 2004 04:48:47 -0400
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:60044 helo=[192.168.0.5]) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42) id 1CEkqB-0003VW-8v; Tue, 05 Oct 2004 09:38:35 +0100
In-Reply-To: <EBF631554F9CD7118D0B00065BF34DCB06FA781A@il27exm03.cig.mot.com>
References: <EBF631554F9CD7118D0B00065BF34DCB06FA781A@il27exm03.cig.mot.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <EF6DCE98-16A9-11D9-9E24-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Re: VMR-WB RTP Payload and Storage Formats
Date: Tue, 05 Oct 2004 09:38:30 +0100
To: Scribano Gino-QA1087 <Gino.Scribano@motorola.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: magnus.westerlund@ericsson.com, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Gino, Thanks - this is a much more compelling explanation of the problem. The issue with switching between sampling rates in an RTP session is a well known problem with the way audio payload formats have been defined in the RTP/AVP profile. If you want to work to solve that in the general case, I would support that work. However, introducing workarounds for specific codec - making it inconsistent with the others in the profile - doesn't seem like a good idea to me. On 5 Oct 2004, at 05:58, Scribano Gino-QA1087 wrote: > It seems that the 'sampling rate' issue has now crossed over to the > Storage Format thread. In any case, it's been a while since my initial > comments regarding application impacts of restricting the RTP > timestamp to be equivalent to the source media sampling rate. So, I > would like to reiterate that the impact of this restriction extends > well beyond saving a few bytes of storage in a tone generation box. As > I stated previously, this restriction is also problematic for mixing > and/or switching diverse media sources in streaming and conversational > applications. > > Consider a conference bridging application, where at least one party > is a land-line circuit (which requires 8 KHz sampling) and at least > one other party is a wideband VMR-WB terminal (which may employ 16 KHz > sampling). Conference bridging for these media streams requires > switching and/or mixing the input streams into like output streams. > According to your restricted method, use of the VMR-WB sample rate > adaptation function for this application requires end-to-end session > renegotiation (eg, an SDP offer-answer cycle for each leg) in order to > achieve a common sampling rate, and hence timestamp interval, for all > RTP terminations involved in the conference bridge. I would have thought the conference bridge could act as an RTP translator, and resample as appropriate for some participants? > Additional latencies and synchronization complexities associated with > end-to-end renegotiation of the sampling rate for all RTP terminations > should not be required to establish and maintain the bridge in such > applications. Colin _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] VMR-WB RTP Payload and Storage Formats sassan.ahmadi
- [AVT] VMR-WB RTP Payload and Storage Formats sassan.ahmadi
- [AVT] Re: VMR-WB RTP Payload and Storage Formats Colin Perkins
- Re: [AVT] VMR-WB RTP Payload and Storage Formats Randell Jesup
- RE: [AVT] Re: VMR-WB RTP Payload and Storage Form… Scribano Gino-QA1087
- Re: [AVT] Re: VMR-WB RTP Payload and Storage Form… Colin Perkins
- Re: [AVT] Re: VMR-WB RTP Payload and Storage Form… Qiaobing Xie
- Re: [AVT] Re: VMR-WB RTP Payload and Storage Form… Colin Perkins