Explore related tutorials & articles
50
Replies
So perhaps therein lies the issue Dave. How are you seeing that 6701.jpg (our image) is embedded with the Adobe 1998 colour space? When I open it on our systems it shows by all accounts that the profile and working space is sRGB.
To see correctly:
If using a high gamut monitor you need to work with it calibrated to something (I don't think it neecessary needs to be sRGB, Photoshop allows each file to have its own profile, as long you respect the incoming file's profile you should be good, since sRGB has less gamut than most other RGB).
Delivery:
Like others said, all images must be shared with sRGB profile embedded, if working in something else like Adobe RGB it needs to be converted to sRGB.
Sorry no. All that is required for any and all RGB Working Space is an embedded profile defining that color space. And of course, a color managed application. Without color management, sRGB is an utterly meaninless concept. Ditto for any other color space. With color management, all color spaces in a color managed app will preview 'correctly' no matter the gamut of the display. A display profile is equally needed, one that defines that device's behavior. The answer isn't sRGB. The answer is tagged RGB and color managed browsers or applications as explained here:
sRGB urban legend & myths Part 2
In this 17 minute video, I'll discuss some more sRGB misinformation and cover:
When to use sRGB and what to expect on the web and mobile devices
How sRGB doesn't insure a visual match without color management, how to check
The downsides of an all sRGB workflow
sRGB's color gamut vs. "professional" output devices
The future of sRGB and wide gamut display technology
Photo print labs that demand sRGB for output
High resolution: http://digitaldog.net/files/sRGBMythsPart2.mp4
Low resolution on YouTube: https://www.youtube.com/watch?v=WyvVUL1gWVs
Proof to Monitor RGB turns all color management off. Everything you describe is perfectly normal and expected. There is nothing wrong here!
With a wide gamut monitor, you must have full color management at all times. No exceptions! That's the deal you accept when you buy one of these units. If you have applications on your system that don't support full color management - you can't use them anymore. Find color managed alternatives instead.
If sRGB displays oversaturated, the color management chain is broken. Either because the application doesn't do it at all, or because the document doesn't have an embedded profile (or because the profile is nulled out like in Proof to Monitor RGB).
(but i really don't think it is necessary if the photos are in sRGB, which is the standard profile on the Internet)
No, you misunderstand. The internet doesn't "use" sRGB or even know what it is. Traditional monitors were reasonably close to sRGB natively, so if you sent them sRGB data it would look roughly right even without any color management. That's why it was/is the commonly used standard. A wide gamut monitor is not close to sRGB natively, so that no longer applies.
All monitors are different and you always need color management for accurate reproduction. Wide gamut monitors are just more different, to the point where these things become very obvious. Previously you could often get away with ignoring it.
Now, I just can't find where the color management chain is broken here.
By @aleksandarr
If you open the image in Photoshop and all Color Settings are left at default, that's your reference for how it should look. That's the correct version.
One more thing: when you run your calibrator, don't do anything. Set your white point and other parameters, obviously, but when the software is finished, that's it. Don't do anything. I say this because so many believe that they must now "use" this profile in various ways, like set it as working RGB and so on. Don't do that, that's not what it's for. The profile is automatically set up at system level, and Photoshop will find it on its own.
As Dave points out, all major web browsers today are fully color managed and should display identically to Photoshop. Windows "Photos" is also color managed now and will match Photoshop.
If color managed applications don't display identically, that's a sign that the profile is bad/defective/not written correctly to icc spec. A bad profile can affect applications differently - it can work in one but fail in another.
It appears, from reading this and other forums, that Chrome/Edge color management sometimes breaks for whatever reason. It just seems to stop working, don't know why. But that's the main reason I still use Firefox. It has been extremely reliable and always displays correctly on my wide gamut monitors (provided it's set to color management mode 1).
So, why it is oversaturated in Chrome and Edge (i also tried different things in Flags - to force Edge to consider my photo as srgb profiled, also tried other options there - no luck!)
And, even more important, why windows desktop wallpaper also shows it as oversaturated?
I'm seriously FREAKING OUT now! 🙂
By @aleksandarr
Why? Simple: they are either not color-managed or set up properly for color management like your other applications. If they were, they would match. Windows wallpaper, not surprising.
Well, both of those references you mention are basic, and do not adress the question of - why windows is not properly showing photos, and is behaving just like other apps (besides one I can point to CMS)
And, still, my monitor should be able to show precisely anything that does not go out of its own boundaries when it comes to color system.
By @aleksandarr
The entire macOS is color managed.
The entire Windows OS isn't.
If you have a mismatch from color managed app's, the other app isn't color managed or your display profile or path is corrupted.
That's the entire goal of color management. Something on your end is broken with Windows Wallpaper and two browsers. The other products are not.
AdChoices
