v0.0.1-alpha [Proof of Concept]

[Master-Antonio]

Puretype_Prototype.zip

🚀 Puretype v0.0.1-alpha [Proof of Concept]

The first custom subpixel rendering engine for OLED monitors on Windows.

⚠️ WARNING: Experimental Release (Alpha)

This is a Proof of Concept. The software uses system-level API Hooking and DLL Injection to bypass Microsoft's native ClearType rendering. It is not yet ready for daily driver use. You may experience visual glitches, flickering, or unexpected crashes in unsupported applications. Use at your own risk.

---

🧬 Project Status

The core injection engine (injector.exe) and the rendering infrastructure (Puretype.dll) are successfully up and running. The engine can intercept Windows text rendering calls and apply our custom spatial filters.

However, i need the community's help. The mathematical foundation for LG WRGB and Samsung QD-OLED (Triangular) layouts is implemented, but i still need to find the perfect rendering values.

🎯 Call to Action: Tuning the Rendering Values

Currently, the calibration values (convolution kernel weights, linear Gamma curves, and Stem Darkening strength) are just placeholders.
I invite users with OLED panels to test the application (e.g., on notepad.exe) and share feedbacks.
The goal of this phase is to collect visual feedback and macro-photography of the pixels to find the "golden ratio" that guarantees maximum sharpness and zero color fringing.

🛡️ Known Limitations: The Injection Blacklist

To ensure operating system stability and protect users, this release includes a strict, hardcoded blacklist system.
The DLL injection is intentionally blocked from attaching to certain executables. If you notice that some apps still use the old ClearType rendering, they are likely blacklisted.

Currently excluded processes:

• Video Games & Anti-Cheat Engines: (e.g., Vanguard, EasyAntiCheat, BattlEye). Injecting a DLL into competitive games will trigger a ban. SharpType automatically aborts injection here.
• Critical System Processes: (csrss.exe, lsass.exe, winlogon.exe) to prevent Blue Screens of Death (BSOD).
• Certain UWP / Modern Apps: Highly sandboxed applications (AppContainers) might currently ignore the hook or crash if the DLL lacks the ALL APPLICATION PACKAGES security permissions.

---

🛠️ How to Test

1. Extract the .zip archive into a folder.
2. Run the injector
3. Open Notepad (notepad.exe) or other standard Win32 applications to see the difference.
4. Share your macro screenshots and the exact configuration values you used in the "Issues" or "Discussions" tab!

---

This discussion was created from the release Prototype.

[mdrejhon]

I am curious.

Does it support RWBG with B before G, as per 99% of LG products? And accounts for the four-spatial steps?

[mdrejhon]

WRGB doesn't exist. There's no screen with W-R-G-B as it does not exist;

It's only R-W-B-G (most) and R-G-W-B (few).

Easiest is to mostly ignore the W pixel, and focus on R-[gap]-B-G and R-G-[gap]-B

You may want to use a GPU shader approach instead of using CPU SIMD; if possible.

The "PixelLayout" string method found in MacType and FREETYPE

snowie2000/mactype#720 (comment)

I wonder if your INI file potentially support this flexibility, maybe?

What you could potentially do is support the Linux PixelLayout= pixel offset formulas, so there's more flexibility to port between implementations, as I am creating a special TestUFO that will accept & render a PixelLayout= string.

[Master-Antonio]

Thank you for information, I will fix soon