Please help, I have a deadline soon. FCPx is crashing every time I quit. It hangs on stopping background processes when I can not see that there are any, and I have them turned off.
I have done a safe boot, wiped preference, and even created a completely new user on the mac. Nothing helps. Any suggestions would be greatly appreciated.
CCheck the background processes window before you quit. Are you having to force quit?
Yes, having to force quit every time. No background task appear in the manager, yet when I quit I get the drop down saying Quitting Background Processes
WWhat are your syatem specs and has Final Cut ever worked on the system? If you are using a separate medie drive and/or if you have any other drives connected, disconnect them and try a test project from your boot drive.
RUss
mac dave wrote:
Please help, I have a deadline soon.
I would guess you have the latest system, Yosemite and FCPX 10.1.4, right ?
Thank you everyone for your comments and help. We had to push the release back two weeks for many reasons, some of them this issue.
But I thought my solution would be good to know for people. For the record I was attempting to edit at 4k with imported RED files converted to optimized media. What I didn't realize is that some of those clips were actually shot at 5 or 6k. I think that was one problem in and of itself, so I converted my projects to 1080p. Still got memory errors though.
So I think what solved the issue was when I flushed the cache by moving it outside the library. I think FCP had crashed while doing background renders from choking on some of the odd clips. I believe that corrupted some of the cache system, and wasn't fixed even when regenerating the cache files.
So I went to project settings and set the project cache to be outside of my project file in a folder I created. When doing so you are prompted to decide whether or not to move your current cache. I didn't, and this forced it to re-reender all those clips (but not the original optimized or proxy media). This seemed to clear up every problem I was having with Final Cut Running Out of Memory problems. I bet it was the cache, but could have been related to the mixed resolutions.
So I thought this might helpful to others searching this forum, and thanks again for everyone's help!
I am glad you sorted it out. For the record, I really think that your conjecture about a corrupt cache is correct. Mixing resolutions should be no problem.
Crash on quit due to background processes
