Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

After Effects Deleting Sequence Render Information

R

Ryan Lightbourn

Well-known member
Joined
Nov 3, 2012
Messages
310
Reaction score
0
Points
0
Location
Orlando, FL
I can't find anything on the internet about this.

It's incredibly frustrating and time consuming...why won't After Effects retain render information in the sequence, and why won't it render out longer sequences (doesn't matter how much storage I devote to AE)?

If anyone has a workaround, thanks in advance!
 
Please explain your workflow.

I'm not sure what you mean by render long sequences?

If you are rendering with CS6 or older over a SBM or AFP network there is a 2GB file limit bug that both Apple and Abobe have been dealing with for years.

And when you mean render information, do you mean the log text file?
 
Are you using the render queue? Each time you render from there, your previous render settings are kept. you can simply copy and paste the previous render and use it as your next render. As to the render long sequences issue, you need to go into more detail. How long is your sequence? What resolution is your footage? What effects have you applied to the footage? How much Ram do you have. Have you tried switching between multi processing on and off?
 
I'm referring to the renders to playback/preview my sequences in real time. Whether I hit the "0" key or choose Ram Preview in the menu, my sequence will render (partially if over 2 mins) and show a green indicator line, but the second I stop it, the render indicator line (or whatever it's called) goes blue (over some or all clips), or simply disappears (over some or all clips).

Ram settings, storage capacity, multi-threading, etc. doesn't really make a difference. This has been happening to me for years...6-core desktop, quad-core iMac, MacBook pro, etc.
 
This happened a lot for me in CS4 which was possibly the worse upgrade in the history of Adobe products.

We had 32GB RAM in 2008 Mac Pro with Quadro 4000 and 4800 at the time.

Did not get the same issues with CS6 and Mac Pro 2012 as well as CC on new Mac Pro.
 
In Adobe CC, the RAM render preview should not be acting the way you describe. In fact, the realtime preview settings in CC are very smart, only requireing re rendering of clips that have big changes to them. Sometime small changes can be re rendered very quickly. Which version of After effects are you using. What resolution of footage are you editing with (and what are your preview settings - Full, half, quarter)? How much Ram do you have insalled? 4K and 5K footage can eat up ram very quickly at full resolution.
 
Stefan Scherperel said:
In Adobe CC, the RAM render preview should not be acting the way you describe. In fact, the realtime preview settings in CC are very smart, only requireing re rendering of clips that have big changes to them. Sometime small changes can be re rendered very quickly. Which version of After effects are you using. What resolution of footage are you editing with (and what are your preview settings - Full, half, quarter)? How much Ram do you have insalled? 4K and 5K footage can eat up ram very quickly at full resolution.
Click to expand...

I'm using After Effects CC. In Premiere the renders work as you describe.

Resolution & preview settings don't really affect anything. I have 32GB Ram. I usually stay in 1/2 res when cutting 4K.
 
Another update, I disabled Multiprocessing in OSX and now the renders don't disappear. Windows is still working a little faster for me though, so I'm sticking with 7 for now.

EDIT: I think it was a combo of clearing cache and disabling multiprocessing
 
Last edited:
You must log in or register to reply here.
Back
Top