j_rgen_irt98ss1iwpha's profile

7 Messages

 • 

144 Points

Mon, Nov 18, 2019 10:46 AM

Lightroom Classic: Exporting EXIF with high "Transform" value

I just encountered a weird thing. My website complains with just TWO out of many photos I posted (JPG from LR), that it can't read the EXIF data. Looking with IrfanView, there are no EXIF data in these two (they got exported in one batch with all the others).
I noticed that these two photos are heavily transformed (Vertical -65), whereas all the others, that got some transformation (not all but quite some) don't have such high values and got exported with their EXIF. So. I played around with the vertical value and found out, that the EXIF data gets exported up to the value -39 and from -40 on it's missing. Reproducible.

Responses

645 Messages

 • 

11.5K Points

2 y ago

I haven't been able to reproduce it in Lr 9 on Win10 with any of my raw or jpg originals.
What version of Lr & OS are you running?
What are your originals - raw, jpg, from what camera, etc?
Are you having the same issue with images from other cameras/formats?
Are you sure you don't have an export preset or plug in that's set to remove the metadata? 

Adobe Administrator

 • 

10.7K Messages

 • 

142.1K Points

2 y ago

I have not been able to reproduce either using LrC 9.0 and Win 10 -1903.  The information Tom requests might help us duplicate your issue.

7 Messages

 • 

144 Points

2 y ago

Windows 10.1903 Enterprise
Lightroom Classic 9.0
The source files are Canon CR2 with 50 megapixels.
I could reproduce it several times without fail. So, I am a bit surprised.

Employee

 • 

1.7K Messages

 • 

32.4K Points

2 y ago

What are your steps to reproduce the bug? Are you using some ftp publish service? What are the export settings? Could you share a raw file and the associated imp?

7 Messages

 • 

144 Points

2 y ago

Since two people couldn't reproduce it, I tried again, and it just went as described: -39 - EXIF - yes, -40 - EXIF nopes.
So, since I tried those two pictures that caused the trouble in the first place, I thought, let's try another one. I selected some random picture, that I did not export previously. There I couldn't reproduce it! I even copied with "Previous" the changes I've made to that selected photo.
So somehow it must be that RAW together with the vertical transform setting.

I could provide the RAW and the end result, yes. How? Should I upload it to my server and provide a link?

Employee

 • 

1.7K Messages

 • 

32.4K Points

2 y ago

For sharing the photo and the xmp, you could use the Creative Cloud sync or other dropbox style sharing service and share the link.

Champion

 • 

6K Messages

 • 

103.6K Points

2 y ago

With JPEGs exported from your sample photo in my LR 9.0, ExifTool shows EXIF data when Vertical = -39 but not when Vertical = -40. 

The -39 JPEG has two APP13 Photoshop segments, while the -40 JPEG has three.  It appears that the Photoshop Thumbnail field increased in size from 64346 to 64717 bytes between the two photos, just enough to require a third APP13 segment.  It's likely this third segment is related to LR getting confused and omitting or overwriting the APP1 segment containing the EXIF fields.

Employee

 • 

1.7K Messages

 • 

32.4K Points

2 y ago

Thanks for the report. We'll investigate and log bug if necessary.

115 Messages

 • 

2.3K Points

2 y ago

We are working on a fix for this. Thank you for reporting this and for providing samples!

For now, a workaround is to open the photo in Photoshop and save it as a JPEG from there... yes, I know this is not awesome.

This will be more likely to happen with photos that are square (and square-ish) and have a lot of subject detail. The reason why different transforms make a difference is probably because some end up pushing more detail into the final image bounds than other transforms.

Adobe Administrator

 • 

10.7K Messages

 • 

142.1K Points

1 y ago

Updates to Lightroom Classic, Camera Raw, and the Lightroom Ecosystem were released yesterday and contain a fix for this issue.  Please install the appropriate update and see if it solves this problem. You can read more about the updates here.

Thank you for your patience.