1

I'm using the latest version of Lightroom Classic (10.1) on Windows 10 but I think I've seen this issue in previous versions as well.

Lightoom provides a "metadata has been changed" flag as a library filter item or when defining a smart collection. When a file has this flag set, I can usually go to Metadata --> Save Metadata to File (Ctrl+S) and it will rewrite the image file and clear the flag. But I am running into a handful of images where this doesn't work. I use Ctrl+S to save the metadata, and alhough I can see the modification time on the file change, the "metadata has been changed" flag remains set for that image.

It happens for several different file types (JPG, TIFF, and PSD). My library settings are ON for "Include Develop settings in metadate inside JPEG, TIFF, PNG, and PSD files", and OFF for "Automatically write changes into XMP".

Is there another setting somewhere I should check? Any insight into why this might be happening?

UPDATE - I originally stated DNG files were sometimes included in the problematic image list. But the menu item Metadata --> Update DNG Previews & Metadata corrected that issue, so I removed "DNG" from the description above.

1

This is a known bug that has existed for years. This is one relevant thread on the feedback.photoshop.com forum site.

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-incorrect-flag-metadata-was-changed-externally/5f5f46214b561a3d4274fb58

It seems to be that there are two time tags in the metadata and there can be a conflict... or at east that is one potential cause. This post describes the timestamp issue.

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-wrong-timestamp-stored-in-catalog-causing-wrong-metadata-status-all-windows-versions/5f5f458e4b561a3d42537137

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.