On this page
Updated November 15, 2026
I would start with one coherent part of your audio archive. Describe the recordings and the AI use, establish the permissions, and count the material that fits. Then compare the offer, agree who prepares the copy, let the buyer run a permitted sample review, and put delivery, acceptance and payment in writing.
At Rightmark, the initial audio appraisal starts with hours, languages and what your consent covers. It needs no files or system access. That is a useful first step before spending money transcribing a whole archive or promising a music catalog whose rights have not been checked.
This guide covers existing calls, multilingual speech, podcasts, music, stems and sound effects. A recording licensed for speech recognition, a particular person's synthetic voice and music for a generative model are different products. The same file can serve several purposes only when the permissions and technical specification support each use.
You keep ownership when you license material; the grant determines what others may do with it. The practical goal is a package a buyer can evaluate, with proceeds and obligations you understand. A large raw-hour count alone cannot tell you either.
See the audio licensing process from description to payment
- Define the package and its intended use.
- Reconcile the quantity and compare the price basis.
- Establish who can permit each use.
- Choose the route and calculate owner proceeds.
- Prepare a controlled, useful copy.
- Agree and evaluate a representative sample.
- Confirm the license and payment event.
- Deliver, reconcile acceptance and track cash.
- Owner inventory and intended AI use
- Recording type
- Recording type
- Speech and voice: speakers, channels, transcripts
- Music: recordings, compositions, versions
- Sound effects: events, context, embedded material
- Speech and voice: speakers, channels, transcripts
- Rights review and scoped offer
- Music: recordings, compositions, versions
- Rights review and scoped offer
- Sound effects: events, context, embedded material
- Rights review and scoped offer
- Rights review and scoped offer
- Unresolved authority or no fit: Hold, exclude, narrow or decline
- Permission and work order for preparation
- Hold, exclude, narrow or decline
- Permission and work order for preparation
- Owner-approved sample and permitted buyer tests
- Owner-approved sample and permitted buyer tests
- Bounded correction or changed scope: Permission and work order for preparation
- No acceptable path: Hold, exclude, narrow or decline
- Proceed: Agreed license and identified delivery
- Agreed license and identified delivery
- Receipt and integrity checks
- Receipt and integrity checks
- Acceptance and final quantity
- Acceptance and final quantity
- Invoice and agreed due event
- Invoice and agreed due event
- Cash reconciliation and ongoing rights register
- Cash reconciliation and ongoing rights register
Text version: Start with one inventory, then follow the speech, music or sound-effects branch. Rejoin at the rights review and offer. Resolve missing authority before access. Agree the preparation and sample permission, then evaluate. A failed sample returns to a bounded correction, a changed scope or a decision to stop. A successful sample supports negotiation. The agreed license identifies the delivery; receipt, acceptance, invoice and cash remain separate events. Track obligations after payment too.
These are decisions, not a requirement to sign a separate document at every step. One agreement may cover several functions. Read the grant before signing and confirm that it supplies the permission needed for the next action.
| Handoff artifact | Owner and rights lead | Audio preparer | Intermediary, if used | Buyer |
|---|---|---|---|---|
| Non-sensitive description | Defines asset, use and known gaps | States available formats | Checks possible route | States the task |
| Inventory and rights summary | Links assets to authority | Measures agreed units | Coordinates open questions | Identifies useful scope |
| Work order and cost base | Approves access and release | Names tools, outputs and work | States included services and fees | Confirms funded work |
| Sample cover sheet | Approves recipient and use | Supplies identified sample | Coordinates review | Returns agreed test evidence |
| Offer and license schedule | Decides rights and proceeds | Confirms deliverability | Reconciles the proposal | Approves scope and cost |
| Manifest and cash record | Reconciles rights and receipts | Identifies delivered version | Performs agreed administration | Records receipt, acceptance and payment |
Name actual people in your private copy. A party funding preparation is not necessarily the person doing it.
1. Separate your recordings into packages a buyer can use
Match the recording to the model's task
Start with what the buyer needs to learn or test. For speech recognition, that might be conversations in a particular dialect, recorded on the devices its users carry. A model handling interrupted support calls has a different need from one producing a studio narrator's voice.
Microsoft's custom speech guidance, updated December 19, 2025, recommends matching training material to the relevant speech variations, acoustic environments and recording hardware. That is a useful task-matching principle; its program's file and quantity requirements are not universal buyer specifications.
Write the task before deciding that noise, overlapping speech or a particular recording format is unacceptable. Background sound may be part of the intended conditions. A missing speaker channel, unintelligible passage or badly clipped signal can remove information the buyer needs. Have the buyer identify which distinction matters.
| Package and task | Buyer question | Countable asset | Evidence and public scope example | Hold or mismatch to resolve |
|---|---|---|---|---|
| Speech recognition and conversation understanding | Which language, domain and recording conditions match the task? | Identified recordings with an agreed hour definition | Actual channels, transcripts and speaker labels; SE-A calls list recognition, understanding and evaluation | Its call route excludes cloning, synthesis and identification; unresolved notice, consent or confidential content needs review |
| Meeting and project-call summarization | Do the audio and summaries cover useful conversations? | Identified calls and their linked transcripts or summaries | AV-CALLS-CLIENT describes studio-client calls with transcripts, summaries and separate tracks or labels | Its recording rights and permission route are unresolved. Check the actual channels; mono fails a separated-speaker requirement, not every task |
| A named synthetic voice | Which person's voice may be generated, and for what use? | Authorized voice material and the separately defined voice use | Speaker-specific permission, permitted outputs and restrictions | A recording or speech-recognition grant does not establish permission to synthesize that person's voice |
| Music generation, analysis or source separation | Which recordings, underlying works and versions are needed? | Distinct recordings, compositions and included stems or versions | AV-OPTIN uses composer agreements; check recording/composition authority, contributors, samples and actual mix/stem relationships | Hold tracks without the required active agreements; check earlier buyer overlap. Do not promise original stems that do not exist |
| Sound-event recognition, effects and ambience | Which events or acoustic conditions must be covered? | Distinct clips and duration, with repeat takes identified | AV-FIELD-SFX separates existing location recordings from new capture to a brief | Confirm ownership before samples; agree event coverage, production and delivery for commissioned work; resolve embedded speech or music |
This is a specification aid. It does not define acceptance tiers. A music mix, an instrumental version and the component stems can be useful together, but each should be described accurately. A sound-effect recording may contain no musical composition at all; check what is actually in it.
Check the representation being offered too. AV-CALLS proposes de-identified transcripts with voices removed, rather than its recordings; rights and permission questions remain. By contrast, the published panel-podcast lot describes material for multi-speaker conversation models, with each speaker's written permission still to confirm. Publication history and channel layout are task questions, not blanket rejection rules.
Describe one coherent slice before asking for a catalog price
Group material by recording source, period, language or sound category, format, permission status and annotation coverage. Use controlled package and speaker IDs. Keep the private identity lookup and agreements in a restricted location, outside the first description.
Inventory originals and derivatives separately. Repeated exports, compressed copies, remixes, stems and alternate edits can inflate a folder count. Keep relationships between them so a buyer can understand whether it is receiving new material or another representation of the same recording.
We will follow Harbor Support's call archive, an example; the company and the people are invented. All quantities, findings, rates and outcomes in this continuing example are assumptions. Harbor has 1,000 recorded hours across several languages, repeated exports, permission gaps and incomplete transcripts. Its first task is to identify a useful, permissioned slice for a speech-recognition buyer.
An initial message could read:
We have an archive of multilingual support calls, with approximately 1,000 elapsed recording hours before deduplication and exclusions. Formats and channels vary; transcripts cover part of the archive. Some client and speaker permissions need review. We can start with one language and collection period. Which intended use, count basis and evidence should we scope first?
This is an invented inquiry template, not a customer quotation. It contains enough to begin a conversation without attaching recordings, real transcript excerpts or customer identifiers.
Rightmark's audio qualification work reviewed on November 15 asks for hours by language, format, bitrate, channel separation, metadata, transcripts and permission evidence. Those questions help define a package. They do not establish a minimum size, a ranking of valuable languages or an offer to buy every qualifying archive.
Treat a catalog headline as the start of diligence
The current public music lot, checked November 15, illustrates why the detail matters. It describes about 200,000 tracks with owner-stated AI clearances, WAV or FLAC files, DDEX metadata and release covers. The detailed card says the offering party is the licensor rather than the track owner. The number cleared for both recording and composition is unstated; some tracks may already have AI licenses, and no stems are included.
That is a described licensing opportunity, not independently audited deliverable quantity or a completed sale. Before pricing it, establish which tracks the licensor can actually include for the requested use. The same exercise applies to a small independent catalog.
Keep a private inventory row for each package: controlled ID, category, intended use, raw quantity and unit, uniqueness basis, source period, languages or genres, encoding/channels, available labels, rights references, exclusions and responsible role. The inventory and rights companion provides blanks and filled fictional examples.
2. Count the licensable package before comparing prices
Make the denominator visible
An hour may measure elapsed recording time, speech-only time or summed speaker/channel time. These are different quantities.
Invented clock illustration: a 100-minute call stored as two full-length speaker channels contains 100 elapsed minutes and 200 channel-minutes. Suppose speech occupies 70 minutes on one channel and 50 on the other, with 30 minutes of simultaneous speech. The sum is 120 speaker-minutes, but speech occurs somewhere in the call for 70 + 50 - 30 = 90 elapsed minutes. None of those counts automatically determines the bill.
Agree how silence, hold music, overlapping speech, duplicate exports, partial clips and minimum clip lengths affect the payable unit. Two channels do not automatically double the licensed hours. The existing guide to how an audio hour becomes comparable develops that distinction for speech datasets.
Keep four totals: recorded material; unique material with permission for the proposed use; the buyer-selected package; and delivered material accepted under the written count rule. A rights gap cannot be cured by pricing its hours lower.
Follow the inventory through exclusions
For invented Harbor, assume the exclusions below do not overlap. Each deduction applies only to material still remaining. The unit throughout is elapsed file hours, with no multiplication for channels.
| Inventory step | Change | Remaining hours | Decision |
|---|---|---|---|
| Recorded archive | Starting quantity | 1,000 | Raw description only |
| Repeated exports | Remove 100 | 900 | Keep one identified version |
| Additional recordings with unresolved permission | Hold 200 | 700 | Do not offer these |
| Additional material outside requested language/task | Exclude 150 | 550 | Keep outside this package |
| Additional material failing the agreed technical specification | Hold 50 | 500 | Investigate separately |
| Proposed package | No further change | 500 | Ready for scoped review, not yet accepted |
| Later hypothetical acceptance | 50 hours not accepted | 450 | Use the signed reconciliation rule |
Harbor's 500 proposed hours are half its original total, but that is arithmetic from invented exclusions, not an industry yield benchmark. If two flags apply to the same recording, deduct it once and retain both reasons. If the buyer changes to speech-only hours, recalculate rather than copying the elapsed-hour total into the new unit.
For music, retain distinct recording count, composition count, duration and version count. Ten stems and one mix are not eleven independently composed songs. Record how many included tracks have the required rights evidence, not just how many files are available.
Use price references for the product they describe
The Q4 2026 Rightmark Price Index, published and updated October 26, records a Medium-confidence historical ask of $6.30 to $7 per hour. The August 3, 2025 archive of FileMarket's Datarade listing shows a claimed million-hour multilingual catalog at $7 per hour, with a 10% marketplace discount to $6.30. Those figures are an asking price and channel discount, not paid-price dispersion, today's floor or owner proceeds. August 3 is the archive date, not a claimed publication date. Do not multiply your whole archive by that reference.
A public catalog price can orient a discussion, provided you keep the product and payer visible.
| Reference | Amount and unit | Evidence date and scope | What it cannot establish |
|---|---|---|---|
| SpeechData.ai buying guide | $60 to $95 per hour for its ready-made catalog | Published June 18, updated October 17, 2026; supplier's published buyer price | A raw archive owner's payout, a completed transaction or a universal AI-lab tariff |
| Rightmark's music lot | Price after catalog and rights review | Public non-exclusive opportunity checked November 15, 2026 | A per-track tariff or an accepted cleared quantity |
| Your actual offer | Amount and denominator to obtain in writing | Named package, use, services and offer expiry | Future repeat sales beyond the agreement |
Confirm the quote's hour definition, annotations and license scope; your package may require different preparation and rights.
The Rightmark Price Index is organized by unit, source and confidence. Preserve those fields when using it. An asking price, paid transaction, appraisal estimate, subscription and revenue share are different evidence types. Confidence describes the evidence behind a figure; it does not express the probability that your package will sell.
For a comparison card, write down currency and tax treatment, source and date, quantity, denominator, minimum commitment, permitted use, term, exclusivity, included work and the price's expiry. Leave unknown fields open. Averaging prices for different objects will not produce an appraisal.
A performer-specific voice library uses another model. ElevenLabs' February 13, 2024 launch announcement describes rewards when paid subscribers use an approved professional voice clone. That is a usage model, rather than a payment for each hour of recordings supplied. Check a platform's current terms before selecting that route.
Compare the actual scope behind several lot asks
These public listings were read on November 15, 2026. Quantities are owner-reported; the asking terms are Low-confidence indicative estimates, not offers or completed transactions. A listing does not establish cleared delivery. The holds below are part of the comparison.
| Public lot | Asking basis | Scope and conditions to resolve |
|---|---|---|
| SE-A calls | $5.70 to $7 per delivered call hour for one non-exclusive license of 12 to 24 months; calls can be licensed separately | Up to 15,900 hours by the owner's count, potentially lower after measurement. Recognition, understanding and evaluation only; no cloning, synthesis or speaker identification. Review recording notice, consent and confidential content. Screen-share is excluded; EU, UK and Canada participants remain held until counsel sets the route |
| AV-CALLS-CLIENT | $1,800 to $2,000 per non-exclusive license for about 350 hours and 597 calls | Recording ownership is unresolved and identifiable speakers lack AI-training consent. Resolve permission and privacy treatment before a sample. Standalone licensing also needs the owner's agreement on economics. De-identification wording does not establish anonymous voices or licensing authority |
| AV-OPTIN | On request: revenue share after buyer review; no public percentage | About 20,000 songs covered by earlier non-exclusive AI licenses. Only tracks with a composer AI addendum and an active main agreement enter delivery; check whether the buyer already has them. Composition/master scope, owner buyer approval and composer notice remain part of this route |
| AV-FIELD-SFX | On request: priced per hour and for new recordings to a brief; non-exclusive | About 50 existing hours are separate from commissioned recording. Confirm ownership before samples. Define the event coverage, production work and delivery before pricing new capture |
SE-A prices delivered hours within a term. The studio-call row is a package ask with unresolved standalone economics; dividing it by 350 would hide those conditions. The music row needs a defined revenue-share base and reporting terms. The field-effects row needs separate scope for existing files and newly produced material. The earlier music-clearance lot has another unresolved input: its headline track count does not establish the both-rights-cleared quantity.
Do not average these rows into a tariff. Compare the actual unit, selected quantity, use, term, preparation and permission state. A missing permission is a reason to hold material, not a reason to discount it into eligibility.
Move from a reference to a quote for your package
The data valuation guide explains the method behind an indicative range and a reviewed quote. For audio, start with the unit and eligible quantity, then select a dated reference with comparable scope. Prepare a non-sensitive description for appraisal. Resolve permission, agree an NDA and the permitted sample tests, and ask for a quote on the buyer-selected package. Put the accepted-unit rule, fees, preparation responsibilities and payment conditions into the signed license.
Keep the state visible: a historical ask informs a comparison; an appraisal is indicative; a quote states proposed commercial terms; a signed license supplies the agreed terms. Later acceptance determines the payable quantity under that agreement, and a remittance establishes cash received. A quote or signature is not proof of those later events.
Improve the part that changes the buyer's decision
I would ask what evidence or improvement changes this particular offer before commissioning a large processing job. Language fit, collection context, relevant speaker coverage, intelligibility, useful channels, requested labels and documented rights can each affect usefulness. Scarcity alone is insufficient: a buyer needs the scarce material for a task.
| Weak point | First useful action | When to hold spending |
|---|---|---|
| Permission is missing | Resolve the scope or exclude affected material | Until authority exists |
| Quantity is unreliable | Reconcile duplicates and the hour rule | Before quoting the full archive |
| Transcript accuracy is unknown | Agree a small checked sample and error categories | Before bulk transcription |
| Buyer needs stems that do not exist | State what versions are available | Before promising machine separation as original stems |
| Buyer asks for costly new collection | Obtain a concrete specification and cost allocation | While demand and payment remain speculative |
Separate invented offer comparison: 500 accepted hours at an assumed $40 produces $20,000; 300 accepted hours at an assumed $55 produces $16,500. The higher hourly figure yields less total license consideration. Align use, term, services and certainty before choosing between them. These are arithmetic assumptions, not market rates or Harbor's final acceptance.
Separate invented improvement decision: an owner-funded preparation task costs $3,000 and adds an assumed $2,000 to owner proceeds. Its incremental result is negative $1,000 before time and tax. Buyer-funded preparation changes that calculation. Use additional owner proceeds minus owner-borne cost and any explicitly estimated opportunity cost, rather than treating the buyer's entire bill as your gain.
A low offer may reflect a small eligible package, unsuitable conditions, costly annotation or available substitutes. Ask for the reason and propose a narrower grant or better evidence. Hold or decline if deductions are unexplained, the requested rights are unacceptable or the work cannot be justified.
3. Establish who can permit each audio use
Connect each recording to the relevant authority
For calls, separate control of the recording from authority to license its contents. Check the client or BPO agreement, staff contributions, customer notice and any speaker permission against the intended AI use. Rightmark's call-recording process asks for AI-training scope and client sign-off where needed. A general quality-assurance recording notice is a question to investigate, not evidence of every onward use.
For podcasts and radio, inspect the host and guest releases, production and distribution agreements, commissioned segments, advertisements, music and stings. An episode may contain several separately controlled contributions. Choose cleared segments or obtain missing scope; a right to publish a show does not itself settle a right to imitate its guest.
The US Copyright Office's Circular 56A, revised March 2021, treats a musical composition and its sound recording as separate copyrighted works. Rights in one do not substitute for rights in the other. That distinction identifies two questions to resolve; registration by itself does not supply an AI-training grant.
For a music package, map master recording and composition/lyrics authority, co-writers and shares, performer or session agreements, samples and existing grants. A publisher, label, distributor or licensor may control only part. Rightmark's music and sound guidance asks for both composition and master rights, plus relevant session and sample rights, for included music.
For sound effects, check the recording's provenance and the authority to license that recording as data. A library license allowing an effect in a film does not establish authority to sublicense the library itself. Resolve audible speech or music where present, without imposing a composition requirement on a simple nonmusical sound.
Keep evaluation, training and voice synthesis on separate lines
Use a permission matrix with a decision for every activity:
| Activity | Scope to settle before it happens |
|---|---|
| Describe the package | Approved non-sensitive description and recipients |
| Share a sample | Exact sample, reviewer, access route and retention |
| Evaluate with a model | Named test, tool, operator and permitted outputs |
| Train or fine-tune | Data version, intended models/use and recipient scope |
| Create a named synthetic voice | Person's specific permitted identity/voice uses and restrictions |
| Generate music or other audio | Output uses, attribution and restrictions to resolve |
| Sublicense or create derived datasets | Allowed recipients and onward rights |
| Run a public demo | Express scope for public disclosure and output |
Confidentiality and use permission do different jobs. An NDA can protect disclosed material while leaving training, hosted processing or public demonstration outside the grant.
Microsoft's custom-voice documentation, updated September 23, 2026, requires a recorded talent consent statement before its professional voice fine-tuning. This is a concrete program-specific example of separating synthetic-voice permission from possession of recordings; it is neither a universal legal rule nor a Rightmark voice product.
For an identifiable voice, have the appropriate rights and privacy lead resolve the actual purpose, recipients, territory, term, prohibited uses and withdrawal or post-term treatment. Explain the intended use plainly to the person whose permission is needed. Removing their name from a transcript does not create a voice-cloning grant.
Ditto's AI music licensing program, dated August 25, 2026, distinguishes opting in from actual selection. It also explains that opting out does not reverse training already performed. Its page gives no payout percentage. For any program, establish what withdrawal changes about future supply, existing copies and earlier grants.
Build a rights-complete music package
Consider Cedar Sound, an example; the company and the people are invented. It has 100 distinct recordings. The following disjoint counts and authority findings are assumed, unrelated to the public music lot above.
| Recording group | Count | Proposed-use evidence | Decision |
|---|---|---|---|
| M001 to M060 | 60 | Recording and composition authority documented for this use | Candidate package, subject to remaining checks |
| M061 to M085 | 25 | Composition authority unresolved | Hold until resolved |
| M086 to M100 | 15 | Earlier exclusive AI grant conflicts with requested use | Exclude from this proposal |
The candidate starts at 60 recordings. List remixes and stems separately where they exist and are covered. If one of those 60 recordings has a sample with unresolved authority, it leaves the candidate set until that issue is settled. The spreadsheet cannot grant a missing right.
Keep agreement reference, version, covered assets and authority decision separate. A field reading “consent: yes” is harder to audit than a controlled reference tied to a collection event and the included files. The audio, transcript and consent provenance guide provides that evidence structure while keeping legal decisions separate.
For every gap, assign an action: obtain the needed permission, narrow the use, omit a track or segment, or hold the package. Record the responsible person and next decision date. Do not assume a new notice retroactively resolves old recordings. A later withdrawal or discovered conflict needs a recorded response under the applicable agreement, including any effect on future supply and previously licensed material.
4. Choose the rights you will license and calculate what you keep
Pick a route that fits the work you can do
A direct buyer can be a good route when you already have a credible buyer, a rights team and delivery capability. An intermediary can coordinate qualification, scope, evidence, negotiation and administration. A music specialist can help where authority is fragmented. A performer seeking to license only their synthetic voice needs a program built for that use.
| Route | Who does the work | Payment basis to examine | Question to resolve |
|---|---|---|---|
| Direct license | Owner and buyer assign preparation and diligence | Package fee, term payment or another negotiated basis | Can we support delivery and enforcement ourselves? |
| Intermediary-coordinated license | Written service scope divides the jobs | License amount plus fee or agreed share | Which deliverables does the fee buy? |
| Catalog or distributor program | Program terms govern submission and selection | Selection-based license or reported revenue share | What is selected, reported and paid? |
| Performer voice platform | Performer and platform follow its voice process | Usage rewards under current terms | Which uses, withdrawal rules and payout conditions apply? |
A catalog listing is an opportunity to be considered. Revenue share depends on actual attributable revenue and its defined base. Ask about deductions, reporting, minimum guarantees or recoupable advances if any, statement access, audit rights and post-term reporting. Do not multiply recording hours by an imagined royalty rate.
Rightmark's current audio pages describe appraisal, title/consent checks, route selection, owner scope approval and agreed transfer. Identify the actual hands-on preparer in the work order. Coordination is a service; it does not establish that every transcription or voice-transformation task is included. The guide to what a licensing broker does helps separate those responsibilities.
Follow Harbor's proposal into a conditional agreement
Invented negotiation: Harbor, the buyer, every amount, finding, duration and condition in this sequence are fictional assumptions. The public lots above do not substantiate this agreement.
| Step | Hypothetical position | What remains conditional |
|---|---|---|
| Owner proposal | Harbor proposes its 500-hour elapsed-time package for $20,000 | Exact use, recipients, preparation, acceptance and payment terms still need agreement |
| Buyer counterproposal | $40 per accepted elapsed hour, after permitted representative-sample evaluation | Asking for a sample is not an agreement to buy 500 hours; the written count and acceptance rule will govern |
| Agreed scope | A 12-month non-exclusive grant for the stated recognition task, with defined recipients and permitted training/evaluation; cloning, synthesis and identification excluded | Retained rights and end-of-term treatment are agreed separately. Preparation and delivery must meet the signed scope |
| Signed money terms | A fixed assumed $1,800 buyer-paid intermediary fee and $2,000 buyer-paid preparation, in addition to accepted-hour consideration | The fixed fee is an invented amount, not an inferred public percentage. Invoice requirements and payment conditions must be satisfied |
| Assumed later outcome | 500 hours delivered, 450 accepted: $18,000 license consideration; $21,800 buyer total before excluded charges | Owner expected receipt is $18,000 before its own obligations. Cash must actually arrive; acceptance alone does not prove payment |
Harbor could counter on use, quantity, term, cost allocation or payment, or decline. In this continuing example the parties resolve those questions before signing. The separated-speaker alternative in section 6 remains a different branch; the settlement above assumes the original 500-hour scope continues. The completed calendar in section 8 shows the distinct signing, acceptance and cash events under further invented timing assumptions.
Price exclusivity as a defined restriction
Write down the recording list, AI use, recipients or affiliates, territory and term. Then reserve any intended continued publishing, streaming, internal use or other licensing. Decide whether future episodes, new releases, lyrics, stems and updates are included. Disclose earlier grants; a buyer cannot receive an exclusivity promise that conflicts with them.
An exclusive offer can be valuable because it pays for alternatives you give up. Compare that extra consideration with credible forgone opportunities and the added obligations. There is no useful universal multiplier.
Invented two-year choice: assume a $30,000 exclusive offer for one defined audio slice versus $20,000 for one non-exclusive license. Both are assumed payable at the same milestone, with the same $2,000 owner-borne transaction cost. The $10,000 difference buys the restriction. A possible second non-exclusive license could add an assumed $12,000 in year two, with an additional $1,000 cost.
| Assumed outcome | Exclusive proceeds after stated cost | Non-exclusive proceeds after stated costs |
|---|---|---|
| No second buyer appears | $28,000 | $18,000 |
| Second license occurs in year two | $28,000 | $29,000, including $11,000 arriving later |
These are scenarios, not forecasts; no probability is assigned. The later $11,000 is uncertain and arrives at a different time. An owner could reasonably prefer the contracted exclusive offer. Another could value retained rights or negotiate a shorter term, narrower use or minimum guarantee. Consider cash timing and restrictions alongside the totals.
Exclusivity, confidentiality and publicity are separate clauses. A non-exclusive dataset can still be confidential, and a confidential agreement need not prevent a second permitted license.
Put the buyer's total and your proceeds on the same sheet
Rightmark's published offer, checked November 15, says standard licenses carry no Rightmark deduction from the owner's payout: the buyer pays its fee on top. Premium and bespoke deals leave 75% to 85% with the owner, agreed in writing before sale. Buyers cover extraction, scrubbing and transfer, with nothing upfront for the owner.
Convert that offer into a defined sharing base and written work scope. The standard buyer-fee percentage is not published. Included preparation, extra work and any exceptions belong in the actual proposal. An owner's separate contributor obligations, taxes or bank charges are not the same as a Rightmark commission.
Invented mechanics, separate from Harbor: all dollar amounts, the $2,000 fee and the selected 80% share below are assumptions. Preparation is assumed separate and buyer-paid. Taxes and contributor payments are excluded. The columns illustrate different fee structures, not equivalent competing service quotes.
| Money line | Standard fee-on-top illustration | Premium share illustration |
|---|---|---|
| License consideration or agreed sharing base | $20,000 owner consideration | $20,000 sharing base |
| Intermediary fee/share | $2,000 additional, paid by buyer | $4,000 inside base |
| Owner proceeds before own obligations | $20,000 | $20,000 × 80% = $16,000 |
| Preparation paid separately by buyer | $2,000 | $2,000 |
| Buyer total | $24,000 | $22,000 |
Do not add the premium intermediary share to the buyer's bill twice. It is already inside the assumed $20,000 base. The retained share is also not necessarily the owner's final take-home amount, and the intermediary's share is not its net profit.
Rightmark's Trust page says a Scout is paid from Rightmark's income, not the owner's. Do not add an assumed second Scout deduction. Reconcile every other charge by payer, recipient, base, deliverable and trigger.
For like-for-like offers, compare owner net, buyer all-in spend and the rights left with the owner. A buyer-paid fee still consumes buyer budget. Ask what the fee covers and whether preparation has a cap, defined outputs and a process for extras.
Use the blank audio offer worksheet to put both sides of the proposed deal on one page before approving preparation.
5. Prepare a controlled copy without removing what makes it useful
Agree the operator, workspace and bill first
Name who extracts, transcribes, annotates, redacts, processes and checks the audio. Specify the approved workspace, tools, outside services, network and export limits, reviewers, retention, outputs and release authority. State the work's cost and payer, including what happens if no license follows.
A controlled workspace restricts access; it does not itself make a voice unidentifiable. Rightmark's Clean Room page describes operational-archive early access and code workflows. For this audio job, ask what environment and preparation are actually being proposed.
Preserve the authorized original and make an identified working copy. Keep input/output IDs, fingerprints, tool and policy versions, exclusions and transformation logs. Store the identity and consent lookup separately. Removing public-facing identifiers should not destroy the evidence needed to explain which permission covers which recording.
| Invented Harbor operation | Operator and boundary | Expected output | Cost and approval |
|---|---|---|---|
| Deduplicate candidate | Owner engineer in approved workspace | Unique-file map, with retained originals identified | Agreed work order |
| Check channels and encoding | Named audio preparer on working copy | Stream report and exceptions | Defined inspection scope |
| Correct included transcripts | Approved annotator, authorized files only | Versioned transcripts tied to audio | Funded task, extras require decision |
| Remove approved sensitive intervals | Authorized preparer | Changed audio/transcript pair and interval log | Owner/rights lead checks sample |
| Release evaluation sample | Responsible owner | Sample manifest and use permission | Release decision recorded |
This is an illustrative assignment, not a statement that Rightmark performs these operations automatically. The preparation and delivery companion provides the full blank work order.
Inspect the source before choosing transformations
Check decoding, duration, sample rate, codec and bit depth, channel count and layout, discontinuities, silence, clipping and alignment. A two-channel file might be stereo or two separated speakers. Confirm which before mixing it down. Use bounded technical observations and listening checks against the intended task.
The audio stream and channel review explains a reproducible inspection method. It distinguishes metadata, decoded observations and decisions. A clean result in an inspected window does not prove every hour is clean or establish rights.
Agree the target encoding, chunk boundaries and transcript format with the buyer. Putting compressed audio into a lossless container cannot reconstruct information already discarded. Resampling, mixing and denoising should have a purpose and a logged result. Removing all overlap or background sound may remove the conditions the buyer wanted to study.
For transcripts, record whether they are machine-generated, human-reviewed or human-produced. Check words against identified audio, timestamp reference, segment boundaries, stable speaker labels and language changes. Diarization means assigning speech segments to speakers; it does not by itself identify who those people are. Agree error categories and a checked sample rather than adopting an unexplained universal accuracy threshold.
For music and effects, verify the actual versions supplied. Check categories, instruments, tempo or key only where promised and supported. Keep stems aligned when they are meant to reconstruct a mix. Label generated or altered material accurately; a machine-separated component is not an original multitrack merely because it has been saved as a separate file.
A manifest should connect package/version, asset ID, source and derivative IDs, file fingerprint, duration, format/layout, transcript/annotation version, rights reference, transformation history and disposition. A missing value remains unknown. Decide whether to keep, transform with approval, relabel, exclude or investigate each finding.
Keep privacy treatment and task utility separate
Text and audio can expose different things. The following operations solve different parts of the job:
| Operation | What to record |
|---|---|
| Content redaction | Exact words, intervals or metadata removed from each representation |
| Pseudonymous identifiers | Replacement IDs and separately restricted lookup, if retained |
| Voice transformation | Acoustic changes and the version produced |
| Identification assessment | Remaining voice/context clues, recipient conditions and residual findings |
None supplies missing licensing permission. A claim that a release is anonymous requires its own assessment; the table is not a legal certification.
Invented Harbor interval: a customer name is spoken from 00:12.0 to 00:12.8. Replacing the transcript text with [SENSITIVE] leaves the name audible. Suppose the approved treatment silences that 0.8-second interval without shortening the file and marks the matching transcript cue. The later timestamps can retain their reference. If the interval is cut instead, regenerate and validate the timeline mapping.
| Invented representation | Change | Check |
|---|---|---|
| Prepared audio A017-v2 | Silence 00:12.0 to 00:12.8 on affected channels | Interval changed; duration preserved |
| Transcript T017-v2 | Replace corresponding cue with [SENSITIVE] | Linked to A017-v2 and same time reference |
| Alternate export | Apply approved treatment or exclude it | No untreated duplicate supplied |
| Metadata | Remove the corresponding identifier where present | Keep controlled rights reference privately |
The remaining voice and conversation can still reveal identity. Text redaction has not changed the speaker's acoustic characteristics elsewhere in the file. EURECOM's VoicePrivacy 2026 evaluation-plan abstract, dated March 21, 2026, describes separate speaker-privacy and linguistic/emotional-utility evaluation. It is a technical benchmark example, not a legal anonymity standard or a Rightmark service.
Test both sides of a proposed transformation: does it reduce the identification risk you are assessing, and does the result still support the permitted task? Record the method, coverage, residual finding and decision for each. An identity-dependent voice use may conflict with concealment. Resolve the use and permission rather than promising recognizable identity and anonymity together.
Run that test on the permitted sample before processing everything. Return the before/after findings, remaining files, exclusions, revised count and known gaps to the owner. A changed count or extra processing task must reach the quote. Excluding a tenth of the files does not necessarily exclude a tenth of the hours.
6. Agree what the buyer may test and what the sample must show
Sample the package you are actually offering
A polished demonstration can show a capability; it does not necessarily represent the archive. State the selection method and the population it covers. Include useful variation in recording conditions, languages, speakers, durations, channels and annotations within the permissioned package. Do not include uncleared material simply to make a sample representative.
For invented Harbor's 500 proposed hours, assume this selection plan. The sample is deliberately stratified, with noisy calls oversampled; these are design assumptions, not measured quality results or a standard sample-size rule.
| Stratum | Proposed elapsed hours | Sample elapsed hours | Purpose |
|---|---|---|---|
| Language A, separated channels, quieter calls | 250 | 2 | Check ordinary channel/transcript handling |
| Language A, mono, noisier calls | 150 | 2 | Expose a likely acoustic weak point |
| Language B, separated channels, mixed conditions | 100 | 1 | Check language and label handling |
| Total | 500 | 5 | Bounded inspection of these selected clips |
No held permission-gap files enter the five hours. Because selection is not proportional or random, do not report an unweighted sample error rate as the whole archive's measured rate. Keep inspected findings and any justified broader inference separate.
For music, use the offered rights-cleared subset and show the actual genre, duration, mix/stem and metadata variation. For sound effects, cover the agreed event classes and recording conditions. A missing class should be visible rather than quietly replaced with another example.
The cover sheet travels with the sample: package/sample IDs, versions, population, selection method, quantity unit, formats, labels, transformations, rights references, allowed recipients and tests, access expiry and exclusions. Keep sensitive identity evidence on its separately agreed review channel.
Put the test permission beside the success criterion
Separate listening, transcript scoring, inference using an existing model, fine-tuning, public demonstration and onward disclosure. Name any hosted service before material is sent to it. Access to files is not blanket authorization for every experiment.
| Evaluation question | Agreed method and evidence | Decision to define |
|---|---|---|
| Do the files meet the format specification? | Decode identified files; record layout, durations and failures | Required format and handling of exceptions |
| Do transcripts and speaker labels match? | Check selected cues against audio; return error categories | Checked coverage, threshold and correction path |
| Does the package cover the task? | Inspect the stated language/context/category strata | Required coverage and known omissions |
| Is the rights chain traceable? | Review controlled references under agreed access | Who decides authority and resolves gaps |
| Is the transformed sample suitable? | Agreed privacy and utility tests | Residual findings and responsible decision |
For each row also record the authorized operator/tool, retained outputs, expiry and response date. This is a way to agree a test, not a claim that every buyer or Rightmark route uses the same threshold.
Turn feedback into a bounded next step
Ask the buyer to identify the sample version, method and affected IDs. “Needs better audio” is difficult to act on. “The second speaker is absent in these files, contrary to the channel specification” identifies a bounded issue.
A rights failure sends the affected material back to hold or exclusion. A format or label defect may justify a funded correction and retest. Missing task coverage may require a different slice and revised quote. No fit can be a reason to decline. Agree the work and payer before undertaking it.
For invented Harbor, suppose the mono stratum is unsuitable for a buyer that now requires separated speakers. That is a scope decision: narrow the package and reprice it, or decline that requirement. Do not relabel mono recordings as separated channels to preserve the count. This is an alternative branch; the later settlement example assumes the original 500-hour scope continues to delivery.
Record each revised sample and its relationship to the offer. A request for more material, another recipient or a new model operation needs scope review. If the opportunity ends, close access and follow the agreed retention and deletion terms. Passing the sample supports a commercial decision; it does not automatically authorize training, accept the full delivery or trigger payment.
7. Put the dataset, permitted use and payment event in writing
Match each document to the authority it supplies
Confidentiality protects disclosed information. An engagement defines an intermediary's or preparer's job and fees. Evaluation permission defines sample access and tests. The dataset license grants the actual rights. These functions can be combined, but they should remain understandable.
For invented Harbor, the conditional counterproposal becomes operative only through the signed license with its defined package, permitted use and acceptance rule. Its 12-month term does not by itself decide what happens to retained copies or previously trained models; the example assumes separate end-of-term terms.
Before signing the operative grant, work through this schedule:
| Field | Question to settle |
|---|---|
| Parties and authority | Who can grant the included recording, composition and contributor rights? |
| Dataset | Which manifest, version, cutoff, units and exclusions are covered? |
| Uses and outputs | Which evaluation, training, synthesis and commercial output uses are permitted? |
| Recipients and onward rights | Who receives copies, and may they sublicense or create derived datasets? |
| Term and exclusivity | What restrictions apply, for how long and where? |
| Reserved rights | Which publishing, streaming, internal or other licensing uses remain? |
| Updates and end of term | What happens to new recordings, corrections, retained copies and existing grants? |
| Money | Which base, deductions, funded work and payment event govern? |
Retained ownership can coexist with a broad, long-lived grant. Read that grant with the person responsible for rights and the relevant advisers. For music, keep masters, compositions, lyrics and versions explicit. For a named voice, keep synthesis permission distinct from recognition. Resolve warranties, liability, indemnities, handling and dispute terms against the control you actually have; do not promise universal ownership or erasure of effects from previously trained models.
The current public music lot describes owner approval of buyer, use, price and terms before sharing and direct owner-buyer signature. That is the route described for that lot. Your paperwork should identify the route governing your package.
Agree acceptance and remedies before full delivery
A manifest digest establishes byte identity. It does not establish accurate transcripts, valid rights or a useful model result. Define acceptance using the promised files, count rule, formats, annotations, rights evidence, exclusions and tests.
Name the decision-maker, inspection coverage, response period, defect evidence and consequences of partial acceptance. Decide whether silence has any effect; do not assume it does. Keep receipt and acceptance as separate records.
| Question | Agreed answer to record |
|---|---|
| What is a defect? | Specific failure against a stated criterion and identified files |
| Who investigates? | Responsible party, evidence and response period |
| What correction is allowed? | Correction, replacement or retest scope and number of attempts if limited |
| Who pays? | Included work versus separately authorized charges |
| What if it remains unresolved? | Negotiated rejection, narrowed delivery, adjustment, refund or other remedy |
| What happens to partial acceptance? | Accepted units and the resulting price/payment calculation |
These are terms to negotiate for the deal. They are not a standard Rightmark refund or unlimited-rework policy.
Invented distinction: a transcript promised for A017 is missing. That is a possible defect against the agreed deliverable. A buyer later asking for emotion labels that were never included is a change request. The second task needs its own scope, price and permission, even if the same recording is used.
State when money becomes due
Put the payment trigger next to the amount: signature, specified delivery, acceptance or another expressly agreed milestone. Record invoice requirements, payer and payee, currency, due period, taxes, withholding, transfer costs and any installment conditions. If owner settlement depends on buyer funds clearing, make that visible before accepting the deal.
For a per-unit license, define provisional and accepted quantities, any minimum commitment and the dispute adjustment. For revenue share, define attributable gross or net revenue, allowed deductions, reporting cadence, statement access, advances or minimums, and post-term duties. A track being opted in does not itself establish revenue.
Reconcile intermediary compensation and preparation charges against the same document. A cost deducted from a share should not also appear as an additional charge unless that separate treatment is expressly agreed. An invoice issued, a contractual due date and cleared money are three different states.
8. Deliver the agreed version, reconcile acceptance and track payment
Send a package the recipient can identify
Confirm the authorized recipient, transfer route, purpose and delivery schedule. Rightmark's audio process describes scoped, revocable connections approved by administrators or exports; it says Rightmark never holds passwords. Use the agreed mechanism, with the permissions needed for this package.
Bundle the promised audio and included transcripts or annotations with a manifest, fingerprints, format/channel/timestamp description, source-to-derivative references, rights-evidence references, exclusions and QA summary. Include license-use restrictions and the responsible contacts. Sensitive identity evidence belongs on the restricted review path, not automatically in every training folder.
| Invented Harbor delivery record | Entry |
|---|---|
| Package/version | HARBOR-SPEECH-v3, an invented controlled reference |
| Proposed quantity | 500 elapsed hours, using the agreed exclusions and count method |
| Delivered scope | Identified audio, included transcript versions and manifest |
| Receipt | Buyer confirms transfer completeness and manifest match |
| Acceptance | Assumed 450 hours accepted; 50 hours held out under the agreed criteria |
| Commercial effect | Reconcile payment on 450 accepted hours under this assumed deal |
The companion manifest leaves actual file fingerprints blank for computation from actual files. An invented digest would provide no integrity evidence. For a partial batch, state which units and milestone it covers. When files change, issue a new version and update audio, transcripts and manifest together.
Delivery tip: A receiver saying “the transfer finished” has confirmed arrival. Obtain the separate acceptance decision and count before treating the payable quantity as settled.
Build the calendar from named events
The current Rightmark buyer page gives 2 to 6 weeks from the end of scoping to first audio samples. It identifies this as an October 2026 Rightmark planning estimate at Low confidence, indicative and confirmed at scoping. It does not measure first inquiry to full delivery, acceptance or payment.
Indicative estimate, not an offer. Final offers depend on the systems you connect, data size and quality, access terms and due diligence.
| Stage | Start and completion evidence | Next responsible party | Timing basis |
|---|---|---|---|
| Initial description | Owner chooses slice; useful inventory description supplied | Owner and route contact | Agree next decision date |
| Rights and prior grants | Scope identified; authority gaps resolved or excluded | Owner/rights lead | Depends on actual records and permissions |
| Scope, work and price | Requirements available; written scope and work allocation agreed | Parties approving proposal | Agree for this deal |
| Preparation to first samples | End of scoping; first agreed samples supplied | Named preparer and owner release lead | Published 2 to 6 weeks, Low confidence |
| Evaluation and commercial decision | Permitted sample received; findings and next decision recorded | Buyer and parties negotiating | Agree response window |
| Delivery and acceptance | Agreed package sent; receipt then acceptance recorded | Sender and buyer | Contractual schedule and review window |
| Invoice and cash | Agreed invoice event; due date then actual receipt | Named payer/payee | Actual payment terms |
Each handoff needs a named person, required artifact and agreed next date. Client or guest permission, composition authority, transcript work, sample-test approval, contract negotiation and buyer response can determine the critical path. Those are dependencies to manage, not measured average delays.
Some work can proceed in parallel. Do not add overlapping estimates into a new total or borrow a code or company-archive clock for audio. Revisit the calendar when a rights gap or changed requirement alters the work.
Walk through a completed calendar, then replace its assumptions
Invented Harbor calendar: all dates, durations, permissions, contractual windows and outcomes below are assumptions. Day 0 is the first complete non-sensitive inquiry. This is not a normal, average or promised Rightmark timeline, and it is unrelated to a completed transaction.
| Relative calendar day | Assumed event | Evidence and next decision in the example |
|---|---|---|
| Day 0 | Complete non-sensitive inquiry | Asset, task, approximate count and known gaps described |
| Day 3 | NDA and evaluation permission signed | Recipients and permitted sample tests defined; this does not clear unresolved recordings |
| Day 7 | Scoping ends | Package, relevant permissions and preparation work order agreed; only the cleared slice proceeds |
| Day 28 | First samples supplied | Identified sample, selection method and permitted tests travel together |
| Day 35 | Buyer decision and final license | The conditional price and defined use become signed terms |
| Day 42 | Identified full delivery | Manifest and receipt cover the agreed 500 hours; substantive acceptance remains separate |
| Day 49 | Written acceptance and valid invoice | 450 hours accepted; the invented 14-calendar-day payment term begins |
| Day 63 | Funds actually received | The example assumes payment arrives on its due date; remittance confirms the $18,000 owner receipt |
Day 7 to Day 28 is 21 elapsed days, or three weeks. Day 0 to Day 63 is 63 elapsed days, or nine weeks. Those are calculations from this example, not an estimate for your archive. The published sample clock above has its own start and scope; it supplies no guarantee for the remaining stages.
Permitted rights and contract work can overlap preparation, but nothing uncleared enters a sample. If permission remains unresolved on Day 7, hold that slice, finish or revise scope and rebase the later dates. A changed channel requirement returns the parties to the package, sample and quote. If money has not arrived on Day 63, record it as due or outstanding, not paid. No acceptance-by-silence, automatic deadline extension or refund rule is assumed.
Music and commissioned effects have different early dependencies. Both sequences below are separate invented examples: all dates and terms are assumptions, and each cash date assumes actual receipt. No price is specified. The music sequence assumes a fixed-fee license; it is not AV-OPTIN's revenue-share route, which would need its own reporting and cash cycle.
| Invented audio-family sequence | Scoping and sample | License, delivery and acceptance | Assumed cash event and dependency |
|---|---|---|---|
| Music catalog | Unresolved composition authority holds scope until Day 21; first sample Day 42 | License Day 49; delivery Day 56; written acceptance and valid invoice Day 63 | Cash received Day 77 under an invented 14-calendar-day fixed-fee term. Both-rights review and version mapping determine readiness |
| Commissioned field effects | Work order, sample permission and funding agreed Day 7; recording and preparation begin Day 8; first sample Day 21 | Final license Day 28; delivery Day 35; written acceptance and valid invoice Day 42 | Final-license cash received Day 56 under an invented 14-calendar-day term. Earlier preparation funding is a separate money event; capture availability, ownership and event coverage govern readiness |
For commissioned work, agree responsibilities and sample rights before recording begins. For your real opportunity, use the companion's blank milestone planner and enter the actual events and dates. Keep the completed examples separate from that record.
Reconcile the accepted units to cash
Return to invented Harbor. Assume the final agreement pays $40 per accepted elapsed hour, with 450 hours accepted. Gross license consideration is 450 × $40 = $18,000. Assume a standard fee-on-top structure, a fixed additional $1,800 buyer-paid intermediary fee and $2,000 buyer-paid preparation. These are invented amounts, not published tariffs.
| Invented cash line | Amount or state |
|---|---|
| Owner license consideration | $18,000 |
| Intermediary fee paid separately by buyer | $1,800 |
| Preparation paid separately by buyer | $2,000 |
| Buyer all-in amount before excluded tax/charges | $21,800 |
| Owner expected receipt before own obligations | $18,000 |
| Assumed invoice trigger | Written acceptance plus valid invoice |
| Invented due period | 14 calendar days after written acceptance and valid invoice on Day 49; due Day 63 |
| Assumed cash received for illustration | $18,000 on Day 63, after checking remittance; receipt is assumed, not inferred from the due date |
| Unexplained difference | $0 under these assumptions |
The hypothetical cash result is not evidence of a real transaction. If only $17,700 arrives, the $300 difference needs a supported explanation, such as agreed withholding or a bank charge; do not automatically call it commission. Record actual remittance, allowed deductions, exchange treatment and outstanding balance in your private cash sheet.
A useful event log has separate columns for delivered, received, accepted, invoiced, due and paid, with evidence for each. An advance or installments can change the order. Follow the actual contract rather than forcing every deal into one sequence.
Keep the rights register useful after payment
Maintain package/version, recipient or approved recipient scope, use, term, exclusivity, prior grants and ongoing obligations. For music, retain recording/composition scope and included versions. For a named voice, retain the specific permitted use. Check those commitments before offering the prepared files again.
New episodes, added stems, corrected transcripts or newly documented permissions do not silently become part of the old delivery. Record an agreed update, exclusion or new license. Track renewal/reporting dates and retention or deletion evidence. Ending access is a different action from changing previously granted rights or reversing model training.
For the first conversation, you need a smaller set of answers: the asset and task, approximate quantity with its unit, languages or genres and recording context, available formats and labels, known rights and gaps, desired license scope, and a responsible contact. Keep real recordings and identifiable transcripts out of that first description.
- 01 inventory rights (MD)
- 02 offer economics (MD)
- 03 preparation delivery cash (MD)
- Audio process text (MD)
- Audio process (MMD)
If your sole aim is to license a personal synthetic voice, use a suitable voice platform's own permission and payout process. For an existing audio package, I would begin with the slice you can describe, clear and count. The first review does not commit you to licensing or promise a buyer. Appraise your audio to explore its indicative value and possible route.
Sources
- Datarade via Internet Archive (archive capture 2025-08-03).
- License Your Data to AI Companies (2026-10-26).
- Buy AI Training Data With Clean Title (2026-10-21).
- Rightmark Price Index for AI Data Licensing (2026-10-26).
- Trust and Compliance for AI Data Licensing (2026-10-18).
- Voice and Audio Data Licensing for AI | Rightmark (2026-10-10).
- Audio Sample Rate, Channel, and Clipping Review | Rightmark (2026-10-22).
- Audio Transcript Consent and Provenance Review | Rightmark (2026-10-22).
- Rightmark Clean Room: Raw Data Never Leaves Your Building (2026-11-11).
- EURECOM (2026-03-21).
- License music stems and sound (2026-10-08).
- Arabic speech and priced hours (2026-11-12).
- Private company data, licensed by the companies that own it (2026-11-10).
- Microsoft (2026-09-23).
- United States Copyright Office (2021-03).
- ElevenLabs (2024-02-13).
- SpeechData.ai (2026-10-17).
- Microsoft (2025-12-19).
- Ditto Music (2026-08-25).
- License call center and sales call recordings (2026-10-18).
- Public lot AV-CALLS (2026-11-10).
- Public lot AV-CALLS-CLIENT (2026-11-10).
- Public lot AV-FIELD-SFX (2026-11-11).
- Public lot AV-MUSIC-CLEARED (2026-11-15).
- Public lot AV-OPTIN (2026-11-11).
- Public lot AV-PANEL-PODCAST (2026-11-10).
- Public lot SE-A (2026-11-10).
- Data valuation (2026-11-15).
- Data licensing broker: what earns the fee (2026-11-15).
- How to license voice, music and audio to AI labs: labeled worked examples and assumptions (2026-11-15).