Batch Generation: Processing Long Content

Generating one episode is easy. A full audiobook, course, or season introduces a different problem: how do you keep every approved choice intact while you review hours of audio?

Vois gives long-form work a single local project for scripts, voice assignments, pronunciation rules, timeline edits, mastering, and export. That lets you work in reviewable batches and repair a sentence, chapter, or episode without disturbing the work you already approved.

Batching is not about firing everything off at once. It is about creating a production order that catches a bad setting before it becomes thirty bad chapters.

Divide content at natural boundaries

Chapters for an audiobook, episodes for a podcast, and lessons for a course are already useful batches. Keep each batch small enough to hear in one focused review session. For many projects, that means a 20 to 45 minute audiobook chapter, a 15 to 60 minute episode, or a 10 to 30 minute lesson.

Use clear names that let you identify a script, generated draft, and approved export without opening every file. A simple directory pattern can support your Vois project and delivery files:

MyProject/
├── 01-chapter-one/
│   ├── script.md
│   ├── generated/
│   └── final/
├── 02-chapter-two/
│   ├── script.md
│   ├── generated/
│   └── final/
└── settings/
    └── review-notes.md

This is an organizational example, not a configuration you need to run. The important part is the review trail: what changed, why it changed, and which version is approved.

Lock the creative decisions before volume

Finish the scripts before you commit to the batch. Editing text after generation is a reliable way to create needless rework.

Then choose the voice, baseline pace, export format, and mastering target in Vois. Test one complete representative chapter or episode. Listen on the devices your audience will use. Check difficult names with the pronunciation dictionary. If the test does not sound ready, change the setup now, not after the remaining batches are generated.

Use a staged production order

The safest first pass is staged:

1. Generate one representative batch in Vois.
2. Review voice contrast, pacing, pronunciation, and the mastering choice.
3. Approve the settings or revise them in the project.
4. Generate a small next group while reviewing the prior group.
5. Continue only after the recurring issues are resolved.

This hybrid sequence is faster than producing one batch at a time, but it protects you from discovering a core mistake after every chapter is complete. Keep a simple status table with script ready, generated, reviewed, issue, and approved columns. A specific note such as "Chapter 3, 12:45, correct Nguyen" is far more useful than "Chapter 3 has an issue."

Prompt your agent, then keep approval with the producer

An external coding agent can reduce clerical work through the Vois CLI. Ask it for a proposed plan and review it before it changes or exports anything:

Prompt your agent: "Inspect the current Vois long-form project and produce a batch plan grouped by chapter or episode. List unassigned speakers, repeated proper nouns, missing pronunciation entries, and batches that exceed 45 minutes. Do not generate audio, alter voice settings, export files, or delete anything. Wait for my approval."

Use this review flow:

1. Check the batch plan against the script and your delivery schedule.
2. Approve the voice assignments, pronunciation rules, and one test batch in Vois.
3. Ask the agent to prepare only the approved batch order.
4. Listen to each generated batch and record only the fixes that matter.
5. Approve the final mastering and exports after a complete transition check.

Listen for consistency, not just obvious errors

Someone must hear every second of a long-form production. In each batch, check pronunciation, pacing, text accuracy, and audio consistency. Periodically compare a later section to an early approved section. Long projects can drift in energy or rhythm even when individual files sound fine.

Vois makes a surgical fix practical: revise the affected text or pronunciation entry, regenerate the affected portion, and review it in the project timeline. Do not recreate a chapter because one word is wrong.

Protect the project between review sessions

Long productions have a mundane failure mode: people lose track of what was approved. Keep the source script, generated draft, review notes, and final delivery file clearly separated. Back up approved exports before a large regeneration pass. If you change a voice assignment, pronunciation entry, or mastering choice, write down the reason and the batches it affects.

Do not rely on filenames alone to explain a revision. A brief note such as "Episode 4, updated product name after client review" lets a collaborator understand why the audio changed months later. It also prevents an older, unapproved export from quietly becoming the delivery file.

When the production involves multiple people, agree on the handoff rule before generation begins. One person can prepare and flag the scripts, another can listen for continuity, and one producer should approve final export. Vois keeps the working audio in one project, but a clear human owner keeps the project moving.

Finish with an assembled-project review

Before delivery, listen across boundaries. A chapter that sounds right alone can be too quiet after the previous chapter, or it can start too abruptly. Confirm the mastering target, format, metadata, and platform requirements only after the complete sequence is assembled.

Long-form work rewards a boring system: one approved setup, small reviewable batches, precise notes, and final checks that happen before publication. Get started with Vois to keep that system in one local production studio, then review pricing when your content volume begins to grow.

The Vois Team