Move your ‘Final Cut Pro.app’ from the Applications folder to the DesktopĢ. So if you already updated to 7.0.2 here a tip how you can create ‘clean’ XMLs.ġ. This is more than annoying if you work with subtitles, but it can/will be the same little disaster if you want to ‘downgrade’ to a lower version of FCP or collaborate using XML as interchange format. This is a known bug of FCP 7.0.2 and will affect all XML exports and there is no workaround within FCP. Imagine, if you need about 1 minute to control each title, it would take about 250 hours to fix this one movie. It was solved by the workaround described below – the customer was more than happy. I got a customer who had a documentation with 7 languages each about more than 2000 subtitles which were fine tuned within FCP - all in all there were around 15,000 subtitles screwed up for release on DVD, film, YouTube etc. This is a real disaster, if you working with subtitles which are are sent forth and back between systems using XML. With any app which tries to interpret the XML - this includes FCP itself. Enter a text with line breaks into any metadata field which allows that - like with text generators, markers or comments. The issue is very simple and probably won’t affect too many of your readers, but I got more than hundred mails about that issue. Over the last few weeks I got more and more mails from people who complained about missing line breaks in XML metadata text entries - and they asked for a workaround. There’s a problem with the XML Export function in Final Cut Pro 7.0.2.
If you are running an earlier version of Final Cut Pro, please read on.Īndreas Kiel, of Spherico, brought this to my attention yesterday. You can get the latest version via Software Update. Yesterday, Apple updated Final Cut Pro to 7.0.3 which, among other things, fixes this problem.
0 kommentar(er)
