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

<skillzero@gmail.com> Sun, 03 July 2005 23:08 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpDZZ-000390-K2; Sun, 03 Jul 2005 19:08:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpDZY-00038v-FU for avt@megatron.ietf.org; Sun, 03 Jul 2005 19:08:24 -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 TAA22799 for <avt@ietf.org>; Sun, 3 Jul 2005 19:08:21 -0400 (EDT)
Received: from wproxy.gmail.com ([64.233.184.202]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DpE00-0007to-7W for avt@ietf.org; Sun, 03 Jul 2005 19:35:45 -0400
Received: by wproxy.gmail.com with SMTP id i6so612615wra for <avt@ietf.org>; Sun, 03 Jul 2005 16:08:14 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GGkCy2rq9a+uLUDuXvzK1csYk+bFHvNlQiwrLIei5c3VV+EbOGcFUi5Qgwd0y9uggQZtS/v1Rt9H0VjSiHJjnwF4SMpwc7RzXojNFPTNKn9vDYiE5wPK3bn+Wh17VBisf1FZWfNLCK14bppdCNxRVYX+SAIwOboLCEYKZMA3IL8=
Received: by 10.54.11.25 with SMTP id 25mr3187522wrk; Sun, 03 Jul 2005 16:08:14 -0700 (PDT)
Received: by 10.54.63.20 with HTTP; Sun, 3 Jul 2005 16:08:13 -0700 (PDT)
Message-ID: <2729632a05070316087858205d@mail.gmail.com>
Date: Sun, 03 Jul 2005 16:08:14 -0700
From: skillzero@gmail.com
To: avt@ietf.org
Subject: Re: [AVT] Syncronization of co-located clients?
In-Reply-To: <Pine.LNX.4.61.0507022110250.14450@hawaii.herlein.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <Pine.LNX.4.61.0507022110250.14450@hawaii.herlein.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: quoted-printable
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: skillzero@gmail.com
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 7/2/05, Greg Herlein <gherlein@herlein.com> 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 may be oversimplifying your problem, but have you looked into using
the NTP and RTP timestamp information in RTCP sender/receiver reports
to synchronize? These RTCP reports allow you to determine the relative
offset of each client to the reference clock of the sender. Using
this, each client can adjust its playout delay to play at an absolute
time that is the same as the other clients.

I'm certainly not an expert, but this is what I am doing to play an
RTP audio stream in sync to multiple clients within audible range of
each other. What I found helpful is the book "RTP: Audio and Video for
the Internet" by Colin Perkins (ISBN 0-672-32248-8). The chapter on
Lip Synchronization describes the process of syncing streams using
RTCP reports.

It would be great to hear about other techniques, experiences, and
reading material.

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