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

Studio Engineer wrote:

 

Highly frustrating I would say. And THAT frustration (IMO) is exactly what will make this whole thing push forward to days of glory where users, hand in hand with dev. can be happy about using their fav. app...

 

I personally LONG for those days ;-)

I'm a developer for a large company, and I, too, long for those days when we could work hand-in-hand with users, and we would all be proud of the result. I'm going off-topic here, but this is one of my major pet peaves with today's corporate environment.

<sigh>

Dan

Walt Disney did say, "If you can dream it you can do it".....don't stop dreaming Dan, perhaps the dream will find it's way thhru the corporate labyrinth!!! But writing it has more chances then dreaming it, so let's hope someone at Apple sees your dream in writing here!

le500 wrote:

 

Studio Engineer,

 

I wish I had the same convictions and levels of assurance and patience as you have, but with lack of evidence on their part thru lack of information provided to their customers, I stand firm on one statement I wrote: "By any standards this is totally unacceptable." There is no acceptable reason to have professional clients crippled from doing their jobs for such a long period of time. We are talking about Apple that has so much cash it could buy half of America. So let them spend some on adding more resources to their professional Apps department and have this thing fixed asap.

 

X2

If a customer of my small business spent almost $4000 on a certain product, I would certainly make sure it worked before I delivered it.

yes... hard times ;-)

All I can state is that the more folks writing detailed reports to Apple FCPx Feedback, the better our chances are of collectively finding a solution ;-)

le500 wrote:

 

In your example I place myself as one of those nice proud and attentive FCPX members reading this and with my way of thinking I would use messages like mine to tell the boss; see boss we need more help, you have to hire or transfer more people to our team, we are burning midnight oil and still have no clue as to what's causing this. Please send in the cavalry and help us get our customers smiling again and more importantly get them productive so they can deliver their projects and get paid.

 

I can guarantee you that the developers have complained to the Powers That Be. Constantly. Loudly. It may not be the number of developers that's the issue, but whatever it is, I guarantee you they've complained. But I'm sure it hasn't helped. Gone are the days when anyone cares what us developers think. We're considered comodities nowadays - interchangable parts. (Hence the popularity of outsourcing.)

It used to be that a talented developer could hold sway over the Powers That Be, because they wouldn't want to lose us. We were treated like "talent" in the movie and TV industry. Nowadays, not so much.

So yes, let's tell the developers when they've done a good job, and complain when they've messed up. Just remember that a lot of things are no longer in their hands. And if you think you're frustrated, the level of frustration the developers are feeling can be multiuplied tenfold.

Dan

le500 wrote:

 

Walt Disney did say, "If you can dream it you can do it"

LOL. You don't know how close to home that quote is, for me.

Dan

Another update: No freezing during editing so far, after having removed SliceX. Again, I'm not doing anything fancy. Still, it's nice to work for hours without a crash. Knock on wood.

Dan

Hi Dan,

are the specs on your machine the same as the ones having problems on every edit and every render? Do you have the NVIDIA Graphics card GeForce 680MX 2GB which is what seems to be the common denominator? Tried looking thru the thread to find this info about your machine but did not see it, sorry to bother if you had posted it.

Ooh, good question. No, my specs aren't the same. I have a 21" iMac that I just bought last month - it's the new model. It has an NVIDIA GeForce GT 650M 512 MB. 2.9GHz Intel Core i5, 16GB RAM, and the 1.2 TB Fusion hard drive.

Dan

The issue this topic (originally) described is probably caused by the GPU (680MX) - the only common factor up to now (see previous pages for details, as all users have top spec'd 27" iMacs).

I can't say for sure that everyone else who has reported the problem has the same specs (as I doubt that everyone has reported their specs), but if you say so, I'll take your word for it.

However, I *can* say this for sure: I have indeed read all the pages in this thread. And I assure you, the issues I have been facing are the exact same issues as everyone else, regardless of whether I have a 21" or 27" iMac. From that, you are free to draw whatever conclusions you wish.

Dan

Tom Wolsky wrote:

 

This isn't strictly an export problem, and can easily be reproduced when working with the pixie dust title. I tested it in an Apple store. It worked correctly on all the iMacs except the 680MX where the machine twice froze and forced a hard reboot.

Dan - I'm not an engineer/programmer/developer; it's just that, based on the first 7-8 pages of this topic and based on other reports on the internet, this seems like a common issue for all top spec'd 27" iMacs.

The fact that Tom did a couple of quick in-store tests and decided to rule out all iMacs except the 680MX doesn't prove anything. All it shows is that, for the particular tests he ran, that was the only machine affected. I don't doubt for a second that if I tried his tests on my machine, they won't cause my machine to freeze either.

However.

That does *not* mean that there might not be other tasks that freeze other kinds of machines, and it does *not* mean that they aren't caused by the same bug(s). All it really means is that whatever bug is causing this issue apparently manifests itself differently depending on what hardware is being used.

The facts are this: I am experiencing the exact same types of freezes and lock-ups as others have reported here. Whether I am doing the same tasks as others when these issue occur, I can't say. To be honest, I don't care. All I care about is the fact that I'm sick of my computer freezing to the point of requiring me to power it off and back on, while I work in FCPX.

Dan

I agree with Dan, above. There seem to be several issues, from complete freezes to insane slow-downs and spinning wheels. It also seems to be that many of us were working just fine until some as-yet undetermined update or other occurrence (Mercury in retrograde?) caused it to go haywire.

I'm no developer, I'm no (major) geek, but it seems like it's a FCPX issue, possibly in conjunction with iMacs but possibly not.

This is an iMac-specific thread, and so may be drawing an inordinate number of that usergroup. Also, it could be more of us using FCPX went with the new iMacs . . . I know I decided to go with iMac at the store, having went in to purchase the new Macbook Pro retina . . . but the big screen and great price lured me.

I basically bought the top spec'd iMac because I was tired of waiting for that mythical new Mac Pro. (Not to mention it was significantly cheaper too.) Thing is, this is a pro app, not some stupid iOS app, and Apple's own software should run without any issues on Apple's own hardware - it's not like they have one million different configurations to support...