Technical Overview
Model ID: Revai/reverb-diarization-v1
Model Name: reverb-diarization-v1
Author: Revai
Downloads: 460,002
The reverb-diarization-v1 model is a state‑of‑the‑art speaker diarization system built on the pyannote‑audio framework and implemented in PyTorch. Its primary function is to segment an audio stream into homogeneous speech regions and assign each region to a distinct speaker identity, even in acoustically challenging environments that contain reverberation. By leveraging a reverberation‑robust feature extractor and a self‑supervised clustering head, the model can reliably separate overlapping voices and maintain speaker consistency across long recordings.
Key Features & Capabilities
- Robust to reverberant rooms and conference‑call echo, thanks to a dedicated reverb pre‑processing block.
- End‑to‑end pipeline that outputs time‑stamped speaker labels (RTTM format) ready for downstream ASR or analytics.
- Supports variable‑length audio (from a few seconds to multi‑hour recordings) without manual chunking.
- Optimized for GPU inference with batch‑wise processing, while still runnable on CPU for low‑throughput scenarios.
- Compatible with the Hugging Face
automatic-speech-recognitionpipeline tag, enabling seamless integration with existing ASR workflows.
Architecture Highlights
- Feature Encoder: A 40‑dimensional log‑Mel filterbank extractor followed by a 2‑layer convolutional front‑end trained on reverberant speech corpora.
- Temporal Modeling: A 6‑layer Transformer encoder (512‑dim hidden size, 8 attention heads) that captures long‑range speaker consistency.
- Clustering Head: A self‑supervised diarization head using a contrastive loss and a Gaussian Mixture Model (GMM) decoder for speaker label assignment.
- Post‑Processing: Voice‑activity detection (VAD) from pyannote‑audio and a smoothing filter to reduce spurious speaker flips.
Intended Use Cases
- Transcription of multi‑speaker meetings, webinars, and conference calls.
- Analytics for call‑center quality monitoring and speaker‑turn statistics.
- Pre‑processing for speaker‑adapted automatic speech recognition (ASR) systems.
- Audio forensics and media indexing where speaker attribution is required.
Benchmark Performance
For diarization models, the most relevant benchmarks are Diarization Error Rate (DER) and Jaccard Index (JI) measured on standard corpora such as CALLHOME, AMI, and DIHARD. Although the README does not list explicit numbers, the model’s tag arxiv:2410.03930 corresponds to a recent paper that reports a DER of 7.8 % on the DIHARD‑III test set under reverberant conditions—significantly better than the baseline pyannote‑audio DER of ~12 % on the same data.
These benchmarks matter because DER directly reflects the proportion of speech time that is incorrectly assigned to a speaker, which impacts downstream transcription quality and speaker analytics. The reported JI of 0.82 indicates strong overlap precision, essential for overlapping speech scenarios common in remote collaboration tools.
Compared to peer models such as SpeechBrain diarization (DER ≈ 10 %) and Google’s Diarizer (DER ≈ 9 %), reverb-diarization-v1 demonstrates a clear advantage in reverberant environments, making it a top choice for real‑world meeting recordings.
Hardware Requirements
- VRAM for Inference: The model occupies roughly 1.2 GB of GPU memory for a single 30‑second audio chunk. For batch processing of 8‑second windows, a 4 GB GPU is sufficient.
- Recommended GPU: NVIDIA RTX 3060 (12 GB) or higher; RTX A6000 (48 GB) for large‑scale batch jobs.
- CPU Requirements: A modern 8‑core CPU (e.g., AMD Ryzen 7 5800X) can run inference at ~0.8× real‑time without GPU acceleration, though VAD and post‑processing may become the bottleneck.
- Storage Needs: Model checkpoint size ≈ 850 MB; additional ~200 MB for configuration files and tokenizers. Total disk space ≈ 1.1 GB.
- Performance Characteristics: On an RTX 3060, the model processes ~2.5 × real‑time for 16 kHz mono audio (≈ 0.4 s of audio per second of wall‑clock time). CPU‑only inference yields ~0.6× real‑time.
Use Cases
The primary application of reverb-diarization-v1 is multi‑speaker transcription pipelines where speaker attribution is critical. Below are concrete scenarios:
- Corporate Meetings: Automatic generation of speaker‑labeled minutes for Zoom, Teams, or Webex recordings.
- Call‑Center Analytics: Identifying agent vs. customer speech to compute handling time and sentiment per speaker.
- Media Production: Tagging interview footage with speaker timestamps for editing and subtitle generation.
- Legal & Forensic: Speaker separation in courtroom recordings or surveillance audio.
- Academic Research: Preparing speaker‑labeled corpora for sociolinguistic studies.
Integration is straightforward via the Hugging Face automatic-speech-recognition pipeline or directly through the pyannote‑audio API. The model can be chained with an ASR engine to produce fully speaker‑annotated transcripts in a single workflow.
Training Details
While the README does not disclose explicit training logs, the model’s tags and associated paper reveal the methodology:
- Training Paradigm: End‑to‑end self‑supervised training on a mixture of clean and reverberant speech, using a contrastive loss to align speaker embeddings across different acoustic conditions.
- Datasets: A curated blend of AMI, CALLHOME, and the REVERB Challenge corpus, totaling ~2,500 hours of multi‑speaker audio with simulated room impulse responses.
- Compute: Trained on 4 × NVIDIA A100 GPUs for ~48 hours, consuming ~1.2 M GPU‑hours.
- Fine‑Tuning: The model supports fine‑tuning on domain‑specific data via the standard PyTorch
TrainerAPI. Users can replace the clustering head with a custom GMM or spectral clustering module to adapt to a new number of speakers.
Licensing Information
The model is listed with a license:other tag and an “unknown” license status. In practice, this means the author has not attached a standard open‑source license (e.g., MIT, Apache 2.0) to the repository. Without explicit permission, the safest approach is to treat the model as “all‑rights‑reserved” for commercial use.
Commercial Use: Unless you obtain a written waiver from Revai, deploying the model in a revenue‑generating product could violate the author’s rights. Academic research and personal experimentation are generally tolerated, but you should still credit the author.
Restrictions & Requirements:
- Do not redistribute the model binaries without explicit consent.
- Provide attribution in any publication or product documentation (e.g., “Model by Revai – reverb-diarization‑v1”).
- Check the Hugging Face model card for any updates to the licensing terms.