Import subtitle from markers or XLM

[Nick Swinglehurst]

Hi there,

I would use a script to modify your exported XML sequence, such as AppleScript or Python or even some advanced use of Excel.

First, open your XML in whatever you want to type your transcription into (Excel can handle that) and enter all the transcription.

Next, you’ll need to run a script on it. Wherever the script sees a marker in the XML, it should add a text layer above your video layer and put your transcribed text into the text layer. It will need to be nicely formatted as Final Cut Pro XML which you then reimport into FCP.

You will certainly still need to go through manually to check timings, positions, line breaks, etc, but the script will save you a lot of time and is very flexible if you need to do this again, e.g. for other languages.

In any case, the scripting approach is the most efficient solution but you will need to adapt it to your needs. If you don’t have the expertise yourself, you can hire a freelance Python coder for a one-off job very affordably.

Nick

Nick Scale | Film Editor | Colourist | Compositor

[Neil Sadwelkar]

Sure.

You’ve place markers where the subtitles begin. Now you need to type the subtitle content in the marker label and Extend (opt-`) the marker for the subtitle length.

Then export this sequence as a marker list
File > Export > Markers List as text…

This text file can then be converted to an XML using software like Title Exchange Pro.
Test it to see if it works.

———————————–
Neil Sadwelkar
neilsadwelkar.blogspot.com
twitter: fcpguru
FCP Editor, Edit systems consultant
Mumbai India

[Nick Meyers]

there is an App that will make FCP subtitles from sequence markers.

it is called Title Exchange Pro, from Spherico FIlmtools
it costs a bit, but it actually does a lot MORE than turn markers in to subs.
it is for converting one title format to another.

for instance, turning an STL file (from a DVD, say) into FCP text, or vice-cersa,

or could be for making a global changes to an FCP text style
(like you’ve got a thousand subtitles, and the producer says: no a little bit bigger!’

nick

[Nicolas Servide]

Thanks guys!
I will try those options.
Best,
Nicolas

[Mustafa s. Zeno]

Can someone expound on if they ever tried this and it worked? I’m exporting the markers as text, adding duration, and trying to convert them in TitleExchange to XML but there’s no option to read a Marker text file. When I try the ‘generic timed text’ option instead the XML file is not recognized in FCP. Please help!

[Nick Meyers]

yeah, i used it, and it worked.
but you don’t export the markers as text,
you export an XML from the sequence, and open that in TEP.

in TEP there’s a whole lot of option for your “IN” format and your “OUT” format.
from memory you want to import a XML Marker (FCP) and export XML (FCP) if you want to geet it back into FCP

nick

[Mustafa s. Zeno]

Thanks for the prompt help Nick! I tried that too but it kept on saying “no markers found”. Obviously there are many scene markers. Any idea why that is?

[Nick Meyers]

i *think* i know what that means.
coul be to do with Teomplates

TEP has to make titles for you.
but you have to tell it how you want them formatted.
what font, what point size,

what Generator even, as is which SORT of FCP title.
plain old “text”?
outline text?

or maybe one of the 3rd party subtitle generators, like Spherico’s own Text Up Pro,
or the one from Digital Heaven.

so you put your preferred text in an FCP timeline, export an XML,
and in TEP you ad that to a bank of Templates.

if that’s not it, you can always get in touch w Andreas from Spherico

nick

[Mustafa s. Zeno]

Hi Nick,

Thanks again for your response. Yeah I made a template with all this info, and TEP seems to be accepting my template just fine. It’s just not liking the xml of the actual sequence, almost as if the exported XML of the sequence isn’t including the markers in the export. I will also try to contact Andreas and see what he says.

Thank you!

-Mustafa

[Nick Meyers]

maybe make a COPY of the sequence in FCP,
and delete all the contents.

it’ll be a much leaner XML.

nick