Sorry Andreas, you too have slightly misunderstood me. My fault I suppose though. I know only full well that xml is used for lots of things, not least databases and in HTML for providing plenty other information. I also use the EX3 which also has XMLs on it’s cards for metadata. So yes, XMLs DO resemble XMPs in this one regard.
However, what I was specifically talking about was it’s use for FCP exports. In a similar way to how Avid, Premiere Pro, After Effects, Motion, Soundtrack Pro, Grass Valley, and crap loads of other software use it 😛 for sending edit and effects information to each other – or anything potentially in fact.
So, Tell me please how XMP is like that? It’s not. It’s extended metadata. That’s it. It can’t transfer edit information over to FCP, After Effects, Avid. It could, but it doesn’t. Not yet anyway. – But of course you don’t need me to tell you that (forgive my apparent insolence. It wasn’t meant for your benefit, it’s for anyone else who may stumble across this thread in search of valid information).
FCP’s XML interchange protocol is to address this (the transfer of edit/sequence AND clip specific information) and is what the Original Poster was writing about when he spoke of the API’s Apple were going to release.
Who’s AXEL by the way? :/ Is he/they creating a new solution for data interchange.
What do you think about the Alexa when working with Prores, what is the XML on the card for? Data or metadata.
P2? Canon 5D/7D?
Que? Oh, sarcasm. I see 😀 Like it
So to sum up, when I said ‘XMP is metadata, whereas XML is for data transfer through a packaged markup language’ what I should have added (for those who couldn’t be bothered to link it with the rest of the post) was ‘from Final Cut Pro to some other edit or sequence based application – because obviously if I wanted to send just a clip I would export a quicktime with a crap load of metadata’ 😉
Sean
Pi Digital