This content has been marked as final. Show 11 replies
Tried a restart?
What camera? (firmware, etc.)
What recently changed on your machine?
Hi - yes, I tried restarting.
I am using the most recent firmware on my D80 and unknown firmware version on my D200.
No recent system changes.
Nothing else is running strangely.
Plenty of RAM, speed, disk space, and I increased the cache in ACR to 2 gigs after clearing it.
What compression options are you using when converting to DNG? What type of Edits did you perform in ACR? Thanks, adriana
1. I have been using the Lossless Compression option when converting NEF's to DNG's, per Bruce and Jeff's recommendation in _Camera Raw_.
2. I performed a wide range of edits on these files in their NEF version before attempting the conversion to DNG, but none of it is exotic. I mean, things like WB, detail, exposure, hue, sharpening, masking, spot-healing, etc.
Thanks. I'm a bit worried that maybe this is turning out to be an unusual problem with no obvious / well-known solution... ?
You say this has started in ACR 4.4.1 correct? Did you perform the same edits and conversion in ACR 4.3? What version of Bridge are you running?
Have you tried the same workflow using ACR via Photoshop? Thanks!
Hi again, Adriana.
I believe I've identified the source of the problem: It sees to happen whenever I click "DONE" in ACR...before the conversions to DNG are complete. Rather than alert me ("CLOSING NOW MAY CAUSE LOST DATA"), ACR seems to just interrupt the conversion in mid-stream. The result is no thumbnail, partial meta-data, and perhaps other unknown losses.
Is this a known limitation of ACR -- that it saves incomplete files if you click DONE before it's truly done?
Or, does the pattern imply that something is buggy in my particular installation?
I'd love to know either way.
I think you're making a big mistake by clicking on the Done button while there are still images in the buffer waiting to be saved. I always wait until the saving process is complete before I close ACR and, so far, I have never encountered the problem you are experiencing.
The book says that you can be doing processing in ACR and go back and do other things in Bridge during that processing, but I don't believe the intention was to be able to close ACR before the processing completes.
Hi, Jim. Clearly, you're right.
I think new users might benefit from a defeatable warning that all current batch jobs will be interrupted when they click "DONE". As in all of my other software, I just assumed I'd be warned if I was harming any important background process.
I realize, too, that my original urge to be "done" with the ACR window as soon as possible came from ACR's lack of a conventional "MINIMIZE" icon. The options to quickly get ACR 100% out of the way -- in order to see Bridge again -- seem limited (in Windows, anyway).
Thanks again for your help, each of you.
"but I don't believe the intention was to be able to close ACR before the processing completes"
Wrong. That was absolutely the intention.
The problem was probably Bridge was caching the same folder the files were being saved to by the background queue. It saw the partially saved files and tried to read them, but since there where not fully saved yet, it saw them as corrupted.
The files are almost certainly just fine. Bridge's cache just still thinks they are bad.
Purging the Bridge cache for the problem folder should resolve the Bridge issue.
Aha! And in much the same spirit, I see now that merely hitting "refresh" in Bridge also solves it.
The one remaining wrinkle is that the DNG's don't have an "open with ACR" option when I right-click...whereas the NEF's do have that option.
I'm betting that's just some preference setting that I've forgotten about.
Anyway, my major worry is solved: The files are _not_ corrupted nor incomplete -- they just won't show the metadata, thumbnail, etc. until refreshed/uncached in Bridge.