Skip to main content
H
Hadmut Danisch
Participating Frequently
May 22, 2011
Open for Voting

P: Include additional metadata in XMP (flags, collections, VC's, etc.)

  • May 22, 2011
  • 118 replies
  • 2526 views

Hi,

when letting Lightroom write all the picture settings to a xmp file, both the stacking and the collection settings are missing.

Basically, I'd expect to find just every work done about the picture in the xmp file (e.g. for use with other tools. If I put several pictures in collection, I'd like to use that information and the order of the pictures from other programs.)

Even worse, when making a virtual copy of a picture, it's settings do not appear anywhere in an xmp file.

regards

118 replies

A
AndyWizz
Inspiring
April 27, 2020
Photoshop should take the smart object as a basis, which is 4000px x ?
I just opened the extension Generator Configurator and switched my settings back to the origin. Which solved the problem for smart objects as .psd
After so many years these Generator-Settings should get in the app plus .webp for windows.
I needed these settings to embed .icc
A
AndyWizz
Inspiring
April 27, 2020
in your example, the image has been scaled down significantly, so it looks as expected.
A
AndyWizz
Inspiring
April 27, 2020
Four years later and still no fix!
In CC2020, 21.1.2 generator still goes blurry (or again) at 200% with smart objects, even when a psd is inside. Here is my proof
NetPixel Studio
NetPixel Studio
Known Participant
July 11, 2019
Actually, this is what I'm doing before removing photos from catalog for backup purposes. Keywords like _flag_, _reject_ do the job.
L
Lumigraphics
Legend
July 11, 2019
You could also use keywords. Flagged and reject. Lots of software reads keywords and you can search and filter for them. Keywords are written to most graphic file formats, not just XMP sidecars.

Bottom line, since you know this desired feature doesn't exist, it might be best to adjust your workflow to fit.
NetPixel Studio
NetPixel Studio
Known Participant
July 11, 2019
Not, that's the wrong way. Export as catalog is cumbersome, heavy and inappropriate. Not saving the flags in the .xmp is a bug.
NetPixel Studio
NetPixel Studio
Known Participant
July 11, 2019
This is the problem: flags aren't stored in XMP. Regardless of one what would do with the files/catalog/etc., flags should be stored in the XMP.
Another way of losing your work is to backup the .cr2 files with .xmp files, sadly, when importing back the .cr2 files in another catalog (that is created for the backup drive), the flags are gone.
JohanElzenga
Community Expert
JohanElzengaCommunity Expert
Community Expert
July 10, 2019
The main purpose is to transfer raw develop settings and other metadata between different applications. Many applications can read metadata like keywords, only Adobe applications can fully read the develop settings written by other Adobe apps.
-- Johan W. Elzenga
Victoria Bampton LR Queen
Community Expert
Victoria Bampton LR QueenCommunity Expert
Community Expert
July 10, 2019
It's essentially for cross-app compatibility, not just within Adobe but across a multitude of programs. https://www.adobe.com/products/xmp.html
Victoria - The Lightroom Queen
F
FeedbackCommunityMember
Inspiring
July 10, 2019
I do have a broader question: what is the purpose of an XMP file? 
Also, until Adobe doesn't save flags into the XMP, I've been using the "reg" colour label and/or (1 *) as my "rejection" flag when I need that information recorded in my XMPs for use in Bridge.
Show more replies
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices