[argyllcms] Re: dispwin -D use a lot of cpu

  • From: Andrew Lutomirski <amluto@xxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Fri, 8 Jan 2010 17:09:01 +0800

In my experience, dispwin -D (1.0, anyway) is rather buggy, but I've
had much better luck with my calibration staying loaded with a very
recent Xorg.  (The intel driver, on any Xorg older than the one in
Fedora 12, loves to reset the calibration on its own.  Other drivers
may behave similarly.)

You could also file a bug with the wine developers -- IMO wine has no
business changing the calibration under any circumstances (except when
running a full-screen game, I suppose, although I don't really
understand why games feel the need to change the calibration).

It might be nice if there were some standard library for full-screen
programs that want to display at a nonstandard gamma to use to (a)
restore the calibration properly when closed and (b) compose the gamma
correction with the calibration instead of replacing it.


On Fri, Jan 8, 2010 at 4:31 PM, Lars Tore Gustavsen
<lars.tore@xxxxxxxxxxxxxx> wrote:
> Fighting with the vcgt curve on linux can be quite frustrating.  I
> discovered recently that wine (I’m talking software:-) ) deletes my
> vcgt curve and don’t restore it either.
> I have tried dispwin –D to fight all this issues, and it works very
> well, but  the cost is too high on my system. I should of course
> mention that my computer is 6 years old. I have attached a screenshot
> showing cpu costs. In the screenshot dispwin –D is killed in the
> middle and started again.
> If there was a way to set the iteration time, I could run it much more
> economically. I could live with one time each 30 seconds or even more
> infrequently.
> Regards
> Lars Tore Gustavsen

Other related posts: