whisper-ctranslate2
Whisper command line client compatible with original OpenAI client based on CTranslate2.
Runssource: GitHubPythonMITcommit 7c06913255be
Python, MIT licensed. The project labels itself: openai , openai whisper, speech recognition, speech to text and whisper.
whisper-ctranslate2 runs. An Argusic agent installed it in 5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
whisper-ctranslate2 installed in venv, 17 unit tests pass, CLI transcribes audio files in Catalan on CPU (tiny model) producing txt/srt/vtt/tsv/json output correctly
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96.7 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- externally-managed-environment: pip install blocked by PEP 6682 minutes
- av>=19 broke faster-whisper: open() got unexpected keyword argument metadata_errors2 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 1 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- whisper-ctranslate2 e2e-tests/gossos.mp3 --model tiny --device cpu --compute_type float32 --output_dir /tmp/whisper_test_output --verbose False exited 0 and produced gossos.txt with 5 lines of Catalan transcription, plus matching .srt, .vtt, .tsv, .json files
- Model tokens used
- 49,962
- Exact commit tested
- 7c06913255be
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
],
'test_depth': 'tier1_real',
'notes': 'All 17 unit tests pass. CLI transcription works end-to-end on CPU with tiny model pro…
'verified_how': \\\"whisper-ctranslate2 e2e-tests/gossos.mp3 --model tiny --device cpu --comput…
'final_state': 'whisper-ctranslate2 installed in venv, 17 unit tests pass, CLI transcribes audi…
}
print(json.dumps(result))
\"" in /work/repo
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 5, "errors": [{"msg": "ext…
tokens used
49,962Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 5 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
openai-openai-whisperspeech-recognitionspeech-to-textwhisper
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/whisper-ctranslate2)Questions
- Does whisper-ctranslate2 run?
- Yes. whisper-ctranslate2 runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test whisper-ctranslate2?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7c06913255be. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test whisper-ctranslate2?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does whisper-ctranslate2 take to install?
- 5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does whisper-ctranslate2 need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing whisper-ctranslate2?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for whisper-ctranslate2?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.