YuzuLingo vs Video Subtitler (KarinBrisker)
YuzuLingo stays in the browser. You cover burned-in subtitles on the video you are already watching, including YouTube, Bilibili, and other web players. There is no script to run and no video file to start from. Turn on Interact to read the burned-in line on your device, with furigana or pinyin when the language has them. Show that text always, on hover, or while you hold a hotkey.
Video Subtitler is KarinBriskerās Python app, in the repo Video-Subtitler. You give it a local video. FFmpeg pulls out the audio, then Whisperās base model transcribes it on your machine, on a GPU when CUDA is available and on the CPU otherwise. It writes an SRT and a VTT. If the output language differs, googletrans translates the transcript, and that call goes to Google. The README acknowledgements name Google Cloud Translation. The script uses the googletrans package. FFmpeg then burns the subtitles into a new video file. There is a command line and a Gradio demo, and the README points at a Hugging Face Space. The README says you can leave the input language unset so Whisper detects it. The transcribe call in the code does not pass that language through, and it defaults to English. The README was rewritten about 3 months ago. The Python files last changed about 3 years ago. There is no release. MIT license.
Where each one fits
| Feature | YuzuLingo | Video Subtitler |
|---|---|---|
| Install in the browser, no script to run | ||
| Cover burned-in subs while a web video plays | ||
| No video file to start from | ||
| Read that burned-in line while the web video plays, on your device | ||
| Furigana or pinyin on that line | ||
| Show that text always, on hover, or while you hold a hotkey | ||
| Transcribe the speech in a local video into an SRT and a VTT | ||
| Speech-to-text stays on the device | ||
| Translate that transcript | ||
| Burn those subtitles into a new video file | ||
| Add the line to an Anki deck |