Read & Seek error at scanline 0, mod. "TIFFReadEncodedStrip"

Asked by aseidel on 2019-02-23

Is this behavior a bug or normal behavior?

Some projects will report "hugin Error" "Seek error at scanline 0, strip 1568 (in module "TIFFReadEncodedStrip") that carries details expanding to a series of Read and Seek errors at scanline 0 within the TIFFReadEncodedStrip module.

Example:
15:28:11: Read error at scanline 0; got 344 bytes, expected 955 (in module "TIFFReadEncodedStrip")
15:28:11: Seek error at scanline 0, strip 1568 (in module "TIFFReadEncodedStrip")
15:28:11: Read error at scanline 0; got 344 bytes, expected 955 (in module "TIFFReadEncodedStrip")
15:28:11: Seek error at scanline 0, strip 1568 (in module "TIFFReadEncodedStrip")
15:28:12: Read error at scanline 0; got 344 bytes, expected 955 (in module "TIFFReadEncodedStrip")
15:28:12: Seek error at scanline 0, strip 1568 (in module "TIFFReadEncodedStrip")
15:28:12: Read error at scanline 0; got 344 bytes, expected 955 (in module "TIFFReadEncodedStrip")
15:28:12: Seek error at scanline 0, strip 1568 (in module "TIFFReadEncodedStrip")
15:28:12: Read error at scanline 0; got 344 bytes, expected 955 (in module "TIFFReadEncodedStrip")
15:28:12: Seek error at scanline 0, strip 1568 (in module "TIFFReadEncodedStrip")

For the example above the project comprises five tif files.

The error instance appears to be benign and is not repeatable once it has first occurred within an active project.

From a saved project the error message pops up at the first time the project's Projection type is changed to any other projection type.

Within a new project the error message pops up at the first time the project's Projection type is changed to any other projection type in the "Stitcher" pane or upon the first instance showing the "Fast Panorama preview" window.

Hugin 2019, OSX

Question information

Language:
English Edit question
Status:
Solved
For:
Hugin Edit question
Assignee:
No assignee Edit question
Solved by:
aseidel
Solved:
2019-02-27
Last query:
2019-02-27
Last reply:
2019-02-27
tmodes (tmodes) said : #1

Either the TIFF file is corrupted or it is a very strange subformat.

aseidel (akseidel) said : #2

The TIFF files are created by SilverFast 8.8.0 r14 (Aug 31 2018) 88cdfc4 31.08.

 I have noticed what looks like a pattern by using the ExifTool information reported by GraphicConverter for the TIFF files. In the IFD1 information section the Image Width value is the value that the Hugin message says it expected. In the listing above this would be the 955 value.

In all the Hugin projects I have checked so far, some getting the error and some not, it is only the projects where the IFD1 Image Width information reported is an odd integer, as opposed to an even integer where I see the Hugin error messages. I can in fact use that IFD1 Image Width information value odd or evenness to predict whether or not Hugin will throw the error.

I know nothing about the ExifTool information. These TIFF images have both an IFD0 and an IFD1 section as reported by GraphicConverter.

tmodes (tmodes) said : #3

Can you provide some small examples?

aseidel (akseidel) said : #4

I can provide two example projects where one generates the error and the other does not. Each project file uses two TIFF sized about 84 MB each. I do not think I can make the erring TIFFs smaller.

So if that size, four 84 MB TIFF files and two 3 KB project files, is not too large, then I can place them at a DropBox for you get get at or use some other method that you recommend.

tmodes (tmodes) said : #5

I was hoping for a smaller size. But it is okay. Dropbox is ok for sharing.

tmodes (tmodes) said : #7

Ok. There is a problem in the underlying library exiv2 when extracting the preview image. This results in the error message. But it does not affect the output at all, because there the preview image is not used at all.
I therefor fixed Hugin to ignore this error. The fix will be in 2019.0 rc1.

aseidel (akseidel) said : #8

Your ability to track this down is impressive. I will be removing the Dropbox files after some time. Thank you.