TADA-3B-ML is a multilingual text-to-speech model built on Meta Llama 3.2 3B with a flow-matching (FM) speech decoder and custom Hume codec. Key property: **1:1 token alignment** — every text token maps to exactly one speech vector, eliminating transcript hallucination. Supports 10 languages (en, es, ja, zh, de, fr, it, pt, ko, ar). 24 kHz mono output. The Q4_K file uses a TADA-aware quantization policy (tail=14): large transformer block matrices are quantized, while the last 14 token-embedding rows and all `tada.*` flow-matching tensors are kept at F16. This preserves the timing and acoustic conditioning paths where quantization noise matters most. For near-lossless quality use `tada-tts-3b-ml-q8_0.gguf`; for the F16 reference quality use `tada-tts-3b-ml-f16.gguf`.
Explore AI models 84991
Apache-2.0 Tesseract LSTM line-recognition models converted to GGUF for CrispEmbed. The repository contains English, German, French, Spanish, Italian, Portuguese, Dutch, Russian, Arabic, Simplified Chinese, Japanese, and Korean variants. These are line recognizers: normalize and crop individual text lines before recognition, or pair them with a detector such as DBNet for full-page OCR. Each language has an F32 reference, an F16 deployment model, and Q8_0/Q4_K variants. The quantized models preserve `output.weight` and `output.bias` at the source precision (F16 for the multilingual F16-derived models; F32 for German regenerated from its original `.traineddata`). Only recurrent matrices are quantized. This preserves the CTC decision boundary and keeps critical character logits stable.
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
> The Q8_0/Q4_K files keep the diffusion prediction head, connectors and > EOS classifier at full precision (only the two Qwen2 backbones are > quantized). The head runs under classifier-free guidance over 20 solver > steps, so quantizing it could push the first frames onto a wrong > trajectory that decodes as a brief non-speech "music"/hum onset before > the voice; keeping it at full precision avoids that at a small size cost. A voice prompt is **required** for TTS. Each `.gguf` voice pack ships pre-computed KV caches that establish a fixed speaker identity (the realtime variant is *not* WAV-cloning — for runtime cloning, use `cstr/vibevoice-1.5b-GGUF` instead). This repo bundles all 25 demo voices from `microsoft/VibeVoice@main demo/voices/streaming_model/` — same MIT license as the model.
voxcpm2-GGUF
cstrHistorical T4 Vulkan component measurements found CFM per audio step of 70.2 ms for Q8_0 versus 59.4 ms for the mixed recipe at ten steps. An eight-step run measured 46.7 ms. These component timings do **not** establish speech quality or an accepted end-to-end speedup. The mixed file was built with `crispasr-quantize voxcpm2-f16.gguf out.gguf q8_0 --tensor-type "^locdit\.=f16"`. A previous CPU synthesis roundtrip is not GPU acceptance. **Validation update, 2026-10-09:** matched real T4 tests at ten steps and seed 2 produced repeated tokens in the **Nemotron ASR transcripts** of the short test sentence for both Q8_0 and the mixed recipe. Six of sixteen exact primary ASR cases passed. This rejected gate is not proof that synthesized audio audibly stutters: a later fixed-audio comparison found **both Parakeet and Qwen3 transcribe every one of 22 original Python/native CPU/GPU controls exactly** across three resampling paths, while Nemotron retains errors. Resampling alone does not resolve the discrepancy. The completed original NVIDIA float32 and native F16 comparison reads **all 22 VoxCPM2 controls correctly**; native Q4 reads only 8/22. Original and F16 normalized words agree on all 26 tested clips, and fresh/reused sessions agree. The repeated tokens are therefore attributable to the native Nemotron Q4 recognizer on these fixed controls. Critical RNNT precision guards are being tested before changing that quant or its defaults. The published Q4 primary gate remains rejected while that recognizer is repaired. This diagnosis does not certify eight steps, Intel B390 performance, or complete original/native waveform parity. Defaults remain ten steps. Original NVIDIA/F16/Q4 inputs, features, encoder states and complete transcripts (SHA256 `7762f2a73d8ae7dad05d667fbf0bca393a0b3b7ad622b1b1f09473fa8f5d0463`).
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
GGUF quantizations of mistralai/Voxtral-Mini-4B-Realtime-2602, a **4.4B-parameter realtime streaming speech-to-text model** with a causal audio encoder and configurable transcription delay. ⚠ This table used to name the F16 `voxtral-mini-4b-realtime.gguf`, and no such file was ever uploaded. The published name is `…-f16.gguf`, matching the quant suffix CrispASR's `-m auto:f16` resolver expects.
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
No matching models
Adjust provider, category or input/output filters. New models are added continuously.
Great models. Clear costs.
Adjust monthly token usage to compare estimated API costs.
Compares base text-token rates within the same channel
Uses collected, comparable USD-per-million-token rates. Snapshots exclude cache discounts, tiers, extra reasoning output and taxes. Check current source prices.
Understand before you choose
How should API prices be compared?+
Separate input, output and cache rates, then estimate the same workload. Image, audio and video rates may use items, duration or resolution rather than tokens.
Do open weights mean free commercial use?+
Not necessarily. Check each version’s license, commercial restrictions and policies. Self-hosting also incurs compute and maintenance costs.
Is the top-ranked model the best for me?+
Rankings depend on tasks, versions and methods. Compare accuracy, latency, reliability and costs on your own workload.