Troubleshooting
Having issues with a scene, script, or voice performance? Find your issue below.
Script issues
Line came in as the wrong type, or the wrong speaker? Hover the line for its [⋯] menu and use Turn into to reassign the type, or click the character's name above the line to fix the speaker. Keep a character's name spelled identically everywhere, otherwise the app treats it as two different characters. See Line types for what each type means.
Voice and audio issues
Voice sounds robotic or flat? Add punctuation and clearer sentence structure, this shapes delivery for every voice type. For Dramatic voices you can also add speech instructions. See Understanding voice types.
No audio on one specific line? Some voices have safety filters that occasionally block strong language or mature content. Tap the line's refresh icon to regenerate it, or try a Consistent voice instead. Still silent? Contact support.
No audio at all, on every line? Check your Available credit in Account Settings, you may be out of credit or on a limit. Also check the browser tab isn't muted, disconnect any Bluetooth audio device that might be stealing playback, and click anywhere on the page first (Safari blocks autoplay until you interact with it).
Pauses the first time you run a scene? Normal, audio is generating in real time. Cached lines play instantly on later runs.
A voice is too fast or slow? Set Speed (0.75x-2x) in the Reader settings before you start, this applies to every voice at once. Locked once a session is running. For finer control per line, see Voice customization.
Speech recognition issues
Applies to Perform mode only, the paid, speech-recognition session type. Free Listen sessions don't use your microphone at all, see Listen mode.
Microphone permission blocked
- "Microphone access is required" - allow mic access when prompted, or re-enable it in your browser's site settings.
- "No microphone found" / "Microphone blocked by your operating system" - your OS is blocking the browser. Check System Settings → Privacy & Security → Microphone (macOS) or Settings → Privacy → Microphone (Windows).
Recognition cutting in and out? Check your mic isn't muffled, project your voice if you're a few feet from the device, and cut background noise (fans, traffic, echo). Still unreliable? Refresh the page, restart the browser, or try the mobile app on iOS, it handles the mic natively.
Cue not recognized
The reader can trip up on a specific line, usually because of wording, not your hardware:
- Match what the reader hears - the app shows what it thought you said. Edit your line to match that instead of what you actually said (e.g. "cigs" heard as "secs" → change the line to "secs").
- Trim filler words - "uh", "hmm" and similar often don't register and can throw off cue detection.
- Simplify or delete the line and add a pause instead, if it consistently fails.
- Switch that line to a timer-based turn to bypass speech recognition for it entirely, see choosing how a line advances.
Still stuck on one line? Contact support with the line, it helps us improve recognition.
My lines are skipped
Check the line is typed as Dialogue, not Direction, non-Dialogue lines aren't read and won't wait for your cue. See Line types.
Reader is slow to respond
By default it waits for your speech-recognition cue. For exact timing instead, switch the line to a timer-based turn, see choosing how a line advances. If you're sticking with voice cues, trimming the last word or two off your own line can make the reader jump in faster.
Browser and device issues
We support Google Chrome (and Chromium browsers like Brave, Edge, Arc) and Safari. Other browsers may partly work but aren't tested.
On mobile, some features (line learning, teleprompter, long scripts) work best on desktop, or use the mobile app for the best phone/tablet experience.
Microphone access denied? See Microphone permission blocked above.
Still stuck?
Contact support with your browser/device, what you were trying to do, and any error message, the more detail, the faster we can help.