|
TLDR
The first of the two Suno courtrooms from issue 115 has answered, and it answered against the model.
• The Munich Regional Court ruled today that Suno memorized six GEMA songs, Rasputin and Mambo No. 5 among them, and reproduced them unlawfully.
• The order has three parts: an injunction, disclosure of the figures needed to set damages, and damages still to be quantified.
• The United States fair-use case in Boston is a separate matter, unaffected and still undecided.
• The finding covers model versions 3.5 and 4, the verdict can be appealed, and Suno says it is weighing exactly that, so this is the start of the answer, not the end.
|
••• |
|
The answer arrived on a Friday. In issue 115 I wrote about two courtrooms deciding, under two different theories, whether a music model must license the songs it learns from. The first of them has now spoken. The Munich Regional Court found this morning that Suno memorized six songs from GEMA’s repertoire, Rasputin and Daddy Cool and Mambo No. 5 among them, and reproduced them without permission.
The word carrying the weight is memorized. The court did not hold that learning from music is itself the violation. It held that the six compositions are reproducibly contained in the models it examined, versions 3.5 and 4. The melodies can be brought back out of the weights. In the court’s reading, analysis became storage, and storage is a copy.
I sell finished tracks to clients, so I read the coverage the way I read a contract: slowly, and looking for the parts that name me. Most of the ruling names the model, not the musician. But a few of its lines reach all the way down to how I write a style field.
|
|
THE FINDING
Memorized, not merely analyzed.
|
|
Generating one of the six songs in Germany counts as unlawful reproduction and public performance, the chamber held, and it went a step further: making the model available there infringes on its own, because the copies already sit inside the weights. The order that follows has three parts.
|
THE ORDER
An injunction against further use of the six works. Disclosure of the figures needed to set damages. Damages themselves, in an amount still to be decided. The verdict can be appealed, and Suno, which says the ruling rests on a mischaracterization of how its technology works, has said it is weighing that step.
|
|
What the ruling does not say matters as much. It does not declare every generated track infringing, and it does not touch the newer model versions. The finding is about what versions 3.5 and 4 retained, not about what you made with them.
|
|
THE OTHER COURTROOM
Boston has not spoken.
|
|
The United States case, brought by the labels and argued around fair use, is still waiting on its own answer, and nothing from Munich binds it. The two courts are weighing two different questions: whether the training was permitted to happen, and whether what the model retained is a copy. The world issue 115 sketched is arriving piece by piece. One set of rules where a model is trained, another where it is used, and a working musician standing in between.
|
|
WHAT IT CHANGES
Licensing stops being hypothetical.
|
|
This is GEMA’s second win in Munich, after the lyrics case against OpenAI last November, and the trade press is describing it as the first European decision to say a music model needs a license for its training catalog. Wins like that turn a principle into a price. I expect licensed-catalog modes, regional model versions, and quiet changes to subscription terms before I expect any model to leave Europe. None of that is a promise of new money for musicians. It is a bill being worked out between institutions, slowly, on appeal.
|
|
THE CRAFT MOVE
Keep an origin log.
|
|
The habit this ruling rewards is one I half-keep already and will now keep properly. For every finished track: the reference described rather than named, the style field written as description instead of catalog shorthand, the prompts as actually sent, and one listen-through against the references before delivery. Ten minutes, dated, saved in the project folder. A question about where a track came from should have a written answer.
The style-field rule from issue 135 turns out to be legal hygiene as well as craft. A field that says 1970s euro disco, four on the floor, a spoken male hook is asking the model for a register. A field that names the song is asking it to remember.
|
|
THE TAKEAWAY
Description was always the better craft.
|
|
Munich drew the legal line at memory: a model in trouble for remembering too well, and by extension a workflow in trouble for asking it to. The craft line was already there. Tracks briefed from description come out more yours than tracks briefed from a catalog name, and they were more yours before any chamber said so. The law and the craft are, for once, pointing in the same direction.
|
|
•••
I am putting together an origin log: a one-page record for every finished track, the references described rather than named, the prompts as sent, and the originality checks that ran before handoff, with a worked example for each part of a paid delivery.
Want it when it ships? Reply with send me the origin log and I will get it to you.
|
|
A QUESTION FOR YOU
Could you show where your last track started?
Replies that name the record you already keep, a note, a folder, a saved prompt, tell me what the origin log most needs to include.
If this was useful, forward it to a creator who sells finished tracks to clients.
|
|
Until next time,
Luxe Prompting
|
|
Luxe Prompting
AI Systems and Prompt Craft for Creators
|
|
