However not for 32 bit files, but judging from your command
line above I assume you meant 16 bit, or both gmic and gimp
are broken, who knows :)
Yeah, my g'mic example had a semantic mistake, sorry: it should have
read something like:
gmic 32bit_float_input_with_range_to_65535.tif -/ 65535
On Thu, 2017-04-27 at 23:07 -0700, Casey Connor wrote:
> ...and a final follow-up, just so people don't need to spend any time
> on
> this: changing the range with g'mic makes the files work properly in
> GIMP:
>
> gmic 16bit_input.tif -/ 65535 -o 32bit_float_output.tif
>
> (that scales the
...and a final follow-up, just so people don't need to spend any time on
this: changing the range with g'mic makes the files work properly in GIMP:
gmic 16bit_input.tif -/ 65535 -o 32bit_float_output.tif
(that scales the output to the [0,1] range.)
So that seems like the logical way to handle
Just a follow-up in case anyone is interested: apparently one issue is
that G'MIC outputs 32bit float tiffs in the range 0-65536, which might
explain why they are all-white (and sometimes there are some black
pixels). (This according to folks on the g'mic forum. As to why
sometimes changing to
Hello -- I've been posting around trying to help get to the bottom of
various problems with tiff formats in higher bit depths -- perhaps you
saw my posts on gimp-user-list. I'm told that the .tif format is a bit
of a mess, but in case it's useful, I thought I'd post here (apologies
for the
