Implement into displays

[mdrejhon]

Meta Tracker

This is the most difficult biggie. It's easier to BYOA (Bring Your Own Algorithm), but it would be fantastic if this is built into the firmware of at least one future OLED (of at least 480Hz), as an optional CRT emulator setting.

It would pretty much capture the CRT-replacement market especially as OLED prices fall and replacement CRTs become unaffordable in the 2030s+.

It would also appeal to motion blur reduction enthusiasts, being gentler on the eyes than BFI.

Are you a display manufacturer?

I'm a hobby turned business, but now work with display manufacturers on contract from time to time. I help implement algorithms into your firmware, contact me at services.blurbusters.com, I can at least help in an advisory role. I can teach your software engineer how to port this to FPGA or other architecture, including reducing requirements (e.g. fewer lookbehind framebuffers, as few as 1).

[ColonelGerdauf]

I wonder if the shader languages are able to retrieve the refresh of the display, for example the EDID maximum, and then apply the suitable calculations.

[mdrejhon]

No but those can easily be relayed as "shader uniforms".

In other words, the firmware containing the shader will do the EDID and relay the values as shader uniforms (variables that get updated once a Hz).

I have some of this updated at the Open Source Display v1.01 spec at www.blurbusters.com/osi