This repository has been archived on 2026-09-16. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
Syplheed-Reborn/docs/re/data/splash-ramp-check.txt
Sylpheed RE agent 531840b417 re(ui): Q1 -- the interpolation law holds, the group timeline does not
Q1's gate asks whether the ramp is linear. It is, and that result stands:
it rests on the splash's _eff glows, which reproduce exactly. This adds
the part that does not.

The test is a calibration, not a fit. Fix the clock on
palogo_gamearts_eff -- declared 15-unit fade-in 0@15 -> 255@30 against
captured alphas 34,68,102,136,170,204,238, a constant step of 34, giving
t = 2f - 171 -- then check that against the glow's own next landmark: its
declared hold ends t=45, predicted frame 108.0, observed last full-alpha
frame 107. Then apply it to palogo_gamearts in the same bundle and the
same frames, with no free parameter left:

  declared a=232 at t=206 -> frame 188.5, observed alpha 255
  declared a= 32 at t=210 -> frame 190.5, observed alpha 255

The logo is still at full alpha nine frames after it should read 32; its
fade-out runs ~17 frames late; its declared 80-frame fade-in is never
drawn. Not culling -- the same element is submitted down to a=7 on the
way out. Calibration-free version: the declared fade-out spends 12 of 16
units dropping 23/255 of the alpha, and the capture has no such plateau.

Candidate, offered and NOT adopted: if +36 held the NEXT keyframe's time,
the fade-out shape fits (RMS 4.05 vs 12.13, two elements) and the
decoder's "last block's time is unreadable" special case disappears --
the last block would simply have no successor. Rejected for now because
it explains neither the missing fade-in nor the lateness, and because the
_eff elements cannot discriminate between the readings at all (with four
blocks the shift only relabels the phases). Decoder unchanged.

Also withdrawn, mine, within the iteration: "the _eff glows hold a
constant alpha 33". They ramp 34 -> 255 in steps of 34. I printed the
series minimum and read it as its range, with a "14 distinct colours"
column sitting next to it saying otherwise.
2026-08-28 22:56:17 +00:00

21 lines
1.2 KiB
Plaintext

CONTROL — the eff glow's fade-in must be linear at a constant step
alphas [34, 68, 102, 136, 170, 204, 238] steps [34, 34, 34, 34, 34, 34]
=> 2.000 units/frame; t(f) = 2*f - 171
check: declared hold ends t=45 -> predicted frame 108.0; observed last full-alpha frame 107
LOGO — palogo_gamearts, checked against that calibration
observed: first drawn frame 116 at alpha 255; full alpha through 198; fade-out 199..211
declared a= 0 at t= 15 -> frame 93.0 observed alpha NOT DRAWN
declared a= 0 at t= 30 -> frame 100.5 observed alpha NOT DRAWN
declared a=255 at t=190 -> frame 180.5 observed alpha 255
declared a=255 at t=194 -> frame 182.5 observed alpha 255
declared a=232 at t=206 -> frame 188.5 observed alpha 255
declared a= 32 at t=210 -> frame 190.5 observed alpha 255
SHAPE, independent of any calibration:
declared fade-out spans t=194..210 (16 units); of that,
12/16 units drop only 23/255 of the alpha (a near-flat leg),
4/16 units drop 200/255 (a cliff).
captured fade-out: [255, 254, 243, 237, 215, 181, 148, 131, 98, 65, 48, 23, 15, 7]
per-frame drops: [1, 11, 6, 22, 34, 33, 17, 33, 33, 17, 25, 8, 8] -> no near-flat leg