aubuti;427743 Wrote:
>
> radish is probably right that an "all pixels on" plugin would probably
> be ridiculously easy to write. Until that appears to restore stale
> pixels a good preventative is the FuzzyTime plugin, which allows the
> date/time screensaver to drift back and forth across the V
TiredLegs;427717 Wrote:
> In the case of a CRT, true "screensavers" light up the screen in
> pseudo-random patterns, which smooth out transitions to areas that have
> high burn-in.
Hmm, that was never my experience. My understanding is that
screensavers were designed to *prevent* burn-in on CRTs,
On the AV receiver's VFD, the process seems to even out about 80 percent
of the difference. After the whole screen is lit up for a couple of
hours, you can still make out which pixels get more use but that
distinction becomes subtle. When you go back to normal display usage,
it's barely noticeable
Oh I know all about CRT screensavers :) I'm surprised about the VFD
stuff, some of my older players have very distinct burn patterns, so if
it's fixable I'd be very happy - but no one's mentioned the possibility
in previous discussions of screen fade. Shouldn't be hard to rig up an
"all on" plugi
In the case of a CRT, true "screensavers" light up the screen in
pseudo-random patterns, which smooth out transitions to areas that have
high burn-in.
For VFDs, what you're saying might be true near the end of pixel life,
but it doesn't seem to work that way during the bulk of the lifespan. On
my
I can't see how that would work for a VFD (or CRT for that matter) - the
pixels have a finite life and get darker with usage. Hence why some are
darker than others (they're used more often). Just lighting up the whole
display would start wearing them all out equally - but they'd all get
dimmer at
I noticed the other day that many of the pixels on the display of my
Squeezebox 2 are not equally bright. My AV receiver has a function that
lights up all the pixels on its internal display for a few hours, which
restores the pixels to equal intensity. The AV receiver documentation
refers to this
