DagoImaging wrote in post #18514586
Nope, but that only works in PS if you open the image from Cam Raw as a smart object. It would be interesting to see numbers of how many people actually do that. I for one never do that. So if you use Cam Raw, make an edit and take the photo into PS after CR and then go back to CR after other adjustments, your CR sliders are all zeroed. This is true for CR or taking the image from LR.
I'm not sure how you are seeing that the ACR adjustments for the image are at zero, after editing a RAW in ACR, then moving to Ps, making edits in Ps and saving them as a PSD/TIFF with layers. I normally use Lr, and open in Ps from there, but I have some CR2's that are not in the catalogue, as they require preprocessing to DNG's for editing, so I tried a couple of those from Bridge via ACR.
All of the ACR edits made to the CR2 files are auto saved to the .xmp sidecar file. So the edits to the RAW are kept at that level. The same applies to opening a RAW image into Ps from Lr with the Edit in command. All the existing RAW file's edits are kept as is.
The PSD file is a new RGB file, and all of the visible image data is RGB. Yes you can open an RGB file in ACR, and there can be good reasons to do so. However since the saved file will be a new RGB file, you will start with the default settings for an RGB file if you do open it in ACR. The same applies to a new RGB file imported into Lr, which is what happens when you hit Save in Ps, after opening in Ps from Lr using the Edit in command.
So normally you keep the existing RAW edits in the RAW file, either stored in the Lr catalogue, or in xmp sidecar files, or in my case both, so that I can use both Lr and Bridge together. New images get a new set of defaults, existing images retain any existing edits, just as you would expect.
On the subject of opening the RAW in Ps as a Smart Object, that is how I have regularly opened images to Ps since I got my new system about 18 months ago. Yes it makes for a much larger file, but it does have some advantages though. One advantage is that it gives you the possibility of having multiple conversions of the same image, that you can see while using Bridge. It's nowhere close to as efficient as the Virtual Copies that you can use in Lr, and IMO Virtual Copies would be much easier to implement in Bridge than its effort at doing Smart Collections. The actual reason that I open as a Smart Object is that very often I will realise that I missed something at the RAW stage while editing in Ps, and this gives me a means to correct the problem, without the effort required to go back to the RAW editor, make the change, then get that new version into the existing RGB image as a layer. Of course the downside is that the corrections you do make to the Smart Object within the RGB file can't be propagated back to the original file. As I have got more into Smart Objects the more useful I have found them. Having flexibility built in is useful where you might need to make adjustments a few layers or steps back to balance later effects out.
Alan
)
