Dataset specification · Production scale
500 hours of Kannada Telephony Speech
A production scale build of 500 hours of Kannada telephony speech. The point at which a corpus is large enough to train a deployable model rather than adapt someone else's. Speech captured over a real telephony path — a genuine call through the network, not studio audio downsampled afterwards to imitate one.

- Volume
- 500 hours
- Scale
- Production scale
- Per speaker
- 10–20 minutes of accepted audio per speaker
- Accepted yield
- 50–60% of recorded time is accepted
How Kannada telephony speech is captured
Speech captured over a real telephony path — a genuine call through the network, not studio audio downsampled afterwards to imitate one.
Scenario-driven calls between a caller and an agent or IVR flow, each leg recorded separately, across a deliberate spread of handsets and network conditions.
Yield at this style: 50–60% of recorded time is accepted. Dropped calls, network artefacts beyond tolerance and unusable legs are discarded. Real network conditions are the point of the style and also its main cost.
The specification
| Field | Value |
|---|---|
| Language | Kannada (kn-IN, Kannada) |
| Volume | 500 hours |
| Equivalent | 1,000 speakers at 30 minutes each, or 500 speakers at one hour each |
| Speech type | Telephony Speech |
| Per speaker | 10–20 minutes of accepted audio per speaker |
| Sample rate | 8 kHz narrowband, matching what a deployed contact-centre model actually receives |
| Codec | G.711 and AMR-NB captured explicitly, with the codec recorded per call in the manifest |
| Legs | Caller and agent recorded on separate legs, never as a mixed call recording |
| Network conditions | Handset type, network carrier and packet-loss events logged per call |
| Dialects | Bangalore urban, Mysuru (standard literary), Dharwad / North Karnataka, Mangaluru coastal |
| Transcription | Verbatim, native-speaker, second-pass reviewed |

Designing the call flows for Kannada
- Call scenarios drawn from real contact-centre intents: balance enquiry, complaint, booking change, escalation
- IVR flows scripted with deliberate mis-entry and barge-in paths, since those are where deployed systems fail
- Handset spread specified up front — low-end Android, feature phone, landline — because handset variance is a real acoustic axis
- Background conditions varied on purpose: street, vehicle, indoor, since real callers are rarely in quiet rooms
- 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.
Running a production scale Kannada build
Eight to twelve weeks. Cities are staggered rather than started together, so the protocol corrections found in the first city are applied before the last one begins recording.
Six to eight batches, fortnightly, each speaker-disjoint so you can train on early batches without contaminating a later evaluation split.
Screen Bengaluru participants for native fluency and years of Karnataka residence; otherwise the cohort drifts towards second-language Kannada.
| Parameter | At this volume |
|---|---|
| Cities | Five to six — Bengaluru, Mysuru, Hubballi-Dharwad, Mangaluru, Kalaburagi |
| Studios | Six rooms plus two mobile rigs for rural capture |
| Recruiters | Six coordinators under one programme lead |
| Speakers | ~1,000–1,200 |
| Sessions per day | 40–50 nationally |
| Team | 1 programme lead, 6 coordinators, 12 engineers, 25 transcribers, 3 QA leads |
Cohort design
At 500 hours 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.
Recruitment must be stratified by handset and carrier as well as by dialect, which adds a screening axis the other styles do not have.
| Dimension | Typical split | Why it matters for Kannada |
|---|---|---|
| Gender | 50 / 50 | Pitch range differences change acoustic model behaviour; unbalanced cohorts bias recognition |
| Age | 18-25: 30%, 26-40: 40%, 41-60: 30% | Older speakers retain conservative Kannada forms that younger urban speakers have lost |
| Region | Karnataka / parts of Maharashtra, Tamil Nadu and Andhra Pradesh and others | Dialect spread across 5 recognised varieties |
| Education | Mixed, including below-graduate | Prompt-reading fluency correlates with education and skews prosody |
| Condition | Studio / quiet room / field | Match the noise profile of your deployment |
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.
Quality gates for telephony speech
- Codec and sample rate verified per file, rejecting any studio audio that has been downsampled to fake a telephony path
- Echo and double-talk checked on both legs
- DTMF events verified against the call log
- Level normalisation applied per leg, since handset output levels vary far more than studio microphones do
- Northern lexical items replaced with standard equivalents
- Inconsistent transliteration of English technical terms
100% technical QA, 10% content QA stratified by city, dialect, transcriber and recording condition, with automatic escalation to 100% on any failing batch.
What goes wrong on telephony speech sessions
- Studio audio downsampled to 8 kHz and passed off as telephony, which has none of the codec or packet-loss characteristics that matter
- Echo and double-talk that make the agent leg unusable
- Carrier and handset monoculture, producing a corpus that only represents one acoustic path
- Over-clean recordings from participants who move somewhere quiet to take the call, defeating the purpose
Risks at production scale in Kannada
Cost at this band is driven by: Field and rural capture ratio — mobile rig hours cost more than studio hours; Rare dialect quotas, where the last 10% of the cohort can cost as much as the first 40%.
- Speaker duplication across cities becomes a real risk at this cohort size and needs active de-duplication against voice and ID
- Rural capture depends on weather and travel in a way studio work does not, so mobile-rig batches carry schedule variance
- Quota drift compounds across six cities unless demographics are reconciled weekly rather than at the end
- 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.
Deliverables
- WAV audio to your naming convention, with the per-file manifest
- Verbatim Kannada transcripts with utterance-level timestamps
- Call metadata: duration, codec, handset class, carrier, packet-loss events
- Intent label per call and per turn
- DTMF and hold, transfer and barge-in events
- Agent and caller leg identifiers
- 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
What this trains, and what it does not
- Contact-centre and IVR ASR
- Voice bots operating over the phone network
- Intent classification on narrowband audio
- Robustness to codec and packet loss
Narrowband telephony audio is the wrong input for TTS or any wideband model — the frequency content simply is not there. Use it for models that will be deployed on a phone line and nothing else.
Frequently asked
Is 500 hours of Kannada enough?
Enough to train a deployable model for a single language, or to substantially improve a multilingual one. This is the most common production band.
Why telephony speech rather than another speech type?
Contact-centre and IVR ASR, Voice bots operating over the phone network, Intent classification on narrowband audio are what this style is the right input for. Narrowband telephony audio is the wrong input for TTS or any wideband model — the frequency content simply is not there. Use it for models that will be deployed on a phone line and nothing else.
How long does a production scale Kannada build take?
Eight to twelve weeks. Cities are staggered rather than started together, so the protocol corrections found in the first city are applied before the last one begins recording. Six to eight batches, fortnightly, each speaker-disjoint so you can train on early batches without contaminating a later evaluation split.
What does 500 hours of Kannada telephony speech cost?
Quoted per delivered hour against this specification. At this band the drivers are field and rural capture ratio — mobile rig hours cost more than studio hours and rare dialect quotas, where the last 10% of the cohort can cost as much as the first 40%. 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, dialect, transcriber and recording condition, with automatic escalation to 100% on any failing batch.
Quote this Kannada dataset
500 hours, telephony speech, Kannada — production scale. Adjust anything and send it.