The spec states clearly that the data window describes the area which has data, which is how Hugin treats it. So switching data and display window as you propose would clearly violate the spec. (Or Hugin would required to save a lot of black pixels with no information but increased file size). The behaviour of OpenEXR data window/display window is analogous how Hugin is using cropped TIFF images. Luminance HDR displays such a OpenEXR without problems (without black border). If darktable shows only a black border on the left and top then it ignores the display window and is using only the offset of the data window. Otherwise it should also show a black border on the right and bottom.
** Changed in: hugin Status: New => Invalid -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1865333 Title: dataWindow and displayWindow look swapped in generated OpenEXR files Status in Hugin: Invalid Bug description: When exporting a high dynamic range image with a crop as an OpenEXR file, the cropped dimensions end up as the dataWindow and the canvas size as the displayWindow, which seems like it’s the wrong way around. When imported back into darktable, the image has a black border on the left and at the top. Export settings: https://i.imgur.com/TFmA6zP.png (also attached) exrheader output: dataWindow (type box2i): (51 78) - (5292 3991) displayWindow (type box2i): (0 0) - (5345 4070) This happens on intermediary remapped files too, not just the final merged output. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1865333/+subscriptions _______________________________________________ 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