Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP taking too long to open

  • FCP taking too long to open

    Posted by Jenny Himmelrick on May 12, 2010 at 2:31 pm

    I’ve been editing some big projects lately and my final cut is taking at least 15-20 minutes to open up anymore. What can I do to help it out so that I wont crash my system? I’m going to be uploading some Apple ProRes footage soon and I just know that those files are going to make it take even longer to open the program. I read somewhere about deleting rendered files or changing something about RT? I dont really understand all that stuff…help, please!

    Jenny

    John Fishback replied 13 years, 3 months ago 5 Members · 8 Replies
  • 8 Replies
  • Tom Bucknall

    May 12, 2010 at 3:26 pm

    Are you opening a project when you open FCP, and if so what size is the project you are loading. Typically FCP will not work well with projects >100MB.

    Tom

  • John Fishback

    May 12, 2010 at 3:43 pm

    Never hurts to trash prefs and repair permissions.

    John

    MacPro 8-core 2.8GHz 8 GB RAM OS 10.5.8 QT7.6.4 Kona 3 Dual Cinema 23 ATI Radeon HD 3870, 24″ TV-Logic Monitor, ATTO ExpressSAS R380 RAID Adapter, PDE enclosure with 8-drive 6TB RAID 5
    FCS 3 (FCP 7.0.2, Motion 4.0.2, Comp 3.5.2, DVDSP 4.2.2, Color 1.5.2)

    Pro Tools HD w SYNC IO & 192 Digital I/O, Yamaha DM1000, Millennia Media HV-3C, Neumann U87, Schoeps Mk41 mics, Genelec Monitors, PrimaLT ISDN

  • Jared Levy

    September 28, 2010 at 4:16 pm

    A project I am currently working on, a documentary with roughly 1.5 terabytes of material (Canon 5D Mark II files are exploding this project) is currently 130 MBs… I read in the previous post that projects over 100 MBs slow FCP down a lot. Right now, it is taking an excruciating 45-60 minutes to open the project in FCP. Even when open, it is prone to random shut downs and is constantly lagging.

    Any suggestions about ways to minimize the project? I have a lot of timelapses with thousands of photos. I am sure that is hurting performance but I am not sure how to rectify the issue. Should I delete all render files for the timelapses and only render them at the last moment? Does that even help the project size?

    I have 8gbs of ram and according to my activity monitor, lack of ram is not the issue.

    Thanks so much!

  • Jared Levy

    September 28, 2010 at 5:34 pm

    Just want to update. I created a new project and dumped all of the timelapse material there. That drastically dropped the project weight for the A-camera stuff. As for the timelapse project, it is still very heavy but I plan on exporting out movie versions of each timelapse sequence, thereby reducing the images from thousands to simply one movie file per timelapse. I am hoping I can then import those finished movie files back into the main project.

    If anyone has ideas to further help this out… I’m all ears, but so far so good.

  • Lanny Cotler

    January 13, 2013 at 5:25 am

    I also am finding FCPX to open painfully slowly. I must say that currently all my projects are with still images, not video clips. This it seems is important for FCPX.

    I speeded things up (from 20 mins to 10 mins) by removing all still images greater than 2K pixels wide.

    And I have a permanent catalog of images I need ONLINE of more than 3700 images!

    I’m also experiencing TOTAL COMPUTER (MacBookPro8,3 – 16 GB RAM) LOCKUP that not even Force Quit will remedy. I have to bomb the machine with Power Button crash. Very disconcerting. This happens usually during rendering. Four times in a row the machine froze on 39% in the render window. What gives?!

    While there are many features that I love in FCPX, perhaps I should find another editing software for my work with stills.

    LannyATlcotler.com

  • John Fishback

    January 13, 2013 at 4:28 pm

    I’ve recently had slow down & lockup issues. I found that running Disk Warrior & then Repair Permissions helped considerably. Disk health is apparently very important with FCPX. Also, I use Event Manager X which only opens the event you’re working on.

    John

    MacPro 8-core 2.8GHz, 8 GB RAM, OS 10.7.4, QT10.1, Kona 3, Dual Cinema 23, ATI Radeon HD 5870, 24″ TV-Logic Monitor, ATTO ExpressSAS R380 RAID Adapter, PDE enclosure with 8-drive 6TB RAID 5
    FCS 3 (FCP 7.0.3, Motion 4.0.3, Comp 3.5.3, DVDSP 4.2.2, Color 1.5.3)
    FCP-X 10.0.6

    Pro Tools HD 10 w SYNC IO & 192 Digital I/O, Yamaha DM1000, Millennia Media HV-3C, Neumann U87, Schoeps Mk41 mics, Genelec DSP Monitors, Prima CDQ120 ISDN

  • Lanny Cotler

    January 13, 2013 at 7:27 pm

    I use Event Manager X, too. It’s good.

    I’ve repaired permissions, but don’t have Disk Warrior. Should I get it?

    Lanny

  • John Fishback

    January 13, 2013 at 8:19 pm

    Disk Warrior is a lifesaver. If there’s one program every Mac owner should have, Disk Warrior’s it.

    John

    MacPro 8-core 2.8GHz, 16 GB RAM, OS 10.7.4, QT10.1, Kona 3, Dual Cinema 23, ATI Radeon HD 5870, 24″ TV-Logic Monitor, ATTO ExpressSAS R380 RAID Adapter, PDE enclosure with 8-drive 6TB RAID 5
    FCS 3 (FCP 7.0.3, Motion 4.0.3, Comp 3.5.3, DVDSP 4.2.2, Color 1.5.3)
    FCP-X 10.0.7, Motion 5.0.6, Compressor 4.0.6

    Pro Tools HD 10 w SYNC IO & 192 Digital I/O, Yamaha DM1000, Millennia Media HV-3C, Neumann U87, Schoeps Mk41 mics, Genelec DSP Monitors, Prima CDQ120 ISDN

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