On Tue, Feb 26, 2008 at 12:07 PM, Darren Salt <[EMAIL PROTECTED]> wrote: > retitle 467105 ATI driver: "xset dpms force on" causes one monitor to be > blanked briefly > thanks > > I demand that Alex Deucher may or may not have written... > > > > On Sun, Feb 24, 2008 at 11:21 AM, Darren Salt > > <[EMAIL PROTECTED]> wrote: > >> I demand that Brice Goglin may or may not have written... > >>> Darren Salt wrote: > >>>> One of my monitors (VGA-0) is repeatedly and regularly blanked and > >>>> unblanked, each change being approx. 1s apart when Xv is in use, e.g. by > >>>> gxine. > >> Actually, more like 1s off, 3s on, and for each pair of state changes, > >> there is a corresponding pair of > >> enable montype: 1 > >> enable montype: 3 > >> in the log. > > > Why is gxine calling the DPMS hooks for the monitors? > > It's designed to allow blanking when nothing is being played or the stream is > paused; on starting or resuming playback, it is intended that gxine will > unblank the display automatically. (There's no guarantee that the method used > to resume or start playback will also cause X to automatically unblank the > display; equally, there's no guarantee that the screen blanker will have cut > in, and gxine has no knowledge of whether it has.) > > Also, I don't want it to ever be able to fail to restore the DPMS settings – > by not altering them, there's nothing to restore. This does require ensuring > that the blank timer never reaches 0 (unless it's set ludicrously low). >
But why does it do it repeatedly? that's what causes the blinking. it should do it once, or am I missing something? > > > Do other video players have the same problem? > > Any which use the same methods will, since "xset dpms force on" is sufficient > to trigger the problem. when you run "xset dpms force on" does the blinking continue after you run it or does it happen once? Alex
