Re: [AVT] Syncronization of co-located clients?

Stephen Casner <casner@acm.org> Sun, 03 July 2005 23:22 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpDnS-0005O3-0Y; Sun, 03 Jul 2005 19:22:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpDnQ-0005Nt-1X for avt@megatron.ietf.org; Sun, 03 Jul 2005 19:22:44 -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 TAA23829 for <avt@ietf.org>; Sun, 3 Jul 2005 19:22:41 -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 1DpEDs-0000Zj-LQ for avt@ietf.org; Sun, 03 Jul 2005 19:50:05 -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 j63NMOa2048632; Sun, 3 Jul 2005 16:22:24 -0700 (PDT) (envelope-from casner@acm.org)
Date: Sun, 03 Jul 2005 16:21:58 -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.0507031200380.20914@hawaii.herlein.com>
Message-ID: <20050703161251.N9967@oak.packetdesign.com>
References: <Pine.LNX.4.61.0507022110250.14450@hawaii.herlein.com> <20050703105831.L9967@oak.packetdesign.com> <Pine.LNX.4.61.0507031200380.20914@hawaii.herlein.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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 Sun, 3 Jul 2005, Greg Herlein wrote:

> I found this as well - might provide a mechanism for sync based
> on SMPTE time code:
>
> http://www.ietf.org/internet-drafts/draft-singer-smpte-rtp-01.txt
>
> Assuming all clients controlled the playout buffer using the
> SMPTE time code, this could likely do it.  My particular
> application is on a local LAN (a controlled VLAN actually) so I
> am not expecting the network to present significant problems.

I don't think the SMPTE timecodes help unless they are representing an
absolute time in the future, where the sender has made a prediction
about the amount of time needed for propagation to all receivers and
buffering time within each receiver.  That might work in a controlled
LAN environment, but it is not a general solution.

The BBN Synchronization Protocol that I mentioned is based on using
synchronized clocks at the receivers (e.g., using NTP).  Each receiver
relates its earliest possible playout time for a media timestamp to
real time, and communicates that back to the controller.  The
controller finds the latest of these times and informs all the
receives so they can choose the same playout time.  There's more to it
than that, of course.  Sync "epochs" were used to deal with media
clock drifts, etc.

[I state the above without having read the paper in a long time.  I
seem to remember a centralized controller, but it could be done in a
distributed manner as well.]

                                                        -- Steve

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