Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Can’t open earlier FCP projects?

  • Can’t open earlier FCP projects?

    Posted by Walter Biscardi on April 29, 2011 at 2:17 am

    Philip Hodgetts just raised a very interesting topic of concern on his Twitter feed and something we just discussed briefly on Larry Jordan and Michael Hortons Digital Production Buzz.

    Can Final Cut Pro X open a Final Cut Pro 7 project? Philip says it’s not yet known if it can.

    I can’t imagine it wouldn’t but then again to have someone like Philip ask that question has me concerned. That would definitely cause utter chaos in our shop. We would have to keep final cut pro 7 running for years to update and open old projects.

    And so much for the earlier suggestion of running FCP 7 and X side by side on the same machine. You would have to commit before the project starts what you will use. Honestly this never even crossed my mind.

    Walter Biscardi, Jr.
    Editor, Colorist, Director, Writer, Consultant, Author, Chef.
    HD Post and Production
    Biscardi Creative Media

    Blog Twitter Facebook

    David Roth weiss replied 14 years, 12 months ago 15 Members · 36 Replies
  • 36 Replies
  • Craig Seeman

    April 29, 2011 at 2:58 am

    Don’t worry, Wes Plate will have an Automatic Duck FCPX Import product to solve this if need be. Just $495
    Export XML and OMF from FCPX? Just $495. Since FCPX is $299 you now have a total cost of $1289 so you can stop worrying about FCPX being underpriced.

  • David Roth weiss

    April 29, 2011 at 5:30 am

    I’m certain this is really nothing to be concerned about. There are a number of ways to accomplish moving projects between versions, with XML being among them. I can virtually guaranty that Apple will make backward compatibity a priority. They aren’t idiots. Phil is a smart guy, and many of his guesses have been pretty good, but he doesn’t have inside information..

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

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Business & Marketing and Apple Final Cut Pro forums. Formerly host of the Apple Final Cut Basics, Indie Film & Documentary, and Film History & Appreciations forums.

  • Andreas Kiel

    April 29, 2011 at 10:05 am

    Nobody here can say what will really happen – either it’s a guess or (s)he is not allowed.

    Problem is that there is a lot of unsureness even at the developers of third party stuff. Wes as well doesn’t have any insight. So it will take some time for everybody to catch up.
    What’s pretty clear: FCP X will take some of the features currently implemented in iMovie. Some of this stuff is difficult to be transferred or mapped from the ‘old’ structure to the ‘new’ structure. Maybe something is not working at all.

    So for all of us it will be a situation where we have to run both apps in parallel, at least for a while.
    That’s not a problem I think – many people do run CS5 and FCP in parallel right now or use an AVID on the same machine. You even can run FCP 6 and FCP 7 in parallel right now – though they share some prefs, plugins and the serial number.

    Andreas

    Spherico
    https://www.spherico.com/filmtools

  • Andy Mees

    April 29, 2011 at 2:07 pm

    We know that iMovie can export projects in FCP 7 XML format which suggests that some form of translation between FCP X and FCP 7 (and hence visa versa) is not necessarily unknown territory. Universal compatibility, function for function? That would seem doubtful, but I’d expect it to be largely compatible. Much as one might simplify aspects of FCP 7 project before sending out to Color, I could see more complex FCP 7 projects needing some simplification before exporting as an XML that would be compatible for import to FCP X.

  • Chris Kenny

    April 29, 2011 at 2:40 pm

    Hey, so I don’ have any specific information, but I’d like to point out that we don’t know whether or not Final Cut Pro X causes cancer. That would definitely cause utter chaos in our shop. We would have to keep Final Cut Pro 7 running for years to avoid dying horribly.

    Seriously, the “What’s the worst thing that could possibly be true about FCP X?” game is getting really, really old. Maybe Apple has cut all sorts of essential features… but there is absolutely no information indicating that, and in the absence of such information it’s rather more reasonable to believe that Apple is not, in fact, carrying out an elaborate and expensive suicide in the pro video editing market at this time.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read Does FCP X make project files obsolete? on our blog.

  • Andy Mees

    April 29, 2011 at 2:49 pm

    >Seriously, the “What’s the worst thing that could possibly be true about FCP X?” game is getting really, really old.

    So stop playing Chris, you don’t have to comment on every thread, especially if you have nothing especially constructive to add to it.

  • Chris Kenny

    April 29, 2011 at 2:53 pm

    Nobody has anything constructive to add on this subject, because there is no information. This sort of baseless speculation simply amounts to trolling at this point.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read Does FCP X make project files obsolete? on our blog.

  • Andy Mees

    April 29, 2011 at 3:10 pm

    >Nobody has anything constructive to add

    Did you get out of bed the wrong side this morning Chris? This is the FCP X forum, of course there is rampant speculation in here, how could there not be?
    You’ve got a brain up there, why not consider the question and put forward what you think might be valid arguments for or against the supposition? Simply harping on with the same canned response is getting a bit old.

  • Arnie Schlissel

    April 29, 2011 at 3:13 pm

    [walter biscardi] “Can Final Cut Pro X open a Final Cut Pro 7 project? Philip says it’s not yet known if it can.”

    I’d like to point out that it’s also not yet known if it can’t. Yes, backward compatibility is a very serious issue, but I suspect that someone at Apple (like Randy Ubillos, perhaps?) kind of knows this already.

    [Chris Kenny] “Hey, so I don’ have any specific information, but I’d like to point out that we don’t know whether or not Final Cut Pro X causes cancer.”

    I’m also worried that it might cause all of my food to spoil. No one’s really addressed that concern, either.

    [Chris Kenny] “Seriously, the “What’s the worst thing that could possibly be true about FCP X?” game is getting really, really old. “

    Me too! We’re engaging in a game of kremlinology, where we look at a photo of the Soviet leaders watching the annual May Day parade, and then interpret that photo to tell us what the state of the Soviet wheat harvest will be. But the kremlinologists don’t seem to know or care that the photo is doctored and the event is staged.

    Read my blog if you need that explained: https://www.arniepix.com

    Arnie
    Post production is not an afterthought!
    https://www.arniepix.com/

  • Craig Shields

    April 29, 2011 at 3:15 pm

    During the demo, they showed a big project opened in both 7 and X. He mentioned that it was the exact same project with the same cuts and transitions. I think that was your hint. Why would they rebuild that extensive project? I think they wanted to show that you could not only open those projects, but also make them less cumbersome with the grouping/nesting feature.

Page 1 of 4

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