[Sidefx-houdini-list] compressed rib?

Jeff Higgins jeff at coredp.com
Thu Mar 16 10:05:25 EST 2006


Rob Pieké wrote:

>> If you're only worried about disk space you could wrap your rib 
>> output in
>> a call to catrib, I think it has a -binary option, but you might get
>> subtly different results.
>
>
> And '-gzip'. Just make sure your RIB is "clean". We ran into an issue 
> where certain RIB files went through the 'render' command without any 
> problems but would cause 'catrib' to choke. The culprit, in the end, 
> was a shader OTL that wasn't declaring the type of each parameter (so 
> you'd end up with something like: Surface "mySurface" "myParam" [1] 
> ... and then catrib would die not knowing what kind of parameter 
> 'myParam' was).
>
> Cheers!
> _______________________________________________
> Sidefx-houdini-list mailing list
> Sidefx-houdini-list at sidefx.com
> https://lists.sidefx.com:443/mailman/listinfo/sidefx-houdini-list
>
>
if you're talking about writing it using the hdk.

i've had success generating binary ribs which are more efficient to 
render and also give you around 50% less space.  I think its houdini's 
zlib library which is the culprit for making it a pain in the arse to 
gzip, because it doesn't play nicely with prman's libzip.

not to sound like a sesi salesman, but it should be fixed in v9.

if you're just talking about generating a rib from your scene then on 
your renderman rop, instead of using generate script, you using *catrib 
-binary -gzip > foo.rib *instead of *render* should work.  this will 
save you the overhead of generating ascii and then gzipping it afterwards.

-- 
.....................................................................
jeff higgins                                   email: jeff at coredp.com
c.o.r.e. digital pictures                       http://www.coredp.com
.....................................................................




More information about the Sidefx-houdini-list mailing list