From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: After Effects and Rush
   Date: Tue, 14 Feb 2006 15:21:40 -0500
Msg# 1241
View Complete Thread (12 articles) | All Threads
Last Next
Victor DiMichina wrote:
We are trying to set up our Maya render farm to support After Effects too. Unfortunately, our IT guy says that we need a full licensed copy on every render node (and we aren't budgeted for that). Has anyone ever got After Effects to work with Rush as a render-only install?

Thanks

We use network imaging, so every single machine for workstations as well as render farms has the exact same image on their hard drives. Full installs of Maya, Shake, and After Effects. Since Maya, Shake, and AE offer unlimited rendering, and Rush only calls up the command line renderer for each respective program, there is no conflict whatsoever. As long as you have enough licenses for the full version of the app that your artists use, you'll be fine. In an answer to your question, however, I can say YES we have had Rush working with a render only install. In the end of the day, Rush simply calls up the command line app "aerender."

	Yes, definitely it all comes down to a command line invocation.
	So for instance, shake GUI licenses shouldn't be needed for rush rendering.
	(Unless they've changed their licensing since 1999, shake licenses the GUI
	separately from the command line, the gui being a bit more expensive then
	command line licenses. With macs, maybe licensing is 'free' somehow)

	IIRC, one of the cable companies had an AE issue where a few machines weren't rendering
	a particular scene correctly because the plugins were failing. They kept reinstalling AE
	(render only) and the plugins to no avail.

	Turned out to be those machines had the render only installs.. all the working machines
	had full installs. When they installed the full AE software and plugins, it went fine.
	I think the problem was some plugin they were using needed the full AE install. I'm afraid
	I don't know specifics, as there was no followup analysis by the customer once things
	were working. It did seem to be plugin specific. It's quite possible the plugin was
	hardwired for a non-"RE" path, and could maybe have been fixed by administering the
	plugin. Hard to say.
	
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)

Last Next