An unofficial PyTorch implementation of VALL-E
Go to file
2024-12-21 22:52:10 -06:00
data added extremely barebones vall_e.cpp so I can stop having to juggle this file around so much 2024-12-21 10:57:02 -06:00
docs exposed additional task (ns, sr, vc) (vc is experimental) 2024-12-20 11:15:29 -06:00
scripts agony 2024-12-21 22:52:10 -06:00
vall_e agony 2024-12-21 22:52:10 -06:00
vall_e.cpp agony 2024-12-21 22:52:10 -06:00
.gitignore crammed encodec.cpp in 2024-12-21 15:48:12 -06:00
LICENSE Rewrite init 2023-08-02 21:53:35 +00:00
README.md more fixes for local engine backend 2024-12-12 14:38:42 -06:00
setup.py added WER/SIM-O metrics, added APOLLO but I need to test it 2024-12-10 20:13:21 -06:00
vall-e.png Rewrite init 2023-08-02 21:53:35 +00:00

VALL'E

An unofficial PyTorch implementation of VALL-E (last updated: 2024.12.11), utilizing the EnCodec encoder/decoder.

A demo is available on HuggingFace here.

Requirements

Besides a working PyTorch environment, the only hard requirement is espeak-ng for phonemizing text:

  • Linux users can consult their package managers on installing espeak/espeak-ng.
  • Windows users are required to install espeak-ng.
    • additionally, you may be required to set the PHONEMIZER_ESPEAK_LIBRARY environment variable to specify the path to libespeak-ng.dll.
  • In the future, an internal homebrew to replace this would be fantastic.

Install

Simply run pip install git+https://git.ecker.tech/mrq/vall-e or pip install git+https://github.com/e-c-k-e-r/vall-e.

This repo is tested under Python versions 3.10.9, 3.11.3, and 3.12.3.

Pre-Trained Model

Pre-trained weights can be acquired from

  • here or automatically when either inferencing or running the web UI.
  • ./scripts/setup.sh, a script to setup a proper environment and download the weights. This will also automatically create a venv.
  • when inferencing, either through the web UI or CLI, if no model is passed, the default model will download automatically instead, and should automatically update.

Documentation

The provided documentation under ./docs/ should provide thorough coverage over most, if not all, of this project.

Markdown files should correspond directly to their respective file or folder under ./vall_e/.