AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2020.08.16 02:02 "[Tiff] Problems with Photoshop when a file is written is strips", by David C. Partridge
2020.08.16 13:01 "Re: [Tiff] Problems with Photoshop when a file is written is strips", by Kemp Watson
2020.08.16 13:20 "Re: [Tiff] Problems with Photoshop when a file is written is strips", by Bob Friesenhahn
2020.08.16 15:16 "Re: [Tiff] Problems with Photoshop when a file is written is strips", by David C. Partridge
2020.08.17 10:13 "Re: [Tiff] Problems with Photoshop when a file is written is strips", by David C. Partridge
2020.08.17 10:30 "Re: [Tiff] Problems with Photoshop when a file is written is strips", by David C. Partridge
2020.09.08 10:52 "Re: [Tiff] Problems with Photoshop when a file is written is strips", by Ive
[...]

2020.09.08 10:52 "Re: [Tiff] Problems with Photoshop when a file is written is strips", by Ive

When opened in Photoshop CS6 through to CC 2020 it displays fine and I can convert to 16bit and save it and PS will reload it OK, but all other applications choke on the 16 bit file.

I can open the 32 bit file OK in GIMP and IrfanView, so I don't think that I've messed up - I think it's a PS bug.

Have you seen this before?

Yes. It is a PS bug that even exists since CS5.

What actually happens is this: If you open any floating point TIFF file in PS and then save it as integer format TIFF - PS will write a wrong floating point predictor field to the TIFF. I once (at times of PS5) wrote bug report about this issue to Adobe and even got a response that they will fix it, but obviously they never did.

-Ive