-
Cutting down on render times
Hi everyone,
Does anyone have tips on improving render speeds? I’m working on an HD project (1280×720, 8-bit, ntsc). I have a scene that contains 64 layers, motion blur activated on all layers, and the scene’s duration is 30 seconds. I started a JPG sequence render overnight, and so far I have managed to render half of the sequence – 15 seconds. This has taken about 10 hours, so there is a remaining 10-12 hours left for this scene. I’m running on a 2GB pentium 4 2.77Ghz pc.
Are these render times normal, or are they ways to cut down on render time? It’s my first HD project, so i just hope i’m not missing out on some tips. My soltion so far will be to render on 2 computers, so render times will decrease by half.
Any suggestions would be greatly appreciated. I’ve attached 2 screenshots of the project window + render window (with Estimated Time remaining) to give you an idea of how i’m working.
PROJECT WINDOW
” target=”_blank”>https://www.defasten.com/files/be-ae-01.gifRENDER WINDOW
” target=”_blank”>https://www.defasten.com/files/be-ae-02.gifThanks in advance,
Patrick
-
4 Replies
-
Sounds normal. I’m working on a program that involves on or about a hundred layer per scene, including DOF and motion blur. Top it off with some grain and CC toner, some renders have taken 48hrs (about 30 seconds of footage) — in SD.
Lights with shadows are HAYMAKERS. Be careful with them. Especially if you start to use more than one light emitting a shadow.
-
A famous tip I’ve seen alot here on the COW, is to leave the caps lock on, so it doesn’t have to display each frame as it renders. (especially helps if you’re leaving it overnight
-
a 3.8ghz or even a dual 3.8 would help out
-
if you’re rendering hd regularly, you might want to check out gridiron nucleo pro — cuts down on rendering big time and not terribly expensive
Reply to this Discussion! Login or Sign Up