Dataset · ta-IN · Scripted Speech
Buy a Tamil scripted speech dataset
Speakers read prompts from a phonetically balanced script shown one line at a time, with retakes on any flubbed or misread line. Available for Tamil as a licensed build against your specification, with audio, verbatim transcripts, speaker metadata and consent records.
- Language
- Tamil (Tamil)
- Type
- Scripted Speech
- Per speaker
- 20–30 minutes of accepted audio per speaker
- Accepted yield
- 85–90% of recorded time is accepted
How Tamil scripted speech is recorded
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.
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.
What is in the package
- 16-bit PCM WAV audio, captured at 48 kHz / 24-bit and delivered at your target rate
- Verbatim Tamil 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, device
- Consent records mapped to speaker IDs and retained for audit
- Speaker-disjoint train / dev / test splits
Specification
| Field | Standard value |
|---|---|
| Language | Tamil (ta-IN) |
| Speech type | Scripted Speech |
| Per speaker | 20–30 minutes of accepted audio per speaker |
| File granularity | One WAV per prompt, named by prompt ID and speaker ID |
| Prompt coverage | Triphone-balanced script with digit, date, name and domain-lexicon blocks |
| Leading/trailing silence | 200 ms padded, verified automatically on every file |
| Alignment | Prompt text is ground truth; deviations are flagged rather than silently corrected |
| Dialects covered | Chennai (Madras Bashai), Kongu (Coimbatore), Madurai, Nellai (Tirunelveli) |
| Recording cities | Chennai, Coimbatore, Madurai, Tiruchirappalli |
| Transcription | Native verbatim, second-pass reviewed |
Quality gates applied to scripted speech
The failure modes this style is prone to: reading voice: flat prosody and unnatural stress that trains a model on speech nobody actually produces
- 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
Pricing and volumes
| Volume | Indicative range | Delivery |
|---|---|---|
| 50 hours (pilot-scale) | ₹1,60,000 – ₹3,25,000 | 3-4 weeks |
| 250 hours | ₹7,60,000 – ₹15,43,750 | 5-8 weeks |
| 1,000 hours | ₹27,20,000 – ₹55,25,000 | 10-16 weeks |
Bands, not a price list. A signed specification converts them into one fixed figure, and staged delivery lets you start training before the full corpus lands.
Why generic Tamil corpora underperform
Almost all public Tamil audio is literary read speech from news or scripture. Genuine colloquial Tamil, especially southern and Kongu varieties, is the single biggest gap for anyone building Tamil voice products.
Tanglish is the default urban register. Technology, finance, and workplace vocabulary is largely English embedded in Tamil syntax.
- Transcribers normalising spoken Tamil into literary Tamil, destroying the acoustic-text alignment
- ழ / ள / ல confusion
- Inconsistent handling of English insertions: Tamil script transliteration vs Latin script must be fixed in the guide
Licensing and compliance
- Perpetual, transferable licence covering model training, derivative models and commercial deployment
- Written informed consent from every speaker, retained and auditable
- Compliant with India's DPDP Act 2023 handling requirements and mapped to GDPR obligations for EU buyers
- No scraped, resold or re-licensed third-party audio in any delivery
How buying works
- Send your specification or use the standard one above
- Receive a fixed scope, price and delivery schedule within one working day
- Optional paid pilot of 10-20 hours against the same spec
- Recruitment and recording begin on signature, with staged batches
- Acceptance testing per batch, then final delivery with the full manifest
Frequently asked
Can I buy an off-the-shelf Tamil scripted speech dataset today?
We build to specification rather than reselling a fixed corpus, because off-the-shelf Tamil audio almost never matches a real deployment's dialect mix and noise profile. A 50-hour build ships in three to four weeks.
What licence do we get?
A perpetual, transferable licence with full IP transfer on delivery. You can train, distribute and commercialise models built on the data without further payment.
Can we get a free sample?
Yes — a short sample reflecting the agreed specification is provided before the pilot is signed, so you can check transcript quality and audio characteristics.
Which Tamil dialects are included?
By default Chennai (Madras Bashai), Kongu (Coimbatore), Madurai and others, with quotas set at recruitment. You can weight the mix to match where your product is deployed.
Related pages
Quote this Tamil dataset
Tell us the volume and dialect mix for Tamil scripted speech and you get a fixed price and delivery date.