corrupt tiff-file

[sinus]

For some situations I have since years the same procedure.
I take pictures with nef, then open them in Photoshop (CS6), and store them as tifs.
Then they were imported into IMatch and propagated.

It looks then like attachement 1. Fine.
Then I open the tif in PS to work on it.
And now I have something, what I have never seen before in PS, see attachement 2.

This is the first time, what I have indexed and worked with new images in IMatch 2025.

The curious thing is, some of the images, what are edited in the same way, I can normally open in PS, but mostly not.

Of course I will be able to solve this, because I have to deliver them, but I wonder.
What makes sense to you, Mario? Send you such a file or what makes sense, that help find out, what is wrong or I did wrong.

From the log (not debug) maybe this line is interesting:
02.20 12:58:02+ 1469 [1CD4] 01  W> ETWARN:Warning: IFD0 BitsPerSample should have 3 values - D:/Archiv-SINUS-AKTUELL/00_timeline-aktuell/2022-2025/25_timeline-2025/1_archiv-bild-2025/b-2025-02-Feb/20250218-0951-484607-s-coo-ayanthy_m.nef
  'V:\develop\IMatch5\src\IMEngine\PTETWrapper.cpp(3796)'

*******
update: after propagation, all is ok, then I click on the pencil to write, all is ok NOW.
But I can remember the last time, I had to click on the pencil two or three time, before it disappears.
Means, has something to my progataion. I guess, I have to check them.

But for the moment, all is ok and I can work further, HENCE NO HURRY is needed. :-)
 

[Mario]

You let IMatch propagate metadata from the NEF to TIFF files, correct?

Ps 6 is a decade old now. Maybe this is part of the problem? Not sure, I don't have Photoshop 6 around.

For a test I've opened a D-300 NEF and a Z7 NEF and saved them as 16-bit TIFF with LZW compression in IBM PC byte order in Photoshop 26.3 (most recent version).

I have a version rule NEF->TIF active so the TIFF files become versions automatically.
The rule propagates rating, label, collections and a huge set of XMP and all IPTC XMP tags.

I add metadata to the images (rating, label, keywords, headline, copyright info, legal, title etc.) and write back the masters. The data is propagated to the TIFF files. I verify that the data is there.

I drop the TIFF files onto Photoshop and it opens them without any problem.

The effect you are seeing can have many reasons. A specific NEF / TIFF combination. Ps 6 writing an old or maybe even damaged TIFF file in this particular version. Maybe the TIFF settings you use?

I would need 
+ an original NEF 
+ a TIFF you have exported for that NEF in Ps6 but not modified in any other way to conduct some tests
+ one of the broken TIFF files
+ a detailed list of the tags you propagate (I need to rebuild your rule here)
+ the precise TIFF settings you use in Ps6 (bit depth, color handling, compression scheme)

You know my email address. Include a link back to this topic so I know what's what.

[sinus]

Thanks, Mario, for the superquick answer.

Yes, nefs to tifs.
CS6 is of course old, but I work the same procedure sind years with IMatch and PS, do always the same (most are actions in PS).
Never had this, and this is the first time, I work with new images with IMatch 2025.

But I will check it more carefully, then report, what is the problem was or if I cannot find it out, I would send you the things, what you have asked for. 
I guess, it has something to to with propatation-rules, maybe with gps, but I will check it all first deeper.

Finally, before you have the work, I can look deeper into my problem. 

[Mario]

Be careful and don't propagate EXIF between different file formats, or GPS (which is also native metadata). After Ps6 was released, several new TIFF flavors were standardized and who knows...

I have not seen this effect before, no other user reported this effect, IMatch has many customers in libraries and they all archive in TIF.

Maybe it's a bug in ExifTool or the way IMatch propagates the data. I need to be able to reproduce this before I can tell more.