Hi,

There have been a few usage cases reported that exercised parts of the 
optimised reading code path which unfortunately revealed erroneous assumptions 
in the source.

We have a fix for handling these, which also extents to handling more general 
cases,  in a separate branch and will be releasing that once we have built up 
more usage cycles.

In the meantime, however, a v2.0.1 release will be available shortly, which 
disables the optimisation.



- Piotr
_______________________________________________
Openexr-user mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/openexr-user

Reply via email to