transcript.setEngine error text lists whisperLargeV3/whisperLargeV3Turbo as valid, but the handler rejects them

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

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
objective-c
Domain
api

Research direction

Open SpliceKitServer.m at SpliceKit_handleTranscriptSetEngine (~line 6851): the two error strings list whisper engines that the following if/else chain never handles. First run the transcript setEngine tool with whisperLargeV3 to confirm the rejection, then edit both strings (and the set_transcript_engine MCP tool description) so they list only fcpNative, appleSpeech, parakeetV3, parakeetV2. Done means every advertised engine is actually handled and the error text matches.

Written by the indexing model from the issue text.

Description

Summary

transcript.setEngine error messages list whisperLargeV3Turbo and whisperLargeV3 as valid engines, but the handler rejects them with "Unknown engine". Whisper is only wired into the Captions panel, not the transcript panel.

Evidence

SpliceKit_handleTranscriptSetEngine (SpliceKitServer.m ~line 6851):

if (!engineName) return @{@"error": @"engine is required ('fcpNative', 'appleSpeech', 'parakeetV3', 'parakeetV2', 'whisperLargeV3Turbo', 'whisperLargeV3')"};
...
} else {
    return @{@"error": @"Unknown engine. Use 'fcpNative', 'appleSpeech', 'parakeetV3', 'parakeetV2', 'whisperLargeV3Turbo', or 'whisperLargeV3'"};
}

Only fcpNative / appleSpeech / parakeetV3 / parakeetV2 are actually handled.

Suggested fix

Remove the Whisper engine names from both error strings (and from the set_transcript_engine MCP tool description, which only mentions fcpNative/appleSpeech), or add a SpliceKitTranscriptEngineWhisper that shells out to whisper-transcriber the same way the captions panel does.

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.