A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "Timed track formats"

From WHATWG Wiki
Jump to: navigation, search
Line 11: Line 11:
  
 
Uses frames for timings.
 
Uses frames for timings.
 +
 +
== CIP (.cip) ==
 +
 +
Couldn't find a specification for this format.
  
 
== DKS (.dks) ==
 
== DKS (.dks) ==
Line 26: Line 30:
 
Simple format. Uses '<P>' for line breaks. Uses tabs as a deliminator in one version, spaces and commas in another.
 
Simple format. Uses '<P>' for line breaks. Uses tabs as a deliminator in one version, spaces and commas in another.
  
== EBU STL ==
+
== EBU STL (.ebu) ==
  
 
Couldn't find a specification for this format.
 
Couldn't find a specification for this format.
Line 193: Line 197:
  
 
Still to be investigated:
 
Still to be investigated:
*.PAC
 
*.RAC
 
 
*.CHK
 
*.CHK
 
*.AYA
 
*.AYA
*.890
 
*.CIP
 
 
*.CA
 
*.CA
 
*.ULT
 
*.ULT
Line 207: Line 207:
 
*.ST7
 
*.ST7
 
*.TIT
 
*.TIT
*.STL
 

Revision as of 01:05, 1 May 2010

Part of the work on Timed tracks.

Requirements:

  • We need to use time for timings, not frames, because the same file might apply to multiple versions of the same video, with different frame rates.
  • For a similar reason, any positioning needs to be relative to the frame, not absolute (in pixels)

(Extensions marked * below are shared by multiple formats.)

AQTitle (.aqt)

Uses frames for timings.

CIP (.cip)

Couldn't find a specification for this format.

DKS (.dks)

Probably too simple to be useful. Doesn't seem to support overlapping times. Uses "[br]" for line breaks. Unclear how easy it would be to extend usefully without effectively making a completely new format.

DVD Studio Pro

Simple format. Uses '<P>' for line breaks. Uses tabs as a deliminator in one version, spaces and commas in another.

EBU STL (.ebu)

Couldn't find a specification for this format.

FAB Subtitler

Simple format. Uses real line breaks. Could be extended usefully.

JACOSub (.jss)

Pretty complicated. Uses "\n" for line breaks.

Kate

Binary format with text components, making it hard to hand-edit. The text components seem pretty verbose.

MacSUB

Uses frames for timings. Uses real line breaks.

MicroDVD (.sub*)

Uses frames for timings. Uses "|" for line breaks.

(Appears to be basically the PowerDivX format, but using frames instead of seconds.)

MPEG-4 Timed Text (.ttxt)

Pretty complicated. Seems to be formatting-centric. Has some pixel-based positioning. Difficult to hand-edit. Uses strings delimited by apostrophes to mark line breaks.

MPL (.mpl)

Uses frames for timings in the first version; decaseconds in the second version. Simple format. Uses "|" for line breaks.

MPSub (.sub*)

Relative timings, which can be hard to hand-edit correctly. Uses real line breaks. Could be extended, though most useful extensions would not be backwards-compatible (e.g. adding a new timing format).

Ogg Writ

Binary format, nigh on impossible to hand-edit.

Phoenix Subtitle (.pjs)

Uses frames for timings. Has some weird rules relating to displaying multiple subtitles at once.

PowerDivX (.psb)

Currently has low resolution timings. Uses "|" for line breaks. Simple format. Could be extended usefully.

(Appears to be basically the MicroDVD format, but using seconds instead of frames.)

PU2000 (.rac, .pac)

Couldn't find a specification for this format or it's later version PU2020. Appears to be a binary format.

RealText (.rt)

Supports a number of features that aren't necessary. Uses "<br/>" for line breaks. Could probably be used as the basis for a new similar format.

SAMI (.smi)

Probably has complicated legacy parsing requirements. Uses "<BR>" for line breaks. Would be difficult to extend in a backwards-compatible way.

Spruce STL

Couldn't find a specification for this format.

Structured Subtitle Format (.ssf)

Ludicrously verbose. Not a good format for hand-editing. Uses "\n" for line breaks.

SubRip (.srt)

Currently has pixel-based positioning. Simple format. Uses real line breaks. Could be extended usefully.

Subsonic

Unclear format ("~:"?).

Gloss Subtitle (.gsub)

Couldn't find any information on this format.

smilText

Pretty complicated. Seems to be formatting-centric. Has some pixel-based positioning. Difficult to hand-edit.

SubStation Alpha (.ssa)

Pretty verbose. Has some pixel-based positioning. Uses "\N" for line breaks (though this is somewhat configurable). Has some rather subtle syntax of the kind that typically results in buggy implementations. (Indeed, see the "note" in [1].)

A later version called Advanced SubStation Alpha (.ass) is even more complicated.

SubViewer (.sub*)

Either uses "[br]" for line breaks, "|" for line breaks, or real line breaks, depending on the version. Making a backwards-compatible parser would likely require more effort than for most other formats.

TTML

Pretty complicated. Seems to be formatting-centric. Has some pixel-based positioning. Difficult to hand-edit.

Turbotitler

Unclear format ("NTP"?). Uses "|" for line breaks.

Universal Subtitle Format (.usf)

Extremely verbose. Uses "<br/>" for line breaks. Not a good format for hand-editing.

VPlayer

Supports several different syntaxes. Doesn't seem to support overlapping times in the time-based modes (though apparently it does in the frame-based modes). Uses "|" for line breaks.

XombieSub

Apparently similar to SubStation Alpha. Couldn't find any concrete information.

ZeroG

Unclear format.

Other formats

CVD, DVB subtitles, SVCD, VobSub (.sub and .idx), and XSUB (DivX subtitles) are not listed as they appear to be image-based formats.

CMML and SMIL are not listed above since they don't appear to be subtitle formats so much as timed media mixing formats.

Still to be investigated:

  • .CHK
  • .AYA
  • .CA
  • .ULT
  • .USF
  • .CIN
  • .L32
  • .ST4
  • .ST7
  • .TIT