Re: [AVT] Syncronization of co-located clients?
Stephen Casner <casner@acm.org> Sun, 03 July 2005 18:02 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dp8n6-0001ps-Rp; Sun, 03 Jul 2005 14:02:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dp8n4-0001pn-Ia for avt@megatron.ietf.org; Sun, 03 Jul 2005 14:02:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22733 for <avt@ietf.org>; Sun, 3 Jul 2005 14:02:01 -0400 (EDT)
Received: from dns.packetdesign.com ([65.192.41.10] helo=mailman.packetdesign.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dp9DT-0002Rt-GU for avt@ietf.org; Sun, 03 Jul 2005 14:29:20 -0400
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254]) by mailman.packetdesign.com (8.12.8/8.12.8) with ESMTP id j63I1Za2043536; Sun, 3 Jul 2005 11:01:36 -0700 (PDT) (envelope-from casner@acm.org)
Date: Sun, 03 Jul 2005 11:01:32 -0700
From: Stephen Casner <casner@acm.org>
To: Greg Herlein <gherlein@herlein.com>
Subject: Re: [AVT] Syncronization of co-located clients?
In-Reply-To: <Pine.LNX.4.61.0507022110250.14450@hawaii.herlein.com>
Message-ID: <20050703105831.L9967@oak.packetdesign.com>
References: <Pine.LNX.4.61.0507022110250.14450@hawaii.herlein.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: 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
On Sat, 2 Jul 2005, Greg Herlein wrote:
> I've got a scenario where I need to multicast RTP streams to
> multiple clients, and some of those may be within visual (and
> worse, audible) range of another client.
>
> Is there a profile or other trick to help ensure syncronization
> *between* the clients? In other words, ensure that the
> presentation of the material from one client is in sync with the
> others nearby?
>
> I have some approaches to this, and have been hunting for other
> ideas.
>
> Any links, references, research papers - whatever - would be
> appreciated.
The following paper describes a nice synchronization protocol
developed by Julio Escobar and colleagues at BBN which allows
specifying the synchronization goals and dynamically determining the
offsets needed to achieve sync:
Julio Escobar, Craig Partridge, Debra Deutsch, "Flow
Synchronization Protocol" IEEE/ACM Transactions on Networking,
Vol.2, No. 2, pp.111-121, April 1994.
This may be more academic than you want; it defines a synchronization
model and what information needs to be communicated, rather than
providing a detailed protocol specification. This protocol was
discussed in AVT for a while to consider whether RTP itself needed any
changes to support more general synchronization, but we concluded that
it did not.
This synchronization protocol was used in a demonstration of
distributed music performance that I helped implement at the ACM
Multimedia Conference 1994. The music was a Haydn trio performed from
three different locations across the country. Since only two
performers were available, one part was recorded. That part was
transmitted over the network and played out simultaneously at the two
other locations. The two live performers played their parts along
with that first one, not hearing each other. All three parts were
multicast to multiple receivers, each of which synchronized the three
streams to play out the trio in unison. The synchronization was
achieved through the timestamps on the media packets in combination
with delay offsets calculated by the synchronization protocol.
The synchronization goal for this demo is different from yours, but
the protocol is general. You may find that you need to implement
something specific for your application, and this paper will give you
the theory behind it so you know what information needs to be
communicated where.
-- Steve
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Syncronization of co-located clients? Greg Herlein
- Re: [AVT] Syncronization of co-located clients? Stephen Casner
- Re: [AVT] Syncronization of co-located clients? Greg Herlein
- Re: [AVT] Syncronization of co-located clients? Chuck Harrison
- Re: [AVT] Syncronization of co-located clients? Stephen Casner
- Re: [AVT] Syncronization of co-located clients? skillzero
- [AVT] Re: Syncronization of co-located clients? lazzaro
- Re: [AVT] Syncronization of co-located clients? lazzaro