> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ai-coustics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rook Multi Speaker

> Speech enhancement for human listening in calls and other real-time audio applications.

**Rook Multi Speaker** targets speech naturalness and intelligibility for human listeners. Use it for calls and other applications where people hear the enhanced output. Its multi-speaker models aim to retain speech from both foreground and background participants while reducing noise and reverberation.

For machine listening and speech-to-text (STT), evaluate [Quail Multi Speaker](/models/speech-enhancement/quail-multi-speaker). For isolating one primary speaker, evaluate [Quail Voice Focus](/models/voice-focus/quail-voice-focus).

## Choose a variant

Rook Multi Speaker is available in small and large variants at 8 kHz, 16 kHz and 48 kHz. Examples are `rook-ms-s-16khz` and `rook-ms-l-48khz`. The [model reference](/reference/sdk/models#rook-multi-speaker) lists all current IDs and their native block sizes.

Match the model's native rate to the frequency range your application needs, then measure quality and CPU use on target hardware. Processing 48 kHz audio through a 16 kHz model does not make that model enhance frequencies above its native range.

## Evaluate for listeners

Use paired recordings and listening tests with representative speech, noise, reverberation and overlapping speakers. Check speech retention and artifacts as well as noise reduction. Measure latency through the complete capture, processing and playback path.

Rook Multi Speaker can also precede a third-party voice activity detector, but test that detector's false starts, missed speech and timing with the enhanced signal. Do not assume one enhancement level gives the best result for every detector. Dedicated [ai-coustics VAD](/models/voice-activity-detection/vad) should receive the original input audio.

Start with the [SDK quickstart](/models/get-started/sdk-quickstart), then use the [latency guide](/reference/concepts/latency) to evaluate your call path.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.