FCP X: Avoid Corrupted Libraries [u]

Posted on by Larry

Logo-FCPX.jpg[ Updated 6/11/2017 to add information about maximum clip limits in FCP X. ]

Nothing is worse than opening a Library and discovering a problem, or not being able to open a Library at all. The principle reason for a corrupted Library is running low on space, however, Final Cut Pro X also has an internal limit to the number of clips that can be store in a library. Either way, the first thing to consider is that you might be running out of space.

NOTE: Here’s an article that explains how to determine hard disk free space.

However, there’s also the perception that a Library is corrupted, when, in fact, it isn’t. This can happen when you accidentally open a clip in the Timeline, instead of editing a clip in the Timeline.

Finally, sometimes a Library acts like its corrupted, but it really isn’t. Instead, Final Cut’s preference files are screwed up. Fix those and, voilá, your Library is back to normal.

This article talks about all of these.

FINAL CUT LIBRARIES HAVE LIMITS

All versions of Final Cut Pro X have an internal limit to the number of clips that can be stored in a Library. (This includes all versions from FCP 10.0 through 10.3.4; hopefully, Apple will increase this limit in future versions.)

NOTE: To the best of my knowledge, this limit still exists in FCP X 10.4.x.

That limit depends upon the amount of RAM in your system, as well as a variety of other technical factors, but, in general, consider the maximum number of clips to be between 3,000 and 3,500 assuming you have 16 GB of RAM. If you need to work with more clips than that, spread them between multiple libraries.

If your library already exceeds this limit, or you guess that it does, create a new library and move events and clips from the over-full library to the new one. Here’s a video that explains how:  Copy or Move Media, Events and Projects into New Libraries

TRASH FINAL CUT PRO X PREFERENCE FILES

“Preferences” sounds so innocent. But the preference files that Final Cut creates lie at the heart of the smooth operation of the software. If these preference files are screwed up – and it isn’t your fault if they are – then Final Cut is not going to work well, if at all.

Trashing them is easy and should always be your first trouble-shooting step when FCP X acts up: Press and hold both the Option and Command keys when starting FCP X from the Dock.

Trash001

Click Delete Preferences and, if everything goes well, when you reopen your Library from the Finder (as the Recent Library list in the File menu of Final Cut will be cleared) your Library and everything in it is good to go.

Here’s an article that discusses trashing preferences in more detail.

MAINTAIN SUFFICIENT FREE SPACE

Like all video editing software, Final Cut Pro X needs lots of free space on your hard disk to operate efficiently. I strongly recommend ALL your hard disks contain at least 20% free space.

The reason this is important is that if your hard disk runs out of free space during editing, your library file can become corrupted. This principally applies to the hard disk where the library is stored, but if the boot disk gets too full, that can cause problems as well.

When the hard disk storing the library gets too full, it can cause the library to be saved incompletely. This may also prevent a backup file being saved. A lack of free space could also interrupt copying items between libraries which would leave the library in an incomplete state.

Here’s an article that explains how to move libraries, media, events and projects.

EDIT CLIPS IN PROJECTS

Danger

One of the unsung features of Final Cut Pro X is the ability to edit multicam, compound and media clips in the Timeline directly, as opposed to first editing them into a project. This is called “Opening a clip in the Timeline.”

In the case of multicam and compound clips, this is a good thing. In the case of individual clips, this can cause problems.

NOTE: Editing clips directly is done by right-clicking the clip in the Browser and selecting “Open in Timeline.”

For example, you might open a clip with “Open in Timeline” and begin editing thinking that you were inside a project. But you aren’t. Suddenly, you notice that your project is “gone” or doesn’t include the previous work you did when you next re-open the library the next time. This can lead to feelings of panic and terror.

If you feel that your recent work is missing, select each of your longer clips – one at a time – then use the “Open in Timeline” command to see there if your work is actually inside the clip, rather than inside the project.

Open in Timeline is a very powerful feature of FCP X as it allows you to combine multiple clips into a single clip. Still, this is very different from other editing systems and can get you in trouble if you don’t realize that you are not editing the clip where you think you are editing it.

Here’s an article that explains “Open in Timeline” in more detail.


Bookmark the permalink.

15 Responses to FCP X: Avoid Corrupted Libraries [u]

  1. Tomas says:

    I’m trying to open a library that was working perfectly until it suddenly decided to stop working.

    It just freezes while loading (the loading bar doesn’t move) and I get the “not responding” in the Force Quit Applications window.

    I’ve tried deleting the preferences, I’ve tried creating a new library and copying my library’s files in there, i’ve restarted, i’ve tried it on a different computer, I tried it from the desktop instead of from the external drive. Nothing is working. My FCPX is up to date.

    What else can I do?

    Thanks!

  2. Jes Webb says:

    Hello Larry,

    I had an usual one today, but all is well.

    After watching your FCPX 10/3 training I bought a while back, I wanted to change my content structure and the way I organize my files, so I opened a rather large library that was specific to one client and contract with about 20 projects. It was already formatted for the 10.3.2 build though I hadn’t dug into it since November. As I opened it up FCPX told me a particular project was corrupt, and I could go to a backup or continue. I continued because the project was inconsequential and I just deleted it after FCPX was open. But then I opened FCPX again a few minutes later and the same thing happened with a new project. After about 5 projects were deleted I saw what was coming so I went through your suggestions. above.

    I ended up making a new Library on a new drive, moving my content over with a “select all”, and then moved the remaining projects over one at a time from both the Library that was corrupt, and a previous backup. Everything seems better now.

    Now, if I can just get organized.

  3. Doug Benn says:

    Hi Larry,

    You mention in the article that the limit is 3000-3500 clips per library if you’re running 16GB or RAM. If my system is running 32GB of RAM or more, does this number double or get higher at all or is it just a best practice to not exceed 3500 clips per library?

    Thanks!

    • Larry says:

      Doug:

      To be honest, I don’t know the answer. My GUESS is that the clip count will vary.

      However, as “best practice” I recommend keeping your clip count before 3,500.

      Larry

  4. mark.suszko says:

    Two questions:

    Is it “wrong” to make a new library and project file, for each and every program I make? Depending on the nature of the work, and how much footage there is, I either import/copy the relevant video files or leave them where they are on the RAID and have FCPX reference them externally.

    I like my library uncluttered and without a bunch of extraneous irrelevant stuff in it.

    The nature of my work is ephemeral, so my libraries and projects get nuked about a month after we have an approved master (Though I usually also save off a clean version with separate audio stems and no graphics, just because I’m not a complete noob, 🙂

    Something that happens to me from time to time is, FCPX seems to randomly “forget” it imported my clips.

    I offload my P2 card to a folder in the RAID before I open FCPX. I remove the P2 by closing and ejecting, and then import footage from the folder in the RAID, and all is well.

    Yet, occasionally, mid-edit,FCPX crashes and when it comes back, the bin erupts into crimson picons warning some or all the media is gone. The “reconnect-media” function stays grayed out or does nothing, and so instead I hit “import” from the folder on the RAID and everything is restored again, my timeline comes back. But… come time to “share” out a master file, that option is grayed-out, and stays grayed-out even after I force a render of the timeline.

    The picons in the bin will show the little “camera” mini-symbol and if I leave it alone, these will turn into little clocks, showing the footage is re-importing. This takes forever when you’re on deadline to air.

    This has tripped me up on deadline jobs a time or two and I hate it, but can’t quite figure out how and why it happens. Or how to recover from it faster.

    • Larry says:

      Mark:

      It is never “wrong” to make a new library for each program, though, totally acceptable to have multiple projects (timelines) related to that program stored in a library. This is how I do most of my training. I keep my libraries small and focused.

      I have never heard of the problem you report – I strongly recommend you contact Apple Support when you have an example so they can track this down.

      Larry

      • Lydia Robertson says:

        Hi Larry, I hope you are well. I just experienced this forgetting imported (greyed out) clips for the first time.Like this fellow about, I just reimported and the connectios were made again instead of the material being imported twice. Weird.

  5. Jon Williams says:

    I had the same problem this afternoon.

    My original library wouldn’t open, nor would any of the FCP X-generated backups, although a backup I’d made manually the night before would open. But I was in danger of losing a lot of work from this morning. Other libraries not part of this client’s project would open, too. So I copied both the original library and the latest FCPX-generated backup (neither of which was working on my iMac) to the drive that contains a backup of all my media files, then took that to my MacBook Pro. The original library crashed it as well, but the FCPX-generated backup, once free from the iMac’s icy embrace, didn’t crash FCP X on the MacBook Pro.

    It did pause to tell me that the library from which it had been created was missing and that I would need to save my backup library to another location. I did that and it loaded up fine, but reported that my storage locations (on the iMac) couldn’t be found. I changed them to the backup drive and all was good, though I would have been in need of relinking to the media files on my backup drive.

    Instead, I brought the newly saved library backup back to the iMac and launched it. It didn’t crash FCP X on the iMac. Instead I had to change the storage locations back and then relink to the media files on the iMac. Not at all sure what was happening but it’s all (knock on wood) working now. I did have a lot of unused media files and preliminary projects in my project, so I’ve created a new, empty library and dragged the projects I still need into it. That gives me a project with a lot less garbage to wade through or worry about.

    • Larry says:

      Jon:

      Thanks for this write-up. While FCP X does not have an internal “limit” on how many clips it supports, the amount of RAM does affect how big your library can get.

      It is a good idea to keep libraries below around 3,000 clips just to be safe.

      Larry

Leave a Reply to Tomas Cancel reply

Your email address will not be published. Required fields are marked *

Larry Recommends

Final Cut Pro X 10.4

FCPX Complete

Edit smarter with Larry’s brand-new webinars, all available in our store.

Access over 1,900 on-demand video editing courses. Become a member of our Video Training Library today!

JOIN NOW

Subscribe to Larry's FREE weekly newsletter and save 10%
on your first purchase.