Skip to main content
Adobe Photoshop Family

5 Messages

 • 

110 Points

Mon, Apr 30, 2018 10:25 AM

Lightroom Classic: When I export as DNG the embedded preview of the image is 'original' rather than the edit

If I export as a DNG, and then preview the file in Finder or similar, the preview displays the original image, rather than the edited image that was exported. If I open in Camera Raw, the image displays as edited (which is the expected behaviour)

The preview thumbnail should match the edited image.

Responses

204 Messages

 • 

4.1K Points

2 years ago

In Lightroom filmstrip theres an icon at top right of each thumbnail... three lines with a downward pointing arrow, click that to update the preview. However on windows ACDsee still display the old file  but Photo Gallery displays the updated.

5 Messages

 • 

110 Points

Hi, thanks for the reply. I assume this is the same as 'update preview' via the photo menu. I think it's a bug-- the embedded preview is just wrong. If you save as a TIFF. there's not problem. it's specific to the export as DNG function.

Champion

 • 

3.1K Messages

 • 

55.9K Points

I think this is more a matter of philosophy. Exporting as DNG is like exporting ‘as original’, except that the file type is now DNG rather than proprietary raw. Yes, your edits are stored in the metadata, so an Adobe application like Photoshop /Camera Raw will open it with these edits applied. So looking through Adobe glasses you might expect the preview to show the edits too. But if you open the DNG in any other application, it will open as a non-edited raw file and then the preview is correct.

Johan W. Elzenga,

http://www.johanfoto.com

5 Messages

 • 

110 Points

Hi Johan, If there was consistency, it would be okay. Unfortunately, there isn't. If I export this to my desktop, the thumbnail contains edits. If I view the file in finder, it doesn't--- Both these systems are outside of the adobe ecosystem and yet render differently. Philosophy aside, non-deterministic behaviour relating to the DNG filetype is problematic. I completely understand your points about it being similar to 'as original'-- my point is, the experience of using it is sub-optimal.

Champion

 • 

3.1K Messages

 • 

55.9K Points

I agree that the thumbnail should also be the original.

Johan W. Elzenga,

http://www.johanfoto.com

1.3K Messages

 • 

22.5K Points

2 years ago

Are you sure that this isn't Apple's OS-level raw processing?

If you export a DNG and review it in PhotoMechanic, for example, you see the edited version.

5 Messages

 • 

110 Points

it's non-deterministic-- which is my issue. I think it would be possible to export the file, view it in your OS, and assume your edits had not been exported with the file. This is compounded by viewing the file in different ways, and seeing different results. The point of the thumbnail is to be representative. The option to include the original file within the DNG file at time of export suggests that the thumbnail should represent the DNG, rather than the original.

1.3K Messages

 • 

22.5K Points

No idea what you mean by non-deterministic, but it's simple. The thumbnail appears one way when it's rendered in a raw processor, and showing all the Adobe edits in apps that aren't raw processors. If you want to see them in Finder with Adobe adjustments, can't you just switch off raw conversion in Finder?

Champion

 • 

745 Messages

 • 

13.3K Points

I can duplicate the display of the "original" in Finder and the "edited" on the desktop of a DNG export but this seems to be more of an Apple issue than Adobe.   

5 Messages

 • 

110 Points

Hi Robert--- Adobe operates in an environment--- It's not fair to blame the OS when the app exists within that environment. It's the applications' responsibility to provide consistent behaviour. The embedded thumbnail is the contention here--- that is the responsibility of the application. 

Champion

 • 

745 Messages

 • 

13.3K Points

Apparently Apple uses the the embedded thumbnail when displaying the Icon on the desktop and renders the RAW when creating the thumbnail in Finder so why is it an Adobe problem when Apple choses to do it differently in different places.  Apple OS and software has really went downhill the last several years and this might be another example.