Middle East & North Africa · Arabic / Latin

Kurdish Speech Commands Dataset

Kurdish speech commands sourced to your specification — no inventory, no fixed listing. This page covers what is specifically hard about this pairing, and which fields your specification needs to pin down.

Why speech commands in Kurdish is its own problem

A Kurdish command list is not portable. The everyday word for a basic action differs between Kurmanji and Sorani, so a list built in one branch is unusable in the other, and within a single branch the word a speaker reaches for tracks their country — one form where Turkish influence dominates, another where Arabic does. Wake-word work also needs the list written down in a fixed script, and the two branches do not share one. Fixing the branch, the country, and the written form before recording is what keeps the batch usable; adding entries later means a fresh round of speakers.

The field to pin down first: The command list is frozen per branch and per country before recording, with its written form fixed in one script; a list carried over from the other branch cannot be recorded as it stands.

At a glance

LanguageKurdish
Primary regionMiddle East & North Africa
Writing systemArabic / Latin
CategorySpeech Commands
Specification field to settle firstThe command list is frozen per branch and per country before recording, with its written form fixed in one script; a list carried over from the other branch cannot be recorded as it stands.
DeliverySourced to order, pilot batch before the full run

What speech commands data is

Targeted recordings of short command words or phrases, usually with many speakers reading each entry several times over, used for wake words and on-device command recognition.

What buyers get wrong about it

What buyers consistently underestimate is the repetition count — a single command entry needs at least a few dozen distinct speakers, each reading it multiple times, to cover pronunciation variation.

The specification field that decides the quote

Once the word list is locked it cannot change; adding words midway means starting a new batch.

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.

More on Kurdish speech data →

What we can put in this delivery

  • Read and conversational speech

    Scripted recording for TTS, and unscripted conversation for recognition. Specified separately because they need different speaker pools.

  • Transcription to your convention

    Orthographic or phonetic, with the guideline written before production and shared with you for review.

  • Speaker metadata

    Age band, gender, region and dialect background per file, so you can slice the dataset rather than take it whole.

  • Consent documentation

    Signed speaker 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

    Audio format, sampling rate, segmentation length and metadata schema set to your pipeline's requirements.

What arrives in a delivery

ComponentWhat it is
Audio filesFormat, sampling rate and segmentation length set to your pipeline. Named to a convention you specify.
TranscriptionOrthographic or phonetic, produced under a guideline you review before production starts.
Speaker metadataAge band, gender, region and dialect background per file, plus a speaker identifier so the dataset can be sliced.
Recording conditionsEnvironment, device and, where relevant, measured signal-to-noise ratio per file.
Annotation guidelineThe document the annotators worked from, so you can reproduce the conventions on your own data.
Consent recordsSigned speaker consent covering your intended use, with the transfer mechanism addressed where required.
Collection methodologyHow speakers were recruited, screened and scheduled — the part that tells you how biased the pool is.
Quality reportPilot outcome, re-work log, and the annotator agreement figures where the task supports measuring them.

Questions we get about Kurdish Speech Commands

How many distinct speakers can you provide for Kurdish Speech Commands?

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 command list is frozen per branch and per country before recording, with its written form fixed in one script; a list carried over from the other branch cannot be recorded as it stands.

Can you annotate to our own guideline instead of the default?

Yes, and for this pairing we would recommend it. A Kurdish command list is not portable. 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 Speech Commands 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 Audiobook

    Continuous long-form narration in audiobook style, steady in intonation and generous in duration, the main source material for high-quality TTS.

  • 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 — fast-paced and heavily improvised.

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

All Kurdish data →

Request Kurdish Speech Commands

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.

We reply within two business days. Your details are used only to answer this request. See our privacy policy.

Contact

Talk to a human

Send a specification and we will come back with a real number and timeline.

Submit a sourcing request

Or email hello@linguacorpus.com