2

When I'm using the LibTiff.Net 2.3 library I'm confused as to why I would ever want to save as a multi-strip TIFF image. Why not just always use the one big chunk (single-strip) rather then all the tiny chunks (multi-strip)? I think the multi-strip is even a little bigger possibly?

Arvo Bowen
  • 4,524
  • 6
  • 51
  • 109

2 Answers2

3

Usually a multi-strip image is a little bit larger (in terms of file size) than single strip. But multi-strip images has some advantages:

  • Less memory can be used to process whole image because an application can process on strip at a time. For very large images it can make a difference. See this question for example.

  • Random access to image data is less complicated. Some compression schemes like LZW do not allow random scanline to be read. The library must decode all scanlines from the start of a strip in order to decode a scanline within a strip.

Community
  • 1
  • 1
Bobrovsky
  • 13,789
  • 19
  • 80
  • 130
0

I believe the multi-strip TIFF was from the old FAX Days. It was a way of semantically breaking up a single image into parts (or in this case pages). This could also provide a similar function in rendering, allowing the image to "scan in" piece by piece, instead of requiring the entire massive strip before it could display anything.

Aren
  • 54,668
  • 9
  • 68
  • 101
  • OK that makes sense. :) Is there a standard StripOffset that is used in the multi-strip file? If I had to guess I would say it is 768? – Arvo Bowen Feb 24 '12 at 22:33
  • According to the spec, ' TIFF also supports breaking an image into separate strips for increased editing flexibility and efficient I/O buffering'. So I don't think this is a legacy hangover from FAX. It's benefits would hold for current systems too. – bincob Feb 07 '18 at 09:02