Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Backwards compatible

  • Backwards compatible

    Posted by Walter Bienz on May 19, 2007 at 4:33 am

    I was wondering if anyone has come up against this problem. I’m trying to check an edit in FCP 5.0 from a project created in FCP 5.1.
    Simply trying to open the project doesn’t work. And although exporting EDL’s is a successful way to bring in a timeline, it doesn’t contain all the effect info.

    Any ideas gratefully received, thanks.

    It’s life Jim, but not as we know it.

    Steve Cohen replied 18 years, 12 months ago 6 Members · 9 Replies
  • 9 Replies
  • John Foley

    May 19, 2007 at 1:11 pm

    This question has come up literally hundreds of time. The same answer as always. NO.
    Project files are not backwards compatible. However, with FCP 4, we were introduced to XML.
    You can output your timeline to an XML file that can be read back by another XML capable program (IE: earlier version of FCP)

    Please visit http://www.thefinalcutstore.com for all your Final Cut needs.

  • Alan Lacey

    May 20, 2007 at 11:03 am

    what? Not even from ver5 to 5.1

    Alan

  • Walter Biscardi

    May 20, 2007 at 11:04 am

    [Alan Lacey] “what? Not even from ver5 to 5.1”

    Nope, not even from v5.1.4 to 5.1.2. You cannot open any FCP project in any older version.

    Walter Biscardi, Jr.
    https://www.biscardicreative.com
    HD Editorial & Animation for Broadcast and independent productions.

    All Things Apple Podcast! https://cowcast.creativecow.net/all_things_apple/index.html

    Read my blog! https://blogs.creativecow.net/WalterBiscardi

  • Walter Bienz

    May 20, 2007 at 11:10 am

    Thanks for your reply.

    It’s life Jim, but not as we know it.

  • Steve Cohen

    May 20, 2007 at 11:55 am

    I thought so as weell, but came to find ou that it is backwards compatable from 5.1.4 to 5.1.2.

    Oue engineer started updating some of our systems and didn’t quite finish (and now has decided not to finish until we get 6).

    I can open a project in 5.1.4 work on it, save it and then open it in 5.1.2.

    Steve Cohen
    Editor
    O2 Media Inc.

  • Walter Biscardi

    May 20, 2007 at 11:57 am

    [Steve C]
    I can open a project in 5.1.4 work on it, save it and then open it in 5.1.2.”

    Interesting because that does not work here. We get the warning that the project was created in a newer version of FCP.

    Walter Biscardi, Jr.
    https://www.biscardicreative.com
    HD Editorial & Animation for Broadcast and independent productions.

    All Things Apple Podcast! https://cowcast.creativecow.net/all_things_apple/index.html

    Read my blog! https://blogs.creativecow.net/WalterBiscardi

  • Steve Cohen

    May 20, 2007 at 12:25 pm

    If I remember correctly (I’m not at work right now). I get the warning also, but whn I open it and save the project, it will syill open in 5.1.2.

    Steve Cohen
    Editor
    O2 Media Inc.

  • Shane Ross

    May 20, 2007 at 1:13 pm

    Yep, If I have a project that I created in 5.1.2 (on my G5), I can open it on my laptop (FCP 5.1.4) and not get the “this project file will be upgraded” prompt. It just opens. Then I work for a bit, save it, and that file is openable on the G5 with 5.1.2.

    This is the only time I have seen this happen. I think it is because 5.1.4 was a minor fix to 5.1.3, which was a minor fix to 5.1.2.

    Shane

    Littlefrog Post
    http://www.lfhd.net

  • Steve Cohen

    May 20, 2007 at 1:35 pm

    I’m not 100% sure, but updates should be backwards compatible, but upgrades are not.

    Wikipedia=Backward compatibility is the special case of compatibility in which the new server has a direct historical ancestral relationship with the old server. If this special relationship does not exist then it not usually spoken of as “backward” compatibility but is instead just “compatible”

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