seeseemelk/cool-retro-term
1
0
Fork 0
Code Issues449 Pull Requests12 Actions Packages Projects Releases8 Wiki Activity

Long-term burn-in #238

New Issue
Open
opened 2015-04-01 13:37:46 +02:00 by merijnv · 2 comments
merijnv commented 2015-04-01 13:37:46 +02:00 (Migrated from github.com)

Since the nineties I use irc and other tools with some of the text rather fixed (ie top).

Long term degradation due to burn-in was an issue, where burn-in would mean the degradation of certain pixels over time when they have to glow longtime as high intentisy. This left a physical (darker) imprint on the screen (where the phosphor was burnt away), and the pixels would glow less when triggered. Ths always showing signs of the use of things like top, the headline of "watch" ouptut or irc-status.

The suggestion would be to define a number of frames of glowing at max intensity that would leave a lasting imprint, maybe as an image file.

Or, maybe easier, let the user choose such an image that contains a mask of pixels to darken to simulate the same effect.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Since the nineties I use irc and other tools with some of the text rather fixed (ie top). Long term degradation due to burn-in was an issue, where burn-in would mean the degradation of certain pixels over time when they have to glow longtime as high intentisy. This left a physical (darker) imprint on the screen (where the phosphor was burnt away), and the pixels would glow less when triggered. Ths always showing signs of the use of things like top, the headline of "watch" ouptut or irc-status. The suggestion would be to define a number of frames of glowing at max intensity that would leave a lasting imprint, maybe as an image file. Or, maybe easier, let the user choose such an image that contains a mask of pixels to darken to simulate the same effect. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/10310239-long-term-burn-in?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github). </bountysource-plugin>
Swordfish90 commented 2015-04-03 17:50:19 +02:00 (Migrated from github.com)

Hi, thank you for sharing this. While this was already reported , you added ideas and I also like the namings. I personally don't agree with the idea of loading a custom picture, but I just tried a dummy implementation which takes a sample every N seconds (currently 10) and add them to an accumulator with a very slow decay. I believe the result is quite good and not too heavy in terms of resources (since the sampling rate is very low).

In the next days I'll probably clean up the implementation to gather some feedbacks.

Hi, thank you for sharing this. While this was already reported #98 , you added ideas and I also like the namings. I personally don't agree with the idea of loading a custom picture, but I just tried a dummy implementation which takes a sample every N seconds (currently 10) and add them to an accumulator with a very slow decay. I believe the result is quite good and not too heavy in terms of resources (since the sampling rate is very low). In the next days I'll probably clean up the implementation to gather some feedbacks.
👍 1
Swordfish90 commented 2015-04-03 18:34:30 +02:00 (Migrated from github.com)

Ok, here we have an initial implementation. https://github.com/Swordfish90/cool-retro-term/tree/longburnin

Ok, here we have an initial implementation. https://github.com/Swordfish90/cool-retro-term/tree/longburnin
👍 1
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#238
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?