Replace an Interactive Film Shot: Audit Subtitles, Trailers and Demo Versions

After replacing an interactive film shot, first find all uses by shot ID, judge subtitle, edit and story changes row by row, then open each deliverable to verify it. The reusable tool is a shot-reference list: each row records one use of one shot in one deliverable. Two uses in the same trailer need two rows.

An ordinary change log answers “What changed?” The reference list also answers “Where is old content still used, who handles it, and what confirms completion?” “Shot updated” cannot establish that a demo package’s copy changed or find an outdated press-kit screenshot.

The Rainy-Night Storage Locker is a fictional teaching example. All IDs, times and arrangements are illustrative, not real user cases, measured results or product features. Teams can maintain this list manually without any automatic checking mechanism.

Shot “Shot017” originally lasts eight seconds: the character lifts a key and says, “I’ve had the key all along.” The new six-second shot puts it on the counter and says, “I’m handing it to you now.” Both serve the same handover passage, so the shot ID remains while files are distinguished as old and new.

Write a replacement record: Shot017, eight seconds becomes six; dialogue changes; key possession becomes handover; planned for demo V7. This sets review scope: relisten for subtitles, check meaning in the trailer, inspect following dialogue in the playable demo, and review stills and descriptions in the press kit.

There are three impacts. File impact means references still point to old files; timing impact means shorter footage misaligns subtitles or later cuts; semantic impact means the image is updated but text still says the key was not handed over. Replacing a path alone handles only the first.

Re-encoding identical content may preserve the edit plan, but still requires confirming exported files. If the new version becomes a different story outcome, give it another shot ID and inspect both IDs’ destinations separately, avoiding replacement of a valid old branch.

Copy these columns. Every example row is a proposed task, not completed work. Locations and versions are shortened here; add file paths or project locations the team can directly find.

Reference objects must include versions, not just “trailer.” Match location type to object: subtitle cues, video intervals, demo entry paths and document pages. Source-shot times and trailer times use different coordinates; label them explicitly “source time” or “trailer time.”

Use method determines review. Separate subtitles can be revised independently; burned-in subtitles are part of the image and require a new video export. Stills may retain outdated story information even without a file dependency. Search beyond asset filenames to screenshots, text cards and corresponding dialogue.

Check subtitles first. Replace the old line with new dialogue and set appearance/disappearance against the new audio. Do not shift every following subtitle two seconds earlier: pauses may restore the duration and leave later timing unchanged. Log actual revised cues and play new subtitles together with the delivery video.

Then check the trailer. Suppose 12–16 seconds use the old shot, preceded by “He has always held the last bargaining chip.” After the key handover, that card may contradict the image even if the extract still fits. Rewrite the card or use another shot. If extracting only action before handover, still check whether neighboring images mislead.

Next check the demo. Open V7 prepared for delivery and follow “Enter hall → Ask about the storage locker → Counter handover” to the shot, then continue. If the next character still asks “Why won’t you hand it over?” add that line as a related review item. The table can extend from direct uses to adjacent content, but every added item needs a specific relationship reason.

Finally check the press kit. Page 3’s old still shows the character gripping the key, captioned “Refuses to hand it over.” Include it even if its filename differs entirely from the shot’s. After replacing the image, inspect the exported document to ensure the old caption is gone too.

Each row’s completion evidence must at least contain delivery version, viewed location, observation result and reviewer. For example: “Demo V7; counter handover path; new dialogue matches subtitles and following line connects; reviewer signature pending.” This is a record-format example, not actual playback or a pass to fill in beforehand.

Use consistent statuses: pending action, pending review, closed, retaining for now. Close a row only after the target deliverable is generated, the specified location viewed and the result recorded. A trailer whose source project is corrected but not re-exported stays pending review.

Not every old version must be deleted. Retain historical archives with recorded purposes, confirming current public entry points no longer point to them. If one trailer will remain unchanged for now, state the reason, display scope and next review condition. A blank status cannot substitute for a decision.

Common omissions are another language’s subtitles, a trailer in another aspect ratio or a separate copy sent to demonstrators. At wrap-up, reverse-check the current delivery directory: has every file still used been checked for Shot017 and its derived images and text? Add rows for omissions.

The table traces registered references and those found now; it cannot prove unknown copies do not exist. If the delivery directory is incomplete, list currently external-facing versions before closing checks. Hand over the reference list with corresponding delivery versions so the next person can locate, inspect and review every conclusion.