abogen

Generate audiobooks from EPUBs, PDFs and text with synchronized captions.

Runssource: GitHubhomepagePythonMITcommit 08e2ee8b85bb

Python, MIT licensed. The project labels itself: audiobook, audiobooks, content creation, content creator, ebook, epub, epub converter and kokoro.

abogen runs. An Argusic agent installed it in 18 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

All 1592 tests pass, the Flask web UI serves HTTP on port 8808, and the PyQt6 desktop GUI launches on the virtual display.

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

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
2
last tested
stars
6,235
forks
500
open issues
52
watchers
30
size
7 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.

Install time
18 minutes
Cold machine to finish
13 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
QT_QPA_PLATFORM=offscreen python -m pytest tests/ -q --tb=no returned 1592 passed, 0 failed; curl http://127.0.0.1:8808/ returned 200 with dashboard HTML; abogen-pyqt started window on DISPLAY; abogen-web server started and served requests
Model tokens used
112,766
Exact commit tested
08e2ee8b85bb
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.

/bin/sh -lc 'cd /work/repo && . /tmp/abogen_venv/bin/activate && python -m pytest tests/ -q --tb=no…
 succeeded in 719ms:
Fatal Python error: Aborted
Aborted (core dumped)
exec
/bin/sh -lc 'cd /work/repo && . /tmp/abogen_venv/bin/activate && QT_QPA_PLATFORM=offscreen python -…
 succeeded in 128412ms:
1592 passed, 41 warnings in 125.96s (0:02:05)
All 1592 tests pass. Here's the final result:
tokens used
112,766
All 1592 tests pass. Here's the final result:

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.
  • Installed in 18 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • 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.
  • Following its own README: the documented path worked with nothing to fix.

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/3Runs100.000.06
Argusic Runner1/3Runs100.000.13

Topics (from GitHub)

audiobookaudiobookscontent-creationcontent-creatorebookepubepub-converterkokorokokoro-82mkokoro-ttsllmmedia-generationnarratorspeech-synthesissubtitlestext-to-audiotext-to-speechttsvoice-conversionvoice-synthesis

Embed the badge

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

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

Questions

Does abogen run?
Yes. abogen runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test abogen?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 08e2ee8b85bb. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test abogen?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does abogen take to install?
18 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 abogen need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing abogen?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for abogen?
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