FUZZ-1.1 Pro is the legacy professional tier in the Riffusion FUZZ series, suitable for organizing song themes, lyrics, and sound direction into listenable musical works. On this platform, you can create through Producer or the Riffusion audio entry point, and obtain audio links and song information. It is especially suitable for projects that continue to use this version, rather than being the default choice that bundles all next-generation music tools together.
Clarify capacity, inputs and outputs, and invocation methods before choosing a model.
The above describes the inputs, outputs, and controls of this platform's creation entry points and does not represent native capacity metrics; editing actions are performed according to the actual support of the entry point and model used.
Learn what FUZZ-1.1 Pro can bring to your work.
When lyrics are not yet written, use prompts to describe the song’s theme, mood, and sonic direction; when lyrics already exist, submit the text and title through custom mode. These two approaches allow FUZZ-1.1 Pro to support both inspiration exploration and the conversion of a defined lyric concept into a listening sample.
Lyric content and sound descriptions can be prepared separately, making it easier to distinguish between “what is sung” and “what it sounds like.” The Riffusion entry provides style, while the Producer entry uses prompt to describe the creative direction. This is suitable for finalizing lyrics first, then comparing different instrumentation and mood options, rather than rewriting the full creative brief each time.
Generated results provide not only audio links, but also song ID, title, lyrics, status, and actual duration, making it convenient to save works and connect follow-up tasks. The asynchronous approach can first obtain a task_id, then query it or receive callbacks, allowing listening samples, selection, and archiving to fit into the normal workflow of music creation applications.
Start with specific tasks and find where the model can be effective.
Enter completed verse and chorus lyrics, then add a song title and sonic direction to generate listening samples for creators to discuss. The focus is on judging the overall feel once the words are set to music, then deciding whether to revise the lyrics or try a different arrangement direction; the deliverables are the audio work and its associated information.
Prepare theme and mood descriptions for short films, podcasts, or event content, and use lyric-free mode to explore soundtrack directions. After listening, provide suitable work links and actual durations to editors for selecting material and arranging pacing; do not treat duration requirements in natural language as precise editing instructions.
For song projects already using FUZZ-1.1 Pro, retain the model selection, lyrics, and sound description to continue producing candidate works. When an existing song needs editing, prepare the audio_id and a clear modification objective, then use an appropriate continuation or segment replacement task, saving the new results for comparison listening.
Choose based on task complexity, input materials, and expected results.
If a project has already established listening preferences around FUZZ-1.1 Pro, or needs to maintain the same version's creative conditions as existing work, it is worth keeping. FUZZ-1.1 is the standard tier of the same generation, while FUZZ-1.0 Pro is another historical version; do not judge differences solely by the Pro name, and compare results using the same lyrics and sound requirements.
For brand-new projects, you can compare FUZZ-2.0, FUZZ-2.0 Pro, and this model through listening tests: the former is the general recommended tier, the latter is for professional production, while FUZZ-1.1 Pro retains value as a historical professional-tier option. Make trade-offs based on lyric rendering, musical direction, and required editing tasks, rather than applying all features of later versions to this model.
From a small-scale task to production integration.
Define objectives, required inputs, and output requirements, using real business examples as a starting point.
Open the trial page, confirm the parameters supported by this endpoint, then submit a small-scale task to review 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 output quality and capability boundaries.
Answers to common questions about using FUZZ-1.1 Pro.
No. They are different tiers from the same generation: FUZZ-1.1 Pro is the historical professional tier, while FUZZ-1.1 is the standard tier. When calling it, explicitly specify FUZZ-1.1 Pro; when choosing, you can audition them using the same lyrics and sound direction without assuming a fixed level of audio-quality improvement.
Use generate and enable custom mode, then submit lyric; you can also provide a title and sound direction. The Producer endpoint requires action, lyric, and prompt; the Riffusion endpoint requires action and lyric, and you can use style to describe the style.
You can use instrumental mode without lyrics and describe the musical direction around mood, instrumentation, and intended use. It is suitable for soundtrack candidates and instrumental previews; requests must still retain the fields required by the endpoint, and the final length should be read from the generated result rather than treating length descriptions in the prompt as a hard guarantee.
If you already have a Riffusion creation workflow, you can continue using /riffusion/audios; if you use the Producer workflow, use /producer/audios. Both can specify this model, but their field and action names differ, so keep request construction and result parsing consistent with the selected endpoint.
After the task is complete, read audio_url from data to obtain the audio, and save the song ID, title, and status. When using async=true, save task_id first and then query the completed result; you can also configure callback_url to receive callbacks and associate returned works with the original creation task.
Model information · Updated: 2026-10-01. For call parameters and billing rules, see the API and pricing sections.
Start with a clear objective and decide from real results whether it suits your work.
This is only a basic call example. See the full docs for more parameters and advanced usage.
View Docs