Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects After Effects CS4 on Mac Pro 2.26 Nehalem horribly slow

  • After Effects CS4 on Mac Pro 2.26 Nehalem horribly slow

    Posted by Jens Schneider on November 18, 2009 at 5:58 pm

    Hey guys!

    Just curious to see if anyone has the same problems (and maybe a solution):

    AE CS4 on my Mac Pro 2009 8-core 2.26GHz (12GB Ram) runs terribly slow compared to a 2009 8-core 2.66GHz (8GB Ram).
    And I mean REALLY painfully slow. Render times differ vastly, way beyond what common sense might imply by the faster processor speed.
    Plus I get super weird behaviour with my Kona LHi and before that the IO HD. Realtime RAM preview would sometimes work, other times it would just stutter horribly giving me 3-4 fps with the exact same settings. Someone from Adobe wrote me a couple of months ago that this kind of behaviour seems to appear on just a handful of machines and that they are working on it but I haven’t heard back since.

    Anyone else experiencing this kind of weirdness?

    Jens Schneider replied 16 years, 6 months ago 31,165 Members · 1 Reply
  • 1 Reply
  • Jens Schneider

    November 19, 2009 at 8:31 am

    Hi Dave,

    thank you for the response.
    Both machines were crunching through the exact same project . All of the footage is in Apple ProRes 422 (HQ) at 1920×1080, 30fps. We really had a 1:1 comparison so to speak and the 2.66 smoked my 2.26. We are talking about 2 to 3 times faster.

    I’ll definitely try disabling Open GL as I suspect this to be the origin of another problem my box seems to have.
    When I linearize my workspace I sometimes get extreme banding on RAM previews that make it impossible to judge the outcome. When I pause however and let it redraw the quality is fine.

    I’m running hardware test this very second as I suspect something might be wrong with my box causing the unacceptable performance.

    We just finished a rather complex project and in retrospect we probably could have been done about a day or two earlier considering the insane render times the 2.26 had. If this doesn’t prove to be a hardware issue then I really don’t know what. I have my fingers crossed though.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy