From: Victor DiMichina <victor@(email surpressed)>
Subject: Re: Auto Rendering of QT's on jobcomplete
   Date: Wed, 27 May 2009 13:11:57 -0400
Msg# 1842
View Complete Thread (17 articles) | All Threads
Last Next
You can try something like this,  suited to your needs of course.   Note the eval command (thanks go  to Greg again and again,  of course)

################################
#!/bin/csh -f
if ( ! $?RUSH_DIR ) setenv RUSH_DIR /usr/local/rush
source $RUSH_DIR/etc/.submit
eval `/usr/local/rush/bin/rush -submit` << EOF
title           (your title)
ram             1
frames          (your frame range)
logdir          (your log dir)
command        perl //server/raid/2D_Apps/RushSubmits/Applications/submit-shake.app/Contents/MacOS/submit-shake-autolog.pl -render 1 1 Fail  /server/raid/path/to/someshakeproject.shk  0 -v -proxyscale 1 -v
cpus            +farm=10@10
notes           (optional)
EOF
if ( $status ) exit 1
# (eval eats the setenv command, so we duplicate it here)
echo "setenv RUSH_JOBID $RUSH_JOBID"
echo $RUSH_JOBID > /tmp/curr_jobid.txt
# Job #2 -
/usr/local/rush/bin/rush -submit << EOF
title           (your 2nd title)
ram             1
frames          (frame range)
logdir          (your log dir)
command         (another command)
cpus            +farm=11@980
waitfor         $RUSH_JOBID
waitforstate    done
notes           (optional)
EOF
####################################################


HTH
Vic


On Wed, May 27, 2009 at 7:54 AM, Craig Allison <craig@(email surpressed)> wrote:
Ok, so I've finally got around to looking into this and have decided to change my original way of thinking and give the artists the opportunity to render a quicktime on the farm once they are happy with the results previewed in Framecycler.

I have taken the submit-shake-quicktime script and amended it to allow users to select which film they are working on, select the first frame in the sequence to render and dialogue for slate notes etc - the combination of all this information chooses the correct shake setup script on the network, replaces the variables, saves a copy and submits it to the farm.

The script renders a 2K slate & greyscale (named and numbered correctly) and also a QT with the appropriate settings for the production.  I have it working fine but now want to speed it up by splitting the job into two, i.e. one script to render the two 2k frames and one script to render the QT.

I've got rush creating the 2 distinct shake scripts to render, but don't know how to get 2 scripts to render with a single rush submit, is there an easy way?

Cheers

Craig


Craig Allison

Digital Systems & Data Manager

The Senate Visual Effects

Twickenham Film Studios

St.Margarets

Twickenham

TW1 2AW


t: 0208 607 8866 

skype: craig_9000

www.senatevfx.com

On 19 Dec 2008, at 09:20, Abraham Schneider wrote:

[posted to rush.general]

Greg Ercolano schrieb:
Sounds interesting, but unless they have a non-gui interface,
it's not something I think Rush can control properly.

yes, that's right. I'm doing it in two steps at the moment: rush=20
executes a jobdonecommand script which creates an entry with the path to =

the image sequence in a queue folder. A small python script on my QT=20
creation Mac is watching this folder and does the actual 'feeding' of=20
the Silverstack rendering app (called Cinemator).

That's not a perfect solution but it works quite well for us at the=20
moment. And with the template files it is easy to do different burnins,=20
codecs, framerates, etc. depending on project or user choose.

Abraham

--
Abraham Schneider
Senior VFX Compositor, 2 D Artist
ARRI Film & TV Services GmbH   Tuerkenstr. 89   D-80799 Muenchen / =
Germany
Phone +49 89 3809-1269     EMail aschneider@(email surpressed)
ARRI Film & TV Services GmbH
Sitz: M=FCnchen  -  Registergericht: Amtsgericht M=FCnchen  -  =
Handelsregisternummer: HRB 69396
Gesch=E4ftsf=FChrer: Franz Kraus; Thomas Till





--
Victor DiMichina
Pixel Magic
818.760.0862

Last Next