1687062786273062912, 1692650176102449532

This commit is contained in:
ed committed 2026-08-25 09:28:31 -04:00
1 parent d07fc8fe82
commit 8103e2c8de
3 files changed
+51 -4

No files matched your search

@@ -7,7 +7,7 @@ author: "NOTimothyLottes"
handle: NOTimothyLottes
post_id: "1687062786273062912"
date: 2023-08-03
archived: 2026-08-23
archived: 2026-08-25
draft: false
tags:
- archive
@@ -39,7 +39,7 @@ Clearing page cache to simulate a cold launch: Takes 1.5 sec to read 256 MiB fro
Forgot the timing capture ... Load from SSD.
`1687066126268674048_F2mpszoXMAE00Hy_orig.jpg`
![](https://pbs.twimg.com/media/F2mpszoXMAE00Hy?format=jpg&name=orig)
**4/**
@@ -0,0 +1,43 @@
---
title: "@NOTimothyLottes i am not quite sure what do you mean by subpixel scan? do you override the normal (refresh) scanout process?"
type: archive
source: twitter
source_url: "https://x.com/tomcr2100/status/1692650176102449532"
author: "Tom Keresztes"
handle: tomcr2100
post_id: "1692650176102449532"
date: 2023-08-18
archived: 2026-08-25
draft: false
tags:
- archive
- twitter
- NOTimothyLottes
description: "@NOTimothyLottes i am not quite sure what do you mean by subpixel scan? do you override the normal (refresh) scanout process?"
in_reply_to: ""
parent_post_id: "1692560907988029769"
---
## Source
- URL: https://x.com/tomcr2100/status/1692650176102449532
- Author: Tom Keresztes (@tomcr2100)
- Posted: 2023-08-18 21:30:24
## Branch
**1/**
@NOTimothyLottes i am not quite sure what do you mean by subpixel scan? do you override the normal (refresh) scanout process?
**2/**
@tomcr2100 It's like "clear-type" font rendering where if you know the LCD sub-pixel configuration for the RGB components of a pixel, you can do a much better job of computing and outputing the value at the specific RGB sub-pixel element. So i'm doing this for CRT-like emulation on the Deck
**3/**
@NOTimothyLottes just curious, i started doing something similar, but this year i have focused more on rest&recover. i went with a trilinear style aperture grill approximation, and just allow prim components to leak into the two others.
## Related
- Spine: [[archive/threads/NOTimothyLottes/2023-08-18-spc-crt-shader-on-the-deck]]
@@ -7,7 +7,7 @@ author: "NOTimothyLottes"
handle: NOTimothyLottes
post_id: "1692559239116406864"
date: 2023-08-18
archived: 2026-08-23
archived: 2026-08-25
draft: false
tags:
- archive
@@ -31,6 +31,7 @@ SPC: CRT shader on the Deck. This time not doing subpix render. Yet RGB vs BGR o
![](https://pbs.twimg.com/media/F30tppDWwAAA-8J?format=jpg&name=orig)
![](https://pbs.twimg.com/media/F30tqE8XYAAgrFv?format=jpg&name=orig)
**2/**
Comparing all methods (grille, bad convergence scan, subpix scan)
@@ -38,13 +39,16 @@ Comparing all methods (grille, bad convergence scan, subpix scan)
![](https://pbs.twimg.com/media/F30uJoSWcAA7ICE?format=jpg&name=orig)
![](https://pbs.twimg.com/media/F30uKJdXkAA4PV8?format=jpg&name=orig)
![](https://pbs.twimg.com/media/F30uKouWQAAvY0q?format=jpg&name=orig)
**3/**
The non-subpix scan has 1-pixel separation of RGB (intentional bad convergence) to help hide scaling. The subpix scan uses 1/3-pixel separation (less visible misaligned convergence). Pixel as in output pixel.
Branches: [[archive/threads/NOTimothyLottes/2023-08-18-spc-crt-shader-on-the-deck/2023-08-18-tomcr2100-i-am-not-quite-sure-what-do-you-mean-by-subpixel]]
**4/**
The subpix version is definitely better. Because of the almost 3x doubling of scanline width detail, it just perceptually feels a lot cleaner and easier to reconstruct in the mind.
![](https://pbs.twimg.com/media/F30y9HPWUAAbmmw?format=jpg&name=orig)
![](https://pbs.twimg.com/media/F30y9h3WAAETuui?format=jpg&name=orig)
![](https://pbs.twimg.com/media/F30y9h3WAAETuui?format=jpg&name=orig)