aidataservices.inAI data collection · India

Speaker Diarisation · বাংলা

Bengali Data for Speaker Diarisation

Determining who spoke when in multi-party Indian-language audio, including overlapped speech. In Bengali, the binding constraint is usually dialect coverage and code-mixing, not raw hours.

Request a dataset quoteReply within one working day
Annotator labelling audio segments and speaker turns — Bengali Data for Speaker Diarisation
Language
Bengali
Primary metric
Diarisation error rate
Typical volume
500-2,000 hours
01

Data profile required

  • Per-speaker isolated channels with a mixed reference
  • Genuine overlap preserved
  • Turn-level ground truth
Speaker Diarisation · BengaliData profile that moves itWhat it is scored onPer-speaker isolated channels with a mi…Genuine overlap preservedTurn-level ground truthDiarisation error rateOverlap detection recallSpeaker-count accuracyThe corpus is specified backwards from the right-hand column.
02

What Bengali adds to the requirement

  • Inherent vowel is realised as /ɔ/ or /o/, which breaks G2P rules copied from Devanagari-based systems
  • No phonemic distinction between শ ষ স in most speech despite three orthographic characters
  • Dialects to cover: Kolkata standard (Rarhi), Sylheti-influenced, Rangpuri / North Bengal, Medinipuri
  • Kolkata professional speech mixes English heavily; rural West Bengal much less. A single 'Bengali' dataset without register tags conflates two very different acoustic and lexical distributions.
Field recording session with a rural speaker in India — supporting bengali data for speaker diarisation
Field recording session with a rural speaker in India
03

Metrics to track

  • Diarisation error rate
  • Overlap detection recall
  • Speaker-count accuracy
04

Failure modes

  • Overlap edited out during recording
  • Single-channel-only capture leaving no reliable ground truth

For Bengali specifically: Indian Bengali is under-collected relative to Bangladeshi Bengali, and North Bengal and Tripura varieties are almost entirely missing.

05

Recommended cohort

Tag every speaker as Indian Bengali and record district of origin; mixing in Bangladeshi speech without tags is a common and costly dataset defect.

DimensionTypical splitWhy it matters for Bengali
Gender50 / 50Pitch range differences change acoustic model behaviour; unbalanced cohorts bias recognition
Age18-25: 30%, 26-40: 40%, 41-60: 30%Older speakers retain conservative Bengali forms that younger urban speakers have lost
RegionWest Bengal / Tripura / Assam (Barak Valley) and othersDialect spread across 5 recognised varieties
EducationMixed, including below-graduatePrompt-reading fluency correlates with education and skews prosody
ConditionStudio / quiet room / fieldMatch the noise profile of your deployment
06

Suggested programme shape

Start with an evaluation set of 100 speakers spread across every Bengali dialect in scope, collected before training data. Then field 500-2,000 hours of training data from disjoint speakers.

This ordering is what makes the improvement measurable rather than assumed.

Frequently asked

Is there usable public Bengali data for speaker diarisation?

Indian Bengali is under-collected relative to Bangladeshi Bengali, and North Bengal and Tripura varieties are almost entirely missing.

How many Bengali speakers do we need?

1,000-3,000 speakers for a training corpus, plus a disjoint evaluation cohort covering each dialect. Speaker count matters more than hours for generalisation.

Can you run this across multiple languages at once?

Yes. Multi-language programmes run to one master specification so per-language results stay comparable.

Scope Bengali data for speaker diarisation

Send the target metric and the languages in scope.

Request a dataset quote