Typing [pause:5s] at the top and bottom of every chapter does not give you five seconds of room tone. It gives you renders with paragraph-sized gaps of uneven length, and a retailer's upload checker may then flag the files for a different reason than the one you set out to fix. Silence for distribution is a mastering job, and a script tag cannot do a mastering job.
Silence in narration is three different jobs. The script itself can ask for a breath. An editor can hold a real gap. A retailer's spec can ask for room tone at the head and tail of a file. VoxAnvil helps with the first job. It does not finish the third one for you.
Breaths that belong in the script
A listener needs air at a turn in the thought, not a hole in the file. You create that air with a period, a paragraph break, or a short pause tag.
The studio converts pause tags before speech is requested. [beat] and pause tags under 2 seconds, such as [pause:0.5s] and [pause:1s], become an ellipsis. Pause tags of 2 seconds or more, and [long-pause], become paragraph breaks. Use them when the scene actually changes. Do not sprinkle them to "make it cinematic." A cinematic hole in a headphone can sound like a dropout.
Chapter titles are their own decision. If "Chapter 4" should be spoken, leave it as words. If you only wanted a file named chapter 4, take the words out of the script and let the file name do that work. A spoken title plus a paragraph break is a clean opening. A spoken title plus a five-second tag is a guess.
Between scenes inside a chapter, a paragraph break is the default. A line of asterisks will be read if you leave it as characters. Replace a scene-break glyph with a blank line. If you need the listener to feel a larger shift, earn it with a sentence, not with a symbol.
What the studio will not mix in
Sound-effect tags are not silence and they are not room tone. A tag such as [sfx:rain:loop] can be recognized as a well-formed tag by Narration QA, and the speech path then removes it. It is not read aloud, and it is not laid under the voice. You will not get rain, and you will not get a noise floor, by writing the tag. If you want a sound bed, build it in an audio editor after you have a clean voice track. Do that only if the edition is allowed to have a bed. Some retailers want dry narration. Check their current rules rather than guessing from a toolbar.
The studio also does not claim to set integrated loudness, true peak, or a noise floor. Those are measurements on the exported file. The distribution workspace includes a checklist for ACX and Findaway that covers the kinds of file, loudness, and metadata questions those retailers publish. Treat the checklist as a reminder to go read the source. A checklist is not an acceptance letter. If a help page you saw last year quoted a peak level or a room-tone duration, confirm it on the retailer's site before you trim heads and tails. Specs move, and this article will not freeze an old number into your upload.
A simple chapter edge
Work the edges in this order:
- Script the opening sentence so it makes sense if the file starts there. No "as I was saying."
- Leave one paragraph break after a spoken chapter title, if you speak the title.
- Generate and listen to the first and last ten seconds. You are listening for a clipped word, a tag read aloud, or a huge hole.
- Export the audio and open it in an editor if you need a measured head or tail. Add or trim silence there, where you can see the duration. Do not go back and add another pause tag hoping the next render matches a spec sheet.
- Listen to the edited edge once. A trimmed head can cut a breath you liked. A long tail can feel like a mistake.
Suppose a chapter ends on the line "She locked the door." You want a beat, not a cave. You leave the period and a paragraph break, generate, and hear a natural stop. In the editor you add the head and tail your current retailer page asks for, then you listen to the file you will actually upload, not the file still sitting in the project. The project file is the performance. The edited file is the submission. Keep both, and do not overwrite the performance with a one-off trim you cannot explain later.
If the middle of the chapter has a hole, that is not a room-tone strategy. It is a join or a pause tag. See splits and joins and the listening pass. Fix the middle before you decorate the edges.
Honesty about polish
Professional audiobooks seem to have a rich silence, the way a studio booth does. A booth has a consistent noise floor because the room was quiet and the chain was the same all day. Separate speech requests do not invent that room. They invent takes. Your job is to keep the takes from having accidental holes, then to meet the written spec in an editor if the spec asks for something the generator does not measure.
Listeners forgive a plain, even voice. They do not forgive a chapter that starts with a blast of leftover countdown or ends by swallowing the last consonant. Those are the silences and the missing silences that matter. The rest is compliance, and compliance is a page you read on the retailer's site the week you upload.
Frequently Asked Questions
Q: Does [pause:5s] equal five seconds of room tone? A: No. In this studio a long pause tag becomes a paragraph break in the text that is sent to speech. Measure real silence in an editor after export.
Q: Should every chapter start with silence in the script? A: No. Start with the words. Add any required head or tail after you can see the waveform, and only to the length the current retailer page asks for.
Q: Can I use an ambience tag as a noise floor? A: No. Those tags are removed before synthesis. They do not create a noise floor. Do not upload a file you have not measured if the retailer asks for a measurement.
Q: Will the distribution checklist master my files? A: It points at the kinds of checks distributors publish. It does not render a mastered master, and it does not submit the book. You export, you measure, you upload.
Before uploading, play only the first and last two seconds of each file. Whatever is there, whether a hiss, a click or half a breath, is what the distributor's checker will hear too.