Middle East & North Africa · Arabic / Latin
Kurdish Read Speech Dataset
Kurdish Read Speech delivered to your specification. A catalog entry, not a stock listing. This page covers what is specifically hard about this pairing, and which fields your specification needs to pin down.
Why Read Speech in Kurdish is its own problem
Read speech needs a text to read, and for Kurdish that is already a decision: the same branch may be written in Latin script in Turkey and Syria and in Arabic script in Iraq and Iran, so the prompt text has to be prepared in a fixed alphabet, and the Sorani Arabic-script text needs its vowel marks handled consistently. Reading aloud also exposes the reader's schooling. A speaker educated in Turkish or Arabic may hesitate over Kurdish orthography, and the hesitation lands in the recording. The result is a batch where fluency varies with literacy in the script, not with command of the language.
The field to pin down first: The alphabet and spelling standard for the prompt text are fixed in writing and attached to the delivery, and readers are screened for literacy in that script before recording rather than after.
At a glance
| Language | Kurdish |
|---|---|
| Primary region | Middle East & North Africa |
| Writing system | Arabic / Latin |
| Category | Read Speech |
| Specification field to settle first | The alphabet and spelling standard for the prompt text are fixed in writing and attached to the delivery, and readers are screened for literacy in that script before recording rather than after. |
| Delivery | Sourced to order, pilot batch before the full run |
What Read Speech data is
Recordings of speakers reading specified text, with clear pronunciation and known text, the base material for TTS and ASR.
What buyers get wrong about it
The trap with read speech is that it is too clean. It comes out sounding like a news anchor, and a model trained on it underperforms in real conditions. We collect an extra set at natural speaking rate as a comparison.
The specification field that decides the quote
Studio (low noise floor) or home (real environment). The two differ in both signal-to-noise ratio and price.
The language side: what Kurdish demands
The two main branches of Kurdish (Sorani and Kurmanji) have low mutual intelligibility, close to two separate languages, and they use different scripts. Public resources are so thin that even TTS datasets are rare. A textbook scarce language.
What we can put in this delivery
-
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.
What arrives in a delivery
| Component | What it is |
|---|---|
| The data files | Format, structure and segmentation set to your pipeline. Named to a convention you specify. |
| Labels or transcription | Orthographic, phonetic or categorical, produced under a guideline you review before production starts. |
| Contributor metadata | The attributes that let you slice the set: age band, gender, region, dialect background, or whatever your task turns on. |
| Collection conditions | Environment, device and, where it can be measured, signal quality: recorded per file. |
| Annotation guideline | The document the annotators worked from, so you can reproduce the conventions on your own data. |
| Consent records | Signed contributor consent covering your intended use, plus cross-border transfer terms where they apply. |
| Collection methodology | How contributors were recruited, screened and scheduled. The part that tells you how biased the pool is. |
| Quality report | Pilot outcome, re-work log, and the annotator agreement figures where the task supports measuring them. |
Questions we get about Kurdish Read Speech Dataset
How many distinct speakers can you provide for Kurdish Read Speech Dataset?
It depends on the specification and the timeline, and we will give a real number rather than a target. For this pairing, speaker recruitment is usually the step that sets the schedule. The alphabet and spelling standard for the prompt text are fixed in writing and attached to the delivery, and readers are screened for literacy in that script before recording rather than after.
Can you annotate to our own guideline instead of the default?
Yes, and for this pairing we would recommend it. Read speech needs a text to read, and for Kurdish that is already a decision: the same branch may be written in Latin script in Turkey and Syria and in Arabic script in Iraq and Iran, so the prompt text has to be prepared in a fixed alphabet, and the Sorani Arabic-script text needs its vowel marks handled consistently. That is exactly the kind of decision a default guideline leaves open, and it is where annotators diverge. Send us your guideline, or we will draft one and you can review it before production starts.
Do you offer a sample before we commit to a full run?
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 for Kurdish Read Speech Dataset before committing to the full volume.
Is the data licensed or owned outright?
Licensing terms are set per project, so tell us how the model will be used and whether it will be distributed. Consent documentation travels with the data either way, and we do not handle medical or clinical data or recorded telephone calls.
Other datasets in Kurdish
-
Kurdish Short Video Speech
Speech in the talking-head style of short video (fast, emotionally strong, colloquial), used for short video subtitles and content understanding.
-
Kurdish Live Stream Speech
Long-session spoken content from live streams (host monologue and responses to audience interaction), unscripted and spoken quickly.
-
Kurdish Voice Assistant
Command and dialogue data for voice assistants, usually with intent annotation, covering the full chain from wake word to understanding to response.
-
Kurdish Elderly Voice
Speech data from elderly speakers, usually stratified by age band and health status, used for voice products built for older users.
-
Kurdish Accented English
English speech from non-native speakers or specific regional accents, grouped by accent origin, used to improve accent robustness in ASR.
-
Kurdish Speech Translation
Parallel data pairing source-language audio with target-language translation, used for speech-to-text and speech-to-speech translation models.
Read Speech in other languages
Request Kurdish Read Speech Dataset
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.