Work rage - methods to calm down (Ae rendering problem)

doru said
Project renders fine till frame 167. If I jump 167 and render from 168 and up still works perfect. Strangely, After Effects struggle with couple of frames after 168 then starts working again with no problem.

No new effect is added at frame 167, nothing is created, nothing is destroyed is just a phone that moves around. Also, the same project worked perfectly till 7-8 hours ago when I create the last working test render.

maybe along the way, the ae file got corrupted or maybe is just bad luck.

This is a computer. 100% rational. I guarantee you there will be a reason for it. I’ll ask one more time… does that frame render at half res?

If it’s any consolation I’ve spent around 12 hours today sorting out a similar nasty technical problem on a job. Just getting it sorted now.

felt_tips said

jvirgos said
i think project is corrupted. make a new project then import the project with the issue. drag the layers to a new comp. render.hope it works. it did it to me sometime ago

Bad idea. Almost certainly not the case. I have not seen a corrupted project that opens in 16 years of After Effectsing.

Yep.. nothing to lose, I guess. As long as getting the layers set up in a new comp doesn’t take too long.

I’d still try all the rendering stuff first though.

Render between 166 and 168: without effects first. Than try without footage 01. If it doesn’t work bring it back and delete footage 02 for example. Repeat until you find the culprit

VICTORY !!!!!!

it passed frame 167! also it took 2 minutes to reach frame 167 instead 8 minutes as before.

now let see if I’m an idiot or no.

so I have a composition with 3D layers inside, all those layers had the “motion blur” switch enabled (forget to disable that ).

the composition “motion blur” switch at the top was disabled.

but still, ae rendered the motion blur. Is this normal? With the switch disabled?

and why it worked fine all day, then suddenly started calculating the motion blur?

It hanged at frame 167 because maybe it was trying to calculate the motion blur for all those layers.

edit:

So that “motion blur” comp switch at the top is for previews only. “Enables Motion Blur for all layers with Motion Blur switch set” Is said nothing about preview so I assumed it enables disables motion blur for the final render.

now what adobe intends with “preview” at this link is unclear. ram preview? , opengl render preview?

jvirgos said

felt_tips said

jvirgos said
i think project is corrupted. make a new project then import the project with the issue. drag the layers to a new comp. render.hope it works. it did it to me sometime ago

Bad idea. Almost certainly not the case. I have not seen a corrupted project that opens in 16 years of After Effectsing.

you are a master i know but i can say with any doubt that i ve seen corrupted projects(after premiere and encore!) that once you import in a new project works right.i did it jumping into ae versions. nothing lose to try.

There is no such thing in computing world as random and corrupt. Everything is 0 and 1, then its pixels and numbers. And every one of them has been predetermined before it happens, it has been calculated in the system of complex algorithms.

Such thing as corrupted AE project with no reason simply doesn’t exist sometimes there is love without a reason, sometimes we buy shit without a reason but in computing world there always is a reason. And it is ALWAYS solvable and if not then it means it is broke/deleted(magnetized)/short-circuited in material world.

Render motion blur settings override comp motion blur settings, but not layer motion blur settings.

I’d still strongly advise you to find the specific layer that’s causing the problem, though.

felt_tips said
I’d still strongly advise you to find the specific layer that’s causing the problem, though.

I found it. I had 20 and something layers with that motion blur enabled. I did that as a test to see how it looks some time ago. I decided that it was not a big improvement for the time that it took ae to calculate a frame so I disabled the motion blur but only from the switch at the top of the layers.

Ae did not show an error, that confused me, now I understand it calculating the motion blur. for some reason that particular frame took so much time to calculate that the other frames so I lost patience and kill the application. Then, while I did the tests to find out the problem I had no time to wait for the software to end the calculations. Kinda lame circle of losing time.

Still don’t know why suddenly it started calculating the blur after three days of no problem

I had similar problem ricently when tried to render about 8 min from AE into Quicktime H.264. It stoped some frame in the midlle few attempts. After experimenting I found that it render into AVI with no problems.

Best Regards, Andrey