Quick help needed, Error parsing files....

[bslanger]

I'm under a deadline, and I have just encountered my first 'There was an error parsing files' message in DNG.  I went through all the steps in the book (re-name, metadata, keywords, rank and adjust, etc), and then I dropped a folder of 600 Canon RAW files on DNG Converter, and about 30 or so of the images get that error.  I can open them fine in Bridge.  What might the problem be, and is there any kind of work around?  What does this mean? Are the images bad?  Much appreciative of any help......

[Rick McCleary]

I don't know what is causing your specific problem, but the general recommendation is to have no more than 300 files in a folder when processing DNG's.

[annbrooks]

I had the same DNG problem. "Error parsing files..." I recently converted RAW_110_060207, a bucket with seven subfolders. Everything converted until the sixth file of 20 images where none parsed and seventh folder of 66 images where 19 converted, the balance didn't.

Opps, I just went back to the RAW file of 20 images mentioned above and tried to convert it alone to DNG and I immediately got the error parsing message for all 20. So I checked all the files again in Bridge and realized those 20 were the files that I couldn't apply CR settings to because "Camera Raw Default" was greyed out. But I know I've had the problem where all images in a file were CR and a few handfulls didn't convert to DNG.

In the past I've converted, for instance, buckets with 500-600 images split 150 & 400 or 250 & 250 +/- between two subfolders and all converted with no problems.

So, in researching this further, I seem to have come up with two problems.

1. Why 20 files of 250 didn't have CR setting applied when all others in the file did and when I went back to apply CR to those I got "Camera Raw Defaults" greyed out.

2. I've had other files where, in converting RAW to DNG, all converted but 15 - 20 in one file of a bucket of two files of approx. 250 each. Why?

Thanks for your help.

Ann

[peterkrogh]

Brian,
A few quick thoughts:

1. Make sure you are using the latest DNG converter (3.4).  Also, I assume you did not touch the files with anything other than Bridge (which does not actually touch the files.  You didn't use anything else on the files, like PhotoMechanic or iView to put in metadata, did you?)

2. Whenever you see the error, be on the lookout for file corruption.  Don't erase any older versions of the files, particularly on the card (if possible).

3. Make a note of all files that produce an error.  The first thing I would do it to try to open them in Camera Raw, and look at them at 100%.  If they look fine in Camera Raw, then you can breath easier.  You may have found a bug in the software if this is the case.

4. If the files *do* open in Camera Raw, you can make your DNGs from there (Save button).

5. If the files do open in CR, try this.  Take the XMP files out of the folder with the images and try to do a conversion to DNG with the DNG converter.  If it works without error (and you are using the latest version) send the XMP files to me, and I'll forward to Thomas Knoll.

6. If the files do not open up to full resolution in Camera Raw (or won't open in CR at all), then you probably have a a file corruption problem.  Try to locate earlier versions of the file and test them.

7. If the files have been erased from the original media cards, you can try to recover them with PhotoRescue.

8. Try to open the files with other software.  Start with manufacturer's software - you can also try Bibble.

Let em know if the above helps and where the error lies.
Peter

[Rick McCleary]

... this is why we love you. Peter...

[bslanger]

Yep, I second Rick's comment.  I checked the files that had the corruption, and they were all.....from my assistants Canon 30D camera, which DNG 3.3 does not cover.    I see the update
for DNG to 3.4 was listed as May 8th.  Is there any way to keep up to date with the latest software?  I believe Adobe has a software updater that is supposed to be fairly automatic,
but I don't find it that accurate.  I'm going to assume the download to 3.4 will fix it all, as the non parsed files all open perfectly in Bridge and CS2.  Thank's for the quick help Peter.

[peterkrogh]

Brian,
I always feel better once we can pinpoint where the trouble was.
Let us know if there are any more issues, but that sounds exactly like the problem.
Peter