Archives for posts with tag: renderman

Alembic is an open computer graphics interchange framework. Alembic distills complex, animated scenes into a non-procedural, application-independent set of baked geometric results. This ‘distillation’ of scenes into baked geometry is exactly analogous to the distillation of lighting and rendering scenes into rendered image data.

Alembic is focused on efficiently storing the computed results of complex procedural geometric constructions. It is very specifically NOT concerned with storing the complex dependency graph of procedural tools used to create the computed results. For example, Alembic will efficiently store the animated vertex positions and animated transforms that result from an arbitrarily complex animation and simulation process which could involve enveloping, corrective shapes, volume-preserving simulations, cloth and flesh simulations, and so on. Alembic will not attempt to store a representation of the network of computations (rigs, basically) which are required to produce the final, animated vertex positions and animated transforms.

The production ready version of Alembic 1.0 was announced at Siggraph 2011 and released on August 9th, 2011 by Lucasfilm and Sony Pictures Imageworks with support from major vendors including Autodesk, Side Effects Software, The Foundry, Luxology, Pixar’s Renderman and NVidia.

Home Page: http://alembic.io/
Project Page: http://code.google.com/p/alembic/
Language: C++, Python
Platform: Linux, OSX, Windows
License: New BSD License
Sponsor: Sony Pictures Imageworks, Lucasfilm

Particles are an important part of effects work, because they allow free-form information in 3D space. Unfortunately, there is no standard format for particles akin to Wavefront .obj. Most animation systems have their own proprietary particle formats. For example Maya uses the binary and ascii particle database formats .pdb and .pda file formats. Houdini uses the .geo and .bgeo geometry uber formats. Renderers typically have their own point cloud format such as RenderMan’s PTC format and Houdini’s .pc. All of these formats share a common theme. They allow particles to be iterated or indexed and associate a customizable set of attributes with them. The goal of Partio is to provide a unified interface akin to unified image libraries that makes it easier to load, save, and manipulate particle files.

Home Page: http://www.disneyanimation.com/technology/partio.html
Project Page: https://github.com/wdas/partio
Language: C++ Python
Platform: Linux, OSX, Windows
License: New BSD
Sponsor: Walt Disney Animation Studios

Jupiter Skin is a project container for several skin shaders developed by /*jupiter jazz*/.

At the moment this project features the following shaders:

  • Jupiter SGI Skin

Jupiter Spherical Gradient Illumination Skin is a 3Delight RenderMan shader that reads scanned RGB world space normal maps for 3 different wavelengths (red, green, blue), and a fourth normal map to be used in the specular term.

(more…)

Project Page: http://code.google.com/p/jupiterskin/
Language: Renderman Shading Language
Platform: Linux, OSX, Windows
License: New BSD License
Sponsor: Jupiter Jazz

JupiterFileCache (JFC) is a general purpose, multi location, multi process, thread safe file read & write cache library.

This is a C++ library that allows caching files in remote (network) locations onto the local client to speed up future accesses to these files. This reduces network traffic, but also, more importantly disk access, on the server. Modern network infrastructures are rarely the problem, but a server’s disks often don’t cope well when hundreds of clients read large files, often repeatedly, by querying small pieces of data, all at the same time.

It comes with a SWIG interface to be easily accessible through scripting languages (e.g Python) without the need to use a C++ compiler.

RSL shadeop implementation, modeled after the automatic network cache in DNA research’s 3Delight. It allows caching files like textures, point clouds or other heavy data, on a render farm client, automatically, by simply specifying the cache location with an environment variable, or in the RIB (with an option). In your shaders you can use the cacheFile() shadeop. It should work with any renderer that has an RSL shadeop API but was tested & used in production with Pixar’s PhotoRealistic RenderMan.

Project Page: http://code.google.com/p/jupiterfilecache
Language: C++ Python
Platform: Linux, OS X, Windows
License: Creative Commons 3.0 BY-SA
Sponsor: Jupiter Jazz

The RmanPtcSop project is a Houdini geometry operator (SOP) for loading and displaying RenderMan point clouds. It is based on the open source dnPtcViewerNode project from Double Negative Visual Effects.

Features of the rmanPtc SOP include:

  • Independent control for limiting the number of points loaded and displayed.
  • Geometry output for all point attributes in the cloud.
  • OpenGL display preview for attributes as point or disk primitives.
  • Ability to cull points based on a reference bounding box.

Home Page: http://danbethell.github.com/rmanptcsop/
Language: C++
Platform: Linux, Windows, OS X
License: New BSD License