Return-Path: owner-tiff@olympiakos.com
Return-Path: <owner-tiff@olympiakos.com>
Received: from localhost (localhost [127.0.0.1])
	by at1895.spb.edu (8.12.1/8.12.1/Debian -5) with ESMTP id g2EDPLeB016886
	for <dron@localhost>; Thu, 14 Mar 2002 16:26:31 +0300
Received: from eudoramail.com [209.185.123.45]
	by localhost with POP3 (fetchmail-5.9.0)
	for dron@localhost (single-drop); Thu, 14 Mar 2002 16:26:31 +0300 (MSK)
Received: from gate7.olympiakos.com ([64.32.199.150]) by shared1-mail.whowhere.com; Thu Mar 14 05:08:10 2002
Received: from localhost (daemon@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) with SMTP id FAA25905;
	Thu, 14 Mar 2002 05:53:46 -0500
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Thu, 14 Mar 2002 05:49:51 -0500
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) id FAA25881
	for tiff-outgoing; Thu, 14 Mar 2002 05:49:51 -0500
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from tecgraf.puc-rio.br (IDENT:root@duchamp.tecgraf.puc-rio.br [139.82.85.1])
	by gate7.olympiakos.com (8.9.3/8.9.3) with ESMTP id FAA25878
	for <tiff@olympiakos.com>; Thu, 14 Mar 2002 05:49:49 -0500
Received: from michelangelo.tecgraf.puc-rio.br (michelangelo [139.82.85.73])
	by tecgraf.puc-rio.br (8.9.3/8.9.3) with ESMTP id HAA04913
	for <tiff@olympiakos.com>; Thu, 14 Mar 2002 07:47:31 -0300
Message-Id: <5.1.0.14.0.20020314073743.00b94cc0@mail.tecgraf.puc-rio.br>
X-Sender: scuri@mail.tecgraf.puc-rio.br
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 14 Mar 2002 07:49:02 -0300
To: tiff@olympiakos.com
From: "Antonio E. Scuri" <scuri@tecgraf.puc-rio.br>
Subject: Using TIFFReadScanLine() for Large images
In-Reply-To: <006401c1cadb$b2fda360$0201a8c0@pacbell.net>
References: <LBEDIBKHPNLCJIHCOFEOCEGACGAA.shan@adsgroup.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-tiff@olympiakos.com
Precedence: bulk
Status: RO
Content-Length: 1068
Lines: 26

At 14:04 13/3/2002 -0800, Peter Montgomery wrote:
>Assuming you've read the TIFF header and know A) how big scanlines are,
>B) how big the image is, and C) have malloc'ed a scanline, just loop
>through and read the scanline into your buffer

   Since TIFF images are writen in "strips" how much memory LibTiff uses 
for reading an image line?

   From another point of view, I have a very large image that does not fits 
in memory. I would like to convert it to another format. I can do this 
using TIFFReadScanLine, but the memory used internally by LibTiff can be 
very large, because the file can be stored in only one strip, or in tiles, 
compressed, and so on...

   Anyone can explain the memory usage in LibTiff? or can explain if the 
TIFFReadScanLine method is ok for reading large images?

   In time, JPEGlib has the same issue. Anyone can comment on the JPEGlib 
memory usage?

Thanks,
Antonio Scuri


To subscribe or unsubscribe email tiff-request@olympiakos.com with subscribe
or unsubscribe in the email body.  Libtiff home page: http://www.libtiff.org

