Also agree that the TIFF workaround does not work in the latest version of hugin on OpenSuSE 11.4
-- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678694 Title: EXR files quietly clipped (black rectangles in output) Status in Hugin - Panorama Tools GUI: Confirmed Bug description: The EXR file format has a maximum encoding value of 65504. The Hugin data flow maintains the absolute exposure through use of the Ev field which effectively scales pixel values. When using Hugin/Nona on an HDR series that includes very bright elements (such as a very bright sky with a very short exposure), some pixels end up with values above 65504. When these are written out by Nona, those pixels are written as NaN's in the EXR output file. If enblend is then used, the problem is further exacerbated. A single NaN pixel results in NaN for entire rectangle of enblend's pyramids. The end result are large black rectangles in the output file. If output is changed to TIFF, then everything works fine. Nona should warn when clipping occurs and then output the maximum possible value rather than a NaN. I assume this is the OpenEXR library itself and probably affects other applications. In fact, if a TIFF generated as above is opened in PhotoShop, it looks fine, but if it is resaved as EXR, the same NaN pixels are created. _______________________________________________ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
