Catch the issues before the client does

A language version can read well in the editor and still miss the delivery brief. One subtitle leaves the screen too quickly, another runs past the line limit, a third starts before the speech it belongs to. Each issue is small, but together they send a file back for another round.

QC gives editors a clear technical review pass before a version leaves the team. It does not replace the person watching the video. It points them to the subtitles that need a decision, so review time goes where it is useful.

  1. 01 / TIMINGDuration
  2. 02 / READABILITYSpeed
  3. 03 / LINE LIMITSLength
  4. 04 / DELIVERYExport
Four areas to check before a language version leaves the team.

Set the limits from the delivery brief

In clipsubs, QC has eight adjustable checks: short and long duration, total and per-line length, line count, reading speed, early starts and formatting. It also detects overlapping subtitles. Every threshold can be changed, so you are not tied to a single fixed profile.

A sensible starting point is the broadcast-style defaults: 37 characters per line, 2 lines and 20 characters per second. Then adjust them to the brief. If the client asks for shorter lines, a slower reading speed or a different minimum duration, set those limits before you run the checks, so the flags reflect the job rather than a general rule.

A flag focuses attention. The editor decides what works on screen.

Work through the flags in the editor

Run QC and jump to the next flagged issue. Each one takes you to the subtitle alongside the video, so you can judge the wording and timing in context. Use one-click auto-fix where it is appropriate, or make the change yourself: drag a boundary on the waveform, nudge a subtitle by 100 ms, split a long subtitle or insert a line break. Per-line character counts show the structure while you work. Whichever route you take, review the result before you move on. If an external specialist does this pass, set whether their task permits QC and automatic fixes.

Before you run QC

  • Confirm the exact language version you are reviewing.
  • Set line length, line count and reading speed from the brief.
  • Check the duration limits and formatting requirements.
  • Agree who makes the final language and specification review.

Re-split or resync, then export

When the flags point to a pattern rather than a handful of subtitles, change the approach. If the words are right but the segmentation does not suit the brief, Re-split rebuilds the lines by sentence or into 1, 2 or 3 lines using your character, reading-speed and duration limits. If the track has drifted from the audio, AI Resync retimes it, and can add missed speech or remove subtitles that do not match. Both keep the original version, so compare the result and run QC again. QC, Re-split and editing are free; AI Resync uses 0.3× the video duration in AI hours.

QC supports the review; it does not approve the delivery. Your team still checks meaning, timing, accessibility and the client’s specification. When that is done, share the version for client review or export SRT, WebVTT or EBU STL. For a batch of incoming files, bulk SRT QA can check and fix up to 30 at once, then the same review applies.