Likely causes (and quick checks) based on our docs:
You limited the dub to a range. In both the UI and API you can dub only a selected portion; if a start/end range of ~0–4s is set, only that slice is processed. In the API, this is controlled by start_time and end_time. Remove these or set them to the full duration. In the UI, ensure you didn’t select only a short portion. (elevenlabs.io)
Only the first clip was generated. In Dubbing Studio, audio generation is per clip and defaults to Fixed Generations; if later segments are stale or ungenerated, the render can appear short. Use “Generate Stale Audio” (or regenerate affected clips) so the entire timeline has audio. (elevenlabs.io)
If a previous render was partial, re-render. There’s a Render endpoint to regenerate audio/video for specific languages within a dubbing project, which also auto-fills missing transcriptions/translations. (elevenlabs.io)
Sanity check limits: the UI supports uploads up to 500 MB and 45 minutes (API up to 1 GB and 2.5 hours). If your source exceeds limits or was clipped on import, only part may process. (elevenlabs.io)
If you can share whether you used the UI or API (and if any start/end range was set), I can point you to the exact steps to fix. (elevenlabs.io)
void smelt
chrome bloom