fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

port: attempt the P4 fidelity question -- four traps reproduced, no verdict claimed

Browse Source 
AUDIO-VERIFICATION.md section 1 calls transcode fidelity the question P4 actually
raised, needing neither an engine nor a device, and gives it in four lines of
shell. Nothing implemented it: verify-video-audio deliberately declines, saying a
difference RMS without alignment is meaningless. So the P4/P7 gate has rested on
level and non-silence and the fidelity claim has never been made.

tools/port/verify-transcode-fidelity now exists and is committed WITHOUT a
verdict, deliberately.

Four ways the measurement lies, each reproduced here rather than reasoned about.
Indexing with a negative lag wraps to the end of the array in Python, so the
difference was the transcode subtracted from an unrelated part of the source --
reported 7 dB LOUDER than the source, the same catastrophic-looking number the
doc warns of. My regex for the recorded -af truncated the fold to its FL half,
folding the source to a left-only signal: the doc names that trap, I reached it
through a parsing bug, and the matrix contains runs of spaces so it cannot be
tokenised on whitespace. -ss before -i is a container-level jump and on this WMA
Pro source returned 4.6 s for a 4.0 s request while the Ogg side returned 4.0 s,
so the windows covered different stretches of the movie, best correlation 0.172 --
this one is NOT in the doc and is indistinguishable from the alignment trap that
is. And the single-resolution search returned +2413 against a window of +-2400,
its own boundary rather than a peak, the same family as the Decoder's period
estimator returning its search floor.

Why no verdict: best alignment is corr 0.763 on S00A and 0.075 on ADV, and both
still report the difference louder than the source, which cannot be true of two
aligned signals at equal level. The remaining fault is on my side. A tool printing
'not faithful' in that state would put a false defect on the exporter. It now
distinguishes 'could not align' from 'not faithful', two failures I conflated
twice before separating them.

Filed for the human as a proposal, not an edit: section 1 should carry the
imprecise-seek trap as a fourth entry.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
This commit is contained in:
Sylpheed port agent
2026-08-30 23:33:38 +00:00
parent 1e8c457a8b
commit ec2a17eaa9
3 changed files with 302 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/port/BLOCKED.md
View File

@@ -147,6 +147,13 @@ HANDOFF.
| ~~P1–P7 — the keyframe record layout~~ | ~~adopt the corrected pose/time pairing~~ | — | ✅ **ADOPTED 2026-08-29 by pinning `formats-pin-2026-08-29c`.** This row was wrong twice: it said the change *"cannot be taken yet"* and that it *"reaches the port only when that branch lands on `main`"*. **It arrives when the tag is pinned**, which is what MISSION §2's tagging rule exists for. ⚠️ And the knob I tested first, `SYLPHEED_KF_TIME_SHIFT`, is a **retired partial fix** that left pose 0 untimed — the real correction is the tagged crate's default, with the old reading behind `SYLPHEED_KF_TIME_LEGACY=1`. **The blast radius was far smaller than this row predicted**: under the correction *every pose is timed* (866 keyframes, 0 untimed), so `pose_at`'s synthetic-exit branch became dead code rather than wrong code and nothing needed re-deriving. Oracle: `publisher_logo` 1.00 %→**0.75 %**, `developer_logos` 0.39 %→**0.33 %**, `extras`' differing region collapsing from 736×525 to **398×295 at the sweep position**. 🔴 Open cost: `sylpheed-cli` builds from the workspace crate, so `verify-screen` compares two decoder eras until the tag reaches `main`. Revert to the path dependency then. |
| ~~P7 / naming — the four unnamed builds~~ | ~~which locale and variant is each of entries 0, 1, 12, 15?~~ | — | ✅ **answered 2026-08-29** (`docs/re/ui-title-build-map.md`): all four are the loading screen, two variants — plain (7 elements) and dressed (10) — decoded from their own `pgloading_*` element names. ⚠️ **Not adopted as names yet, for two reasons the RE agent gave and one the port found.** Theirs: the executable names exactly two, and *which* bundle takes which name is 🟡 undecided, so `LOADING`/`LOADING2` must not go in an asset path; and locale is 🟡 — the English member of a pair is the one in the first half of `GP_TITLE.p00`, 8/8 structurally but only 3/3 where a capture can check, and the three pairs that matter are the three no capture can check. Mine: **the message gives the bundles as "0/1 and 10/11", which is the `is_build` ordinal, and `authored/screen_names.json` is keyed by PAK ENTRY** — in entry space 10 and 11 are `palogo_sqex` and `palogo_gamearts`, the splashes. See the refutation section in `DECISIONS.md`. |
## Open on my own side, 2026-08-30 — derived from HANDOFF `0159527`
| Milestone | Needs | HANDOFF | State |
|---|---|---|---|
| P4/P7 — transcode fidelity | **nothing from anybody; my instrument cannot answer yet** | `0159527` | 🔴 **THE GATE HAS NEVER CARRIED A FIDELITY CLAIM, and now it says so.** `AUDIO-VERIFICATION.md` §1 calls this the question P4 actually raised; nothing implemented it, and `verify-video-audio` explicitly declines it. `tools/port/verify-transcode-fidelity` exists and is **report-only**: best alignment is corr 0.763 on `S00A` and 0.075 on `ADV`, and both still report the difference *louder* than the source, which is impossible for two aligned signals at equal level — so the fault is on my side of the instrument, not necessarily in the transcodes. Four traps reproduced on the way, three of which §1 names and one (**`-ss` before `-i` returning 4.6 s for a 4.0 s request**) it does not. ⚠️ A tool printing "not faithful" in this state would put a **false defect on the exporter**. |
| P4/P7 — a `§1` addition for the HUMAN | **add the imprecise-seek trap to `AUDIO-VERIFICATION.md` §1?** | `0159527` | 🟡 **proposed, not done.** §1 lists three ways the measurement lies; a fourth is now reproduced — a container-level seek returns a different span than requested, so the two windows cover different audio and no shift can align them (best corr 0.172). It is **indistinguishable from the alignment trap §1 already names**. §1 is the human's document, so this is a proposal rather than an edit. |
## Not blocking, recorded so nobody re-investigates — 2026-08-30, HANDOFF `91ada14`
| Milestone | Needs | HANDOFF | State |

48
docs/port/DECISIONS.md
View File

@@ -9,7 +9,7 @@ dies, which is what this file is for.
<!-- INDEX: generated by tools/port/index-decisions -- do not hand-edit -->
256 sections. Search this before re-deriving anything.
257 sections. Search this before re-deriving anything.
* [P0 — the exporter, 2026-08-28](#p0--the-exporter-2026-08-28)
* [P1 — Godot draws the screen, 2026-08-28](#p1--godot-draws-the-screen-2026-08-28)
@@ -267,6 +267,7 @@ dies, which is what this file is for.
* [Their rule applied backwards: my video result is stronger than my withdrawal said](#their-rule-applied-backwards-my-video-result-is-stronger-than-my-withdrawal-said)
* [🔴 I measured my own claim and it is wrong: the player skips, heavily](#i-measured-my-own-claim-and-it-is-wrong-the-player-skips-heavily)
* [🔴 Correcting the correction: the frame probe is an UPPER BOUND, and my contrast was contention](#correcting-the-correction-the-frame-probe-is-an-upper-bound-and-my-contrast-was-contention)
* [The P4 fidelity question, attempted: four traps reproduced, no verdict yet](#the-p4-fidelity-question-attempted-four-traps-reproduced-no-verdict-yet)
<!-- /INDEX -->
## P0 — the exporter, 2026-08-28
@@ -13204,3 +13205,48 @@ ask what else was running.*
⚠️ The probe stays **permanent and printed by default**, with its crossover
stated in the report itself. Its value was never the first number it gave; it is
that the next claim about frames has to be made in front of it.
## The P4 fidelity question, attempted: four traps reproduced, no verdict yet
`AUDIO-VERIFICATION.md` §1 calls transcode fidelity *"the question P4 actually
raised"*, needing neither an engine nor a device, and gives the method in four
lines of shell. **Nothing implemented it.** `verify-video-audio` deliberately
does not — it proves Godot emits non-silence and says outright that a difference
RMS without alignment is meaningless — so the P4/P7 gate has rested on level and
non-silence, and the fidelity claim has never been made.
`tools/port/verify-transcode-fidelity` now exists. **It does not yet produce a
verdict, and it is committed saying so.**
### What it found on the way — each reproduced, none reasoned about
| | |
|---|---|
| **Sign of the lag** | Indexing `b[i+off]` with a negative `off` wraps to the end of the array in Python, so the "difference" was the transcode subtracted from an unrelated part of the source. Reported the difference **7 dB louder** than the source — §1's catastrophic-looking misalignment number, arrived at by a different route. |
| **Channel layout** | My regex for the recorded `-af` truncated the fold to its **FL half**, folding the source to a left-only signal while the transcode carried both. §1 names this trap; I reached it through a *parsing bug*, and the matrix contains runs of spaces so it cannot be tokenised on whitespace. |
| **Imprecise seek — NOT in §1** | `-ss` before `-i` is a container-level jump. On this WMA Pro source a 4.0 s request returned **4.6 s** while the Ogg side returned 4.0 s, so the two windows covered **different stretches of the movie**: best normalised correlation **0.172**, no shift could align them. Decoder-side `-ss` after `-i` is exact. **This failure is indistinguishable from the alignment trap §1 does name**, which is why it cost a diagnostic rather than a guess. |
| **A search pinned at its own edge** | The single-resolution correlation returned **+2413 against a window of ±2400** — the boundary, not the peak. Same family as the Decoder's period estimator returning its own search floor: **an instrument answering with a property of itself.** Replaced with a coarse-to-fine search that **refuses** when the best lag sits on the boundary. |
### 🔴 Why it is committed without a verdict
Best alignment so far is **corr 0.763** on `S00A` and **0.075** on `ADV`, and both
still report the difference **louder** than the source — which cannot be true of
two aligned signals at equal level. **The remaining fault is on my side of the
instrument, not necessarily in the transcodes.**
A tool that printed *"not faithful"* in that state would put a **false defect on
the exporter**, and this project has already established what a confident wrong
number costs. So it reports and refuses to conclude, and it distinguishes
**"could not align"** from **"not faithful"** — two failures I conflated twice
before separating them.
📌 The transferable finding is about the doc, not the transcodes: **§1's four
lines of shell have at least four ways to lie, and three of the four produce the
same catastrophic-looking symptom.** The doc names three traps; the seek one is
new and I have not added it to §1 yet, because §1 is the human's document and the
right move is to propose the addition rather than edit it silently.
⚠️ **Not settled and explicitly not claimed:** whether `ADV.ogv` and `S00A.ogv`
are faithful to their sources. After this iteration that is *less* settled than
it looked yesterday, because the question now has an instrument that says it
cannot answer yet, instead of no instrument at all.