marjopar

Q: While working in multi camera editing in FCP X, having only 2 angles, after cutting for 30 minutes, the editing starts slowing down gradually until it becomes unbearably slow. Can someone tell me what is wrong?

This is the second time I am using the multicamera editing mode. The first time I used it with 2 angles of HD 720p and it worked perfectly. This time I am working with standard definition vodeo and is giving me this problem.

iMac, Mac OS X (10.7.2), 8GB Ram

Posted on Mar 30, 2012 4:29 AM

Close

Q: While working in multi camera editing in FCP X, having only 2 angles, after cutting for 30 minutes, the editing starts slowing dow ... more

  • All replies
  • Helpful answers

  • by Luis Sequeira1,

    Luis Sequeira1 Luis Sequeira1 Mar 30, 2012 6:04 AM in response to marjopar
    Level 6 (12,682 points)
    Mac OS X
    Mar 30, 2012 6:04 AM in response to marjopar

    The slowdown usually means that there almost no free memory. This is a recurring issue, especially in Lion. Inactive Memory grows while Free Memory dwindles.

     

    If you keep Activity Monitor (it is /Applications/Utilities) open, you may notice that the amount of free memory decreases over time.

    One way to help is to quit and restart FCP X. Also, you may want to get the free FreeMemory application. This can force the release of some of the inactive memory.

  • by andynick,Solvedanswer

    andynick andynick Mar 30, 2012 6:47 AM in response to marjopar
    Level 5 (4,943 points)
    Video
    Mar 30, 2012 6:47 AM in response to marjopar

    This is my pet checklist for questions regarding FCP X performance.

     

    Make sure you're using the latest version - 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.

     

    First, check that you have at least 20% free space on the Hard Drive that your System and 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 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.

     

    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.

     

    If you are short of drive space, use ProRes 422 Proxy (FCP X Preferences > Playback) - but remember to select 'Original or Optimised Media' just before you export your movie, otherwise it will be exported at low resolution.

     

    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.

     

    Move your Projects and Events to a fast (Firewire 800 or faster) external HD (make sure it's formatted OS Extended - with journaled on or off) and run from there.

     

    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.

    Andy

  • by marjopar,

    marjopar marjopar Mar 30, 2012 8:13 AM in response to andynick
    Level 1 (0 points)
    Mar 30, 2012 8:13 AM in response to andynick

    Thanks, this is great help.