Back to App

Reader doesn't generate audio

If the Act On Cue reader highlights your lines but no sound comes out, or if the loading spinner spins indefinitely on a specific line, it is usually due to one of three reasons: content filtering, account credits, or browser audio settings.

1. Sensitive or harmful content

Some of our high-fidelity AI voices are powered by providers with strict safety filters. These filters automatically detect and block content that is flagged as:

  • Explicit content (Nudity/Sexual topics)
  • Harmful or violent language
  • Hate speech

If your script contains dramatic scenes involving violence, swearing, or intimate situations, Standard AI voices may refuse to generate the audio for those specific lines.

The Symptom: The reader speaks normal lines perfectly, but consistently skips or stays silent on lines containing strong language or adult themes.

The Fix: Switch to "Audio Guided" Voices

If you are working on a gritty or mature script, we recommend switching the character's voice to an Audio Guided voice.

Audio Guided voices are designed to be more flexible. They are much less sensitive to content filtering and will generate lines that Standard voices might block.

How to change the voice:

  1. Go to Settings -> Character Voices.
  2. Tap the character that is failing to speak.
  3. In the voice selection menu, look for the Audio Guided category.
  4. Select a new voice and try running the scene again.

2. Pauses or delays during the "First Run"

If you are running a scene for the very first time, you might notice pauses or a delay before the reader speaks.

This is normal. The app is generating the speech for your script in real-time.

  • The First Run: You may experience pauses while the system creates the audio for your lines.
  • Subsequent Runs: Will be fluid and instant.

Once the lines are generated, they are saved (cached) to your device. If you restart the scene or run it again, the reader will respond instantly without any loading time. Also, these lines will not cost any credits for playing again.


3. Check your Account Credits

Speech generation requires server resources. If the reader has stopped generating audio entirely for all lines and all characters, you may have run out of usage credits.

How to check:

  1. Go to your Account Settings.
  2. Look for the Subscription or Credits section.
  3. Ensure your account is in good standing and has available generation minutes.

If you are on a free tier or have hit a monthly limit, you may need to upgrade or top up to continue generating new lines.


3. Browser & Device Audio

If your credits are fine and the content is safe for work, the issue might be your device settings.

  • Check the Tab Mute: Ensure the browser tab isn't muted (look for a crossed-out speaker icon on the tab itself).
  • Bluetooth Hijack: If you have Bluetooth headphones connected (even if they are just sitting on the desk), the audio might be routing there instead of your speakers. Disconnect Bluetooth to test.
  • Browser Autoplay: Some browsers (especially Safari) block audio from playing automatically. Click anywhere on the page to "wake up" the audio context.

Still hearing silence?

If you have switched to an Audio Guided voice and confirmed you have credits, please contact support.