Why I Stopped Using Splice for Sync-Eligible Music

The Session I Built That I Could Not License

A while back I was producing a beat that an agency wanted to shop for sync. They liked the track. They asked for stems — isolated WAV files of every layer, 24/48, delivered as separate files for the supervisor to mix to picture.

This is a standard sync deliverable. Without isolated stems, the music supervisor cannot duck levels under dialogue, conform cues to specific scene lengths, or process individual elements without affecting the whole mix. The request was reasonable.

I had eight Splice loops in the beat. I opened my Splice license to check what I was allowed to deliver. That is where I hit the wall.

The Clause That Ends Most Splice Sync Deals

Splice's licensing FAQ is explicit about synchronization. The relevant line says, almost word-for-word, that Splice has no restriction on its sounds being used in synchronization contexts. Read on its own, that line makes you think you are good to deliver. You are not.

The next clause is the one that ends the conversation: subscribers cannot sublicense Splice sounds in isolation. That means you are not allowed to deliver a stem that consists primarily of an unedited Splice loop. In a sync deliverable, that is exactly what an "isolated stem" is — the loop, on its own, on its own track, ready for the supervisor to mix.

So legally, the beat is sync-cleared. Operationally, I could not deliver the stems the agency was asking for. I had to walk away from the deal.

Why Supervisors Ask For Those Stems

This is not a Splice gotcha — it is how sync actually works. The supervisor needs flexibility. They have to mix the cue to picture, drop levels under dialogue, sometimes loop a section to fit a longer scene than the original cue length, sometimes mute an element that conflicts with a sound design choice.

Without stems, every edit has to happen on the bounced master. That introduces real compromises — no level control on individual elements, no isolation of specific layers, no ability to swap a kick or remove a vocal chop. Supervisors who accept master-only deliverables are usually settling, not preferring it.

The supervisor's request is reasonable. The Splice license is also reasonable in its own context — Splice does not want to wake up to find their flagship loops being sublicensed wholesale through sync libraries. The two positions are individually defensible. They just do not fit together in the same project.

The Supervisor's Other Concern — Uniqueness

Beyond the stem problem, supervisors have a uniqueness problem with sample-pack material. Splice's flagship loops appear in thousands of tracks. The same vocal chop shows up in a Hot 100 song, your beat, your friend's beat, and a streaming-service commercial. That is fine for most music release contexts. For sync, where the supervisor is licensing your track because they want *this sound* for *this scene*, hearing the same chop in seventeen other placements that quarter is a problem.

Industry blogs that cover sync workflows — That Pitch, Tracks and Fields, Music Library Report — flatly recommend against submitting sample-pack-derived tracks for sync. The reasoning is consistent across the field: the legal clearance problem stacks on top of the uniqueness problem, and supervisors weighing two otherwise-equal cues will pick the one that does not carry either risk.

What I Actually Used Instead

I switched my sourcing to public-domain catalogs — Library of Congress, Internet Archive, Citizen DJ, Musopen. The recordings are real performances, not pre-fabricated loops. Every recording is essentially unique. The license is absolute: public-domain means no entity can claim isolated rights over the audio. And the practical consequence — the part that matters for sync — is that when I bounce a stem from a public-domain source, I own the bounce. I can deliver it as an isolated stem to any sync agency without a license conflict, because there is no upstream license to conflict with.

My first sync placements came after that switch. That is the workflow Selekt is built on.

What We Built — and Why It Is Specifically for Sync Work

Every sample in the Selekt catalog is sourced from public-domain or CC0 material. Every download includes a signed Ed25519 audit chain documenting where the audio came from, what its license terms are, and what the screening result was against the commercial-music fingerprint database before it ever entered the catalog.

The audit chain is not theoretical. You can click an example right now: https://selektaudio.com/audit/454ff65b-b98b-4ad9-9dcd-09a698941d39. Press the green Verify Signature button. The math runs in your browser, against Selekt's public key. No round-trip to Selekt. That is the receipt a music supervisor can verify themselves before agreeing to license your cue.

Critically, there is no "you cannot deliver isolated stems" clause. Public-domain audio is yours to bounce, edit, and deliver as the sync agency asks. Pair that with the per-download license certificate PDF and the audit-chain URL and you have everything a supervisor, library, or rights-holder representative wants to see.

The Honest Part

Public-domain audio sounds different from contemporary sample-pack loops. The Selekt catalog leans heavily on pre-1926 jazz, blues, gospel, classical, spoken word, and early popular music — that is the aesthetic, and it suits some genres and projects better than others. Producers who want pristine modern trap loops, EDM stabs, or contemporary R&B vocal chops are not going to get them from Selekt, and that is fine. Splice will keep doing what Splice does, and we are not pretending to be a one-to-one substitute.

For producers chasing sync revenue specifically — film, TV, advertising, library music, trailers — the math works very differently. A single placement can return ten times what streaming pays per stream over a year. Walking away from a sync deal because of a license conflict on two hundred dollars worth of loops is a worse outcome than building tracks on a different source.

What I Would Suggest to Producers Reading This

If sync is not part of your business and you do not want it to be, this whole post is academic. Splice plus a sample-pack workflow is fine for releases.

If sync is part of your business or might be — start with a public-domain or pre-cleared source. Verify that the license actually permits stem delivery. Run a fingerprint screen on your finished mix before submission. The friction you are avoiding is exactly the friction I walked into the first time.

If you try Selekt and the catalog aesthetic does not fit your music, no hard feelings — the structural lesson holds whether you use our catalog or someone else's. Public-domain or fully-cleared underlying material, plus signed provenance attached to every sample, plus no stem-isolation restriction. Those three things together are what makes sync work.