Dataset specification · Flagship cohort
2,000 speakers of Assamese Conversational Speech
A flagship cohort build of 2,000 speakers of Assamese conversational speech. Maximum speaker diversity, for foundation work or a reference corpus where per-cell statistics must hold. Two speakers hold an unscripted conversation seeded with a scenario, recorded on separate channels so overlap and turn-taking survive into the delivered files.

- Volume
- 2,000 speakers
- Scale
- Flagship cohort
- Per speaker
- 20–30 minutes of accepted audio per speaker, in pairs
- Accepted yield
- 55–65% of recorded time is accepted
How Assamese conversational speech is captured
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.
The specification
| Field | Value |
|---|---|
| Language | Assamese (as-IN, Assamese (Eastern Nagari)) |
| Volume | 2,000 speakers |
| Equivalent | 1,000 hours at 30 minutes per speaker |
| Speech type | Conversational Speech |
| Per speaker | 20–30 minutes of accepted audio per speaker, in pairs |
| Channels | Two, one per speaker, never mixed down before delivery |
| Channel isolation | Bleed measured per session and logged; sessions over threshold are re-recorded |
| Overlap | Preserved, timestamped and labelled rather than edited out |
| File granularity | Per-channel session WAV plus a turn-level manifest with speaker IDs |
| Dialects | Kamrupi, Goalparia, Upper Assam (Sibsagar standard), Barak Valley contact varieties |
| Transcription | Verbatim, native-speaker, second-pass reviewed |

Designing the scenarios for Assamese
- 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 Assamese specifically: Assamese has the voiceless velar fricative /x/, unique among major Indian languages and routinely mis-modelled
- Code-mixing handled explicitly rather than edited out — Assamese speech mixes Hindi, English and Bengali, with substantial contact influence in Barak Valley and tea-garden communities.
Running a flagship cohort Assamese build
Sixteen to twenty-two weeks, run in waves so that recruitment in the harder catchments starts early rather than being left to the end.
Ten to twelve batches with rolling demographic reconciliation, since a quota gap discovered in week eighteen is very expensive to close.
Expect longer fielding times and higher per-hour cost than for Hindi or Marathi; the speaker pool with transcription-grade literacy is smaller.
| Parameter | At this volume |
|---|---|
| Cities | Twelve or more, including rural catchments — Guwahati, Jorhat, Dibrugarh, Silchar, Tezpur |
| Studios | Twelve rooms plus five mobile rigs |
| Recruiters | Fourteen coordinators, three regional managers, one programme director |
| Audio yield | ~1,000 hours at 30 minutes per speaker |
| Sessions per day | 90–110 |
| Team | 1 programme director, 3 regional managers, 14 coordinators, 24 engineers, 45 transcribers, 6 QA leads |
Cohort design
At 2,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.
| Dimension | Typical split | Why it matters for Assamese |
|---|---|---|
| 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 Assamese forms that younger urban speakers have lost |
| Region | Assam / Arunachal Pradesh / parts of Nagaland and Meghalaya and others | Dialect spread across 4 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 |
Assamese-specific considerations
- Assamese has the voiceless velar fricative /x/, unique among major Indian languages and routinely mis-modelled
- Assamese speech mixes Hindi, English and Bengali, with substantial contact influence in Barak Valley and tea-garden communities.
- Extremely low-resource. Almost no spontaneous Assamese speech data exists publicly, and non-standard dialects have none.
Quality gates for conversational speech
- 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
- Bengali characters substituted for Assamese ৰ / ৱ
- Goalparia and Kamrupi forms standardised to Sibsagar Assamese
100% technical QA, 7% content QA stratified across every axis, blind re-transcription audit, and per-cell demographic sign-off before final acceptance.
What goes wrong on conversational speech sessions
- 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
Risks at flagship cohort in Assamese
Cost at this band is driven by: Long-tail demographic cells, which dominate both cost and schedule at this size.
- The final 15% of the cohort — the rarest demographic cells — routinely takes as long as the first half and should be scheduled first, not last
- Speaker pool exhaustion is a hard constraint in all but the largest languages
- Voice-based duplicate detection across 2,000 speakers is a genuine engineering task, not a spreadsheet check
- Assamese carries 4 recognised varieties across Assam, Arunachal Pradesh, parts of Nagaland and Meghalaya, so the quota matrix is wider than the headline volume suggests
- Extremely low-resource. Almost no spontaneous Assamese speech data exists publicly, and non-standard dialects have none.
Deliverables
- WAV audio to your naming convention, with the per-file manifest
- Verbatim Assamese (Eastern Nagari) 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
What this trains, and what it does not
- 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.
Frequently asked
Is 2,000 speakers of Assamese enough?
Enough for foundation-scale speaker diversity and for a reference cohort with statistically meaningful per-dialect and per-demographic cells.
Why conversational speech rather than another speech type?
Speaker diarisation, Meeting and multi-party ASR, Turn-taking and endpointing for voice agents are what this style is the right input for. Two-party conversation does not generalise to multi-party meetings with four or more speakers, where overlap statistics change substantially. Specify that case separately.
How long does a flagship cohort Assamese build take?
Sixteen to twenty-two weeks, run in waves so that recruitment in the harder catchments starts early rather than being left to the end. Ten to twelve batches with rolling demographic reconciliation, since a quota gap discovered in week eighteen is very expensive to close.
What does 2,000 speakers of Assamese conversational speech cost?
Quoted per delivered hour against this specification. At this band the drivers are long-tail demographic cells, which dominate both cost and schedule at this size. 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, blind re-transcription audit, and per-cell demographic sign-off before final acceptance.
Quote this Assamese dataset
2,000 speakers, conversational speech, Assamese — flagship cohort. Adjust anything and send it.