k2-fsa · audio tts

OmniVoice

k2-fsa/OmniVoice

OmniVoice at Q4_K_M is exactly 659,959,328 bytes (0.61 GiB / 0.66 GB) — an effective 8.619 bits per weight, not the nominal 4.

From the file· summed from 2 file(s)From the file· KV per layer
Parameters
613M
Architecture
omnivoice-lm
null layers
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_K0.56 GiB597,547,5847.804cstr
Q4_K_M2 shards0.61 GiB659,959,3288.619Serveurperso
Q8_02 shards0.88 GiB945,284,60812.345Serveurperso
Q8_02 shards1.06 GiB1,137,987,64814.862cstr
BF162 shards1.49 GiB1,603,932,92820.947Serveurperso
F162 shards1.52 GiB1,633,808,89621.337cstr
F322 shards2.97 GiB3,189,948,864Serveurperso

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 0.32 GiB. The real file is 0.61 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
Attention heads
KV heads
Head dim
Hidden size
Vocab
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does OmniVoice need?
Q4_K_M is exactly 659,959,328 bytes (0.61 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of OmniVoice should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.