TitleFactory can not only create subtitle images based on unformatted text files, but also based upon files which already contain subtitle text with associated timecodes (or frame counts).
Definitions
TitleFactory provides a unique method for specifying the format of timecoded subtitle text files. These are files which already contain timecodes and text. The use of timecoded textfiles provides a nice way to create subtitle image files when the timecodes are already known. The timecoded subtitle files may be the product of TitleFactory or another program or service. They may be translated files or the original files.
With the definitions TitleFactory can support a wide variety of timecode formats too numerous to list here. It can literally support thousands of formats. However, there are always special cases, that it won't be able to support. One example is where the starting and ending timecodes appear on different input lines.
While there may be timecoded subtitle files that cannot be defined with the TimeCoded Subtitle File Definitions window, it is meant to understand most formats. The text at the bottom of the window shows an example of the file with the definitions provided. This is an example only. TitleFactory is actually more forgiving than what is shown in many cases. For example, TitleFactory does not need the Timecodes to start in position 1 of the input record although it does expect that the staring code will come before the ending code. TitleFactory is delivered with several sample timcoded textfiles, their definitions, and projects that use them.
When TitleFactory reads a timecoded text file it will uses the definitions provided to parse it. Most of the parameters are taken quite literally, such as the timecode format itself.
The Timcoded formats that are delivered (named TitleFactory and SRT) cannot be edited, however, they can be copied (using the 'Create a New Definition' button).
TitleFactory uses the definitions contained in the tc_definitions.txt file, located in the TitleFactory program directory to parse the text. TitleFactory does allow the definitions to be saved in other files, however, using the 'Save' button. However, as previously stated only the definitions in the tc_definitions.txt file will be used.
Timecode File format
Name of the format.
Group Delimiter 1
Defines a line, if any, that indicates the start of a new subtitle with its codes.
Group Delimiter 1
Defines a line, if any, that indicates when a subtitle with its codes, has ended.
Base Format
Specifies that the codes are timecodes or a frame count.
Brackets around codes
Defines the type of brackets surround the codes, if any.
Frames Digit Count
Specifies (for 'frames count Base format), the number of digits that are used.
The following are for timecode base formats:
Hours, Mins, Secs format
Defines the length of these timecode fields.
Hours, Mins, Secs Delimiter
Defines the character that separates these codes, if any.
Frames Delimiter
Defines the character between the seconds field and the frames field.
Frame Format
FPS (frames per second), 1/10, 1/100, or 1/100 of a second format.
Delimiter Between Timecodes: defines a set of characters, if any, that separate the starting timecode from the ending timecode associated with the subtitle text.
Subtitles are on the Same Line as the Timecode: Yes or No.
If Subtitles are on the Same Line as the Timecode is 'yes' then the last two parameters apply.
Delimiter between codes and text: Defines the characters, if any between codes and text. TitleFactory will remove these characters if found.
Delimiter between Text Lines: Defines the characters, if any between lines of subtitle text. TitleFactory will remove these characters if found.
|
Copyright © 2002-2009 . All rights reserved. |