hugin-devs team mailing list archive

[tmodes <1865333@xxxxxxxxxxxxxxxxxx>]

> I believe that darktable is correct according to “Testing Other OpenEXR Viewers” 
I think it is only correct when using darktable as viewer only. But as soon as you process the image, the data outside of the display should not be disregarded. Maybe Darktable should provide an option to use display or data window (as exrdisplay).

The current behavior of Hugin is consistent for TIFF and EXR. If we
would change it for EXR as you propose this would be different for both
file formats which I don't like because then all place where images are
loaded or saved would be checked and modified for this 2 different ways
of storing the information.

-- 
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