I have never experienced that with the DNG converter. Would you care to share one of your NEF files so I could try the conversion here?
Incidentally, I can pretty much replicate your results by moving the temperature slider all the way to the left. How did it get to that position? That certainly wouldn't be a default setting. At least it wouldn't seem to be. Also, the histogram indicates that the image is somewhat overexposed. Is that really the way the DNG converter did its job? Doesn't seem right.
1 person found this helpful
Finally, here's a screenshot showing the NEF, DNG and JPEG of one of the images. All side-by-side.
As you can see, I did a little color correction on the DNG file. In case you're wondering, these were done using the latest Camera Raw. This screenshot is from Bridge. I usually use Lightroom, but didn't see the need since I was using the standalone DNG converter and a couple of "orphan" images.
This is just a thought, and I'm speaking outside of my area of knowledge (let alone any level of expertise). The underscore prefix on the filename indicates that you have your camera programmed to shoot in Adobe RGB. I don't ever try to manipulate any of this stuff, and different color spaces are not supposed to affect raw photography. But I'm just wondering if that might have something to do with this. I don't know. It's just a thought that occurred to me. I'm probably not being much help in this matter.
Thanks for your help JimHess
Resetting to Camera Raw Defaults in Adobe Camera Raw fixed the issue!
Based on your findings, I ruled out any problems with the NEF Raw files from camera, as you were getting the expected results.
I imported a RAW into Photoshop using Camera Raw and got the same blue shift in white balance etc. This led me to look at where DNG Converter and Camera RAW were getting their settings from...
It appears that, although DNG converter is a standalone program, it reads the settings from the same Camera Raw profile as ACR.
It's still a mystery how my Camera Raw Profile got so messed up though... Back to editing @pepe.dog 's snow pics now.
1 person found this helpful
The screenshot you posted shows that extensive edits have been made to the image.
This could have been caused by a develop preset being applied on import, but since all the values are gray (not white), I wonder if you have inadvertently saved these settings as default, so that they are applied to every image you import from that camera.
With an image open, go to Develop > Set default settings, and choose Restore Adobe default settings.
This should change all settings to default/neutral, and set White balance to As shot.
Now click Reset at the bottom right of the screen, which should update the image. and images you import from now on should display properly without any settings applied.
The underscore prefix on the filename indicates that you have your camera programmed to shoot in Adobe RGB. I don't ever try to manipulate any of this stuff, and different color spaces are not supposed to affect raw photography. But I'm just wondering if that might have something to do with this.
The color profile only affects jpgs, and has no effect on raw files, which are grayscale files.
Colors are added in the rendering process, and the image only gets an embedded profile when exporting.
Your answer is spot on!
I couldn't figure out why DNG Converter was applying the changes, I wasn't expecting Lightroom or ACR to have any effect on the file conversion settings.
This is basically the same issue brought up 10 years ago and again 2 years ago, in threads that you were active on. The diagnosis was clear, and your assumption that the DNG converter does not embed any profiles into the DNG was repeatedly corrected. It in fact just does, from the default camera profiles folder, confirmed by Thomas Knoll himself:
Do appreciate your effort though, but in the future you could simply reference those old threads and not make things convoluted by ignoring an already laid out understanding of the problem