Page 1 of 1

possible bug .hdr format writer IM 6.7.1.10 Q16 HDRI

Posted: 2011-08-24T19:52:50-07:00
by fmw42
IM 6.7.1-10 Q16 HDRI Mac OSX Tiger.

I am not able to copy a .hdr file without a color change.

Anthony and I both seem to agree there appears to be some issue with the writing of .hdr.

I am not sure if it has anything to do with the fact that IM formats support:

HDR* HDR rw+ Radiance RGBE image format

but the images I am working with are in Radiance RGBE image format, but colorspace XYZ.

Any way, this causes a change in the verbose info statistics for min,max,mean,std

convert doll.hdr doll2.hdr

but this works fine

convert doll.hdr doll2.exr

The doll.hdr image is available at http://www.mit.edu/~yzli/hdr_companding.htm

Re: possible bug .hdr format writer IM 6.7.1.10 Q16 HDRI

Posted: 2011-08-25T09:51:36-07:00
by fmw42
Further tests, show color changes when converting hdr to pfm (and tiff with or without -define quantum:format=floating-point), but not to miff or mpc or exr. So it seems something more complex is happending here. I am surprised about the color change going to pfm.

Re: possible bug .hdr format writer IM 6.7.1.10 Q16 HDRI

Posted: 2011-08-25T11:54:43-07:00
by magick
We can reproduce the problem you reported. We'll have a patch in ImageMagick 6.7.2-0 Beta by sometime tomorrow. Thanks.

Re: possible bug .hdr format writer IM 6.7.1.10 Q16 HDRI

Posted: 2011-08-25T14:10:16-07:00
by fmw42
magick wrote:We can reproduce the problem you reported. We'll have a patch in ImageMagick 6.7.2-0 Beta by sometime tomorrow. Thanks.
No great urgency. I would just like to get this cleared up (as I am working on some HDR tonemapping and would like to be sure .hdr files work) and glad you could confirm.

Re: possible bug .hdr format writer IM 6.7.1.10 Q16 HDRI

Posted: 2011-08-26T20:33:33-07:00
by fmw42
I have tested this now under IM 6.7.2.0 Q16 HDRI and the problem appears to be fixed. It also seems to make a big positive difference in my tonemapping scripts.

Thanks.

Fred


P.S. The changelog entry seems to indicate it was fixed at 6.7.1.10, but I think that is an error and it should be marked as fixed in 6.7.2.0