Can Lightroom keep a virtual copy synced to the original's Develop settings except crop?
Asked 8/7/2015
3 views
2 answers
0
I use Lightroom virtual copies to make square thumbnail versions of photos. I'd like the thumbnail copy to automatically inherit any Develop changes made to the original image, while keeping its own crop. Is there any built-in way to keep one file or virtual copy permanently synced to another, or any practical workaround such as XMP sidecars?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
11y ago
2 Answers
1
My answer is based on ".XMP" files (sidecar files) and consists of 2 parts. I explain two potential solutions in the first part and explain the parameters to use in the second one.
Two solutions using XMP filesThis part explains 2 potential solutions, using :
- RAW and 2 XMP files
- TIFF and 1 XMP file
1) Using RAW and 2 XMPs
In theory, one solution may be to have 2 XMP files for each picture :
XMP "A" for the original picture (RAW -> image "A"). It should contain all the develop settings of your original picture. Once you are out of Lightroom, all editing software would have to make modification through this XMP file. For Photoshop and others, it mean that all "destructive" editions will have to overwrite the "original" picture (so the original at this point can't be RAW, it must be TIFF-like as you can't "photoshop" a RAW).
XMP "B" for the thumbnail associated to the original (image "A" -> image "B"). It should only contain information about the transformation from original to thumbnail (only cropping I guess).
With this setting, you could write a program to watch for change in the RAW original picture (unlikely to occur) or in the XMP "A" file. You probably need a database with the date of the last known change of the RAW and of the XMP "A". If such a change it's detected, then you use an Image development software to develop your original RAW with the setting of XMP "A" + XMP "B" to get your thumbnail.
Problems :
- I don't know any bash development software capable of using the proprietary XMP fields used by Lightroom (and its proprietary editing software). You can't use Lightroom development tools like any externally called program, so I guess you will need :
- a Lightroom plugin or some kind of Photoshop batch processing to get your developed original image (RAW -> image "A")
- a more basic tool to transform this image to a thumbnail (image "A" -> image "B").
- If you crop/rotate/resize your original image, you WILL have to change XMP "B".
2) Using TIFF and 1 XMP
As you are stuck with TIFF when using Photoshop, you can keep only the XMP "B" to get your thumbnail.
Use any way you want to get TIFF from your RAW and then make all the transformations you want to the TIFF (this TIFF is the result of RAW + XMP "A" in the case of a non destructive transformation). Now, you just have to look for TIFF changes. When one is detected, launch a third party program to automatically create a thumbnail based on a stored transformation. The transformation parameters (cropping,...) could be stored in the XMP format (=XMP "B") or in any compatible format if it is easier for the third party image processing program. Using ImageMagick (version >=v7), something like convert image_A.jpg -profile xmp:image_A2B.xmp image_B.jpg should do the trick (untested).
Cropping and rotating parameters of Lightroom XMP file are saved in the following format (those lines are added to the XMP file when cropping/rotating an image) :
crs:CropTop="0.3"
crs:CropLeft="0.4"
crs:CropBottom="0.9"
crs:CropRight="0.8"
crs:CropAngle="0"
crs:CropConstrainToWarp="0"
crs:HasCrop="True"
crs:AlreadyApplied="False"
The 4 first fields (crs:CropTop, crs:CropLeft, crs:CropBottom and crs:CropRight) are expressed in a fraction of the original image size, given from the top-left corner :
The field "crs:CropAngle" defined the rotation but it shouldn't concern you.
I Hope this help :)
Originally by user26456. Source · Licensed CC BY-SA 4.0
user26456
10y ago
0
Generated from our catalog & community — verify before relying on it.
Lightroom does not natively support a permanent live link between an original photo and a virtual copy where Develop changes stay synced but crop remains independent.
A possible workaround is based on XMP metadata, but it’s awkward and limited. In theory, you could separate editing data so one set of settings is shared and another holds the alternate crop/version. This is more feasible with files that can carry or use XMP metadata, but it is not a smooth Lightroom feature and would require careful external file handling.
In practice, Lightroom virtual copies are meant to be independent versions once created. If you change the original later, those changes are not automatically pushed to the copy. The usual workflow is to resync settings manually when needed, then reapply the different crop to the square version.
So the short answer is: no built-in permanent sync, and no simple robust third-party solution is indicated here. XMP-based approaches are theoretical workarounds rather than a clean Lightroom workflow.
Recommended products
UniqueBot
AI11y ago
Your Answer
Related Questions
How can I manage multiple Lightroom crops for different aspect ratios more efficiently?
How can I make a Lightroom Smart Collection for all virtual copies?
Can Lightroom save virtual copy develop settings to XMP sidecar files?
Do Lightroom virtual copies get saved in XMP sidecar files?
Can Lightroom publish to Flickr while I'm away if my originals are on a NAS?
