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

Same thing Tom, I agree with you on this one, a signature can take many forms. Agreeing thru a link is one of them...;-)

Sorrry for that - MOA = Mall of America in Bloomington, MN. I specifically checked to make sure the machine was running OSX 10.8.3 and FCPX 10.0.7, which it was. As I noted, the machine was amazingly fast until I got to Pixie Dust.

Also tried out a couple of other applications including iPhoto and Safari. Superb performance.

@hirschkorn I did not suggest you should not respect an NDA I was mearly trying to find out if indeed they had you sing it in writing or electronically. SO if you're working on a fix with them, great and it only gives creadence to my hunch. 10.8.3 did not include a fix...;-) Apple usually advertises their fixes in their new releases of OS!

That was my point.

It's not easy to answer your question as your experience of this issue will vary depending on your projects and ways of working. Speaking as someone who has battled on with tens of projects despite this issue, learning to work around it and compromising what I wanted to create, my workflow and putting up with LOTS of forced restarts, this improvement is welcome and really helps, BUT it is still far from solved as it is.

The "lock ups" are still frequent, but can be managed by ensuring background rendering is off, only adding items which will induce it late in the project work and accepting that it will affect final render times, but I can at least now actually do the work on the machine rather than having to either miss out certain aspects of the projects or resorting to using another Mac once I get to that point in the workflow.

As to the symptoms, depending on what you are doing, it "feels" like exactly the same as before the update except that the mouse pointer itself doesn't stop moving (every aspect of the interface not just FCPX does stop responding, not just a beachball and not allowing any other tasks to respond), you still get the less severe struggling interface symptoms with everything very slow to respond (eg the dock icons roll over animation slowing to 1 frame per sec ish) and rendering progress which freezes the OS in the same way, the only real difference now is that as long as you wait 30secs or more - up to a minute ish seems to be the longest, then everything will recover and complete. So, you can now work with FCPX, its still a pain depending on what you need to do, but the machine generally works so well that if you can live with those problems or your work doesn't hit the symptoms too often, its ok.

I have hope now we've seen some improvement that a FCPX update will follow soon and see this problem ended.

Hi, you have probably read my replys. I returned my machine last month just before finding out about the real problem. They gave me a new machine after many phone calls and two trips to the store.

The Apple Store didn't know about the problem either. In my case, yes, the machine is improved with 10.3 just like yours. Still studders and stops and I have to sit and wait. I edit an hour program every week and it is title intensive so that makes it hard. Otherwise, I like my top spec iMac.

With all the engineering power Apple has, you would think they could fix something in less than 3 months.

Hi,

here the solution to my question.

You need only another rewarpping of the mts files.

Then import works without the thumnail problem.

This file plays 9:33 minutes at a size of 2.2GB ;-)

Edit without any problem in FCPX.

I've been following this and all I can say is I really hope Apple fixes this soon. I have a top-of-the-line iMac (haha, that makes me laugh) I have an expensive, sub-par iMac with a 680MX graphics card arriving at my house soon. I need it to work. The comments about people "getting by" and "making due" with the $4,000 piece of crap sitting on their desk is really surprising to me.

@canyouhearme hahaha nice comment and oh yes I can hear you, but I'm sure many here can't or don't want to hear you. Some may even say that what you are saying is completely wrong....:-) but it's the best description of what is happening here.

Best part of your hilarious description of this messed up dis functional human behavior is your actually laughing at it. Laughter is a good thing. Many have spent to much time crying over a piece of subpar top of the line crap.....lololol

canyouhearme wrote:

... with the $4,000 piece of crap sitting on their desk ...

Thanks a lot. That's an image I'll never be able to erase from my memory. 😝

Dan

So the question becomes are they going to give us all loaner machines until this is resolved? I, for one, can't afford to have one of my edit suites locked up all the time. They've known about this apparently since January, so this is ridiculous.

I say we all call and let them know our addresses and find out when we can expect them with a machine that will work while we wait for the fix.

Looks like your loaner machine idea worked over at FCP.co

http://www.fcp.co/hardware-and-software/pro/1082-apple-loan-fcp-co-a-top-of-the- range-imac-to-test-part-one-unboxing-and-first-thoughts

It would appear that version 10.0.8 has resolved the issues I was having with Pixie Dust and Far,Far, Away titles. Can anyone else confirm this?

LB

UPDATES FOR FINAL CUT PRO X IS NOW AVAILABLE AT https://itunes.apple.com/us/app/final-cut-pro/id424389933?mt=12

Well they finally got it right. I'm currently exporting 400 large Tiff files from Lightroom, while PhotomatixPro is merging another 1200 files to create HDR single files (resource intensive process) Bridge is creating previews for another 400 or so files, while FCPX is quitly no slowdown, no freeze exporting a project and well what do you know in about 10 minutes it just completed the export while all that was going on and I was writing the post.

Thank you Steve, and the new Cook, and godfromthecloud (even if they deleted his message) I'm sure he had lot's to do with theis fix and thank you to all of you for taking in with so much humour my ranting and complaining...;-)

See you all on the next messup from Apple!

Hi Le500

That is good news! I assume you tried the titles of death too?

Aside from the fcp x update was there a prompt to update cuda drivers?