matx wrote:
> [posted to rush.general]
>
> On 2008-12-16 11:16:35 -0800, Craig Allison <craig@(email surpressed)> said:
>> I'll have a look at AppleScript as a possible interim solution,
>
> We use an AppleScript to interface between a template Shake script and
> the image sequence selected (drag drop folder onto script). After the
> images are rendered by an artist they make a QT using this tools which
> basically substitutes new fileins and fileouts, etc.
If this is something you can call as a command, then
you can make it the jobdonecommand for the job.
> I'd love to see how you could incorporate a Shake script in a
> shake-submit for Rush as a followup job using the variables of the
> previous job. Can RUSH pass variables to another job?
You can pass anything you want, but you'd need to add
the operation to do it.
The manual way is: submit your shake job, and lets say
its jobid is "tahoe.1". While it's rendering, you can
fill out the submit-shake-quicktime.pl form, and set
these fields:
WaitFor: tahoe.1
Wait For State: Done
..and submit the job. This way when your shake job
finishes the last frame, the shake quicktime script
runs to do the QT conversion.
Or, if you're clever with scripting, you can modify
the submit-shake script to automatically fire off
submit-shake-quicktime to do the QT conversion as a "jobdonecommand".
It's currently a two step process use submit-shake-quicktime.pl,
After you submit the shake job, you can use submit-shake-quicktime.pl
to submit a separate job to handle the conversion.
It needs to know the input images and output quicktime file.
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|