AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
April 2004

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

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



Valid HTML 4.01!



Thread

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

2004.04.26 14:50 "Re: Large TIFF files", by Marco Schmidt

On Thu, 22 Apr 2004 16:59:24 -0700, you wrote:

[...]

> The IFD already allows for you to do things like that (solution a).
> Yes, the current approach leaves a hole and adds to the end.  But you 
> rarely end up with too large a hole.

Besides, an additional utility could analyze a TIFF file and report
how much space is wasted. Another one could write a new file that
copies from the first, of course without the holes. Maybe even
"linearizing" the TIFF - if somebody finds that useful.

[memory managment]
> OK - that's much too complex.
> Now you're trying to implement a file system within a file.
> That's been tried before - and it was a nightmare.

But isn't adding to the end and leaving a hole already the beginning
of a "file system within a file"? In-place editing of files with
complex binary headers always has the potential to become a nightmare.
Know-how from managing database files could be reused. With those
files, the authors of the DBMS code have to deal with holes, deletion
markers, overflow areas, periodic reorganization to reclaim space etc.
all the time. However, such a file memory management project is
probably the exact opposite of "a small extension of TIFF".

A lot of work could be saved if writing back image data into a TIFF
file would remain reserved to compression type 1 (uncompressed). The
amount of data for a strip / tile would never expand compared to the
previous size of the same strip / tile. Thus, "only" metadata from
IFDs would have to be moved around.

Another approach (for a completely new file format) could save
metadata in one file and each strip / tile in a file of its own. This
hands over all the work of managing changing strip sizes to the file
system, where it belongs. Obviously, having a number of files for one
image instead of a single file makes it less convenient to handle
those images. But it's not that hard either, and the necessity to copy
these huge images between places may be smaller compared to
normal-sized image files.

By the way, I agree with the notion that any file format that breaks
TIFF compatibility should get a file extension of its own. Also a name
that doesn't have TIFF in it, to avoid confusion. Java and JavaScript
still suffer from people thinking that those two languages are
somewhat related (understandable given the name similarity). With end
users of imaging software (instead of developers) it's likely to be
even worse.

[memory managed file format]
> The most complex I'd go is something like the ZIP archive format.
> And that's only really useful if you're dealing with several 
> independent chunks of data.

I don't think archiver programs really do in-place editing of ZIPs.
They read from the original and write to a new file.

Regards,
Marco