On 4/7/16, Martin Vignali <martin.vign...@gmail.com> wrote: > Hello, > > in attach, a patch with some modifications in size/data window management, > in order to manage > negative datawindow/display window, and datawindow who can exceed display > window > > Size of the picture is now set from min and max value of the display window > (before the patch, xmin, ymin of the display window are ignored (and assume > to be 0)) > > With the previous patch (fix channel detection), official samples > ./scanline/Blobbies.exr > can now be correctly decode. > > > DataWindow bigger than display window is a feature of the openExr. > It can be use in some softwares, (for example to improve blur quality) > Following the official documentation, for display, we need to use the > display window only. > > > In this patch, xmin, xmax, ymin, ymax, are now int32_t instead of uint32_t, > because these values can be negative. (See officiel sample ./Displaywindow > http://download.savannah.nongnu.org/releases/openexr/openexr-images-1.7.0.tar.gz > ) > > Comments welcome
Crashes with: openexr-images-1.7.0/DisplayWindow/t03.exr Please use int and unsigned instead of int32_t and uint32_t. > > Martin > Jokyo Images > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
