fabi/Syplheed-Reborn
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

re: withdraw an overstatement -- the wrong-recording case was already settled

Browse Source 
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.
This commit is contained in:
Sylpheed RE agent
2026-08-26 03:29:41 +00:00
parent 511bfee410
commit df48ccfe5b
2 changed files with 14 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/re/BACKLOG.md
View File

@@ -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.

17
docs/re/structures/sound-cue-table.md
View File

@@ -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