LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
September 2005

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems

Thread

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

2005.09.13 01:26 "Re: read-by-scan-line buffers full strip, part 2", by Joris Van Damme

2005.09.13 15:34 "Re: read-by-scan-line buffers full strip, part 2", by Mark R Olin

2005.09.13 15:58 "Re: read-by-scan-line buffers full strip, part 2", by Joris Van Damme

2005.09.13 16:17 "read-by-scan-line buffers full strip, part 3", by Mark Pilon

2005.09.13 16:54 "Re: read-by-scan-line buffers full strip, part 3", by Joris Van Damme

2005.09.13 17:48 "Re: read-by-scan-line buffers full strip, part 3", by Mark Pilon

2005.09.12 21:22 "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