moss-tts-nano-cli
One-command zero-shot voice cloning with the MOSS-TTS-Nano-100M model, powered by mlx-audio.
Features
- No manual setup:
uvx moss-tts-nano-cliinstalls the environment automatically. - Lazy model download: the model is fetched from Hugging Face on first use.
- Voice cloning: pass a reference WAV and text to synthesize speech in that voice.
- Apple Silicon optimized: runs on MLX.
Requirements
- Python 3.12+
- macOS with Apple Silicon (MLX backend)
- uv (recommended)
- FFmpeg (used indirectly by audio tooling)
If your
uvis configured to use a PyPI mirror that has not synced the package yet, run with the official index:uvx --index-url https://pypi.org/simple moss-tts-nano-cli --help
Install
uv tool install moss-tts-nano-cli
Or run without installing:
uvx moss-tts-nano-cli --help
Usage
Clone a voice
moss-tts-nano-cli clone \
--ref ./my_voice.wav \
--text "Hello, this is my cloned voice speaking." \
--out output.wav
The first run downloads mlx-community/MOSS-TTS-Nano-100M and the audio tokenizer into the Hugging Face cache (~/.cache/huggingface).
Eagerly download the model
moss-tts-nano-cli download
Show info
moss-tts-nano-cli info
Development
git clone https://github.com/vra/moss-tts-nano-cli.git
cd moss-tts-nano-cli
uv sync --extra dev
uv run pytest
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for moss-tts-nano-cli 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| moss_tts_nano_cli-0.1.3.tar.gz | 54.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| moss_tts_nano_cli-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 60.4 kB
Release files / moss_tts_nano_cli-0.1.3.tar.gz
| Download URL | moss_tts_nano_cli-0.1.3.tar.gz |
|---|---|
| Size | 54.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17703585a1be779ee8b385eed736640b7c19cc99788b54f0e263b2491f77c15b
|
|
BLAKE2b-256 checksum How to use checksums |
855bb97211b428b80274b0815040a682bec9f798f48637391a4da939a69464a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.8 {"installer":{"name":"uv","version":"0.11.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / moss_tts_nano_cli-0.1.3-py3-none-any.whl
| Download URL | moss_tts_nano_cli-0.1.3-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c7b9f9dbb8b606cd7665fc8104434f0e06242ab1875112ecd62c1e5188ceddf0
|
|
BLAKE2b-256 checksum How to use checksums |
293ce1842d4f7835eed78627c195eba8a3dd0051311d557d350b51767a0ad0b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.8 {"installer":{"name":"uv","version":"0.11.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for moss-tts-nano-cli 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
