Copy link to clipboard
Copied
I recently come across the following Issue:
I have a bunch of jpg files I have post-processed in Photoshop that I want to add geo locations to using the Lightroom Classic map module. After adding the locations I mark all images and do right click - metadata - save metadata to file. For some jpg files the data is written into the jpg file (desired behavior and how I know it from LR Classic for the past 6 years), while for others LR creates a seperate xml file (same location same name as the jpg) containing all metadata including the location.
Since this is a recent thing for me I suspected LR 14 to be the issue so I downgraded back to 13 but the issue persists.
I already cleared out my complete LR catalog and only importet a hand full of jpg files to test but the issues persists.
The issue can be reproduced, it is always the same jpgs causing the issue.
When I open one of the not functioning jpg files in Photoshop and save it again in a new location the issue persists. When I open it, create a new document of the same dimensions, mark all in the original, copy across to the new document and then save the new document as jpg I can then add gps locations to the new jpg in LR as expected.
I can also copy the gps data from a working jpg to one of the ones LR refuses to add gps data to using exiftools so the jpg file does not seem to be inherently broken in some way.
There is no different between the jpg files LR can write to and the ones where it insists on writing a xml file. They were taken using the same camera and have gone through the same workflow.
Any help would be appreciated since as of right now I am resorting to using a dummy image I assign the desired location to in LR and then use command line + exiftools to copy the gps tag across to the non functioning jpg which is extremely cumbersome.
It appears this behavior is caused by the addition of Content Credentials to the JPEG, which are added to the JUMBF metadata section.
In the past, when LR didn't know how to update an industry-standard file format, LR would write a .xmp sidecar instead. For example, when LR first added support for HEIC, it wrote .xmp sidecars; a later version of LR wrote directly into the HEIC file. Similarly, LR still creates .xmp sidecars for AVIFs, even though that format supports updatable metadata. (Actuall
...As-designed
In case of already signed JPEGs, metadata and develop settings are written to sidecar XMPS so as not to invalidate the CAI signature.
Copy link to clipboard
Copied
I disabled CC for an image I am working on, and when I saved as a jpeg it, no longer gave me a c2paws file. When I add that image, and a few other jpegs to LR, changed the dates, then saved, I am no longer getting XMP files created. So I guess I will just keep CC disabled for a while until they work the bugs out.
Copy link to clipboard
Copied
in my photoshop i have content credentials disabled in the settings (both option are set to NONE).
i also checked in lightroom export settings, that feature is also disabled.
some of the images affected where never exported by LIGHTROOM, just imported and keyworded.
it also only affects JPG files.
why would TIFF files are not affected when it is about content credentials?
if LR can not write to files with content credentials as a "safety reason" (to protect the integrity) it should affect all files with content credentials, not just JPG files.
or content credentials are not stored in TIFF files? i have no idea because i don´t use that feature.
my main concern is that LR does not write the metadata into the file.
if it would write the data into the file and make an ADDITIONAL XMP file it would not be such a serious issue for me. it would still be annoying behavior but not potentially harmful.
but i can´t trust LR when it works this way.