MatroskaWebVTT - Revision history

Rillian: Link to the google draft

2012-01-29T19:12:01Z

Link to the google draft

← Older revision		Revision as of 19:12, 29 January 2012
Line 1:		Line 1:
			See also the [[https://docs.google.com/document/d/1-tVXd1mRlWNvZrdIkLAJEp5xt3gDVDwfVubyUm9oNJ4/edit Google proposal]].

	== '''DRAFT''' ==		== '''DRAFT''' ==

Rillian: /* DRAFT */ specify track type, although it's obvious

2012-01-27T23:47:21Z

DRAFT: specify track type, although it's obvious

← Older revision		Revision as of 23:47, 27 January 2012
Line 6:		Line 6:

	- CodecID is S_WEBVTT		- CodecID is S_WEBVTT
			- TrackType is 0x11 subtitle
	- File-header metadata, if any, is included verbatim in CodecPrivate		- File-header metadata, if any, is included verbatim in CodecPrivate
	- cue text/payload is included verbatim in the Block data		- cue text/payload is included verbatim in the Block data

Rillian: /* DRAFT */ chapters should be chapters, not subtitles.

2012-01-27T23:46:44Z

DRAFT: chapters should be chapters, not subtitles.

← Older revision		Revision as of 23:46, 27 January 2012
Line 11:		Line 11:

	The sequence number and presentation attributes from the cue header are not represented.		The sequence number and presentation attributes from the cue header are not represented.

			The 'Chapters' kind of WebVTT file should be translated in to the equivalent Matroska element for marking chapters. Both formats allow the same hierarchical/overlapping options, so this should be an equivalent representation.

	=== Questions ===		=== Questions ===

Rillian: /* Questions */ what to do about kind and lang

2012-01-27T23:44:19Z

Questions: what to do about kind and lang

← Older revision		Revision as of 23:44, 27 January 2012
Line 13:		Line 13:

	=== Questions ===		=== Questions ===

			We need some way to signal the 'kind' attribute from the html5 embedding. That is, whether a give track is subtitles, captions, description, or metadata. Use per-track Tag elements? Likewise for 'srclang'.

	It would be nice to represent the presentation attributes. How do to that?		It would be nice to represent the presentation attributes. How do to that?

	Would be be easier to embed the complete cue as is? The parser has to handle this from javascript. The Matroska subtitle guidelines recommend against including the cue timings in the packet data because it makes it harder to edit the file.		Would be be easier to embed the complete cue as is? The parser has to handle this from javascript. The Matroska subtitle guidelines recommend against including the cue timings in the packet data because it makes it harder to edit the file.

Rillian: /* DRAFT */ 'cue text' is 'cue payload' for metadata tracks

2012-01-27T23:40:09Z

DRAFT: 'cue text' is 'cue payload' for metadata tracks

← Older revision		Revision as of 23:40, 27 January 2012
Line 7:		Line 7:
	- CodecID is S_WEBVTT		- CodecID is S_WEBVTT
	- File-header metadata, if any, is included verbatim in CodecPrivate		- File-header metadata, if any, is included verbatim in CodecPrivate
	- cue text is included verbatim in the Block data		- cue text/payload is included verbatim in the Block data
	- timestamp and BlockDuration as set from the cue timestamps		- timestamp and BlockDuration as set from the cue timestamps

Rillian: /* Questions */ webvtt uses the term 'cue timings'

2012-01-27T23:36:45Z

Questions: webvtt uses the term 'cue timings'

← Older revision		Revision as of 23:36, 27 January 2012
Line 16:		Line 16:
	It would be nice to represent the presentation attributes. How do to that?		It would be nice to represent the presentation attributes. How do to that?

	Would be be easier to embed the complete cue as is? The parser has to handle this from javascript. The Matroska subtitle guidelines recommend against ~~this~~ because it makes it harder to edit the file.		Would be be easier to embed the complete cue as is? The parser has to handle this from javascript. The Matroska subtitle guidelines recommend against including the cue timings in the packet data because it makes it harder to edit the file.

Rillian: draft ideas for Matroska encapsulation of WebVTT

2012-01-27T23:35:20Z

draft ideas for Matroska encapsulation of WebVTT

New page

== '''DRAFT''' ==

[[http://dev.w3.org/html5/webvtt/ WebVTT]] is a subtitle/text track format developed for the HTML5 media element and related applications. This is a proposal for how to encapsulate such tracks in the Matroska/WebM container.

WebVTT is based on the .srt format, effectively the simplest text track format is use, so we can make use of the [[http://matroska.org/technical/specs/subtitles/srt.html Matroska mapping for SRT]] as a starting point.

- CodecID is S_WEBVTT
- File-header metadata, if any, is included verbatim in CodecPrivate
- cue text is included verbatim in the Block data
- timestamp and BlockDuration as set from the cue timestamps

The sequence number and presentation attributes from the cue header are not represented.

=== Questions ===

It would be nice to represent the presentation attributes. How do to that?

Would be be easier to embed the complete cue as is? The parser has to handle this from javascript. The Matroska subtitle guidelines recommend against this because it makes it harder to edit the file.