[AVT] Carrying SMPTE TimeCode in RTP

Dave Singer <singer@apple.com> Thu, 02 March 2006 00:45 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEbwC-0007Jl-BS; Wed, 01 Mar 2006 19:45:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEbwA-0007JU-Vs for avt@ietf.org; Wed, 01 Mar 2006 19:44:58 -0500
Received: from mail-out4.apple.com ([17.254.13.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEbw9-0000pa-JN for avt@ietf.org; Wed, 01 Mar 2006 19:44:58 -0500
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id k220iuPj009276 for <avt@ietf.org>; Wed, 1 Mar 2006 16:44:56 -0800 (PST)
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52]) by relay5.apple.com (Apple SCV relay) with ESMTP id C03D8324017 for <avt@ietf.org>; Wed, 1 Mar 2006 16:44:49 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06230922c02bee60237b@[17.202.35.52]>
In-Reply-To: <p06230944c02267cd005a@[17.202.35.52]>
References: <E1F7LY1-0001Xu-UP@newodin.ietf.org> <p06230944c02267cd005a@[17.202.35.52]>
Date: Wed, 01 Mar 2006 16:42:21 -0800
To: avt@ietf.org
From: Dave Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Subject: [AVT] Carrying SMPTE TimeCode in RTP
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>
Errors-To: avt-bounces@ietf.org

Answering my own email here, I'm assuming that the answer is yes to 
the 2nd question.

The extra bits in an 8-byte SMPTE time-code can be used to
a) maintain the polarity of the code (numbers of 1s and 0s)
b) indicate the relationship of the codes to color fields
c) indicate whether it's drop-frame coding
d) and then do one of
    i) carry 4 characters more
    ii) carry a date and time-zone indication (SMPTE 309M)
    iii) carry some general SMPTE 262M data (control codes, text, 
production info etc.)

I don't believe we need color and polarity handling in RTP.
We have drop-frame in the signalling.

If we want to carry something as slowly-changing as a date or as 
unchanging as a time-zone, I on't believe that embedding it here is 
right.  Certainly thought should be applied before blindly applying 
it.  If a date is needed, it's not needed inline;  at most it would 
be in RTCP, and then I would argue for a new RTCP packet type to 
carry it.

The other two possibilities are 'general meta-data' and should not be 
sub-embedded in a time-code, in RTP, but elevated and properly 
labelled at the stream level.

So, my answer is no, we do not need the full 8-byte SMPTE time-code.

On the other open question, it's a question of taste.  I prefer it 
this way but I'm not pedantic.



At 11:13  -0800 22/02/06, Dave Singer wrote:
>In this I-D, there are still a couple of open questions.  I'm 
>wondering if any on the list can indicate their preferences, or 
>whether the editor should make his best guess.
>
>Would people like more background info (e.g. the 6 flag bits and 8 
>4-bit binary groups documentation)?
>
>* * * * *
>
>
>Open question: should we normally compute framespersecond from frameduration?
>
>Open question: should we allow for a full 8-byte SMPTE time-code 
>formatted exactly as in SMPTE 12M? We are currently missing the 6 
>flag bits and the 8 4-bit binary groups.
>
>--
>David Singer
>Apple Computer/QuickTime
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt


-- 
David Singer
Apple Computer/QuickTime

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