whatmodel.sh / tts / Vevo (Amphion)

Vevo (Amphion) is an open-weights text-to-speech model from Amphion (CUHK-Shenzhen), released December 2024. Its published size is 1.32B parameters. Licence: cc-by-nc-4.0.

Catalogue identity notes

amphion/Vevo (vq8192 tokenizer, PhoneToVq8192 AR model, Vq8192ToMels flow matching, vocoder), the ICLR 2025 Vevo 1.0 release; distinct from Vevo1.5 and Vevo2.

Model information sources

· Parameter count ↗

OUR SUM of the maker-stated components on the official card for the Vevo-TTS path: PhoneToVq8192 AR transformer (740M) + Vq8192ToMels flow-matching transformer (330M) + Vocos-based vocoder (250M) = 1.32B. The vq8192 content-style tokenizer is not sized and is excluded. If a single stated figure is preferred, the AR model alone is 0.74.

46.2±3.1#77 of 118 text-to-speech modelsfrom 9 benchmark results across 4 sources

Score within the Vapi Humanness · Bradley–Terry rating, 2026-09-25 snapshot comparison set only.

$ how it compares

The text-to-speech models ranked either side of Vevo (Amphion), out of 148 with a score, then more from Amphion (CUHK-Shenzhen).

#modelscorewhereRAMreleased
95Amphion VALL-E (LibriLight 6k) Amphion (CUHK-Shenzhen)47±14local~1.6GB2024-01
96Piper (en_US lessac medium) Open Home Foundation (Piper)47±5local~0.1GB2023-06
97Vevo (Amphion) Amphion (CUHK-Shenzhen)46±3local~6.8GB2024-12
98Qwen3-TTS 12Hz 0.6B CustomVoice Alibaba (Qwen)46±6comparison only2026-01
99Dia2 2B Nari Labs45±6local~8.1GB2025-11
more from Amphion (CUHK-Shenzhen)
53MaskGCT Amphion (CUHK-Shenzhen)59±1local~6.6GB2024-10
121Amphion VALL-E v2 recipe (MLS) Amphion (CUHK-Shenzhen)36±3local~2.9GB2024-06
146Amphion NaturalSpeech 2 (LibriTTS) Amphion (CUHK-Shenzhen)14±3local~1.7GB2023-12

see all text-to-speech models · find the ones that fit your machine

$ what it's good at

other tests9 not in a task · 96% of its score
testresultvs the others in its rundifficultycountswhy
TTSDS2 listening test · speaker-similarity MOS (4 English domains)4.01 / 5 ✎▅·█▅▅·█▃▃▅·▅ beats 14/17easy · avg 4.03 / 5▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 61%at its level
SAP voice reconstruction · human BWS reconstruction preference836.0 ✎█▄█····▄··▄▄ beats 2/7avg 995▇▇▇▇ 11%typical
TTSDS2 listening test · naturalness MOS (4 English domains)3.36 / 5 ✎▅··▃▅··▅█▅██ beats 16/17medium · avg 3.30 / 5▇▇▇ 6.3%blunt · at its level
TTSDS2 multilingual benchmark · Chinese overall (YouTube, 2025 round)86.8% ✎▄▄·····▄··▄█ beats 2/5very easy · avg 88%▇▇ 6.1%blunt
TTSDS2 multilingual benchmark · English overall (YouTube, 2025 round)86.5% ✎▂▂█·▂·█▆▂·▄▂ beats 10/17very easy · avg 89%▇▇ 4.1%blunt
CodecMOS-Accent VCTK voice clone · human speaker-similarity MOS (S-SPK-SIM)4.48 / 5 ✎▄▄█·▄▄▄▄▄·▄█ beats 9/11easy · avg 4.20 / 5▇ 2.6%blunt
CodecMOS-Accent VCTK voice clone · human naturalness MOS (S-NAT)3.66 / 5 ✎█··▄▄██▄·▄▄▄ beats 3/11easy · avg 3.99 / 5▇ 2.5%blunt · at its level
SAP voice reconstruction · TTSDS dual-reference distributional score84.2% ✎▄····▄▄▄▄▄·█ beats 4/7very easy · avg 86%▇ 1.9%blunt
1 more test
testresultvs the others in its rundifficultycountswhy
SAP voice reconstruction · WER of reconstructed speech (Whisper turbo)34.8% ✎▄▄▄··█▄··▄·▄ beats 1/7avg 17%▇ 0.2%blunt · noisy

$ where to run it

Other ways to run it

  1. Run it as published · needs ~6.78 GB · from github.com/open-mmlab
    git clone https://github.com/open-mmlab/Amphion.git && cd Amphion && conda create -n vevo python=3.10 && conda activate vevo && pip install -r models/vc/vevo/requirements.txt && python -m models.vc.vevo.infer_vevotts

Official weights and documentation: huggingface.co/amphion ↗

$ how the score was worked out · TTSDS2 listening test results… 68%, An Evaluation Framework for T… 13%, TTSDS2 multilingual benchmark… 10% and 1 more

Each result implies a score on its own, after adjusting for how hard its test is and who ran it. The score is their weighted average, with a small pull toward the middle for thinly tested models. Each test's weight is its counts column above; here it's added up by who ran the tests. How it works

$ improve this page

Use a short GitHub form or edit the data through a pull request. Every number needs a source; here's which ones we can use.

data updated · sources and licences · json