>From the OpenEXR documentation >(https://www.openexr.com/documentation/ReadingAndWritingImageFiles.pdf): "An OpenEXR image may not have pixel data for all the pixels in the display window, or it may have pixel data beyond the boundaries of the display window. The region for which pixel data are available is defined by a second axis-parallel rectangle in pixel space, the data window." Hugin's notification is like the example on page 7 (top figure) in the linked documentation. So I think that the Hugins current notification is right and conforms the spec.
** 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