Discofork
Repository brief

CorentinJ/Real-Time-Voice-Cloning

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T12:59:23.637Z
3mo ago

CorentinJ/Real-Time-Voice-Cloning

CorentinJ/Real-Time-Voice-Cloning is a Python-based open-source voice cloning repo for cloning a voice from a few seconds of audio and generating arbitrary speech in real time. It implements SV2TTS plus encoder, synthesizer, and vocoder components, and the repo is still maintained with recent fixes and packaging updates. It is very popular, with 59,571 stars and 9,415 forks.

GitHub
Loading tags...
Stars59,571
Forks9,415
Default branchmaster
Last pushed2026-03-09T10:31:58Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if multilingual voice-cloning experiments matter more than freshness or reliability. Prefer upstream if you want the better-maintained baseline and recent compatibility fixes.

Choose this fork only if the REPL workflow or CPU-mode tweaks are the main reason you are adopting it. For anything that depends on current fixes, packaging, or ongoing maintenance, upstream is the safer base.

Prefer this fork only if its setup shortcuts or legacy-environment tweaks solve a concrete problem for you; otherwise the much newer upstream is the safer base because this fork is materially older and missing recent maintenance.

Prefer this fork if your priority is Chinese dataset support in the encoder pipeline; prefer upstream if you want the most maintained, general-purpose version with newer fixes and packaging.

Choose this fork if your goal is Korean voice cloning and you value built-in Korean preprocessing over upstream freshness. Choose upstream instead if you want the broadest support, newer maintenance fixes, or a more general-purpose baseline.

Choose this fork only if the CPU-only workflow is the main goal. If you want an actively maintained baseline with newer install and compatibility fixes, upstream is the better choice.

Prefer this fork if you need German-oriented preprocessing and training conveniences. Prefer upstream if you want the more maintained baseline and the newer dependency/install fixes.

Choose this fork only if you specifically want the added sample voice files and can tolerate an old, largely unmaintained codebase. For active use, upstream is the better choice because it is much more current and has recent compatibility and packaging fixes.

Prefer this fork only if you need an unchanged older baseline. For most adopters, upstream is clearly better because this fork adds no visible capability and misses recent compatibility and packaging work.

Prefer upstream unless you explicitly want an untouched, older snapshot. This fork adds no visible capabilities, while lagging well behind upstream on maintenance and compatibility.