AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2008.03.29 04:18 "[Tiff] TIFFReadRawStrip buffer data type", by James Sumners
2008.03.29 06:05 "Re: [Tiff] TIFFReadRawStrip buffer data type", by Bob Friesenhahn
2008.03.29 11:44 "Re: [Tiff] TIFFReadRawStrip buffer data type", by James Sumners
2008.03.29 15:41 "Re: [Tiff] TIFFReadRawStrip buffer data type", by Bob Friesenhahn
2008.03.29 16:26 "Re: [Tiff] TIFFReadRawStrip buffer data type", by James Sumners
2008.03.29 14:58 "Re: [Tiff] TIFFReadRawStrip buffer data type", by Frank Warmerdam
2008.03.29 16:29 "Re: [Tiff] TIFFReadRawStrip buffer data type", by James Sumners
2008.03.29 16:51 "Re: [Tiff] TIFFReadRawStrip buffer data type", by Bob Friesenhahn
2008.04.24 14:16 "Re: [Tiff] TIFFReadRawStrip buffer data type", by James Sumners

2008.04.24 14:16 "Re: [Tiff] TIFFReadRawStrip buffer data type", by James Sumners

Thank you guys. I got everything working as it should be.

On Sat, Mar 29, 2008 at 12:51 PM, Bob Friesenhahn <bfriesen@simple.dallas.tx.us> wrote:

That makes a little sense. I was reading the image into a char buffer before, but got the feeling that I wasn't working with the correct values. I didn't think about an unsigned char. I'll give that a try and see how it works for me.

The only time there is benefit to using something other than an 'unsigned char' buffer type is when the bits per sample is 16, 32, or 64 and the data is presented the same as the CPU's native respresentation. Otherwise the data is packed in bitwise "natural" (MSB) order and needs to be unpacked using bit shifts/masks or some other approach.

--
James Sumners
http://james.roomfullofmirrors.com/

"All governments suffer a recurring problem: Power attracts
pathological personalities. It is not that power corrupts but that it
is magnetic to the corruptible. Such people have a tendency to become
drunk on violence, a condition to which they are quickly addicted."

Missionaria Protectiva, Text QIV (decto)
CH:D 59