[argyllcms] Re: Win7 losing monitor profile on wake
- From: Roger Breton Vaio <graxx@xxxxxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Mon, 23 Aug 2010 18:38:06 -0400
I have the same problem here, under Win7. When returning from sleep, the
LUTs are reset to linear. Nothing I can do other than re-download the
calibration over and over and over and over. Or, never let the computer go
to sleep.
Best / Roger
-----Original Message-----
From: argyllcms-bounce@xxxxxxxxxxxxx [mailto:argyllcms-bounce@xxxxxxxxxxxxx]
On Behalf Of Eric Thomas
Sent: August-23-10 5:32 PM
To: argyllcms@xxxxxxxxxxxxx
Subject: [argyllcms] Re: Win7 losing monitor profile on wake
On Mon, Aug 23, 2010 at 3:12 PM, Juergen Lilien <jp.lilien@xxxxxxxxxxxxxx>
wrote:
>
> Eric Thomas wrote:
>
> > However, when the laptop wakes from sleep or hibernate, the monitor
> > profile information appears to be lost and the colors return to the
system default.
>
> Have you checked that the monitor profile is set as the default
> monitor profile in the system settings (color) and that the Spyder
> profile loader is no longer running/installed?
>
> (No problem here with W7 and recent ATI driver.)
>
> Regards, Juergen
>
I definitely have the Spyder profile loader uninstalled.
I have the profile installed under 'Color Management'-->Devices-->Profiles.
This was done by dispcalGUI automatically. I've also now added it to 'Color
Management'-->Advanced-->'Change system defaults'. I'm noticing that on
wake, the correct profile is active for about 1 second after I log in, but
then something is changing the profile.
Florian: Kudos on the task scheduler approach ... I see the event you are
talking about in event viewer and was able to setup a task.
However, because of the 1 second delay I mentioned, there seems to be a race
condition going on and the displayGUI profile loader is running before the
other app (or Win7) that is changing the profile.
Both the laptops I have are doing this and both are using Intel Embedded
Graphics. I'm fairly sure the color settings that are being applied are the
settings that the Intel Graphics and Media Control Panel is using, so I'm
thinking this may be my conflicting culprit ...
now I just need to figure out how to stop it.
Thanks,
Eric
Other related posts:
