You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
convert() (and consequently pilconvert.py) seems to clip 16 bit grayscale tiffs when they convert to jpeg. This seems to persist no matter what order of conversions is applied. The two attached images were made with pilconvert.py -g and -r. Unfortunately GitHub won't let me upload a Tiff, but I'm happy to send the original via email if that would help.
The text was updated successfully, but these errors were encountered:
I think conversions of 16bit->8bit tend to be done by clipping everything above 255. It might work better to use the ImageMath module to map the 16bit values to 0-255, and then convert to L mode.
(a linear map would be easy, but other mappings might perserve more information)
Huh, I've never encountered that behavior before. The four other toolkits we use (IrfanView, libtiff, Aware, and GraphicsMagic) all manage this conversion in a way that results in a more-or-less recognizable facsimile of the original.
We wound up, as a temporary hack, simply shelling out to tiff2rgba prior to saving as a jpeg, (e.g. check_call(["tiff2rgba", file, file])).
convert() (and consequently pilconvert.py) seems to clip 16 bit grayscale tiffs when they convert to jpeg. This seems to persist no matter what order of conversions is applied. The two attached images were made with pilconvert.py -g and -r. Unfortunately GitHub won't let me upload a Tiff, but I'm happy to send the original via email if that would help.
The text was updated successfully, but these errors were encountered: