JacobLinCool / JacobLinCool/whisper-cli
Possible caching idea for the server
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Hi.
I'm considering creating a transcriber server with transcription caching support, but based on the content of the uploaded media. Basically:
- Receive the uploaded file from the client
- Generate an MD5 hash based on the file content
- Transcribe the media and relate the transcription to the hash
- Save the hash to a database
This way, if the client sends the same media file, the cached transcription will be served. It will help avoid re-transcribing stuffs, especially for large media files, saving time and hosting costs.
Would this idea be useful for `whisper-cli` in server mode?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing whisper-cli's server-mode entry point and current transcription flow. Assess whether caching by uploaded media content hash and saving the hash and transcription in a database fit the project; a concrete scope, storage choice, and acceptance criteria are needed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100