hypitFIELDNOTES

GUIDE 03 / Composition / Read: 5 min

Time captions and graphics to the right words

Good captions need accurate content, readable placement and the right timing. For narrated work, let the actual audio establish the timing, then place captions and graphics alongside the meaning they support.

01

Accept the audio before aligning it

The final recorded or generated narration determines when words are actually spoken. After changing the voice or speaking rate, check alignment again instead of assuming old timings remain valid.

Hypit’s upstream workflow can use WhisperX to obtain words and their timings. Availability depends on the project’s Runtime, Provider and configured services.

02

Emphasize only what matters

Avoid giving every word the same strong animation. Choose the nouns, numbers, turning points or answers viewers should remember, and reserve visual changes for those moments.

When product footage is already dense with information, captions can be restrained. Simpler images leave more room for text to explain.

03

Leave room for phones and platform controls

Buttons and description areas differ across platforms. Check readability in the destination platform’s preview instead of assuming one fixed margin will work everywhere.

  • Keep faces, product labels and important actions unobstructed.
  • Review at the actual publishing aspect ratio, not only in a large desktop preview.
  • Split long sentences into readable phrases and check punctuation and proper nouns.
  • Use an appropriate background or outline when the picture changes brightness.
04

Review timing in Studio

Once you have a usable Run and assets, open Studio to inspect the composition. The build.svrun filename below is an example; replace it with the actual Run in your project.

  • Play the composition and check when text appears, stays and disappears.
  • Pause at transitions and look for lingering elements from the previous shot.
  • Edit only properties exposed by the component, and confirm the changes save.
  • Watch the exported file after changes; preview and export need separate checks.
For your agent
hypit studio --run build.svrun
05

Leave feedback with a time and a clear action

Useful feedback names the time, object and desired change: “At eight seconds, the product name arrives late; show it when the narrator says it.” Studio’s Comments view can hold time-based feedback.

A graphic being visible does not mean every property can be edited by dragging. Controls depend on what the component exposes. Ask the agent to edit source files when necessary.

Source and scope

This is an independent guide, not an official Hypit instruction. Adapt the steps to your project environment.

Read the source documentation ↗
Next guideMake new versions by reusing accepted assets →