Hardware & Technical Do monitors still suffer from 'Burn in' ?
- Thread starter Macy
- Start date
Come on mate - how on earth have you reached 'competent' on the forums without having the presence of mind to do a quick search. Plenty of people have brought this up already since yesterday's release, and plenty of others have relayed FD's assertion that
- it's a mistake - it should not be there
- it will be removed asap
As far as burn in - Yes, some LCD monitors can suffer from burn-in, but it takes a lot of time on a static image to do it. For instance, I bought 10 monitors for a control system and they were kept on the same screens for a number of years before some started to fail. When replaced, These monitors had burnt-in images of the basic control screens. These were 4x3 florescent backlit flat panel LCD monitors.
When upgrading and expanding the system, I bought 16 newer LED backlit 16x9 monitors. They've been stuck on the same screens for about 2 years and none are showing signs of burn-in. This is an extreme environment for the monitors, so I'd say that the newer LEDs are immune.
TL
R - Older LCD monitors can suffer from burn-in, but I haven't experienced it with newer LED monitors.
When upgrading and expanding the system, I bought 16 newer LED backlit 16x9 monitors. They've been stuck on the same screens for about 2 years and none are showing signs of burn-in. This is an extreme environment for the monitors, so I'd say that the newer LEDs are immune.
TL
R - Older LCD monitors can suffer from burn-in, but I haven't experienced it with newer LED monitors.
Last edited:
I've only seen screen burn on one LCD monitor at work. It is an old Dell 1600x1200, high end when it was bought around 10 years ago. It is still in use now, and I find if the same image is left on it for a long time (many hours, days), you can see a ghost of that image for some time after. Also there is a colour shift starting on one edge. Not sure what the mechanism for that is.
The image persistence effect on LCDs is a bit different to burn in. And it seems that it is quite often correctable. I've never experienced it, so I've never tried.