Author Topic: xmp files generated by lightroom that are not read by PMP  (Read 184 times)

Offline Alberto

  • Newcomer
  • *
  • Posts: 8
    • View Profile
xmp files generated by lightroom that are not read by PMP
« on: June 03, 2025, 10:35:33 AM »
In some cases, especially when a .jpg file is exported from Photoshop and then changes are made to the metadata (title or other) on Lightroom, a .xmp file is generated
that is completely ignored by Photomechanic and in addition a thumbnail is generated for the xmp file. This behavior in the iteration between Photomechanic and Lightroom represents a problem. How can it be remedied? Is there some setting to activate? Thanks a lot

Offline ahoward

  • Camera Bits Staff
  • Uber Member
  • *****
  • Posts: 1117
    • View Profile
Re: xmp files generated by lightroom that are not read by PMP
« Reply #1 on: June 03, 2025, 05:04:06 PM »
Photo Mechanic has never recognized XMP sidecar files (or additional independent thumbnail files) for JPEGs, so whatever behavior has changed must be within Lightroom, though I am not aware of any situation where Lightroom will create an XMP sidecar for JPEGs. It sounds like getting Lightroom to write the metadata into the JPEGs would solve the issue, but I don't know what to suggest to change it to do that, so this might be a question for Adobe.

On the other hand, if it's not reading XMP files for RAW files, please show an example of that (preferably with screenshots or a screen recording).

Offline Alberto

  • Newcomer
  • *
  • Posts: 8
    • View Profile
Re: xmp files generated by lightroom that are not read by PMP
« Reply #2 on: June 04, 2025, 01:38:35 AM »
I tried to look into the problem further and this seems to be the answer to this problem. Can it be solved somehow?
According to this help page, (https://helpx.adobe.com/photoshop/using/content-credentials.html) "Adobe automatically applies Content Credentials to assets generated with Adobe Firefly features, such as Generative Fill in Photoshop", regardless of your Photoshop settings.
Because the JPEG contains content credentials, saving metadata into the file itself would invalidate the digital signatures on those credentials. So LR saves the updated metadata to a .xmp sidecar.  Given Adobe's policy about AI "transparency" and adding credentials automatically, I doubt that LR would ever provide an option to overwrite existing Firefly credentials.
Thanks a lot

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 25323
    • View Profile
    • Camera Bits, Inc.
Re: xmp files generated by lightroom that are not read by PMP
« Reply #3 on: June 05, 2025, 09:54:00 AM »
Please zip up a JPEG and XMP file and post it here.  Use the 'Attachments and other options' link when you're composing your reply to this message and there you'll be able to upload your ZIP file.

Thanks,

-Kirk

Offline Alberto

  • Newcomer
  • *
  • Posts: 8
    • View Profile
Re: xmp files generated by lightroom that are not read by PMP
« Reply #4 on: June 05, 2025, 03:49:12 PM »
Hi Kirk,
I'm sending you the jpg and the xmp. In the meantime I've done further tests and it seems that today the problem with photos modified with generative ai no longer occurs. The photos that generate the problem are processing from a few months ago on which I had done some tests with the ai. The one I'm sending you is one of those and I managed to reproduce the problem by performing these steps.
Opening the photo in photoshop
Exporting the jpg
Importing the jpg into lightroom (and up to this point the xmp didn't exist)
adding a class color in lightroom
and here the xmp file was created.
To be precise, on the other photos where the problem occurred, metadata had been added by PM so in these situations I really think it's enough to update any data.
Thanks