What is ASR training data? Audio, transcripts and a usable training record Understand ASR audio–text pairs, segment boundaries, transcript conventions, source sample rates and an illustrative record you can inspect before training. ASR training data teaches automatic speech recognition systems to map audio to written text. A typical supervised example contains an audio interval and its corresponding transcript, with enough identifiers and preparation metadata to reproduce the pairing. Speaker labels, word timestamps and phoneme boundaries are additional layers, not universal requirements for every recognition recipe. The right record depends on the selected model and the errors the project is trying to reduce. The core pair is audio plus the words actually spoken In supervised recognition, the audio and target text must describe the same speech. A fluent summary, edited show notes or a translation is not an interchangeable transcript. If an interval contains “Friday—sorry, Thursday,” a verbatim reference needs a rule for the correction rather than silently changing the utterance into a clean instruction. The [Hugging Face ASR task guide](https://huggingface.co/docs/transformers/en/tasks/asr) illustrates an audio/text training workflow with model-specific preprocessing. Treat that as an implementation example, not a promise that one file format or sampling rate works for every model. Keep the original recording separate from any derived training inputs. An inspectable example record This invented record describes a segment cut from a longer session. It preserves both a source sampling rate and the rate selected for one model input. The numbers are illustrative and do not describe AIPodcast inventory or a standard delivery package. { "recording_id": "session-023", "segment_id": "session-023-012400-018100", "start_s": 12.4, "end_s": 18.1, "transcript_raw": "Please reschedule the delivery.", "transcript_normalized": "please reschedule the delivery", "speaker_group": "spk-07", "source_sample_rate_hz": 48000, "model_input_sample_rate_hz": 16000, "text_policy_version": "recognition-v1" } What the fields let a reviewer verify The segment lasts 5.7 seconds, calculated as 18.1 minus 12.4. A reviewer should be able to find that interval in the source and confirm the words. The segment identifier gives a stable reference; the recording identifier connects related cuts; the speaker group can support evaluation grouping when its evidence is trustworthy. An opaque ID by itself does not prove speaker identity. Raw and normalized transcripts serve different purposes. The raw reference can preserve punctuation and spoken form, while the normalized target follows a documented scoring or training convention. Store the transformation version so a later capitalization or number rule does not silently change the dataset. If a model requires a different normalization policy, derive a new target instead of overwriting the source text. Recognition, diarization and synthesis need different targets Recognition asks what was said. Diarization asks which speaker spoke when. Synthesis generates speech from an input representation and introduces a different relationship between text, voice and permitted use. A file can support several tasks, but a label needed for one task should not be assumed available or necessary for all of them. Layer Question it supports What it does not establish Segment transcript Which words occur in this audio interval? Precise word boundaries or speaker identity Speaker turn annotation Who spoke during each labeled interval? Correct words or permission to reproduce a voice Forced alignment Where supplied words are estimated to occur That the supplied transcript contains every spoken word Source and use documentation What material and project scope were reviewed Model accuracy or a universal license for downstream uses File preparation should follow the selected model Check the recipe’s input channel, sample-rate and length constraints, then document the actual conversion. Resampling changes the digital sampling grid; it does not make a noisy source into a clean studio recording. Mono mixing can erase channel separation useful for other tasks. Preserve the unmodified originals and identify any channel selection, gain change, filtering or clipping. For comparison, the [LibriSpeech release](https://www.openslr.org/12) describes 16 kHz read English speech. That is one corpus design, not a universal ASR requirement. Telephone conversation, long interviews and accented domain speech can have different distributions. Match the evaluation question to the expected source rather than treating a recognizable benchmark name as proof of fit. Review pairing failures before choosing more hours Inspect clipped sentence starts, transcripts copied from the wrong edition, silent files paired with text, overlapping speakers and words hidden by music. Report unreadable or uncertain speech explicitly under the reference policy. Do not force an annotator to invent a word to make an example look complete. A small audit can follow one record from original session through segmentation, transcript review and model-input conversion. Compare source duration against segment duration, check that offsets use one declared clock, and verify that related recordings stay grouped during evaluation. These checks explain defects that an aggregate file count cannot. A useful first sourcing request Describe the deployment setting, language varieties, channel conditions, target transcript policy and grouping requirement. Include a few representative utterances and error cases: names, numbers, corrections, overlapping talk or specialized terms. Ask which annotations already exist and which require new review. AIPodcast can discuss candidate sources and preparation against that request. Source availability, actual recording format, annotation quality, permitted use and pricing are confirmed for the selected project. This article does not establish stocked ASR or TTS corpora, guaranteed word-aligned files or a minimum number of hours. Do all ASR datasets need word timestamps? No. Some supervised recipes use segment-level audio/text pairs. Add reviewed word boundaries when the model workflow, evaluation or product needs them; specify their accuracy separately. Is converting a file to 48 kHz an upgrade in source quality? No. A higher output sampling rate does not recreate information absent from the source. Follow the model input requirement and preserve the original recording metadata. Can show notes serve as ASR ground truth? Only if they are actually a reviewed transcript of the selected audio under the chosen policy. Summaries and edited descriptions usually answer another question. Research method: Fiund research desk; public sources, explicit worked-example labels and project-specific availability review. Editorial contact: hello@fiund.com. Sources Transformers automatic speech recognition task guide: https://huggingface.co/docs/transformers/en/tasks/asr LibriSpeech ASR corpus, SLR12: https://www.openslr.org/12