hugin-devs team mailing list archive

[rew <679858@xxxxxxxxxxxxxxxxxx>]

I think the concept should be that

the 0....65535 range and 0..255 range are considered to be 0..1 ranges.
That's the only way to get consistent results.

(otherwise a float file that started out as bytes might have a 0...255
range. (this is so stupid we already don't do it). )


** Changed in: hugin
   Importance: Undecided => Wishlist

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

** Tags added: hdr nona

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679858

Title:
  nona should scale non-float HDR output files

Status in Hugin - Panorama Tools GUI:
  Triaged

Bug description:
  If nona is used with the HDR option (-r hdr) and a pixel type other than FLOAT (e.g. UINT16), the output is still in the range 0..1 rather than 0..65535.    This particular combination of options is useful in aligning 16-bit linear files without converting to EXR or HDR.   

Note that this can be worked around by setting the EV of the input images to 16.