Activity › Forums › Adobe After Effects › Massive Render Strain and a Need to Fix That NOW.
-
Massive Render Strain and a Need to Fix That NOW.
Walter Soyka replied 12 years, 9 months ago 5 Members · 17 Replies
-
Jim Zarbaugh
December 4, 2013 at 11:59 pmSo the settings look OK?
Thanks- I think breaking it into smaller pieces for render is a good idea.
-
Jim Zarbaugh
December 5, 2013 at 2:29 amWalter- I posted my multiprocessing and memory info. If you get a chance, let me know what you think. I really just now enough about the technical side to do more harm than good.
-
Jim Zarbaugh
December 5, 2013 at 2:33 amDean,
I posted memory and multiprocessing info, but still not sure what the disc configuration is. If you get a chance, can you take a look and give me your opinion? It would really help.
I am currently re-compressing all my animation files to about one sixth the data size. I can hardly tell the difference visually- I am really quite shocked. However, how this will help the final product render is still left to be seen.
Thanks again
-
Dean Pickersgill
December 5, 2013 at 8:17 amJim, the other fella’s you’re talking to on this thread are much more enlightened than I on these matters so I’ll bow out for the moment to reduce the noise 🙂 I’ll chip in should I see something they miss (although I doubt that) but for now wish you success.
-
Walter Soyka
December 6, 2013 at 1:57 am[Jim Zarbaugh] “Walter- I posted my multiprocessing and memory info. If you get a chance, let me know what you think. I really just now enough about the technical side to do more harm than good.”
Jim, I generally recommend leaving one quarter of your total RAM and half your total CPUs for other applications. You should also consider lowering your RAM allocation per background CPU. Your comp is large, but you might be able to get away with 3 GB per background CPU.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events -
Walter Soyka
December 6, 2013 at 1:59 am[Dean Pickersgill] “Jim, the other fella’s you’re talking to on this thread are much more enlightened than I on these matters so I’ll bow out for the moment to reduce the noise 🙂 I’ll chip in should I see something they miss (although I doubt that) but for now wish you success.”
Dean, the more the merrier! Please do feel free to contribute.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events -
Walter Soyka
December 6, 2013 at 2:03 am[Dave LaRonde] “I’d nest that one big, huge comp in the smaller comps, taking great care to position it properly for each movie you have to make.”
This actually quadruples the rendering required for anything that’s not cached, because the entire comp will be rendered anew and then cropped for each of the four little “window” renders.
Better to cache, or to use multiple output modules for the same render queue item (which will render the large image once and then crop it for each output module), or to render a single large movie/image sequence and use that as the source for these cut-ups.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events
Reply to this Discussion! Login or Sign Up