drmhse/tts-rs-assets
tts-rs-assets Derived assets for tts-rs: per-stage reference activations that the Rust ports are gated against, plus two small CosyVoice artifacts that cannot be produced without the upstream python package. No model weights are here. You download those from their own repositories; see docs/setup.md in tts-rs. What is in here, and why it is not in the git repo file size what it is cosyvoice/rand_noise.safetensors 4.6 MB The CFM decoder's fixed noise… See the full description on the dataset page: https://huggingface.co/datasets/drmhse/tts-rs-assets.
tts-rs-assets
Derived assets for `tts-rs`: per-stage reference activations that the Rust ports are gated against, plus two small CosyVoice artifacts that cannot be produced without the upstream python package.
No model weights are here. You download those from their own repositories; see docs/setup.md in tts-rs.
What is in here, and why it is not in the git repo
The first two exist because producing them requires the upstream CosyVoice repository on PYTHONPATH under python 3.10 / torch 2.3.1. Hosting them means running CosyVoice needs neither. The fixtures exist so that ./scripts/gates.sh — the thing that substantiates every correctness claim in the tts-rs README — runs on a machine with no PyTorch at all.
Both remain reproducible from source: references/cosyvoice/convert.py and each engine's dump_fixtures.py regenerate them. See docs/setup.md §3. If you are checking the ports rather than using them, regenerating is the stronger move — verifying against tensors somebody else uploaded is trusting the upload.
Integrity
SHA256SUMS covers every file. scripts/fetch-assets.sh in tts-rs verifies against it and refuses a mismatch.
shasum -a 256 -c SHA256SUMSProvenance
Dumped from these upstream models. The Rust ports were written against these revisions; a fixture mismatch after an upstream update is a revision difference, not necessarily a port bug.
Those SHAs are each repository's HEAD as read on 2026-08-12, recorded so that future drift is diagnosable. The dumps themselves were taken in late July / early August 2026; if an upstream repository moved between the dump and that reading, the SHA above is the later one. Regenerate from source if you need certainty.
Licence
Apache-2.0, inherited from all three upstream models. Every file here is a derivative work of an Apache-2.0 model — activations computed by it, a tokenizer built by its code, or a tensor drawn by its constructor. Attribution is above; see NOTICE in the tts-rs repository.
