From: "Michael Oliver" <moliver@(email surpressed)>
Subject: Re: Shake rendering
   Date: Wed, 28 May 2008 16:25:30 -0400
Msg# 1746
View Complete Thread (3 articles) | All Threads
Last Next
setting the environment variables work wonderfully for shake!  Thanks Greg. 
You can actually use environement variables to set a wide range of things 
including file-in's, file-outs, text fields, and a plethora of other things. 
Just make sure you choose your environment variable names appropriately or 
you could end up overwriting an important one!


"Greg Ercolano" <erco@(email surpressed)> wrote in message 
news:1727-rush decimal general at seriss decimal com...
> Michael Oliver wrote:
>> I know shake has a very indepth command line renderer that will allow you 
>> to
>> parse a variety of things including file-in, file-out, resize, adding 
>> text,
>> etc....
>>
>> I'm looking for a way to execute a shake script that has already been
>> created, but be able to change certain variables (ie. file-in nodes).
>> Anyone know if this is possible without having to send the shake script 
>> to a
>> parser first?  There will only be one file in and one file out.
>>
>> For example..could you send a command like:  shake -exec foo.shk -fi
>> targas.tga -fo targasQT.mov  (I know this command does not work..looking 
>> for
>> something similar that does! :) )
>
> Hmm, others should probably respond here who know shake
> better than me..
>
> But as a side note, IIRC, you can use environment variables
> to communicate with your shk script.
>
> So eg. your .shk file you might have:
>
> IN1 = FileIn("$file_in", ..);
> [..]
> OUT = FileOut(COMP, "$file_out", ..);
>
> ..and so, from a csh script, you might invoke shake this way
> to pass those values to the .shk file:
>
> #!/bin/csh -f
> setenv file_in  "targas.tga"
> setenv file_out "targasQT.mov"
> shake -exec foo.shk
>
> ..or from perl:
>
> #!/usr/bin/perl -w
> $ENV{file_in}  = "targas.tga";
> $ENV{file_out} = "targasQT.mov";
> system("shake -exec foo.shk");
>
> I have not tested this, just going by the shake docs on
> environment variables, and some long ago braincells on
> shake file programming.
>
> I'm not sure if the ""'s are needed in the .shk file around the
> $file_xxx variables.
>
> I'm also not sure if there's a way to more easily pass variables
> via the shake command line.
>
>
>
>
> -- 
> Greg Ercolano, erco@(email surpressed)
> Seriss Corporation
> Rush Render Queue, http://seriss.com/rush/
> Tel: 626-795-5922
> Fax: 626-795-5947
> Cel: 310-266-8906 



Last Next