Copy link to clipboard
Copied
I print for a living. Photos and fine art. The majority of customers provide files in sRGB unfortunately. Adobe RGB and ProPhoto RGB are my working spaces and until recently nothing changes when I convert the files upon import. But the last couple updates everything changes. When you convert an sRGB image to Adobe RGB it should look the same. Converting it is essentially pointless but I like keeping everything standard. But now converting makes some random files look really off. The same files look totally fine in LR Classic. And in Apple Preview. And Qimage One prints them fine. But opening them in PS to crop or manipulate them tweaks them out even if I dont actually convert. Any one else having these problems?
Running Mac Sonoma 14.2.1 and the lates PS.
Copy link to clipboard
Copied
@D Fosse when facing this type of problem, it is the first one that comes to mind.
"But opening them in PS to crop or manipulate them tweaks them out even if I dont actually convert"
It seems Photoshop may be applying changes to a photo automatically. This could be due to the File > Scripts > Script Events Manager setting. If 'Enable Events' is checked, simply uncheck it.
Copy link to clipboard
Copied
Do all the incoming files have an embedded profile? It sounds like they may not.
Policies for handling untagged files varies a lot from application to application. Photoshop will assign the working space and treat the file as such, including for conversions.
This is the simple way to keep track:
Copy link to clipboard
Copied
Oh, and one more thing: you cannot have policies set to "convert when opening". That's precisely when this can happen. It needs to be "preserve embedded profiles".
Copy link to clipboard
Copied
I have it set to prompt me and no matter what selection I choose to use the embedded profile, to convert, whatever I do it's still screws the colors up.
Copy link to clipboard
Copied
It seems like you're encountering inconsistencies in color rendering when converting sRGB images to Adobe RGB in the latest updates of Photoshop. This issue isn't isolated, as some files appear distorted upon manipulation, despite displaying correctly in other software like Lightroom Classic and Apple Preview. Have you checked for any color profile conflicts or software-specific settings that might be causing this discrepancy?
Copy link to clipboard
Copied
But the question was, is there an embedded profile? If not, it may be wrong whatever you choose.
That's why the status bar setting that I showed is much more effective than any of the warning dialogs. You spot untagged files right away and can decide what profile seems to fit best.
Copy link to clipboard
Copied
So I tried turning off the auto convert profile. I opened the file and was still prompted with a message saying its embedded profile is different than my working space. I chose to keep it with its embedded profile. The prompt said that was sRGB. However when the file opened, its marked as "untagged RGB" in the lower left. The image still looks WAY off. Im enclosing a screenshot of the image in PS next to the same image in Apple Preview. The Apple Preview version (right) is how its supposed to look. This happened with all three files from this customer, all scans from different scanners.
Copy link to clipboard
Copied
This is how a ProPhoto RGB image looks if you assign Adobe RGB or Display P3 which is very similar.
What I think happened here is that the scanner profiles are non-standard and get thrown out in other applications because they're not written to correct icc spec. That's not uncommon.
I suspect the left (saturated) version is the correct one, but you should go back and confirm that. Ask them to resave the file with a good standard profile embedded (not a scanner profile).
Copy link to clipboard
Copied
The same thing happened with a few images last week from a different customer. Those were not scans but sRGB files created in Photoshop, but I don't think they embedded the profile when exporting. In this case, the unsaturated image was accurate as told by the customer. Same thing with the images last week the saturation was somehow jacked to 1,000. But Apple Preview isnt doing this when I open it there, so those have been my references in both cases. When I converted this untagged horse image to sRGB it looked better, and more how the customer wanted.
I guess I'm also confused because I was under the impression that files converted "up" would look the same. So if I got an image from LR where I store my own photos, and converted it from Pro Photo in LR to Adobe RGB in PS, then BACK to Pro Photo in PS (just for testing purposes) the photo would remain the same. That basically the gamut could not be expanded as the data was lost when I converted it down to Adobe.
I feel like for now my practice should be converting to sRGB when im sent an untagged image as thats most likely what my customers are used to. People who are more advanced and work with thier own photos or art generally send me files with embedded profiles and this isnt an issue.
Copy link to clipboard
Copied
This whole thing boils down to a valid profile being embedded. Whether the profile is bad or missing amounts to the same thing: all bets are off and you don't know what it's supposed to look like. It can have too much or too little saturation depending - you just don't know.
I'd recommend to just turn off all the warning dialogs. Trust what it says in the status bar.
Copy link to clipboard
Copied
So if I turn off all warning and it does NOT have a profile embedded, it will say "untagged" correct? And if so you are advising I do NOT convert it to any profile at all prior to printing? For what its worth I don't use Photoshop to print only for image adjustments.
Copy link to clipboard
Copied
Yes. If it says "untagged", don't convert. Find the right profile and assign that first.
The problem, of course, is that you don't know what the right profile is. Sometimes you can make a good educated guess simply based on what looks good and "natural", but basically you have no way to know for certain. So then you need to go back and ask.
With your unicorn, the left version looks best. The purple sky on the right can't be intended. But also - those purples are very typical of a ProPhoto image displayed in one of the smaller color spaces like Adobe RGB or sRGB. So that kind of looked like a smoking gun to me.
Copy link to clipboard
Copied
BTW I very much appreciate your time..
Copy link to clipboard
Copied
Did you get this resolved? I am having the same problem, and it is very frustrating!
Copy link to clipboard
Copied
Same problem as what?
Is there an embedded color profile in your file?
Copy link to clipboard
Copied
I am having the same problem!
Copy link to clipboard
Copied
@glness we need to know more, what's the source profile, what's the destination profile, how is the monitor display calibrated?
Please ad screenshots inline using the image icon you see above the text window here
I hope this helps neil barstow, colourmanagement net - adobe forum volunteer - co-author: 'getting colour right' google me "neil barstow colourmanagement" for lots of free articles on colour management Help others by clicking "Correct Answer" if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for usefuI hope this helps
neil barstow, colourmanagement net - adobe forum volunteer - co-author: 'getting colour right'
google me "neil barstow colourmanagement" for lots of free articles on colour management
Help others by clicking "Correct Answer" if the question is answered.
Found the answer elsewhere? Share it here. "Upvote" is for useful posts.