Bug/Problem in Adobe DNG Converter 6.4.0.139 - Some Canon RAW images not converted completely

  • 1
  • Problem
  • Updated 7 years ago
Of 500 images on a cheap no-name CF card, 5 images cannot be converted completely into a DNG using the Adobe DNG Converter version 6.4.0.139. See the following screen for the result of those 5 images:

Second example:


This is how it comes out freshly from DNG converter. This is the worst example - the other 4 images are not as bad and only a smaller portion is chipped away. I strongly thing that the files themselves are damaged and DNG converter is doing everything correctly - but two problems persist:

1. The original CR2 file opens just fine, I can import it to Lightroom and everything
2. If the CR2 was somehow damaged, shouldn't the DNG converter warn me about this damaged image and that the output will look like we see on the Screenshot?

Contact me directly so I can give you a link for the CR2 RAW files in question for your testing purposes.
Photo of Dennis Gaida

Dennis Gaida

  • 12 Posts
  • 0 Reply Likes
  • undecided

Posted 7 years ago

  • 1
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2656 Posts
  • 341 Reply Likes
Does the same thing happen with the new DNGC 6.5 release candidate available at Adobe Labs: http://labs.adobe.com/

Also if you convert the files, again, do they show exactly the same problem, or was it a transient condition?
Photo of Dennis Gaida

Dennis Gaida

  • 12 Posts
  • 0 Reply Likes
The converted files show exactly the same problem when using the DNG converter again as well as when using the Lightroom built-in conversion on import (which is using the same DLLs I suppose).

I could not find a standalone DNG converter 6.5 release candidate, only Lightroom 3.5 + Camera RAW 3.5 - what should I do with these.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2656 Posts
  • 341 Reply Likes
So the problem is repeatable with the same source CR2 and wasn't a transient event.

LR and the DNGC are separate products and wouldn't share the same DLL although the core codebase should be the same.

The DNGC accompanies ACR, so follow the Camera RAW path on Labs for a few clicks and you'll see the download link.
Photo of Dennis Gaida

Dennis Gaida

  • 12 Posts
  • 0 Reply Likes
Found version 6.5.0.200 beta here: http://labs.adobe.com/downloads/camer...

The problem persists and the rendering errors look exactly the same as they look in the old DNG converter.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2656 Posts
  • 341 Reply Likes
Try "converting" to a Linear DNG and see if you get an error from the DNGC, then.

I would expect the DNGC to deal the the RAW data in a more detailed way when creating the linear format than when it creates a normal DNG so you may actually get an error.

Do you feel comfortable posting a link to an one of your files that doesn't work for others on the forum to try, to see if it's a machine-specific issue or not?
Photo of Dennis Gaida

Dennis Gaida

  • 12 Posts
  • 0 Reply Likes
Same things happens with a linear DNG.

Have a go at a CR2 RAW file: http://bit.ly/nGbk7m

When I convert it, the lower left corner (approx. 1/4th of the image) is missing.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2656 Posts
  • 341 Reply Likes
So far I have only tried opening the CR2 in Canon's Digital Photo Professional, and while it doesn't give me an error on opening, if I try to Convert and Save the process hangs about 85% of the way across and has been that way for 10 minutes, so far. I'll probably let it run another 10 minutes to see if I eventually get an error or not. The CPU is at 100%.

Does LR actually Export these CR2s to JPGs, properly, or not? Can you see a full-resolution 100% preview in Develop in LR after you change something like sharpness? Initially the LR previews will be just the CR2's embedded JPG and maybe LR is hanging on the decode, too.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2656 Posts
  • 341 Reply Likes
Ok, after a total of about 15 minutes trying to do a Convert and Save, Canon's DPP finally aborted with a simple message: "An Error Occurred: Decoding Failed"

This suggests the files are corrupt and the fact LR doesn't easily detect this is the only mystery. My experience with LR is that it renders whatever it finds and doesn't really display error messages. That is why I ask if it will create an intact-looking JPG if asked to Export, or not.
Photo of Geoff Walker

Geoff Walker, Champion

  • 214 Posts
  • 43 Reply Likes
Having had a look at the file.
It is unfortunately corrupt. The ok looking view is only the jpeg preview and as soon as it is rendered by LR/ACR the corruption shows.
If they are still on the card, try another card reader/usb cable. If they are still corrupt, the card is most likely the culprit.
Photo of Dennis Gaida

Dennis Gaida

  • 12 Posts
  • 0 Reply Likes
Thanks guys.
As I said in the beginning - it was a cheap-o card, so I wouldn't be surprised if the images really were damaged. My second reason for posting this is that somehow Lightroom/DNGC should be able to tell corrupt files from non-corrupt apart.

Maybe the file(s) can serve to provide a better algorithm for corruption detection? So the user could get a message like "the file you are trying to convert seems to be corrupt".
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2656 Posts
  • 341 Reply Likes
The error condition is being reported, as a weird looking image, just not with words.

The image-import doesn't actually decode the RAW data so doesn't know something is wrong to report it, and once the images are in LR, itself, the corruption should be obvious if you actually work with the image, and if it's not obvious or only in a portion of the image that doesn't matter, then why should LR bother you with a message when you can see for yourself and crop off the bad part of the image.