Kwisatz
07-08-2008, 02:08 PM
Is there a way to read AND comp a multi-channel (say 50 channels) exr file rendered from another program like RenderMan for instance as it is now? I read the following from the Blender site so it looks like it might be natively available in the future. I'm not expecting something like Nuke performance, but maybe a Shake like approach or even an After Effects type solution.
BTW, the following is mis-leading as I think once you leave the "Blender" world you're on your own. In other words, you can/will be able to only comp Blender generated exrs.
Multi-layer, Multi-pass, tile-based files
An OpenEXR file can hold unlimited layers and passes, stored hierarchically. This feature now is in use for the "Save Buffers" render option. This option doesn't allocate the entire final Render Result before render (which can have many layers and passes), but saves for each tile the intermediate result to a single OpenEXR file in the default Blender 'temp' directory.
When rendering is finished, after all render data has been freed, this then is read back entirely in memory.
In a next release we will make this format available as a standard render output option too, allowing to re-use it in the Compositor for example, with access to all Layers and Passes like the current RenderLayer Node. (See Render Pipeline (http://www.blender.org/development/release-logs/blender-242/render-pipeline/) too.)
BTW, the following is mis-leading as I think once you leave the "Blender" world you're on your own. In other words, you can/will be able to only comp Blender generated exrs.
Multi-layer, Multi-pass, tile-based files
An OpenEXR file can hold unlimited layers and passes, stored hierarchically. This feature now is in use for the "Save Buffers" render option. This option doesn't allocate the entire final Render Result before render (which can have many layers and passes), but saves for each tile the intermediate result to a single OpenEXR file in the default Blender 'temp' directory.
When rendering is finished, after all render data has been freed, this then is read back entirely in memory.
In a next release we will make this format available as a standard render output option too, allowing to re-use it in the Compositor for example, with access to all Layers and Passes like the current RenderLayer Node. (See Render Pipeline (http://www.blender.org/development/release-logs/blender-242/render-pipeline/) too.)