GratisAIaccessibility · field guide · local-first · no account
splice cuebook

Rebase Transcript Times After a Leading Cut — Free

After removing a lead-in, every transcript cue needs the same offset but a cue crossing the cut also needs clipping. Keep those cases visible instead of generating negative timestamps.

The proof surface

Caption-speed audits measure reading load. This performs a single leading-cut time translation and marks removed or clipped cues; it does not change the transcript text.

Inputcue | original start seconds | original end seconds; seconds removed from the start
Rare deviceCaption-speed audits measure reading load. This performs a single leading-cut time translation and marks removed or clipped cues; it does not change the transcript text.
Output artifactretained cue seconds per row with transparent workings
Cost$0 · local-first · one free run · samples labelled
Sample, not your facts: Illustrative sample: Welcome | 8 | 16; Access instructions | 18 | 30. With seconds removed from the start set to 12, total is 16.00 retained cue seconds.

Why the flat version breaks

Subtracting only from the start

The end timestamp must move by the same offset.

Keeping negative timecodes

Cues crossing the cut must be clipped or rewritten.

Applying this to internal edits

One offset cannot describe several separated cuts.

How to work the splice cuebook

Work from a backup transcript

Use non-sensitive cue labels with start and end times in decimal seconds. Convert minute-and-second notation before entry; 1:30 is ninety seconds, not 1.30.

Identify the exact leading cut

Read its duration from the editor timeline. This tool supports one cut at the beginning, not internal edits, speed changes or multiple discontinuities.

Subtract and clip to zero

Subtract the cut from both endpoints and floor each at zero. A cue from eight to sixteen seconds after a twelve-second cut becomes zero to four; fully removed cues retain zero duration.

Listen around the edit boundary

Review every flagged cue in the edited media and update wording if a sentence was cut. The row notes show new endpoints, but no subtitle file is exported or validated.

What the splice cuebook replaces

QuestionBeforeVisible working
Subtracting only from the startThe end timestamp must move by the same offset.Identify the exact leading cut
Keeping negative timecodesCues crossing the cut must be clipped or rewritten.Subtract and clip to zero
Applying this to internal editsOne offset cannot describe several separated cuts.Listen around the edit boundary

A local arithmetic aid replaces hand calculation, not expert review. No paid AI service is needed.

Run it on the samples, right here

FIRST-LOAD

Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.

Timing arithmetic only. Review synchronization, cue wording and speaker identification in the finished media before publishing.

Data note: Everything runs in this browser tab on the splice cuebook: your cue | original start seconds | original end seconds stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.

Go deeper: the companion app files the same reading as a clerk's docket sheet

The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the splice cuebook reading, and holds your drafts on this device — one free run, then $ 4 one-time for the layer that keeps filing.

The splice cuebook reading is complete for free. The optional $4 layer adds print, row CSV and the last five local reading summaries; it does not add hidden answers. Checkout is not configured yet; the article demo remains unlimited.

Open the rebase transcript times after a leading cut companion

Boundary

Timing arithmetic only. Review synchronization, cue wording and speaker identification in the finished media before publishing.

What this is built on

Before: The end timestamp must move by the same offset. After: the splice cuebook shows the working beside each named row so the reader can change the assumption and inspect the consequence.

Optional AI formatting, not calculation

For this splice cuebook, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.

Format my non-sensitive notes for a splice cuebook. Return plain rows only: cue | original start seconds | original end seconds. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.

Accepted schema: cue | original start seconds | original end seconds. No AI response is executed as code.