aidataservices.inAI data collection · India

Dataset specification · Production cohort

1,000 speakers of Kannada Scripted Speech

A production cohort build of 1,000 speakers of Kannada scripted speech. Generalisation across speakers, which is what actually drives real-world ASR robustness. Speakers read prompts from a phonetically balanced script shown one line at a time, with retakes on any flubbed or misread line.

Request a dataset quoteReply within one working day
Structured dataset packages ready for delivery — 1,000 speakers of Kannada Scripted Speech
Volume
1,000 speakers
Scale
Production cohort
Per speaker
20–30 minutes of accepted audio per speaker
Accepted yield
85–90% of recorded time is accepted
01

How Kannada scripted speech is captured

Speakers read prompts from a phonetically balanced script shown one line at a time, with retakes on any flubbed or misread line.

A 45-minute booth session yields roughly 300–400 prompts. One file per utterance, cut at the prompt boundary, so alignment is exact before any forced-alignment pass runs.

Yield at this style: 85–90% of recorded time is accepted. Prompt-level retakes catch problems inside the session, so very little is discarded afterwards. This is the highest-yield style we run.

Production cohort — what the build is actually made ofCitiesSix to eightStudiosEight rooms plus two mo…RecruitersEight coordinators, one…Audio yield~500 hours at 30 minute…Sessions per day45–55Team1 programme lead, 1 reg…
02

The specification

FieldValue
LanguageKannada (kn-IN, Kannada)
Volume1,000 speakers
Equivalent500 hours at 30 minutes per speaker
Speech typeScripted Speech
Per speaker20–30 minutes of accepted audio per speaker
File granularityOne WAV per prompt, named by prompt ID and speaker ID
Prompt coverageTriphone-balanced script with digit, date, name and domain-lexicon blocks
Leading/trailing silence200 ms padded, verified automatically on every file
AlignmentPrompt text is ground truth; deviations are flagged rather than silently corrected
DialectsBangalore urban, Mysuru (standard literary), Dharwad / North Karnataka, Mangaluru coastal
TranscriptionVerbatim, native-speaker, second-pass reviewed
Audio QC engineer inspecting waveforms and spectrograms — supporting 1,000 speakers of kannada scripted speech
Audio QC engineer inspecting waveforms and spectrograms
03

Designing the script for Kannada

  • Script built for triphone coverage rather than word coverage, so rare phone contexts appear often enough to train on
  • Digit strings, dates, currency and person names blocked separately, because these are where deployed ASR actually fails
  • Domain lexicon injected from your product vocabulary when you supply one
  • Sentence-length distribution spread deliberately, since all-short prompts produce a model that cannot handle long utterances
  • Built against Kannada specifically: North Karnataka speech has markedly different intonation and lexicon from Mysuru standard
  • Code-mixing handled explicitly rather than edited out — Bengaluru is a migration city: Kannada speech there is mixed with English, Hindi, Tamil and Telugu. Native-only Kannada cohorts recruited in Bengaluru are hard to fill without screening for years of residence.
04

Running a production cohort Kannada build

Nine to twelve weeks, with recruitment running continuously rather than in a front-loaded phase.

Six to eight batches, speaker-disjoint by construction so held-out speakers are genuinely held out.

Screen Bengaluru participants for native fluency and years of Karnataka residence; otherwise the cohort drifts towards second-language Kannada.

ParameterAt this volume
CitiesSix to eight — Bengaluru, Mysuru, Hubballi-Dharwad, Mangaluru, Kalaburagi
StudiosEight rooms plus two mobile rigs
RecruitersEight coordinators, one regional manager
Audio yield~500 hours at 30 minutes per speaker
Sessions per day45–55
Team1 programme lead, 1 regional manager, 8 coordinators, 14 engineers, 25 transcribers, 3 QA leads
05

Cohort design

At 1,000 speakers the quota matrix is enforced per cell, not in aggregate. Every dialect, age and gender combination carries its own target and is signed off individually before final acceptance, because an aggregate 50/50 split can hide a cell that was never filled at all.

Requires literate speakers comfortable reading aloud in the target script, which is the main constraint on cohort breadth and has to be actively counterweighted.

DimensionTypical splitWhy it matters for Kannada
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 Kannada forms that younger urban speakers have lost
RegionKarnataka / parts of Maharashtra, Tamil Nadu and Andhra Pradesh 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

Kannada-specific considerations

  • North Karnataka speech has markedly different intonation and lexicon from Mysuru standard
  • Bengaluru is a migration city: Kannada speech there is mixed with English, Hindi, Tamil and Telugu. Native-only Kannada cohorts recruited in Bengaluru are hard to fill without screening for years of residence.
  • Mysuru/Bengaluru standard dominates. North Karnataka (Dharwad, Kalaburagi) and coastal Mangaluru speech are barely represented in any public corpus.
07

Quality gates for scripted speech

  • Prompt-to-audio match verified by a native reviewer; a misread line is a rejected file, not an edited transcript
  • Hyperarticulation flagged — a speaker over-enunciating because they are reading produces audio that does not match deployment
  • Clipping and truncation checked at both utterance boundaries
  • Per-speaker prompt coverage confirmed, so no speaker silently skips a block
  • Northern lexical items replaced with standard equivalents
  • Inconsistent transliteration of English technical terms

100% technical QA, 10% content QA stratified by city and coordinator, with voice-based duplicate detection across the whole cohort.

08

What goes wrong on scripted speech sessions

  • Reading voice: flat prosody and unnatural stress that trains a model on speech nobody actually produces
  • Prompt fatigue in the back half of long sessions, where accuracy drops and pace flattens
  • Speakers who are not fluent readers, which quietly biases the cohort toward higher education bands
  • Script leakage across speakers, producing a corpus that memorises sentences instead of covering sounds
09

Risks at production cohort in Kannada

Cost at this band is driven by: Number of distinct demographic cells rather than total speakers.

  • Speaker-disjoint splits are only trustworthy if duplicate detection is voice-based rather than ID-based, since one person can present two identities
  • Coordinator-level demographic bias becomes measurable at this size and should be reported, not smoothed over
  • Kannada carries 5 recognised varieties across Karnataka, parts of Maharashtra, Tamil Nadu and Andhra Pradesh, so the quota matrix is wider than the headline volume suggests
  • Mysuru/Bengaluru standard dominates. North Karnataka (Dharwad, Kalaburagi) and coastal Mangaluru speech are barely represented in any public corpus.
10

Deliverables

  • WAV audio to your naming convention, with the per-file manifest
  • Verbatim Kannada transcripts with utterance-level timestamps
  • Prompt ID mapped to every utterance
  • Verbatim deviation flags where the speaker departed from the script
  • Per-utterance SNR and duration in the manifest
  • Per-speaker metadata: age band, gender, region, dialect, education band
  • Consent records mapped to speaker IDs
  • QA report with pass rates, rejection reasons and agreement statistics
  • Speaker-disjoint train / dev / test splits on request
11

What this trains, and what it does not

  • ASR acoustic model baselines
  • TTS voice building where a single speaker is recorded at depth
  • Pronunciation lexicon and G2P validation
  • Forced-alignment and phone-boundary work

Scripted audio contains no disfluencies, no false starts and no natural turn-taking. A model trained on it alone degrades sharply on real spontaneous input, so it is a baseline layer rather than a complete training set.

Frequently asked

Is 1,000 speakers of Kannada enough?

Enough for production ASR generalisation and for a speaker-verification corpus with meaningful negative pairs.

Why scripted speech rather than another speech type?

ASR acoustic model baselines, TTS voice building where a single speaker is recorded at depth, Pronunciation lexicon and G2P validation are what this style is the right input for. Scripted audio contains no disfluencies, no false starts and no natural turn-taking. A model trained on it alone degrades sharply on real spontaneous input, so it is a baseline layer rather than a complete training set.

How long does a production cohort Kannada build take?

Nine to twelve weeks, with recruitment running continuously rather than in a front-loaded phase. Six to eight batches, speaker-disjoint by construction so held-out speakers are genuinely held out.

What does 1,000 speakers of Kannada scripted speech cost?

Quoted per delivered hour against this specification. At this band the drivers are number of distinct demographic cells rather than total speakers. Send the spec and you get one fixed figure.

How much QA is applied at this volume?

100% technical QA, 10% content QA stratified by city and coordinator, with voice-based duplicate detection across the whole cohort.

Quote this Kannada dataset

1,000 speakers, scripted speech, Kannada — production cohort. Adjust anything and send it.

Request a dataset quote