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
{{ message }}
Repository navigation
Simple conversion of Tiff file to PNG or JPG generates a strange result, even, at certain times, it is in 3D perspective #2679
The expected decoded image Image_021.tiff should look like this:
It actually looks like this from the main branch:
The tiffinfo is:
TIFFReadDirectory: Warning, Unknown field with tag 347 (0x15b) encountered.
Image_021.tif: JPEG compression support is not configured.
=== TIFF directory 0 ===
TIFF Directory at offset 0x8 (8)
Image Width: 1666 Image Length: 2359
Resolution: 200, 200 pixels/inch
Bits/Sample: 8
Compression Scheme: JPEG
Photometric Interpretation: YCbCr
YCbCr Subsampling: 2, 2
Samples/Pixel: 3
Planar Configuration: single image plane
Reference Black/White:
0: 0 255
1: 128 255
2: 128 255
So this is a jpeg compressed tiff image. The image decodes correctly, if we set the ycbcrSubSampling to 1, 1 instead of 2, 2, since this is already handled by the jpeg decoding part.
I am not 100% sure if we always can assume ycbcrSubSampling to 1, 1 with tiff compressed jpeg's. @JimBobSquarePants any thoughts?
I had another dig through our Tiff code (I really do not enjoy how complicated it is to follow) and it appears to me that our jpeg scan decoder is already handling the deinterleaving so we can treat the subsampling as [1, 1] when using the jpeg decoder.
I had another dig through our Tiff code (I really do not enjoy how complicated it is to follow) and it appears to me that our jpeg scan decoder is already handling the deinterleaving so we can treat the subsampling as [1, 1] when using the jpeg decoder.
Ok, thanks for confirming. I think what makes it so complicated is the myriads of possible combinations of compressions, pixelformats and colorspaces. When ever I think now we finally covered all possible combinations someone comes up with a new tiff variant.
I will try to make a fix for that. @yuridiniz Is it ok, if we use your testimage in a unit-test?
Activity
brianpopow commentedon Mar 6, 2024
The expected decoded image

Image_021.tiffshould look like this:It actually looks like this from the main branch:

The tiffinfo is:
So this is a jpeg compressed tiff image. The image decodes correctly, if we set the ycbcrSubSampling to 1, 1 instead of 2, 2, since this is already handled by the jpeg decoding part.
I am not 100% sure if we always can assume ycbcrSubSampling to 1, 1 with tiff compressed jpeg's. @JimBobSquarePants any thoughts?
JimBobSquarePants commentedon Mar 6, 2024
Does the tag specifically state the subsampling is 2, 2?
https://www.awaresystems.be/imaging/tiff/tifftags/ycbcrsubsampling.html
brianpopow commentedon Mar 7, 2024
Yes YCbCrSubSampling is [2, 2] here in the example image
Image_021.tiffas can be seen in the tiffinfo section above.JimBobSquarePants commentedon Mar 11, 2024
I had another dig through our Tiff code (I really do not enjoy how complicated it is to follow) and it appears to me that our jpeg scan decoder is already handling the deinterleaving so we can treat the subsampling as [1, 1] when using the jpeg decoder.
brianpopow commentedon Mar 11, 2024
Ok, thanks for confirming. I think what makes it so complicated is the myriads of possible combinations of compressions, pixelformats and colorspaces. When ever I think now we finally covered all possible combinations someone comes up with a new tiff variant.
I will try to make a fix for that. @yuridiniz Is it ok, if we use your testimage in a unit-test?
shapeh commentedon Apr 16, 2024
TIFF stands for Thousands of Incompatible File Formats!
Not helpful but couldn't help myself ;)
Always set YcbcrSubSampling to 1:1 for TiffCompression.Jpeg, fixes is…
brianpopow commentedon Aug 24, 2024
Since #2789 was merged, I will close this now as completed
Backport #2679 for v3. See #2994