Hey all, I’m attempting to use Draft to assemble an h.264 preview of a large image sequence rendered out from AE. The actual frame count is about 15,000 frames but even in my test of just doing the 1st 150 frames the machine I’m rendering on seems to just sit there. I can see the Draft python process eating a bunch of RAM but I see no movement or output from the script. Any thoughts on how to diagnose this one?
Thanks.
Vaughn
Deadline 6.1
Windows 7 64bit4
My first instinct is that it might be “thrashing”, although I haven’t experienced this problem with Draft myself… what dimensions are your images? Would you be able to send us a subset of images for testing? (Either attached here, or zipped to support@thinkboxsoftware.com.)
Thanks,
Andrea
Thanks Andrea, it turns out, I’m impatient. The render completed in about an hour which, in hind-sight, should have been expected. I was confused mostly because I wasn’t seeing any progress logged by the slave. I was expecting somesort of feedback there.
Thanks for replying!
Vaughn
Not a problem.
If you want to see progress logged by the slave, you need to add two lines to your script in your main processing loop:
[code]for frameNumber in range(startFrame, endFrame+1):
percentage = 100 * (frameNumber - startFrame) / (endFrame - startFrame + 1)
print "Encoding Progress: %s " % percentage
encoder.EncodeNextFrame( […] )
[…][/code] The lines you’re adding are the one that computes the progress (percentage), and the one that prints it out.
Cheers,
Andrea
That’s fantastic, thanks!
V
Welcome!