Lightroom Classic: Before after comparison of metadata conflicts

  • 21
  • Idea
  • Updated 5 days ago
  • (Edited)
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.
Photo of Bryn Forbes

Bryn Forbes

  • 158 Posts
  • 21 Reply Likes

Posted 8 years ago

  • 21
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 388 Reply Likes
@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.
Photo of Bryn Forbes

Bryn Forbes

  • 158 Posts
  • 21 Reply Likes
Since Rob's website is gone, we're back to "huh, there's a metadata conflict. I have no idea what to do"
Photo of Itai

Itai

  • 2 Posts
  • 4 Reply Likes
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.
Photo of MerlinDE

MerlinDE

  • 2 Posts
  • 5 Reply Likes
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!
Photo of Russell Cardwell

Russell Cardwell

  • 58 Posts
  • 24 Reply Likes
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.
Photo of Jeremy Caney

Jeremy Caney

  • 26 Posts
  • 14 Reply Likes
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?
Photo of Cristen Gillespie

Cristen Gillespie

  • 1780 Posts
  • 605 Reply Likes
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.
Photo of Hennell

Hennell

  • 4 Posts
  • 3 Reply Likes
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!"


Photo of Rob Rippengale

Rob Rippengale

  • 99 Posts
  • 64 Reply Likes
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.
Photo of Russell Cardwell

Russell Cardwell

  • 58 Posts
  • 24 Reply Likes
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.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4683 Posts
  • 1268 Reply Likes
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.)
Photo of DenisPac

DenisPac

  • 2 Posts
  • 0 Reply Likes
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?
Photo of John R. Ellis

John R. Ellis, Champion

  • 4683 Posts
  • 1268 Reply Likes
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).
Photo of Richard Kain

Richard Kain

  • 56 Posts
  • 6 Reply Likes
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???