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

The problem here Hirschkorn and which is why I say I hate apple (not their products) the company is they have broken those rules and created a new paradigm. Their products are what we all love, they are unic and leading eadge and different. They are cool, well built, high design and the list goes on. The reason why those rules don't apply to apple is that we can't go to the competition. Competition stinks. When Apples messes up like in this case our only option is to wait. Image if this would have happened on a Windows OS computer. Many have been there and don't want to go back to the days where the computer manufacturer blames the software manufacurer and they play ping pong with the client.

Here we only have one company to blame, but they are inaccessible hiding behind rock solid walls of barriers to ensure we can't speak to the higher levels. Remember what happpened when I wrote the name of the boss, my message was deleted.

We can't do anything else then wait, which is why I hate the company and love their products so much that I'm stuck with them. And I'm sure there are many more like me except they don't stop and think that NO they don't like Apple in fact they hate Apple that takes advantage of their clients position of submission.

Ok enough said, I could go on for days with this and maybe one day I'll write a book about it.

Read the lines you wrote Hirschkorn, taken from text book business gurus and answer honestly, will you leave Apple because of this or any of the stuff written in that lineup of reasons why companies lose clients?

Well I won't because there's nothing out there that compares and that really annoys me.....

I am just about to order my 27" iMac but with the NVIDIA GeForce GTX 675MX with 1GB. Are people with this card having the freezing and stalling problems. Please let me know your thoughts before I place this order. Thank you.

attis, no problem with 675mx as far as we are aware

Hi all! I write from Italy

I also purchased the iMac 27 "video card gtx 680mx

32gb of ram and fusion drive 1tb.

I found exactly the same freezing problems using the effect PIXIE DUST.

The iMac I received February 14 and being aware of this post I immediately wanted to try this effect and boom stuck car!!

Trying other third-party effects (FxFactory) FCPX I quit unexpectedly without causing frostbite.

Of course I warned my technician that I installed the car and I wanted to say that it could be a limit of mountain lion segnalandomi who do not are no longer updating because they are developing the new OS lincis scheduled for release around June .... . (my feeling is that the present along with the mac pro, but that's just my feeling).

Having said that my technical concept that I ripreparerà the car again by formatting everything, and try to do a hardware test to verify that there are no problems in this regard.

In the meantime, having read here of someone who has updated the video card drivers, I did too.

I immediately noticed a marked improvement in the car and FCPX has not done more naughty. Clearly I have not retried the pixie dust effect for fear cel freezing but all other effects that I spent playing with the machine did not cause any crashes.

Even premiere cs6 that very little use has not given me any problems activating the processing of cuda gtx 680mx.

Photoshop even with the computer is a rocket ... fast.

I will do other tests and after the hardware test I'll post the results.

Greetings to all

Mario

I forgot to say sorry for my english.

I speak little, and I helped with the translator of google.

I hope to be of some help.

Mario

Regarding the 675MX: I have a 21" with the 650M. For a while I experienced constant freezes like the 27" peopla have been reporting. But I was able to eliminate the freezing on my systerm by removing my SliceX add-ins. So while the 675MX may work better, you can't be sure it won't have *some* issues.

So my advice is this: If you *do* experience freezes, start a simple test project. Add in some footage and render. If that doesn't freeze, methodically add new effects one or two at a time, until you can determine what is causing the issue. If you get lucky, then you'll only have to avoid a few effects until they fix the problem.

If you don't have any freezes at all, just be sure that you remember what you've changed between each render, so if it does start to freeze, you've got some idea of what changed. I didn't do that, and it took me days to finally remember what I changed when the freezes started.

Taking a guess by the lack of 675MX people reporting in this thread, the 675MX either doesn't experience any freezing, or if it does, the situations are isolated, so you may be in luck. Just keep all of this in mind in case your luck starts to run out.

Oh, I should mention that I have yet to do much with Titles in the projects I'm working on, so it's still possible that I'll experience more freezes when I do. Crossing my fingers.

Dan

Dude.........the english totally rocks. You should hear my italian (I'll spare you, though)😎

The issue is FCPX does not handle RAM well. Even with a quad core Mac Pro with 16 gigs of RAM running Lion, I need to turn off all other programs to use it. It freezes constantly and then to reboot I also have to turn off the extenral harddrives where the files are located. People in this discussion are fixated on Pixie Dust or Slice X or titles or using background rendering. It is not one thing. It is anything that stresses the system. I know because I have been dealing with this much longer than any of the discussers. I have just put up with it. It is not just a fix for the video card. The program needs to be made much more stable. If they just fixate on the iMac, they will miss the big picture. The program itself is too buggy. When it runs, it screams, but just ask it to do too much and then it is time to reboot.

Event Manager X is mandatory to get every other Event off of FCPX 's attention. It just needs every ounce of RAM.

Sorry guys in Cupertino. It needs a major update, not just a minor fix.

You may have been dealing with FCPX crashing "longer than any of the discussers here" ,might be true true. However, I can assure you that this problem is different and more significant. I've been running FCPX for a long time too... and dealing with its quirks. This freeze issue isn't just a quirky little problem, it's a full blown crash that utterly halts productivity; and it happens while editing almost every single project. The freeze doesn't only happen with those named title affects; those particular ones are just guaranteed to make it crash. It doesn't need a fusion drive, external hard drive, and it doesn't matter if there are other programs running, the system freezes.

Yes, FCPX does need to be more stable. At this point I'd be satisified if it ran as good as it did on my 2010 MacBook Pro.

To be honest, I've never had any issues with FCPX until now. I'm using it since it was launched, back in 2011; my late 2009 iMac 27" and my late 2011 MBP were/are both great. (Both machines had AMD/ATi GPUs - but I don't know if that's significant or not.) And I've used add-ons almost since the beginning. Not even a single glitch, and I'm not just a hobbyist... I'm handling hours of HD footage every week.

This issue and Apple's "response" to it drives me crazy though.

I'm having the same issue with FCP X and Motion 5.

New iMac i7, 3.4 with fusion drive and GTX680MX. Freezing while using titles and while rendering. It slows down then freezes. Not even a cursor. Same thing happens with Motion 5 while rendering or just playing back a simple title zoom. I spent a lot of time on the phone the last couple weeks then took it to the Apple store.

After two trips to the store they ordered a new one for me. Took two weeks. I'm not using it to edit till Apple fixes this. I can't even put it in my work flow now and that's a big loss. Come on guys, put this on the front burner!

Sorry, but you've missed the point. Sure FCPX has "issues" on any platform, anyone who's use it much will know that, but the frequency of this specific rapid catastrophic issue with the 680MX card is of a different order of magnitude. The same project will work fine on other platforms, and it is in no way limited to a single effect/title, its just that PixieDust out of the box without changing a thing is a short hand way to reproduce the issue. I've never used that title in earnest in any project, but without any 3rd party add ins, with a clean machine and a project of a few 100MB and a single title, FCPX on the 680MX will crash the entire machine reliably. That level of instability and degree of impact just isn't the case on other platforms. It's also been tested by others on this thread that an earlier version of FCPX doesn't crash with the same projects and "only" with the same frequency of other platforms again. So, there is definately something specific about this combination rendering (!) it unusable for some and at least very annoying and risky for everyone, and entirely unacceptable.

If Apple can get FCPX back to the "usual" levels of instability that you talk about (and which I too am used to) on this platform, I'd take that gladly right now!

By the way, I'm running with 32GB RAM and FCPX is barely making a dent in it or the CPU or even the disk throughput when it crashes in this way - as an IT professional (only an amature video maker) I've been monitoring them all, as well as sampling the processes, etc to try to see any pattern/clues etc, comparing results across multiple platforms etc, and this is NOT the same issue of FCPX being a resource hog and hence slowing to a crawl you seem to be referring to. Sure, that happens too, but that exhibits itself in a different way.

I have a sick feeling we will have to wait for the next update to FCPX to see this resolved.