Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects Weird AE error message driving me batty

  • Weird AE error message driving me batty

    Posted by Devin Uzan on October 24, 2006 at 1:18 am

    I’m doing some really simple stuff on 4K images and keep getting this error with simple effects like Hue/Saturation, Levels, Brightness.

    “After Effects error: “name of effect” returned invalid max_result_rect from PF_Cmd_SMART_PRE_RENDER”

    When I quit and open AE again it sometimes goes away only to reappear again after a while.

    Dual 2.5 G5, 4 Gigs RAM, AE 7, OS 10.4.8 (maybe I shouldn’t have updated)

    Preferences trashed

    Andrea Cowen replied 9 years ago 4 Members · 4 Replies
  • 4 Replies
  • Devin Uzan

    October 24, 2006 at 1:28 am

    Well I snooped around a little and found out this is a known bug. I guess I will work in 6.5 for these simple 4K matte paintings.

  • Jeremy Richardson

    November 1, 2006 at 1:35 am

    I’ve been having this same error. I’ve found that if I put a Color Balance (HLS) effect before the offending effect it seems to work. I just leave the Color Balance so they are not affecting the image. Play around with the ordering of this effect in comparison to offending effects. May also work with certain other effects.

    later

  • Erik Waluska

    February 17, 2009 at 9:51 pm

    I had the same problem but I am running AE CS3 on an Intel Mac and I am using the levels effect in an adjustment layer at the top of my layers stack as a TV safe levels filter. Every time I tried to render I would get the error message described above.

    I tried to add a Hue/Saturation and several other effects and changed the order of the effects, restarted After Effects and even cursed at the computer but nothing worked.

    Then I twirled up the histogram for the Levels effect in the effect controls window so that the graph was not visible and also toggled the “Clip Output to Black” and “Clip Output to White” options from the default “Off for 32bpc Color” to “Off” and then back to “Off for 32bpc Color”.

    I’m not sure which one of those things cleared up the bug but now it is rendering fine.

    -E

  • Andrea Cowen

    July 10, 2017 at 7:17 pm

    I found that if I lowered the resolution of my preview i.e. the downsample factor (not the magnification of the preview) then I no longer got the error message.

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