Phosphor persistence needs a log curve #283

Open
opened 2016-03-15 21:53:54 +01:00 by vphantom · 0 comments
vphantom commented 2016-03-15 21:53:54 +01:00 (Migrated from github.com)

Hello,

While I intend to tackle this issue I figured filing it here would be a good idea to avoid stepping on each other's toes. :) (Plus I have no idea yet if I'll be able to achieve my intention, not being a C++ programmer.) I was wondering why the persistence in xscreensaver's "phosphor" looked better and finally realized what was perfectible:

  1. The phenomenon currently named "BurnIn" in CRT is actually called "persistence", which is when turning off a pixel it gradually fades to black instead of turning off immediately. "BurnIn" should be renamed "Persistence" uniformly to make room for a future actual "Burn-In" feature (which seems to be in the works already), although this would break existing configuration profiles...
  2. Actual CRT phosphorus doesn't dim evenly over time: all the charts I've seen point to some kind of log formula, for example at Chocolate Doom. I believe this would address the "odd" impression I get when for example holding the SPACE bar and looking near the cursor, regardless of "BurnIn" percentage the effect seems too pronounced initially, then not enough.

Note that there's also a power-up curve for phosphor, but it's of course below 1/30th of a second so it's not a concern here.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/31924430-phosphor-persistence-needs-a-log-curve?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).
Hello, While I intend to tackle this issue I figured filing it here would be a good idea to avoid stepping on each other's toes. :) (Plus I have no idea yet if I'll be able to achieve my intention, not being a C++ programmer.) I was wondering why the persistence in xscreensaver's "phosphor" looked better and finally realized what was perfectible: 1. The phenomenon currently named "BurnIn" in CRT is actually called "persistence", which is when turning off a pixel it gradually fades to black instead of turning off immediately. "BurnIn" should be renamed "Persistence" uniformly to make room for a future actual "Burn-In" feature (which seems to be in the works already), although this would break existing configuration profiles... 2. Actual CRT phosphorus doesn't dim evenly over time: all the charts I've seen point to some kind of log formula, for example at [Chocolate Doom](https://github.com/chocolate-doom/chocolate-doom/issues/628). I believe this would address the "odd" impression I get when for example holding the SPACE bar and looking near the cursor, regardless of "BurnIn" percentage the effect seems too pronounced initially, then not enough. Note that there's also a power-up curve for phosphor, but it's of course below 1/30th of a second so it's not a concern here. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/31924430-phosphor-persistence-needs-a-log-curve?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>
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#283
No description provided.