> ## Documentation Index
> Fetch the complete documentation index at: https://www.latentcast.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Narration

> Changing what the presenter says — the three ways to ask, what follows automatically, and the one consequence to plan for.

Changing the <Tooltip tip="The script a scene is spoken from. Change it and the audio, timings and on-screen text follow."><strong>narration</strong></Tooltip> is the most consequential edit in a story,
because the words drive everything else: the audio, the timing of the on-screen text, the length of
the scene, and the presenter's lip movement.

The [tuning chat](/docs/guides/stories/tuning-chat) handles all of it, but it is worth knowing what you
are setting in motion.

## Three ways to ask

**A targeted tweak.** Name what to change and leave the rest alone.

> *"In scene 2, change 'significant savings' to 'up to 30% savings'."*

This is the safest kind. It keeps the surrounding sentences, so the on-screen text that was timed to
them stays where it was.

**A full rewrite.** Say what you want the scene to do differently.

> *"Rewrite scene 3 to lead with the customer result instead of the technology."*

You get better prose and you pay for it in timing: every anchor in the scene moves, so on-screen
events have to be placed again.

**Dictation.** Give the exact words you want spoken and they are used as written.

## What happens when you approve

The chat shows you the proposed text and what it expects to follow. On approval:

1. The new words are saved.
2. The scene is re-spoken in the presenter's voice.
3. On-screen events are re-timed to the new words. Anything the system could not place with
   confidence is flagged for you rather than guessed at, and shows a **Review timing** marker you
   clear once you have looked.
4. The scene's length is adjusted, and its neighbours accommodate it.
5. If the scene had an animated presenter, it returns to a still image.

That last point is the one to plan around.

<Warning>
  **Re-writing a scene sets its animated presenter aside.** The animation was lip-synced to the old
  words and no longer matches, so the scene falls back to the still image and the original animation
  is kept rather than destroyed. Re-animating takes several minutes and is never started without your
  say-so. Get the script right first, then animate.
</Warning>

## Length is guarded

A story is built to a target duration, and each scene has a share of it. Ask for something much
longer than the scene can hold and the chat will tell you, and offer to fit it. You can insist, and
the story simply runs longer.

## Undo

The whole change, including everything that cascaded from it, is one undo. If you would rather have
a marked point to return to, save a [checkpoint](/docs/guides/stories/tuning-chat) before you start.

## Next

<CardGroup cols={2}>
  <Card title="Events, presenter and scenes" href="/docs/guides/stories/events-and-scenes">
    On-screen text, presenter placement, and scene order.
  </Card>

  <Card title="Reviewing and rendering" href="/docs/guides/stories/reviewing-and-rendering">
    Check the result and make the video.
  </Card>
</CardGroup>