Received: from [192.48.153.1] by phillip.thumbsplus.com (NTMail 3.03.0017/7.aaxh) with ESMTP id pcrews for <pcrews@cerious.com>; Tue, 26 May 1998 10:23:53 -0400
Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by sgi.sgi.com (980309.SGI.8.8.8-aspam-6.2/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id HAA22183; Tue, 26 May 1998 07:03:27 -0700 (PDT)
	mail_from (owner-tiff@sgi.engr.sgi.com)
Received: (from majordomo-owner@localhost)
	by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF)
	id GAA76546
	for tiff-list;
	Tue, 26 May 1998 06:37:59 -0700 (PDT)
	mail_from (owner-tiff@sgi.sgi.com)
Received: from sgi.sgi.com (sgi.engr.sgi.com [192.26.80.37])
	by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF)
	via ESMTP id GAA68840
	for <tiff-relay@cthulhu.engr.sgi.com>;
	Tue, 26 May 1998 06:37:57 -0700 (PDT)
	mail_from (owner-tiff@sgi.sgi.com)
Received: from hermes.csd.unb.ca (hermes.csd.unb.ca [131.202.3.20]) by sgi.sgi.com (980309.SGI.8.8.8-aspam-6.2/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id GAA14786
	for <tiff@sgi.com>; Tue, 26 May 1998 06:37:56 -0700 (PDT)
	mail_from (w6wnk@unb.ca)
Received: from unix.unb.ca (w6wnk@sol.sun.csd.unb.ca [131.202.3.6])
	by unb.ca (8.8.7/980316-15:45) with ESMTP id KAA07260
	for <tiff@sgi.com>; Tue, 26 May 1998 10:37:55 -0300 (ADT)
Received: from localhost by unix.unb.ca (8.8.5/970702-14:15)
	id KAA01027; Tue, 26 May 1998 10:37:53 -0300 (ADT)
Date: Tue, 26 May 1998 10:37:52 -0300 (ADT)
From: Roland Hammerle <w6wnk@unb.ca>
X-Sender: w6wnk@sol.sun.csd.unb.ca
Reply-To: hammerle@acm.org
To: tiff@sgi.com
Subject: Re: Processing large files
Message-ID: <Pine.SOL.3.96.980526103517.501A-100000@sol.sun.csd.unb.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-tiff@fddi-sgi.sgi.com
Precedence: bulk

At 08:39 PM 26/05/98 +0900, you wrote:
>At 16:20 98.05.25 -0300, Roland Hammerle wrote:
>>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?
>>
>>Thank you,
>>Roland
>
>Hi
>
>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()?
>
>Thank you
>
>Takao
>
>

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.

Regards,
Roland

