Skip to main content

Fix generation problems

Use these checks when a preview or full project does not finish, produces no audible sound, or leaves an unclear credit result. A failed display does not by itself prove that credits were refunded.

Check the project state first​

  1. Note whether you started a single-section preview or Generate all sections and play audio.
  2. Check each section for a visible processing or failure status and read any error message.
  3. Confirm the script is not empty, each section has a selected voice, and the voice language matches the text.
  4. If some sections succeeded, keep them. The editor can retain successful sections when others fail; a stitching failure can also leave paragraph audio available.

Recover from a settled editor error​

Use these steps only after the editor has stopped processing and displayed an error. For a message that one or more sections could not be generated, keep successful sections, correct the indicated issue, then select Generate all sections and play audio. The editor retries sections without audio and reuses retained section audio when assembling the result.

For The final audio could not be stitched together, the section audio is retained. Select Generate all sections and play audio to assemble the result again from the retained sections.

These editor recovery steps do not apply to REST or MCP requests; follow their separate API or assistant guidance. A still-running request, timeout, disconnect, or unclear outcome is not a settled editor error. Wait and check whether audio appeared in the section or player, inspect project and usage state, and contact support if the outcome remains unclear. Do not blindly resubmit an uncertain paid request.

If audio is silent​

  • Confirm the player is not muted and the device volume is audible.
  • Try the section preview and the full-project player to isolate the issue.
  • Check another browser tab or local audio file to confirm the device can play sound.
  • Reload only after noting the project state; reopen the project and verify whether generated audio remains available.

Check credits safely​

Credits are character-based. Cloned-voice generation uses twice the input-character amount. Team members may be drawing from a shared team allowance even when their personal counter does not show the shared total. For API requests, only an explicit quota_status: refunded confirms a refund; an unknown or absent status needs investigation. Do not automatically resubmit an uncertain request.

If the status and credit change remain unclear, capture the project name, approximate time, affected section, and displayed error, then contact Acoust support. Do not send passwords, API keys, or verification codes.

Related: Generate audio · Credit usage overview