Topic: Do changes to "Master" carry over to Virtual Copy (Read 5423 times)

wlemann · « **on:** February 10, 2014, 01:51:22 pm »

So here is the scenario:

If you crop and spot a file, then create a VC does that include the cropping and spotting or does the VC only apply to the underlying Raw image?

digitaldog · « **Reply #1 on:** February 10, 2014, 01:54:45 pm »

The VC should take on the attributes of the master prior to it's creation. If you want a VC that's untouched, you'd go back in History then make the VC.

wlemann · « **Reply #2 on:** February 10, 2014, 02:12:41 pm »

So that's good.
If I understand correctly, changes I want applied to all subsequent iterations, like spotting, can be done on the so called Master which now becomes the new Master and from which VC's can be made to do things from Basic adjustments to B+W conversions.
Do I have it correctly?

digitaldog · « **Reply #3 on:** February 10, 2014, 02:18:32 pm »

Quote from: wlemann on February 10, 2014, 02:12:41 pm

If I understand correctly, changes I want applied to all subsequent iterations, like spotting, can be done on the so called Master which now becomes the new Master and from which VC's can be made to do things from Basic adjustments to B+W conversions.
Do I have it correctly?

Yes. The VC is 'stored' in the database. The 'master' is the source raw. All the edits are of course in the database too. I point this out as often, I'll work on various VC's to get a feel for what I want, then I'll end up with a hero. Since I'm paranoid about backing everything up, I'll save the hero VC as a DNG. Those edits and another 'copy' of the raw data so to speak is now self contained. So think of the Master as just the first set of instructions for editing that are associated with the raw. Raw is raw, it's never really touched in Adobe's products. The raw plus the instructions (sidecar, within the database) are what could be rendered to an image (TIFF, JPEG etc).

wlemann · « **Reply #4 on:** February 10, 2014, 02:50:07 pm »

Therein lies the question. Is this a hub and spoke model or a daisy chain model.
If the former, then the spotted image is really just the Raw data plus the Spotting "instructions" in which case it would seem that the VC is the Raw data only w/o the Spotting "instructions".
If the latter, then the spotted image, admittedly still the Raw plus the accompanying Spotting "instructions" becomes the basis for the VC.
Is my thinking correct or off base?

digitaldog · « **Reply #5 on:** February 10, 2014, 02:52:57 pm »

Quote from: wlemann on February 10, 2014, 02:50:07 pm

Therein lies the question. Is this a hub and spoke model or a daisy chain model.
If the former, then the spotted image is really just the Raw data plus the Spotting "instructions" in which case it would seem that the VC is the Raw data only w/o the Spotting "instructions".
If the latter, then the spotted image, admittedly still the Raw plus the accompanying Spotting "instructions" becomes the basis for the VC.
Is my thinking correct or off base?

The raw is just the raw. It is read only. The instructions are just the instructions which can be used with the raw to produce a final rendered image.

wlemann · « **Reply #6 on:** February 10, 2014, 03:22:02 pm »

So maybe this is a better way to frame the question. Is it true that, until you have rendered a file to TIFF etc., the instructions are just one set of instructions. But if that is true how can you have multiple versions--one more contrasty, one B+W etc?

digitaldog · « **Reply #7 on:** February 10, 2014, 03:25:06 pm »

Quote from: wlemann on February 10, 2014, 03:22:02 pm

So maybe this is a better way to frame the question. Is it true that, until you have rendered a file to TIFF etc., the instructions are just one set of instructions. But if that is true how can you have multiple versions--one more contrasty, one B+W etc?

There can be multiple instructions. VC 1 is one set, VC 2 is another. Master as you call it is the first set. You select VC 2 and ask for a TIFF. LR takes those specific instructions and the raw and renders that to produce your TIFF.

Tony Jay · « **Reply #8 on:** February 10, 2014, 04:43:36 pm »

Wieman, Andrew has given a pretty good synopsis.

To emphasize, one can create as many virtual copies from a single RAW image as one wants.
A virtual copy is an extra copy of develop instructions that are separate from the the develop instructions of the original image.

When a virtual copy is created it exactly copies the develop instructions that are extant at the time of its creation - and so, to start with it will look exactly the same as the image it was derived from.

However, any changes subsequently made to the virtual copy are confined to that virtual copy and any changes subsequently made to the original RAW image will be confined to that image and will not be reflected in the virtual copy.

Tony Jay

aduke · « **Reply #9 on:** February 10, 2014, 05:03:13 pm »

One additional point, you can use the Reset button in Develop mode to reset the changes to the VC. This removes all settings you've applied since import, back to where you first saw it, after the default settings were applied.

Alan

davidedric · « **Reply #10 on:** February 10, 2014, 05:56:05 pm »

Yes, but...

The VC must "contain" all the edits leading up to it, but you can't see or use them. In other words the VC appears similar to a fresh import, with the earlier edit steps baked in. Cannot see why this is desirable. Can anyone suggest why it is implemented in this way?

digitaldog · « **Reply #11 on:** February 10, 2014, 06:28:25 pm »

Quote from: davidedric on February 10, 2014, 05:56:05 pm

Yes, but...

The VC must "contain" all the edits leading up to it, but you can't see or use them. In other words the VC appears similar to a fresh import, with the earlier edit steps baked in. Cannot see why this is desirable. Can anyone suggest why it is implemented in this way?

Again, you can have it both ways depending on when/where in History you ask for the VC. The VC now draws a line in the sand by not showing you the previous history, that's all in the previous Master/VC. I suppose there could be an option to either work as it does now, OR make a VC that has all the history in it, but it might confuse a lot of users and as I said, you can have it such that the VC reflects where in the previous iteration you want to draw a line in the sand and make a new iteration. As such, why is the previous history important?

There is no duplicate command. But you could force the issue and easily with a DNG. Then you'd have the "VC" (sort of, it's got the original raw data overhead) with the history as well.

Tony Jay · « **Reply #12 on:** February 10, 2014, 06:52:52 pm »

Quote from: davidedric on February 10, 2014, 05:56:05 pm

Yes, but...

The VC must "contain" all the edits leading up to it, but you can't see or use them. In other words the VC appears similar to a fresh import, with the earlier edit steps baked in. Cannot see why this is desirable. Can anyone suggest why it is implemented in this way?

It isn't a bad question - but I think Adobe should be the one's to answer the question.

For what it is worth I have never seen the lack of a Develop history as a big problem with a newly created VC.
I can still manipulate it any way I want to without "hurting" the image - obviously the the same parametric editing paradigm still applies.

Tony Jay

wolfnowl · « **Reply #13 on:** February 11, 2014, 01:56:42 am »

Also, if you end up with a VC that you like best of all, in the Library module you can go to Photo/Set Copy as Master.

Mike.

Schewe · « **Reply #14 on:** February 11, 2014, 02:05:01 am »

Or simply create a new Snapshot...which will be added not only to the VC (all VC's) but also to the original master. Really, if you are gonna use VC's, it behooves you to learn how to use them. Note: ACR is limited to only Snapshots–LR has both VC's but also Snapshots...

PhotoEcosse · « **Reply #15 on:** February 11, 2014, 05:32:46 am »

Quote from: davidedric on February 10, 2014, 05:56:05 pm

Yes, but...

The VC must "contain" all the edits leading up to it, but you can't see or use them. In other words the VC appears similar to a fresh import, with the earlier edit steps baked in.

That is simply incorrect.

If you process an image in Lightroom's Develop module and then make a Virtual Copy, the VC shows the Develop Module slider positions at the point where you created the VC. For example, if in your original edit you moved the Clarity slider to +40, then if you make a VC, it will start with the Clarity slider at +40. You can then adjust from that position as you wish.

Steve House · « **Reply #16 on:** February 11, 2014, 05:37:23 am »

If you make changes to the original image and make a VC, the VC inherits those changes. But if you subsequently GO BACK to the original and make further changes, those changes DO NOT automaticaly propagate to any already existing VCs. I think that was the OPs original question.

Tony Jay · « **Reply #17 on:** February 11, 2014, 05:49:07 am »

Quote from: Steve House on February 11, 2014, 05:37:23 am

If you make changes to the original image and make a VC, the VC inherits those changes. But if you subsequently GO BACK to the original and make further changes, those changes DO NOT automaticaly propagate to any already existing VCs. I think that was the OPs original question.

I thought I made that crystal clear in my post.
But there you go!

Tony Jay

wlemann · « **Reply #18 on:** February 11, 2014, 10:59:14 am »

Final summary; maybe:
RAW data, if this is "edited" without first making a VC, those edits will NOT appear in any subsequent VC's made from the RAW data.

If you want the first "edits", e.g. spotting to stick for subsequent VC's you first need to make a VC (#1) with the spotting edits. Subsequent VC's made from VC #1 will contain the spotting plus whatever, e.g., Hue VC #2 (with spotting) VC going back to VC #1 (with spotting edits) plus Tone Curve VC #3 (but without Hue). If you want spotting plus Tone Curve plus Contraast you take VC #3, make VC#4 and then make Contrast edits.

So how do you get spotting plus Hue plus Tone Curve plus Contrast?

davidedric · « **Reply #19 on:** February 11, 2014, 12:25:50 pm »

Quote

Yes, but...

The VC must "contain" all the edits leading up to it, but you can't see or use them. In other words the VC appears similar to a fresh import, with the earlier edit steps baked in.

That is simply incorrect.

If you process an image in Lightroom's Develop module and then make a Virtual Copy, the VC shows the Develop Module slider positions at the point where you created the VC. For example, if in your original edit you moved the Clarity slider to +40, then if you make a VC, it will start with the Clarity slider at +40. You can then adjust from that position as you wish.

True enough, but you could make much the same observation of the master copy.

It's no big deal, though it surprised when first I saw it. My reason for wanting it as an option is, if I think the current edit has started to wrong about "here" then I'll create a VC from that point in the history and carry on. I would prefer to be then working exactly as if I were working the original image. Just seems more logical, at least to me.

Dave

Author Topic: Do changes to "Master" carry over to Virtual Copy (Read 5423 times)