vox-dia
Dia TTS adapter package for Vox.
Included adapter
dia-tts-torch— Dia 1.6B text-to-speech backend
Install
pip install vox-dia
Runtime Dependencies
Dia uses an isolated target runtime at $VOX_HOME/runtime/dia for backend
packages that must not leak into the base Vox app environment.
The adapter package itself is intentionally lightweight and does not install Torch. The current Dia backend uses Hugging Face Transformers and requires a Vox runtime/image that already provides PyTorch with CUDA. CPU execution is not supported by the official Dia Transformers runtime used by this adapter.
The current Vox adapter is classified for Linux x86_64 CUDA/Torch runtimes. CPU, ONNX, and Spark/ARM NVIDIA paths are not currently production-supported by this adapter. Upstream Dia 1.6B documentation says the model has only been tested on GPUs with PyTorch/CUDA and that CPU support is future work: https://github.com/nari-labs/dia#hardware-and-inference-speed
Plan for at least 12GiB of usable VRAM budget: upstream reports that the full
Dia 1.6B model requires around 10GB of VRAM, and Vox budgets the adapter's 10GB
model estimate plus the deployment's configured VRAM headroom. A server started
with --max-vram 10GiB --vram-headroom 1GiB will reject Dia at load time.
During vox pull, the adapter verifies or installs the Dia-capable
Transformers runtime into $VOX_HOME/runtime/dia. It uses the released
transformers==4.57.6 runtime rather than a moving source checkout, so clean
pulls are reproducible. Model weights remain in the normal Vox model store.
Use with Vox
vox pull dia-tts:1.6b
Dia prompt control is text-driven. Use speaker tags and non-verbal markers in the input text, for example:
[S1] This is Dia speaking. (laughs) [S2] Keep the tags sparse or artifacts can appear.
The adapter supports Dia's audio-prompt voice cloning path when Vox resolves a
stored cloned voice into both reference_audio and reference_text. Dia needs
the reference transcript for the reference clip; requests with reference audio
but no reference text are rejected clearly.
The adapter also exposes Dia generation parameters through Vox synthesis
params:
max_new_tokens(integer, default3072, range1..8192)guidance_scale(number, default3.0, range0..10)temperature(number, default1.8, range0..3)top_p(number, default0.9, range0..1)top_k(integer, default45, range0..200)
Metadata
Release files for vox-dia 0.2.15
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 | Actions |
|---|---|---|---|---|
| vox_dia-0.2.15.tar.gz | 6.5 kB | Without provenance | Details for vox_dia-0.2.15.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vox_dia-0.2.15-py3-none-any.whl | Python 3 | none | any | Details for vox_dia-0.2.15-py3-none-any.whl |
Total release size: 13.8 kB
Release files / vox_dia-0.2.15.tar.gz
| Download URL | vox_dia-0.2.15.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ab64639711aa023a715594349546349f6a34adcdc6c833519de172b07e7603f
|
|
BLAKE2b-256 checksum How to use checksums |
fa3a5a0cf1f9c14574d7ba2bcd9100dea2a70d2c77274c5f9b85183943881b67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.0
|
Release files / vox_dia-0.2.15-py3-none-any.whl
| Download URL | vox_dia-0.2.15-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
249272de3fae264eff2bc4237fcb2e27baa313ba662ca67a66a36158f12bd9e1
|
|
BLAKE2b-256 checksum How to use checksums |
71f1922ed817eecbd14343458ee6c0ad6e8e5cc434744aea336fc4bff00f9dd9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.0
|
Security for vox-dia 0.2.15
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.