Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations What happened to the APIs Apple was going to release in the next “few weeks”?

  • What happened to the APIs Apple was going to release in the next “few weeks”?

    Posted by Helmut Kobler on August 18, 2011 at 5:55 am

    Apple published its Final Cut Pro X FAQ in late June, and in that document, it said it would release APIs so third parties could add XML support. See here (and scroll down to Export): https://www.apple.com/finalcutpro/faq/

    So it’s been almost 6 weeks since the FAQ appeared, and still no word about the APIs, yes? Or did I miss that?

    I hope I missed it, because it doesn’t look good for Apple to try to assure jittery users about its commitment, and then immediately be late.

    ——————-
    Documentary Camera in Los Angeles
    http://www.lacameraman.com

    Anders Teigen replied 14 years, 7 months ago 17 Members · 29 Replies
  • 29 Replies
  • Chris Harlan

    August 18, 2011 at 7:10 am

    And, hey, let’s not forget that support for external monitoring that should be coming any day now.

  • James Mortner

    August 18, 2011 at 9:53 am

    Hmmm, almost as if they’re an incredibly profitable company with far bigger cash cows to milk….

  • Brian Mulligan

    August 18, 2011 at 12:11 pm

    “They lied. They lied to us!”
    “I told you Steve would never consciously betray the Rebellion.
    “Terminate him… immediately!”

    Brian Mulligan
    Senior Editor – Autodesk Smoke
    WTHR-TV Indianapolis,IN, USA
    Twitter: @bkmeditor

  • Oliver Peters

    August 18, 2011 at 12:34 pm

    Most speculation points to a minor update in September. Hard to say whether this would include anything with XML. Of course, once it’s a public SDK, then it will still take a while for developers to create applications based on it.

    Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Sean Cole

    August 18, 2011 at 4:10 pm

    Oh, it gets better than that Helmut,

    Back on Jul 28th Walter Biscardi wrote in a post here that

    Apple will be releasing the XML code, or “hooks” to developers in 2 weeks so they can start developing third party XML apps – Evan Schectman from Outpost Digital.

    Well, I’ve been checking back with Apple every day for the last 2 months and still nothing. It’s now 3weeks and 1day since the meeting in Atlanta and it’s obvious that Mr Schectman was either misinformed or misunderstood. Or, maybe Apple are talking in biblical ‘weeks of years’ in which case we might see them sometime in the next 14 years – yay!

    In the meantime I’ve been busy getting my code together ready for the big day it is finally released. Please do send me your feature requests for what you want to do with this XML once it’s here. Realistic uses – I mean, if you want it to convert to EDL, what do you need the EDL for. If you only want it to talk to a SVHS machine then there’s not really any point – What DO people want EDLs for these days??

    All the best

    Sean
    Pi Digital

  • Oliver Peters

    August 18, 2011 at 4:28 pm

    [Sean Cole] “Realistic uses – I mean, if you want it to convert to EDL, what do you need the EDL for…… What DO people want EDLs for these days??”

    Pretty much every colorist and DI house works with EDLs. Avid created a specially modified 16 character EDL for RED files because of this. Want to send a Baselight colorist an FCP project for grading? You will be asked for QT camera files and an EDL so they can conform and grade. Want to work with a CDL color grading list? This is basically an EDL with comments. Want to import a self-contained QT into a grading application and have the cuts “notched” at the edit points? EDLs are the common language. So yes, this almost 40-year-old format is still proving more versatile and alive than AAF, OMF and XML in many, many post applications.

    Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Robert Brown

    August 18, 2011 at 4:36 pm

    Yeah when it comes down to it, a list of shots used is not complicated, and having a simple txt file that’s readable and editable by humans is hard to beat.

    Also offline to online is still alive and well as high end productions still shoot uncompressed, so edl’s are often the best way to get your cut from an Avid or whatever to whatever you will conform it on – Smoke, Quantel etc.

    And tape to tape is almost dead but probably not quite.

  • Chris Harlan

    August 18, 2011 at 4:46 pm

    Also, compliance issues and delivery requirements. Sometimes legal departments need a paper record of footage used. And, many networks and studios require an .edl as part of their full delivery package, so that they can resuscitate elements of your project from scratch across platforms.

  • Sean Cole

    August 18, 2011 at 5:10 pm

    Perfect feedback Oliver, Robert and Chris

    So, I’ll create a version of EDL similar to Avids RED format. What other standards of EDL do you use the most or prefer to use. CMX, Sony or other?

    I am concentrating on porting FCP6/7 XMLs into FCPX and vice versa and also to Soundtrack-pro/Logic (huh, good luck I hear you cry), Color (even though these may be upgraded soon, or abandoned) and After Effects. But what else would you like to see it talk to?

    Sean
    Pi Digital

  • Oliver Peters

    August 18, 2011 at 5:27 pm

    [Sean Cole] “CMX”

    CMX 3600 or GVG lists seem to be the most universal. Sony lists tended to reverse key elements. These should also be A-mode and C-mode layouts. With comments supported.

    [Sean Cole] “But what else would you like to see it talk to?”

    Premiere Pro, Avid, Smoke. Although other tools may do that fine if you get the right XML out.

    Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

Page 1 of 3

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