aspeak

A simple text-to-speech client for Azure TTS API.

Runs with mockssource: GitHubRustMITcommit 98cd49d9b44c

Rust, MIT licensed. The project labels itself: aspeak, azure cognitive services, cli, python, speech synthesis, text to speech, tts and tts engine.

aspeak runs, with stand-ins for the services it depends on. An Argusic agent installed it in 4.2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

aspeak 6.1.0 builds and runs from source with PKG_CONFIG_PATH and LIBRARY_PATH workarounds; CLI text and SSML synthesis, stdout output, and offline subcommands (list-formats, list-qualities, --help, --version) all work; real Azure endpoint tests skipped due to missing credentials.

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

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
1
last tested
stars
495
forks
61
open issues
9
watchers
7
size
1 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 aspeak, 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.

  • alsa-sys build fails: libasound2-dev not installed (no root)0.5 minutes
  • Linker cannot find libasound.so symlink0.2 minutes
Install time
4 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
cargo test --lib -- parse::test net::test passed 5/5; aspeak text -o /tmp/t.wav 'Hello' against mock server produced valid WAV (RIFF/WAVE header, 364 bytes); aspeak text -o - 'Hello' produced valid WAV on stdout; aspeak ssml and list-qualities/list-formats also work; aspeak --version prints 6.1.0
Model tokens used
455,089
Exact commit tested
98cd49d9b44c
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

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

**Launch**: The binary runs — `./target/debug/aspeak --version` prints `aspeak 6.1.0`, `--help` pri…
**Tests**: 5 `net::test` unit tests passed. CLI verified against a mock HTTP server: text-to-file, …
**Errors**: Two blockers, both fixed — (1) `alsa-sys` needed `libasound2-dev` which isn't installed…
**Mock**: A Python HTTP server on `127.0.0.1:8765` returns valid 16-bit 16 kHz mono PCM WAV audio. …
tokens used
455,089
Here's a summary of everything I did and found.
**Install**: `cargo build --features binary` succeeded after fixing the `alsa-sys` build (extracted…
**Launch**: The binary runs — `./target/debug/aspeak --version` prints `aspeak 6.1.0`, `--help` pri…
**Tests**: 5 `net::test` unit tests passed. CLI verified against a mock HTTP server: text-to-file, …
**Errors**: Two blockers, both fixed — (1) `alsa-sys` needed `libasound2-dev` which isn't installed…
**Mock**: A Python HTTP server on `127.0.0.1:8765` returns valid 16-bit 16 kHz mono PCM WAV audio. …

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

  • Installed in 4.2 minutes.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 Runner1/3Runs with mocks92.000.04

Topics (from GitHub)

aspeakazure-cognitive-servicesclipythonspeech-synthesistext-to-speechttstts-engine

Embed the badge

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

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

Questions

Does aspeak run?
aspeak runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test aspeak?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 98cd49d9b44c. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test aspeak?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does aspeak take to install?
4.2 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 aspeak need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing aspeak?
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 aspeak?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion