

You may have to edit the title's styles again.

Then copy the text from the translation and paste it into the text entry of the subtitle. Using the example above the timeline will jump to the selected subtitle "My Text" wherever it is. If you got the changed export from a coworker (or you might have done it by yourself) you can copy the UUID and paste it into the search entry of the project's browser. Other than the old FCP XML the current basic FCPX XML does not not support any style information (beside other things) and it's left to the user to replace wrong/changed/translated titles manually. If a coworker will do a translation for that, as an example into German, it will look like: If you use the UUID option together with the text export you can import the text file into Excel (I hope - I don't own any MS product). It's both simple and complicated with the current XML implantation of FCPX. I will make MTT available with more features end of October - it will make the above described easier. I made a test last week "hacking" Simon's subtitle template which uses a background box and it worked fine with the beta of the beta app. Within the app the user can then select the "template group" which should be used. This way the app could scan reliably all available subtitle templates during launch - or on request. Only one text entry set up in Motion, just to make the FCPX browser not to crowded) A description of the template set up in Motion) "myTemplate Plain", "myTemplate Bold", "myTemplate Italic", "myTemplate Bold-Italic" A naming convention for the templates i.e.

A sub folder named "Standard Subtitles" - this must be set in Motion as wellģ. A folder with your "brand" within the "Titles" folderĢ. So the idea is that anybody using this app can create his custom "Basic Subtitle".īut there are some rules which need to be followed to allow the app to manage these - and help the user to manage the workflow.ġ. This allows to have those titles to reflect the original source style in a kind of "something is better than nothing". Subtitles are affected heavily.Īs I did with my "Basic Subtitle" I created Motion Templates for each font style. Some workflows are affected more than others.
AEGISUB MAC QUITS UNEXPECTANTLY MANUAL
As mentioned in the manual the XML implementation of FCPX is pretty poor.
