Your reading path
Start with the right questions.
From principle to practice
Public list prices with their actual unit
Open the worked exampleProsody is more specific than an emotion label
Prosody includes timing, emphasis, rhythm and pitch-related variation. An emotion label can describe how a passage is perceived or how an actor was instructed, but it does not specify every acoustic behavior. Two recordings labeled happy can differ in pace, loudness, pauses and emphasis.
Define the control the model needs to learn. A narration system may need phrase emphasis and paragraph continuity; a conversational system may need acknowledgments and questions. Do not assume one broad expressive label supplies every target. Preserve observable source properties and distinguish instructions from reviewer judgments.
Text-to-speech and voice conversion are different tasks
TTS generates speech from text, while voice conversion transforms an existing speech signal toward another voice representation. Some source material can support both, but the pairings, evaluation and permission scope can differ. This page focuses on text-conditioned expressive generation rather than duplicating an identity-conversion guide.
If a project also needs speaker adaptation or identity-specific output, state that explicitly. A style instruction such as whisper is not itself authorization to imitate a person. Keep voice identity, linguistic content and expressive control separate in the source and commercial specification.
Public benchmark families and their limits
LibriTTS provides approximately 585 hours of read English at 24 kHz, with text layers designed for TTS research. Its restored version changes sound quality rather than creating independent original sessions. These are useful references, but read speech is not automatically a broad expressive-dialogue corpus.
Expresso’s original project contains four studio speakers with read and improvised expressive material. Its dataset documentation specifies noncommercial terms. The Emotional Speech Dataset repository also states research-only use despite a repository code-license badge. Check the actual data conditions before considering commercial work.
RAVDESS: a concrete comparison with a commercial route
RAVDESS’s original release contains 7,356 files across audio and visual representations from 24 actors. Those are not 7,356 independent utterances. The controlled statements and acted expressions make it a particular research design, not a substitute for arbitrary long-form spontaneous speech.
The owner links a separate commercial license. A commercial dataset route does not imply that all synthesis, identity or redistribution uses are automatically covered. Review the current written scope for the intended project. The comparison is useful precisely because corpus access, content design and commercial permission remain distinct questions.
Public list prices with their actual unit
As checked November 12, 2026, the RAVDESS owner’s fee page lists the following two-year commercial options in Canadian dollars. These are dataset-specific posted fees, not a market average, completed transaction or Fiund quote.
- Business category
- Regular two-year license
- Full set
- CAD 9,000
- Audio-only or video-only
- CAD 8,000
- Business category
- Qualifying start-up two-year license
- Full set
- CAD 7,000
- Audio-only or video-only
- CAD 6,000
What buyers can learn from a voice partnership
ElevenLabs and Hasbro’s announcement describes authorized character voices built with new recordings, archives and talent involvement. Its financial terms are undisclosed. It is evidence of a licensed voice-use workflow, not a disclosed bulk training-corpus purchase or an hourly dataset rate.
Potential buyers of expressive source material include speech-generation developers, narration systems and interactive voice products. Their needs can differ from those of a marketplace customer licensing an already built voice. Do not conflate access to a generation service with ownership of, or permission to redistribute, its training recordings.
Design a style inventory around the application
Choose styles that are meaningful to the product, then describe how they are elicited or selected. A fixed script read in several styles offers one kind of control; improvised conversation offers another. Preserve that source class and any instructions rather than presenting all expression as naturally occurring.
Balance useful variation with enough repeated structure to interpret it. If style and speaker are perfectly linked, a model can learn voice identity instead of a transferable style. If every expressive example uses a different topic, content can become another confounder. Record the design so the evaluation can test the intended control.
A TTS source schema worth requesting
Keep literal text, normalized text and acoustic source relationships together without collapsing them into one field. The schema should identify which expressive information was instructed, observed or reviewed.
- Field group
- Identity
- Suggested content
- utterance_id, speaker group, session_id
- Purpose
- Preserves original source relationships
- Field group
- Text
- Suggested content
- spoken text, normalized text, uncertain spans
- Purpose
- Keeps the linguistic target traceable
- Field group
- Style
- Suggested content
- instruction, perceived label, review status
- Purpose
- Separates intended performance from observed expression
- Field group
- Audio
- Suggested content
- original format, capture setup, prepared version
- Purpose
- Makes processing and source quality visible
- Field group
- Timing
- Suggested content
- utterance boundaries, optional word/phrase events
- Purpose
- Supports the required control granularity
- Field group
- Scope
- Suggested content
- voice/use authorization record reference
- Purpose
- Links the proposed model use to source review
- Field group
- Partition
- Suggested content
- speaker, session, text-family groups
- Purpose
- Supports deliberate held-out tests
Recording conditions and processing
Consistent recording can help isolate expressive variation, but excessive processing can remove or alter quiet breaths, effort and emphasis. Decide what noise, clipping or enhancement is acceptable for the intended model. Retain source properties separately from delivered format.
An upsampled file does not create additional original acoustic information. A restored version is a derivative rather than another independent performance. If both originals and processed variants are supplied, connect them in the manifest and keep them together in evaluation grouping. Describe any synthetic or repaired regions instead of calling them all original speech.
Text and acoustic alignment
A fluent transcript can differ from the performance if it removes repetitions or repairs wording. TTS preparation needs a defined relation between text and audio. Decide how nonverbal sounds, false starts and partial words are represented, and preserve uncertain regions rather than inventing a clean target.
If phrase or word timing is required, state the method and review convention. A forced alignment output is not automatically an independently checked reference. Inspect expressive passages where stretching, laughter or whispering can make ordinary alignment assumptions less reliable. Keep text correction and boundary review as separate status fields.
Evaluation should separate content, quality and control
Assess whether generated speech preserves the requested words, remains intelligible and follows the intended style. A natural-sounding output can still miss a name or number. A recognizable voice can still fail the expressive instruction. Keep those criteria distinguishable rather than relying on one overall preference score.
If listening evaluation is used, document the prompts, source comparisons and reviewer procedure. Avoid claiming actual listening or validated performance from file checks alone. The dataset proposal should describe how a representative sample can test the specification, not guarantee a future model’s quality.
Source and voice permissions
Corpus access, recording rights and identity-specific uses can be governed differently. Review the selected source and proposed model behavior, including synthesis, adaptation, downstream access and any restrictions. A publicly downloadable recording or a code license is not a substitute for that review.
Use collection-specific documentation rather than a blanket website claim. If a style or speaker is outside scope, preserve the exclusion. A sourcing discussion should not promise every named voice or character. Begin with a high-level brief and agree appropriate handling before transferring private session files or participant documents.
Pricing a custom expressive collection
No defensible universal market average for custom expressive TTS data was established here. Price can depend on recruitment, voice authorization, script design, performance variation, recording setup, transcript preparation and independent acceptance. A posted research-corpus fee does not price a newly commissioned voice project.
For a hypothetical ten-hour pilot, invented placeholders might allocate USD 2,000 to scoped recording/source rights, USD 1,200 to recording and preparation, USD 900 to text/style review and USD 900 to independent acceptance: USD 5,000 total. These assumptions illustrate budget components; they are not supplier rates or a Fiund offer.
Pilot acceptance and split design
Inspect a typical reading, a sustained expressive passage, a difficult name or number, a quiet style and a transition between delivery styles. Verify the source/text relationship and whether style labels represent instructions or reviewed perception. Include ambiguous examples so the policy can be applied consistently.
Keep related recordings, restored versions and repeated texts grouped according to the experiment. A speaker-held-out test answers a different question from a new-text test on familiar voices. Document the chosen design and any missing source relationships. No collection should be called universally independent merely because files were randomly assigned.
Long-form continuity and style transitions
A set of isolated expressive sentences does not necessarily show how a voice maintains style across a paragraph or changes it at a discourse boundary. If the application generates longer narration, include source units that preserve that context and identify how they relate to shorter segments.
Check whether a requested style can be distinguished from loudness normalization or a recording-session change. A model may otherwise learn a capture artifact instead of the intended expressive control. Preserve source sessions and style instructions so a held-out comparison can test that distinction. In a pilot, review a sustained passage and a transition rather than only the most dramatic clips. Record what reviewers actually heard and how uncertain judgments were handled; a label inventory alone is not evidence of consistent perceptual control.
Discuss an expressive-speech brief with Fiund
Email hello@fiund.com with languages, voice structure, text domain, style controls, recording expectations and intended use. State whether the project needs existing archives or commissioned performances, and which reference and authorization evidence is required.
Fiund can discuss candidate source fit and a bounded pilot. Availability, permissions, preparation, pricing and delivery are confirmed for selected material. This research did not establish a largest publicly priced expressive-TTS dataset sale; licensed voice partnerships and aggregate creator earnings are different economic measures.
Questions buyers ask
Sources & research notes
Public documentation reviewed 2026-11-12. Provider descriptions and published terms are attributed below. Published facts are attributed to their sources. Worked files are labeled as illustrative or as an inspected editorial source; neither implies commercial dataset clearance.
- OpenSLR LibriTTSwww.openslr.org · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
- OpenSLR LibriTTS-Rwww.openslr.org · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
- ElevenLabs Hasbro voice partnershipelevenlabs.io · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
- Expresso original projectspeechbot.github.io · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
- RAVDESS original releasezenodo.org · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
- RAVDESS owner commercial pricingaffectivedatascience.com · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
- Emotional Speech Dataset original repositorygithub.com · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
- Expresso original dataset license documentationgithub.com · Reviewed 2026-11-12
Primary source reviewed November 12, 2026; check the current release and project-specific terms.
