Skip to content
Strumly
Sign in
← All guides

Rights & IP · 7 min read

What Happens to Your Guitar Samples in AI Training

Your guitar recordings are likely already in AI training sets. How the scraping pipeline works, what rights you have now, and what an ownership layer changes.

By Jason Colapietro

AI music models are trained on real recordings — yours included. Here's what the pipeline looks like and what your rights actually are.

If you have ever posted a guitar riff to SoundCloud, uploaded a demo to Bandcamp, or dropped a loop pack on any royalty-free marketplace, that audio is almost certainly in an AI training dataset somewhere. Not maybe. Not hypothetically. The pipelines that scrape audio for AI training do not ask for permission, and most terms of service that platform users agree to explicitly permit it.

This is not a conspiracy. It is an engineering reality. And understanding how it works — specifically how your guitar recordings travel from your hard drive into a foundation model — is the first step toward knowing what, if anything, you can do about it.

How audio ends up in training data

The pipeline typically works in four stages:

1. Scraping. Large-scale crawlers pull publicly accessible audio from streaming platforms, music hosting services, sample libraries, and archival collections. The scraper does not distinguish between commercially released work, bedroom recordings, and free loops. If the URL is public and the file is audio, it goes into the pipeline.

2. Filtering. The raw scrape is filtered for audio quality, format compatibility, and sometimes genre or instrument classification. Guitar-heavy content is particularly useful for training generation models because it is abundant, stylistically diverse, and carries clear tonal signatures that the model can learn to replicate.

3. Stripping. Metadata is often stripped or truncated at this stage. The file name, the ID3 tags, the embedded album art, the original uploader's name — all of it may be dropped before the audio reaches the training loop. This is where provenance breaks. The model learns from your playing, but the chain back to you as the creator is severed.

4. Training. The processed audio is converted to spectrograms or audio tokens and fed into the model. The model does not store your specific recording. It encodes the statistical patterns: the way a particular picking attack decays, how a stacked-humbucker midrange compresses, the timing feel of a certain strumming pattern. That signature — your signature — becomes part of the model's learned capabilities. Without attribution, without compensation, without notice.

"The model doesn't store your recording. It stores the pattern. But the pattern came from somewhere, and that somewhere is you."

— Jason Colapietro

What the law currently says

Copyright law protects expression, not style. You own the specific recording you made. You own the specific composition you wrote. What you do not own is the general style of playing, the tonal characteristic of your guitar, or the statistical pattern of how you pick a note.

This is not a new doctrine. It predates AI by decades. Sampling cases in the 1990s established that taking a specific recording without license is infringement. Style-copying cases — George Harrison, Led Zeppelin's "Stairway to Heaven" dispute — largely failed because courts drew a hard line between the specific expression and the general style.

AI training sits in this contested middle ground. If a model was trained on your copyrighted recordings without a license, there is a plausible infringement argument at the training stage. Several major lawsuits are currently working through this question. As of 2026, there is no settled precedent. Courts are actively wrestling with whether ingestion of copyrighted audio for model training constitutes fair use.

For independent guitarists, the practical reality is this: you have a copyright in your recordings from the moment they are fixed in a tangible medium. That copyright exists whether you register it or not. But enforcing an unregistered copyright is significantly harder. Statutory damages — the provision that makes copyright suits economically viable against large defendants — are only available for works registered before the infringement or within three months of publication.

The sample pack problem is different

If you have sold or distributed loop packs, sample libraries, or royalty-free guitar content, the analysis shifts. The license you offered buyers may have been broad enough to permit AI training use. Many royalty-free licenses include language about "any purpose," "commercial use," and "modification" that a determined AI company could argue covers training ingestion.

This was not what most sample creators intended when they wrote those licenses in 2015. It is increasingly what the licenses technically say. If you have existing sample libraries available under broad royalty-free terms, the moment to review those licenses was yesterday. The moment after that is now.

"Royalty-free has never meant free for every possible use. AI training is a use that most 2015 license templates never contemplated."

— Jason Colapietro, Suede Labs AI

What an ownership layer changes

The underlying problem is that provenance breaks at ingestion. If your recording carries no machine-readable ownership claim — no registry record, no content hash linked to you, no metadata that survives stripping — then by the time the model is trained, there is no evidence connecting your work to the resulting capability.

A working ownership layer changes this at the source. When a recording is registered with a verifiable content hash at the moment of creation, the hash travels with the work. If the audio is scraped, the hash is scrapeable too. If the hash is stripped, the stripping itself becomes part of the evidence chain. Future auditing tools — and regulators are beginning to require them in some jurisdictions — can use those hashes to trace what was used and who owned it.

This does not prevent the scraping. It does not retroactively fix training datasets that are already built. What it does is establish a provenance record that survives the pipeline and can anchor a licensing or compensation claim.

What you can do right now

  • Register your recordings with the US Copyright Office. SR registration covers sound recordings. $65 for a single work, $55 for a group registration of up to 10 unpublished works. This creates the legal prerequisite for statutory damages.
  • Review any existing royalty-free licenses. If you have sample packs or loops available under broad terms, consider whether an updated license with explicit AI training carve-outs is appropriate.
  • Embed ownership metadata in your audio files. ID3 tags, XMP metadata, and broadcast wave chunks can carry copyright notice, ISRC codes, and contact information. None of this is legally binding on its own, but it establishes intent and can survive in partial scrapes.
  • Keep a timestamped evidence bundle. Store the original recording, session files, ownership metadata, agreements, and a content hash together. That bundle gives a future ownership or attribution discussion something concrete to examine.

The guitar samples going into AI training today are building the sonic vocabularies that models will deploy for the next decade. Whether you are credited, compensated, or simply erased from that process depends on what ownership infrastructure you put in place before the scraper finds your work.

Basic tools for preserving source files, metadata, and hashes exist now. They are not expensive or complicated. They are simply not the default.

Use the US Copyright Office where appropriate and preserve your own source evidence before the scraper arrives. Suede's IP Registry is live at ip.suedeai.ai and will timestamp a fingerprint of that evidence on Base and Avalanche mainnet. It records provenance; it issues no licenses and is not a substitute for copyright registration.

Further Reading

See also: Rights Metadata Is the Dark Matter of the Creative Economy, AI Training and Your Music: What Every Guitarist Needs to Know, Who Owns the Output Stage.