AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2002.04.05 09:19 "Saturation problem with REC601 YCbCr TIFF files", by Peter Vince
2002.04.06 15:43 "Re: Saturation problem with REC601 YCbCr TIFF files", by Andreas R. Kleinert
2002.04.08 15:48 "Re: writing tiff incrementally", by Daniel McCoy
2002.04.08 15:45 "writing tiff incrementally", by
2002.04.08 19:50 "Re: writing tiff incrementally", by Daniel McCoy
2002.04.08 16:02 "Re: writing tiff incrementally", by Sam Leffler
2002.04.08 16:11 "Re: writing tiff incrementally", by Daniel McCoy
2002.04.08 20:18 "TIFF_BYTE fields", by Dwight Kelly

2002.04.08 16:11 "Re: writing tiff incrementally", by Daniel McCoy

From: Sam Leffler <sam@errno.com>

Huh? I merged this way long ago. Sounds like it got lost.

I thought I remembered you merging it in too, but I took a look at the latest libtiff to make sure and it's not there.

We'll get it straightened out.

I would much rather get the one Pixar's been shipping to customers in production code and banging on for years merged into the mainstream than have someone cook up something new to cover the same territory.

Long ago, I added an entry point called "TIFFCheckpointDirectory()" in tif_dirwrite.c to accomplish this.

You basically call TIFFCheckpointDirectory() any time you want the tiff file so far to be readable.

Pixar has been using it for years so you can view the incomplete output of our renderer.

A quick check reveals that this has not been merged back into the generally available libtiff. We should get this merged in to the mainstream.

I'm no longer involved in libtiff support here but I'll check with the folks who are about getting this made available.

Daniel McCoy

From: myia@is.elta.co.il