2 Replies Latest reply: Oct 24, 2012 9:42 AM by andynick
LeikoLyn Level 1 Level 1 (0 points)

Hey so I am a upcoming editor and I use a number of programs... But FCPX just so happens to be one of my fav. Anywho I need help! Everytime I begin working, my system instantly crashes and slows down! I've done everything that I could think of and nothing works! Please help me!!


Final Cut Pro X, Mac OS X (10.7.5)
  • 1. Re: Crashes EVERYTIME!
    DJ Duke Level 1 Level 1 (55 points)

    You have to give us more specifics of what you are doing and what version of FCPX you are using.  What computer and OS are you using?

  • 2. Re: Crashes EVERYTIME!
    andynick Level 5 Level 5 (4,840 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.

     

    Make sure you're using the latest version of the application - FCP X 10.0.6 runs very well on my 2 x 2.4 GHz 6-Core Intel Xeon with 16 GB RAM and ATI Radeon HD 5870 1024 MB. I run it with Mountain Lion 10.8.2.

     

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

     

    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.

     

    Check the spec of your Mac against the system requirements:

    http://www.apple.com/finalcutpro/specs/

     

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

    http://support.apple.com/kb/HT4664

     

    If you are getting crashes, there is some conflict on the OS. Create a new (admin) user account on your system and use FCP X from there - if it runs a lot better, there's a conflict and a clean install would be recommended.

     

    Keep projects to 20 mins or less. If you have a long project, work on 20 min sections then paste these into a final project for export.

     

    If you 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.

     

    Do not use Proxy for Colour Correction or for shot selection (especially if focus is in question) as the image quality is bad.

     

    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.

     

    I find I can run my XDCAM EX and Canon 5D mk iii footage natively, without using Proxy or ProRes 422, although ProRes 422 is best for colour correction.

     

    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.

    http://assistedediting.intelligentassistance.com/EventManagerX/

     

    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.

     

    Before I upgraded to the new MacPro I ran a 2009 machine, and the biggest single improvement I saw in performance was when I upgraded the RAM from 8 GB to 16.

    Andy