[Sidefx-houdini-list] advice on a "set shot" workflow inwindows!??!! (WTF)
Andrew D Lyons
tstexture at gmail.com
Wed May 26 00:53:09 EDT 2010
So tab/enter works as "send" in gmail. Awesome for coders... Let me try and
finish that email so it makes sense:
You can put some cool data (and related methods) such as your current shot
in a python 'pipe' object and monkey patch it to the hou module on startup
(456.py). Unfortunately environment variables in Houdini don't hook into
os.environ - so you still pretty much need a unix shell to set those as
persistent values for each session - or find a way to use Houdini
environment variables. For instance you can set $SHOT as a Houdini
environment variable, and then access it in python with a python method
return hou.hscript('echo $SHOT').rstrip()
You can then build other paths from that. This would allow you to do away
with a shell, and do things like change $SHOT, and all related paths in the
middle of a session. That would be cool. $JOB kind of does that I guess. Of
course any solution that involves Houdini variables has the risk of baking
of values into hipfiles. That can cause inadvertent problems. Also, $JOB
gets auto-set at times by Houdini which can be bad.
Houdini loves automation - and this stuff is good for that. Everyone loves
environment variables - but python provides alternatives these days...
> On 25 May 2010 18:16, Ammon Riley <ammon.riley at gmail.com> wrote:
>> On Tue, May 25, 2010 at 3:35 PM, <Sean.Lewkiw at cis-vancouver.com> wrote:
>> > I have to second these sentiments. Anytime you let the artist use their
>> > "creativity" in naming files and organizing directory structures,
>> I'm not sure he was arguing for allowing the artist control over those,
>> so much as if you make it simple, the artist won't have problems, and
>> won't need to deal with a "set shot" type of system. If that's true
>> (which experience has repeatedly shown wrong), it still ignores the fact
>> that even with a simple structure, automation can remove the need for
>> an artist to think about such things far more than "keeping it simple"
>> and one of the first steps towards automation, is being able to set/reset
>> and determine states: set shot.
>> > you can count on 10x the work downstream trying to figure out what
>> > the heck was going through their head during their career-long tequila
>> > break.
>> Sometimes it's not hard to figure it out. My favourite example of all
>> time was the file naming scheme where the number of "fuck"s in the
>> name increased with each saved version. Quite easy to tell what's
>> going through his head, especially when you correlate it with the
>> time-stamps marching from early evening to early morning. Now,
>> whether or not you could match that up with the rendered files
>> each one generated, is another question.
>> Sidefx-houdini-list mailing list
>> Sidefx-houdini-list at sidefx.com
> Andrew D Lyons | Digital Artist | http://www.tstex.com
Andrew D Lyons | Digital Artist | http://www.tstex.com
More information about the Sidefx-houdini-list