Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP 6.0.6 super slow, crashes easily

  • FCP 6.0.6 super slow, crashes easily

    Posted by Bennett Jones on May 22, 2010 at 9:44 pm

    Help!

    I recently switched to a different G5 dual 2.5ghz keeping the startup disc from my old one (same model, died of a coolant leak) and was getting a lot of “file not found!’s” with my FCP.

    I freed up some space on my external scratch disc (moving some source files around in the process) and the program ran slower and crashed as soon as I started any kind of work, even pressing play.

    During the switch over, I got a “re-set your clock or stuff will run slow” message (i’m using a wireless bearextender for my internet connection). I reset the clock and the internet sped back up but not FCP. Don’t know if this has anything to do with the problem, just thought I’d throw it in here in case.

    I’ve dumped preferences and re-installed the FCP 6.0.6 suite. No changes. I’m thinking it has something to do with:

    A) moving all those source files around
    B) some kind of corrupted media due to different file types – I’ve got a lot of JPEGs in the timeline (though never had these problems before)
    C) Something messed up with the replacement G5
    D) The wrath of Zeus.

    I’m pretty green as far as this goes – any help would be awesome!
    thanks
    Bennett

    Bennett Jones replied 15 years, 11 months ago 2 Members · 2 Replies
  • 2 Replies
  • John Adams

    May 23, 2010 at 5:23 am

    don’t know if this will help but…

    I’ve often had probs with stills in my timeline — ensure that they’re less than 4000 pixels in either direction (FCP’s max resolution is 4K). And if the stills are not required to be that big, then resize them to something less memory intensive (ie. as small as they can be without sacrificing image quality in your timeline).

    If you think your project file is corrupted yet you can still open it, try copying all the bins/clips into a fresh project file — save this new one and work from it. This trick has saved me more than a few times.

    best of luck — hope this helps

    – – – – –

    http://www.tinypalace.net

  • Bennett Jones

    May 25, 2010 at 1:01 am

    thanks for the response
    After much troubleshooting, including your suggestions, it turns out to be a ram issue. I’m putting in 2 1gig sticks tomorrow and that should (hopefully) be the end of it.
    thanks again!
    B

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