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 Render Failed

H

HD Hildebrand

Well-known member
Joined
Dec 28, 2006
Messages
857
Reaction score
0
Points
16
Location
planetearth
Website
www.hildebrandfilms.com
HI there,

I keep getting "render failed" when going from 4k raw in after effects to 2k 2048x1024 ProRes 4444 (also failed with tiffs and other formats). I've rendered many red projects and/or segments in the past with success, but everything I try on this one does not work.

I've tried the secret prefs, rendering out short segments (though that helps a bit but still fails), unplugging the entire system and raids for 10 minutes, purged, cleaned cache.

I'm running a mac 8 core with 16gb of ram.

Any wisdom is truly appreciated.

Cheers,
Dale
 
Are you rendering with multi-processors turned on/off?

Does it throw up warnings in RAM preview or just fail write to disk renders?

Have you tried the same render with just one clip, sans effects?
 
"Are you rendering with multi-processors turned on/off?"


Tried both on and off.


"Does it throw up warnings in RAM preview or just fail write to disk renders?"


Just on write to disk.



"Have you tried the same render with just one clip, sans effects?"


Tried one shot that had a dissolve. Still had problem only this time an Error 4 came up.
 
HD Hildebrand said:
Also, I do have some dslr timelapse sequences mixed in the sequences in PJPEG format. However I have rendered out the entire sequence in the past without error.
Click to expand...

Sounds like a RAM issue... checked your RAM settings? Is tuned for the type of rendering you're doing? Have you upgraded to snowL recently, added RAM recently?

How full is your boot volume and your target render disk?

Tried repairing Disk Permissions/Volume check on target drive?
 
"Check your RAM settings? Is tuned for the type of rendering you're doing? "

What do you suggest?

"Have you upgraded to snowL recently, added RAM recently?"

No.


"How full is your boot volume and your target render disk?"

Boot has about 16gb and target has 1.2 TB



"Tried repairing Disk Permissions/Volume check on target drive?"

Have not repaired disk permissions for a few days, though every time I do (since upgrading to FCP7 and 10.5.6) there are a lot of Quicktime permission repairs going on.

Thank you for all your help Brandon.
 
HD Hildebrand said:
"Check your RAM settings? Is tuned for the type of rendering you're doing? "

What do you suggest?
Click to expand...

Your boot drive is pretty full so make sure it's not caching to that volume, although you said it only happened on write to disk, any format, not RAM preview. Make sure your RAM cache size is set to allow for the RAM allotment you need if you are multi-processing, and higher if your not.

Not sure why this just cropped up for you, hope you get it going.
 
sure... if your multiprocessing, you need enough ram for each processor out of your 16 GB total, so you need to lower your ram cache amount (%) to free up enough ram so each processor has an even allotment to work with. If your not multiprocessing you can increase RAM cache to get better performance out of straight rendering. In Secret I would leave both unchecked as a baseline test. I'm not suggesting this is the issue but it's worth a look at.

i assume that it takes more frames to fail a render than you are able to create in a ram cache right? Anyone else knows of known issues to cause this with the new codec?
 
Repaired permissions, unchecked both Secret, turned off multiprocessing (it has been off for the past few tries), moved database and cache to a scratch disk, enable disk cache size is 4000MB.

Result: Render now seems to fail on the very first frame.



Brandon Kraemer said:
sure... if your multiprocessing, you need enough ram for each processor out of your 16 GB total, so you need to lower your ram cache amount (%) to free up enough ram so each processor has an even allotment to work with. If your not multiprocessing you can increase RAM cache to get better performance out of straight rendering. In Secret I would leave both unchecked as a baseline test. I'm not suggesting this is the issue but it's worth a look at.

i assume that it takes more frames to fail a render than you are able to create in a ram cache right? Anyone else knows of known issues to cause this with the new codec?
Click to expand...
 
Try purging your RAM thenstart a new project with the same settings, then drag your existing project into the new timeline. Sometimes that can do the trick.
 
Okay, sometimes your plugs dontnlike higher bit depths. If your project is 32 bit, try dropping it to 16. If that doesn't work, try 8 bit.
 
It's late and I didn't read through all the responses, if I'm redundant, my apologies. But having done a lot of 4k AE stuff, I will say this.

You need to use the secret preferences... hold shift down and select preferences and then you need to purge after every frame. It will then allow you to render. AE cannot handle 4k footage. What used to be my favorite application is failing miserably at keeping up with the times.

Anyway the secret preferences are your key to success, google them if my explanation did not make sense. I think they used to be called "shecret" preferences.

Anyway goodluck, the purging will slow down some renders, but not all renders suffer that much from it.

(Umm.... by the way I know it CAN handle 4k footage but more often than not it will crash on renders like this.)
 
Michael Schmitt said:
Try purging your RAM thenstart a new project with the same settings, then drag your existing project into the new timeline. Sometimes that can do the trick.
Click to expand...

Thank you so much Brandon, Michael, and Mark - these are all very valuable tricks for me to continue to refer to. I sincerely appreciate it. What seems to be the winning trick, in this case (it's still rendering - so knock on wood), is Michael's suggestion. I made a new project, imported the old, cut and pasted contents of entire timeline into new timeline. Tests so far have worked. I am now rendering a longer segment, but so far so good. Not only that, but the rendering seems significantly faster. I'll report back once I render out this segment.

Again, that you all for your generosity.

Respectfully,
Dale
 
Update and fyi - had a problem with another timeline/project (timelines are broken up by commercial break and divided into different projects). Tried the same technique of creating a new project, importing old and pasting old into new timeline. Render failed. After that, I rebuilt in the same way, only this time made sure I purged each sequence before cutting and pasting in new sequence. Render is working again.

Moral of the story, make sure you purge before you cut and past into a new timeline.

Cheers,
Dale
 
You must log in or register to reply here.
Back
Top