TakeCriptProcessing stuck
What to do when project processing takes too long
Last updated: 2026-03-10
Processing stuck
Processing runs in the background and includes transcription, silence detection, and script matching. Here is what to do if it seems stuck.
Expected processing times
| Total footage duration | Approximate time |
|---|---|
| Under 5 minutes | 1-2 minutes |
| 5-15 minutes | 2-5 minutes |
| 15-30 minutes | 5-8 minutes |
| Over 30 minutes | 8-15 minutes |
These are estimates. Actual times depend on audio quality, number of clips, and current server load.
Troubleshooting steps
Refresh the page
Processing happens in the background, so the status may not update in real time. Refresh the page to see the latest status.
Wait a few more minutes
If your clips total more than 15 minutes of footage, processing can take up to 15 minutes. The transcription step is usually the slowest part.
Check the project status
Go back to the dashboard and click on your project. If the status shows an error, the processing failed and you can try reprocessing from the project settings.
You can safely close the browser tab while processing runs. Your project will continue processing in the background. Come back any time to check the status.
If processing fails repeatedly, the issue may be with the audio quality of your clips. Make sure your clips have clear, audible speech.
Low coverage or unexpected results
If processing completes but the results are not what you expected (low coverage, duplicated segments, or missing content), the most common cause is a mismatch between your script and what you actually said.
Edit your script and reprocess. If you improvised, rephrased, or added extra context during recording, update your script blocks to reflect what you actually said, then reprocess the project. This is the fastest way to improve results.
"No speech detected" warning
During processing, some clips may show an orange warning icon with the label "No speech detected". This means TakeCript analyzed the clip and determined it contains no spoken audio.
Why does this happen?
- The clip has only ambient sound, music, or silence — no voice.
- The clip was accidentally classified as A-roll or Voice-over when it should be B-roll.
What does it mean for your project?
- Clips marked as "No speech detected" are skipped during matching. Since there is no speech to compare against your script, they are not included in the final timeline.
- This does not block the rest of your project. All other clips continue processing normally.
- If all your clips are marked as "No speech detected", processing will fail because there is nothing to match against your script.
What can you do?
- If the clip really has no voice, no action is needed — TakeCript handled it correctly.
- If you think the clip does have speech, check the original file. Very low volume or heavy background noise can prevent speech detection.
- You can reclassify the clip as B-roll from the project page so it is not sent for transcription on future processing runs.
Was this article helpful?