-
XML based app to import subtitles into FCPX
Prelude: about Motion based (sub)titling workflows.
They been around for quite a while in let’s say limited way.
See my little movie about that a did quite while ago:
https://www.spherico.de/filmtools/TitleExchange/MotionTutorial/Meanwhile the Motion connection to FCPX (and Motion itself) is way more matured.
But there is a big BUT when it comes to interchange (sub)titles via XML.
The Motion templates don’t allow to export/import any settings and handling is very slow. Legacy fxScript based text generators did transport all info about any setting of a text. This allowed to change things like font, font size etc globally even if you didn’t know much about XML.
With the new way you can do it like it is shown in the movie, but only if you use your own templates. In this case no XML is needed – just change the settings in Motion and they will be applied to all instances in your project(s). So be careful when other rather then the actual project use the same template.Sometimes you may want to import timed subtitles from an external text file. I created a little app which allows to create FCPXML from Spruce Text STLs. You can download it here from the link below.
https://www.spherico.com/filmtools/TitleExchange/stl2FCPX.dmg
Regards
AndreasP.s. There is another one to export titles from FCPX.
https://www.spherico.com/filmtools/TitleExchange/FCPXTitles.dmgSpherico
https://www.spherico.com/filmtools -
11 Replies
-
Fantastic work!
——
T. Payton
OneCreative, Albuquerque -
Coincidently I have a need for this on a current project. I have my STL file but when I open stl2FCPX and choose convert it is asking for a FCPXML file (I was thinking it would ask for a stl file). So I point it to a FCPXML and it says it is unreadable.
Thoughts?
——
T. Payton
OneCreative, Albuquerque -
My bad, apparently a bad XML file on my end. So it chooses and XML file and I assign a role (very cool BTW) but it won’t let me select my STL.
——
T. Payton
OneCreative, Albuquerque -
Ahh. The extension on the STL file must be .txt.
——
T. Payton
OneCreative, Albuquerque -
Sorry, I should have it the small help file that the STL extension should be .txt.
I will add that for the next version.Andreas
Spherico
https://www.spherico.com/filmtools -
Hi Andreas, this is fantastic, just what I have been looking for. I don’t quite understand how to choose which motion generator is used for the titles though? Should I give an fcpxml file from an empty project as the source? Or the project I want to add titles to? Should I set up a template title on that project?
Gregor
-
Hi Gregor,
Have a look at the Help menu. It’s explained there how to create a template.
Regards
AndreasP.S. the FCPX title exporter will be updated later today (European time)
I now makes a rough analyzis of the Motion XMLs and extracts font, font size and font style. I’m still working on alignment – means searching for this entry in this unfortunately undocumented Apple Motion XML.Spherico
https://www.spherico.com/filmtools -
Thank you Andreas, that is very helpful! I looked for a readme and I looked on your site but stupidly never thought about the help menu!
-
Andreas, the link doesn’t seem to be working any more. Do you have the app available to work with the lastest FCPX 10.0.5? Specifically, I’ve noticed that motion templates xmls do not include the tag, they are tagged as and thus do not retain any text. Any workarounds?
-
Hi Ariane,
The FCPX title conversion tools are now part of the TitleExchange installation which can be found here:
https://www.spherico.com/filmtools/TitleExchange/TitleExchangePro_SL.dmgI don’t understand what you mean by tags. You can send my an example.
-Andreas
Spherico
https://www.spherico.com/filmtools
Reply to this Discussion! Login or Sign Up