RealtimeTTS

Converts text to speech in realtime

Runssource: GitHubPythonApache-2.0commit 50abd79cfb60

Python, Apache-2.0 licensed. The project labels itself: python, realtime, speech synthesis and text to speech.

RealtimeTTS runs. An Argusic agent installed it in 12.4 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

realtimetts 0.8.10 installed and built wheel+sdist; 369 of 380 tests pass covering BaseEngine, alignment, language router, sentence splitting, streaming, stream player, release guard (except ssh-keygen), and Qwen studio; Qwen server starts and fails only on CUDA GPU requirement; pyttsx3 SystemEngine requires espeak

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 92.7 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
92.7 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
2
last tested
stars
4,058
forks
420
open issues
131
watchers
37
size
139 MB
created
last push

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.

Time lost to each failure while testing RealtimeTTS, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • PyAudio failed to build: missing python3-dev and portaudio19-dev headers (no root access)2 minutes
  • realtimetts[system] install failed because pyaudio build dependency failed1 minute
  • ssh-keygen not available - release guard CLI attestation test fails
  • Qwen server requires CUDA GPU (libcuda.so.1 not found)
  • SystemEngine pyttsx3 requires espeak/espeak-ng (no system TTS in container)
Install time
12 minutes
Cold machine to finish
13 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
pytest tests/ --ignore=tests/test_callbacks.py --ignore=tests/test_on_audio_chunk_callback.py: 369 passed, 1 failed, 10 skipped
Model tokens used
125,389
Exact commit tested
50abd79cfb60
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

 succeeded in 0ms:
exec
/bin/sh -lc "cd /work/repo && /tmp/tts_venv/bin/python_tts -c \"
import json
s = '{\\\"install_succeeded\\\": true, \\\"launch_succeeded\\\": true, \\\"install_minutes\\\": 12.…
d = json.loads(s)
print('Valid JSON:', d['install_succeeded'], d['test_depth'])
\"" in /work/repo
 succeeded in 0ms:
Valid JSON: True tier1_real
tokens used
125,389

Replay 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.
  • Recovered from all 5 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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 12.4 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.

Of the 5 python projects Argusic has installed and timed, RealtimeTTS was the 4th fastest to reach a running state, and 5 of 5 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks85.330.14
Argusic Runner1/3Runs100.000.09

Topics (from GitHub)

pythonrealtimespeech-synthesistext-to-speech

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/RealtimeTTS.svg)](https://argusic.com/subject/realtimetts)

Questions

Does RealtimeTTS run?
Yes. RealtimeTTS runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test RealtimeTTS?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 50abd79cfb60. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test RealtimeTTS?
The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does RealtimeTTS take to install?
12.4 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 RealtimeTTS need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing RealtimeTTS?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does RealtimeTTS compare with the alternatives?
Of the 5 python projects Argusic has installed and timed, RealtimeTTS was the 4th fastest to reach a running state, and 5 of 5 reached one at all.
Where is the evidence for RealtimeTTS?
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.

Discussion