Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Green Freeze

  • Posted by Chris Wasmer on October 1, 2008 at 5:50 pm

    Running OS 10.5.2, FCP 6.0.3, QuickTime 7.4.5, 4 Gigs RAM.
    Working on a DVCPRO HD project at 23.98.
    For the past month no problems, but now every 10 – 20 minutes, the canvas goes green and then FCP freezes — “FCP not responding.”
    I tried trashing preferences and repairing disk permissions, but this didn’t help.
    Media is on a FireWire 800 drive with about 1/3 free space left.
    Help! Thank you.

    Chris Wasmer replied 17 years, 7 months ago 3 Members · 18 Replies
  • 18 Replies
  • Jeremy Garchow

    October 1, 2008 at 6:17 pm

    Do you have any capture card or anything to monitor your footage with?

  • Chris Wasmer

    October 1, 2008 at 6:43 pm

    Yes. I am using a Matrox MXO. I disconnected it and still have the same problems.

  • Jeremy Garchow

    October 1, 2008 at 6:48 pm

    Hmm. That green is usally a corrupt file somewhere.

    Do you have still images in your project?

  • Chris Wasmer

    October 1, 2008 at 6:53 pm

    no stills. I slowed down one shot.

  • Jeremy Garchow

    October 1, 2008 at 6:58 pm

    What format is all of your footage?

  • Chris Wasmer

    October 1, 2008 at 7:05 pm

    DVCPRO HD 1080i60. Used Cinema Tool to remove pulldown.

  • Jeremy Garchow

    October 1, 2008 at 9:09 pm

    Hmm. That could be the culprit. How much footage do you have? The easiest way to check for corrupt footage is to make it all offline and then reconnect a handful of files at a time. Total PIA, but it tell you if one of those files went bad.

    Jeremy

  • Chris Wasmer

    October 1, 2008 at 9:25 pm

    I have A LOT of footage. I’ll try and get back to you.

  • Jeremy Garchow

    October 1, 2008 at 10:09 pm

    Sorry, Chris. it’s a pain, I know.

    Jeremy

  • Chris Wasmer

    October 2, 2008 at 1:17 am

    I tried “offlining” the suspect media, but it didn’t solve the problem.
    So I made a new project and duplicated my most recent sequences into it. I then deleted a suspect sequence, and the problem went away!
    I still have media on the drive from this corrupt sequence, and this media is in almost all of my duplicated sequences.
    So it seems that a corrupt sequence was screwing up the project. but i’m not sure…
    My new project has a lot less items in it. So maybe this helped?

Page 1 of 2

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