There's enough here to correct some of my mistaken beliefs, but if you look at my modified description of the problem, I don't think we've addressed it. The assigned color space for these images on my camera is Adobe RGB. I understand that for a RAW file, this isn't really "there", but ACR at least notices this preference and brings the image up with the image tagged as Adobe RGB in "Workflow Options". Then when the imiage is brought into Photoshop, it has AdobeRGB as the assigned space. Based on what you are telling me, this process is irrelevant. The problem is this: the colors shown onscreen in ACR differ from what is seen when the image is brought into Photoshop. (It also differes from Bridge). The difference between to two is similar to the difference between an AdobeRGB image when it is displayed in the correct color space and when it is displayed as sRGB. It doesn't sound like that kind of assignment issue is what is really going on here, but what is true is that colors onscreen in ACR aren't right. Changing the color space in "workflow options" doesn't change the way the colors appear in ACR. What matters is that when the image is opened into Photoshop, the images are far more vibrant (and to my eyes, correct, as the ACR display looks muted and sour). The bottom line is that something is affecting how ACR displays its colors since the 10.3 update: right now I don't see it as likely being a problem internal to ACR that I could fix by changing a setting, but rather a byproduct of 10.3 interacting with SpectraView or my video card in a way that is different than how Photoshop works with the calibration or the card. I'm inclined to rebuild my machine from scratch, test the Photoshop and ACR performance before I add monitor calibration. That could rule out that as an influence here. I might also look for another computer that has a different video card. Fortunately, my 10.2 ACR machine works fine.
... View more