Sub-Saharan Africa · Latin / Ajami

Hausa Read Speech Dataset

Hausa read speech 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 read speech in Hausa is its own problem

Hausa read speech is a good technical fit: the language has a settled written standard and speakers read it comfortably. The complication is variety. The standard text is Kano-based, and readers from Sokoto, Katsina, or Niger read the same passage with their own tone and length realizations, so the acoustics differ although the text is identical. Which realization a batch contains has to be known, and plain Boko gives no ground truth for tone or length in the text itself.

The field to pin down first: Annotate the reader's variety per record and deliver in batches by variety; and decide whether the reading text ships with tone and vowel-length marking, since plain Boko leaves both entirely to the reader.

At a glance

LanguageHausa
Primary regionSub-Saharan Africa
Writing systemLatin / Ajami
CategoryRead Speech
Specification field to settle firstAnnotate the reader's variety per record and deliver in batches by variety; and decide whether the reading text ships with tone and vowel-length marking, since plain Boko leaves both entirely to the reader.
DeliverySourced 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 Hausa demands

Hausa is written in two scripts at once: Latin (Boko) dominates, while Arabic script (Ajami) is used in religious contexts. Running both in parallel means the script-to-speech mapping has to be defined separately for each.

More on Hausa 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 Hausa Read Speech

How many distinct speakers can you provide for Hausa Read Speech?

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. Annotate the reader's variety per record and deliver in batches by variety; and decide whether the reading text ships with tone and vowel-length marking, since plain Boko leaves both entirely to the reader.

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

Yes, and for this pairing we would recommend it. Hausa read speech is a good technical fit: the language has a settled written standard and speakers read it comfortably. 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 Hausa Read Speech 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 Hausa

  • Hausa Live Stream Speech

    Long-session spoken content from live streams — host monologue and responses to audience interaction — fast-paced and heavily improvised.

  • Hausa Voice Assistant

    Command and dialogue data for voice assistants, usually with intent annotation, covering the full chain from wake word to understanding to response.

  • Hausa Elderly Voice

    Speech data from elderly speakers, usually stratified by age band and health status, used for voice products built for older users.

  • Hausa Accented English

    English speech from non-native speakers or specific regional accents, grouped by accent origin, used to improve accent robustness in ASR.

  • Hausa Speech Translation

    Parallel data pairing source-language audio with target-language translation, used for speech-to-text and speech-to-speech translation models.

  • Hausa In-the-Wild Speech

    Speech collected under fully natural conditions — no studio, no topic constraints — as close to real usage as collection gets.

All Hausa data →

Read Speech in other languages

All Read Speech data →

Request Hausa Read Speech

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