RE: [AVT] 3GPP timed text draft: more generic?

"Jose Rey" <rey@panasonic.de> Wed, 20 August 2003 12:35 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06480 for <avt-archive@odin.ietf.org>; Wed, 20 Aug 2003 08:35:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19pSB7-0002BG-6F for avt-archive@odin.ietf.org; Wed, 20 Aug 2003 08:35:05 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7KCZ5mR008376 for avt-archive@odin.ietf.org; Wed, 20 Aug 2003 08:35:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19pSB4-0002AF-HV; Wed, 20 Aug 2003 08:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19pSAB-000219-TI for avt@optimus.ietf.org; Wed, 20 Aug 2003 08:34:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06406 for <avt@ietf.org>; Wed, 20 Aug 2003 08:34:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19pSAA-0000Fl-00 for avt@ietf.org; Wed, 20 Aug 2003 08:34:06 -0400
Received: from mail.pel.panasonic.de ([194.162.191.12]) by ietf-mx with esmtp (Exim 4.12) id 19pSA9-0000Fi-00 for avt@ietf.org; Wed, 20 Aug 2003 08:34:05 -0400
Received: from atrgreyj ([10.78.238.55]) by mail.pel.panasonic.de with Microsoft SMTPSVC(5.0.2195.6713); Wed, 20 Aug 2003 14:34:01 +0200
From: Jose Rey <rey@panasonic.de>
To: Colin Perkins <csp@csperkins.org>
Cc: avt@ietf.org
Subject: RE: [AVT] 3GPP timed text draft: more generic?
Date: Wed, 20 Aug 2003 14:34:00 +0200
Message-ID: <NGBBJIBNJOKHDHFKEOMHEELLFCAA.rey@panasonic.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To: <EFE5C849-CBE2-11D7-B8F1-000A957FC5F2@csperkins.org>
X-Message-Flag: Follow up
X-OriginalArrivalTime: 20 Aug 2003 12:34:01.0172 (UTC) FILETIME=[556E8140:01C36717]
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi Colin, all,


> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]
> Sent: Monday, August 11, 2003 12:03 PM
> To: Jose Rey
> Cc: avt@ietf.org
> Subject: Re: [AVT] 3GPP timed text draft: more generic?
>
>
> On Monday, Aug 11, 2003, at 09:15 Europe/London, Jose Rey wrote:
> > Colin Perkins wrote:
> >> A specific payload format for 3GPP timed text might be
> >> appropriate, but I
> >> would like to understand the options and alternatives before
> >> we make that
> >> choice. Is 3GPP the only body doing timed and/or decorated
> >> text? If not,
> >> what are the alternatives, and how do they relate?
> >>
> >> --
> >
> > at the moment there are at least two more standardisation bodies
> > interested in timed text: MPEG and W3C.
> >
> > - MPEG is currently defining their own TT format based on
> 3GPP TT (see
> > Committee Draft of ISO/IEC 14496-17 from July'03 Meeting in
> Trondheim)
> > by defining the access unit structure, the stream type, the
> object type
> > indication and decoder specific info of the timed text samples. The
> > definition of these items enables the transport over RTP using the
> > mpeg4simple draft. The work in MPEG is assumed to be
> finalised around
> > July 2004.
> >
> > - W3C is at a very early stage in defining a timed text authoring
> > format. It has recently (May'03) published a draft for use
> cases and
> > requirements of a timed text authoring format:
> > http://www.w3.org/TR/2003/WD-tt-af-1-0-req-20030515/. This
> draft has a
> > rather long list of requirements and lists many
> functionalities. In my
> > understanding W3C targets to a generic format with rich
> functionality.
> > I
> > don't know how quick it may develop (anyone?).
>
> I believe SMPTE may also have timed text work in their Digital Cinema
> group?
>

Yes, there is a DC28.2W Subtitles and Captions Adhoc Group in SMPTE
dealing with a stream timed text format. I've checked the website and as
far as I understand from the available documents they intend to develop
a media format to stream text encoded as MNG (Multi-image Network
Graphics) images. On April'02 they were still working on a requirements
document for the stream text format but no output has been published
until today, at least publicly.

Question to the group: is anyone aware of the progress of this item?

thanks,

Jose



> > None of these above is an option for us, because 1) the
> only timed text
> > format in 3GPP is 3GPP timed text 2) 3GPP has not adopted the
> > mpeg4simple for
> > transport and 3) for this 3GPP timed text format we need an
> RTP payload
> > format within the current 3GPP Release 6 schedule (i.e. March'04).
>
> I agree that using the MPEG4-simple format doesn't make
> sense, and that
> the W3C schedule looks to be too long for 3GPP requirements.
>
> --
> Colin Perkins
> http://csperkins.org/
>


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