1 person found this helpful
Render order and how the items are related, most certainly. When you render from the main comp, AE would only request the frame it currently needs for temporal sampling. It is smart enough for that. By pre-rendering in combination with your other effects you may somehow trigger a weird loop that forces AE to request multiple frames multiple times based on how it processes the effects stack. Hard to tell without seeing your actual setup. I wouldn't even call it a bug, but it's certainly an unfavorable behavior. The only other option I could think of is that it is not doing any frame-blending when you render from you main comp. You should see that by differences in the resulting clips. In that case some layer switch (continuous rasterization springs to mind) may bypass the Timewarp effect/ disable some of its routines - by design or based on buggy code. i realyl think it's a combination of a few things.
I can say so much that the Timewarp effect performs beautifully in the final render, It is one of the first times I have used it, and I am very impressed. I adjust the speed several places, to match one action with another action. At a certain point, Timewarp only has a few frames to stretch over a longer time span, and it does this just beautifully, real convincing slowmo. So it definitely kicks in when doing the final render.
Anyhows - I do not give it too much thought.
What I did, I rendered the original clip and accepted 24 minutes to get it done. I then used it in the main comp, and can now preview at full speed.But one and a half hour in a nested comp - as opposed to seven minutes in the final render.. I suspect you are right, AE is working too hard and thinking too much I believe..
AE is working too hard and thinking too much I believe..
Quite possible that in this case the smart cahcing (to RAM) is working against it. I agree, though, rendering once then working at normal speeds sounds like an acceptable compromise.