openlrc

Transcribe and translate voice into LRC file using Whisper and LLMs (GPT, Claude, et,al). 使用whisper和LLM(GPT,Claude等)来转录、翻译你的音频为字幕文件。

Runs with mockssource: GitHubhomepagePythonMITcommit 7b7f6186c34c

Python, MIT licensed. The project labels itself: auto subtitle, faster whisper, lyrics, lyrics generator, openai api, openlrc, python and speech to text.

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

openlrc 1.7.0a2 is installed and built in a Python 3.12 venv; all 186 mock-based unit tests pass; the httpx/httpx2 compatibility bug in ClaudeBot and GPTBot constructors is fixed

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.06 (measured)
recorded runs
1
last tested
stars
684
forks
52
open issues
5
watchers
11
size
9 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 openlrc, 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.

  • anthropic v1.14.0 and openai v2.54.0 use httpx2 internally, rejecting httpx.Client(proxy=...) passed in ClaudeBot and GPTBot constructors with TypeError5 minutes
Install time
6 minutes
Cold machine to finish
27 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
python -m pytest tests/ -k 'not (Live or test_translate_live)' (167 passed) + tests/test_openlrc.py (19 passed) = 186 passed, 9 skipped, 0 failed; also verified lightweight imports and CLI (openlrc gui) work
Model tokens used
619,768
Exact commit tested
7b7f6186c34c
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.

tests/test_openlrc.py::TestLRCer::test_multiple_audio_transcription_translation
tests/test_openlrc.py::TestLRCer::test_multiple_audio_transcription_translation
tests/test_openlrc.py::TestLRCer::test_multiple_audio_transcription_translation
tests/test_openlrc.py: 2688 warnings
================ 19 passed, 2691 warnings in 173.07s (0:02:53) =================
All tests are verified. Let me compile the final summary
exec
/bin/sh -lc 'cd /work/repo && echo "Total test summary: 186 passed, 9 skipped, 0 failed across all …
 succeeded in 0ms:
Total test summary: 186 passed, 9 skipped, 0 failed across all 16 test files (excluding 6 Live API …
tokens used
619,768

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 6 minutes.
  • Recovered from all 1 error 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.06

Topics (from GitHub)

auto-subtitlefaster-whisperlyricslyrics-generatoropenai-apiopenlrcpythonspeech-to-textsubtitle-translationtranscribevoice-to-textwhisper

Embed the badge

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

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

Questions

Does openlrc run?
openlrc runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 6 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test openlrc?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7b7f6186c34c. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test openlrc?
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 openlrc take to install?
6 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 openlrc need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing openlrc?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for openlrc?
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