Yes, it's time for this year's thread about avoiding screen burn. But first, the preliminaries: it is usually claimed that LCD screens do not suffer from screen burn. Not so!
In 2006 I purchased a Toshiba LCD TV with fluorescent illumination. I used it for three years with a Humax PVR connected via SCART; this had some overscan, so there were no black strips around the edges of the picture. Then in 2009 I started using Windows Media Center, connected initially via VGA, and later via DVI. The best fit that I could get (whilst avoiding overscan) left a one-centimeter black strip on all four edges of the picture. About a year later, I discovered how to scale the Windows desktop so that it fitted the screen exactly without overscan. But by then it was too late -- the black strips around the edges of the picture had permanently imprinted themselves onto the screen, with the result that the former boundaries between picture and black strip are now visible when there are areas of plain tone near the edges (such as plain blue sky).
I also use a character-based file-manager on the HTPC. This file manager has quite saturated colours, and if left on the screen for a peroid of time (15-30 minutes), it leaves a ghost image when that window is closed.
This ghost image remains visible for several hours (but thankfully does fade eventually).
Recently I purchased a new TV -- a Sony LCD with LED illumination. So the question of screen burn has captured my attention again. The Sony has a very useful "Picture off" function, that simply turns off the LEDs, whilst leaving everything else operating normally. This is ideal for listening to DVB-T radio broadcasts, or listening to music sourced from the HTPC. The problem is that it takes 13 button presses on the remote control to use this function!
So, it is not really a practical solution (it needs to be a simple toggle accessed directly from a button on the remote control).
Now we come to MP. I tried enabling MP's "Screen Saver" function, selecting the "blank screen" option with a 30-second timeout. Does it work? Well, yes and no!
It actually behaves in two different ways according to what is displayed on the screen:
(1) If I pause high definition live TV, or a recording of HD TV, when the screen-saver activates, the screen blanks and the LEDs turn off.
(2) If I pause standard definition live TV, or a recording of SD TV, when the screen-saver activates, the screen blanks but the LEDs do NOT turn off. This is also the case for the MP panels that do not have video, and the MP panels that play the radio (both paused and not paused).
(3) If the MP panel has a video thumbnail, the screen blanks even when the video is playing, but behaves as (1) or (2) according to whether the video in the thumbnail is HD or SD.
I used the Sony's "Info" display to see what it thought it was displaying, and it showed "1080p" in all cases (video running, video paused, HD, SD).
So it seems as though MP's Screen Saver does something different when displaying HD, compared to displaying SD. Needless to say, I would prefer the LEDs to turn off when the screen is blanked, and hence I would like MP to use the HD action in all situations. Questions:
(a) Is there any explanation for this difference in screen-saver behaviour between HD and SD?
(b) Is there any chance that MP could be altered to use the HD method in all cases?
Thank you.
-- from CyberSimian in the UK
In 2006 I purchased a Toshiba LCD TV with fluorescent illumination. I used it for three years with a Humax PVR connected via SCART; this had some overscan, so there were no black strips around the edges of the picture. Then in 2009 I started using Windows Media Center, connected initially via VGA, and later via DVI. The best fit that I could get (whilst avoiding overscan) left a one-centimeter black strip on all four edges of the picture. About a year later, I discovered how to scale the Windows desktop so that it fitted the screen exactly without overscan. But by then it was too late -- the black strips around the edges of the picture had permanently imprinted themselves onto the screen, with the result that the former boundaries between picture and black strip are now visible when there are areas of plain tone near the edges (such as plain blue sky).
I also use a character-based file-manager on the HTPC. This file manager has quite saturated colours, and if left on the screen for a peroid of time (15-30 minutes), it leaves a ghost image when that window is closed.
Recently I purchased a new TV -- a Sony LCD with LED illumination. So the question of screen burn has captured my attention again. The Sony has a very useful "Picture off" function, that simply turns off the LEDs, whilst leaving everything else operating normally. This is ideal for listening to DVB-T radio broadcasts, or listening to music sourced from the HTPC. The problem is that it takes 13 button presses on the remote control to use this function!
Now we come to MP. I tried enabling MP's "Screen Saver" function, selecting the "blank screen" option with a 30-second timeout. Does it work? Well, yes and no!
(1) If I pause high definition live TV, or a recording of HD TV, when the screen-saver activates, the screen blanks and the LEDs turn off.
(2) If I pause standard definition live TV, or a recording of SD TV, when the screen-saver activates, the screen blanks but the LEDs do NOT turn off. This is also the case for the MP panels that do not have video, and the MP panels that play the radio (both paused and not paused).
(3) If the MP panel has a video thumbnail, the screen blanks even when the video is playing, but behaves as (1) or (2) according to whether the video in the thumbnail is HD or SD.
I used the Sony's "Info" display to see what it thought it was displaying, and it showed "1080p" in all cases (video running, video paused, HD, SD).
So it seems as though MP's Screen Saver does something different when displaying HD, compared to displaying SD. Needless to say, I would prefer the LEDs to turn off when the screen is blanked, and hence I would like MP to use the HD action in all situations. Questions:
(a) Is there any explanation for this difference in screen-saver behaviour between HD and SD?
(b) Is there any chance that MP could be altered to use the HD method in all cases?
Thank you.
-- from CyberSimian in the UK
Last edited: