whisper-transcriber binary not installed by patcher, but Captions panel defaults to Whisper

Open Beginner friendly
#109 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
objective-c, swift

Research direction

Start with the patcher/make deploy step that currently copies parakeet-transcriber into ~/Applications/SpliceKit/tools/ and add whisper-transcriber to that same install list, building it via swift build -c release in tools/whisper-transcriber. Then look at -[SpliceKitCaptionPanel transcriberBinaryPathForName:] to see where discovery fails and surface a clearer error. Done means a fresh install finds the binary in the tools dir and a caption batch transcribes without manual copying.

Written by the indexing model from the issue text.

Description

Summary

The Captions panel defaults to Whisper (SpliceKitCaptionEngine default = whisperLargeV3), but the whisper-transcriber binary was not installed by the patcher into any of the searched locations, so caption transcription fails out of the box on this install.

Evidence

Search paths checked by -[SpliceKitCaptionPanel transcriberBinaryPathForName:]:

  • ~/Applications/SpliceKit/tools/ → contains only parakeet-transcriber, silence-detector, ffmpeg, yt-dlp
  • ~/Library/Application Support/SpliceKit/tools/ → does not exist
  • ~/Library/Caches/SpliceKit/tools/whisper-transcriber/.build/release/ → does not exist

The Whisper CoreML models were downloaded (~/Library/Application Support/SpliceKit/Models/whisper, ~3 GB, large-v3_turbo), so the user had run Whisper at some point — but the binary itself was missing from the tools dir. Building from tools/whisper-transcriber (swift build -c release) and copying the binary to ~/Applications/SpliceKit/tools/ fixed discovery.

Suggested fix

Have the patcher (and/or make deploy) install whisper-transcriber alongside parakeet-transcriber in ~/Applications/SpliceKit/tools/, and/or surface a clearer error in the Captions panel when the selected engine's binary is missing (it currently just fails the batch with a generic error).

Dominant language
Objective-C
Stars
208
Forks
37
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elliotttate/SpliceKit

All issues in elliotttate/SpliceKit

Similar issues

More Objective-C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.