- This topic has 32 replies, 15 voices, and was last updated 1 year, 4 months ago by
.
-
Posts
-
1. Calibration loading and profile installation
Calibration loading may stop working. This affects both the Windows-internal calibration loader as well as any 3rd party calibration loaders (including DisplayCAL profile loader), applications like f.lux, and others that try to use the Windows SetDeviceGammaRamp API. Profile installation (which sets initial calibration upon installation) may also not be possible.
To resolve these problems, please install KB4501375 (released June 27, 2019, OS build 18362.207), offered via Windows Update (you may have to manually check for updates and then manually select to install the update under “Additional Updates”).
Relevant KB4501375 fixes:
- Addresses an issue that may cause Night light, Color Management profiles, or gamma correction to stop working after shutting down a device.
In case this does not fix the issues completely, turn OFF “Fast Startup” in the “legacy” Windows control panel under “Hardware and Sound” -> “Power Options” -> “Choose what the power buttons do”.
2. Severe banding even with linear/identity (no) calibration, and/or severe color casts (pink/green/red/blue/yellow)
If you are observing severe banding (stripes) on gradients even when no calibration is active or severe color casts and posterization, install KB4505903 (released July 26, 2019, OS build 18362.267), offered via Windows Update (you may have to manually check for updates and then manually select to install the update under “Additional Updates”).
Relevant KB4505903 fixes:
- Addresses an issue that may display colors incorrectly when viewing an image on 10-bit display panels.
In case this does not fix the issue completely, disable the task “Calibration Loader” in the Windows 10 Task Scheduler under “Microsoft” -> “Windows” -> “WindowsColorSystem” (DisplayCAL 3.8.3 profile loader will try to do this automatically for you), and log out and back in. The log out and back in procedure may need to be repeated each time a display’s default associated profile is changed.
-
This topic was modified 4 years, 5 months ago by
. Reason: Added steps to disable Windows Calibration Loader
-
This topic was modified 4 years, 5 months ago by . Reason: Added more info for Windows 10 1903 banding issue
-
This topic was modified 4 years, 4 months ago by . Reason: Added KB4505903 info
-
This topic was modified 4 years, 4 months ago by . Reason: Amended KB4505903 info about incorrect color
Just wanted to report that disabling fast startup and the WindowsColorSystem task solves the issue on my system, but only with the latest Nvidia driver (430.86).
With older driver 419.xx I still have some banding near black, which does not occur on Win 10 1809.
Hi Florian, does this banding issue affect Color managed apps negatively (unpredictably) such as photoshop and Madvr (mpchc) ?
Do you recommend going back to older versions of windows or even windows 7 for more reliable Color ?
How do experts such as yourself setup their color environment for reliability and immunity towards anomalies such as these updates ?
Hi Florian, does this banding issue affect Color managed apps negatively (unpredictably) such as photoshop and Madvr (mpchc) ?
It affects the whole desktop.
Do you recommend going back to older versions of windows or even windows 7 for more reliable Color ?
Microsoft themselves recommend to not update to 1903 until issues are resolved with a future Windows 10 update. I wouldn’t go back to Windows 7 myself, MS will cease support (security updates) on 14 January 2020 (except for enterprise customers with a volume license, but they intend to charge for this extended support).
How do experts such as yourself setup their color environment for reliability and immunity towards anomalies such as these updates ?
I deal with them as they occur. I am also not usually updating right as a big update becomes available, but hold off until I get a clearer picture (reading forums, news articles) what the update might affect. I am currently using 1903 with the latest updates. As I do not often change profiles, the log out and back in requirement doesn’t bother me much.
Hi, I have the color banding issue on my system as well. Can you load an ICC profile without banding after applying the Task Scheduler fix?
Hi,
Does this issue affect calibration measurements? Bcs, my display calibration was done without the fix applied.
Can you load an ICC profile without banding after applying the Task Scheduler fix?
See above. Log out and back in is required after a profile change.
Does this issue affect calibration measurements?
Banding issue – yes, because it reduces the effective bit depth.
Thank you. It works for standard srgb profile but when I load another icc profile, I get banding again. It’s not the same vertical banding like the bug from Windows but I get a couple of hard lines towards the darks. Do you know what would be the cause? Do all icc profiles cause banding or is it possible for them to still display smooth gradients?
Thanks
Thank you. It works for standard srgb profile but when I load another icc profile, I get banding again. It’s not the same vertical banding like the bug from Windows
This sounds exactly like 2. above though.
Do all icc profiles cause banding or is it possible for them to still display smooth gradients?
It depends on the application that is used. On a purely 8-bit display path, some banding with nonlinear calibration is unavoidable if the graphics card doesn’t apply dithering. But apart from calibration-induced banding (which can be normal to some extent), there’s also the color management of applications that can introduce (additional) banding if it doesn’t do processing in high enough bit depth and doesn’t employ dithering.
For my system , solution number 2 removes vertical banding like this : https://www.eizoglobal.com/support/compatibility/software/problem_windows10_may_2019_update/index.html.
If the standard srgb profile was loaded in the first place. After the fix, I get a perfectly smooth gradient.
Now, If I apply another profile, I will get the same vertical banding as in the link. I then try solution number 2 which removes that kind of banding but does not make the gradient perfectly smooth like with the srb profile. I get a couple of hard lines here and there. I am just asking to understand if this is normal and if there’s a way of applying an icc profile with no banding at all. If that was possible even before the 1903 bug.
does not make the gradient perfectly smooth like with the srb profile
The sRGB profile does not contain any calibration.
I get a couple of hard lines here and there. I am just asking to understand if this is normal
Yes.
if there’s a way of applying an icc profile with no banding at all
Only if the graphics driver applies dithering.
Thank you for your help. I’m a bit new to color calibration and higher bit depth monitors in Windows. Do you know if, for example a geforce1050 Ti would apply dithering or I would have to go quadro for that? I am using a gaming laptop with an 8 bit display but still want to do photo editing and graphic work.
Do you know if, for example a geforce1050 Ti would apply dithering or I would have to go quadro for that?
It depends on the operating system, graphics driver, connection and display. No hard and fast rules. Dithering with nVidia is very hit and miss. See respective sticky thread how to try and force dithering.
In other news, the not graphics card vendor or dithering related severe banding (stripes) has been addressed by Microsoft with KB4505903, see first post.
With Windows 10 Update KB4512941 and the Nvidia Studio driver 430.86 (for a GTX1080 Ti), the problems persist on my system, and DisplayCal can’t install its profile, neither on a user account- nor on a system-wide level.
Here’s the log:
12:08:26,308 Loading calibration curves from file... 12:08:26,309 C:\Users\paragram\AppData\Roaming\dispcalGUI\storage\LCD #1 2019-09-08 23-06 ↲ ↳ 0.3127x 0.329y S XYZLUT\LCD #1 2019-09-08 23-06 0.3127x 0.329y S XYZLUT.icm 12:08:26,375 About to open dispwin object on the display 12:08:26,375 About to clear the calibration 12:08:26,375 About to set display to given calibration 12:08:26,377 Calibration set 12:08:26,377 About to destroy dispwin object 12:08:26,381 ...ok. 12:08:26,400 DisplayCAL-apply-profiles getcfg profile.load_on_login returned ↲ ↳ profile.load_on_login = 1 12:08:30,811 -------------------------------------------------------------------------------- 12:08:30,812 Install profile 12:08:30,904 -------------------------------------------------------------------------------- 12:08:30,904 Session log: LCD #1 2019-09-08 23-06 0.3127x 0.329y S XYZLUT 12:08:30,904 12:08:30,904 Working directory: 12:08:30,907 c:\ 12:08:30,907 users\ 12:08:30,907 paragram\ 12:08:30,908 appdata\ 12:08:30,908 local\ 12:08:30,910 temp\ 12:08:30,910 DisplayCAL-osltll\ 12:08:30,911 12:08:30,911 Command line: 12:08:30,913 C:\Users\paragram\AppData\Roaming\dispcalGUI\dl\Argyll_V2.1.1\bin\dispwin.exe 12:08:30,914 -v 12:08:30,914 -d1 12:08:30,914 -c 12:08:30,914 -I 12:08:30,915 "LCD #1 2019-09-08 23-06 0.3127x 0.329y S XYZLUT.icm" 12:08:30,917 12:08:31,029 About to open dispwin object on the display 12:08:31,029 About to clear the calibration 12:08:31,029 About to install 'LCD #1 2019-09-08 23-06 0.3127x 0.329y S XYZLUT.icm' as ↲ ↳ display's default profile 12:08:31,029 Dispwin: Error - Failed to install profile 'LCD #1 2019-09-08 23-06 0.3127x ↲ ↳ 0.329y S XYZLUT.icm'! 12:08:31,059 ┌------------------------------------------------------------------------------┐ 12:08:31,059 │ The profile could not be installed/activated. │ 12:08:31,061 └------------------------------------------------------------------------------┘
