FUZZ-1.1 is a legacy music generation model in the Riffusion FUZZ series, suited for turning song themes, style ideas, or self-written lyrics into listenable audio. It offers both inspiration and custom creation modes, and can also be set for instrumental tasks. On this platform, it can be accessed through the Riffusion or Producer audio entry points, with works and follow-up tasks managed around song IDs.
Clarify capacity, inputs and outputs, and invocation methods before selecting a model.
The above are the input and output specifications for this platform's creation entry points. Use editing actions and control parameters according to the applicable scope of the selected entry point and model.
Learn what FUZZ-1.1 can bring to your work.
When you do not yet have lyrics, you can first use a prompt to describe the song's theme, mood, instruments, and stylistic direction, then initiate creation with generate. For example, organize “rainy night, soft piano, warm atmosphere” into a prompt to obtain listenable music material and determine whether the idea is worth developing further.
When you already have lyrics, use custom=true to enter custom mode, place the lyrics in lyric, and add a title. In the Riffusion entry point, you can also fill in style separately, allowing lyric content and sonic direction to be expressed independently. This is suitable for first defining the narrative and chorus, then trying song drafts in different styles.
FUZZ-1.1 creation results are delivered as audio links and song information, making them easy to audition, save, and associate with projects. Applications can record song IDs, titles, and statuses, and use asynchronous tasks or callbacks to arrange result delivery, integrating music creation into content management workflows rather than always waiting for a single request to finish.
Start with specific tasks to find where the model can be effective.
Enter completed verses, choruses, and a song title, then add the styles you want to try to generate a listening draft for discussion. You can use the same lyrics to try different sonic directions, compare how the words are expressed in music, then decide which sections need adjustment. The deliverables are audio and the corresponding song record.
For short films, product demos, or event videos, enter descriptions of mood, instruments, and atmosphere, and use the instrumental setting for instrumental music tasks. First use generated audio to determine the soundtrack direction, then handle duration and transitions in editing software; this approach is suitable for finding creative ideas, but prompts should not be treated as precise timelines.
For music projects that previously used FUZZ-1.1, you can continue to explicitly select this model and retain lyrics, prompts, and titles as creative records. Listen to new audio alongside older work and compare whether the expressive direction suits the current project; version comparisons should be based on the actual sound rather than only the model name.
Choose based on task complexity, input materials, and expected results.
FUZZ-1.1 and FUZZ-1.1 Pro are separate models, and they also differ from FUZZ-1.0 and FUZZ-2.0. If you have existing FUZZ-1.1 creation records or want to continue experimenting around this historical version, you can choose it; for new projects, it is advisable to compare listening results using the same lyrics and prompts, choosing based on the song's expression rather than inferring results solely from version numbers.
If you want to fill in style separately, choose /riffusion/audios; if you already have a Producer integration workflow, use /producer/audios and explicitly set FUZZ-1.1. Requests for the two cannot be exchanged as-is; Producer requires action, lyric, and prompt to be included together. When you need variation or editing tasks, you should also distinguish between entry point actions and model suitability.
From a small-scale task to formal integration.
Define the goal, required inputs, and output requirements, using real business examples as a starting point.
Open the trial page, confirm the parameters supported by this entry point, then submit a small-scale task to view the results.
Keep the complete model ID, use the request format specified in the documentation, and confirm billing rules on the Pricing page.
Before formal use, understand the output quality and range of capabilities.
Answers to common questions about using FUZZ-1.1.
No, they are separately listed models, and calling FUZZ-1.1 does not make it equivalent to Pro because of the similar name. When choosing, you can compare them by previewing the same lyrics and style, then decide based on the result; do not apply Pro descriptions or generation examples from other versions to FUZZ-1.1.
You can start with inspiration mode, using prompt to express the theme, mood, and sonic direction, without completing the full lyrics first. However, the request must still include the fields required by the endpoint: Riffusion requires action and lyric, while Producer also requires prompt; whether lyric content is needed and whether a field is required are two different things.
Write the lyrics in lyric, set custom=true, and use action=generate、model=FUZZ-1.1. You can add title; in the Riffusion endpoint you can also fill in style. Lyrics are recommended to be organized into sections such as verses and choruses, and after generation, focus on previewing the verbal expression and musical structure.
The creation endpoint provides an instrumental switch, which can be used to set an instrumental task, then describe the instruments, mood, and style with prompts. An instrumental setting does not mean specifying an exact song length or receiving stem files; when delivering, read the actual audio and duration, and perform post-processing according to the intended use.
After completion, read audio_url from data, and save the song ID and status. When using async=true, first obtain task_id, then retrieve the result through task queries; you can also set callback_url to receive completion notifications. Successful task submission and completed audio should be presented separately in the application.
Model information · Updated: 2026-10-01. For calling parameters and billing rules, see the API and pricing sections.
Start with a clear goal and judge whether it fits your work based on real results.
