![]() Did a file comparison of both the RAW and the xmp files with the thumbdrive versions - XMP: no substantive differences (see below), RAW/.CR2 no file differences. Open original hard drive's RAW+xmp - still incorrectly renders. Desktop's Ps+ACR renders thumbdrive RAW+xmp version correctly! WTF. Then decided to have my desktop Ps open the RAW+xmp and TIFF files off the thumbdrive (i.e., open same exact files that the laptop opened, rather than the original hard drive versions). Just saw that laptop just installed a Windows 10 update, so retried experiment there and same result: correct Ps+ACR rendering of RAW+xmp. I am leaning toward removing and reinstalling my desktop's Photoshop and ACR, but I hesitate since I'd like to figure out what's going on before I brute-force fix it (it's the engineer in me). And I believe that I have also ruled out Lightroom as a factor. So, the big finding here is that my Laptop's Photoshop basically renders the RAW+xmp file correctly. Same results as above: So also going to ignore this version strangeness. Anyway, then performed same as above by opening RAW and TIFF versions. so updated laptop's Ps and it now reports same v20170425.r.252 圆4 version as before, so don't know what the update did. Laptop's Creative Cloud app then notified me that Photoshop needed updating, but not ACR.But I'm going to ignore this for the time being and focus on the fact that the laptop's ACR rendering is essentially correct, and assume therefore that there is something odd with my desktop Photoshop installation/configuration. RAW+xmp rendering looks correct to my discerning eye! When I compared it to Photoshop's TIFF file rendering, I saw an extremely small brightness difference in shadows and, sure enough, performing a difference comparison using layers & extreme curves enhancement showed some difference. Then copied RAW+xmp & TIFF "Export." image files to my laptop and opened using same v20170425.r.252 圆4 version of Photoshop.I then simply converted and opened image in Ps, and, sure enough, same rendering difference/error is there. as a result, fiile opens directly into Ps' ACR. Remove interface concerns between Lr & Ps by, within Lr, writing image's ACR settings to image's xmp sidecar file and then opened that RAW file using Photoshop's Open.I also double checked that correct monitor profile is being used (through Window's "Color Management") Although it seemed a long shot, I re-calibrated my monitor since other forum threads suggested doing that."Color Settings" in Photoshop has the 3 "Ask" boxes checked for missing and mismatched color profiles. Double checked that Lightroom's "Preferences/External Editing": exports to Photoshop in "ProPhotoRGB 16bits" Checked that my Photoshop default Color Space is the same.Turned off GPU acceleration in Lightroom & Photoshop.Running Windows 10, Creator's Edition 圆4 with all Microsoft updates applied.I'm at a loss why this is now happening.I have checked: That is, I can perform these 3 different ways of editing a RAW image in Photoshop and compare the 3 resulting Photoshop edit windows side-by-side - the "Edit in." and "Smart Object" versions will be exactly the same but wrong (usually too Cyan), with only the "Export." version's color correctly matching Lightroom's window. However, if I instead use Lightroom's "Export." to send the RAW file to Photoshop as either a PSD or a TIFF, the image opens in Ps with color that matches Lightroom's. All of a sudden, I am getting image color casts when I use Lightroom's "Edit in Photoshop CC 2017." or "Open as Smart Object" to open a RAW file in Photoshop CC 2017.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |