XMP files not beng applied in different LR3 Catalog

[ElCapitan]

I have a few LR3 Catalogs going on right now. One main one that has all my files, one on my laptop for working on images at work or on the go, and then one specifically for work images.

I have about 12 or so images that I worked on in the laptop catalog and then backed up on my main hdd. I then imported those files into the main catalog with everything. For some reason some images wont load the all the changes I made in the develop module. The xmp files are there, and they work fine in the laptop catalog but just don't show up in the main catalog.

Does anyone have any idea why this would be? I really don't want to have to re-edit them all in LR3 again.

[Doug Sundseth]

LR stores edits in an internal database. It also has the option of writing the edits to an XMP file. (This is different from Bridge, which only stores edits in XMP files.)

If there is a conflict between the XMP and the internal, I don't know what it does. Since you're editing files on multiple computers, I suspect that you are running into a conflict.

FWIW, I've had situations where LR has misplaced information about photos when moving from one computer to another. Specifically, I've had photos with the wrong preview images that I could only fix by deleting from the catalog and reimporting. So it might be something related to that, too.

I'd be tempted to change the filename (on image and corresponding .xmp file) and reimport to fix the problem. Sorry I don't have anything more definitive.

[ElCapitan]

I may have found a solution to the problem. I am not sure what caused it to begin with, but if I selected an image while in catalog A that worked in catalog A, I could right click, hover over metadata, and then select save metadata to file. Then when importing that image into catalog B, and the image was fine. Also, if this did not work for certain images, while in catalog B, I could right click the image, hover over metadata, and select read metadata from file.


Everything seems to be working fine now, but like I said, I am not exactly sure why this happened. At least I know how to solve the issue though.