| The older interchange formats were versions 1 to 5 of xmeml. The new format is version 1 of fcpxml, so there should be no confusion if you're needing to write code that supports both.
Also FCPX outputs xml with a ".fcpxml" extension which makes it easier to distinguish between the two (for open dialogs etc.)
Cheers,
Greg On Sep 21, 2011, at 2:01 AM, Jack James wrote: This sounds to work exactly the same as FCPXML from previous versions, for example it doesn't store things related to the UI in the XML file. A cursory look at the new format would seem to allow for round-tripping.
Also, why on earth is it labelled as FCPXML 1.0? There is already an FCPXML 1.0 from final cut pro 4 (or thereabouts). This is going to get unnecessarily confusing for us and for end-users. Shouldn't it have been called FCPXXML? Or FCPXML 6.0 (or 10.0?)
---------- Original message ----------
Hello all,
early in the new doc describing FCP X XML there is this:
"Important: FCPXML Version 1.0 describes certain project data that is useful for exchanging with other
applications. It does not describe all possible data, and therefore is not a substitute for the native project file
when archiving a project or moving a complete project from one system to another."
This sounds like workflows that rely on getting a sequence XML out of FCP, manipulating the XML, and finally putting the XML back into FCP will potentially break things, as in: the returned sequence will drop things that where in it in the first place. Is that correct?
Also, what is it that gets lost?
Thanks,
Rainer
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|