2003.02.07 14:11 "Re: tiffset.exe instructions (was Re: tiffcp problems)", by Ray Pixley

Peter

What are you using tiffcp to do? Are you performing some additional conversions such as compression type?

Several things later on, but right now I want to use it to change the compression to G4, because HP's scanner software doesn't use that compression. That way I can work on getting rid of my shoeboxes of receipts and papers and keep them on smaller CDs. (I'd like to throw them out, but I learned long ago that the day or even years after they are gone, I end up needing a copy of them. I've looked and purchased some so-called "commercial" software that supposedly does that, but such software has too many of the wrong kind of bells and whistles and usually worthless support despite insisting on keeping the source code a "trade secret". The latter would be fine if they supported it properly. While their reality is that they do, my reality is they don't. Bigtime. Enough flaming.)

My app is pretty simple in that it just searches for the appropriate tag, checks the value, and then converts it if it isn't what was passed on the commandline.

That's what I was looking for, and was trying to do with VBA. But when I tried, I got a lot of "this is not a tif file" messages. Hence, my posting.

I am curious if all your files are the same endian.

I'm familiar with the endian "feature". Some of my files are little, some are big and I have some VBA code that tells me which are which. So far, there are no indications that this alone could be the problem. But I still have some combinations to try.

I'm just trying to think of what might be causing the problem on my end.

I don't think its your end.

BTW, if you simply need to change the photometric interpretation, then you don't need tiffcp.

I also plan to use tiffcp to concatenate some files later on. But one thing at a time.

PS - Have you tried taking a problem file and just running it only through my tweaker program? You should then perform the same experiment and just use tiffcp. See if you can isolate the odd behavior to either of the two apps separately.

That's essentially what I'm doing.

Thanks

Ray