- This topic has 81 replies, 13 voices, and was last updated 5 months ago by
.
-
Posts
-
When I disable Auto Colour Management on Win. 11 24h2 , Nvidia GPU system, my colours are not colour managed (oversaturated) in Chrome, VLC and Davinci Resolve, but Edge and Photoshop are showing them properly.
I don´t know anymore what is happening, and I need this to work properly for my job. Sorry for spamming, I just spent too much time on it and don´t know what to do to make it work like before.I don´t want to clip colours to just SRGB, and I have tried MHC2Gen, but it didn´t solve this problem for me.
Just a heads up, novideo_srgb can clip to other color spaces like P3, Adobe RGB and BT.2020. But, for color-critical work I would stick to DisplayCal’s profile loader and make sure Photoshops color management engine is set up properly. Photoshop is more refined with mapping black point offsets and such, a solution like novideo_srgb won’t be as advanced. Skip other solutions like ACM or novideo_srgb. Add a second monitor for non-color critical work, you can clip the second monitor to sRGB.
If you mean without having to limit the monitor’s gamut in hardware, then yes. You are still limiting the monitor’s gamut, though, that’s the point. And novideo_sRGB and ACM should do a similar job in that regard, it’s just that novideo_sRGB has more options and is easier to understand for most I think.
But, as MW points out, for color managed applications, obviously just use “full-blown” color management.
my colours are not colour managed (oversaturated) in Chrome, VLC and Davinci Resolve, but Edge and Photoshop are showing them properly.
You might need to enable color management in Chrome, but it should work (I don’t really have much experience with Chrome in regards to color-management, I use Vivaldi, but both are based on Chromium and so is Edge, so). For VLC, you’d probably need a LUT to have accurate colors, and certainly for Resolve.
Edge and certainly Photoshop are color managed, so even if you disable ACM, they will follow your monitor’s color profile as long as you have one installed/enabled. Turning off ACM doesn’t mean turning off color management entirely.
Remember that at least in past W11 editions, I do not remember if 23H2 o4 24H2, ACM uses EDID info, not profile info to extract “display primaries in its current state”.
So any attempt to use a widegamut in an OSD preset/HW cal different than native gamut is likely to fail.IMHO is a broken feature from start.
It’s easier to live in W10 or W11 with ACM off, oversaturated colors for non color managed apps, and use color manageds apps for most of your daily tasks:
-color managed browsers: Firefox, edge, maybe chrome and opera
-color managed vide players : madVR compatible, mpv variants
-color managed image viewers, like classic W7 viewer that can be enabled with a registry entry
-color managed editors like adobe
-color managed video editors, like Adobe (out of teh box) or Resolve (LUT3D)
and the missing part here are:
-games,
-MS office or equivalent
-coding/programing.
For those 3 tasks is easier to rely on monitor vendor tools to switch between OSD presets /HW calibration slot + (optional) displaycal tray app to load a custom grey calibration for them, or to rely on novideo_sRGB / AMD.
Try to find a way to apply these “limited SRGB mode” with a few mose click and live with it until MS fix this mess.Honestly, it’s hard to swallow how broken Windows still is when it comes to proper color management. After all these years, it’s still a patchwork of half-working systems and inconsistent behavior between updates.
And the irony is that Apple actually got this right ages ago, but their GPU situation is such a joke that anyone relying on serious graphics hardware is basically forced to stay on Windows and deal with this mess.
It’s the classic case of choosing between a system that manages color correctly but lacks GPU horsepower and one that has powerful GPUs but treats color like an afterthought.
@Vincent Yeah I’m trying to use the same way as you describing and I was using it before and it worked.
I’m not exactly sure when it stopped working I just think it was when I did update to 24h2
I did clean reinstall to 25h2 and now even Microsoft Edge Colour management is broken, which worked before.
That’s why ACM is not recommended, it’s too new and subject to change.
You may consider a conditional novideo_srgb and DisplayCal loader setup:
-Set up novideo_srgb to use a DisplayCal icm profile. In DisplayCal loader set the display profile to a generic sRGB profile.
-When you are using professional content editing apps, uncheck “clamped” in novideo_srgb and set the display profile in DisplayCal loader to a DisplayCal icm profile.
To make this all work smoothly you want to profile with “tone curve:as measured” in DisplayCal.But I want to use the full gamut and leave it to the “professional” software to colour manage it. Colour management is broken in those pro apps right now.
I´m probably writing this in the wrong thread tho.
I’m using W11 25H2 and Adobe suite, Firefox (configured to render untagged as sRGB) and Edge are working properly. Although (even in W10) sometimes when you open Edge it does not (but very uncommon issue), closing edge and opening it again solved the issue.
Are your sure you are using the “simplest” and more compatible ICC type? single curve + matrix + BPC.
But I want to use the full gamut and leave it to the “professional” software to colour manage it. Colour management is broken in those pro apps right now.
I´m probably writing this in the wrong thread tho.
Read my steps again because you are asking for something which is already provided: https://hub.displaycal.net/forums/reply/144948/
FYI ACM is an extension to “classic” windows color management. It was rolled out recently as an official feature, despite not being finalized, and despite not being broadly adopted by many professional apps. Feature stability is a requirement for professional app adoption and ACM lacks this. Hope this clears your confusion.
I’m using W11 25H2 and Adobe suite, Firefox (configured to render untagged as sRGB) and Edge are working properly. Although (even in W10) sometimes when you open Edge it does not (but very uncommon issue), closing edge and opening it again solved the issue.
Are your sure you are using the “simplest” and more compatible ICC type? single curve + matrix + BPC.
Thanks for the info, good to know that it can work on 25h2. Closing and reopening Edge didn´t help.
These are my settings; those should be all right, right?
But I want to use the full gamut and leave it to the “professional” software to colour manage it. Colour management is broken in those pro apps right now.
I´m probably writing this in the wrong thread tho.
Read my steps again because you are asking for something which is already provided: https://hub.displaycal.net/forums/reply/144948/
FYI ACM is an extension to “classic” windows color management. It was rolled out recently as an official feature, despite not being finalized, and despite not being broadly adopted by many professional apps. Feature stability is a requirement for professional app adoption and ACM lacks this. Hope this clears your confusion.
I´ve read it whole, but when I do this:
When you are using professional content editing apps, uncheck “clamped” in novideo_srgb and set the display profile in DisplayCal loader to a DisplayCal icm profile.”My professional content editing app’s colour management is not working for some reason, and that´s the thing I´m trying to solve. It used to work in the past.
I have ACM turned off btw.Still thx a lot for trying to help!
But I want to use the full gamut and leave it to the “professional” software to colour manage it. Colour management is broken in those pro apps right now.
I´m probably writing this in the wrong thread tho.
Read my steps again because you are asking for something which is already provided: https://hub.displaycal.net/forums/reply/144948/
FYI ACM is an extension to “classic” windows color management. It was rolled out recently as an official feature, despite not being finalized, and despite not being broadly adopted by many professional apps. Feature stability is a requirement for professional app adoption and ACM lacks this. Hope this clears your confusion.
I´ve read it whole, but when I do this:
When you are using professional content editing apps, uncheck “clamped” in novideo_srgb and set the display profile in DisplayCal loader to a DisplayCal icm profile.”My professional content editing app’s colour management is not working for some reason, and that´s the thing I´m trying to solve. It used to work in the past.
I have ACM turned off btw.Still thx a lot for trying to help!
Very good, this provides details about your issue that makes it easier to help. I suggest:
1. Upload your profile folder as a zip file here
2. Ensure that DisplayCal profile loader is started with windows. If not you can enable it by rerunning the Displaycal installation exe.Are your sure you are using the “simplest” and more compatible ICC type? single curve + matrix + BPC.
These are my settings; those should be all right, right?
No, as explained above, but Adobe suite should be able to use table (Xrite) / XYZLUT (ArgyllCMS) profiles. Browsers don’t like those.
If you want to limit to matrix profiles manually enable advanced options or if not doing that lower number of profiling patches.Also IDNK what you mean that color management is not working for some reason in Adobe Suite or others,
-if it means undersaturation (which would be linked novideSRGB or something like that with native gamut ICC profile as display profile in OS),
-or oversaturation which is linted to app not usig OS info about display profile or that OS has not assigned as default profile the profile that describes display in its current preset & config.
