Generate Mashup Music · V6_MINI

The speed tier of the same idea

Mashing two tracks together into a third one is the kind of thing you want to audition a lot before committing. That's what this node is for. KIE_Next_V6_MINI_456f3d2f calls KIE.ai's Suno mashup endpoint with the V6_MINI model - KIE describes that version as "lightweight and fast, balancing quality and speed for effortless creation." Translation: it's the one to hammer while you're figuring out whether the pairing works.

The pack generated a node for every model version KIE documents, so Generate Mashup Music · V6 and · V6_WILD are its siblings. Same fields, different musical temperament. If you're iterating on which two songs belong together, stay here and burn credits cheaply; once a pairing clicks, re-run it on the bigger version.

How it works, briefly

You're not running anything locally. The node assembles the mashup request, posts it to KIE's task queue, and polls for the result with a 2.5-to-15-second backoff until the job lands or timeout_seconds runs out. The V6_MINI identifier travels inside the payload; the outer job envelope uses KIE's market name for the mashup API. The returned track is downloaded and converted into ComfyUI's AUDIO type, all inside the same execute() call - which means you get a normal node that blocks, not a fire-and-forget submitter.

Worth knowing because it's on the louder edge of what this pack does: the audio in the API-wrapper category leaves your machine by design. Prompts and source URLs go to KIE's servers, and KIE's URL fetcher has to be able to reach them.

Inputs worth thinking about

• upload_url_list - a JSON array in a text box, not a socket. Two public URLs, e.g. ["https://cdn.example.com/a.mp3", "https://cdn.example.com/b.mp3"]. The author's own note says upstream reads only the first two entries, so don't paste five and hope. To use a local file, upload it with KIE • Upload Audio first and paste the returned URL.
• style - required, and this is the actual creative control. "Jazz" fuses differently than "Jazz, 90s boom bap, female vocal" - the latter is where the interesting results come from.
• title - required, cosmetic. It ends up in the filename and the player.
• prompt - a description of what you want. Careful: it's treated as lyrics when you leave lyrics blank.
• duration - 10 to 360 seconds, default 20. Twenty seconds is a draft, not a track.
• style_weight, weirdness_constraint, audio_weight - the three floats that decide whether you get a recognisable hybrid or something unrecognisable. If MINI's output feels like it ignored your sources, push audio_weight up before blaming the model.
• variety - 0 to 4. At 0 you get the same style twice; at 4 you get two very different tracks, per the tooltip's "unreasonably varied."

Outputs

audio is your mashup - the native ComfyUI audio object, ready for Save Audio or a video mux. url is the first result URL, all_urls_json holds every result URL, task_id identifies the job, raw_json is the whole provider response, and credits_consumed / credits_left report the spend, which the pack also paints onto the node body after each successful run.

One trap: Suno returns two tracks per request, and audio only carries the first. If take two is the one you want, open all_urls_json and pull the second URL out of it.

Install and key setup

cd ComfyUI/custom_nodes
git clone https://github.com/felipederosilva/ComfyUI-KIE-Nodes-Next
cd ComfyUI-KIE-Nodes-Next && pip install -r requirements.txt

Restart ComfyUI. Dependencies are just requests, Pillow, numpy and PyYAML - no checkpoints, no model files, nothing to download. There's also a Windows one-click installer in the repo's dist/ directory if you'd rather not touch a terminal.

Then set the key once: Settings → KIE.ai Nodes Next → Connection, paste your KIE.ai API key. It's validated against KIE before it replaces a working key, you'll see a masked fingerprint rather than the key itself, and the status flips to a plain "connected" line when it takes. Servers and headless installs can use the KIE_API_KEY environment variable instead, which takes priority.

Things that go wrong

A malformed upload_url_list fails fast with a JSON parse error - that's a good failure, not a mystery. A URL KIE can't fetch is a bad one: an expensive failed job instead of an error message you can act on.

If the node times out, don't immediately re-run. The task is probably still alive; check task_id with KIE • Task Status or park KIE • Wait for Task on it. Re-submitting is the one mistake here that costs money twice.

And if you're on a pre-0.4.10 build and see model-related rejections, update and restart - that release fixed Suno nodes sending the version string where KIE wanted the market model name.