Lightroom Classic: Before after comparison of metadata conflicts

  • 21
  • Idea
  • Updated 1 day 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 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


  • 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 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!"