TIFF and LibTiff Mail List Archive


1998.05.26 13:00 "Processing large files", by Roland Hammerle
1998.05.26 13:10 "Re: Processing large files", by Takao Matsuda
1998.05.26 13:37 "Re: Processing large files", by Roland Hammerle
1998.05.26 16:07 "Re: Processing large files", by Joe Longo

1998.05.26 13:37 "Re: Processing large files", by Roland Hammerle

What is the easiest way to use the TIFF library when one has large files whose raster image cannot be buffered in memory? Using TIFFRGBAImage one always has to allocate memory that can hold the whole structure. Is it possible to allocate memory for only one strip at a time *and* using some high-level interface for reading TIFF files?

It's not the answer to your post, but it gave me a question. It may be a very basic issue, but I'm very new to this library, so...

Do you always have to allocate memory with the size of the whole image data? For instance, when you TIFFWriteRawStrip(), does it write to the memory and write to the file only when you TIFFClose()?? Or does it write to the file directly when you TIFFWriteRawStrip()?

I don't know that much about the TIFF library. Usually, IO is buffered and only when TIFFClose or TIFFFlush are called the contents will be written to the disk. When reading/writing raw strips only memory of the size of the strip has to be allocated. However, I am not interested in raw strips. I simply want the same functionality as TIFFRGBAImage provides - except that I can read the file piece by piece instead of in one huge chunk.