Sinhala speech dataset
We source Sinhala speech data to order: speaker recruitment, recording, transcription and annotation, delivered with the consent documentation that makes the dataset usable rather than merely delivered.
What makes Sinhala hard to collect
Everyday Sinhala conversation is heavily embedded with English words, especially in the Colombo urban belt. Treating this mixed speech as pure Sinhala strips out high-frequency loanwords as if they were errors.
This is the part that cannot be templated. Every language has a specific failure mode, and a project that does not plan for it produces data that looks complete and trains badly.
Language profile
| Language | Sinhala |
|---|---|
| Primary region | South Asia |
| Writing system | Sinhala |
| Collection difficulty | Code-switching in daily speech |
What we deliver for Sinhala
-
Collection to your specification
Scripted or unscripted, in the language, domain and conditions your task needs. Specified separately where the variants need different contributor pools.
-
Labels to your convention
Orthographic, phonetic or categorical, with the guideline written before production and shared with you for review.
-
Contributor metadata
The attributes that let you slice the set rather than take it whole. The ones your task turns on, not a fixed list.
-
Consent documentation
Signed contributor consent covering the intended use, plus collection methodology and the annotation guideline.
-
Pilot batch
A small batch first, which you can reject. Misalignments surface after a few hours rather than at delivery.
-
Delivery in your format
File format, structure, segmentation and metadata schema set to your pipeline's requirements.
More on Sinhala
-
Sinhala ASR datasets
What has to be settled before transcription starts, and why speaker count matters more than hours.
-
Sinhala TTS datasets
Recording one voice properly, and the script decisions that decide whether the result is usable.
-
Sinhala Voice datasets
Identification, verification and cloning need different data, and the consent has to match the purpose.
-
Multilingual projects
Running Sinhala as part of a multi-language delivery, and what changes.
Questions we get about Sinhala
How many distinct speakers can you provide for Sinhala?
It depends on the specification and the timeline, and we will give a real number rather than a target. Speaker recruitment is usually the step that sets the schedule for Sinhala, so the answer to this question is also the answer to how long the project takes.
Can you annotate to a custom guideline?
Yes, and for Sinhala we would recommend it. The default conventions for this language leave several decisions open, and those decisions are exactly where annotators diverge. Send us your guideline, or we will draft one and you can review it before production.
Do you offer a sample before we commit?
Yes. Select a free sample in the request form and describe what you need. A pilot batch is the cheapest way to establish whether the quality bar is reachable before committing to a full run.
What if Sinhala is not something you can source?
Then we will tell you rather than take the order. We would rather decline a project than deliver something that does not meet the specification.
Request Sinhala speech data
Tell us the language, the hours, and what the data needs to look like. You will get a real number and a real timeline, not a range. If we cannot source it well, we will tell you that instead.
- Pilot batch before the full run, so problems surface early.
- Consent documentation delivered with the data.
- No medical or clinical data. No recorded telephone calls.
- You send the spec Language, hours, recording conditions, and the deadline.
- We reply within two business days A real number and a real timeline, not a range.
- You approve a pilot batch A small run first, so problems surface before the full order.
- Full run, then delivery with documents Audio, transcripts, and the consent record for every speaker.