Additional YouTube/Google formats (10.5/10.6 version)
DFXP import/export support (10.5/10.6 version)
Final Cut Server Annotation import (10.5/10.6 version)
Blue Ray XML import (10.5/10.6 version)
DLP Cinema import/export support - now included for free (10.5/10.6 version)
Structured Subtitle import/export support
Sonic text import/export support
Cinevation import/export support (10.5/10.6 version)
Continous Timed Title import support (10.5/10.6 version)
For more news see version description

You get a great subtitle generator for free!
New Price: since the raising amount of support, I had to raise the price of the Pro version of TitleExchange to 185 Euro by the end of 2009.
I think it is worth the money, if you consider the time savings you will get. Quote from a customer: ... I was able to to add 5 languages to my sequence in less than half an hour ... (Note: each track had about 1000 titles).

A TitleExchange intro:

Though the actual process of converting files is both simple and fast - the options on how to set up the conversion will be a bit more complicated -- maybe.

TitleExchange shows up with a tiny little window which displays the "which to what" conversion.


You can either click on the "in text" or the "out text" or press "cmd-," to go to the conversion preferences where you can change source and destination formats and modify the destination format options.

What do the available options mean?

Some of the target formats are not yet implemented or released in the current version -- so they are greyed out.

Target file formats
The output file formats in some cases do allow special settings. These might be more or less complicated.
Most of these format are plain text files. So little changes can be done easily with TextEdit or another text editor like TextWrangler or BBEedit when you are working with right to left written titles.

Final Cut Pro XML as target format
STL/QTtext as target format
SubBits as target format
DS Caption as target format
DLP Cinema XML as target format
Adobe Encore as target format
SubRip SRT as target format
Belle Nuit as target format
Structured Subtitles as target format
Cavena MTL as target format
SubViewer SUB as target format
SubStation Alpha as target format
SCC as target format
DFXP as target format

"XML" as target

This allows a setup of how an exported XML will look like later.
There are little help buttons which will give you a quick explanation on what this setting will change or cause.

You can setup what "text generator" to use.
If you don't choose a pre-defined template the application will ask you for one. To create either a temporay generator template or a stationary to have to do some setup within Final Cut Pro.
Here in short how to do:
• Within Final Cut Pro create a new sequence with the settings of your choice.
• Select the generator of your choice (see supported generators) and do the setup -- you can also add filters and motion settings.
• Drag it to the sequence.
• Then in the browser select the sequence and export as XML -- it might be a good idea to create a shortcut for that within Final Cut Pro.
Instead of creating a new sequence you also can use an existent one which includes your "favorite" generator first place. This means if you got many generators and many tracks in there, the application will take the first found one of the first found track which includes a generator.
The sequence settings and especially the timebase will be used with the later conversion!

How to create and save a stationary generator template?
In Final Cut Pro do as above. With TitleExchange choose the menu "Tools -> Final Cut Pro XML Templates -> Import Final Cut Pro XML as Template..." or press "ctrl-opt-T". This will ask for a XML file to import and analyze.

The resulting panel will give you all the basic information about both the generator and the sequence. The "Template Name" text field will suggest a name which can be changed by the user. The save button will direct to TitleExchange's "Template directory" by default -- you shouldn't change unless you know why.
It might happen that one or more of the generator options include a "n.a". This means that the generator doesn't support this kind of option or is not setup correctly. TitleExchange supports virtually any kind of text generators and it comes with a basic setup which includes a data base of most of the actual text generators known (see supported generators). The database doesn't include all the "Motion Templates" which come with Final Cut Studio. You can easily modify or add those (or any other) by updating the data base.

Next step would be to setup the generators behavior in the sequence.
You can decide whether it will use fades or not. The fades currently are standard "Dissolves". You got the choice to create fixed fades or fades which are set by the source (currently only STL text and XML are supported).
Now you may want to setup a way how your subtitles look regarding the font settings and the alignment. This will work with some kind of XML files that include the subtitles as generators, some STL text files and partially with DVDSP "track items". QTtext will follow later.
In any case you have to make sure that the generator (template) does support those settings -- if not, all or some of these settings will be ignored.



Set up the XML saving and handling
You can use just a standard creation of an XML (compatible was any version of Final Cut Pro) or an extended XML (compatible with Final Cut Pro 5.1.4 and higher) by un-checking/checking the "XML Import Options". If you check this option there will be further options.

The way Final Cut Pro imports the XML can be setup by the following options

"STL Text/QTtext" as target

This allows a setup of how an exported STL or QTtext file will look like later.
There are little help buttons which will give you a quick explanation on what this setting will change or cause.

"Use Sequence XML Start TC": if this box is checked the STL/QTtext will use the actual timecodes instead of zero-based timecodes. An example a sequence starts with "10:00:00:00". TitleExchange by default will take the 10 hours as "offset" and subtract it from each subtitle timecode.
"Create Smile File": this will create a little XML which links both to a movie and the QTtext file. This way caption data can be stored outside the movie. The Smile file will appear as a normal QuickTime movie - though it references to several files.

You can decide whether to use fades or not. You got the choice to create fixed fades or fades which are set by the source (currently only STL text is supported).
You also may want to setup how your subtitles look regarding the font settings and the alignment. You can choose either "Source" or "User". Currently only XML generators will support the "Source" option. This would for example allow to extract font style from a generator and use it with the STL. QTtext will follow later.

"SubBits" as target
SubBits is nice application from Edit B which allows to spot subtitles and export those to various formats. Though the format is text based, it's bit more complicated to change in a text editor
In general subtitles normally only support 2-line subtitles, and SubBits does the same. So Final Cut Pro generator text will be broke down to two paragraphs. Currently there is no font style support as the format only supports a common style for all titles and a "character based" italic support - which is supported by most of the Final Cut Pro generators. Latter will change soon for "complete" italic Final Cut Pro subtitles.
This format supports timebase settings.

"DS Caption" as target
DS Caption is a format developed by Avid. It allows to transport simple timing and subtitle text into many of the Avid applications. It is also restricted to 2-line subtitles, but there are no leading empty lines allowed. TitleExchange Pro does take care of those restrictions. DS Caption also does not allow any "per tilte" or "per character" style settings - so nothing of that will be transported.

"DLP Cinema" as target
DLP Cinema Caption is a XML based format developed by Texas Instruments. It allows to transport timing and subtitle text to a system using a DLP Cinema Projector. The subtitles will be "keyed" in movie in real time during projection. This format allows to use several of the text styles which are available for subtitling.

"Adobe Encore" as target
This is a text based format developed by Adobe. It allows to transport simple timing and subtitle text into Adobe's DVD authoring tool "Encore". This format also does not allow any "per tilte" or "per character" style settings - so nothing of that will be transported.

"Cavena MTL" as target
This is another text based format. It allows to transport simple timing and subtitle text. This format does not allow any "per tilte" or "per character" style settings - so nothing of that will be transported.

"SRT" as target
This is a text based format. It allows to transport simple timing and subtitle text. This format also does not allow any "per title" or "per character" style settings - so nothing of that will be transported. It does allow more than 2 lines per title.
The SRT format can be used to add subtitles (captions) to YouTube movies.

"Cinevation" as target
This is a text based format. It allows to transport simple timing and subtitle text. This format also does not allow any "per title" or "per character" style settings - so nothing of that will be transported. It does allow more than 2 lines per title.

"Sonic Format" as target
This is a text based format. It allows to transport simple timing and subtitle text. This format does allow "per title" italic style settings. It does allow more than 2 lines per title.

"DFXP Format" as target
This is a XML based format based on the W3 org recommendations. It's used in different flavours from different companies. It allows to transport timing and subtitle text. This format does allow "per title" italic style settings. It also allows horizontal and vertical alignments -- per title vertical alignment currently is only supported by the 'MTV flavour". It should allow more than 2 lines per title.

The Conversion.
After the setup is done, click either "cmd-I" or click the "Import Subtitle File" button on the main window.
Depending on the source file some additional panels may show up.

XML source file:
If the timeline contains more than 1 title track the app will ask you to select a track.


STL Text source file:
As STL files often do not provide a timebase/framerate TitleExchange will ask you for it -- if none is found.

The selected framerate has to match the target framerate in case of an XML - if not the conversion may fail.

DVDSP Track Item source file:
If you import a DVD Sudio track item which contains more than one subtitle track a panel - which may look similar to the below - will appear. If the languange is not defined within DVDSP the track will be named "not set".

Other source files:
Many source files do not provide a timebase/framerate TitleExchange will ask you for it -- if none is found.

The selected framerate has to match the target framerate in case of an XML - if not the conversion may fail.

After a few seconds the conversion is done.

If both source format and target format are the same, the app will "clean" the input file, means the app will remove timecode overlaps and bad durations for STL and QTtext or replace generator with an XML
In case of a sequence XML the app just swaps from one text generator to another or will equalize settings which can be customized be the user.
To equalize settings just set up the first text generator of the title track you want to process in the sequence in a way you want the rest of the generators should behave, then export as XML. In TitleExchange Pro's "XML Settings" make sure to uncheck the "Use Template" button and select the original XML both as template and source. TitleExchange Pro will take the first generator as template and change all others to the same settings.

Tools Menu
Comming soon

Some notes

Why did I add QTtext to the In/Out option?
The big advantage while working with QTtext is, that it finally doesn't require any rendering time - even with thousands of titles and "no RAM" installed. And there are no audio/video delays. It does require some typing to fine tune, but that's normally less time than doing the editing in Final Cut Pro.
TitleExchange does create QTtext by using a very simple scheme. To create a QuickTime timescale for the movie the frames per second are multiplied by 100 with a DF timecode or just left as the fps with NDF timecode - so QT timecode is still user readable after conversion: a "10:02:01:16" will be a "[10:02:01.16]" after the conversion. This does make it easier for editing as if using the "600" or "1000" steps per second timescale many of the other applications do use.
A typical QTtext file will look like below:
{QTtext}{font:Didot}{Plain}{anti-alias:on}{keyedText:on}{size:24}{qtTextColor: 65535, 63861, 52265}{backColor: 0, 0, 0}{justify:Center}{timeScale:25}{width:720}{height:36}{timeStamps:absolute}{language:2}
[00:00:28.23]
Was?
[00:00:29.23]
[00:00:30.19]
Wer?
[00:00:31.15]
Nein, nein, hier spricht Martin Schlegel ...
[00:00:33.11]
Hermann Schlegel ist mein Vater.
[00:00:35.15]
[00:00:35.19]
Was?
[00:00:37.13]
[00:00:37.17]
Unfall?
[00:00:39.07]
...
It's human readable and can be changed easily. Unfortunately several of the old QT Player Pro features have been disappeared (so keep a copy of QT Player 6.5.1 if you still have it), but you can still open and copy/paste these text files to a movie with immediate response.
QTText also would allow to integrate subtitles for iPhone, iPod, iTunes with some easy steps.

Why did I add XML Marker to the input options?
Because this can speed up the process for subtitling movies. It's easy to press "MM" in Final Cut Pro and type in some text (or paste it) and maybe add a duration and forget about the double "double clicks" and "clicks" and copy and pastes. Just make a rough timing and titling and let TitleExchange Pro do some work for you.
If you do not specify a duration for a title (created by a marker) TitleExchange Pro will calculate the time the title needs to be displayed based on a given reading speed, the app also will take care that there are no overlaps.
You even can abuse this feature to render your normal sequence markers into a movie.

There is a small utitlity available now to view Arabic or Hebrew text STLs created by TitleExchange or other apps. This viewer is also intergrated within the app. These files may look weird in TextEdit as TextEdit can't handle right to left writing languages.
Get the viewer app here. To modify those STLs by hand you may use Barebones BBEdit.

The current version of TitleExchange Pro is available "as is" for 185 EUR (per license/machine) with free updates and tech support for three month. Multiple licenses (>4), educational pricing and modifications are available upon request.
You can get the application using the link below and register with an valid eMail address.
If you do not like that procedure, you can still send me a personal eMail with a request for the application.

Try before Buy:
Version 1.9. 3 for Tiger: Click here to download the TitleExchange Pro 1.9 for 10.4 (demo version works for 30 days as Pro version - with 50 title limitation - then the application will turn into Lite version, if no serial number is entered)

Version 1.9. 64 for Leopard/Snow Leopard: Click here to download the TitleExchange Pro for 10.5, 10.6 10.7 (demo version works for 30 days as Pro version - with 50 title limitation - then the application will turn into Lite version, if no serial number is entered)


To get a serial number for the unlocked version of TitleExchange Pro version click the PayPal button below.
(Note: Paypal currently does sometimes sent a different payment notification depending on your location and account, these notifications are not processed automatically on my server, but within 24 hours by me)

Limitations for TitleExchange Lite/Pro:
As with many of my XML tools the XML must be a "Sequence XML".
But you can use the new "Project Listing" feature to get a list of all projects and their sequences and then directly import from Final Cut Pro - though this may take a long time with big projects.
Titles have to be in one track (though you can choose the track), nested sequences are ignored. And - due to the limitations of the Boris generators within FCP, exported Boris text titles are not transfered as readable data.

Limitations of the free version and demo:
Only 50 titles can be converted at a time, you have to split STLs, XMLs etc. to work with big files.

Versions:

• 1.0 First release
• 1.02 Lite/Pro Version:
  • Creates a basic "STL Header", which allows to overwrite DVD SP's settings, the STL text file can be edited manually for fine tune as before.
  • Transfers "Standard Transitions"
  • First "Pro Version" with additional support for XML output, QTtext output, STL input, QTtext input.
• 1.04 b
  • QT to QT cleaning fixed
  • Preference AS errors fixed
  • Generator naming issues with UTF8 fixed
  • XML Marker format added
• 1.2.1 b
  • Rewritten for Tiger
  • New "helper concept"
• 1.5.1 b
  • Tiger issues fixed
  • Final Cut Pro 5 issues fixed
  • Support for non Western Roman text input
  • Conversion of SWIFT text to STL
  • Conversion of tab-delimited text to STL
  • Conversion of STL text to csv text
  • QT Player Script temporary disabled
• 1.6/1.7 b
  • minor bug fixes
  • Unicode and Windows STL/QT text import improved
• 1.7.5
  • QT conversion: some more stuff handled
  • new panel for selecting frame rate when no frame rate is provided by the source/target file
• 1.7.8
  • 24 -> 25, 25 -> 24 Timecode conversion for STL files.
  • Better handling for some "unusual" QTtext files
  • New text conversion options
• 1.8
  • Fixed wrong source TC entries (STL) using "." as seperators are fixed while importing source
• 1.8.6
  • UB support
  • minor bug fixes
  • Final Cut Pro XML cleaning for more security
  • Unicode text fully handled
  • New "TextUp" Generator for "Pro Users"
  • Arabic/Hebrew STL(text) viewer availble to check right to left reading STLs.
• 1.9.0
  • Final Cut Pro Apple Event support
  • DVD Studio "Track Item" support
  • STL binary import
  • XML "Generator Analyze" tool
  • "Style" support (where it supplies)
  • and more ...
• 1.9.02
  • Avid DS Caption support
  • Avid (SubCap) STL Binary import support
  • Edit B's Subbits support
  • Belle Nuit import support
• 1.9.08
  • Adobe Encore support
  • more of the "style transport" included
  • 2-byte character support improved
• 1.9.15
  • Cavena MTL doc/txt format support
  • SRT format support
  • 2-byte character support improved again
• 1.9.24
  • Framework fixes
  • Full DCP support via additional plugin - requires a special license +50 EUR (currently no direct FCP XML to DCP XML), standard version allows 20 DCP titles
• 1.9.30 L/SL
  • Beta for Snow Leopard 10.6.2 (works on Leopard as well)
• 1.9.31 L/SL
  • 3 new formats added: Sonic Text, Cinevation Text, Structured Subtitles
  • Some fixes for binary STL, DCP and Avid DS
• 1.9.33 L/SL
  • Some fixes for binary STL
• 1.9.34e L/SL
  • Some cosmetic fixes, Avid DS fixes
• 1.9.34h L/SL
• • New Format added (kind of timed titles)
• 1.9.34i L/SL
  • Bug fix for SRT import
  • Blue Ray Graphics XML import added
• 1.9.34j L/SL
  • Bug fix for 'bad space' characters in FCP XMLs
• 1.9.34k L/SL
  • Bug fix for text based STLs and improvements
• 1.9.34l L/SL
  • Another bug fix for text based STLs which was introduced by the previous version.
• 1.9.35 L/SL
  • Imports '<<Graphic>>' pathes from text STLs to Final Cut Pro XML.
  • Final Cut Server XML -- annotations now can be retrieved.
  • Bug fix for DCP XML export.
• 1.9.36 L/SL
  • Bug fix for STL plugin
  • Some more fixes/simplifying for DCP
• 1.9.37 L/SL
  • Workaround for FCP 7.0.2 XMLs with missing returns
  • Some more font options for DCP XML exports
• 1.9.40 L/SL beta
  • First version with a more 'unified' inter-format handling.
  • Some global import settings, to make handling easier.
  • AVID DS import enhancements.
  • Some more font options for DCP XML exports.
  • Some fixes for STL handling.
  • Improved support for bad formated SRT/SSA files.
  • Basic implementation for DFXP format (both standard version and MTVN version).
• 1.9.41 L/SL
  • DFXP options extended.
  • DFXP from FCP XML fixed (bold or bold/italic styles still do not work as the DFXP format is a bit strange with that)
  • Some other cosmetic fixes.
• 1.9.41b L/SL
  • More DFXP options for Flash and MTVN.
  • Workaround for badly formated Sonic files.
• 1.9.45b L/SL (stable)
  • Handling for ugly FAB EBU STL files.
  • Some polishes.
• 1.9.46b
  • Better handling of some ARTE EBU STL files.
  • Handling for an Adobe Encore import bug.
  • Improvements for DCP import.
  • Bug fixes for DCP export.
  • Some improvements for BluRay import.
  • Other minor fixes.
• 1.9.47
  • Bitmap subtitle import for Adobe Encore, BluRay, Sonic,Spruce STL (note: bitmap graphics are not supported by several output formats).
  • Some changes for DCP again.
• 1.9.48
  • Changes to the generator data source
  • All Apple localized text generators added to standard generator data base.
• 1.9.50b (stable)
  • Changes to the generator data source (some more relaxed handling of user modified generators)
  • Support for the new TextUp Pro v2 generator (different styles per paragraph)
  • TextUp Pro v2 Demo included within the installer
• 1.9.52
  • SAMI Support added
  • Fixes with illegal linefeeds in FCP XML
• 1.9.59
  • Generic Timed Text Support added
  • Fixes with several formats when source files were not formated correctly
  • New helper tool for FCP XMLs added
  • Standard generator database now includes Digital Heaven's Subtitle 2.5.1
• 1.9.64
  • Apple iTT (iTunes Timed Text) format added
  • Autodesk Smoke XML added