Known Participant

Question

Lr needlessly generating XMP sidecar for ALL imported photos

Forum|Forum|1 year ago
May 13, 2024
6 replies
1485 views

After the latest update to Lr 13.2 & Camera Raw 16.2, i noticed all my photos folders have been populated with an xmp file for each image file, even those unedited! All these new xmp files have the same date of creation, May 1st, which around the time i updated Lr.

The Lr option says "Automatically write changes into XMP" not generate a pointless sidecar for every imported photo, and i've had that checked for years, it seems it's only after the last update that it went crazy with it.

And now, some photos in the catalog even have an alert icon saying the xmp settings have been changed outside of Lr (which can't be, i haven't even looked at them after the bulk import, much less edit them in some other software).

Does anyone know what this is? Is it a bug or the intended way the new Lr update is supposed to work? I didn't mind a few xmp files (so that i see the same edits in CR and also as backup) but now doubling the number of items in each folder for pointless xmp files is crazy. And i can't even delete them as i don't know which ones actually have edits and which don't.

My Lr version is 13.2, Camera Raw 16.2

and i'm on an iMac Retina 21.5", 2017,

Processor: 3.6 GHz Quad-Core Intel Core i7

Memory: 16 GB 2400 MHz DDR4

Graphics: Radeon Pro 560 4 GB

macOS

This topic has been closed for replies.

johnrellis

Legend

@alxb49009547 and @rotorglow, you're probably tripping over this bug:

https://community.adobe.com/t5/lightroom-classic-bugs/p-save-metadata-to-file-doesn-t-always-set-metadata-status-to-up-to-date/idi-p/14641120

DdeGannes

Community Expert

@alxb49009547 , Try the option available at import to use "Embedded and sidecar" then the import process will not use an Adobe White balance setting which will constitute a change and create an XMP sidecar. You can view the import in the Library module and this will change when you select the Develop Module, then "As shot WB" will display in the History panel.

I have not verified on my system since I will not select the Option " Automatically write changes to XMP" since that would cause multiple XMP files on my system.
There is also another thread reporting a bug with respect to " As shot WB" showing in the history panel which happens when "Embedded and sidecar" is used at import.

It is my opinion neither of these issues are "bugs".

Regards, Denis: iMac 27” mid-2015, macOS 11.7.10 Big Sur; 2TB SSD, 24 GB Ram, GPU 2 GB; LrC 12.5,; Lr 6.5, PS 24.7,; ACR 15.5,; (also Laptop Win 11, ver 24H2, LrC 15.3; PS 27.0; ) Camera Oly OM-D E-M1.

DdeGannes

Community Expert

The option is located in Catalog Settings> Metadata> Automatically write changes to XMP.

It stands to reason any "change" made at import to Metadata, edits etc will generate an XMP sidecar for RAW images. Example, if you create keywords, Copyright etc a XMP sidecar will be automatically created,

Regards, Denis: iMac 27” mid-2015, macOS 11.7.10 Big Sur; 2TB SSD, 24 GB Ram, GPU 2 GB; LrC 12.5,; Lr 6.5, PS 24.7,; ACR 15.5,; (also Laptop Win 11, ver 24H2, LrC 15.3; PS 27.0; ) Camera Oly OM-D E-M1.

R

rotorglow

Participant

Yes, I'm aware that IF I had made any changes to these old photos (note that I'm not talking about during import), and the Write Changes To XMP checkbox was checked, there would be new XMP files written out.

What's happening to me (and the OP as far as I can tell) is different. Write Changes was enabled, but out of the blue Lightroom was going through 20-40K OLD EXISTING images and writing new XMP files for no apparent reason.

Turning off Write Changes has fixed the problem, and probably should have been off from the begining, but for the current images I'm working (which sit on an SSD), it's preferable to have Write Changes enabled for my needs. What's confusing and unwelcome is LIghtroom deciding the other 80K images in my library had changed through no action of mine.

Per Berntsen

Community Expert

but for the current images I'm working (which sit on an SSD), it's preferable to have Write Changes enabled for my needs.

By @rotorglow

When you have finished editing these images. select them in Library, and go to Metadata > Save metadata to file.

Or press Ctrl + S (Windows), Cmd + S (Mac).

If you do further edits or add/change any metadata later, you have to repeat the command.

R

rotorglow

Participant

This is happening to me too, with LR Classic 13.3. XMP files for about 30K images (on a spinning hard drive) that haven't been touched in months or years are being resaved for some reason. My latest plan is to let it finish and hope LRC doesn't decide it needs to do this again.

JohanElzenga

Community Expert

> And i can't even delete them as i don't know which ones actually have edits and which don't.

You can always delete them if you don't want them. XMP sidecar files are extras, and are not used by Lightroom. They are just written to XMP (if you want to) for use in other apps. Lightroom itself only uses the edits and other metadata that are saved in the catalog.

-- Johan W. Elzenga

alxb49009547Author

Known Participant

Yes, i know i can delete the xmp files and i won't lose the edits in Lr, but i was keeping them mostly as backup and sometimes to show me the same edits in camera raw 🙂 So if i want to keep just those ones, i can't only delete the useless ones without edits, unless i go through each photo one by one and see which one has edits (that i'd want to keep the sidecar for) and which ones don't. My Lr catalog has about 20k photos 🙂

dj_paige

Legend

Are you applying a preset at Import? These would be "changes" that should be written to XMP (if the option is checked).

alxb49009547Author

Known Participant

Nope, nothing applied at import. I haven't changed any setting, and it was behaving normally until the last update.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded