Licensing samples legally: CC, clearance and attribution

The moment a sample-based track leaves your laptop — a Bandcamp release, a livestreamed set that gets archived, a beat sold to a client — its legal status stops being academic. This module builds one whole professional habit: sourcing sounds from mixed origins (a Freesound field recording, a credited CC-BY loop, a lifted commercial break) and shipping them with a licence/attribution sheet that a label, a sync supervisor, or your future self can trust.

The arc starts supported. First exercises are pure badge-reading: given a sound page, name what CC0, CC-BY, CC-BY-NC and the legacy Sampling+ badge each permit — drill this until it is a snap judgment, because every later decision hangs off it. Next comes reasoning about the sounds themselves: what is even copyrightable in a recording (rain isn’t; a drummer’s break is), and, for the commercial sample, why clearance means two separate deals — one with the master owner, one with the publisher. A middle exercise has you trace remix compatibility through a chain of inputs to pick a legal output licence, with the fair-use/fair-dealing doctrine as the tool for deciding whether an appropriation needs clearance at all.

The capstone is unsupported: three real sources, one track, one release-ready sheet. Every required atom gates it — you cannot state “what is cleared” without the licence tiers and the two clearance rights, cannot state the permitted output licence without remix-compatibility logic, and cannot fill the risk column without knowing how Content ID fingerprints raw CC sounds and how CC terms are being read against AI training. The supporting atoms enrich the picture: sampling history, Funky Drummer economics, ROM-synth traps, and obfuscation craft explain why this paperwork culture exists — read them to understand the stakes, not to pass the capstone.