The new API is available now for performance validation testing, and then in future OpenEXR releases, the C++ API will migrate to use the new core in stages. The initial release is incremental the existing API and underlying behavior has not changed. The 3.1 release represents a technology preview for upcoming releases. This C library also introduces an easier path to implementing OpenEXR bindings in other languages, such as Rust. It provides efficient direct access to EXR files in texturing applications. This new low-level API allows applications to do custom unpacking of EXR data, such as on the GPU, while still benefiting from efficient I/O, file validation, and other semantics. ![]() It is written entirely in C and provides a new C-language API alongside the existing C++ API. The OpenEXRCore library provides thread-safe, non-blocking access to files, which was not possible with the current API, where the framebuffer management is separate from read requests. It begins to address long-standing scalability issues with multithreaded image reading and writing. The 3.1 release of OpenEXR introduces a new library, OpenEXRCore, which is the result of a significant re-thinking of how OpenEXR manages file I/O and provides access to image data. Minor release with significant new features:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |