Home/ The Signal/ Industry/ AI Music Generation Litigation: How a Copyright Case Turns Into Your Licensing Problem
Copyright

AI Music Generation Litigation: How a Copyright Case Turns Into Your Licensing Problem

The email arrives four days after you delivered the cue: 45 seconds, 128 BPM, a detuned Rhodes under a filtered break, bounced to 48kHz WAV, already approved by the client's creative director.

A dimly lit professional recording studio at night, shot from behind an empty producer's…

The email arrives four days after you delivered the cue: 45 seconds, 128 BPM, a detuned Rhodes under a filtered break, bounced to 48kHz WAV, already approved by the client's creative director. Legal has one question. Where did this music come from, and will you warrant that nobody else owns it. AI music generation litigation is why that email exists, and why it will keep arriving long after the current cases are resolved.

Here is the verdict in a sentence: these lawsuits are not a referendum on whether AI music is legal, they are a machine for converting unlicensed training data into licensed training data, and the cost of that conversion travels downhill to whoever is rendering tracks at the end of the pipe.

The machine runs in a fixed order. It is worth walking through in order, because each stage determines what the next one is able to do.

First: the corpus goes in, unpriced

Every generative music model starts with an ingestion decision that gets made quickly and documented badly. Someone assembles a training corpus, and in music that corpus is made of sound recordings — masters — not sheet music. This matters more than it sounds. A song carries two separate copyrights: the composition, controlled by publishers and songwriters, and the master recording, controlled by the label. When a model learns timbre, room tone, the particular compression on a snare, it is learning from the master. That is the asset the major labels own outright and have spent forty years litigating over.

So the first stage of the mechanism is not a legal event at all. It is an engineering decision, made under deadline pressure, that quietly creates a per-work count. Every recording in that corpus becomes a countable unit. Nobody prices it at the time. The pricing happens later, by someone else, in a filing.

Second: the complaint does arithmetic

The complaint is where the count becomes a number, and the number is the whole point.

Under US copyright law, a rightsholder who registered their work can elect statutory damages instead of proving actual losses, and the ceiling for willful infringement is $150,000 per work. That figure is durable — it has been the statutory maximum for a long while — and it is the reason these filings read the way they do. As of writing, Sony Music's suit against Udio put the count of allegedly ingested recordings in the neighborhood of 30,000. Multiply the two and you get a theoretical exposure north of four billion dollars.

No generative music startup has four billion dollars. That is not a flaw in the strategy, it is the strategy. The arithmetic is not there to be collected. It is there to make continued operation contingent on a conversation, and to make the conversation happen on the plaintiff's calendar. The word "willful" is doing the heaviest lifting in the paragraph — it multiplies the ceiling by five, and it is why every internal message about scraping becomes relevant later.

Third: discovery, which is where the leverage actually lives

Most people following these cases watch the filings and the press statements. The filings are theater. Discovery is the part that sets the price.

What gets produced in discovery is the training manifest, the ingestion pipeline logs, the storage buckets, the vendor contracts, and — reliably the most expensive documents in the set — the internal messages in which engineers and executives discussed whether what they were doing was permitted. There is usually an output-side exhibit too: a list of prompts that returned something a listener would recognize as a specific recording, or a voice that sits uncomfortably close to a named artist.

The defense at this stage tends to be an analogy. The model listened and learned the way a student listens and learns; abstraction is not copying. It is a serious argument, and it maps onto fair use doctrine in ways courts have not yet settled for audio. It is also an argument nobody wants to be the first to lose in a published opinion, on either side. That mutual reluctance is what makes stage four inevitable.

Fourth: the settlement, which is not a verdict

As of writing, both Universal and Warner have reached settlements with AI music companies rather than pushing to judgment. Read that carefully, because it is the load-bearing fact in this entire story.

A settlement produces no ruling. It answers nothing about fair use, sets no precedent, and leaves the next company to negotiate from scratch. What it produces instead is a license — usually bundled with commercial terms, sometimes equity, generally an ongoing relationship in which the rightsholder gains a say in how the model behaves. Artist opt-in mechanics. Restrictions on generating in the style of, or in the voice of, specific performers. A royalty pool. Guardrails written into the product by the people who sued over the product.

The market answers the legal question the courts have not. Training on major-label catalogue becomes a thing you pay for and get permission for, and the price of entry rises for whoever comes next.

Fifth: the terms change under you

This is the stage that reaches your project folder.

When a company settles and retrains on a licensed corpus, its terms of service get rewritten. Sometimes the model you used in March is not the model that exists in October, and the output you delivered in March came from the older one. Indemnity language appears, which sounds like protection until you read the conditions: indemnities are commonly gated to paid tiers, capped at some multiple of what you have paid, and voided if you prompted with an artist's name or used the output in a way the agreement excludes. Free tiers are almost universally non-commercial, and the word "commercial" is doing a lot of quiet work in those documents.

None of this is unusual or scandalous. It is what happens when an unpriced input gets priced. But it means the license you believed you had is a license as of a date, and dates move.

What I check before betting a paid deliverable on a tool

Clause to find The question it answers The failure mode
Commercial use grant Does the tier I actually pay for permit paid client work Grant lives one tier above the one you are on
Indemnity Will they defend me if a claim lands Capped at your annual spend, or absent entirely
Survival on termination Do delivered tracks stay licensed after I cancel Rights lapse when the subscription does
Model and training disclosure What is the corpus, and has it changed No disclosure at all, which is common
Export Stems, 48kHz WAV, or only a lossy stereo bounce Client asks for stems on Thursday, you have an MP3

An honest negative applies to every tool in this category without exception: not one of them can hand you the clean chain of title a broadcast clearance department is used to receiving from a production music library. They can give you a contractual promise. That is a different object, and it is worth less when the promising party is a startup with active litigation on its docket.

Who this should worry, and who can keep working

Worry if you deliver into broadcast, national advertising, a game shipping on a major storefront, or anything that touches errors-and-omissions insurance and a music cue sheet. Those pipelines require warranties you personally sign, and an insurer will happily push the risk onto you.

Keep working if you are doing internal decks, prototypes, temp tracks before a real score, personal releases, or a client video with a small audience and a client who understands the tradeoff. For a Friday edit that lives on one YouTube channel, this is not your risk. For a spot with a media buy behind it, someone will make it your risk.

What to do this week

Open the terms page of the one tool you actually use. Find the indemnity paragraph and the commercial-use grant, screenshot both with today's date visible, and drop the images into a folder alongside the exact prompt text and the rendered file for your most recent paid delivery. Fifteen minutes, one project. Then do it for each new delivery as you go.

A license you cannot produce on demand is not a license, it is a story.

Not sure which tool to use?

Compare the top AI music and sound tools side by side — honest reviews, real pricing, no sponsorships.

Compare the Tools
N

Nova Reyes

Editor, The Signal

Nova Reyes edits The Signal and reviews AI music tools after a decade scoring indie games and short films; still owns four broken synthesizers. More by Nova Reyes →