Skip to content

feat: add resume-from-interruption support for long audio transcriptions - #1

Merged
strawb3rry8ear merged 1 commit into
DrJuChunKoO:mainfrom
tc3oliver:feat/resume-transcription
Jun 12, 2026
Merged

strawb3rry8ear merged 1 commit into
DrJuChunKoO:mainfrom
tc3oliver:feat/resume-transcription

Conversation

@tc3oliver

Copy link
Copy Markdown
Contributor

Summary

  • Use deterministic temp directory naming (md5 of file path) instead of Date.now(), so the same audio file always maps to the same temp directory
  • Save completed chunk results to progress.json after each chunk is transcribed (with atomic write to prevent corruption)
  • On re-run, detect previous progress, skip already-completed chunks, and resume from where the last run stopped
  • Skip discoverSpeakers on resume to save API calls and avoid inconsistent speaker lists
  • Validate chunk indices on resume (handles cases where the audio file changed but kept the same name)
  • Add --clean flag to manually discard saved progress
  • Only clean temp directory on successful completion; preserve it on error so users can resume

Motivation

When transcribing long audio files (1+ hours), an API timeout or network interruption means losing all progress and starting over. This is especially painful when most chunks are already done.

Test plan

  • Verify fresh run still works end-to-end
  • Interrupt a transcription mid-way and re-run to confirm it resumes correctly
  • Test --clean flag clears the temp directory
  • Test with a corrupted progress.json (should warn and start fresh)
  • Verify --clean does not trigger a new transcription
  • Verify temp directory is cleaned up after successful completion

Use deterministic temp directory naming (md5 of file path) and
progress.json to track completed chunks. On re-run, skip already
transcribed segments and continue from where the previous run stopped.

Add --clean flag to manually discard saved progress.
@strawb3rry8ear
strawb3rry8ear merged commit f4e3cf2 into DrJuChunKoO:main Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants