6 Replies Latest reply: Feb 23, 2013 12:58 PM by W. Richard Glendon
mrobumc Level 1 (0 points)



So far m experience with FCPx is just awful. Constantly freezs. Constantly resarting. I've moved all of the files onto an external drive fun off of my firewire port. Didn't help. Deleted everything and reloaded. Didnt' help. Deleted previous version of FX Express. Nothing improved. Tried turning off the background rendering. Didn't help. All software up to date. iMac 2.66 GHz Intel i5, 4 GB 1067 MHz DDR 3. I should NOT be having this much trouble. Help me. Any ideas?

Final Cut Pro X, Mac OS X (10.7.3), iMac
  • andynick Level 5 (4,925 points)

    This is my pet checklist for questions regarding FCP X performance - you may have already addressed some of the items but it's worth checking.


    Check the spec of your Mac against the system requirements:



    Check the spec of your graphics card. If it's listed here, it's not suitable:



    Make sure you're using the latest version of the application - FCP X 10.0.3 runs very well on my 2009 MacPro 2 x 2.26 GHz Quad-Core Intel Xeon with 16 GB RAM and ATI Radeon HD 5870 1024 MB. I run it with Lion 10.7.3.


    Check that you have at least 20% free space on your system drive.


    If you have not already done so, move your Projects and Events to a fast (Firewire 800 or faster) external HD. Make sure the drive's formatted OS Extended (journalling's not required for video). You should always keep at least 20% free space on the Hard Drives that your Media, Projects and Events are on.


    If you are getting crashes, there is some conflict on the OS. Create a new (admin) user account on your system. Do NOT import any of the settings etc from the old account - simply use FCP X from there - if it runs a lot better, there's a conflict and a clean install would be recommended - but remember, if you reinstall the system, and then use Migration Assistant (or anything else) to import all your old settings etc etc, you may well be importing the cause of the conflict in the first place.


    Keep projects to 20 mins or less (about half that for Multicam). If you have a long project, work on short sections, make them into Compound Clips and then paste these into a final project for export.


    If you ever experience dropped frames, I strongly recommend you use ProRes 422 Proxy - it edits and plays back like silk because the files are small but lightly compressed (not much packing and unpacking to do) - but remember to select 'Original or Optimised Media' (FCP X Preferences > Playback) just before you export your movie, otherwise it will be exported at low resolution.


    If you have plenty of processor power, for the ultimate editing experience, create Optimised Media - most camera native files are highly compressed and need a great deal of processor power to play back - particularly if you add titles, filters or effects. ProRes 422 takes up much more hard drive space but is very lightly compressed. It edits and plays back superbly.


    Hide Audio Waveforms at all times when you don't need them (both in Browser and Storyline / Timeline). They take up a lot of processor power. (Use the switch icon at the bottom-right of your timeline to select a format without waveforms if you don't need them at the moment, then switch back when you do).


    Create folders in the Project and Events libraries and put any projects you are not working on currently, in those folders. This will help a lot. There's a great application for this, called Event Manager X - for the tiny cost it's an invaluable application.



    Unless you cannot edit and playback without it, turn off Background Rendering in Preferences (under Playback) - this will help general performance and you can always render when you need to by selecting the clip (or clips) and pressing Ctrl+R.


    The biggest single improvement I saw in performance was when I upgraded the RAM from 8 GB to 16.


  • Prof. Torg Level 1 (0 points)

    Mmm. Thanks! I've got a 77 minute project I'm working on all at once. Would a solution be to divide into 4 different parts, export those parts as quicktime files and then import into one big project for final export?


    I appreciate your help.



  • FrustratedFCPXguy Level 1 (0 points)

    What is happening to you happens  to many of us.  I am hopeful  that sometime in the next month or so they announce new Mac Pro's and a newer version of FCPX   to eradicate this issue.  We need to remember  that FCP 7  was not faultless  but FCPX is  a pain because  so many of us need to rebooot  so often to get the freezing to go away.   Plugins  which most of us have can cause issues but  if we did n't need the plugins we wouldn't  have them.

  • ClioPad Level 1 (0 points)

    Just got my new iMac.



    3,4 GHz Quad-Core Intel Core i7, Turbo Boost 3,9 GHz

    16 GB 1600 MHz DDR3 SDRAM - 2 x 8 GB

    3 TB Fusion Drive
    NVIDIA GeForce GTX 680MX med 2 GB GDDR5


    CLEAN install.


    Downloaded the 30 day trail of FCPX.


    It freezes ALL the time, trying to edit a 6 minute long GoPro file.

    Well, if it's not working better than this I will stick to Premiere Elements, better than a constant feeze and a power button reset every 2-5 minutes.

  • mrobumc Level 1 (0 points)

    I cured this problem (or at least reduced it) but getting a 2 TB external drive at used the Firewire 800 port to attach. Then, made sure that my original files were on and saved to the external drive. Then, the main film to edit should be worked on from your internal HD. It seems that the processor and hard drive can't process fast enough if the files are on the internal drive, processing and rendering to the internal drive. Evidently, that's the trick.

  • W. Richard Glendon Level 4 (1,015 points)

    ClioPad wrote:


    Just got my new iMac.



    3,4 GHz Quad-Core Intel Core i7, Turbo Boost 3,9 GHz

    16 GB 1600 MHz DDR3 SDRAM - 2 x 8 GB

    3 TB Fusion Drive
    NVIDIA GeForce GTX 680MX med 2 GB GDDR5


    I don't think that being in good company will be much help but, if you haven't already, you should read as much as you can stand of this thread


    sorry to bring discouraging news


    dick glendon