Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects RAM preview showing old imagery in destroyed output.

  • RAM preview showing old imagery in destroyed output.

    Posted by Michael Nielsen on March 5, 2014 at 3:50 pm

    Hey all.

    Has anyone else experienced this? Apologies if it has happened since v.1. Im on a pc, so ram previews are preferably rendered in .avi.

    https://www.vredefilm.net/HP_REVID/render_crazy.png

    So I did a ram render of some work that I just wanted out asap. The frames are icky and riddled with errors. But what struck me as completely absurd was that there were frames in the output from an entirely different job and project.

    Can anyone explain what is going on, and how I might avoid those icky ram preview renders?

    Walter Soyka replied 12 years, 2 months ago 3 Members · 4 Replies
  • 4 Replies
  • Ridley Walker

    March 6, 2014 at 1:04 am

    [Michael Nielsen] ” there were frames in the output from an entirely different job and project.”

    Very likely due to the media and disk cache retaining frames from previous RAM previews. Try emptying the caches, go to Preferences > Media and Disk Cache and click Empty Disk Cache, then click Clean Database and Cache.

  • Michael Nielsen

    March 6, 2014 at 2:41 pm

    Thanks for the input. The odd thing is, if I use another codec, say h.264, for the preview render, it flies just fine. I only have this issue with .avi.

  • Michael Nielsen

    March 6, 2014 at 2:54 pm

    Thanks for the thoughts. Trashing prefs did not resolve the issue.

    I am running a Windows 7, i7 2600K hyperthreaded, tho I dont use multiprocessing for internal renders, 32gb ram and an array of nas, local drives and ssd´s. Dual gtx670 cards, but the preview is not rendered with raytracing enabled. Latest CC-update.

    The issue is more of an output than an input based one. Everything I import, ranging from .ai, psd and jpg-files to camera and output based .mxf, .mov, .mp4, etc. has presented this issue, but only if the ram render output is an .avi container. Mp4, mxf, mp2 and image sequences fly just fine, but some are of course sorely missing in depth and so on.

    I just want a complete lossless translation of the ram-preview and I want it in .avi. But the issue persists. Is it possible that the .avi becomes so big that its choking my pipeline?

  • Walter Soyka

    March 6, 2014 at 10:12 pm

    [Michael Nielsen] “Thanks for the input. The odd thing is, if I use another codec, say h.264, for the preview render, it flies just fine. I only have this issue with .avi.”

    None of this should be happening — especially that nonsense with the cached frames.

    Would you consider filing a bug report [link]?

    Walter Soyka
    Principal & Designer at Keen Live
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    RenderBreak Blog – What I’m thinking when my workstation’s thinking
    Creative Cow Forum Host: Live & Stage Events

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