Skip navigation

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

42303 Views 489 Replies Latest reply: Sep 22, 2013 6:20 AM by Tom Wolsky RSS Branched to a new discussion.
  • le500 Level 1 Level 1 (0 points)

    As mentionned in earlier post last weekend, I spoke with Applecare yesterday about this issue and they passed me over to the FCPX specialists. They are aware of the issue and working on resolving it. So I wouldn't bite my nails until they bleed, cause help is on its way. Furthermore this issue only happens when using FCPX, and heavy video editing can be done with other apps like Premiere Pro from Adobe...;-) And that's why I had not noticed the issue for almost a month after receiving my new iMac. I use Adobe After Effects CS6 and Adobe Premire Pro CS6 which both are configured to take full advantge of the new NVIDIA graphics card on this machine and the new processors also.


    How ironic that Apple's own software is the one struggling to keep up with Apple's new hardware. I would be embarrassed in there place.

  • le500 Level 1 Level 1 (0 points)


  • INVIDIO Calculating status...

    If there is anyone of you who communicates with Apple,

    may add that the exact same problem

    occurs when exporting the same file from Motion 5



  • le500 Level 1 Level 1 (0 points)

    This thread is now being read by the FinalCutProX team and they will likely catch that detail as Motion is a FCPX add on. In any event when they get back to me I'll make sure they are told as I have an APplecare case number attached to this event.

  • le500 Level 1 Level 1 (0 points)

    Just received this email from the FCPX Team member working on this case:


    Hi Jose

    Just awaiting an update from the Engineering Team. I hope to have an update shortly.

    Many thanks


  • VSKiwi Calculating status...

    Has there been any movement on this as yet???


    Cheers Greg

  • le500 Level 1 Level 1 (0 points)

    Hi they are working on a solution. As of last Thursday January 31st I as contacted by Apple and they sent me an application to install on my iMac that would collect all the data they need to fully investigate this issue. I ran the application and sent them the reports it generated that same day and expect to hear from them next week.


    Fingers crossed but don't hold your breath, you could die...;-)





  • le500 Level 1 Level 1 (0 points)



    I was asked by the FCPX team to provide the CurrentVersion.fcpproject file located in the project's folder and a crash report. We realised that this crash or freeze up did not create a crash report in the logs folder in the Lybrairy.


    So we tried other things and the situation is quite different now. Originaly I and probably others assumed that this crash situation was going to happen in all exports but we tested by creating a new project to export and it worked fine. Then we tested again by trying to export another old project and it worked also without problems. So the FCPX team now has the currentVersion.fcpproject files of the three projects: The one that is an old project that crashes and was the initial project to raise concern, they also have the file of the new Test project that did not crash and the file of the old project that also did not crash.


    I hope they can get back to me with why this one project does crash. BUt at least I no longer see this situation as critical as I perceived it initially.

  • Tom Wolsky Level 10 Level 10 (104,760 points)

    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.

  • le500 Level 1 Level 1 (0 points)

    Hi Tom,


    I agree with you that this may not be just an export problem, but I have to add that it certainly is not just a pixie dust title problem either. In my latest update, by luck I had used the pixie dust title in both projects, the one that crashes and the one that doesn't. So I just ran another test. I DUPLICATED the project that crashes by using the option Duplicate "Project and Referenced Events" and once the duplicate  was done I proceeded to export the project in which there is the pixie dust title just as in the other project that did not crash and this time the exported worked perfectly.


    So now I have no idea where the problem is with that project!!!

  • le500 Level 1 Level 1 (0 points)

    Hi jonuk85


    I just updated the FCPX team in contact with me about this issue and sent them the new file along with a link to this conversation so they can see what's going on. Wow what a bummer for you if you are having issues on several projects. For me it is only with one project (although tested only with one other one plus the duplicate and seems ok) but perhaps I should try other older projects as the newly created project worked all right. SO to conclude that the problem is the NVIDIA card is in my humble opinion a tad premature.


    Let's see what the FCPX team has to say about the latest test files they have.....

  • le500 Level 1 Level 1 (0 points)

    Am forwarding this last update to them as the person I am in contact with is reading this for sure. But what baffles me is that in my case I have reduced the issue to one project only and even found a workaround to it by duplicarting the project and exporting it. Have you tried that with one of your numerous projects that crashes?

1 ... 4 5 6 7 8 ... 33 Previous Next


More Like This

  • Retrieving data ...

Bookmarked By (11)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.