6d280360e3
ADV.wmv carries ONE audio stream and it is wmapro 5.1, not XMA. Any framing of the intro's audio as only 'which of three voice streams to ship' was missing the bed. Aligned the 148 s capture against that track (envelope r 0.769 against a median of -0.001, refined to +224 samples, r 0.900) and solved capture = g x movie + residual per channel. The gain is 0.600 on every channel -- a uniform -4.44 dB, a mixer setting rather than a fit artefact. LFE reproduces to -115.73 dBFS, 72 dB down, which is what rules out codec difference as the explanation for the other residuals. FC is the exception: the movie explains NOTHING of it (-0.09 dB), and the movie's own FC is 91.6 % silent. The residual is three signals, not one: a front pair (r 0.918), a rear pair (r 0.929), and a centre whose partner LFE is empty. The FC residual spans 34 dB across 100 ms frames -- bursty, not steady noise. That CONFIRMS the corpus's 5.1 reading, which voice-three-streams-are-concurrent recorded as not established, and it confirms the specific detail it offered: that the mono-in-stereo stream is 'a centre paired with a silent LFE'. Measured from the output with no access to the stream contents. Also corrects my own census page: it labelled channels with the ALSA permutation [0,1,4,5,2,3] from the recipe page, which does NOT apply to this capture. The 6x6 matrix was computed assuming no order, every row's max falls on a distinct movie channel, and the answer is the identity -- so the census's 'BR is 82 % silent' was really LFE, reconciling with the movie's own 80.64 % silent LFE. Reach: one boot, one movie; which XMA context is front/centre/rear is not determined, only that the residual occupies those positions; and whether 0.600 is a fixed constant or a volume setting is unknown. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
Sylpheed
A clean-room reverse engineering and port project for Project Sylpheed: Arc of Deception (Xbox 360, 2007).
Three things live here, in one repository so that a change spanning them lands as one commit:
| The decoders | crates/sylpheed-formats — the disc's formats, read and verified disc-wide |
| The port | port/ — a Godot 4 project, plus crates/sylpheed-export which converts a disc into the open asset tree it reads |
| The corpus | docs/re/ — what has been reverse engineered, with its evidence, its retractions and its dead ends |
You need your own copy of the game. No game content is in this repository and none ever will be. The exporter reads the disc you supply.
The oracle is the real game
sylpheed-cliand the Explorer are tools for verifying our decoding. They are hypotheses under test and they have been wrong. When something must be checked against the truth, the truth is the game running in Xenia Canary, captured — not any renderer of ours.
This is stated first because getting it backwards is the most expensive mistake this project has made.
Layout
crates/
sylpheed-formats/ the decoders. Disc-wide verified; the corpus is its spec
sylpheed-cli/ headless tools -- render a screen, dump a table, probe audio
sylpheed-viewer/ the Explorer: a human's window onto the disc. STATIC data only
sylpheed-export/ disc -> the open, moddable asset tree
port/ the Godot 4 project. Reads open formats ONLY
authored/ decisions that are NOT on the disc, each with its reason
data/
base/ generated by the exporter. Gitignored, never hand-edited
mods/ drop-in overrides. Yours
docs/
re/ the corpus: findings, refutations, method traps
game/ how the game is navigated -- menus, modals, flight
port/ the port's mission, its handoff contract, modding rules
agents/ how the agent team works together
tools/ capture harnesses, probes, the share tool
exchange/ transient inter-agent files. NOT in git
docker/ the agent containers
Where to start
docs/re/INDEX.md— what is decodeddocs/re/REFUTED.md— what has been tested and dieddocs/re/METHOD.md— traps this project has already paid fordocs/game/navigation.md— how the game is navigateddocs/port/MODDING.md— why the asset tree looks the way it does
Xenia Canary is a separate repository: it is a fork tracking upstream, and it carries our instrumentation.
Conventions
Confidence is per claim, never per document: ✅ CONFIRMED · 🟡 PROBABLE ·
❔ HYPOTHESIS · ❌ REFUTED. A withdrawn result is kept with its reasoning
rather than deleted — that is why the numbers here can be trusted.