2 Messages
•
280 Points
Thu, Feb 23, 2017 11:48 PM
16
Lightroom: Virtual copy using a new xmp file
It would be great if the virtual copy can also be stored in an other side amp file like for instance DSC09009.xmp for the master and DSC09009-1.xmp for a virtual copy.
This way one could share the different develop setting and also be able to sync a folder previously 'developed'/treated with an other catalog.
I now they are some workaround with developments versions but is not practical.
Develop version are stored in the xmp but not the virtual copies
This way one could share the different develop setting and also be able to sync a folder previously 'developed'/treated with an other catalog.
I now they are some workaround with developments versions but is not practical.
Develop version are stored in the xmp but not the virtual copies
Ideas
•
Updated
3 years ago
15
3
16
Helpful Widget
How can we improve?
Tags
No tags available
Responses
jacob_hutson
16 Messages
•
330 Points
3 years ago
Surely the -1.xmp file can reference the original RAW file.
It would make archiving collections much easier as its wouldn't be reliant on the catalog any more.
0
phil_burton_7735307
83 Messages
•
1.6K Points
3 years ago
0
0
photographe
242 Messages
•
9.1K Points
3 years ago
Currently, the LR catalgue has the ability to export some but not all photo attribues via xmp (whether by sidecar or as part of a file).
Chief among the things that are not exported is Collections, but there are other items, such has virtual copies, history, publish services, certain metadata, and stacks (I am sure people can name others that I do not know about).
This makes it harder to share such things with other users and with Bridge; it also creates uncertainty. As a non-techy I never know what's in the catalogue and what's in the xmps.
I have started writing all collection info into keywords, which is time consuming and error-prone.
A way to export collection and VC information, at a minimum, would be great.
0
0