Match Interactive Film Subtitles to the Edit: Stop Old Lines Appearing After Pickups

When pickup footage replaces an interactive film video segment, explicitly record which subtitle version and language pair with that clip version. Leave pairings without review records pending verification. Subtitle completion should mean more than delivery of translated text: the exact finished video it belongs to must be confirmed. A folder containing both a new video and new subtitles does not prove they match.

The smallest delivery unit is “use location + clip version + language + subtitle version.” A story node may have replaced footage, and one video may have several subtitle files. Node names, file dates and “final version” cannot independently establish a pair. Version numbers distinguish revisions; matching numbers do not imply compatibility.

The fictional short Echoes Behind the Door illustrates this. A character in a corridor decides whether to hand over a key; a pickup replaces one dialogue passage. All lines, times and delivery records are teaching designs, not real user cases, tested results or product features. They do not imply that DramaFork performs these checks automatically.

Create the delivery index below, recording one language and one pairing per row. Subtitle versions may increase independently, but specify the video version they are based on. Index locations must point to concrete files, not merely someone’s “latest subtitles.”

For actual use, add each file’s full relative path, video duration, subtitle time reference, revision basis, reviewer and review-record location. State “times measured from this clip’s start” or explain conversion from the editing timeline. Mixing the two origins places correct numbers over the wrong images.

Do not write only “pickup update” as the timing-change reason. At least identify the affected interval, additions or removals and corresponding subtitle entries. Retain the row after confirming a pair; create a new revision record for further changes instead of overwriting the old basis. When a video is re-exported, confirm file identity even if its name is unchanged before deciding whether subtitles can be reused.

The example’s old V3 clip is 24 seconds long and new V4 is 26 seconds. The new edit adds a 1.2-second opening pause and inserts a 0.8-second reaction shot at the old clip’s 10-second point. A pickup also changes one spoken line. All times below use the start of the respective video file as zero.

Only the opening addition affects the first line; both additions affect the third. Do not shift the entire subtitle file by 1.2 seconds. Even if the second line is shifted correctly, its text remains wrong. It needs new words, new subtitle breaks and new timing, rather than an ordinary timing shift.

Record this change as: “Based on clip V4; add 1.2 seconds to line 1 and 2 seconds to line 3; retire line 2’s old text and rebuild from pickup dialogue.” This gives later language editors change locations and reasons, not final times they may blindly copy. Translation length, line breaks and reading rhythm still require separate checks.

The calculation applies only to the example’s two simple insertions. If actual editing also changes speech speed, overlapping dialogue or shot order, retime against new sound and images. A two-second increase in total duration does not mean every line moves two seconds.

First compare dialogue against the new finished video, then check each subtitle’s start, end and sequence, and finally inspect pairing references in the delivery package. Simply opening the correct file in a subtitle editor does not prove the work uses it when entering that segment.

Here, enter the corresponding clips through both “Hand over the key” and “Keep the key” in every delivery language. For the first, check that the new line appears and the old one disappears; for the second, confirm that this unchanged clip still references its original correct subtitles. If a replay entry also exists, index it too rather than updating only the main path.

Use a short review-record format: “use location, actual video, actual subtitles, observation point, judgment.” For example: “Hand-over-key entry; Corridor V4; Simplified Chinese V7; pickup dialogue; confirmation pending that ‘Give it to me now’ no longer appears.” This is a planned review task, not a pass result that can be recorded in advance.

When leaving a clip, check that its final subtitle disappears; when entering the next, check for a lingering line from the previous clip. If in-file timing is correct but text remains after switching, clearing subtitle display state may be the issue. Record the reproducing entry and transition position rather than hiding it by shortening every subtitle.

If only color grading changes and sound, edit order, duration and time reference remain unchanged, reuse the subtitle version after checking and add a pairing-confirmation record. If only a fixed opening duration is added, shift all subtitles provisionally, then check the ends and dialogue. Changed words, removed lines or reordered shots require rebuilding affected entries.

Small projects can check every subtitle individually. With many entries, use edit-change records to identify affected ranges, then check their boundaries. Without change records, “seems unchanged” cannot justify reuse; widen the review scope.

Before delivery, use three conditions to decide whether to pause: the video version underlying subtitles cannot be identified; a language has not addressed known wording changes; or an actual entry still references an old pairing. If a language is not ready, delay that language’s delivery or explicitly disable it under project agreements. Do not quietly fill the gap with old lines.

The final package should contain video, subtitles for each language, the pairing index and review records. For rollback, restore video and subtitles together using a recorded pair, then check entry references. This index handles version mismatches and change tracking; translation accuracy and natural expression still need their own editorial work.