1,000 speakers of Telugu Conversational Speech

Two speakers hold an unscripted conversation seeded with a scenario, recorded on separate channels so overlap and turn-taking survive into the delivered files.

A 45–60 minute paired session with both speakers on isolated microphones, either in adjacent treated rooms or split-mic in one room with bleed measured and logged.

Yield at this style: 55–65% of recorded time is accepted. Overlap regions, crosstalk bleed and one-sided stretches all cost delivered time. The lowest-yield studio style we run, and priced accordingly.

• Scenario seeds rather than scripts — a disagreement to resolve, a plan to make, an experience to compare
• Pairing designed deliberately: familiar pairs produce natural interruption, stranger pairs produce polite turn-taking, and you need both
• Scenarios that invite disagreement, because agreeable conversation produces almost no overlap to train on
• Register mixed across pairs so the corpus is not uniformly formal
• Built against Telugu specifically: Vowel-length contrasts are phonemic and short/long confusion changes meaning outright
• Code-mixing handled explicitly rather than edited out — Hyderabad speech mixes Telugu, Urdu/Deccani, Hindi and English. A Telugu dataset for Hyderabad deployment must include Urdu-origin vocabulary.

Nine to twelve weeks, with recruitment running continuously rather than in a front-loaded phase.

Six to eight batches, speaker-disjoint by construction so held-out speakers are genuinely held out.

Split cohorts explicitly between Telangana and Andhra Pradesh and tag every speaker; models trained without the tag cannot be evaluated per region.

At 1,000 speakers 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.

Effectively doubles recruitment load, since speakers are booked in matched pairs and a single drop-out cancels the whole session. Plan on 20–25% over-recruitment.

• Vowel-length contrasts are phonemic and short/long confusion changes meaning outright
• Hyderabad speech mixes Telugu, Urdu/Deccani, Hindi and English. A Telugu dataset for Hyderabad deployment must include Urdu-origin vocabulary.
• Coastal Andhra read speech dominates. Telangana rural and Rayalaseema speech is thin, despite Hyderabad being the largest deployment market.

• Channel bleed measured on every session and rejected above the agreed threshold
• Diarisation labels verified against the isolated channels rather than inferred from the mix
• Turn boundaries and overlap regions checked by a native listener
• Speaking-time balance per pair audited, so a dominant speaker does not silently halve the session's value
• Telangana forms normalised to Coastal Andhra standard
• Long/short vowel marking errors under time pressure

100% technical QA, 10% content QA stratified by city and coordinator, with voice-based duplicate detection across the whole cohort.

• Crosstalk bleed that makes clean per-speaker training targets impossible to recover afterwards
• One speaker dominating, leaving a pair that delivers half the expected audio
• Unnatural politeness between strangers, producing clean but unrepresentative turn-taking
• Scheduling attrition — both speakers have to show up, so no-show rates compound rather than add

Cost at this band is driven by: Number of distinct demographic cells rather than total speakers.

• Speaker-disjoint splits are only trustworthy if duplicate detection is voice-based rather than ID-based, since one person can present two identities
• Coordinator-level demographic bias becomes measurable at this size and should be reported, not smoothed over
• Telugu carries 4 recognised varieties across Andhra Pradesh, Telangana, parts of Karnataka and Odisha, so the quota matrix is wider than the headline volume suggests
• Coastal Andhra read speech dominates. Telangana rural and Rayalaseema speech is thin, despite Hyderabad being the largest deployment market.

• WAV audio to your naming convention, with the per-file manifest
• Verbatim Telugu transcripts with utterance-level timestamps
• Speaker-turn segmentation with start and end timestamps
• Overlap regions marked with participating speaker IDs
• Backchannel and interruption markers
• Per-pair relationship metadata: familiar or stranger
• 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

• Speaker diarisation
• Meeting and multi-party ASR
• Turn-taking and endpointing for voice agents
• Speaker separation and target-speaker extraction

Two-party conversation does not generalise to multi-party meetings with four or more speakers, where overlap statistics change substantially. Specify that case separately.