Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy ongoing crashes

  • ongoing crashes

    Posted by Bill Parker on December 10, 2009 at 11:55 am

    I’m using FCP 7.0.1 on a Mac Pro 2×2.26 GHZ Quad-Core Intel Xeon and for some reason, FCP has been crashing on me recently. I opened a project and worked on it and encountered the spinning ball. I force quit and then reopened to the same result – three times more. I trashed preferences and that fixed it temporarily. Then it started again. I copied the files onto a new project and that seemed to fix it – for a while – and then again. I then decided to open older projects and encountered the same thing – trashing preferences a temporary fix. Has anyone else encountered this? Thanks.

    Martin Phillips replied 16 years, 5 months ago 3 Members · 4 Replies
  • 4 Replies
  • Jeremy Garchow

    December 10, 2009 at 5:05 pm

    Please give way more information about your project.

    There’s obviously something in the project that is tripping up FCP.

    Jeremy

  • Bill Parker

    December 11, 2009 at 4:31 pm

    I have a Kona LHe card that I thought might be connected to the problem so I removed it and reseated it and voila! – problem solved. I’m not sure what happened, but I’m back in business. i’ll keep my fingers crossed. Thanks.

  • Bill Parker

    December 17, 2009 at 2:14 pm

    Even removing the Kona card hasn’t helped. When I trash preferences, I’m fine for a while, but then it starts again. I edit for a while, but I get the spinning ball before long (during playback) and I have to wait about a minute before it will start playing back again. Do you think it makes sense to reinstall FCP Studio?

  • Martin Phillips

    December 17, 2009 at 2:23 pm

    Bill – check that one of your memory modules isn’t playing up. I had the same recently and found that one of mine was giving ECC Errors. You can check by going to Apple > About this Mac > More Info > Memory (You can see the status). If it is this – just remove the bad module and you should be fine.

    Hope you find a way out of this.

    Martin.

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