Frame Rate and Timecode

<< Click to Display Table of Contents >>

Navigation:  Batch conversions and automation > Metadata pass-through >

Frame Rate and Timecode

Utilizing the original frame rate and timecode format of the source file can be extremely helpful as it reduces the number of Watch Folders or Command Line configurations needed in the day-to-day operations. Now, a single Watch Folder or the same Command Line configuration can effectively be used for conversions of files intended and created for different frame rates.

The process is quite simple:

1. Set the Frame Rate parameter in the Watch Folder or the .cfg configuration file to <from_source>.

Note: Please refer to the topics dedicated to configuring Watch Folder or doing the conversion with the Command Line tool for the details.

2. If the source file doesn't contain information about the frame rate, the conversion will be canceled and the appropriate message will be output in Watch Folder's error log or in the Command Line console (error stream).

3. If the source file has information about the frame rate but not about the timecode format (drop or non-drop), the timecode format selected in Watch Folder's/Command Line configuration will be used instead.

4. If the source file contains both the frame rate and timecode format , the conversion will be initiated and the output will be converted in the same frame rate /timecode format as the frame rate of the source file.

For your convenience, we compiled a list of the subtitling formats supporting those parameters.

Formats supporting Frame Rate and Timecode Format

Our proprietary EZT and EZTXML formats

Plain ASCII (.txt) created by EZTitles and exported with the File Header option turned on

RTF, Doc or DocX created by EZTitles and exported with the File Header option turned on

TTML ver.1 and TTML ver.2 when timeBase="SMPTE"

EBU-TT and EBU-TT ver. 1.1 when timeBase="SMPTE"

EBU-TT ver.1.0 BBC

Netflix Timed Text when timeBase="SMPTE". The only exception is Netflix-TT file in Japanese as these are IMSC compliant and as such the timeBase parameter is always set as "Media"

Apple iTunes Timed Text

Final Cut Pro XML (FCP7 and FCPX)

MCC

Formats supporting only Frame Rate

DCDM SMPTE 428-7-2007 XML

TTML ver.1 and TTML ver.2 when timeBase="Media"

EBU-TT and EBU-TT ver. 1.1 when timeBase="Media"

IMSC ver. 1 and IMSC ver.1.1

EBU-TT-D and EBU-TT-D BBC

SMPTE-TT Subtitles

Netflix Timed Text when timeBase="Media". Netflix-TT files in Japanese are IMSC compliant and such timeBase is always set to "Media" for them

Disney IMSC 1.1

OOYALA Timed Text

Formats limited to work with certain frame rates only

EBU STL & EBU for Arte -limited by the original specifications for use with materials in 25fps and 29.97fps only. With a custom-made change EBU STL do also support 24fps.

890 - limited to 23.976fps, 25fps and 29.97fps.

Softitler TXT - limited to 25fps and 29.97fps