FCP X: Advanced Trouble-Shooting

Posted: September 27, 2013


Most of the emails I get each day revolve around trouble-shooting. When Final Cut Pro X starts acting up, the two best things to do are:

  • Trash Final Cut Pro X preference files
  • Do a Safe Boot on your computer

In most cases, one of these two will fix whatever’s wrong and get you back on your way.

NOTE: Here’s an article that describes how to do both of these.


However, sometimes we need to dig deeper to figure out what’s wrong. And that’s what this article is about. I went back through my emails and started cataloging problems that readers have reported, and rephrased them into questions. Then, I went rooting around into the dark corners of Apple Support to find the answers.

In a Question and Answer format, here’s what I learned.

= = =

Q: Periodically, my Final Cut Pro X system slows down. What could be causing this?

If your system has always been slow, it is generally because you don’t have enough RAM, or your computer is too old to keep up with the latest video formats.

Assuming your system was working fine, but now is slower, trash preference files and do a Safe Boot. If trashing preferences and a Safe Boot didn’t fix things, life gets murky because most of the time the problem is specific to a particular clip, render file, or system component.

If this is the case, here are some ideas to consider:

  • Editing with a minimum of RAM can slow your system down. The best thing you can do to improve performance is add more RAM. Personally, I recommend 8 GB because it is a good compromise between cost and performance. However, FCP X will use all the RAM you’ve installed on your system.
  • Some video codecs are harder to edit than others. ProRes and DV are easy. AVCHD and H.264 are hard. Switching to a different codec may bog down your system because it is inherently harder to edit. (“Hard” means that the math involved in the codec is very complex, which requires more computing power to playback in real-time.)
  • Editing larger image sizes or faster frame rates requires more computing power. In other words, you will need a beefier system if you are editing large image sizes, faster frame rates, in camera native formats.
  • Delete all render files by selecting the Project in the Project Library, then go to File > Delete Project Render Files and delete All Render Files.
  • FCP X aggressively uses the GPU (Graphics Processing Unit). Upgrading to a better GPU can make a difference; but not as much of a difference as increasing RAM to at least 8 GB.
  • Reduce the number of applications that are running at the same time.
  • Reduce the number of background processes that are running. (See the next question.)

NOTE: Deleting render files won’t make your system go faster, but it will clear out space on the drive and, if the drive was getting too full, then by opening up more free space you will get better drive performance. Also, if you are getting an error message about bad media, deleting render files may often fix it.

= = =

Q. Does Final Cut slow down when it is doing something the background?

Final Cut has full control over all its background processes. So, if you start editing, FCP X pauses everything running in the background. This means you always have full access to your entire system when editing. But it also means that jobs running in the background take longer.

But, FCP X can’t control background processes running from other applications. In which case, either canceling that process, or waiting for it to finish will improve editing performance.

Your computer has a finite amount of power. The more software that is tapping into that power at the same time means that each individual software package has less of it to use.

= = =

Q. My computer slowly slows down over time. Why?

You may have a RAM leak. This is where an application is not properly managing memory and RAM that’s supposed to be available to other applications is locked up.

The easiest way to fix this is to restart your computer to reset all RAM. Then, only run the applications you need for editing. You can isolate the problem by watching to see if one particular app causes the slow-down, then contact the developer to see if they have an update.

= = =

Q. What parts of Final Cut operation are RAM dependent?

Well, actually, all of them. Final Cut thinks of RAM as a super-fast hard drive. It will load everything it can into RAM to speed things up.

NOTE: You and I think of hard drives as being very fast. To the CPU, the hard drive is like running in molasses, in January, um, wearing snow shoes. The CPU wants to avoid the hard disk as much as possible.

Large projects require more memory – not surprisingly – in order to store thumbnails, waveforms, metadata, clip information and so on. Also, projects with larger image sizes or frame rates take more memory.

When there isn’t enough memory, the operating system does “page swaps,” where it saves sections of RAM to the hard disk when it isn’t needed, then “swaps” it back from the disk into RAM when it is. The smaller your RAM, the more frequent the page swaps and the slower the overall operation of the system.

= = =

Q. Is there anything I can do with my storage to speed things up?

Yes, lots.

  • USB 2 drives may be very cheap, but they are not fast enough for video editing. Don’t use them.
  • The fuller a hard disk gets, the slower it goes. My recommendation is to maintain at least 20% free space on any drive used for editing.
  • Both USB 2 and FireWire slow down as you daisy-chain more devices together. Try to limit the number of drives daisy-chained to no more than five. (Daisy-chaining is not a problem with Thunderbolt, which limits the total number of devices in one chain to six.)
  • If you are powering the drives from the FireWire or USB bus – that is, they are not plugged into AC power – the more devices daisy-chained together the less power each receives and the slower they go.
  • A rule of thumb about ProRes 422 (the default optimization and render format) is that one HD video stream (or one angle in a multicam clip) is about 18 MB/second.
  • A rule of thumb about hard drives is that one drive can transfer data to or from the computer about 100 MB/second. So, if you are planning a six camera multicam shoot, that’s about 120 MB/second, which means you can’t edit it using a single hard drive.
  • The speed of a USB 3 or Thunderbolt device is determined by the number of drives it contains, not the protocol. So, a 2-drive Thunderbolt RAID will be roughly 200 MB/second. A 4-drive Thunderbolt RAID will be roughly 400 MB/second.

= = =

Q. Does the version of the operating system impact performance?

Yes and no.

Final Cut Pro X runs fine on OS X 10.6.8 and above. However, Apple is always improving performance with each iteration of the operating system. In general, Apple recommends upgrading to the latest version of the operating system.

Personally, I have three edit bays in my office. One is running 10.6.8 and the other two are running 10.8.5, as of the date of this writing.

= = =

Q. If a project database becomes corrupted, how can you tell Final Cut Pro X to open a backup?

Final Cut should open the backup automatically.

If it doesn’t, you can replace the current project with a backup version manually.

  • First, and VERY important, quit Final Cut Pro X.
  • On the drive containing the corrupted project, open the Final Cut Projects folder.
  • Open the Project folder that you want to fix.

  • Delete “CurrentVersion.fcpproject” – this is the database for that Project.

NOTE: All FCP X projects are stored in a database named “CurrentVersion.fcpproject” There is one database for each project and the database is stored in the Project folder. It is critical that you open the appropriate Project folder to prevent deleting the wrong Project database.

  • Open the Backups folder and drag the most recent backup database up one level into the Project folder.

  • Rename the backup database to: “CurrentVersion.fcpproject
  • Restart Final Cut Pro X and your project should start working.

Keep in mind that the backup may not contain your most recent edits. So you may need to redo a few of them. Also, if the new Project fails to open, the backup itself may be corrupted, so repeat this process using an older backup file.

Also keep in mind that if a project file is frequently becoming corrupted, that’s a good indicator that there is something else wrong with your system; such as a failing hard disk or a hard disk that’s too full. If you are getting lots of corrupted projects, its time to visit Apple for a hardware checkup.

= = =

Q. Can you put too many clips into an Event?

Yes, but the number of clips supported by an Event is in the thousands. Still, it is good practice to keep the number of clips in an Event to a reasonable number in the hundreds. If you have lots and lots of clips to manage, spread them across multiple Events instead of one big Event.

= = =

Q. I want to trash a 3rd-party effect/filter/transition/generator. Where do I look?

All effects in Final Cut Pro X are actually Motion templates. And all Motion templates are stored in one place:

  • Home Directory > Movies > Motion Templates.

Within the Motion Templates folder there’s a folder for each Effects category. Open the category folder containing the effect you want to delete and delete the entire folder named for the the effect you want to remove.

= = =

Q. But, when I delete an effect, it keeps coming back.

Certain effects, and the ones by FX Factory come instantly to mind, have their own installer/loader. When FCP X starts, it asks the loader to check over all the effects to make sure everything is installed correctly. If the loader discovers that an effect that had been previously installed is missing, it reinstalls it.

Which kinda isn’t what you want to have happen.

Where the developer supplies a loader, open the loader application – such as FXFactory stored in the Applications folder – and delete or disable the effect from there.

= = =

Q. If two drives are cloned so that they have the same media and folder structure, then given to two different editors, can I share projects by simply copying the project database between drives?

Yes – provided the Project database is stored in a folder named after your Project and the database itself is called “CurrentVersion.fcpproject”

Keep in mind that two editors can not work on the same project at the same time and reconcile changes. Only one editor can make changes to a project at a time. Also, if one editor adds effects that require rendering, the other editor will also need to render the Project.

= = =

Q. When I capture a file from my camera, I keep getting a “file unlinked” message every time I reopen the project. What’s happening?

There are several reasons why a file can become unlinked, but it starts by not copying the file into the Event. Files which are not copied into the Event folder are called “Reference files.” It is easy for a reference file to become unlinked:

  • You renamed the folder that contains the source file on your hard disk
  • You moved the folder containing the file on your hard disk
  • The hard disk containing the file is off-line, or just turned off.

NOTE: Final Cut Pro X handles renamed files a lot better than FCP 7. If you rename a file in the Finder, but don’t change its location, it will go offline. However, when you quit Final Cut and restart it, FCP X will automatically find the renamed file. This is because FCP X tags each file with an invisible file ID, which FCP X uses to reconnect to files that have changed names.

However, there’s also a sneakier reason a file goes off-line: If you are capturing a file directly from the camera – which I don’t recommend – and the file is large, FCP X processes that file in the background. Specifically, it transfers it from the camera to the Event folder, calculates thumbnails and waveforms and, if you request it, optimizes it. For large files this can take a long time.

So long, in fact, that you forget that FCP X is processing files in the background.

Thus, when you quit FCP X, the file is not fully transferred from the camera to the hard disk. And a partial file shows up as unlinked.

My STRONG recommendation is to always transfer files from the camera to the hard disk before doing any work with it in FCP X. Then, import all files once they’ve been transferred to the hard disk.

Here’s an article that explains this in more detail.

= = =

Q. Aside from saving time, is there any advantage to compressing files in FCP X, rather than using Compressor?

First, FCP X uses the same compression engine as Compressor. So, given the same settings you will get the same results. However, you have much more control over compression using Compressor.

If you choose File > Share > Master File and your Project uses ProRes, exporting a project bypasses compressor totally. This is the fastest way to get a project exported from Final Cut Pro X.

If you choose File > Share > Master File and your Project uses a combination of ProRes and other formats, the other formats will be exported through compressor and converted to ProRes 422 during the export.

= = =

Q. Is there a video format that works better for monitoring on a video monitor than another?

In general, I-frame-based video formats are better than Long-GOP-based formats. These two terms describe how media is compressed. I-frame formats, generally, have higher quality, while Long-GOP formats, generally, have smaller files.

Here are some selected formats and how they are compressed:


  • DV
  • DigiBeta
  • AVC-Intra
  • ProRes (all versions)
  • DNxHD


  • HDV
  • H.264
  • MPEG-4

My general recommendation is to optimize all Long-GOP formats when you import them, even though this will create much larger file sizes.

= = =

I hope these tips help you keep your system running at peak efficiency. And, if you discover other ideas that solve problems for you, please add them to the comments below.

14 Comments to “FCP X: Advanced Trouble-Shooting”
  1. sofia says:

    Hello Larry, thanks for your answer.
    i try Trash Final Cut Pro X preference files and do a Safe Boot.
    But the video export still with noise. Im export using H264.

    Thanks so much!

  2. pfflahe@carrollk12.org says:

    Larry, I used a Toxic Title from Digital Juice on my timeline in FCPX project and the timeline causes my FCPx to crash it won’t open FCPX. I trashed preferences and did a safe boot but to no avail. I had to go into my finder and go to the project file on the external HD and delete the project to get FCPx to open. I couple projects before this one I had some problems with a Noise Industry plug-in which would not let me use compressor. I eventually dumped the effect from the time line . I’m hoping that this is not a bug between FCPx and the plug-ins.

    • Larry says:


      It would be nice to say that all plug-ins work perfectly. However, we both know that software has bugs. So, at this point, it would be safe to say that these plug-ins don’t like something on your system.

      I just realized that I have not written about how to remove plug-ins from FCP X. I’ll work on this for this week’s newsletter.


  3. Stuart Davis says:

    Hey Larry, wanted to share this trick I discovered that helped me and may help others.

    I was unable to export / share a particular project in FCPX. Not sure why, but every time I tried to export / share, I got this error message-

    Video Rendering Error: -50 fcpx

    and then the export / share would fail. I was confused, all my other projects exported fine, and I’ve never had an issue on an export. I tried lots of stuff, but somewhat surprisingly what ended up solving the problem was I simply selected the entire project in the timeline, and then made a compound clip of the whole thing. Once I did that, it exported fine. I don’t know why this worked, but it did. And it was so simple and easy and it was a lot better than some of the more involved and time-consuming trouble-shooting that I was about to attempt next. So, hope you’ll share this if it helps others. Thanks for your great work !

  4. Johan says:

    Hi Larry
    I have a mysterious problem here. Suddenly I can’t set my FCP X to work with Proxy any more, I also can’t set it to Better Performance – intact if I close down my library – its there when I start FCP X again ( together with the empty default one ) . I have had proxys generated for all my projects btw

    I have trashed preferences, but that doesnt help. All other stuff like repairing permissions, and similar as well. Do you know what file is storing the interface settings of FCP X? the FCP preferences does that , but there are some other prefs as well that keeps these kind of interface settings? I can change Display and Channels, but not Quality and Media. I don’t think I should mess with the DB in the events folder really cause they are more describing the actual editing decisions.

    mny tnx

    • LarryJ says:


      VERY strange. If this appears in one project, but not another, it would seem to me to be a corrupted project. Try creating a new one and see if FCP X behaves properly. (You should be able to copy and paste media between projects.)

      If not, its time to call Apple Support for help.


  5. Claudia says:

    Hi Larry,

    I have a big problem here. I use FCPX 10.1.3 in two Macs, an iMac Core i5 with 32Gb and in a MacBook Pro Core i7 with 16 Gb. Both with OSX 10.9.5.

    All my projects are in external HDs. I use the Neat Video plugin to remove noise from my footage.

    My problem is: the iMac takes about 20 hours to render a film with 45 minutes. When I take the HD with this project and connect to the MacBook Pro, FCPX dont recognize the render files and do the render all over again but takes only one hour.

    When I share my film after render in the iMac, my film dont have any noise, the plugin works very well. When I open the same project in MacBook Pro, the film dont have the noise in the viewer window but the shared film have all the noise again.

    It seems that FCPX in the Macbook Pro render my footage but ignore the Neat Video plugin and the iMac dont do that.

    What can I do?

    Thanks for your help.

    • LarryJ says:


      First, this sounds like the render files are not being stored where you think they are. The render files are fully compatible between the two systems. The only reason they would not be recognized from one system to the next is because they don’t exist on your external drives.

      Please check very carefully that you are storing the files in the correct place.

      Second, contact the folks at Neat Video about the differences in output. I suspect that a setting is incorrect and they should be able to help you with that.


  6. JoT says:

    FCPX seems to have some of a set of my photos on a “blacklist”. When those few photos are added to the edit track, they look like corrupted files, but appear fine when viewed with other methods including FCPX – view in browser. I have tried shifting the files onto the desktop instead of hard drive, which didn’t change the problem.

    What should I do?

  7. Norex says:

    Hello Larry! Sorry for my englsih, I made a hackintosh,My Final Cut X 10.9 projects and events on principal SSD 600 MB/sec SSD 500 GB. The footages(prores 422 HQ,MOV) on SSHD(Leave on place, doest import to the ssd) 200 Mb/sec 2TB. This is Intel Core i7-3930K 6 core 3.2GHz(3,8), 32 GB RAM 2166 MHZ, GTX 780 Titanium 3GB. I use Mavericks 10.9.5, the problem is if I want to use neat video(noise reduction) plugin, my processor usage only 35%, but if I use stabilition 60-70%. The same with MPEG Streamclip, if I use usage 30%, but if I use AVCHD to MOV Free program from appstore the usage 100%, why is this ?

    • Larry Jordan says:


      For programming reasons that I don’t understand, not all applications use 100% of the processor at all times. Even with fast RAM and fast hard disks, there are inherent delays in the system.

      While measuring CPU load is a good indication of how well things are working, it is not the sole criteria for speed.


  8. Cameron says:

    Hi Larry,

    I have a problem that i cant seem to find an answer to.
    My FCPX crashes on start up during loading of the projects library.
    My crash report says that it seems to be caused by a Motion Effect and i cant find a way around this.
    if you need more info to help solve this please let me know.

    the relevant line is
    5 com.apple.Motion.effect 0x0000000119585e6d -[FFMotionEffect _makeLoadedDocReady] + 427

    Thank you.

    • Larry Jordan says:


      First, delete FCP X preferences by pressing Option and Command while restarting the application.

      Second, create a new library and make sure that FCP X does not crash. If it does, reinstall the application.

      Third, reopen the project that crashes. If, after trashing preferences, FCP X crashes again, you’ll need to contact Apple Support. Hopefully, they will have a way to disable the offending effect.

      Let us know what finally got this to work.


Your thoughts are welcome


Larry Jordan & Associates, Inc
Video Editor
Experience Revolutionary Video Editing Techniques Through Final Cut Pro X Tutorials, Adobe Video Editing Classes, Final Cut Pro Classes, & A Variety of Other Software! Larry Jordan, Internationally - Renowned With 35+ Years Experience, Delivers Final Cut Pro Training & Other Software Via Live Webinars, Hosts Internet Radio, Podcasts, & More!
Los Angeles, CA
United States of America

Google Privacy Policy

Follow Larry

  • Facebook
  • Twitter
  • YouTube
  • Flickr
  • Google+