OpenMOSS-Team · audio asr

MOSS-Transcribe-Diarize

OpenMOSS-Team/MOSS-Transcribe-Diarize

MOSS-Transcribe-Diarize at Q4_K is exactly 535,272,448 bytes (0.50 GiB / 0.54 GB) — an effective 4.713 bits per weight, not the nominal 4. Its KV cache at 32K is 3.50 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
909M
Architecture
campplus
28 layers
Context
131,072
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_K0.50 GiB535,272,4484.713mudler
Q4_00.50 GiB535,272,4484.713mudler
Q5_00.60 GiB648,174,5925.708mudler
Q5_K0.60 GiB648,174,5925.708mudler
Q6_K0.72 GiB768,133,1206.764mudler
Q8_00.92 GiB986,881,0248.690mudler
Q4_K1.11 GiB1,190,110,81610.480cstr
Q8_01.31 GiB1,410,311,77612.419cstr
F161.70 GiB1,823,188,51216.054cstr
F161.71 GiB1,833,647,10416.146mudler
F323.39 GiB3,640,081,40832.053Luigi

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.44 GiB0.44 GiB28 / 0 / 0
8,1920.88 GiB0.88 GiB28 / 0 / 0
16,3841.75 GiB1.75 GiB28 / 0 / 0
32,7683.50 GiB3.50 GiB28 / 0 / 0
65,5367.00 GiB7.00 GiB28 / 0 / 0
131,07214.00 GiB14.00 GiB28 / 0 / 0

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 at roughly 0.48 GiB. The real file is 0.50 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
28
Attention heads
16
KV heads
8
Head dim
128
Hidden size
1024
Vocab
151,936
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does MOSS-Transcribe-Diarize need?
Q4_K is exactly 535,272,448 bytes (0.50 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is MOSS-Transcribe-Diarize's KV cache?
3.50 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of MOSS-Transcribe-Diarize 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.