LIGHTROOM - "Create a REAL copy" ( vs. 'Create a Virtual copy')

  • 1
  • Idea
  • Updated 3 years ago
  • (Edited)
What about easily "convert" an image (or/and already a virtual copy) into, say, DNG, such as to appear right away next to the "original" (and be added into the "original folder") ?

I keep forgetting if this is easy
( i keep confused if it requiers steps such as 'export' and 'import'? - if this can be "scripted").

In other words;
one should be able to have a right-click : Create a REAL Copy (versus Virtual),
and such new files SHOULD INCLUDE the process history.. (is already 'so'?)

(Naturally that means the additional weight of a full new image-file each time - but why not; for when, amongst more then one virtual copy, one of them deserves becoming à file/version of its own.)
Photo of Niala

Niala

  • 74 Posts
  • 17 Reply Likes

Posted 3 years ago

  • 1
Photo of Rory Hill

Rory Hill

  • 242 Posts
  • 35 Reply Likes
Create an export preset, with image format set to Original or DNG. You can automatically add it to the same folder and even add it to a stack with the original.
Photo of Niala

Niala

  • 74 Posts
  • 17 Reply Likes
Thank You !
As I mentionned, I must have donne it in the past, but not gone through the important step to make it a preset and thus include it in my workflow..
Thank You again very much, now I will really implement it
(even search for those virtual copies that are edited and important to me, "finals" :-( and batch-create "real copies" of them..)
Photo of Rory Hill

Rory Hill

  • 242 Posts
  • 35 Reply Likes
You're welcome. Not sure I understand why you need new copies since that is the purpose of virtual copies...
Photo of Niala

Niala

  • 74 Posts
  • 17 Reply Likes
Am afraid of corrupt or mishandled catalogue -whereby integrity of the virtual copies, I feel, are more at risk.

I have long ago come into the habit of making extensively use of virtual copies, without (before) being concerned (conscient) of the fact that finalized virtual copies canot (naturally) exist as entities on my HD with their own XML sidcarfile (or incapsulated in DNG - which they are not, since they are virtual copies, vs. real copies). Of corse, catalogue backups remain good discipline..

Sometimes I now copy the results of all (best) elaborated editing made on a virtual version- back to over the master (sometimes doing first a snapshot of the stage the master was before synchronizing above it (but then there is no detailed history present -else then "synchronized").

I'm not talking about converting ALL virtual copies, but perhaps just the "best ones. (At least I'm gonna check what percentage this represents)
Photo of Rory Hill

Rory Hill

  • 242 Posts
  • 35 Reply Likes
If I understand correctly your concern is backup for your edits. I assume you have a backup strategy for your original raw files. Anyway this is the first time I've heard of anyone employing your strategy. Can't hurt!
Photo of john beardsworth

john beardsworth

  • 1041 Posts
  • 239 Reply Likes
Corrupt catalogues are rare, and your backup should be a backup of the catalogue.

Also, VCs are only one feature that doesn't get into the xmp sidecar - flags, assignment to collections, history steps, stacking, etc. xmp is meant for passing data to other apps, and is second rate backup.

However, just for the purpose you describe, look at the Snapshotter plugin which copies VC info to snapshots, which do save to xmp.