50 hours of Assamese 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 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.

Three to four weeks from signed specification. Recruitment is the critical path, not recording — the studio time itself is under two weeks.

Two batches: a 10-hour first batch in week two so you can run it through your pipeline while the rest is still recording, then the balance on completion.

Expect longer fielding times and higher per-hour cost than for Hindi or Marathi; the speaker pool with transcription-grade literacy is smaller.

At 50 hours the cohort is deliberately simplified: two or three dialect groups rather than the full spread, with quotas enforced in aggregate. A build this size cannot support per-cell targets and should not claim to.

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.

• 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.

• 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% content QA. At this volume there is no reason to sample, and a pilot exists precisely to surface specification problems.

• 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: Fixed setup cost is amortised over very few hours, so the per-hour rate is at its highest here; Narrow demographic requirements bite hardest at small cohort sizes.

• The specification itself is usually the risk, not delivery — pilots exist to find the clauses that do not survive contact with real speakers
• A single-city cohort will not represent the language nationally, and reading pilot results as national is the most common mistake at this band
• 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.

• 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

• 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.