A transcript, a translation and a language label
A transcript represents what was said in the source language. A translation expresses its meaning in a target language. A language label identifies an audio region under a stated convention. These layers can appear in one package, but they should not be treated as interchangeable.
A source may support recognition without supporting translation, or support file-level identification without precise language boundaries. Define which references the task requires. If the product generates target speech, it needs additional pairing and voice considerations beyond a speech-to-text translation benchmark. Do not infer those modalities from a multilingual title.
Public research evidence and buyer categories
CoVoST’s original repository documents a major speech-to-text translation resource. Google’s FLEURS card describes a 102-language speech benchmark. These are concrete research applications from model developers, not evidence that their authors are currently buying any particular Fiund source.
Potential users include multilingual speech systems, translation products and pipelines that choose processing based on detected language. Their evaluation questions differ. A language router may need a reliable unknown state; a translator needs meaning-preserving targets; a live product may also need incremental output. Keep the sourcing brief tied to the actual task.
Benchmark comparison with direction-level interpretation
CoVoST 2 reports 2,880 speech hours with 21 languages into English and English into 15 languages. Those directions are not a claim of equal volume in every pair. The same source speech can support several translated targets, so translation-pair totals should not be confused with independent original audio hours.
VoxPopuli and Multilingual LibriSpeech provide other multilingual source designs, with different speech styles and annotation layers. A parliamentary or read-audiobook source is not automatically representative of spontaneous customer conversation. Compare the actual source and current terms rather than only the headline scale.
Language coverage is not balanced translation coverage
A collection can contain many languages while offering little material in one required direction. List the source language, target language, accepted source duration and reviewed target count separately. A reverse direction should not be assumed available merely because one direction exists.
Also distinguish spoken variety, script and locale metadata from the language target. Preserve the evidence supporting those labels and leave unknown values explicit. A broad country label does not establish one uniform speech variety, and a file-level language field can hide mixed-language regions that affect both identification and translation.
Speech-to-text and speech-to-speech targets
A speech-to-text translation package can include source audio, source transcript and target text. Speech-to-speech work may additionally require target recordings and the relationship between source content, target expression and permitted voice use. These are different deliverables and can have different source restrictions.
If target speech is synthetic or dubbed, label that source class. It may be useful when authorized, but it is not an independent natural conversation. Preserve original and derived relationships rather than counting every translated output as new source audio. The manifest should make the construction clear enough for later evaluation.
Build a per-direction acceptance table
Use a coverage plan that states which units are required and what evidence qualifies each one. Keep optional expansion directions outside the minimum accepted set.
Translation quality needs more than fluent wording
A target can read fluently while changing a number, omitting a qualification or assigning a statement to the wrong person. Define a review policy for meaning-critical content, including names, negation, units and uncertainty. Keep literal recognition errors separate from translation decisions where both layers exist.
Multiple reasonable translations can preserve the same meaning. A benchmark should document whether it uses one reference, several references or qualified review of acceptable alternatives. Do not rewrite ambiguous source speech into a confident target simply to produce a complete row. An unresolved or excluded region can be more honest than invented precision.
Language identification needs an unknown policy
A very short utterance, a name, background speech or a switch can be difficult to assign to one language. Decide whether the task supports multiple labels, a span-level sequence or an unknown state. File-level labels alone may be insufficient for a system that changes processing mid-conversation.
Preserve the label method and review evidence. Do not infer sensitive personal identity from language classification, and do not present a recognized language as proof of nationality or background. The data target concerns the observed audio under a stated convention, not a broad claim about the person speaking.
Source timing and parallel relationships
Target text can correspond to a full utterance without sharing word-by-word timing. A translation can reorder content naturally, so time alignment needs a deliberate definition. State whether references locate source sentences, semantic units or another segment type.
Keep source edits and target revisions connected. If an advertisement or uncertain passage is removed, update the paired target and any offsets. A file rename does not establish parallelism. Review at least one relationship from source recording through transcript, target and prepared version so the buyer can see what the package actually supports.
A delivery schema for multilingual tasks
Stable identifiers should connect the source audio with the appropriate labels and targets without duplicating private metadata across every export.
Evaluation should match the operating condition
An offline translator that hears a complete recording has different context from a streaming system. Define when outputs are produced, what revisions are allowed and how latency is measured if it is in scope. Do not compare results without stating those conditions.
For identification, report the amount of evidence and confusion among required classes, including unknown or mixed cases. For translation, preserve per-direction results and the review/scoring method. A single aggregate can be dominated by the largest direction. Use weighting that reflects the evaluation question rather than choosing it after seeing which view looks best.
Provider models and source permissions
A research maintainer offers a fixed corpus under its actual conditions. A multilingual collection provider can recruit to a brief, while a language-service provider can translate material the buyer is authorized to process. A source archive owner can grant only the scope it controls. These roles should remain separate in the proposal.
CoVoST’s repository distinguishes its data, additional Tatoeba material and other resources in its license table. That is a concrete reason to review source components rather than applying a single code badge to everything. A language catalog or translation subscription is not automatically a transferable audio dataset license.
Pricing and a hypothetical direction-level pilot
No defensible public average for a fully licensed, reviewed speech-translation and identification collection was established here. A quote can depend on source access, direction coverage, qualified review, alignment, allowed use and preparation. A conversational-speech list rate does not automatically include translation targets.
For a planning-only pilot with three directions and four accepted source hours per direction, invented placeholders might allocate USD 1,200 for source access, USD 1,800 for target preparation, USD 1,200 for independent review and USD 600 for packaging: USD 4,800. These are assumptions, not supplier prices or a Fiund quote. Shared source audio should still be counted separately from direction-hours.
Pilot acceptance and split design
Inspect a typical utterance, a name or number, a qualification or negation, a mixed-language region and an uncertain source segment. Review source and target together with qualified reviewers where the task requires it. For identification, include an example that should remain unknown rather than forcing a label.
Keep related sessions, speakers and repeated source text together according to the experiment. A translation of a training source is not an independent held-out example merely because it is in another language. Document missing relationships and preserve partition versions. A sample review should report actual inspected coverage rather than claim a complete archive audit.
Reference independence and critical meaning
If target text begins as a machine translation, record how it was reviewed. Fluent automatic wording is not an independent standard simply because it was generated by a different system from the one being evaluated. Qualified review should examine the source meaning, not only whether the target reads naturally.
Preserve disagreements about names, numbers, negation and scope because those details can change the answer even when an aggregate text-similarity score looks favorable. A language-identification label has another uncertainty pattern and should keep its own review status. Do not let one completed column imply that every reference layer was independently validated. A small pilot can reveal which decisions need additional examples or a narrower specification before preparing a larger collection.
Discuss a multilingual task brief with Fiund
Email jaeden@fiund.com with directions, source styles, languages, recording conditions and required target layers. State whether the project needs transcripts, translations, language regions or target speech, and whether evaluation is offline or incremental. Include uncertainty and acceptance policies if available.
Fiund can discuss candidate source fit and a bounded pilot. Availability, permissions, preparation, pricing and delivery are confirmed for selected material. No largest publicly priced category-specific transaction was verified here; model funding, company acquisitions and general language-service contracts are not equivalent to a corpus sale.
Questions buyers ask
Sources & research notes
Public documentation reviewed 2026-11-12. Provider descriptions and published terms are attributed below. This guide does not report hands-on dataset testing or confirm a current Fiund collection.
- OpenSLR Multilingual LibriSpeechwww.openslr.org · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
- Google FLEURS official dataset cardhuggingface.co · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
- Meta VoxPopuli official repositorygithub.com · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
- CoVoST original Meta repositorygithub.com · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.