111
Replies
NEF is proprietary and Its just that Nikon software ignores those errors.
As written before those are lines in the file (of pixels) which are "not used/inside the range of pixels that should be used".
As it seems Photoshop still reads them/uses them to have more information for processing (but its garbage in some cases).
My thinking is now if I should just write a small command line program that fixes the RAW file huff code to be conformant with Photoshop.
Not that difficult. Maybe I should do a kickstarter project... 
Chris, the http://regex.info/exif.cgi website does not report a SubIFD error as would happen with an image slightly corrupted with Nikon Transfer.
MasterPPV,
The file on Dropbox is only 20MB. The image is 16.7 megapixels and I'd expect each pixel to be close to 2 bytes so the raw image data more than 30MB assuming no compression, which there could be. Is 20MB what size it is on your side? Is that a typical raw file size from other photos in similar lighting? It is ISO 1600 so there will be a bit of noise that makes the data less compressible than if it was illuminated well and ISO 100.
It is possible the file wasn't completely uploaded to Dropbox and you could try, again. However, if the NEF is only 20MB on your computer, then it has likely been truncated by some error in writing the raw data, either by the camera writing to the memory card, or transferring from the memory card to the computer or something on the computer.
The first thing to do, if you can, is try to transfer the image from the memory card to the computer, again. If the error was in the initial transfer then usually it'll work the second time. If the image is still the same size and doesn't work when you transfer it, again, then the image is likely corrupted on the memory card and there's not much you can do beside don't use that memory card, again. if a few images are corrupted on several memory cards then the fault is likely in the camera, itself, since not all memory cards would go bad at the same time.
Here is what I see using RawDigger to decode the raw data, where it looks like bits of other images are mixed in, so the file directory information on the memory card isn't pointing to actual data from this NEF, but other bits of information from other images or who know what else, as if the card has had a recovery operation performed on it and not all the information was recovered perfectly:
Looking at the NEF on a website that analyzes images that I referenced in Chris' portion of the reply, the thumbnail and preview JPG seem to be intact so it seems to be just the raw data that is bad:
If what is on Dropbox is what you have on your computer, then the raw data is missing from this file, and the best you can do is use the embedded JPG preview, which you can access by clicking the 1:1 above the preview thumbnail on the website and then right-clicking and doing a Save As to save as a JPG. Unfortunately the JPG will have a gibberish name so you'll probably want to change it to match the NEF base filename. It is possible that other images that are reported as having errors might be missing the embedded preview but at least this image has one that appears to be salvageable.
AdChoices