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

if you use 32 bits composition it may also be the cause.

or just watch some pr0n and go to sleep or call your girlfriend :DD

felt_tips said
Change (“Color”) to (1), manually. Bingo!

I have it like this:

comp(“MAIN”).layer(“WHITE_3D_PHONE_SCENE”).effect(“PHONE_COLOR”)(1)

but the comment left by the script said it didn’t touch this expression and neither the other 5 color expressions. So I have 6 expressions changed but not those I assumed. Now I need to verify what other scripts I write in the project and forget about them (started this project one month ago but worked only for a few hours)

render hangs on “Transform and Composition”, strange

ok thank you all for the overwhelming response definitely I will try some of the methods suggested here.

Render always hangs on Transform and Composite.

You need to look which layer begins at frame 167… or what happens. Look at which layers are active (or become active there). Which nasty FX are stealing all your RAM . 11000 pixel gaussian blur? Timewarp? It’s gotta be something like that.

The universalize is another issue. Try opening it in another language version and see what happens. Otherwise, just publish as is. If foreign language Ae users have a problem, then you’ll know about it soon enough and can fix it.

is not a complicated project, no heavy effects or huge images, is similar with the other three that I already have, so it should work. I tried the version saved before running the language script still hangs out, so is not the script.

I’m trying with CS6 now.

Adobe CS6 hangs on frame 167 of my awesome project.

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

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.

How about if you start at that frame? How about if you set everything to full and just put the playback head at that frame?

How about if you do an image sequence render, both starting and finishing at frame 167? How about if you do it at half res? How about frame 168?

The key is to be completely systematic. You could start soloing layers, for instance. But somewhere will be a piece of media, an effect or an expression that the renderer doesn’t like. You just gotta be systematic and search it down.

Maybe start by just soloing one layer and rendering the frame. Then add another layer to the solo’d set etc.

This kind of thing happens all the time. At least you’re not doing it against the clock with a client sitting behind you in a project that someone else built. Gotta be thankful for small mercies.

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.

edit: I’m doing this systematically (probably it will be all night since there are a lot of layers around the project. )

hangs out on that frame when exporting to psd sequence