Factorized diffusion speech research system that separates content, prosody, timbre and acoustic detail. The main experiment uses 500M diffusion-model parameters and 60,000 hours of LibriLight.
First research-family disclosure on arXiv; reviewed specifications may reflect a later paper revision. Not a commercial or separate variant release date.
An evaluation setting, not an advertised maximum reference duration.
Architecture
FACodec plus factorized discrete diffusion. Shared prosody/content/acoustic-detail Transformer has 12 layers, eight heads and 1,024 embedding dimensions; phoneme and duration paths use separate encoders.Source for Architecture (opens in a new tab)
FACodec factorizes content, prosody, acoustic detail and timbre. Public FACodec checkpoints cover the codec component, not the full diffusion synthesis system.Source for Audio codec design (opens in a new tab)
Four iterations per diffusion process; paper reports 60 forward passes with classifier-free guidance. A one-step inference setting uses 15 forward passes.Source for Research controls (opens in a new tab)
Research configurations
500M / 1,000-hour LibriLight subset, 500M / 60,000-hour LibriLight main model, 500M / 200,000-hour internal corpus, 1B / 200,000-hour internal corpus (separate detail record)Source for Research configurations (opens in a new tab)
Separately trained data/model scaling experiments in Section 4.4; not commercial releases. The one-step latency variant changes inference iterations, not the training dataset.
Access & pricing
Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.
Read the paper and listen to prerecorded examples. No user-callable inference endpoint established by the reviewed project.
Regions
Not applicable to prerecorded research samples.
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
No hosted customer inference or data-retention contract verified.
Caching
Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.
01 / INITIAL INPUTProcess & retain
The system processes eligible input and retains reusable state.
02 / LATER REQUESTCheck available state
Reuse depends on matching input, session state and the cache policy.
03 / CACHE HITReuse & generate
Reusing state can reduce repeated work. Any charges follow the billing rules below.
Microsoft Research (prerecorded samples)
Not verified
No public service cache contract verified.
How it works
Not collected
Minimum reusable input
Not collected
Lifetime & refresh
Not collected
How to enable it
Not collected
Usage fields
Not collected
Billing rules
Not collected
Limits & data boundaries
Not collected
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 14 Oct 2026
What the measurements say
No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.
Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.
The record behind the model
Why it is included
Classification is an evidence-based inference for the original research checkpoint: the authors provide papers and prerecorded samples, but no full original model weights or callable service in the reviewed project materials. The Microsoft Hugging Face account lookup also returns no matching model. This does not classify independent implementations or separately released codec components as closed.