aidataservices.inAI data collection · India

Dataset specification · Evaluation cohort

500 speakers of Kannada Scripted Speech

An evaluation cohort build of 500 speakers of Kannada scripted speech. Speaker-count-driven work: verification, diarisation and accent robustness, where breadth matters more than hours. 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 — 500 speakers of Kannada Scripted Speech
Volume
500 speakers
Scale
Evaluation 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.

Evaluation cohort — what the build is actually made ofCitiesThree to fourStudiosFour roomsRecruitersFour coordinatorsAudio yield~250 hours at 30 minute…Sessions per day25–30Team1 programme lead, 4 coo…
02

The specification

FieldValue
LanguageKannada (kn-IN, Kannada)
Volume500 speakers
Equivalent250 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
Speaker recording scripted prompts for a speech data collection project — supporting 500 speakers of kannada scripted speech
Speaker recording scripted prompts for a speech data collection project
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 an evaluation cohort Kannada build

Six to eight weeks. Speaker-count targets front-load recruitment, so the coordinator team is proportionally larger than an equivalent hours-based build.

Four batches, each one a demographically complete slice rather than a convenient chunk, so early batches are usable for training on their own.

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

ParameterAt this volume
CitiesThree to four — Bengaluru, Mysuru, Hubballi-Dharwad, Mangaluru, Kalaburagi
StudiosFour rooms
RecruitersFour coordinators
Audio yield~250 hours at 30 minutes per speaker
Sessions per day25–30
Team1 programme lead, 4 coordinators, 8 engineers, 14 transcribers, 2 QA leads
05

Cohort design

At 500 speakers quotas are enforced per dialect and reconciled fortnightly. Aggregate demographics are reported per batch so drift is visible while there is still time to correct it.

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, 15% content QA, plus mandatory duplicate-speaker detection across cities.

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 evaluation cohort in Kannada

Cost at this band is driven by: Cohort breadth and screening depth, not recorded hours.

  • Duplicate speakers across cities inflate the apparent cohort and quietly corrupt speaker-disjoint splits
  • Recruiting for breadth tempts coordinators toward the easiest available demographic, which needs weekly quota audit
  • 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 500 speakers of Kannada enough?

Enough for reliable per-dialect evaluation and for training speaker-verification and diarisation systems.

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 an evaluation cohort Kannada build take?

Six to eight weeks. Speaker-count targets front-load recruitment, so the coordinator team is proportionally larger than an equivalent hours-based build. Four batches, each one a demographically complete slice rather than a convenient chunk, so early batches are usable for training on their own.

What does 500 speakers of Kannada scripted speech cost?

Quoted per delivered hour against this specification. At this band the drivers are cohort breadth and screening depth, not recorded hours. Send the spec and you get one fixed figure.

How much QA is applied at this volume?

100% technical QA, 15% content QA, plus mandatory duplicate-speaker detection across cities.

Quote this Kannada dataset

500 speakers, scripted speech, Kannada — evaluation cohort. Adjust anything and send it.

Request a dataset quote