AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2004.04.15 00:26 "[Tiff] Large TIFF files", by Lynn Quam
2004.04.15 01:57 "Re: [Tiff] Large TIFF files", by Frank Warmerdam
2004.04.15 02:17 "Re: [Tiff] Large TIFF files", by Lynn Quam
2004.04.15 04:41 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.15 06:05 "Re: [Tiff] Large TIFF files", by Rob van den Tillaart
2004.04.15 13:33 "Re: [Tiff] Large TIFF files", by Frank Warmerdam
2004.04.15 21:51 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.16 17:23 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.17 02:50 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.22 10:32 "Re: [Tiff] Large TIFF files", by Gerben Vos
2004.04.22 18:41 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.22 19:45 "Re: [Tiff] Large TIFF files", by Dan Smith
2004.04.22 20:08 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.15 12:23 "Re: [Tiff] Large TIFF files", by Dan Smith
2004.04.20 08:29 "Re: [Tiff] Large TIFF files", by Rob van den Tillaart
2004.04.20 14:20 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.21 07:06 "Re: [Tiff] Large TIFF files", by Rob van den Tillaart
2004.04.20 20:44 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.21 07:30 "Re: [Tiff] Large TIFF files", by Rob van den Tillaart
2004.04.21 17:54 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.22 07:38 "Re: [Tiff] Large TIFF files", by Rob van den Tillaart
2004.04.22 18:21 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.22 18:34 "Re: [Tiff] Large TIFF files", by Thomas J. Kacvinsky
2004.04.22 18:43 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.22 18:49 "Re: [Tiff] Large TIFF files", by Bob Friesenhahn
2004.04.22 19:52 "Re: [Tiff] Large TIFF files", by Phillip Crews
2004.04.22 20:45 "Re: [Tiff] Large TIFF files", by Andrey Kiselev
2004.04.22 21:06 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.22 21:35 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.22 21:49 "Re: [Tiff] Large TIFF files", by Bob Friesenhahn
2004.04.22 21:59 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.22 22:23 "Re: [Tiff] Large TIFF files", by Bob Friesenhahn
2004.04.22 22:31 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.22 22:34 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.22 23:03 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.22 23:17 "Re: [Tiff] Large TIFF files", by Bob Friesenhahn
2004.04.22 23:59 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.23 15:58 "Re: [Tiff] Large TIFF files", by Leonard Rosenthol
2004.04.26 14:50 "Re: [Tiff] Large TIFF files", by Marco Schmidt
2004.04.23 12:45 "Re: [Tiff] Large TIFF files", by John Aldridge
2004.04.23 13:12 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.26 07:30 "Re: [Tiff] Large TIFF files", by Rob van den Tillaart
2004.04.26 09:58 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.26 11:06 "Re: [Tiff] Large TIFF files", by Rob van den Tillaart
2004.04.26 11:28 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.26 12:05 "Re: [Tiff] Large TIFF files", by John Aldridge
2004.04.26 12:33 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.26 11:38 "Re: [Tiff] Large TIFF files", by Gerben Vos
2004.04.26 12:50 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.27 06:12 "Re: [Tiff] Large TIFF files", by Rob van den Tillaart
2004.04.26 16:54 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.23 13:16 "Re: [Tiff] Large TIFF files", by Phillip Crews
2004.04.23 20:28 "Re: [Tiff] Large TIFF files", by Andrey Kiselev
2004.04.23 15:54 "Re: [Tiff] Large TIFF files", by Leonard Rosenthol
2004.04.23 20:37 "Re: [Tiff] Large TIFF files", by Bob Friesenhahn
2004.04.23 22:31 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.23 22:38 "Re: [Tiff] Large TIFF files", by Bob Friesenhahn
2004.04.23 22:58 "Re: [Tiff] Large TIFF files", by Chris Cox
2004.04.26 10:03 "Re: [Tiff] Large TIFF files", by Joris Van Damme
2004.04.26 14:32 "Re: [Tiff] Large TIFF files", by Bob Friesenhahn

2004.04.26 07:30 "Re: [Tiff] Large TIFF files", by Rob van den Tillaart

Most important is that any file which does not in fact exceed 2GB must be readable by old code.

I think there may be consensus about that, the point has been raised before, but little has been said about how exactly to achieve this.

The library cannot know in advance how large the TIFF to write is going to be, right? In fact, it's quite possible that the library user / application code does not know in advance, even disregarding unpredictable compression factors.

Can the library know in advance? If it does it can make an optimal choice (32 or 64 bit);

I assume this choice can be made per image (in case of an multipage) which leads to the question:

With a 64bit extention to the current format is it acceptible to have both 32 bit offsets and 64 bit offsets used together?

if the library does not know the size in advance it must use 64 bit.

Q: Can the library know the filesize afterwards?

Yes it can most of the times.

<scenario>
        A tiffwriter has written 64bit tiff file.
        When ready it detects filesize < 4GB so 64 bit was not needed.
        It goes through all tags and replaces all 64 bit tags with 32
        bit tags leaving all data on the same position.
        This tag postprocesing can be fast.
        Drawback is quite some 32 bit holes in the data
        but very backwards compatible!
</scenario>

When postprocessing is not an option, e.g. the data is written to a stream and the writer does not know the final size it should use 64 bit.

Note: This scenario implies that the library internally works in 64 bit mode.

[fileformat and library are closely related but two different things]

Bob raised the hope that a simple redefinition of some types may allready do the job. I'm not a C man myself, wouldn't know for sure, but does this not exclude 32bit and 64bit TIFF living in the same library? If I'm not mistaking, this is the way LibJpeg supports both 8 and 12 bit jpeg, but one needs two seperate compiled LibJpeg libraries to support 'em both in the same app as a consequence. But I'm not a C man, please point out the errors in my thinking.

Is it then an option to include a boolean 32bit/64bit selector in the main LibTiff TIFF structure instead? Thus allowing applications to select either bitdepth *in advance*, for example by means of a flag of some sorts in the TIFFOpen/TIFFClientOpen call? And rewriting some of the IFD handling code to deal with either case?

It is not possible to select allways in advance the right mode, as a user can decide to enlarge a bitmap to > 4GB. When 32 bit mode was chosen and there is a sudden runtime switch to 64bit mode I can imagine quite some difficulties.

=> So the library must work internally in 64 bit mode.

regards,
rob