[Sidefx-houdini-list] Backslash treated as an escape character

Simon Barrick simon at primalpictures.com
Wed Jan 30 10:27:18 EST 2008

If its in an asset can't you just add a little pre-render script to
create the directory if it doesn't exist already..

-----Original Message-----
From: sidefx-houdini-list-bounces at sidefx.com
[mailto:sidefx-houdini-list-bounces at sidefx.com] On Behalf Of Sean Lewkiw
Sent: 30 January 2008 15:21
To: sidefx-houdini-list at sidefx.com
Subject: Re: [Sidefx-houdini-list] Backslash treated as an escape

All good points.  Our HDA does what it sounds like yours does, and the 
users can't enter their own file paths and names.  So I maintain that I 
can be trusted to make sure that the path to which I want to render my 
images is correct, and that Houdini, knowing what this path is can 
simply create it, and that's one less bit of code I have to maintain.  
It's not like Houdini doesn't create other dirs if it needs them, 
($HOME/houdini, etc). 

As an aside, Houdini used to fail with the cryptic warning "Unable to 
create script or pipe" when a target dir didn't exist.  Now it outputs, 
"No such file or directory" to the shell which is a big improvement, 
although the red flag just reports "Command Exit Code 1". 


John Coldrick wrote:
> On Wednesday 30 January 2008 08:41, Sean Lewkiw wrote:
>> I was assuming that Francois wants to automate the process of 
>> creating destination render dirs.  Why would it put them in $HOME/.my

>> etc?
> 	My point was that if you screw up, it will create your screwup.
> you
> formalize the process, as in a script, there's far less liklihood that
> will be a screwup.  I'd rather have the script or houdini slap me in
the face 
> for being an idiot than have houdini blindly create anything I enter
> possibly have missing files that I need to hunt down.   For example,
> rendering script, as part of the process, will check for the existence
> output dirs and create them, all using logic like(python sucks for
> quoting! ;) ):
> if not (os.path.isdir(os.path.join( os.path.split(options.PIC_DIR) [0]

> ,'BKUPS'))):
> 	try:
> 		os.makedirs(os.path.join(
> 	except:
> 		print "Seemed to have some troubles creating",
> os.path.split(options.PIC_DIR)[0] ,'BKUPS'), "- check your
> 		sys.exit()
> 	where options.PIC_DIR was nicely assembled using the user's
> 	options.PIC_DIR =
> 	Going through all this is IMHO infinitely superior to falling
back on
> something the user manually enters over and over again for each job.
I mean, 
> I hear you, sure it could be an option, it's just something you could
> off, but it really is a non-standard approach in applications.  It
forces a 
> certain degree of responsibility - you have to make the output dir.
It falls 
> under the category of the hated 'smart' software model.
> 	Cheers,
> 	J.C.


Sean Lewkiw

CIS London
130 Shaftesbury Avenue
London W1D 5EU

+44 (0) 207.031.1138 (P) (Direct)
+44 (0) 207.031.1136 (F)
+44 (0) 795.606.7245 (M)

Sidefx-houdini-list mailing list
Sidefx-houdini-list at sidefx.com

This communication is from Primal Pictures Ltd., a company registered in England and Wales with registration No. 02622298 and registered office: 4th Floor, Tennyson House, 159-165 Great Portland Street, London, W1W 5PA, UK. VAT registration No. 648874577.

This e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you have received it in error, please contact the sender immediately by return e-mail or by telephoning +44(0)20 7637 1010. Please then delete the e-mail and do not disclose its contents to any person.
This email has been scanned for Primal Pictures by the MessageLabs Email Security System.

More information about the Sidefx-houdini-list mailing list