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

Same situation here: 10.8.3 solved some of the issues, and FCPX 10.0.8 will solve the remaining issues. (Thank God, because I can't stand Adobe or Avid apps; I've heard Smoke is pretty amazing, but I haven't tried it yet).

Hope this puts your mind at rest.

Thank you for that - yes, it really does put my mind at rest 🙂

2Gb of RAM on the video board...

Same problem with my new iMac27" witch 675MX. I observed a strange behaviour. When I watch the GPU MEM with iStatMenus the MEM bar rises very fast and at the end the system freezes for a few seconds, and after working again the GPU MEM ist empty and starts raising again until the next freeze...

This happens on rendering or playback.

Eventually helpfull?!

Know what it's like. Waiting for delivery of my new Mac I came across this thread and panicked in thinking I wouldn't be able to use FCPX! No problems so far though.

@ jonuk85: Due to an NDA, I won't be able to give you crystal-clear answers on the above. But here's what I can tell you:

- OS X 10.8.3 solves most of the issues; the app won't crash anymore and you won't have to hard reboot your machine now; the app stil freezes (only when using Pixie Dust and another title), but if you give it some time (minutes), it "comes back to life" and eventually finishes rendering.

- all signs show that FCPX 10.0.8 will solve the remaining issues.

I can't say more, but you get the idea...

@jonuk85 Hahaha how ironical that you started this and you ended up returning the iMac. Well I'm the nastiest of all the commentators it would seem. Or the most intolerant, after you for having returned the machine...hahaha I love mine too much to return it and prefered switching NLE's but that's another story. Intrinsically I am not one to tolerate abuse to consumers from large corporations and I say outloud what many think but won't put in writing in places like this.

I have the top spec machin, with all the bells and whistles, written the details in this forum countless times for new comers and I also updated to 10.8.3 And YES after doing so I was able to render the Project that I could not render previously. But it took my machine thre to four times longer to do it and if freezing NOT permanantly like it used to requiring a reboot did not occur while rendring/exporting the project I would not say that waiting on my 4500€ iMac while it froze every two to three minutes depriving me from doing anything else is a great Improvement.

We are not talking at least in my case of freezing only a few seconds but close to a minute every two to three minutes to export a 5 minute video that takes forever to export.

I rather do that using my MBP that does it much faster and still allows me to do other stuff while exporting it.

Yes you are right the FCPX team has been kept informed of the activity in this forum and you would think they would reciprocate and keep us informed. But they released 10.8.3 and there was not even a mention that this issue may have been adressed to fix it. My take is, it wasn't and the slight improvement is only circumstancial, not intended and planned. Otherwise it would have been mentionned in the lits of issues this new vintage of the OS fixed.

If I were you I wouldn't run to the Apple store until you see an Apple printed information release acknoledging they fixed this mess.

I've been following this thread since the beginning. I have an older 27" that works fine with FCPX, but happened to be in the MOA Apple Store a few days ago. They had a full spec 27" iMac loaded with FCPX. I tried it out, and it worked beautifully and amazingly fast. Then I added Pixie Dust to the project, and indeed it froze FCPX for around 30 seconds although the mouse and other non-FCPX functions worked. Then FCPX came back to without a restart.

I will be getting the new top of the line iMac as soon as my income tax rebate comes in and I believe it will be essentially fully usable for editing even before the final fix is implemented.

@hirschkorn been meaning to make this comment about your NDA stuff and although I am not a lawyer I have been around them for many years in my past life as a business owner and executive in large corporations.

For you or anyone to be bound and liable to any type of Non Disclosure Agreement, you need to have been presented the said NDA in writing and have signed it for you to be required to non disclosing any information provided in that document. Allow me to have my doubts that Apple would have had you sign such document. If I'm wrong then you are right in not talking and it reassures me that indeed a fix may be on it's way.

"My take is, it wasn't and the slight improvement is only circumstancial, not intended and planned."

This is categorically wrong.

The NDA is in writing. It does not have to be signed. You can agree to the terms with an electronic link, just as you agreed to the terms of this forum when you signed on.

Perhaps so, but neither you or I can demonstrate what we feel...;-) And Apple has certainly not contributed to inform us, or have they passed me? I have had numerous encounters with them and never once have they told me that a fix was included in 10.8.3

And although FCPX does work a tad better it is not up to what it should be doing on a machine I paid 4329€

Forgive me for being so demanding, but heck we pay for top notch products and deserve them te perform as such don't we?

What's the MOA store?

Did you check the OS version? Until late last week the store images were still 10.8.2. I had to get the manager to update the machine for me.

@le500: I graduated law school. In the end, they can't do anything significant if it's not actually signed (by hand or digitally)... but that's not the point: although I'm not a programmer, I find it very useful being able to test pre-release software — and that's not gonna happen if I ignore the NDA.