Skip to main content
create.remix_instrumental takes a piece of music with no vocals and makes new variations of it. On its own, the source guides the result; add a prompt to steer it toward a style or mood you describe. Use it to get fresh versions of a music bed, to vary a theme across a series, or to restyle a track you already own. For a track with vocals, use create.remix_song.

The request

Every field, with its exact rules: submit and poll in the API Reference.

Example

This makes three variations of an instrumental, steered toward synthwave, and saves them. It uses the reference client; save soundpiece.py or soundpiece.mjs next to it first.

The result

run returns the finished remixed_instrumental object, with one entry in outputs per variation:

Choosing parameters

  • With or without a prompt? Leave prompt out for variations that stay close to the source. Add one to move them toward a style or mood. Write it as a short phrase or sentence, such as "A slow, emotional solo piano piece around 80 BPM", not a list of tags. The output is always instrumental, so directions about vocals or lyrics have no effect.
  • Source. Use music without vocals. For a song with vocals, use create.remix_song.
  • n_variations. Ask for two or three when you want to choose; each costs the same as one.
  • Loudness. Off unless you include the block. See the loudness normalisation guide for which target to pick.

Errors

When you submit (the request is refused, nothing is charged): While processing (the operation finishes as failed, with an error.code): Source limits for this endpoint: WAV, MP3 or FLAC, from 1 second to 5 minutes long, and at most 50 MB. See Errors for the response shapes, and for the errors every endpoint can return (401, 403, 429).

Cost

3 credits per variation, so n_variations: 3 costs 9. Normalisation costs nothing extra. Resending a request with the same idempotency key is not charged again.