Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects Renders are problematic

  • Renders are problematic

    Posted by Brannon Bates on November 19, 2010 at 10:25 am

    When I render something, other comps are popping up in the render. Even if I render a solid red layer in a completely new and blank project, the footage from other projects are dropping frames into the rendered red solid…. Did I explain that sufficiently? Please help if you have experienced this.

    Brannon Bates replied 15 years, 5 months ago 2 Members · 13 Replies
  • 13 Replies
  • Kevin Camp

    November 19, 2010 at 4:05 pm

    it sounds like something is going wrong with the cache. try choosing edit>purge>all and see if the problems go away.

    Kevin Camp
    Senior Designer
    KCPQ, KMYQ & KRCW

  • Brannon Bates

    November 19, 2010 at 9:14 pm

    THank you guys for helping 🙂 I’m on win7 x 64 and it is cs5. I have tried to purge all, and cleared my disk cache and even renamed the project that was dropping itself into other renders (and deleted the original project). Somehow renders are still finding it and dropping its frames in.

  • Brannon Bates

    November 19, 2010 at 9:33 pm

    3gb ;/ I’ve been rendering AE cs5 for several months on this project i’m on but it just started a few days ago. I had started using nucleo pro recently but it was working fine for a week before the problem started. I also updated my java recently, not sure if either of those could be a problem.

  • Kevin Camp

    November 19, 2010 at 9:42 pm

    is this a problem with any comp/project, or is it specific to one?

    there are some time effects (cc widetime and cc time blend) that use cached frames and there is a workflow to use when using those effects, so if it is specific to this comp/project and you are using those effects, then that may be the issue.

    if it is any comp/project, and this has recently occurred i would try a reboot.

    other settings you could try is to disable disk caching in the disk cache preference, disable multiprocessing in the multiprocessing preference and disable opengl in the preview preference.

    you might even try resetting the prefs file by holding shift-option-command (osx) or shift-ctrl-alt (win) when launching ae.

    Kevin Camp
    Senior Designer
    KCPQ, KMYQ & KRCW

  • Brannon Bates

    November 19, 2010 at 9:58 pm

    Those were great suggestions, I tried them all with no luck. I’m stumped. It is any project btw. I reset preferences, made a new project, new comp, added a gray solid, rendered it, and still seeing other frames from other comps in the final output.

  • Brannon Bates

    November 19, 2010 at 10:07 pm

    kapiche 🙂 I’m not using multiprocessing. I just finished the adobe update, still no luck. Has to be a link to a cache somewhere.

  • Kevin Camp

    November 19, 2010 at 10:14 pm

    you mentioned nucleo earlier, have you tried disabling nucleo? it makes sense that nucleo would have it’s own cache for the background processes that it has to launch, maybe it is causing this…

    Kevin Camp
    Senior Designer
    KCPQ, KMYQ & KRCW

  • Brannon Bates

    November 19, 2010 at 10:23 pm

    I uninstalled nucleo and it didn’t help. However I reinstalled it and it still had the cache info from before. I deleted its cache, didnt help. Nucleo rendered out a couple dozen comps fine before this issue. I really didn’t have any problems until someone worked on my computer and changed the java version. Could java do this? Or is it a nucleo issue?

  • Brannon Bates

    November 19, 2010 at 10:24 pm

    I am updating my nvidia driver right now too.

  • Brannon Bates

    November 19, 2010 at 10:53 pm

    Well I updated CS5, updated my drivers, cleared all cache I could find, still no luck. I guess my best question to you guys is what are the known paths to cache data for after effects? If I clear all out maybe it will work?

Page 1 of 2

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