Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro 10.1 XML Import Test – Appears to be DOA

  • 10.1 XML Import Test – Appears to be DOA

    Posted by David Roth weiss on September 20, 2011 at 4:41 pm

    Sorry to report, but FCP X nirvana is probably not available for download yet.

    I just tried to import an XML into X 10.1 from FCP and so far XML Import seems to be dead on arrival.

    All FCP XML files are grayed out in the import dialog.

    I’d love to know if someone else gets a different result.

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles
    https://www.drwfilms.com

    Don’t miss my new Creative Cow Podcast: Producing Episodic TV with “24” Producer Michael Klick:
    https://library.creativecow.net/weiss_roth_david/Podcast-Series-1_Michael-Klick/1

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.

    Elias Huch replied 14 years, 5 months ago 18 Members · 35 Replies
  • 35 Replies
  • Bret Williams

    September 20, 2011 at 5:03 pm

    I think they would have mentioned backward compatibility had they achieved it. But only cnet seems to think that.

  • Andrew Richards

    September 20, 2011 at 5:03 pm

    From Apple’s update page:

    “Now you can import and export Final Cut Pro X project and Event information via a rich XML format. XML interchange enables a wide range of third-party workflows, including high-end visual effects, color grading, and media asset management. Blackmagic Design’s DaVinci Resolve, Square Box System’s CatDV, and many other third-party applications will offer XML-based workflows with Final Cut Pro X. (emphasis mine)

    This is an all-new XML shema (AXEL), so it isn’t going to import FCP7 XML. Any third parties like they mention will need to develop a new parse for this flavor of XML.

    Best,
    Andy

  • James Cude

    September 20, 2011 at 5:03 pm

    Hmm- I’d imagine if that feature were enabled Apple would tout it on the updates page but they don’t. So it’s not really ‘DOA’ so much as ‘never promised.’

    Instead it says:
    “Now you can import and export Final Cut Pro X project and Event information via a rich XML format. XML interchange enables a wide range of third-party workflows, including high-end visual effects, color grading, and media asset management. Blackmagic Design’s DaVinci Resolve, Square Box System’s CatDV, and many other third-party applications will offer XML-based workflows with Final Cut Pro X.”

    Sounds like this is still a third party opportunity for now.

  • Craig Seeman

    September 20, 2011 at 5:15 pm

    But it does seem like something may eventually be done to get FCP7 to spit out the new XML format. Let’s just hope it’s not a $500 “quacker”

  • Erik Lundberg

    September 20, 2011 at 5:15 pm

    But now at least, since FCPX is now using the same basic way of communicating , there should be a viable way to get someone to make a translation from a FCP7 flavoured XML to a FCPX flavoured XML.

    Erik Lundberg

    Technical Director, Media Technology, University of Gothenburg, Sweden

  • Andrew Richards

    September 20, 2011 at 5:19 pm

    [Craig Seeman] “Let’s just hope it’s not a $500 “quacker””

    I bet there will be several of varying levels of sophistication with a range of prices.

    Best,
    Andy

  • T. Payton

    September 20, 2011 at 5:25 pm

    The whole point of XML is so that different systems can read and write data. Therefore as long as this new XML format is documented, it will be an easy task to make a translator.

    I started creating a translator that would take a FCP 7 to iMovie project (which is XML) and therefore FCP X and while I was able to get it to work on simple items, the iMovie XML is not a documented format, therefore I hit a wall.

    The new XML format will be documented (Apple said Blackmagic, etc. will be creating import/export capabilities) so just give it some time, maybe even just a day and there will be translators. 😉

    ——
    T. Payton
    OneCreative, Albuquerque

  • James Cude

    September 20, 2011 at 5:34 pm

    I”m guessing an FCP 7 translator will not be impossible. If you do a quick export of your XML from an X project you’ll see the XML is very understandable- as XML generally is. It’s wide open for an enterprising (no pun intended) developer to take it a step further.

  • David Roth weiss

    September 20, 2011 at 6:05 pm

    [Andrew Richards] “This is an all-new XML shema (AXEL), so it isn’t going to import FCP7 XML. Any third parties like they mention will need to develop a new parse for this flavor of XML.

    Interesting! One would think that in the interest of fairness in marketing that information should be coming directly from Apple rather than from you Andrew.

    If FCP 10.1 only imports XMLs from FCP 10.1, Apple should have spelled that out loud and clear. Every press release I’ve read today implies simply that XML Import/Export has been added to the 10.1 release. Nowhere is there any mention that it only supports special FCP X XMLs.

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles
    https://www.drwfilms.com

    Don’t miss my new Creative Cow Podcast: Producing Episodic TV with “24” Producer Michael Klick:
    https://library.creativecow.net/weiss_roth_david/Podcast-Series-1_Michael-Klick/1

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.

  • Simon Ubsdell

    September 20, 2011 at 6:08 pm

    To be fair, Apple are talking about it as “a rich XML format” acknowledging that there is some difference – though they haven’t exactly flagged up its limitations vis-a-vis legacy XML.

    Simon Ubsdell
    Director/Editor/Writer
    http://www.tokyo-uk.com

Page 1 of 4

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy