Huge Library Cache file, and other file problems

On June 1, I had an issue with a corrupted library (I can't remember the exact message I got), and FCPX created a repaired library for me. That new library seems to function perfectly, I have been using it intensively for the last week. All the old events and projects seem to be it.


Logic tells me that I can delete the old problematic library, and the associated Library Cache package. But I would HATE to do something that I regret, so I thought I would ask here first. Is it safe to trash the first and last items in this folder (pictured below)? Obviously I am especially interested in that almost-4T Library Cache file. How did it get so big? If I have deleted the transcoded files (render, proxy and optimized) files for inactive projects, shouldn't that Cache file be pretty small? Even with the repaired and current Library, the cache file is 293GB. I have searched the internet trying to learn more about that file, I don't see a good explanation, or something that tells me how to slim it down (other than deleting those render etc. files).


Any help would be greatly appreciated. Thanks in advance, Peter


User uploaded file

iMac with Retina 5K display, OS X Yosemite (10.10), 24 gb RAM, 1T SSD internal, i7

Posted on Jun 9, 2017 6:48 AM

Reply
4 replies

Jun 9, 2017 7:07 AM in response to Luis Sequeira1

Thanks Luis. I am so paranoid about throwing away something that is irretrievable that I will wait to hear from at least one more person, but I feel sure you are right. And I would think I could also trash that old damage Library file, does that sound right?


Any thoughts about that other cache file, the one associated with the newer repaired library? It is not nearly as big, not really a problem. Does its size go up and down depending on when I delete render/optimized files?

Jun 9, 2017 7:10 AM in response to Peter Bloch

The first item (.fcpcache) contains computer generated files but unclear to me what is the "last item" you're referring to.


How did they get so big? We'd have to know more about your projects, your setup and workflow to answer. Generally speaking, people tend to delete renders and optimized media from the File menu within the application so they don't accumulate to onerous sizes. They can always be regenerated later if required.


Russ

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Huge Library Cache file, and other file problems

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.