hugin-devs team mailing list archive

[Sami Boukortt <1865333@xxxxxxxxxxxxxxxxxx>]

> The spec states clearly that the data window describes the area which
has data, which is how Hugin treats it.

The point is that it’s not clear to me that this is how Hugin treats it.
To me, it seems obvious that the crop size is supposed to indicate what
should be visible in the final image. Why, then, does that end up as the
*data* window and not the display window? And why does the canvas size,
which is always a superset of the crop (the GUI enforces it), ends up as
the display window? That means that there will pretty much always be a
black border, regardless of how completely darktable displays it.

> Luminance HDR displays such a OpenEXR without problems (without black
border).

I don’t think that Luminance HDR should be used as a reference given
that it does not implement support for a display window smaller than the
data window. The only use of the display window is to check whether to
throw "No support for OpenEXR files DataWindow greater than
DisplayWindow" (src/Libpfs/io/exrreader.cpp).

** Changed in: hugin
       Status: Invalid => New

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

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