AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2005.09.12 21:22 "[Tiff] read-by-scan-line buffers full strip, part 2", by Mark Pilon
2005.09.13 01:26 "Re: [Tiff] read-by-scan-line buffers full strip, part 2", by Joris
2005.09.13 15:34 "RE: [Tiff] read-by-scan-line buffers full strip, part 2", by Mark R. Olin
2005.09.13 15:58 "Re: [Tiff] read-by-scan-line buffers full strip, part 2", by Joris
2005.09.13 17:48 "Re: [Tiff] read-by-scan-line buffers full strip, part 3", by Mark Pilon
2005.09.13 16:17 "[Tiff] read-by-scan-line buffers full strip, part 3", by Mark Pilon
2005.09.13 16:54 "Re: [Tiff] read-by-scan-line buffers full strip, part 3", by Joris

2005.09.12 21:22 "[Tiff] read-by-scan-line buffers full strip, part 2", by Mark Pilon

OK,

my initial question was about reading a compressed image of 4420 lines in one band -- libtiff wants to buffer the whole strip; in this case it's the whole image.

The answer I got was a definitive 'no way'...

OK, I buy that; libtiff is designed as a workstation library -- much memory available. what do people do who are using libtiff in embedded / low-memory applications?

I still need to handle the problem image - is there some way to implement a 'null' codec to get me the image data so that I can go off to the side and decompress it line-by-line?

or do I even need to implement anything? -- could I just rewrite the compression type for this image as 'none'?

any other possibilities / suggestions?

thanks,

Mark