hugin-devs team mailing list archive
-
hugin-devs team
-
Mailing list archive
-
Message #07477
[Bug 1865333] Re: dataWindow and displayWindow look swapped in generated OpenEXR files
Hugin calculates and saves only data inside the crop area. This is
stored in OpenEXR as data window as written in the spec.
So there are different ways to interpret the window sizes:
Luminance HDR, Gimp, Picture, Hugin using the data window size.
And darktable shows the display window size...
So I don't see darktable as reference either...
** Changed in: hugin
Status: New => Opinion
--
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:
Opinion
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
References