The main problem is that OpenEXR does not support icc profiles, and Hugin is
using the exr format as intermediate format for HDR output.
But I implemented a workaround: The metadata transfer is now also called for
HDR output (this was currently missing). Beside this new version you need to
add "-icc_profile" to the final argfile for exiftool in preferences, stitching
(2).
(You can copy the icc profile also with exiftool -tagsfromfile input.tif
-icc_profile out.tif.)
** Changed in: hugin
Status: Incomplete => Fix Committed
** Changed in: hugin
Milestone: None => 2018.2beta1
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1752135
Title:
HDR tiff and EXR files lack color space from input files
Status in Hugin:
Fix Committed
Bug description:
I am regularly creating HDR files (EXR and TIFF) from 16 bit source
files using the ProPhoto RGB color space. The resulting HDR outputs
generated by Hugin render with shifted colors. For EXR, sRGB is
wrongly assigned to the file. 32 bit TIFFs are instead untagged and do
not carry a color profile at all. As soon as I manually assign a
profile, colors are back to normal.
Hugin (or whatever process is used in the background), needs to assign
the input color space also to the generated output HDR files.
All of this happens with Hugin 2017.0.0.eac5e8cc546e on Windows 10,
using the standard built-in tools.
Btw, I have been searching for ages how to assign a color space manually to a
file. I ended up using:
magick "DSC_7847 - DSC_7856_hdr.tif" -profile proto.icc out.tiff
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1752135/+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
