Final Cut Pro X freezing on top spec new 27" iMac, help!

Hi Jon,

well I wanted to test that part so I opened the project and proceeded to make some changes and edits and was able to reproduce it also. It was doing fine while cutting some lenghts of the project and editing the sound track but when I got to making changes to the end credits where I have the pixie dust title it started studdering and freezing but not completly as it came back. So I tried to change the palyback to use Proxy instead of Real file and after a few minutes of tweeking it finally froze for good and now have to restart the computer.

In any event the person from FCPX just replied to my email where I sent her this link again and they tell me they are working on this and will get back to me asap.....

Update to my latest post (I must be masochistic)

Now that I started making edits to the project and had almost completed it I needed to push this further as I could not finalize the edits after three crashes. So I created a duplicate of the file as mentionned in earlier posts and I could not only watch the whole video without it crashing (not the case with the original file) but I was able to make the final edits to my satisfaction with no problems at all and then I tried to export the file which is what was important as I needed to send it out today, well forget it, the darn thing froze again. So this shoots down all the previous reports that suggested there was a workaround by making a duplicate of the project.

This is really rediculous!!!!

I just spent a couple of hours on the phone with Apple. Ran a few tests, generated diagnostic reports and sent them off. They're looking into this problem.

If you want to reproduce the issue readily, add a Far, Far Away title to a new project, change text style to Dream. Snap. Done.

Hopefully they come up with a fix quickly.

Hey thanks for this info. When I spoke to the person contacting me earlier today we could not find the crash report in my library. And she did not tell me to look for it using Console. I just did and found todays crash details which I will send her right now as a follow up to our conversation of this morning.

I'm on the verge of purchasing a 27" iMac with the 680mx card. Do you guys feel like I should avoid this card and just opt for the stock one? My main use is going to be Final Cut Pro X. After seeing this thread I'm nervous to get the 680mx since Final Cut Pro X will be the main thing I use the computer for.

If you can tolerate every project crashing at least once, then yeah, go for it. I purchased this new iMac to peimarily use FCPX, so you can imaging how bummed I am that not one project has been produced without a crash.

I believe that they'll eventually come up with an update, but so far for me, the frustration level is pretty high. I have built a few projects in my old MacBook Pro just to avoid the hassle. Here sits a $3000 piece of bling. Surfs the web nice though.

Although I fully understand and share the same frustration as Surf City 1 I can't agree with his recommendation at all. When you allow anger to place words in your mouth that your brain might otherwise not permit you get bad advice. I bought this machine because it's the fastest one available and what I needed was speed and performance. Think about getting a car and it's the fastest out there but you discover once you bought it that it chokes, studders and stops when you fill up with your favorite gazoline. Are you seriously going to return it for something less or will change you change gazoline brands?

There are so many more and better Apps out there to edit video, I for one have switched to Adobe Premiere Pro CS6 and also got for the same price After Effects with it's incredible Warp Stabilizer. I say the same price because now you can lease the complete suite CS6 for some 30$ a month and have access to all the Adobe family products, I mean all of them and that allows you to install it on two machines.

Incredible deal. If that does not force Apple to fix this and other idiosyncrasies they have with some of their software, well too bad, they will miss the boat of Software sales and remain a computer manufacturer, one of the best if I may add, if not the BEST.

Adobe products are built around using the fastest video/graphic cards so buying this machine is not a mistake. Getting something slower and then Apple comes up with a fix will have you regret it during the life cycle of the product.

Think about it!

Without a doubt, this is frustrating: after all, they should have tested it; once again, this proves that "it just works" is just marketing. And, without a doubt, they will release a fix sooner or later (I hope it's sooner though).

As for video editing apps, it's true: there's FCPX, there's the Adobe Suite, there's Avid, there's Smoke... Thing is, I couldn't care less about that: I absolutely love FCPX and I can't stand Adobe's or Avid's software (I've heard Smoke is pretty amazing, but I haven't tested it yet). And I should be able to use Apple's software on Apple's hardware without any hassle — basically, it all comes down to this.

le500 wrote:

Although I fully understand and share the same frustration as Surf City 1 I can't agree with his recommendation at all. When you allow anger to place words in your mouth that your brain might otherwise not permit you get bad advice.

That's funny...then you go on to talk about Adobe ad nauseum, which wasn't even part of Starkgsd's question. Are you an Adobe troll? They specifically asked about how the new iMac functions with FCPX. Perhaps you didn't read it, or are having a difficult time with English.

I'll say it again. My brand new iMac has stuttered and frozen while editing every single project that I've ever built in the month that I've owned it. So my advice stands, if you can tolerate that fact, then yes, go for it!

I did state I shared the same frustrations as you and mearly offered a different opinion. We can express opinions even if we don't share the same opinions but why does offering Starkgsd alternatives generate calling me names and suggesting I'm a troll? So sorry if you were offended but I think my analogy about the car and the apps is quite appropriate and in the end our friend Starkgsd will have to make up his mind on whether to buy a slow card or a fast card. And should he buy a slow card and then find out that Apple fixed it, he'll regret it. I thought that part was quite clear. As for Adobe, I'm not a troll of their's nor anybody elses. I offered alternatives I know of and if I would have known about Avid or any other NLE I would have done the same thing.

Sorry to read you took my comment as an attack on your opinion. One plays the devil's advocate and gets blasted for trying to help......

I appreciate both of your opinions. I've decided to 'gamble' and get the higher end graphics card in hopes that Apple will update it soon. Afterall, my iMac won't arrive for 4-6 weeks. Now let's REALLY hope they get a fix for this issue, but until then I'll suffer through the freezing or use Premiere. Sorry to get off topic. If there are any updates with responses from Apple on what they're doing to fix it, I'm interested!

Thanks guys!

i had such a freeze on my 2008 Mac Pro with an XFX Radeon 6870 1GB.. i think i was also using some kind of title template

i hope Apple can fix that with an OSX or FCPX update

Did they release a fix back then?

EXACT Same problems as jonuk85, and I attempted the exact same fixes. I even went back to the apple store, and purchased a new "Ultimate" configuration iMac, because apple care level 2 support had told me that OpenGL issues were hardware related, and my computer was DOA.

The brand new computer, with no external media, nor external profile data, has the exact same problem. (I turned the computer on, created a blank, new profile, downloaded and opened FCPX, inserted a FCPX generated gap, and pulled down 6 FCPX generated "blur" title effects and attempted to play back, the system immediately froze.

Always the same console error upon restarting the system (but no crash log)

Final Cut Pro[336]: *** OpenGL error 0x0506 (invalid framebuffer operation) in function "GL_CHECK_CURRENT_ERROR"

My system has literally crashed 50 times in the past week, crippling the progress on my projects. It's pretty riduculous, especially because as soon as I received the new system, I had shipped off my old edit system to a Mac Reseller.

Same stats as everyone elses -- 3.4GHz, 680MX, 1TB Fusion

I think it's important to offer my two cents, if only to add to the ranks and bluster the urgency of this problem. I have a spec'd out iMac as well(3.4ghz i7 processor, 680 card, 32gb memory, fusion drive). It's the baddest machine they make and it cannot handle it's company's own software? Today FCP X was working fine until I got an email notification. A freakin' email notification and the screen froze.

I hate having to hard power down a machine this expensive. It's not good for it. Couple this with the fact that most of my files that worked with FCP 7 have to first be converted (by an outside source)before they'll work with FCP X. And don't even get me started on the lack of FireWire ports.