Skip navigation

Final Cut 7 and Mavericks issue report

5333 Views 3 Replies Latest reply: Dec 18, 2013 8:57 AM by Michael Grenadier RSS
Jeff Gibbs Calculating status...
Currently Being Moderated
Oct 30, 2013 7:30 AM

I recently installed Mavericks and FInal Cut Pro 7 seemed to run well.... until I tried to render some archival footage of various flavors that I had been using with zero problem with FCP7 and Mountain Lion. Then I began getting errors: "general error." Or the clip would render then appear white, or various styles of distortion.  I tried creating a new timeline, new project, no change.  I rebooted from a drive with Mountain Lion, opened the project, no change.  I tried rendering small parts--some rendered okay, some didn't.  I even took the project to another computer running Mountain Lion, same issue.  I ran Digital Rebellion's software to look for corrupt files--there were none. 

 

So then I opened a version of the FCP project from weeks ago, instead of projects saved under Mavericks, in Mountain Lion.  I dragged the same seemingly problematic video files into a timeline, hit render, hurray! No problem, perfect playback.  I therefore believe the issue was the way the FCP7 project was saved under the Mavericks OS.  It's important to note that my standard files from my original shoots--with limited testing--seemed to be handled fine.  It was only imported archival footage from various sources, of different flavors and speeds that seemed to be "corrupted" in a FCP7 saved under Mavericks, including some downloaded  and imported only the past few days. 

 

This might be a good caution for those whose projects use archival and downloaded video. I realize that some would just say turn it all to Prores. This would really suck and be extremely time consuming as I have thousands of clips collected over the years and often audtion dozens before choosing which ones to work with.

 

 

For now, I am going back to Mountain Lion, as it seem possible Apple may not resolve whatever this apparent conflict is between FCP7 projects and Mavericks.  Hoepfully they will.

MacBook Pro
  • Shane Ross Level 8 Level 8 (41,655 points)
    Currently Being Moderated
    Oct 30, 2013 9:39 AM (in response to Jeff Gibbs)

    >as it seem possible Apple may not resolve whatever this apparent conflict is between FCP7 projects and Mavericks.  Hoepfully they will.

     

    They won't. Why would they? FCP 7 is 4 years old...discontinued 2.5 years ago. FCX outsold it and all other versions of FCP combined...what possible reason do they have to support it?  They won't make any changes to an OS to support outdated, discontinued software.

     

    Rule of thumb...if you have system that works really well, don't mess with upgrading the OS.  Especially if you rely on that computer to earn a living. Only upgrade if you really need a feature that the new thing has...and always ALWAYS clone your working system before you upgrade, so you can restore that working system when the upgraded one breaks something. 

  • esiounis Calculating status...
    Currently Being Moderated
    Dec 16, 2013 1:45 PM (in response to Shane Ross)

    THIS.

     

    I actually loged in JUST to stress Shane's point. Better safe than sorry.

  • Michael Grenadier Level 6 Level 6 (19,805 points)
    Currently Being Moderated
    Dec 18, 2013 8:57 AM (in response to Shane Ross)

    and here's a user tip about cloning that should point you in the right direction

     

    https://discussions.apple.com/docs/DOC-2494

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.