2009.03.27 22:42 "[Tiff] TIFFOpen throws access error", by
-
2009.03.27 23:57 "Re: [Tiff] TIFFOpen throws access error", by Bob Friesenhahn
- 2009.03.30 18:26 "Re: [Tiff] TIFFOpen throws access error", by
-
2009.04.07 13:44 "Re: [Tiff] Writing tiff to in-memory buffer", by Christian Henning
- 2009.04.06 15:35 "[Tiff] Writing tiff to in-memory buffer", by Christian Henning
- 2009.04.07 14:13 "Re: [Tiff] Writing tiff to in-memory buffer", by Edward Lam
- 2009.04.07 15:35 "Re: [Tiff] Writing tiff to in-memory buffer", by Bob Friesenhahn
- 2009.04.08 20:56 "[Tiff] writing in-memory tiffs", by Christian Henning
- 2009.03.28 01:03 "Re: [Tiff] TIFFOpen throws access error", by Toby Thain
2009.04.07 15:56 "Re: [Tiff] Writing tiff to in-memory buffer", by Christian Henning
Without thoroughly analyzing the code, (and making a WAG) I get the impression that libtiff reads back the header it just wrote to obtain the actual endianness of the data and the TIFF subformat.
Yes, it was a WAG. Obviously. FYI, the read_proc is called before the write_proc. Though, I don't think libtiff is trying to get the endianness.
FWIW, I'm fine with the current solution.
Thank you all for your insight.
Christian