-
FCPX Library gets corrupted after export
Specs first
Late 2013 Mac Pro
OS 10.11.3
3Ghz 8-Core Xeon E5
32GB Ram
Dual AMD FirePro D700
7200 rpm hard drives hooked up via thunderbolt to Mac Pro (Rocketstor 5212)
FCPX 10.2.3Exporting several chunks of an an hour and 45 minute interview shot 5 years ago on Sony Z1u at 1080i. The video was imported via a tape deck and 3 hour and 45min clips/angles were assembled into a multicam. I noticed that if I export a high number of chunks, say 8, and then I attempt to do anything afterwards on my project (such as make a cut, add a marker, even try to quit the app) FCPX hangs. After a while of spinning beach ball, I force quit the app and open fcpx again. This is when the problems start.
Invariably, the library gets messed up. The library takes 3 times as long to open and whenever I try to make a cut, add a marker, or open another project, fcpx hangs again and I need to force quit.
Bear in mind, the library works excellent before export. After the export, I start getting these problems.
Things I have tried:
Deleted preferences, plist, application support, motion templates, etc
Optimized media of HDV clips to try to correct a corrupted file issue
Used digital rebellion’s Pro Maintenance tools. Corrupt Clip Finder throws back no errors, used Quckfix and Housekeeper. Problems remain. Project Repair does throw back a message saying “the library is unfixable and corrupted”.
Uninstalled and re-installed FCPX
Spoke to apple care specialist for 2 hours, no solution.NOTE: This also happened to me on 3 more libraries. On those I was working with 5D2, 5D3, C300 and Sony EX3 footage. Got similar problems as mentioned above.
Anyone got any ideas on what’s causing the corruption? Is it a bug? Anyone else experiencing this? Any advice is welcomed. Thanks
Juan Luis
-
13 Replies
-
Why not just consolidate to a new project? Worth a try and it’s pretty much instantaneous.
-
Hey Bret, thanks for responding. Do you mean to open the corrupt library, drag the projects I need to a new library and then click the consolidate command? Two things I think may be a downside though I am willing to do this if it fixes the issue:
1. Wouldn’t my storage space double in size? I currently have a referenced library, not a managed one.
2. When I try to drag and drop the needed projects to a new library, the corrupt library hangs and can’t move/copy the project to the new location. Any work around that? XML Import screws up all of my color corrections.Thanks
Juan
-
I was thinking more of highlighting the project and doing a file–copy to new project command. I guess it doesn’t matter if you consolidate or not. And fwiw, nope, it will not double the data size, even when consolidated, as long as it’s on the same drive. X uses hard links nowadays. Multiple individual files (NOT aliases) can address the same data. Even if you trash the original file, the data isn’t deleted until the final instance of the hard link is deleted. Hard links are indescernable to the user. They can’t be created in the finder. Only by X. You can test it out by duplicating/consolidating a 500gig project to the same drive in X. It takes mere seconds and the available hard drive space remains the same. Pretty cool.
-
Awesome, thanks for the details. I will test your suggestion and let you know what I find. Gracias
Juan Luis
-
[Juan Luis Lopez Fons] “NOTE: This also happened to me on 3 more libraries. On those I was working with 5D2, 5D3, C300 and Sony EX3 footage. Got similar problems as mentioned above.”
I have never seen or heard of anything even remotely close to this problem.
My advice would be to back up your hard drives and nuke your computer from orbit. It’s the only way to be sure.
https://www.youtube.com/watch?v=aCbfMkh940Q&app=desktop
What I mean is, reformat your hard drive and reinstall from the ground up.
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Haha, well if Ripley suggested it, I guess I should do it then 🙂 Thanks for the suggestion though man… it is an option I may do once I finish this deadline.
UPDATE: I left another HDV project exporting overnight and before I quit the app (Which had been one of the sources of corruption in the past), I decided to purge the RAM from my computer (via an app called Memory Monitor) and when I quit the app, it closed fine and after I reopened FCPX, no signs of corruption.
Is it possible that this was a RAM issue?
Juan
-
I guess it could be? Is your RAM apple RAM or third party?
-
It’s actually apple ram. Mmm, the plot thickens.
Juan
-
Hello Brett, an update: I opened the damaged library, selected the project I wanted to save, clicked on File, copy to a NEW library and after I selected OK, I got spinning beach ball and the app hanged. I eventually force quit the app.
What do you think the problem could be? I am mystified. Thanks
Juan
-
The it should be easy to swap for new RAM. Do you have an apple store near you, or an authorized reseller?
Reply to this Discussion! Login or Sign Up