10.6 fcpxmld

[Andreas Kiel]

Hi Jeremy,

This new format (package) probably was introduced to keep XMLs small and simple while introducing all this new tracking stuff. Latter can create huge amount of data.

This is also valid for other effects data.

So it’s not a real change of format – the XMLs are the same format – but an extension to keep data collections together.

To get a standard XML version export a 1.9 one or just drag whatever you need – project, event, library etc – from the FCP browser either to the Desktop, TextEdit, BBEdit or similar app which supports drag’n drop from clipboard.

[Jeremy Garchow]

I guess I am curious as to what programs or applications will use the tracking data?

And it is only tracking data that gets exported, or what else will get exported that’s not in the XML normally?

[Eric Santiago]

Motion?

[Jeremy Garchow]

Motion doesn’t even import fcpxml! 🙂

X2Pro was updated today to accept the new format.

[Eric Santiago]

Thanks, Jeremy for this tip.

I know it’s been two years but I ran into an issue with FCPX 10.6.7 and R17 today.

Your tip helped with the use of XtoCC 🙂

Now Im hoping there is a fix to this for others that don’t have the XtoCC.

[Jeremy Garchow]

In each FCPXMLD package (you have to right click and “show package contents”), there’s an “info.fcpxml” file that resolve should be able to read.

Resolve 18 has been updated to accept up to fcpxml v1.10, and maybe even 1.11 with the latest release.

[Ran Slavin]

Hi Andreas,

I use FCPX 10.6.10 and trying to export FCPXML to read on another older machine running FCPX 10.4.10

Its a problem i cannot get around with the new fcpxmld, because FCP version 10.4.10 wont read fcpxmld. SendToX wont read it either.

Do you know how it can be possible to do so?

Many thanks

Ran

[Ran Slavin]

Found the solution: Export fcpxmld

Open package content

Open the xml file inside with text edit and change its version from 1.10 to 1.9 or whatever the older fcpx reads.

Save outside of container

Import into fcpx and voila