2004.10.28 12:03 "[Tiff] why does tiffcp::cpSeparateBufToContigBuf takes BYTES_per_sample as parameter?", by Sachin Garg
-
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 18:39 "Re: [Tiff] why does tiffcp::cpSeparateBufToContigBuf takes BYTES_per_sample as parameter?", by Andrey Kiselev
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.
The answer is simple: tiffcp doesn't support such images (howewer, as it was noted, channel interleaved images with unusual bit depths may be processed correctly).
Andrey
Andrey V. Kiselev
Home phone: +7 812 5274898 ICQ# 26871517