Correction: the versions of ACR (and corresponding PS) where the XMP settings are not being read are version 10.0 / process version 10.0 and any and all earlier versions.
1 person found this helpful
Could you please post a screenshot taken of the file in Photoshop at View > 100% and with the pertinent Panels (Layers, Channels, Options Bar, …) visible?
Well, those screenshots are clipped to be fairly close to useless, but according to the Smart Object’s icon in the Photoshop Layers Panel that’s an embedded Smart Object so it has no connection to an external file and what is open in Lightroom I can’t tell.
Edit: Sorry, I had misunderstood the issue … but the screenshots should still include all pertinent elements.
2 people found this helpful
I've just tried here embedding a smart object containing a Camera Raw file processed to black and white in 2016 using a previous version of camera raw (whatever was current in 2016)
Double clicking the SO opens the current version of camera raw (10.3) with those old settings and profile intact i.e. still B&W
I added smart filters to see if that made any difference - it did not.
I am using PS 19.1.4 and Camera Raw 10.3 on Windows 10 so it would be good if someone using a Mac could replicate the same test.
Since I'm having problems with the color files as well and the issue is not repeatable by others (so far), It sounds like time to uninstall and reinstall....
Thanks davescm for trying to replicate.
1 person found this helpful
Probably no use but what happens when you use Layer > Smart Objects > Export Contents?
Is the resulting file missing the RAW adjustments, too?
I reinstalled both Bridge and PS (and ACR by default). Unfortunately the same behavior persists. Exporting the contents as c.pfaffenbichler suggested results in what appears to be the original NEF file with raw defaults since there is no associated XMP file.
I changed the Camera Raw Default settings (first 2) and turned off the graphics processor as well without any changes in behavior.
Is there any utility that can look at a PSD file and analyze whether it is damaged and how? I've got a whole bunch of these.... (thousands)
In saving my various presets and actions for another reinstall, this time initializing all settings, I found some strangeness as to how PS was working.
I'm chasing down the possibility that PS got confused during its installation. Using Sierra, I updated to PS 19.1.3 . After doing some testing, a few days later I upgraded to High Sierra in a new partition, keeping the original Sierra partition. I used Time Machine to load the old Sierra system into the new partition and then upgraded there to High Sierra.
New actions that I have created since then were being still saved to the old Sierra partition. Somehow PS is accessing some old stuff.
I plan on deleting my user library Adobe Application Support files in both partitions and reinstalling completely fresh to see what happens.
Just a stab in the dark: Have you tried foregoing the XMP files by changing the »Save image settings in« setting?
The issue is with the old PSD files. Once a current PSD file is saved, it is being interpreted correctly as a B&W.
In any event, Even with a clean install, having deleted all Adobe products and system and user Library entries along with Plist files the problem did not go away.
However there seems to be an issue apparent with ACR and/or the interface between PS and ACR. I tried a number of install combinations.
Unfortunately when installing older versions of PS (in this case V19.0), the current version of ACR is installed (V10.3.0.933). This combination exhibited the same issue where editing the smart object made the color version available.
However installing the current version of PS (V10.1.4) and an older version of ACR (I had V22.214.171.1240) editing the smart object made the correct B&W image available.
As soon as the current ACR was installed, the smart object went back to making the color version available.
I looked at the Camera Raw scripts, but could not discern any issues.
Not sure why others are not able to replicate this issue, but to me it appears there is a problem with the current version of ACR and older PSD files with smart objects.