Currently Being ModeratedMar 5, 2013 1:42 PM (in response to Hirschkorn)
Holy cow, did you see the last line? It says Apple suggest to get a new iMac to solve the issue. WOW I can't beieve that not only it's still not fixed for those poor buggers but if they get a new iMac look what they're getting into!!!
This is going to end up with a class action suit for sure if these guys keep it up.
Currently Being ModeratedMar 5, 2013 2:18 PM (in response to jonuk85)
Ironically a nice apple man in the call centre SUGGESTED my imac being th best for FCPX and Motion
I did send him a nice email saying it may be best not to recommend this model to new customers until its sorted but he never replied, dissapointing really.
I think we all agree this is a MASSIVE problem because we are not just buying mac mini's here, these are top of the range iMacs..
I love my machine but I cant work with FCPX... Im so close to binning the software and going to Premier Pro
Just emailed Tim Cook, wonder if he will reply
Currently Being ModeratedMar 5, 2013 2:45 PM (in response to Tom Wolsky)
On three occasions, I have gone to an Apple Store to try and reproduce any or all of the problems described in this thread.
The only thing I have been able to reproduce is the freezing when using the Pixie effect.
The most recent test included several effects added to each clip, transitions, and a wide variety of titles. Exporting a completely unrendered sequence was glitch-free. It was also incredibly fast. Only when I added the Pixie title did things get weird.
If I had owned this machine (I wish I did) I doubt I'd have known there was a problem since I probably would go for a long time without needing that effect.
Currently Being ModeratedMar 5, 2013 4:00 PM (in response to Russ H)
I can't comment on the other tests you did, but I can assure you that in real world use, this issue arises for me frequently, although I am getting better at avoiding even thinking about incorporating more things in projects to avoid it, so I /can/ work with FCPX but I am having to significantly compromise my creativity to do so.
And please, don't think "pixie dust" is the limit of this issue, it is just a very quick way to arrive at a situation which causes it that is reliable and reproducible so it is useful for diagnostics. I have never used that effect in anger but I have had projects which were crashing every 5-10 minutes of work, needing about a minute to restart each time and I've had a number of projects which I fought through but have had to transfer to the Mac mini for the final render as it will crash everytime I try to render it on the iMac.
So, you might be lucky, you may naturally never hit a combination which would cause you problems, but unless what you are doing is VERY limited and basic, I would put money on you hitting the issue too once you start trying to use it for real. But, then, if your buying one of these models and expecting it to work for you even after reading the thread including feedback from Apple FCPX engineering team acknowledging the issue, then you are clearly happy to take a gamble with your money anyhow.
Currently Being ModeratedMar 5, 2013 5:27 PM (in response to jonuk85)
I haven't had nearly as many crashes as other people seem to be having i7 gtx 680 n all that 8gb ram fusion drive
I did have trouble with titles but general editing and things haven't seemed to affect it.....
I did also go through the whole deleting prefs thing with a third party app because off the bat the app crashed 2 times and after that it was fine
I'm afraid of throwing pixie dust at it lol
Currently Being ModeratedMar 7, 2013 11:31 AM (in response to elohel)
My freezes only occur when using titles in both FCPX and Motion 5. Every time I try to use a title, the render slows down after starting and then freezes the whole machine. This is my second iMac 27,i7 ,3.4 with 680 MX in almost two months and can not edit my weekly one hour program. Thinking about trying to return it.
I would even welcome any speculation as to when and if an OS fix or new 680MX driver will come. Since the issue is with both fcpx and Motion I would guess their software is ok. I know....speculation doesn't help.
I can't work!
Currently Being ModeratedMar 7, 2013 11:56 AM (in response to Cliff Whitney)
Same situation here. I add any title in FCPX, move it a bit around, change the font... and BAM ! Freeze !
I sent an Disk Image to Apple and told me everything seemed OK... :-(
I CAN'T WORK !
Currently Being ModeratedMar 7, 2013 12:00 PM (in response to Sebastien Davis)
I sent an Disk Image to Apple and told me everything seemed OK
How'd you do that? Who's you hear from?
Currently Being ModeratedMar 7, 2013 12:11 PM (in response to Tom Wolsky)
....through AppleCare I guess.
Currently Being ModeratedMar 7, 2013 4:30 PM (in response to le500)
Gentlemen, the FCPX Team is working on a fix. I'm currently testing some stuff that I'm not allowed to talk about yet... but it appears they at least found a way to stop the machines from freezing/crashing. I wouldn't bet on a quick fix and things could be definitely better performance-wise, but it's a start.
Currently Being ModeratedMar 7, 2013 4:38 PM (in response to Hirschkorn)
Hirschkorn, it's such a big relieve to hear this news! My top spec iMac is on its way to me and I have been waiting for some answers. I am sure that they will find a way to fix this. Thanks for the news.
Currently Being ModeratedMar 8, 2013 11:10 AM (in response to yweski)
Looks like I'll be trying something new here in a bit as well! I sure hope it fixes the problem. Full report forthcoming.
Seems like Apple is on it!
Edit: After reading the non-disclosure agreement, it looks like a full report will not be forthcoming. But...Apple is on it! Let's' see what they've got!
Currently Being ModeratedMar 8, 2013 2:02 PM (in response to Surf City 1)
Yeah, all of you need to be careful regarding NDAs. Sometimes just mentioning there's an NDA in effect is a violation. The last thing we want is for you guys, who are representing us poor users, to get removed from helping solve the problem.
Currently Being ModeratedMar 8, 2013 2:28 PM (in response to Dan Thomas (DAGWare))
Got it! I'm one of those poor users, too.
Currently Being ModeratedMar 10, 2013 6:37 PM (in response to Surf City 1)
I've just been on the phone with Apple Support here in Japan about this. They apologised for the problem, and say that it is being worked on by engineers as a priority.
The current 'fix' is either to have my Mac replaced for a lower spec model, or not use FCPx, or wait - I choose to wait! No timeline on when the fix will be released but they are treating it as a priority.