Code-Switching ASR · ଓଡ଼ିଆ
Odia Data for Code-Switching ASR
Recognising speech that switches between an Indian language and English several times per sentence. In Odia, the binding constraint is usually dialect coverage and code-mixing, not raw hours.
- Language
- Odia
- Primary metric
- Switch-point accuracy
- Typical volume
- 100-500 hours
Data profile required
- Genuinely code-mixed spontaneous speech
- Per-token language ID labels
- A fixed rule for script of English tokens
What Odia adds to the requirement
- Retains a distinct retroflex ଳ and a full retroflex series
- Sambalpuri differs from coastal Odia enough that many speakers treat it as a separate language
- Dialects to cover: Cuttack-Bhubaneswar standard, Sambalpuri (Kosli), Ganjami, Baleswari
- Urban Odia mixes Hindi and English; western Odisha mixes Chhattisgarhi and Sambalpuri forms.
Metrics to track
- Switch-point accuracy
- Mixed-utterance WER
- Language ID token accuracy
Failure modes
- Concatenating monolingual data and calling it code-mixed
- Leaving script conventions to individual annotators
For Odia specifically: Odia is one of the least-resourced major Indian languages. Sambalpuri and Ganjami are effectively absent from public data.
Recommended cohort
Western Odisha recruitment requires local field partners; remote-only recruitment yields an all-coastal cohort.
| 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 |
Suggested programme shape
Start with an evaluation set of 100 speakers spread across every Odia dialect in scope, collected before training data. Then field 100-500 hours of training data from disjoint speakers.
This ordering is what makes the improvement measurable rather than assumed.
Frequently asked
Is there usable public Odia data for code-switching asr?
Odia is one of the least-resourced major Indian languages. Sambalpuri and Ganjami are effectively absent from public data.
How many Odia speakers do we need?
300-800 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 Odia data for code-switching asr
Send the target metric and the languages in scope.