audioshake-stem-separation

What it does

Operates AudioShake's cloud source-separation service to split a recording into stems. It covers driving the developer API, selecting appropriate stem targets for a production task, reviewing stems for bleed and artifacts, and addressing rights, consent, and when to prefer a local open model over the API. It explicitly notes not to generate, synthesize, mix, or master audio and to avoid working with copyright-infringing content without proper rights.

How it works

• Use the Tasks API to upload or reference the source audio (via url or assetId).
• Create a task with POST /tasks, listing one or more targets as { "model": "<name>", "formats": ["<fmt>", ...] } (1–20 targets per task).
• Wait for completion by polling GET /tasks/{id} or via webhooks; each target moves through processing → completed | error.
• Download outputs from the output array; presigned URLs expire ~1 hour after task completion.
• Consider reviewing stems for bleed, artifacts, transient smearing, or phase problems, and repair as described (e.g., add a residual/other target, or reprocess with denoise/dereverb before multi-voice). Ensure responsible handling of rights and privacy.

When to use it

Use when the job requires pulling apart a recording into music stems (vocals, drums, bass, etc.), separating dialogue/music/effects for DME, creating multi-speaker stems, lyric transcription/alignment, or content analysis like music detection.

What it can touch

• API endpoints: https://api.audioshake.ai with authentication header x-api-key: <key>.
• Task definitions including assets/assetId, url, targets, and formats.
• Outputs available via URLs in the output array of the task response.

Caveats

• Not for generating/synthesizing audio, mixing, or mastering.
• Outputs are subject to bleed and artifacts; repairs may require additional strategies (residual targets, denoise/dereverb, etc.).
• Rights and privacy considerations apply: you must have rights to uploaded audio; stems are derivatives; data handling policies may affect confidentiality.
• Output URLs expire ~1 hour after task completion; store promptly.