Skip to main content
Adobe Photoshop Family

165 Messages

 • 

3.2K Points

Fri, Dec 9, 2011 2:36 AM

22

Lightroom Classic: Before after comparison of metadata conflicts

It['d be great to be able to use the before after split screen mode to look at metadata conflicts visually. You could see which version of the metadata is the one to keep. Although you still need to see differences like keywords and so on. I like rob cole's SQLLiteroom's ability to find the files with metadata conflicts, but now I need to figure out which one to keep. Even if it wasn't a visual comparison, that'd be ok. I just feel like I'm blind choosing between the catalog and the xmp file that are out of sync.

Responses

4.5K Messages

 • 

76.3K Points

9 years ago

@2011-12-10 (v4.0), ChangeManager has a feature that presents a dialog box with a list of all develop setting and metadata differences between what's in the catalog, and what's in xmp on disk. I have not thought of a way to include visual comparison, yet.

165 Messages

 • 

3.2K Points

4 years ago

Since Rob's website is gone, we're back to "huh, there's a metadata conflict. I have no idea what to do"

3 Messages

 • 

172 Points

3 years ago

Yes and I would like a sensible resolution choice. Right now we have:
- Overwrite original (terrible terrible terrible)
- Reload from source (looses all keywords, ratings, cropping, development, etc)

We really need a sync the metadata from file but keep Lightroom settings.

4 Messages

 • 

262 Points

3 years ago

This reply was created from a merged topic originally titled Lightroom Classic: Show actual metadata differences on XMP vs catalogue conflicts....

Whenever Lightroom detects any kind of conflict between it's catalogue and a XMP sidecar file, it asks me how to handle that conflict. Problem is, I don't get any detailed information on the conflict like editing timestamps or actual differences in settings.

We do need 
  1. much better conflict detection (often times LR detects conflicts that don't exist)
  2. overview on changes between the two versions
  3. preview of image rendered with the different settings

This has been discussed for years now:
Lightroom: Before after comparison of metadata conflicts

Please fix this!

67 Messages

 • 

1.5K Points

a year ago

This reply was created from a merged topic originally titled Idea: Preview Metadata Changes.

I am constantly confronted with the little exclamation point icon that tells me that metadata has been changed. (Theoretically by another application, but usually no other application has been involved. Lightroom has simply lost track.) 

Unfortunately, all the choices are blind.


  • Blindly overwrite the metadata with different metadata Lightroom has found on the disk.
  • Blindly overwrite the metadata on the disk with different metadata lightroom has found.
  • Or ignore this notice and hope it goes away.
There is no way to know what metadata has been changed. Is it EXIF data or is it develop settings? Which set of data is newest? There's no way to know. 

Long ago, I learned the hard way not to click the button. I ignore it unless I absolutely need to resolve it. At that point the only way to resolve it is to create a virtual copy, update the original, and compare.

Why not add a preview feature, or better a way to compare the two versions side by side? It would save a lot of time.

26 Messages

 • 

872 Points

Out of curiosity, why don’t you click the button to resolve the conflict? Just because it’s ambiguous which is newer? Or have you also encountered issues such as file corruption?

2 Messages

 • 

92 Points

For me, it's because I don't know what I'm changing when I overwrite.  The fear is that I would be over-writing deliberate changes I made in the past, such as new keywords, and lose the work I did.

Champion

 • 

5.3K Messages

 • 

95.4K Points

If you don't use other programs to modify photo's metadata (e.g. Bridge), then it is always safe to to overwrite the file metadata with that from the catalog. Most instances of LR's "conflict" notifications are spurious.

2K Messages

 • 

35K Points

a year ago

This reply was created from a merged topic originally titled Idea: Preview Metadata Changes (merging).

I'm glad you went to the trouble to write this one up. It doesn't sound like an easy "fix," but compared to destroying our metadata, it seems to me to be a worthwhile effort for Adobe to make. If they only let us see what we'd changed, where and when, it could be enough much of the time, but in cases like yours, maybe better to go all the way to letting us compare visually if that's reasonably possible.

Note: This conversation was created from a reply on: Idea: Preview Metadata Changes.

5 Messages

 • 

240 Points

a year ago

Good to know in 8 years this remains unsolved.

Obviously Lightroom can see there is a conflict, so why can't it display it? Even a basic listing of the fields it can see conflicting would be a million times better than the random guessing we have now...

In Library:
Title: "Summer in the pool"
In File:
Title "Summer in the pool!"


108 Messages

 • 

2.7K Points

a year ago

Adobe just emailed an offer to "Learn from the experts on how to create amazing customer experiences." Maybe we'll get lucky and their programmers will sign up for the conference.

67 Messages

 • 

1.5K Points

a year ago

Another thing I have started doing recently:

Since I automatically save metadata as external files, I have started using ‘Show in Finder’ to open the folder at the image location. There, I can make a copy of the XMP file. Then when I click the button to update the settings, I know that I can restore the original by renaming the XMP file.

Not an elegant solution by any stretch. But until Adobe decides to fix this, we’re stuck with such workarounds.

Champion

 • 

5.3K Messages

 • 

95.4K Points

a year ago

If you're sure that you haven't modified a photo or its metadata outside of LR, it's safe to Metadata > Save Metadata To File and choose Overwrite Settings. (This doesn't address the core feature request, but LR tends to generate a lot of spurious metadata-conflict warnings.)

4 Messages

 • 

146 Points

a year ago

I set most of the metadata (keywords, GPS position...) using Geosetter, and I develop all my photos with LR. In some occasions (like today), I forgot to reload the metadata from file before developing and then all developed photos miss the metadata.
Without the metadata comparison, I have the only choice of either lose my Geosetter settings and keep my development settings, or the opposite.
It would be nice to load metadata from file with a comparison box showing the differences between file and LR database to choose the ones to keep (for the current photo and for all photos in the batch).
Outside of LR, is there any plugin that provides this feature?

Champion

 • 

5.3K Messages

 • 

95.4K Points

a year ago

You can download Rob Cole's ChangeManager plugin from here:
https://github.com/DaveBurns?tab=repositories

According to Rob's post from 8 years ago, it displays differences between metadata in the catalog and metadata stored in the photo or sidecar on disk.   I don't know if it lets you merge the two. Many of Rob's plugins appear to work in LR 8, even though they haven't been updated in four years (Rob passed away in 2015).

68 Messages

 • 

1.1K Points

a year ago

I guess that there is some information within the metadata that does not affect the appearance of the image, such as remembering how the image was printed or exported. When such entries change, there is no change in the appearance, which is the most important thing about the image. 

If the above is correct, it would be useful for Lightroom to distinguish changes that affect the appearance of the image from changes that do not change that appearance. Couldn't you simply color the flag (red!?) when the differences affect the appearance, and leave it white when the appearance is not changed by the metadata difference? Using red, for example, would highlight the cases in which the user should really care about the fact that there is a conflict. And if you make such a distinction, perhaps you could add in a script that goes through a folder to remove all of those conflicts, by either updating or not (the choice set as a user preference).

Opinions???

17 Messages

 • 

352 Points

a year ago

The metadata conflict is driving me bonkers.

I created a smart collection with metadata not up to date, about 6K out of 150K show up, select all, ctrl-s, see them saving, watch the count go down, watch the count go back up.
Select all, click conflict icon, overwrite disk, watch the count go to 0, sit back, watch the count go back up again.

LR is broken, or wrong, or both.
If we could only see what the alleged problem is...

484 Messages

 • 

12.3K Points

Do you have any plugin's active (enabled) in your LR Classic Catalog and if so which ones?  I have seen cases where a plugin detects that the metadata field used to indicated a metadata mismatch has changed and in response modifies one of its own metadata fields and that change itself is then flagged as a new mismatch.  

Try disabling all plugin's nut shipped with LR and see if problem persists.  If it does then my speculation is incorrect.  If it does correct the problem, then re-enable the plugin's one by one and test between each one to isolate which plugin is the culprit.

17 Messages

 • 

352 Points

I only have out of box plugins, I disabled them all, and restarted LR.
I repeated the select where status is changed on disk, save metadata, and the changed on disk count went back up as before.

I am speculating, but I wonder if LR gets confused by the file timestamps, as my images are on a NAS (catalog on local SSD), and like most Linux based NAS's it does not have nanosecond timestamp granularity. E.g. I have to use /fft when using robocopy.

If only LR would tell us what changed.

Champion

 • 

5.3K Messages

 • 

95.4K Points

a year ago

It would be good to identify what's causing this problem. Spurious metadata conflicts have continued to be reported over the years, and while the causes of some of them have been identified and fixed, it's clear it continues to be a problem.

Here's a tedious way we can see if there's some metadata field that's causing your spurious conflicts:

1. Download and install the free ExifTool utility. (Select the Windows Executable or MacOS Package as appropriate.)

2. In LR, select one of the photos that LR shows as having a conflict.

3. Right-click the photo and do Show In Finder / Explorer to see exactly where the photo is stored on disk.

4. Start Terminal (Mac) / Command Prompt (Windows) and do this command:
exiftool -a -G "path"
where path is the full path to the file.  If the photo is a raw file, change the path's extension to ".xmp". Be sure to enclose it in double quotes. For example:
exiftool -a -G "/Users/john/Pictures/2019/2019-09-30/DSC02309.xmp"
5. Copy/paste the entire output in your reply here.

6. Download my free plugin Show Catalog Metadata

7. Unzip the download and install "showmetadata.lrplugin" into LR. If you're not familiar with how to install plugins, follow the similar instructions here.

8. In LR, with the same photo selected as in step 2, do the menu command File > Plug-in Extras > Show Catalog Metadata > Show. Copy and paste the contents of the window that appears to your reply here.

These steps will dump out nearly all of the metadata fields stored in the LR catalog with those stored in photo file on disk. We can then compare each metadata field manually to see if any are changing.