Skip to content

Resolve drum-sample licensing for the two bundled music assets #225

Description

@schmug

Task

Determine the actual license and attribution terms for the drum samples in the two music assets now shipping in this plugin, and record the answer in each PROVENANCE.json.

Both assets publish to public RSS feeds on every episode as of the music integration, so this is a live exposure, not a hypothetical.

Context

  • skills/daily-podcast/assets/music/pixel-window.flac — Pixel Window, the daily show's bed.
  • skills/frontier-commits/assets/music/midnight-terminal.wav — Midnight Terminal, the Frontier Commits sting.

Both were composed in Strudel using built-in synth waveforms plus Strudel's default bd, sd and hh samples. The composition itself is Cory's. The samples are not.

Both PROVENANCE.json files currently record license.status: "UNRESOLVED — do not assume, do not invent one" with the explicit note that Strudel's engine license does not automatically cover the sample packs it ships. Neither file asserts a license, deliberately.

What to find out

  1. Which sample bank does Strudel's default bd/sd/hh resolve to? (Strudel loads a default sample map; identify the actual pack and its upstream source.)
  2. What are that pack's license and attribution terms — public domain, CC0, CC-BY (needs credit), or something that forbids redistribution in a podcast?
  3. If attribution is required, where does it belong: the episode description footer (description_footer_text, per-show), the show notes, or the site?

Acceptance criteria

  • Each PROVENANCE.json license block states the actual terms with a link to the source, replacing status: UNRESOLVED.
  • If attribution is required, it is actually wired into whatever the terms demand — not just documented.
  • If the terms forbid this use, say so plainly and open a follow-up to replace the samples; do not quietly keep shipping.

Out of scope

  • Re-composing or replacing the music.
  • Any change to the mix, the music config surface, or render.py.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions