P: Metadata collisions between catalogue and files

|> "Any thoughts on how best to determine whether to keep catalog or external when the files may have been in multiple catalogs?"

Not really.

My workflow is fairly simple - keep photo in only one catalog, and never enter metadata anywhere but Lightroom, and always launch Photoshop from Lightroom. With those rules, it is almost always safe to overwrite disk. If there is any question, I use ChangeManager to provide a detailed list of the differences between settings and metadata in catalog vs. disk.

Having a photo in multiple catalogs definitely poses a wrinkle...

SQLiteroom is super handy for finding which files have conflicts. Any thoughts on how best to determine whether to keep catalog or external when the files may have been in multiple catalogs? http://feedback.photoshop.com/photosh...

SQLiteroom is super handy for finding which files have conflicts. Any thoughts on how best to determine whether to keep catalog or external when the files may have been in multiple catalogs? http://feedback.photoshop.com/photosh...

SQLiteroom will create a collection of photos that have metadata conflicts.

xEmP provides such a collection to all who are willing to use it.

xEmP provides such a collection to all who are willing to use it.

Ino, these symptoms have struck many people. See this topic and add your vote:

http://feedback.photoshop.com/photosh...

Ino, these symptoms have struck many people. See this topic and add your vote:

http://feedback.photoshop.com/photosh...

I've noticed that every time my Lr catalog is optimized several photos randomly change from "up to date" to "has been changed". I'm absolutely sure the photos haven't been changed in any way, internally or externally, so I guess it's a bug with the optimization routine in Lr, related to the persistent general metadata bug.

I dont know why Adobe is dragging their feet on this one. Yes, there are some technical issues around when the info is getting updated, and yes, all are easily solvable, or so it seems to me too, so no - I dont have a clue why Lr3 hasn't got this remedied - maybe Lr4 (or Lr3.5, ha-ha).