Feature request: reliable pause/silence control for Voice Design mode
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 37.8k
- Forks
- 4.3k
- Avg merge
- 7m
- Merged PRs (30d)
- 1
Description
Feature Request: Reliable pause/silence control in Voice Design mode
Context
When using VoxCPM2 in Voice Design mode (text description in parentheses, no reference audio) for long-form narration, sentence-to-sentence pacing is too tight — the next sentence begins almost immediately after a period, which is fatiguing for the listener.
I tried the following approaches to control pause duration. None is reliably effective:
What doesn't work
-
Explicit duration instructions in the Voice Design prompt — adding phrases like "take a one-second pause after every period" or "long pauses between sentences" into the parenthetical description does not produce measurable silence between sentences. The model does not interpret timing instructions semantically.
-
Inline parenthetical pause commands mid-text — inserting
(pause for 1 second)or similar in the middle of the input text causes those words to be spoken verbatim. Parentheses are only parsed as a style descriptor at the very start of the input, not as inline control tokens. -
Ellipsis + em-dash (
... — ...) between sentences produces slightly longer pauses than a plain period — better than nothing, but the difference is subtle and not nearly enough for comfortable narration pacing. It is also undocumented and pollutes the text for any downstream consumer (subtitles, transcripts, etc.).
Related existing issues
- #56 — "Speed parameter?" (open, maintainer: "we are considering adding this parameter")
- #210 — "Style control instructions ignored" (closed; clarified that Ultimate Cloning ignores style prompts — but this issue is about Voice Design, which is the style-controlled mode)
- #117 — "Support word and punctuation timestamps" (about output timestamps, not input pause control)
To my knowledge, no existing issue covers input-side pause duration control.
Proposal
Any of the following would resolve this use case — in rough order of preference:
-
SSML-style inline break tokens, e.g.
<break time="1000ms"/>or[pause:1s]. Deterministic, composable, and familiar from other TTS systems (Amazon Polly, Azure, ElevenLabs). -
Configurable punctuation→pause mapping on
model.generate(...), e.g.pause_map={".": 0.8, ",": 0.3, ";": 0.5}. Even if implemented as post-processing on the output waveform, this would unblock most users. -
Documentation on which input patterns reliably produce longer silences in the current model, so users can make informed choices without reverse-engineering.
Environment
- VoxCPM2 (
voxcpm==2.0.2) - macOS 15.x, Apple M4 Pro
- PyTorch 2.11.0, MPS backend, bfloat16
- Python 3.12
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at model.generate(...) and the Voice Design input handling described in the issue; compare the existing punctuation behavior with the proposed inline controls or pause mapping. Done requires a selected input-side pause mechanism that produces reliable pauses without speaking control text or polluting subtitles and transcripts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- audio-video-rtc, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100