|
|
|
|
|
 |
Mark Christiansen
Mark Christiansen is the author of After Effects Studio Techniques (Adobe Press). He has created visual effects and animations for feature films including Pirates of the Caribbean 3, The Day After Tomorrow and films by Robert Rodriguez. Past corporate clients include Adobe, Cisco, Sun, Cadence, Seagate, Intel and Medtronic, and broadcast work has appeared on HBO and the History Channel. Mark's roles have included producing, directing, designing and effects supervision, and his solo work has appeared at film festivals including L.A. Shorts Fest.
Long a Contributing Editor at DV Magazine during its heyday, Mark has been contracted as a marketing and technical writer on numerous occasions for Adobe Systems Inc. as well as related companies such as Red Giant Software. He has taught at fxPhd.com and Academy of Art University. His career began at LucasArts Entertainment and he is a Phi Beta Kappa graduate of Pomona College.
|
 |
Friday, July 08, 2011
The first featured script was also the first to be considered truly indispensible by most small studios
If you’re an After Effects power user who has gotten at all into scripts, you are most likely already familiar with BG Renderer, which really changed the game for scripts by providing an alternative to much more expensive solutions to any studio or individual in an After Effects render crunch.
Lloyd Alvarez apparently first devised this script on behalf of a studio that had huge rendering needs, yet was unable to harness the full computing power in-house for a simple reason. As great as the After Effects render queue is, when you click Render, the user interface - and thus the whole app - is tied up until the render is completed.
The industry solution for this problem used to be a separate render software, Nucleo Pro from GridIron Software, but Lloyd’s story is that the studio didn’t want to pony up the several hundred dollars that each license seat cost, despite that a few hundred dollars compares favorably with the cost of buying a new Mac Pro or other dedicated render station and the software to run on it.
Like other After Effects nerds, Lloyd knew that there is a free way to render After Effects compositions in the background, on spare or unused processors, while continuing to work in the After Effects UI. The aerender application installs along with the main app and can be run from the Terminal or a DOS shell, but the process is far from automatic. Getting it to work at all requires typing the correct UNIX string, and customizing it so that it doesn’t take so much processing power as to make the system unusable requires extra understanding.
BG Renderer was written to harness the full system resources while providing a low-cost interface available directly in After Effects, and it is available for all versions of After Effects from CS3 onward. If you have a system with multiple processors (you do) and sufficient RAM to support them (ideally in After Effects this means 2GB of RAM per proc, but you can sometimes get away with as little as 1GB if not working with large format footage and stills), and you’ve ever needed to keep working while pushing out a render, you’ve justified purchasing this script.
more »
Page 1 of 1 pages
|
 |
|
|
Mark Christiansen
The first featured script was also the first to be considered truly indispensible by most small studios
|
|
|
|
|
 |
|
 |
|
|
If you’re an After Effects power user who has gotten at all into scripts, you are most likely already familiar with BG Renderer, which really changed the game for scripts by providing an alternative to much more expensive solutions to any studio or individual in an After Effects render crunch.
Lloyd Alvarez apparently first devised this script on behalf of a studio that had huge rendering needs, yet was unable to harness the full computing power in-house for a simple reason. As great as the After Effects render queue is, when you click Render, the user interface - and thus the whole app - is tied up until the render is completed.
The industry solution for this problem used to be a separate render software, Nucleo Pro from GridIron Software, but Lloyd’s story is that the studio didn’t want to pony up the several hundred dollars that each license seat cost, despite that a few hundred dollars compares favorably with the cost of buying a new Mac Pro or other dedicated render station and the software to run on it.
Like other After Effects nerds, Lloyd knew that there is a free way to render After Effects compositions in the background, on spare or unused processors, while continuing to work in the After Effects UI. The aerender application installs along with the main app and can be run from the Terminal or a DOS shell, but the process is far from automatic. Getting it to work at all requires typing the correct UNIX string, and customizing it so that it doesn’t take so much processing power as to make the system unusable requires extra understanding.
BG Renderer was written to harness the full system resources while providing a low-cost interface available directly in After Effects, and it is available for all versions of After Effects from CS3 onward. If you have a system with multiple processors (you do) and sufficient RAM to support them (ideally in After Effects this means 2GB of RAM per proc, but you can sometimes get away with as little as 1GB if not working with large format footage and stills), and you’ve ever needed to keep working while pushing out a render, you’ve justified purchasing this script.