Choose by task
This catalog covers model file format 7 for Python SDK 3.2.0 and core SDK 0.24.0. A download ID selects a compatible artifact; the loaded model’s ID can also include its build identifier. Record both when reproducing an evaluation.
Sizes are approximate decimal MB of model files, not runtime memory. Native rate and optimal block size describe model geometry, not end-to-end latency. For removed models, see deprecated models.
These models process audio rather than a language-specific transcription vocabulary. That does not establish equal quality for every language or acoustic condition. Evaluate the languages and microphones your application supports. Streaming enhancement and VAD support non-native sample rates through the SDK; analysis has separate requirements described below.
Quail Multi Speaker
Quail Multi Speaker targets machine listening while retaining speech from multiple participants. Use it when every speaker matters, then compare transcription results and speech retention. It is not a primary-speaker selector.Quail Voice Focus
Quail Voice Focus targets one primary speaker for machine listening. Evaluate competing speech, quiet target speech, startup context and changes in speaker prominence.VAD Multi Speaker
VAD Multi Speaker detects speech activity from the original audio without producing enhanced audio. Use it when activity from any speaker should count.
Earlier model IDs include
quail-vad-2.0-xxs-16khz and vad-2.1-xxs-16khz. See renamed models before changing an existing deployment.
VAD Voice Focus
VAD Voice Focus targets primary-speaker activity. It is a dedicated VAD model, distinct from the Quail Voice Focus enhancement models.
This model was also published as
quail-vf-vad-2.0-s-16khz. Historical IDs remain distinct from display names. See renamed models.
Tyto
Tyto provides audio-quality analysis. It returns scores rather than enhanced audio or speech-boundary events. Use its 16 kHz analysis path and follow the real-time or batch guide for analysis windows and result interpretation.Rook Multi Speaker
Rook Multi Speaker targets naturalness and intelligibility for human listeners while retaining multiple speakers. Compare variants using listening tests as well as resource and latency measurements.Download a model
Browse the public model catalog or use your binding’s downloader. It chooses a model-file version compatible with that SDK. Use the returned path; downloaded filenames can include a build identifier.Loading and reusing models
A loaded model is its own object, separate from the processor, VAD or analyzer that runs it. Each model type belongs to exactly one kind of object, and a mismatch fails when you create that object rather than when you process audio:One model, many streams
Share one loaded model across independent processors, VADs or analyzers. Each processing object holds one stream’s state while sharing the model weights:aic_model_destroy and the matching *_destroy calls may run in any order.
Loading from memory
Use buffer loading to embed a model or fetch it through your own transport:
An unaligned buffer is rejected with
AIC_ERROR_CODE_MODEL_DATA_UNALIGNED (ModelDataUnalignedError in the bindings that expose it). The Python and Node.js bindings load models from files only.
Using models with non-native sample rates
For Core SDK 0.24.0, streaming enhancement and dedicated VAD accept sample rates from 8 kHz to 192 kHz. The SDK resamples internally to the model’s native rate. QueryModel.get_optimal_block_size(sample_rate) in Python or model.getOptimalBlockSize(sampleRate) in Node for the rate your application uses. The optimal block avoids additional adapter buffering; it is not the only accepted block size.
Higher-rate input: a 16 kHz model processes frequency content up to its native Nyquist limit of 8 kHz, even if input arrives at 48 kHz. Resampling the result back to 48 kHz does not create model enhancement above that range. Blending with the original signal can retain original high-frequency content; the result depends on the model and enhancement setting.
Lower-rate input: resampling 8 kHz input to a 16 kHz model does not recover missing high-frequency information. Compare a native 8 kHz variant when one is available, using the same recordings and downstream task.
Resampling, block adaptation, model size and concurrency all affect resource use. Measure them on your hardware instead of assuming input sample rate has negligible CPU cost. See performance and latency.
Tyto analysis has its own sample-rate and window requirements. Do not apply the streaming Processor rate range to Analyzer or FileAnalyzer; follow the Tyto guides.
Compatibility
Model family, file format, SDK version and framework adapter all matter. A model that loads successfully can still be the wrong type for the component you construct. The compatibility matrix records the selected releases. The official LiveKit plugin exposes its own enhancement model choices and is the canonical path for LiveKit enhancement. Dedicated VAD and Tyto examples use the ai-coustics-maintained plugin where those capabilities are needed. Review plugin scope before installing packages; Python namespaces currently conflict. Pipecat 1.11.0’saic extra uses Python SDK 3.1.x, while the custom LiveKit 0.2.0 example uses SDK 3.2.0. Follow each framework’s pinned LiveKit or Pipecat recipe rather than applying one dependency set to both.