Hi! On Mon, 2010-04-12 at 10:03 +0200, Yury V. Zaytsev wrote:
> Therefore I'd like to inquire whether this is an issue with PIL, or > underlying TIFF reader, or maybe there's a built-in method to quickly > read Z-axis cut that I didn't consider (I'm a total PIL n00b). As a follow-up I have got another idea (which I would be quite reluctant to implement though) on how to dramatically speed up things, that is to convert the image to an uncompressed binary format which would allow random seeking (given that the resolution is known and so is the number of bytes per pixel). Or even consider storing lines of pixel luminosity over time one after another which of course would require to rewrite the whole file to append frames, but this is not really an issue since the length of the recording does not change. However, I'd really like to hear to some other ideas, since these TIFF files do not seem to be using any compression anyway, so in theory, sequential seeking operation should not be too expensive? -- Sincerely yours, Yury V. Zaytsev _______________________________________________ Image-SIG maillist - Image-SIG@python.org http://mail.python.org/mailman/listinfo/image-sig
