Chapter 15 — Subtitles, verification, delivery

Status: DRAFT 1 (2026-09-21), DESIGN v6 §4, §3 W7, §9. Sources: ledger rows 327, 460–461, 585–586, 591–592, 594–599; production/phase3/submission-2026-09-14/SUBMISSION-CONFIRMATION.md, DELIVERY-CUT08.md; docs/artifacts/DELIVERY-SHEET.md:25–27, :39, :67.

15.0 Objective

Given the mix, you can measure subtitle windows from the audio, run the full decode and loudness check against the destination target, add the watermark or tail card if required, submit, and record the confirmation state with your own timestamp.

15.1 What you are deciding

Nothing creative. This chapter is the delivery sheet from Chapter 2, line by line, made true, and the two things a platform cannot do for you: the subtitle placed on the sound it belongs to, and the record of what the platform said when you handed the film over.

15.2 How we did it

Subtitles on measured windows. Subtitles were burned in as transparent PNGs over the segment for a cue window (the build script's cues). Placement was by the line's audio, not by the shot's start: for 3A the caption had been on 0.0–2.8 s while the line's RMS burst measured 2.6–3.7 s in the segment (row 586: "caption cue was 0.0–2.8 → move to 2.5–3.9"). The Director had caught it by ear: "我们去做个足疗 caption not aligned with voice" (row 585). Eighteen of twenty lines carried a burned-in English subtitle (the sheet says seventeen, the shotlist eighteen; the line that changed was English, the one that replaced it Mandarin).

Verification. Every export: full decode (ffmpeg -f null), frame count against the manifest, duration, hash, loudness. The submitted file: "205.4 seconds, 4929 frames; full decode 0; official watermark and packshot; no score" (row 460). The director's cut: 188.33 s, −21.6 LUFS, true peak −1.1 dBTP (row 592). That is 7.6 LU under the sheet's −14 house target for the social post; the cut was never posted, so the house gate was not applied to it, and had it been, it would have failed. The submitted CUT05/08 lineage measured −14.08 (DELIVERY-STATUS.md:7, CUT05). Loudness was measured with media.sh loudness; with --target it enforces and exits 1 (tools/media.sh:221–236; the sheet's G7 command at DELIVERY-SHEET.md:67). The sheet's true-peak field was never filled (:25), so no true-peak gate was ever enforced, only reported.

Delivery. The festival's minimum was two things: the file with watermark and packshot, and a public social post; "Missing either = incomplete" (:39). The post went up at 2026-09-15 00:00 UTC (row 461). The submission itself was a wizard with fields "Details / Film / Social post / Go live; minimum 3 min" (row 327); its final button was classified as a binding entry, so the agent handed the click to the Director (DELIVERY-CUT08.md:7). The Director reported "Done submit"; the agent then read the project page: the control now read "Update", the menu "Your submission", the status "Project is in review", "No numeric receipt ID or accepted-at timestamp was displayed" (SUBMISSION-CONFIRMATION.md:8–12), timestamped by us at 2026-09-15T00:02:56 UTC.

15.3 Case 15-A — the caption that was on the shot, not the line

15.4 Do it with your tools

Need We used Any tool If yours lacks it
Subtitle windows RMS burst per segment (numpy) + whisper transcript any waveform view play the segment and mark in and out by ear, twice
Burned-in captions Pillow PNG overlay in the build any editor's title tool a subtitle file if the destination takes one
Loudness gate media.sh loudness --target L --tol T --peak P any R128 meter —
Confirmation record a screenshot and a page read, timestamped by us same the platform's email, saved with its headers

15.5 Your turn

Time cap: one evening, plus the submission day. Spend: none.

  1. Measure every cue window on the final mix's segments; move any caption that starts more than 0.1 s before its line's burst. New cut folder.
  2. Verify: full decode, frame count against the manifest, duration, hash; loudness against your sheet's target with --target and --peak so it can fail. Ledger every number from the output, not from the plan.
  3. Watermark, tail card, title card as the sheet requires, then verify again (they change the frame count).
  4. Re-read the rules page and write its "last updated" into the timeline (Chapter 2's last row).
  5. Submit. If the last button is a binding entry, it is yours to click, not the agent's. Then read the platform's state and write it down with your own timestamp; save a receipt if one exists.
  6. The social post, if required, from the account the sheet names, with the watermark and tail card in the file you post.
  7. Play the delivered file yourself, start to end, from the platform if it lets you.

15.6 Gate (W7 — Delivered)

Each line needs valid evidence per DESIGN §5; outcomes are pass / fail / unverified, and unverified blocks.

Pass example from HALFWAY: SUBMISSION-CONFIRMATION.md, a status string, our timestamp, and the sentence "This verifies entry review status, not jury acceptance". Fail example: the 3A caption, 2.6 s early, in the submitted entry.