|
Re: After Effects rendering
|
Posted by:
Asa Hammond
Date:
06-07-2010,
14:15:PM
|
Yes you can render these crops separately, but the crops are a post process to the actual render, so you would be rendering the whole frame and then cropping that on each machine, ballooning your render time total. AE always renders whole frames. =(
Asa I don't know if it would be possible, but in theory (TM), it seems like one could make an AE script (tweaked JavaScript) that would add subframes to the render queue using the "crop" function in the output module. You could then add a final task to the render queue to assemble these subframes. The assembling of the subframes might need to be done as a post-process, using something like ImageMagick. On Mon, Jun 7, 2010 at 10:53 AM, Greg Ercolano <erco_mlist@seriss.com> wrote:
Lyn Norstad wrote:
> Is there a way to distribute rendering of a single frame from Ae across
> multiple render nodes?
>
> Kind of like Mental Ray standalone w/Autodesk, but for After Effects?
Yes, "aerender" is their command line tool. An example:
aerender -project //yourserver/scenes/myscene.aep -comp "comp1" -s 1 -e 10
..to render a 10 frame sequence.
See 'aerender -help' for details; if you don't specify the -comp,
it will ignore your frame range and render all frames for all selected
comps.
There are some other caveats with using aerender.
Adobe never completely separated the GUI from the command line tool.
In all implementations of AE I've seen since aerender came out
(about 5 years ago or so), aerender invokes the GUI application
and makes a connection to it to tell it what to do, and reads back
status (error messages, progress, etc) and prints it to stdout/err.
The GUI app runs, but its windows are all stowed (or 'hidden' as much as possible)
so as not to disrupt any users working on the window manager of that machine
at the time.
However, because the GUI app /is/ invoked but hidden, it still has
hidden interactions with the window manager, which can create some
headaches with permissions between the render running, and the user
who is currently logged into the window manager.
On OSX, if the user invoking aerender is the same user as the user
logged into the window manager, it should work OK. But if the users
differ, there will be trouble. Sometimes making the app setuid root
helps solve that problem, but lately Adobe made some changes that
may affect that workaround.
_
StudioSysAdmins-Discuss mailing list
StudioSysAdmins-Discuss@studiosysadmins.com
http://mailman.studiosysadmins.com/mailman/listinfo/studiosysadmins-discuss
-- Jeremy Oddo Amalgamated Pixels 2475 Townsgate Rd. Ste. 220 Westlake Village, CA 91361 818.865.8423
|
