What doesn´t translate through XML?

It would be nice to have a list of things that don´t translate through XML.

So far I found:

- Sync status

Hi Nils
OK going to stick my foot in mouth and say AFAIK there is no universal "What will or won't translate" in XML.
For one thing, different programs interpret XML differently and there are different versions of XML. FCP uses FCPXML(now 1.5 I believe). While XML is supposed to be a easy to translate language, there can be issues.
One source for seeing some XML abilities is the help for Intelligent Assistant (makers of X to CC) has some info on what translates for FCPXML to Premiere Pro and CC apps and from legacy FCP to FCPX.

If folks know of a definitive source, would be interested myself.

Now some folks will chime in an say I'm full of it, but just passing on what I have experienced.

Hope this helps, Greg

Ok, I thought it would have been clear, but I should have stated more precise.

I would like to know what is lost on xml export from within FCPX. (Yes the present version is 1.5)
Or in other word which characteristics will not translate into the resulting fcpxml file.

It´s true that converting the (clip, project, event, library) fcpxml to another format is a different thing and a much more complex topic. But that´s for another thread.

I am not aware of any such repository of knowledge.

It also depends on the Metadata View you use to export. Different metadata views export different things.

I can tell you that the media used in an effect or generator drop zones does not export to XML.

Otherwise your question, while seemingly clear, does not have a clear answer. I suggest you think about what you need translated and then check that stuff specifically.

Thanks for your answer Wes.

Of course different metadata views chosen on export lead to different information in the resulting xml.
Same is valid for the chosen FCPXML version.

But if I create a metadata view with all items checked and exported with this metadata view there will still be information within Final Cut not in the XML.
This is totally normal but it would be good to know.

Please don´t focus on what is going to happen with the xml.
This is not so much about a certain goal I want to achieve at the moment. It´s about knowing the capabilities and limits of FXPXML
I´m sure there is a definitive answer to this.
And I hoped we could just collect the parts of this answer in this thread.

Nils
Have you read Apple's Developer's Material on FCPXML?
developer.apple.com/library/mac/document...on/Introduction.html

Read through that entire section and see what you don't can't figure out, and then focus some questions for us.

Hope this helps, Greg

Hi Greg,

I actually read through the whole FCPXML documentation and through the DTD for version 1.5
The documentation is a good starting point and the DTD is (obviously) quite extensive.
Still you will not find information about everything especially concerning effects.
But I already stated my question. I don´t have a practical problem to solve, I would just like to collect information.
Where are the limits of xml export? What information is stored and used inside FCPX (one could possibly not think about) which will not end up in the xml.

So far I have
- sync status
- media in drop zones (just tested it on one effect myself, dropzone is empty after reimport)