ADOBE AFTER EFFECTS: Forum Expressions Tutorials Podcasts Creative Cloud

After Effects cs4 OS X Leopard with windoes 7 render clients?

COW Forums : Adobe After Effects

<< PREVIOUS   •   FAQ   •   VIEW ALL   •   PRINT   •   NEXT >>
kerrie nessaAfter Effects cs4 OS X Leopard with windoes 7 render clients?
by on May 31, 2010 at 9:20:51 am


does anyone know if i can install a render client on a windows 7 PC, when having a mac os x leopard system and serial???

do i need a windows serial? or can i install from the mac os x cd?

i couldn't find anything in the internet!

hope someone can help! :)

thank you! :)

Return to posts index

Walter SoykaRe: After Effects cs4 OS X Leopard with windoes 7 render clients?
by on Jun 1, 2010 at 4:04:48 pm

From "Network rendering with watch folders" in the Adobe help:
"If you have a full licensed copy of After Effects, you can set it up to work with render-only versions of After Effects called render engines. Your license entitles you to install as many copies of the render engine as you want on your network, as long as one activated copy of After Effects is installed on that network.

You install render engines in the same manner as the full version of the application, but you do not activate them. You run the render engine using the Adobe After Effects Render Engine shortcut in the Adobe After Effects CS4 folder."

In your case, you would need the Windows installer for AE CS4.

Let me first outline how network rendering works with After Effects, and then I will list a couple of bullet point notes from my experiences with network rendering. Much of this information is found in the manuals, but some of is not. All of it was learned the hard way.

How After Effects Network Rendering Works

You use Collect Files to get your project, its render queue, and all required footage together into a single folder. You configure the render nodes to watch that folder; once Collect Files is complete, it creates a render control file. On the render nodes, you select the folder to watch. When the render control file appears in it, the render nodes begin work according to the options it specifies. All watch folder network renders are done as image sequences, with each instance of AE on each render node working on one frame at a time.

There is no active communication among the render nodes, and the machine hosting the watch folder does not actively control them. Control is completely passive -- each machine looks at the shared storage to see if "Frame 0000" has been rendered yet. The first one to see that there is no image for "Frame 0000" will create that first file in the image sequence to claim responsibility for the frame, then begin rendering it. Finally, when the frame is complete, it overwrites the placeholder "Frame 0000" file.

As other render nodes join the party, they will see that "Frame 0000" already exists, so they will skip it and look for "Frame 0001." If "Frame 0001" already exists, they'll continue sequentially until they find the first frame that doesn't exist, create a file for it to claim responsibility for it, and begin rendering.

All the render nodes are also accessing footage from the shared storage, so that storage system is seeing many constant small reads and writes.

As you can imagine, this places some serious strain on the network and disk subsystem on the server.

Notes on After Effects Network Rendering

  • Each of AE's render nodes is self-directed; there is no supervisor or controller for distributing the workload. (See this thread where I explain how the AE network renderer works in some detail.)

  • You need a very fast network and very fast storage on your server. (Again, see the link above for my explanation of how the AE network renderer works and why this is necessary.)

  • Network rendering will create an image sequence on your shared storage. You can add a post-render action to re-import the image sequence and output a movie, but this will only be handled by one computer. If there is sound in your project, don't forget to output it separately if necessary.

  • You must specify the maximum number of render nodes when you set up the watch folder render. Multiprocessing increases your node count. For example, if you have four quad-core machines, you will have 16 render nodes.

  • All fonts and plugins used in your project must be installed on all render nodes.

  • Some plugins are licensed for unlimited use in render farms; others are limited to a specific number of render nodes; still others must be licensed for render nodes separately. Many plugins activate through their installers, but others activate with the AE environment itself. In this case, you will need a full license of AE in order to activate them. Most font licensing also limits the number of workstations they may be installed on.

  • Some plugins allow GPU acceleration. I highly recommend turning this off unless your render farm is completely homogenous.

  • Cross-platform file naming and path conventions can be tricky.

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

Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2016 All Rights Reserved