Displa圜AL has profiles with strongly tinted calibration in various hues in the “tests” folder that you can use for that purpose.
Displaycal load profile at login windows#
For testing purposes, I’d recommend assigning profiles via Windows color management that make the difference in calibration very clear, so that it is more easy to track changes visually as well.
Please try 3.1.7.1 Beta, it has a small bugfix in regards to the way display changes are detected as well as much more verbose logging. I have an idea what the problem might be, but it’ll require more testing. 20:58:30,183 A change in the display device configuration has been detected. I can’t reproduce it here, but from the logs it looks the display is still active, otherwise it wouldn’t be listed. As can be seen, nothing in display configuration really changes aside from FG2421 “moving up” in the list.
Displaycal load profile at login software#
I am hoping this is an issue with the software and can be reproduced, because I have been unsuccessful so far in trying to track down some possible conflict on my end.Īt 20:58:30,111 I switch off the Sony. I basically have to switch my monitors on and off in a certain sequence so I can “stack” the profiles in the correct order to get it working again 😀 This actually has an effect on what calibrations will apply, and which will not. One thing I did notice that changes when this happens is the order in which the profiles are listed in the loader’s notification pop-up. As I said before, profile associations seem to remain intact even after this change. I switch one display on or off, the desktop will flicker (as it usually does), and on the next attempt to load or reset a profile it may no longer work on one of the monitors. I noticed that the troubles start when my display configuration changes. Similarly, calibrations apply and reset correctly if I use that option in Displa圜al UI under the “Options” menu (the loader will override this once I quit), so the issue appears to be specifically with the loader. It appears to work on first launch, but will not apply/reset the calibration “on demand”, so to speak. If I load or reset the calibration and then restart the loader, then it will apply the correct setting once started. It’s clear enough visually, however, that nothing has changed. Logs I have checked tell the same story – everything worked correctly. The pop-up notification will report everything correctly: profile associations will be in order for all displays or it will claim to have applied linear curve to all displays, so as far as loader is concerned everything was applied successfully. What is happening is this: I have a multi-monitor setup (running on Windows 10, if that matters), and in some cases the loader will not apply the selected profile on some of the displays (or it will fail to reset the video gamma table, depending on the option chosen – basically the display will remain “stuck” in whichever mode it was). Now it seems to have become a little more “sticky” for me. I have noticed this happening before, but it seemed rare enough that I didn’t care all that much. As the title suggests, I am having a bit of a problem with the profile loader.
0 kommentar(er)
