[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Openexr-announce] v2.0.0.0 (GM) release announcement

From: Piotr Stanczyk
Subject: [Openexr-announce] v2.0.0.0 (GM) release announcement
Date: Tue, 9 Apr 2013 21:10:34 +0000

Hi All,

Tuesday, April 9th, 2013

OpenEXR v2.0.0 has been released and is available for download. 

The release includes a number of new features that align with the major version number increase. Amongst the major improvements are:

  1. Deep Data support - Pixels can now store a variable-length list of samples. The main rationale behind deep images is to enable the storage of multiple values at different depths for each pixel. OpenEXR 2.0 supports both hard-surface and volumetric representations for Deep Compositing workflows.
  2. Multi-part Image Files - With OpenEXR 2.0, files can now contain a number of separate, but related, data parts in one file. Access to any part is independent of the others, pixels from parts that are not required in the current operation don't need to be accessed, resulting in quicker read times when accessing only a subset of channels. The multipart interface also incorporates support for Stereo images where views are stored in separate parts. This makes stereo OpenEXR 2.0 files significantly faster to work with than the previous multiview support in OpenEXR.
  3. Optimized pixel reading - decoding RGB(A) scanline images has been accelerated on SSE processors providing a significant speedup when reading both old and new format images, including multipart and multiview files.
  4. Namespacing - The library introduces versioned namespaces to avoid conflicts between packages compiled with different versions of the library.

Further information regarding the release, as well as tarball downloads, please visit:

For the developer community: the source code has been tagged as "v2.0.0.GM" and the master branch is now pointing to this.

Many thanks for your continued support in making OpenEXR a success.

Piotr Stanczyk

reply via email to

[Prev in Thread] Current Thread [Next in Thread]