Generative features

Use generation to make candidate sounds from a description, or use a recording as the starting point for stems or a single-note MIDI melody. Choose the tool for the result you need. Hosted generation is in preview and requires account access; individual tools offer different actions.

Choose a musical task

Goal	Useful result
Describe a sound	Candidate hits, textures or loops to audition and curate
Build a kit or bank	Related sounds mapped into a playable instrument
Work with a recording	Separated parts or an extracted single-note melody where the tool supports it
Develop musical ideas	MIDI material or model-assisted interactions in the specific tool that offers them
Make a connected instrument	An explicit generation action with account access, progress and result handling

Audio, MIDI and a playable instrument are different outcomes. MIDI contains musical events and needs a sound source; a generated recording still needs selection and preparation before it becomes a useful bank.

Start with a useful request

Describe what the sound should do in the music: a short dry hit for a drum pad, a sustained texture or a loop with room for a vocal. Include the character and duration when the tool offers those choices.

For a drum hit, check the attack, tail and level against the rest of the kit. For a loop, check the timing and whether it leaves space for the other parts. You may need several candidates or further editing before a result fits.

Keep and reuse results

Hosted generation uses an account and the permissions available to it. Results can become source material for a sampler bank or audio to use in another project. Check the available save and export actions for that workflow.

Generation and credits explains account access and costs. If a service reports a pending job, check its status before submitting the same request again.

If generation is unavailable

Read the tool's message before trying again. Missing account access, an unavailable service and insufficient credits need different remedies; generation and credits explains the account checks. If you cannot resolve the problem, contact support with the tool, job reference if one exists and error message.

Build generation into a product

You can prepare a product's sounds before release, let players generate using their own account, or discuss a server or local-model integration. Generation in your instruments and apps compares those choices.

The generative beatbox example follows a product from playable pads through sign-in, generation, distribution and reporting. For a model or custom workflow, use research and integration projects.

For implementation details or an app integration, continue with developer concepts and the generation reference.