AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2014.06.17 09:46 "[Tiff] In-memory tiffs", by Benedikt_Führer
2014.06.17 13:25 "Re: [Tiff] In-memory tiffs", by Bob Friesenhahn
2014.06.19 21:48 "Re: [Tiff] In-memory tiffs", by Olivier Paquet
2014.06.20 13:23 "Re: [Tiff] In-memory tiffs", by Benedikt_Führer
2014.06.20 17:29 "Re: [Tiff] In-memory tiffs", by Olivier Paquet

2014.06.20 17:29 "Re: [Tiff] In-memory tiffs", by Olivier Paquet

Hi Benedikt,

2014-06-20 9:23 GMT-04:00 "Benedikt Führer" <Banshee999@gmx.de>:

>

And that I find, is somewhat strange because I doubt I'm the first person who wants to use it like that. How was this supposed to be done then?

I suspect it was simply never done with more than one directory. So it's a bug / design issue with the libtiff C++ API. Given the way libtiff works, the "output" API should probably have used a std::iostream. The easiest way to fix this without breaking anything would be to add a 3rd TIFFStreamOpen with just that. I'm a bit rusty on how the read and write parts interact however (specifically, if they always, sometimes or never have separate offsets in the stream). If you must use an already installed (older) libtiff then you'll have to roll your own with TIFFClientOpen().

Olivier