Dataset specification · Programme scale
1,000 hours of Odia Spontaneous Speech
A programme scale build of 1,000 hours of Odia spontaneous speech. Training from scratch in a language where no adequate public corpus exists. Speakers talk unscripted on prompted topics — describing a process, recounting an event, arguing a position — with a moderator who prompts but does not lead.

- Volume
- 1,000 hours
- Scale
- Programme scale
- Per speaker
- 25–40 minutes of accepted audio per speaker
- Accepted yield
- 60–70% of recorded time is accepted
How Odia spontaneous speech is captured
Speakers talk unscripted on prompted topics — describing a process, recounting an event, arguing a position — with a moderator who prompts but does not lead.
A 60-minute session covering six to eight topics, recorded continuously and segmented afterwards into utterances at natural pause boundaries.
Yield at this style: 60–70% of recorded time is accepted. Long silences, moderator speech and abandoned topics are cut in post, so recorded hours run well ahead of delivered hours. Budget for the gap.
The specification
| Field | Value |
|---|---|
| Language | Odia (or-IN, Odia) |
| Volume | 1,000 hours |
| Equivalent | 2,000 speakers at 30 minutes each, or 1,000 speakers at one hour each |
| Speech type | Spontaneous Speech |
| Per speaker | 25–40 minutes of accepted audio per speaker |
| File granularity | Session-length WAV plus segmented utterance files with offsets into the parent |
| Segmentation | Pause-boundary segmentation, reviewed by a native listener rather than left to VAD |
| Moderator channel | Recorded separately and excluded from the delivered speaker audio |
| Disfluency convention | Filled pauses, repetitions and false starts transcribed, not normalised away |
| Dialects | Cuttack-Bhubaneswar standard, Sambalpuri (Kosli), Ganjami, Baleswari |
| Transcription | Verbatim, native-speaker, second-pass reviewed |

Designing the topic bank for Odia
- Topic banks graded by familiarity, so speakers across education and occupation bands all have something to say
- Open prompts only — anything answerable with yes or no produces thirty seconds of audio and a stalled session
- Culturally grounded topics per region, since a prompt that works in Mumbai can draw blank looks in Guwahati
- Topic rotation across the cohort so the corpus does not over-represent a handful of subjects
- Built against Odia specifically: Retains a distinct retroflex ଳ and a full retroflex series
- Code-mixing handled explicitly rather than edited out — Urban Odia mixes Hindi and English; western Odisha mixes Chhattisgarhi and Sambalpuri forms.
Running a programme scale Odia build
Twelve to sixteen weeks. This is a programme with its own governance rather than a project — weekly demographic reconciliation, a standing protocol review and a named counterpart on your side.
Ten to twelve batches, fortnightly, with a formal acceptance test per batch. Rejected batches are re-recorded rather than patched, so schedule contingency is built into the plan.
Western Odisha recruitment requires local field partners; remote-only recruitment yields an all-coastal cohort.
| Parameter | At this volume |
|---|---|
| Cities | Eight to ten — Bhubaneswar, Cuttack, Sambalpur, Berhampur, Rourkela |
| Studios | Ten rooms plus four mobile rigs |
| Recruiters | Ten coordinators, two regional managers, one programme lead |
| Speakers | ~2,000–2,400 |
| Sessions per day | 70–90 nationally |
| Team | 1 programme lead, 2 regional managers, 10 coordinators, 20 engineers, 45 transcribers, 5 QA leads |
Cohort design
At 1,000 hours 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.
Screening is for willingness to talk, not literacy, which opens the cohort to speakers a scripted protocol would exclude. Expect to over-recruit by 15% for speakers who freeze on the day.
| Dimension | Typical split | Why it matters for Odia |
|---|---|---|
| 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 Odia forms that younger urban speakers have lost |
| Region | Odisha / parts of Jharkhand, West Bengal, Chhattisgarh 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 |
Odia-specific considerations
- Retains a distinct retroflex ଳ and a full retroflex series
- Urban Odia mixes Hindi and English; western Odisha mixes Chhattisgarhi and Sambalpuri forms.
- Odia is one of the least-resourced major Indian languages. Sambalpuri and Ganjami are effectively absent from public data.
Quality gates for spontaneous speech
- Segment boundary review — bad boundaries produce truncated words that poison training more than they help
- Disfluency transcription consistency audited across transcribers, since conventions drift fast on this style
- Moderator speech confirmed absent from delivered segments
- Topic distribution checked per speaker so one dominant subject does not skew the language model
- Sambalpuri normalised into coastal Odia
- Unicode confusables between Odia and Bengali characters when transcribers reuse tooling
100% technical QA, 7% content QA stratified across every axis, plus a blind 1% re-transcription audit measuring inter-annotator agreement across the whole programme.
What goes wrong on spontaneous speech sessions
- Speakers who dry up after a minute, leaving sessions that look complete by duration but are mostly silence
- Drift into a reading register when a speaker becomes self-conscious about the microphone
- Moderator over-prompting, which turns a monologue corpus into an interview corpus
- Transcriber normalisation — quietly cleaning up disfluencies destroys the exact signal this style exists to capture
Risks at programme scale in Odia
Cost at this band is driven by: Programme management overhead, which is real at this scale and should be quoted explicitly rather than hidden in the hourly rate; The tail of rare dialect and demographic quotas.
- Transcriber consistency across a 45-person team is the dominant quality risk and needs continuous calibration, not a one-time briefing
- Speaker pool exhaustion in smaller cities, where the genuinely available cohort is finite
- Specification drift over three months as your model team learns what it actually needs — build a change-control step in rather than pretending it will not happen
- Odia carries 5 recognised varieties across Odisha, parts of Jharkhand, West Bengal, Chhattisgarh and Andhra Pradesh, so the quota matrix is wider than the headline volume suggests
- Odia is one of the least-resourced major Indian languages. Sambalpuri and Ganjami are effectively absent from public data.
Deliverables
- WAV audio to your naming convention, with the per-file manifest
- Verbatim Odia transcripts with utterance-level timestamps
- Filled-pause and false-start markers
- Segment offsets into the parent session file
- Topic label per segment
- Speech-rate and pause-density statistics per speaker
- 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
- Robust ASR for real user speech
- Language modelling on natural syntax
- Disfluency detection and removal
- Prosody and speech-rate modelling
Phonetic balance cannot be guaranteed — speakers say what they say. If you need specific phone contexts or a controlled lexicon, this style has to be paired with a scripted layer.
Frequently asked
Is 1,000 hours of Odia enough?
Enough to train from scratch in a single language, or to build a strong multilingual foundation across a language family.
Why spontaneous speech rather than another speech type?
Robust ASR for real user speech, Language modelling on natural syntax, Disfluency detection and removal are what this style is the right input for. Phonetic balance cannot be guaranteed — speakers say what they say. If you need specific phone contexts or a controlled lexicon, this style has to be paired with a scripted layer.
How long does a programme scale Odia build take?
Twelve to sixteen weeks. This is a programme with its own governance rather than a project — weekly demographic reconciliation, a standing protocol review and a named counterpart on your side. Ten to twelve batches, fortnightly, with a formal acceptance test per batch. Rejected batches are re-recorded rather than patched, so schedule contingency is built into the plan.
What does 1,000 hours of Odia spontaneous speech cost?
Quoted per delivered hour against this specification. At this band the drivers are programme management overhead, which is real at this scale and should be quoted explicitly rather than hidden in the hourly rate and the tail of rare dialect and demographic quotas. Send the spec and you get one fixed figure.
How much QA is applied at this volume?
100% technical QA, 7% content QA stratified across every axis, plus a blind 1% re-transcription audit measuring inter-annotator agreement across the whole programme.
Quote this Odia dataset
1,000 hours, spontaneous speech, Odia — programme scale. Adjust anything and send it.