canto-tts
Cantonese Hong Kong Text-to-Speech · CPU-first · Apache-2.0
An open-source Cantonese (Hong Kong) text-to-speech SDK. Runs on CPU via ONNX Runtime — no GPU required. Fine-tuned from MOSS-TTS-Nano (0.1 B params, GPT-2 backbone, Apache-2.0, by OpenMOSS).
Published — CER 11.82% / tone accuracy 84.22% / code-switch CER 13.87% on a 100-sentence gate set (N=5 repeat eval). Weights on HuggingFace. Single default voice only — no voice cloning, no voice selection (yet).
Install
pip install canto-tts
Quickstart
from canto_tts import CantoTTS
tts = CantoTTS() # auto-downloads typangaa/canto-tts-nano from HuggingFace on first use
tts.synthesize("多謝晒,今日天氣幾好。", "hello.wav")
print("Saved to hello.wav")
# English code-switching works too
tts.synthesize("我哋一齊去 IFC food court 食飯。", "codeswitching.wav")
Weights auto-download from HuggingFace and cache via the Hub (~/.cache/huggingface/hub/).
Quality Modes (opt-in)
Two opt-in quality= modes trade extra compute for a more reliable draw, without touching the model:
tts.synthesize(text, "out.wav", quality="duration_filter", max_attempts=3) # no extra deps
tts.synthesize(text, "out.wav", quality="best_of_n", best_of_n=4) # needs canto-tts[quality]
quality="best_of_n" reranks N draws by ASR character-error-rate; pass asr_backend="sensevoice" (needs canto-tts[quality-sensevoice]) for ~7x faster reranking at a small accuracy cost. Full writeup: GitHub README.
Limitations
| Quality | CER 11.82% / tone accuracy 84.22% / code-switch CER 13.87% (N=5 repeat, 100-sentence gate set). |
| Voice | Single default voice. No voice cloning, no voice selection (yet). |
| Language | Cantonese (Hong Kong) + English code-switching only. No Mandarin. |
| Training data | Privately sourced — not released (copyright), regardless of weight status. |
| Weights | ✅ Published — huggingface.co/typangaa/canto-tts-nano. |
Model & License
- Base model: MOSS-TTS-Nano by OpenMOSS
- Weights: published at huggingface.co/typangaa/canto-tts-nano
- License: Apache-2.0 (inherited from MOSS-TTS-Nano)
Full Documentation
Full README, CLI docs, Docker self-hosting, and deployment guide: https://github.com/typangaa/canto-tts
Metadata
Release files for canto-tts 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| canto_tts-0.1.4.tar.gz | 56.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| canto_tts-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 112.6 kB
Release files / canto_tts-0.1.4.tar.gz
| Download URL | canto_tts-0.1.4.tar.gz |
|---|---|
| Size | 56.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c0aa4d62d279cb8cc666a263d421ef30ded4cb7914dc1fff76c689aeeb78203
|
|
BLAKE2b-256 checksum How to use checksums |
7d0723c857425bb24ff53fe485808b48fa3e30f54ddeeddc6258b1a9474543f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency logRelease files / canto_tts-0.1.4-py3-none-any.whl
| Download URL | canto_tts-0.1.4-py3-none-any.whl |
|---|---|
| Size | 55.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8893f6b3bad802199787cf637120d3e49f0c1cd7848a4fd7ce99919a8588c028
|
|
BLAKE2b-256 checksum How to use checksums |
43218e3469cad4618f95979d246f400ae161ddc26b5dcbc46528501173bd9274
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency log