Turn PickScribe into a transcript source for existing media: drop or pick an audio/video file, get a transcript using the whisper.cpp engine that's already shipped — no new STT dependency.
Why
- The engine, model management, and history storage all exist; only the input path is new.
- Common ask for dictation apps, and it makes PickScribe the entry point for video-editing workflows (captions/subtitles from recorded footage).
Scope
Out of scope
- Speaker diarization
- Editing/cutting media
- Batch/folder transcription (follow-up if wanted)
Validation
- Transcribe a short WAV, an MP3, and an MP4 (audio extracted); verify History entry + all three export formats
- Kill/cancel mid-transcription leaves no orphan temp files
- Local-only mode: no network calls during file transcription
cargo test / existing suite stays green
Current status: Planned
Next action: not scheduled — created from the ai-video-editing research session (agents need transcripts of recorded footage; PickScribe already has the engine)
Turn PickScribe into a transcript source for existing media: drop or pick an audio/video file, get a transcript using the whisper.cpp engine that's already shipped — no new STT dependency.
Why
Scope
ffmpegis missingstt.rspath (transcribe_with_cancel), with progress + cancel in UI (files are much longer than dictations)--output-srt/--output-vtt); word-level timestamps where the engine supports itOut of scope
Validation
cargo test/ existing suite stays greenCurrent status: Planned
Next action: not scheduled — created from the ai-video-editing research session (agents need transcripts of recorded footage; PickScribe already has the engine)