-
2004.10.28 14:05 "Re: [Tiff] why does tiffcp::cpSeparateBufToContigBuf takes BYTES_per_sample as parameter?", by Bob Friesenhahn
-
2004.10.28 15:18 "Re: [Tiff] why does tiffcp::cpSeparateBufToContigBuf takes BYTES_per_sample as parameter?", by Sachin Garg
- 2004.10.28 15:43 "Re: [Tiff] why does tiffcp::cpSeparateBufToContigBuf takesBYTES_per_sample as parameter?", by Gerben Vos
- 2004.10.28 16:29 "Re: [Tiff] why does tiffcp::cpSeparateBufToContigBuf takes BYTES_per_sample as parameter?", by Bob Friesenhahn
- 2004.10.28 18:39 "Re: [Tiff] why does tiffcp::cpSeparateBufToContigBuf takes BYTES_per_sample as parameter?", by Andrey Kiselev
- 2004.10.28 17:58 "Re: [Tiff] why does tiffcp::cpSeparateBufToContigBuf takes BYTES_per_sample as parameter?", by Sachin Garg
-
2004.10.28 15:18 "Re: [Tiff] why does tiffcp::cpSeparateBufToContigBuf takes BYTES_per_sample as parameter?", by Sachin Garg
2004.10.28 16:29 "Re: [Tiff] why does tiffcp::cpSeparateBufToContigBuf takes BYTES_per_sample as parameter?", by Bob Friesenhahn
Thanks Bob, this means that I should be expecting any bit-depth in a tiff image.
But I am confused (as mentioned in my original post) how tiffcp routines (cpSeparateBufToContigBuf and cpContigBufToSeparateBuf) handle all bit-depths, they seem to be byte oriented.
I am not prepared to address that since I am not familar with them, however, it is worth noting that libtiff itself supports a far broader range of images (with the assistance of extra user code) than are supported by the libtiff utilities or the simple APIs which accept/prepare RGBA packets. Tiffcp is a good example of code which supports baseline TIFF images and common TIFF formats. It is not prepared to handle unusual bits-per-sample values.
Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen