From cb1967795aa94336e508cf57ec84628c531da733 Mon Sep 17 00:00:00 2001 From: Sylpheed RE agent Date: Wed, 26 Aug 2026 03:29:41 +0000 Subject: [PATCH] re: withdraw an overstatement -- the wrong-recording case was already settled My sound-cue write-up said the table 'does not explain' the VOICE_D_452 rejection and implied it was still open. It is not: voice-bank-leading-region.md settled it earlier -- the bank holds one generic line reused across four stages, so the binding is correct and the expectation was wrong. The narrower true statement, which is what the cue table actually adds, is that the reuse is a movie-slot -> bank relation and not a cue-level one. --- docs/re/BACKLOG.md | 6 +++--- docs/re/structures/sound-cue-table.md | 17 +++++++++++------ 2 files changed, 14 insertions(+), 9 deletions(-) diff --git a/docs/re/BACKLOG.md b/docs/re/BACKLOG.md index a0db97e4..13a0a0d8 100644 --- a/docs/re/BACKLOG.md +++ b/docs/re/BACKLOG.md @@ -27,9 +27,9 @@ and which bank voices a line (`tables.pak`'s cue index — see [`structures/sound-cue-table.md`](structures/sound-cue-table.md); 1 326 of 1 338 script message ids resolve to a `.slb`). -**Still open from this**: the known wrong-recording case, which the cue table -does *not* explain — every cue id is distinct, so bank sharing must happen -inside the bank layer; the other five languages; and play order, since the tool prints +**Still open from this**: nothing about the wrong-recording case — that was +already settled in `voice-bank-leading-region.md` (generic line, correct +binding) and my first write-up wrongly reopened it; the other five languages; and play order, since the tool prints script order without resolving phases or branches. Multi-page captions were settled the same day — and in doing so refuted the first version of the tool, which truncated 356 of the 1338 names to their opening utterance. diff --git a/docs/re/structures/sound-cue-table.md b/docs/re/structures/sound-cue-table.md index 35b11a10..8ebc08e0 100644 --- a/docs/re/structures/sound-cue-table.md +++ b/docs/re/structures/sound-cue-table.md @@ -76,12 +76,17 @@ measurement. ## What this does *not* settle -* **The known wrong-recording case is not explained by this table.** - `VOICE_D_452` — the generic "Resupply complete" line documented in - [voice-bank-leading-region.md](../voice-bank-leading-region.md) — has its own - unique id (7140) and its own bank. Since every id is distinct, bank sharing - is **not** happening at the cue level, so that symptom still has to be - explained inside the bank/`sound.pak` layer. +* **The wrong-recording case was already explained, and I overstated it as + open.** On first writing this page I said the cue table "does not explain" + the `hokyu_DS_s13A → VOICE_D_452` rejection and that the sharing must + therefore live deeper. That was careless: + [voice-bank-leading-region.md](../voice-bank-leading-region.md) settled it + earlier — the bank holds one **generic** line ("Resupply complete. You are + cleared for take-off!") reused across four stages, so the binding is right + and only the expectation was wrong. What this table adds is narrower and + worth stating precisely: the reuse is a **movie-slot → bank** relation, not a + cue-level one, because all 5 797 numeric cue ids are distinct and no two cues + name the same bank file. * **`STAGES` is empty**, and what would have populated it is unknown. * **`SOUNDS`' one non-numeric value** was not chased down. * Only the English pack and the `jpn\` bank paths were examined. Every path in