The Final Cut Pro X CRASH Thread

Hi, I'd like to start a thread for people that experience crashed in Final Cut Pro X.

No other Applications crashes on my Mac Pro. I have never experienced crashes like

I do now with Final Cut Pro X.


During my three hours spend with FCPX it crashed about 8 - 9 times.

The Crash reporter seems to indicate that is related to the functions that use the Video Card acceleration.

It's always OpenCL / OpenGL ...


Please Post if your's crashes, too.

Mac Pro, Mac OS X (10.6.7), 6 Core, 8 GB RAM, Ati 5870

Posted on Jun 21, 2011 11:08 AM

Reply
479 replies

Jan 11, 2012 6:19 PM in response to sfaust439

I am sorry to hear your story.


I personally love this program. It has sped up my work 10 fold. I will ony open fcp7 if I really have to, and my workflow crawls compared. I dread it now.


I just recently finished a fairly complex project with loads of effects, tranitions, stills, movies all overlayed. I threw everything at it. Mind you I was nervous going into it with X, but once I found a flow, it was a breeze to put together. NOTE: Was a Snow Leopard system.. (really helps)


I find color correction is outstanding, always manage to get very lush colors out of X. Much easier than Color.


Intergration with Motion (which is a legend of a program) is seamless now (and was before) but in a new out of the box way of thinking.


I can keep on going, but thats just my opinion and experience. I hope they answer all your wishes very soon and button up this program for humanities sake. Its a great start Apple, just finish it!


regards


brooklyntreez

Jan 11, 2012 6:31 PM in response to Pancenter

None, except the guy on the other thread who said he was an Adobe employee after promoting Adobe software.


Nobody here cares if you switch to Adobe. Do that. This is a support forum. Have a question that isn't rhetorical?


Gi over to the Adobe Premiere Pro forum and see lots of people having problems. What? Ugh, it's a tech support forum. People have problems.


I too have had great success using FCP X except for the memory leak issue in Lion. I still cut and color graded my short in a fraction of the time it would have taken in PP.

Jan 12, 2012 2:02 AM in response to BROOKLYNTREEZ

BROOKLYNTREEZ wrote:


You have a corrupt Event/Project or clip within an Event/Project. Remove all Events & Projects from the Events and Project folders and place them back 1 by 1 until you see the crash again. That will be the problem child.


hope that helps


best


Brooklyntreez

It sounds like you are correct. The issue is we are talking about 250 clips. Im not about to do that. And like I said this should be wrking itself out on its own. Additionally, why did the project work up the time it crashed. Im talking about a days worth of work.


My solution was to trash everything. Import everything again. And I'm still waiting for it to finish transcoding before I touch it.

Jan 12, 2012 2:12 AM in response to bill33

In any case....shoudn't the corrupt clip file - if we assume it existed - be idenified by FCPX?


and/or for whatever the case may be the entire project shoudn't suffer. Maybe restorable versions should be allowed more integrated in to the workflow. Something like a time machine within FCPX -for FCPX projects only- is that possible?

Jan 12, 2012 6:29 AM in response to sfaust439

Purchased Premiere … I had it years ago when you needed a special TV-board on your computer. To learn what Premiere did - after having produced some clips with professional equipment, albeit with some help - took me two days for which I paid a student. When he left, I was alone with Premiere, and did not produce anything until iMovie appeared. My first clip was ready less than an hour after installing iMovie. Then I started to produce videos of about 45 minutes without any further help. I must admit, that I have lost some work due to the problems caused by the program. Later, I bought FCP to become more professional. However, without through training, the outcome of my work was rather poor. With FCP X, I have been successful again. It is much easier to comprehend. May be due to my earlier lessons with other software.


Anyhow, buggy applications can be everywhere. E.g., some time ago I detected that the journal I am editing sent a mail written to one author to another person. And the real recipient has not received anything. The culprit was an application used by hundreds of journals. The provider responded to mail report in an unbelievable way: They told me that mails could also be sent to other journals if I open windows treating data of more than one journal. Goodness!

Jan 12, 2012 9:29 AM in response to BROOKLYNTREEZ

I'm sorry as well. In many ways I like where FCPx is headed, but in its current state there are too many drawbacks needed for our workflow. And since Apple has pulled the plug on FCP, I can't even upgrade my FCP6 to FCP7 and work with that for the next few years as FCPx gets all the kinks out.


My last project with FCPx, and two before it, were tedious and time-consuming. Not because of how FCPx works, or the changes they have made. But due to the bugs we ran into, lost time in troubleshooting, and missing functionality. The last was only a 3 minute marketing video, and it probably took us twice as long to complete since the project was corrupt at one point, compressor crashes (some to kernel panics), and misc other bugs.


I think FCPx is headed in a good direction if they keep going and shape it into the kind of tool we had with FCP7. I just don't think its there yet, and I think it's going to take 2-4 years to get there. I don't want to be sitting on FCP6 that long knowing Apple has killed it, and with PP being such an easy transition (very similar interface,etc), we can be up and running with it in no time, and at only $179 per seat for the upgrade (we currently have CS3 licenses). For us, PP is an easy transition until we see what happens with FCPx. We will keep FCPx around and play with it, but it won't be used for primary projects.

Jan 17, 2012 10:18 AM in response to nfoo

Hello there


I am new to this forum. I just purchased FCPX after using Imovie11 and was essentially happy with it. I am not a pro but not a rookie either. I have maxed out on the learning curve with Imovie 11 and was very excited about FCPX as it was the same format at Imovie11. I empathize with everyone that was having to convert from FCP7 to this.


In any event I assumed that X would at least have a multicam function which I desperately need. Big disappointment. I can still work around that and would be happy if I wasn't running into so many other problems.


Here they are:


1: Crashes and speed. Virtually anything I ask it to do results in the beach ball....and crashes occasionally over what appears to be a simple command.

2: The synch tab is grey and non functional as well as the precision editor.

3. When trying to sync up two storylines I can't seem to access the arrow key to incrememtally move the clip as I could in Imovie11 easily and accurately. I have to drag and drop and have spent 2 hours trying to get one clip lined up. It is also delayed most of the time when I do this. I grab and move and see nothing but the **** balloon and then I pray that I may have got it right or not.

4: Dragging the cursor to move through the storyline does the same as above. Nothing happens when I click it until seconds or minutes after. Driving me nuts. Imovie11 was always immediate and trust worthy.

5: Is there any way of seeing both storylines up on the monitor? They are both there but the cutaway is up front and behind it is the main storyline. Can both be at least seen so edits can be chosen without guessing?


The color correction, balancing and matching is magnificent however. A huge improvement over Imovie's tools. One click and presto.


So any help would be much appreciated.

Jan 17, 2012 11:48 AM in response to duanefromnorth vancouver

Sorry to hear about your problems. I had a lot of crashes when I first started using FCP X. What has made a big difference for me is buying Event Manager. It manages the numbers of events and projects you have open. I now only open the project I'm working on and the program works much better. I believe, and I stand to be corrected here, that if you have several projects and they have unrendered effects in them FCP x will try to render out all those projects at the same time as you're working on your current one, overwhelming the system. You don't say what kind of machine you have. The recommended specs on the apple site are certainly the barest minimum, I think. Hope this helps.

Jan 17, 2012 9:25 PM in response to nfoo

I am running FCPX on a 2011 MBP 2.3 Ghz Intel Core i7 8gig on Lion 10.7.2 and was working fine until I ran out of memory. I realized I had not bothered to place my FCPX files onto my external 3TB G Drive( where I keep my raw footage and ProRes'd files) and was experiencing lagging. So I decided to manually copy my FCPX files onto my external drive (not through final cut). I then moved my previous files to the trash. But now im really scared because I tried to import the project and it says that my files are not supported! How do I restore my project off of my external drive and keep running the files off of that drive? I have even restored the files from the trash but that didn't seem to work either, nor is it convenient to go back to having no memory.


Any help would be GREATLY appreciated I'm really freaking out

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.

The Final Cut Pro X CRASH Thread

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