SoniTranslate

Synchronized Translation for Videos. Video dubbing

Runssource: GitHubPythonApache-2.0commit 70b6390a413b

Python, Apache-2.0 licensed. The project labels itself: asr, audio processing, automatic dubbing, diarization, document translator, dubbing, speech to text and stt.

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

SoniTranslate installs and launches as a Gradio web app on 127.0.0.1:7860 in CPU mode, serving the full video-dubbing UI at HTTP 200.

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.24 (measured)
recorded runs
2
last tested
stars
1,431
forks
357
open issues
119
watchers
26
size
20 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 SoniTranslate, 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.

  • pyworld build fails: Python.h not found3 minutes
  • torchaudio.set_audio_backend/get_audio_backend missing in older torchaudio 2.3.13 minutes
  • pyannote-audio build requires pkg_resources (missing in modern setuptools)2 minutes
  • huggingface_hub HfFolder removed, then is_offline_mode missing2 minutes
  • torchmetrics/torchvision circular import (torch.library.register_fake)2 minutes
  • System Python is externally managed (PEP 668), pip refused1 minute
Install time
28 minutes
Cold machine to finish
52 minutes
Errors hit and fixed
10 hit, 10 fixed with no human help
How the result was proved
curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:7860 returned 200; full Gradio HTML interface returned (926204 bytes)
Model tokens used
140,132
Exact commit tested
70b6390a413b
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.

import torch; print('torch:', torch.__version__)
import torchaudio; print('torchaudio:', torchaudio.__version__)
import torchvision; print('torchvision:', torchvision.__version__)
\" 2>&1 | grep -v Warning" in /work/repo
 succeeded in 5851ms:
torch: 2.15.0+cpu
torchaudio: 2.11.1+cpu
torchvision: 0.29.2+cpu
Here is the summary of what was done and the final result:
tokens used
140,132
Here is the summary of what was done and 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.
  • Recovered from all 10 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 28 minutes to install, slower than the median of the 10 comparable projects Argusic has measured.

Of the 11 asr projects Argusic has installed and timed, SoniTranslate was the 10th fastest to reach a running state, and 8 of 11 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/3Runs100.000.24
Argusic Runner1/3Runs100.000.12

Topics (from GitHub)

asraudio-processingautomatic-dubbingdiarizationdocument-translatordubbingspeech-to-textsttsubtitle-to-speechtext-to-speechtranslate-audiotranslate-videotranslationttsvideo-dubbing

Embed the badge

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

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

Questions

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