Files
Sylpheed/docs/re/data/tie-break-live-over-time-gp_title.txt
sylph-decoder 7b5a4aa041 re: the paint-order tie-break costs one pixel, on one screen we do not ship
Closes the open half of Q3. `ui-paint-order-derived-check.md` bounded WHERE a
wrong tie-break could show -- overlapping same-key pairs -- and said outright
that nobody had measured how many change a pixel.

At the instant the player sees, the answer is: at most 1 px at max channel
difference 1, on the JAPANESE title only (`ptlogo2` x `ptlogo_tm`, 5 px of
shared ink). Exactly 0 px on all five port screens.

The earlier 24-pair bound was counted at `rest()`, and 10 of the title's 11
overlapping tied pairs are between `ptlogo_back2eff1`..`eff5` -- the five
transient flashes from the settle-time finding, transparent on the settled
screen. A tie between two invisible elements cannot cost a pixel.

Not a knife-edge. Sweeping every keyframe time and every midpoint between
keyframe times, the live-pair count is flat across the ENTIRE settle window:
1 on the EN title, 2 on the JP title, 0 on all four loading bundles -- whose
tie is live only at t17..t33, during the build-in, which matters because
their settle windows are narrow enough to deserve little trust otherwise.

Controls: every entry reporting zero also swaps an overlapping DIFFERENT-key
pair, which must and does move pixels (25 310 / 268 698 / ~765 000 px). Zeros
are explained by shared-ink counts rather than asserted -- the `ptframe` pairs
overlap by bounding box and share 0 px of ink. Entries 0/1/12/15 have NO live
control and their zeros rest on keyframe data rather than a render; recorded
as the weaker claim it is.

Refutation attempt on the corpus's "24 overlapping pairs": it SURVIVES as a
rest-pose count -- an independent recount reproduces entry 7's 16 exactly.
What is overturned is its interpretation as the risk surface.

`tie_break_pixel_cost` gains a settle-time case and an alpha/scale filter on
its rect test; `tie_cost_over_time` is new. Also strips 611 bytes of captured
cargo warnings from the head of the committed tie census.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QsEPXWVaEpyfudtR6re1Pd
2026-08-29 19:35:29 +00:00

23 lines
1.8 KiB
Plaintext

# tied pairs that could cost a pixel, over time — /disc/dat/GP_TITLE.pak
entry 0 peak 1 live pair(s) over t=0..40 settle window [34,38] at t=36: 0 ACROSS THE WHOLE WINDOW: max 0
live only at t17:1 t18:1 t19:1 t20:1 t21:1 t22:1 t23:1 t24:1 t25:1 t26:1 t27:1 t28:1 t30:1 t32:1 t33:1
entry 1 peak 1 live pair(s) over t=0..40 settle window [34,38] at t=36: 0 ACROSS THE WHOLE WINDOW: max 0
live only at t17:1 t18:1 t19:1 t20:1 t21:1 t22:1 t23:1 t24:1 t25:1 t26:1 t27:1 t28:1 t30:1 t32:1 t33:1
entry 4 peak 6 live pair(s) over t=0..269 settle window [160,236] at t=198: 1 ACROSS THE WHOLE WINDOW: max 1
live at 62 of 88 sampled instants
entry 5 peak 2 live pair(s) over t=0..80 settle window [44,56] at t=50: 2 ACROSS THE WHOLE WINDOW: max 2
live at 47 of 47 sampled instants
entry 6 peak 2 live pair(s) over t=0..74 settle window [38,50] at t=44: 2 ACROSS THE WHOLE WINDOW: max 2
live at 46 of 46 sampled instants
entry 7 peak 6 live pair(s) over t=0..269 settle window [190,236] at t=213: 2 ACROSS THE WHOLE WINDOW: max 2
live at 92 of 117 sampled instants
entry 8 peak 2 live pair(s) over t=0..80 settle window [44,56] at t=50: 2 ACROSS THE WHOLE WINDOW: max 2
live at 47 of 47 sampled instants
entry 9 peak 2 live pair(s) over t=0..74 settle window [38,50] at t=44: 2 ACROSS THE WHOLE WINDOW: max 2
live at 46 of 46 sampled instants
entry 12 peak 1 live pair(s) over t=0..48 settle window [40,48] at t=44: 0 ACROSS THE WHOLE WINDOW: max 0
live only at t17:1 t18:1 t19:1 t20:1 t21:1 t22:1 t23:1 t24:1 t25:1 t26:1 t27:1 t28:1 t30:1 t32:1 t33:1
entry 15 peak 1 live pair(s) over t=0..48 settle window [40,48] at t=44: 0 ACROSS THE WHOLE WINDOW: max 0
live only at t17:1 t18:1 t19:1 t20:1 t21:1 t22:1 t23:1 t24:1 t25:1 t26:1 t27:1 t28:1 t30:1 t32:1 t33:1