The viewer is built on top of OpenEXR and provides a simple user interface for efficient navigation. The EXR files (JPEGs and PNGs are supported too) are specified using a JSON string and loaded on demand, asynchronously and cached for best user experience. The exr file extension (Extended Dynamic Range image file format) is associated with the OpenEXR image file format. OpenEXR was developed in 1999 by Industrial Light & Magic that is the leader in creating of movie digital tricks and is the open source high dynamic-range (HDR) graphic file format. A simple viewer for OpenEXR files with detailed metadata probing. You can display various types of layers, automatically combines RGB, Luminance-Chroma and Y layers. Launching Visual Studio Code. Your codespace will open once ready. There was a problem preparing your codespace, please try again.

Openexr Viewer Linux
Openexr Viewer Windows
Openexr Online Viewer
Openexr Viewer
Openexr Viewer Ubuntu
Apt Install Openexr-viewer

EXR header values¶

This module represents EXR headers as regular Python dictionaries.Each header entries have a name - a string - and a valuethat may be one of several types, defined by the OpenEXR standard.

The Python module translates these types to Python types when reading OpenEXR headers,and does the reverse translation when writing headers.

The module Imath provides many of the classes for attribute types.

Values in the dictionary may be:

string

float

int

list of strings

New in version 1.2.

This attribute type is used in multiView images, as described in http://www.openexr.com/MultiViewOpenEXR.pdf

dict

A dict represents the image’s channels. In the dict, the keys are the channel names, and the values are of class Imath.Channel:

A preview image, specified by height, width, and a string of length 4*width*height. The pixels are in RGBA order:

or to use a PIL image as an EXR preview:

Imath.Chromaticities

Specifies (x, y) chromaticities for red, green, blue and white components:

OpenEXR provides the specification and reference implementation ofthe EXR file format, the professional-grade image storage format ofthe motion picture industry. The purpose of format is to accuratelyand efficiently represent high-dynamic-range scene-linear image dataand associated metadata, with strong support for multi-part,multi-channel use cases. The library is widely used in hostapplication software where accuracy is critical, such asphotorealistic rendering, texture access, image compositing, deepcompositing, and DI.

OpenEXR a project of the Academy Software Foundation and is part ofthe VFX ReferencePlatform. OpenEXR was originally developed by Industrial Light &Magic (ILM) and first released in 2003. Weta Digital, Walt DisneyAnimation Studios, Sony Pictures Imageworks, Pixar Animation Studios,DreamWorks, and other studios, companies, and individuals have madesignificant contributions to the code base.

Mission Statement

The goal of the OpenEXR project is to keep the format reliable andmodern and to maintain its place as the preferred image format forentertainment content creation. Major revisions are infrequent, andnew features will be carefully weighed against increased complexity.

The principal priorities of the project are:

Robustness, reliability, security
Backwards compatibility, data longevity
Performance - read/write/compression/decompression time
Simplicity, ease of use, maintainability
Wide adoption, multi-platform support - Linux, Windows, macOS, and others

OpenEXR is intended solely for 2D data. It is not appropriate forstorage of volumetric data, cached or lit 3D scenes, or more complex3D data such as light fields.

OpenEXR Features

OpenEXR's features include:

High dynamic range and color precision.
Support for 16-bit floating-point, 32-bit floating-point, and 32-bit integer pixels.
Multiple image compression algorithms, both lossless and lossy. Some of the included codecs can achieve 2:1 lossless compression ratios on images with film grain. The lossy codecs have been tuned for visual quality and decoding performance.
Extensibility. New compression codecs and image types can easily be added by extending the C++ classes included in the OpenEXR software distribution. New image attributes (strings, vectors, integers, etc.) can be added to OpenEXR image headers without affecting backward compatibility with existing OpenEXR applications.
Support for stereoscopic image workflows and a generalization to multi-views.
Flexible support for deep data: pixels can store a variable-length list of samples and, thus, it is possible to store multiple values at different depths for each pixel. Hard surfaces and volumetric data representations are accommodated.
Multipart: ability to encode separate, but related, images in one file. This allows for access to individual parts without the need to read other parts in the file.
Versioning: OpenEXR source allows for user configurable C++ namespaces to provide protection when using multiple versions of the library in the same process space.

OpenEXR and Imath Version 3

With the release of OpenEXR 3, the Imath library formerly distributedvia the IlmBase component of OpenEXR is now an independent librarydependency, available for download from https:://github.com/AcademySoftwareFoundation/Imath.You can choose to build OpenEXR against an external installation ofImath, or the default CMake configuration will download and build itautomatically during the OpenEXR build process. Note that the half16-bit floating point data type is included in Imath.

See the porting guidefor details about differences from previous releases and how toaddress them. Also refer to the porting guide for details aboutchanges to Imath.

The OpenEXR software distribution is licensed under the modifiedBSD license, available here.

Announcements

Aug 2, 2021 - OpenEXR v3.1.1

Patch release that fixes build failures on various systems (ARM64 macOS, FreeBSD), introduces CMake CMAKE_CROSSCOMPILING_EMULATOR support, and fixes a few other minor issues.

See the release notes for more details

Download OpenEXR v3.1.1 from https://github.com/AcademySoftwareFoundation/OpenEXR/releases/tag/v3.1.1.

July 31, 2021 - Imath v3.1.2

Patch release that fixes a potential Windows build issue

Download Imath v3.1.2 from https://github.com/AcademySoftwareFoundation/Imath/releases/tag/v3.1.2.

July 22, 2021 - OpenEXR v3.1.0

The 3.1 release of OpenEXR introduces a new library, OpenEXRCore,which is the result of a significant re-thinking of how OpenEXRmanages file I/O and provides access to image data. It begins toaddress long-standing scalability issues with multithreaded imagereading and writing.

The OpenEXRCore library provides thread-safe, non-blocking access tofiles, which was not possible with the current API, where theframebuffer management is separate from read requests. It is writtenentirely in C and provides a new C-language API alongside the existingC++ API. This new low-level API allows applications to do customunpacking of EXR data, such as on the GPU, while still benefiting fromefficient I/O, file validation, and other semantics. It providesefficient direct access to EXR files in texturing applications. This Clibrary also introduces an easier path to implementing OpenEXRbindings in other languages, such as Rust.

The 3.1 release represents a technology preview for upcomingreleases. The initial release is incremental; the existing API andunderlying behavior has not changed. The new API is available now forperformance validation testing, and then in future OpenEXR releases,the C++ API will migrate to use the new core in stages. It is not theintention to entirely deprecate the C++ API, nor must all applicationsre-implement EXR I/O in terms of the C library. The C API does not,and will not, provide the rich set of utility classes that exist inthe C++ layer. The 3.1 release of the OpenEXRCore library simplyoffers new functionality for specialty applications seeking thehighest possible performance. In the future, the ABI will evolve, butthe API will remain consistent, or only have additions.

Technical Design

The OpenEXRCore API introduces a ``context`` object to manage fileI/O. The context provides customization for I/O, memory allocation,and error handling. This makes it possible to use a decode and/orencode pipeline to customize how the chunk

Openexr Viewer