Warning [minor] Oversized SubIFD1 StripByteCounts etc.

[tommyzebman]

Warning: [minor] Oversized SubIFD1 StripByteCounts (24390144 bytes, but expected 21341376)  << this was from another post and was also a Nikon nef file.


I saw this on another post.  I get the same message SOMETIMES.  I also use Nikon nef files and that is when i get it - but only SOME nefs.  It seems to have something to do with the size of the internal preview jpeg generated by the camera ??

exiftool thinks the jpeg should be a certain size but it is not always in this range?

Metadata goes into the file fine and it looks okay, just seems like a problem somewhere.

ADDED:  I use Nikon D700 camera, 14 bit, no compression - if any of that matters.

[Phil Harvey]

SubIFD1 is the main raw image, not a jpeg preview.

I don't get this problem with a D700 NEF sample I have here.  If you get it only sometimes, perhaps these files have been modified by Nikon software?  I recommend against downloading or modifying NEF files with Nikon software because it does questionable things to these files has a history of corrupting images.

- Phil

[Alan Clifford]

SubIFD1 is the main raw image, not a jpeg preview.

I recommend against downloading or modifying NEF files with Nikon software because it does questionable things to these files has a history of corrupting images.

- Phil

The current crop of Nikon software uses sidecar files rather than modifying the image files.  But I still think the the "download" application still is capable of modifying files but I don't use it for that reason so cannot be really sure.

[tommyzebman]

In the past I have used Capture NX-2 and it did occasionally do some things I did not want.  The new Nikon software does not do any writing to NEF files.

Just took a new image a few minutes ago.

Warning: [minor] Oversized SubIFD1 StripByteCounts (24390144 bytes, but expected 21341376) - C:/Users/thosa/Desktop/New folder/TR1_4822.NEF
    1 directories scanned
    1 image files updated

What I find a little interesting is the byte size numbers are always exactly the same - even from the other forum poster.

[tommyzebman]

Found out some more information.  I do not always update to the newest version of exiftool, however, lately I have made plans to begin using a lot more so I did.  I reloaded an older version from a couple of years ago or so and the error does not occur.  Then tried the newest version again - error warning appears.  Tested a few more times back and forth with the same result.

Maybe the newer version does not like the old camera files?    Not trying to be a thorn, but now it is a little more interesting.  Phil you are still the only "blog hoster" out there that actually responds in a timely manner and provides real help.  So thank you for that.

[StarGeek]

I reloaded an older version from a couple of years ago or so and the error does not occur.  Then tried the newest version again - error warning appears.  Tested a few more times back and forth with the same result.

What is the number of that old version?

[tommyzebman]

Just grabbed an older one i had in the folder at random to test.  Looks like 9.9.0.0  2015.  I guess I could try one from a year ago or so to compare.

[tommyzebman]

exiftool 10.58 (2018) also process these nef files with no warning/error message

[StarGeek]

Are you able to share a file that has the error?

[tommyzebman]

It is not just a problem file it is all nef files created by my Nikon D700 for the newer versions of exiftool.  Something changed later in 2018 with exiftool versions.  Previous to this, the error message does not show using the same files.

Last version that I happen to still have a copy of that has no problem is 10.58  March 2018.  I will just use -m command until it is figured out per this older post (see below).  Notice this post from ANOTHER user with the same problem is Aug. 2018.  Probably started between March and August 2018.

https://exiftool.org/forum/index.php?topic=9443.msg48836#msg48836

[Phil Harvey]

This message was added in newer ExifTool versions.  Older versions didn't report this problem.

- Phil

[tommyzebman]

I am confused as to what the problem is and what causes it.  Or, maybe it is not really a problem, and so I should ignore it.

[Phil Harvey]

If your images aren't showing problems when you view them, you can safely ignore this.

It is odd that my D700 NEF Sample (camera Software Ver.1.00) doesn't have this issue.

This check was added in an attempt to validate the size of the image data, based on SamplesPerPixel, BitsPerSample, StripByteCounts and BytesPerStrip from the TIFF specification.  Although the NEF file is based on the TIFF specification, it is actually a proprietary file format, so Nikon is free to do whatever they want and this can't really be considered an error.

- Phil

[tommyzebman]

Okay thanks.  Maybe 14 bit uncompressed with no jpeg saved (my files) vs. other possible settings.

[tommyzebman]

YES.  Seems that uncompressed nef file (big file) triggers error message but lossless compressed does not trigger it (same basic image, within minutes of each other, etc.)