Speech data collection · اردو
Urdu Speech Data Collection
Recruited-speaker speech corpora recorded to a written specification: scripted prompts, spontaneous monologue, or both, with full speaker metadata. This page covers how that works specifically for Urdu, where shares most phonology with hindi but adds perso-arabic phonemes (/q/, /x/, /ɣ/, /z/, /f/) that many speakers merge.
- Language
- Urdu (ur-IN)
- Dialects covered
- 5
- Typical programme
- 250-1,000 hours
- Cities
- Hyderabad, Lucknow, Delhi
What changes when the language is Urdu
The service specification stays constant across languages; the linguistics do not. For Urdu, three things drive the design of a speech data collection programme.
- Shares most phonology with Hindi but adds Perso-Arabic phonemes (/q/, /x/, /ɣ/, /z/, /f/) that many speakers merge
- Dialect spread: Dakhini (Hyderabad), Lucknawi, Dehlvi, Bihari Urdu
- Spoken Urdu and spoken Hindi are largely mutually intelligible; the distinction is mainly lexical and orthographic. Decide up front whether transcription is in Nastaliq, Devanagari, or both.
Technical specification
| Parameter | Standard |
|---|---|
| Sample rate | 48 kHz capture, delivered at 48/16 kHz as required |
| Bit depth | 24-bit capture, 16-bit PCM delivery |
| Format | WAV (PCM), one file per utterance or per session |
| Channels | Mono per speaker; multi-channel on request |
| Noise floor | Studio sessions below -50 dBFS; field sessions specified per project |
| Clipping | Zero tolerance; clipped takes are re-recorded, not repaired |
Urdu cohort design
Fix the script decision before fielding; retro-transcribing a Nastaliq dataset into Devanagari after delivery costs as much as the original transcription pass.
| Dimension | Typical split | Why it matters for Urdu |
|---|---|---|
| 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 Urdu forms that younger urban speakers have lost |
| Region | Uttar Pradesh / Telangana / Bihar 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 |
Process
- Requirement lock: languages, hours, speaker count, demographic quotas, recording conditions
- Prompt design and linguistic review by native reviewers
- Speaker recruitment and screening against quota, with consent capture
- Recording sessions with real-time level and prompt-coverage monitoring
- Automated technical QA on every file (SNR, clipping, duration, silence)
- Native-speaker content QA on a defined sample, escalating to 100% on failure
- Packaging, manifest generation and delivery
Urdu-specific quality rules
- Right-to-left Nastaliq tooling errors and diacritic loss
- Merged phonemes transcribed by sound rather than by etymology, or vice versa, inconsistently
- Dakhini forms replaced with standard Urdu
Every file passes automated technical checks. Content QA is sampled at 10% by default and raised per batch when the failure rate crosses the agreed threshold.
Deliverables
- Audio files in the agreed format and naming convention
- Per-utterance manifest (speaker ID, prompt ID, duration, condition)
- Speaker metadata: age band, gender, region, dialect, education band
- Consent records mapped to speaker IDs
- QA report with pass rates and rejection reasons
Worked example
A representative Urdu speech data collection engagement: 250 hours from 500 speakers, 50/50 gender, ages 18-45, spread across Hyderabad, Lucknow, Delhi, recorded to the specification above and delivered in WAV with a per-utterance manifest.
Timeline: Typical: 3-6 weeks for 100-500 hours in a single language; multi-language programmes run in parallel.
Where this data is missing today
Indian Urdu specifically, and Dakhini in particular, are absent from public data dominated by Pakistani Urdu broadcast speech.
Frequently asked
How much does Urdu speech data collection cost?
Priced per delivered hour or unit against a written spec. The cost drivers for Urdu are dialect spread, demographic narrowness and recording condition, in that order.
Which Urdu dialects are included?
By default Dakhini (Hyderabad), Lucknawi, Dehlvi, Bihari Urdu and others, tagged per speaker. You can also commission a single-dialect corpus if you are targeting one region.
Can you deliver Urdu data in our format?
Yes. Audio files in the agreed format and naming convention is the default, but naming, schema and directory structure follow your pipeline.
How long does a Urdu programme take?
Typical: 3-6 weeks for 100-500 hours in a single language; multi-language programmes run in parallel.
Request a Urdu speech data collection quote
Hours, speakers, dialects, deadline. Send what you have.