jonuk85

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

I finally received my new 27" iMac today and installed all the latest updates and then the latest versions of FCPX and compressor.

 

Spec of new iMac:

 

27" Late 2012

3.4Ghz Intel i7

8GB RAM (I also added 16GB of third party RAM to the machine to take it up to 24GB RAM but remove this later)

GeForce GTX 680MX 2048MB Graphics card

1.12TB Fusion Drive (1.09TB free)

OS X 10.8.2 Mountain Lion

 

Immediately I noticed performance issues and then it kept freezing whilst running FCPX - the whole OS would freeze resulting in me having to actually turn off the machine and turn it on again. It happened repeatedly so have done all the obvious things but still have the issue.

 

So far I've tried (with no luck):

 

- removing the third party RAM

- restarting the computer, multiple times

- making sure everything is up to date

- removing the FCPX preferences

- doing a PRAM and SMC reset

- fully uninstalling and reinstalling FCPX

- running the short and long Apple Hardware Tests (no problems found)

 

I am working with a large quantity of video files off an 8TB Thunderbolt drive but I've been using FCPX on my old 27" iMac and had no problems with that at all, the spec of that being far less powerful:

 

27" mid 2011

3.4Ghz Intel i7

8GB Ram

Radeon HD 6970M 1024MB

1TB hard drive

 

I'm thinking it could possibly be the graphics card or a software issue?

 

Any help or advice would be great!!!

 

Thanks!

 

Jon

iMac, OS X Mountain Lion (10.8.2)

Posted on Jan 14, 2013 1:51 PM

Close

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

  • All replies
  • Helpful answers

first Previous Page 21 of 33 last Next
  • by Moosha,

    Moosha Moosha Mar 1, 2013 6:14 AM in response to sputuk
    Level 1 (104 points)
    Desktops
    Mar 1, 2013 6:14 AM in response to sputuk

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

  • by ad5901,

    ad5901 ad5901 Mar 1, 2013 6:27 AM in response to Moosha
    Level 1 (4 points)
    Mar 1, 2013 6:27 AM in response to Moosha

    Any idea when this will be??

  • by Moosha,

    Moosha Moosha Mar 1, 2013 6:56 AM in response to ad5901
    Level 1 (104 points)
    Desktops
    Mar 1, 2013 6:56 AM in response to ad5901

    No that's the problem.

  • by Cliff Whitney,

    Cliff Whitney Cliff Whitney Mar 1, 2013 8:09 AM in response to Moosha
    Level 1 (19 points)
    Mac OS X
    Mar 1, 2013 8:09 AM in response to Moosha

    If someone would just tell us, this  will be fixed this week or this month or even before FCP X is updated.

    Begining to wish I had waited for the Pro, or what ever they are going to call it.

  • by alexgrainger,

    alexgrainger alexgrainger Mar 3, 2013 7:25 AM in response to jonuk85
    Level 1 (30 points)
    Mar 3, 2013 7:25 AM in response to jonuk85

    Just tested another machine with 680mx in Apple store in London, Brent Cross and it crashed. I am considering calling up and changing my order arriving in 4 weeks time to use the 675 graphics instead?

     

    Has anyone heard anything more from the Fcpx team on this? So you know if apple will let me change my order which I placed 2 weeks ago?

  • by sputuk,

    sputuk sputuk Mar 3, 2013 8:55 AM in response to alexgrainger
    Level 1 (0 points)
    Mar 3, 2013 8:55 AM in response to alexgrainger

    I've heard nothing since the 13th Feb which was when I was told that if the iMac team got an update from the FCPX team, they'd let me know.  Since I've not heard anything since, I have to assume that the FCPX team have not even provided the iMac team with an ETA - or at least, not one which they feel able to commit to publicly.

     

    My best guess is that this issue has exposed a more fundamental problem which is endemic in FCPX and which they're having difficulty re-engineering the whole app to avoid, especially as they will have already been working on new code internally.  They are probably also feeling that they'll need to have some "new feature" to announce along with any changes to address this issue to avoid it looking like it's only a patch for poor code...not that I'm cynical about how Apple deal with publicity about any flaws in their products at all based on previous experience with other bugs I've tried getting resolved in iOS etc where they've still refused to acknowledge that the problems I'd been having had been due to any flaw, hoping I'd just accept that the issue "magically" stopped after an iOS update.

  • by Tom Wolsky,

    Tom Wolsky Tom Wolsky Mar 3, 2013 9:30 AM in response to sputuk
    Level 10 (118,448 points)
    Apple TV
    Mar 3, 2013 9:30 AM in response to sputuk

    Really speculation but I would have thought it far more likely there is a problem in the OS.

  • by Dan Thomas (DAGWare),

    Dan Thomas (DAGWare) Dan Thomas (DAGWare) Mar 3, 2013 1:44 PM in response to sputuk
    Level 1 (109 points)
    Mar 3, 2013 1:44 PM in response to sputuk

    This is the exact reason why communication is so important. Apple doesn't keep us informed, so we start guessing. It's their own fault.

     

    With that said, I'm not really sure how our speculation helps any. Not that I know anything, but I would still advise against speculating, because the truth is, we have no real idea.

     

    Dan

  • by Gaddster,

    Gaddster Gaddster Mar 3, 2013 2:32 PM in response to Dan Thomas (DAGWare)
    Level 1 (5 points)
    Mar 3, 2013 2:32 PM in response to Dan Thomas (DAGWare)

    Is anyone using the top spec imac with 680mx and using FCPX well keno problems??

     

    Or are we all in the same boat here?

  • by Gaddster,

    Gaddster Gaddster Mar 3, 2013 2:34 PM in response to Gaddster
    Level 1 (5 points)
    Mar 3, 2013 2:34 PM in response to Gaddster

    "Without any problems" should say

  • by powder99,

    powder99 powder99 Mar 4, 2013 3:46 AM in response to Gaddster
    Level 1 (0 points)
    Mar 4, 2013 3:46 AM in response to Gaddster

    No I have exactly the same issue on my 27" with 680MX graphics.  To say I'm disappointed is an understatement.  Hopefully Apple will resolve quickly.

  • by Cliff Whitney,

    Cliff Whitney Cliff Whitney Mar 4, 2013 11:28 AM in response to jonuk85
    Level 1 (19 points)
    Mac OS X
    Mar 4, 2013 11:28 AM in response to jonuk85

    Just don't want everyone to forget this is happening with Motion 5 too.

  • by mpx_32,

    mpx_32 mpx_32 Mar 4, 2013 11:34 AM in response to jonuk85
    Level 1 (0 points)
    Mar 4, 2013 11:34 AM in response to jonuk85

    Same exact issue here

     

    27" imac i7 with 680MX graphics and 32GB memory.

     

    you can recreate the bug at will by using the "pixie dust" title. Definatly a hardware issue.

     

    spoke with apple tech support last week and no fix or ETA for fix available

     

    sad considering i waited 1 month for this "top of the line" computer and it cannot be used for the one application i need it for , Final cut pro X.

     

     

    now can anyone confirm that this issue will not happen with the 675MX graphic? i might downgrade in order to get work done!

  • by matamatario,

    matamatario matamatario Mar 4, 2013 2:45 PM in response to jonuk85
    Level 1 (0 points)
    Mar 4, 2013 2:45 PM in response to jonuk85

    I ran the hardware test with my technician on my imac 27 "

    The test is very accurate lasted more than two hours ..... NO PROBLEM FOUND. iMac is perfect.

    For sure it's a software problem

    I remind you that my mac is 27 "

      680mx gtx video card and 32GB of ram

  • by Gaddster,

    Gaddster Gaddster Mar 4, 2013 2:55 PM in response to matamatario
    Level 1 (5 points)
    Mar 4, 2013 2:55 PM in response to matamatario

    Now that is interesting, apple would like us to believe its the hardware ie nvidia whereas this is definite,y software based then??

     

    I just spent the last two hours editing, fcpx crashed at least 3 times and once it froze the whole imac!!!

     

    Ps I have 27" i7 680mx 1tb fusion and only 24gb ram!

first Previous Page 21 of 33 last Next