This should have already been set up by your sysadmin, or the person who installed the rush software:
This script will be executed not only by the user to bring up the submit-afterfx GUI, but it will also be executed on all the render machines to run the renders.
To ensure the renders run with the proper environment, you'll need to modify these lines at the top of the script to point to where you have your version(s) of After Effects installed. Some examples are included in the file already; modify as needed:
################################################################## ### AFTER EFFECTS SPECIFIC VARIABLES -- CUSTOMIZE AS NECESSARY ### ### See After Effects docs for more info. ### ################################################################## if ( $G::iswindows ) { # WINDOWS $ENV{PATH} = "$ENV{PATH};c:/Program Files/Adobe/After Effects CC/Support Files"; $ENV{PATH} = "$ENV{PATH};c:/Program Files/Adobe/After Effects CS6/Support Files"; $ENV{PATH} = "$ENV{PATH};c:/Program Files/Adobe/Adobe After Effects CS5/Support Files"; $ENV{PATH} = "$ENV{PATH};c:/Program Files/Adobe/Adobe After Effects CS4/Support Files"; $ENV{PATH} = "$ENV{PATH};c:/Program Files/Adobe/After Effects CS3/Support Files"; } elsif ( $G::ismac ) { # MAC OSX $ENV{PATH} = "$ENV{PATH}:/Applications/Adobe After Effects CC"; $ENV{PATH} = "$ENV{PATH}:/Applications/Adobe After Effects CS6"; $ENV{PATH} = "$ENV{PATH}:/Applications/Adobe After Effects CS5"; $ENV{PATH} = "$ENV{PATH}:/Applications/Adobe After Effects CS4"; $ENV{PATH} = "$ENV{PATH}:/Applications/Adobe After Effects CS3"; } |
AfterFX (and any plugins you use) may also depend on other variables; define those in the same section using similar script syntax.
Be sure the shortcut points to a copy on a file server, and not to local files in c:\rush\examples (windows) or /usr/local/rush/examples (unix).
Should be as simple as clicking on your desktop shortcut.
If you prefer using a terminal window, be sure to run the script with an absolute UNC path, eg:
perl //server/jobs/rushscripts/perl/submit-afterfx.plIf you don't run it with an absolute path, the frames will fail because rush didn't have the absolute path to the submit script.
The interface should pop up. If it doesn't, verify (unix) the first line in the script's path points to the correct location of your perl binary, or (windows) the '.pl' extension is configured to correctly invoke perl.
Click the help button (buttons with '?') for any field you want to know more about.
When the GUI pops up, note there are various 'Advanced Options' available if you scroll the window down.
It is assumed you are able to bring up the submit script from a desktop shortcut (which you can make by following these instructions for Mac OSX, Windows, or Linux)
For the Scene Path, navigate to your .aep project using the Browse button. If it is your first time submitting, you may have to manually type in the //server/volume name in order to get a directory listing.
Avoid using a mapped drive letter (z:/yada/yada) to get to your project, to avoid problems with drive maps, eg. when people log out, and the drive maps disappear.
Leave the 'Output Path' blank to use the default in your .aep project file.
Enter the exact comp name that is queued to render. If you have more than one comp to render, you must do separate rush submissions for each one.
This is the range of frames you want to render; normally two values separated by a dash, eg. '1-100'.
You can also specify individual frames, multiple ranges, or cobinations of both, eg. '1 10 20-30 400-900', which would render frames 1, 10, 20 through 30, and 400 through 900.
This will render the comp in 5 frame chunks, and helps speed up the job by limiting the number of times AE has to start up.
In our case, lets use any 5 available cpus at the lowest priority:
+any=5@1
Advanced Options are optional. To see them, use the scroll bar to scroll down to check their settings.
Click the help button (buttons with '?') for any field you want to know more about.
This should submit your job, and a window indicating the jobid should pop up, followed by an irush interface with the jobid already set to the new job.
The next time you bring up the submit form, it will have all the values set from the last execution. Note that you can then save this as a form so you can easily recall it later.
For more info on the irush interface, see the irush tutorial.
Hit 'Frames' in irush to watch the progress of your job.
If some frames are running, or got done already, click on
some, and hit 'Logs' to see the output of the perl commands
you entered.
When you're finished with the job, hit 'Dump' in irush.