Upload And Cover Audio · V4.5ALL

A "cover" in Suno's vocabulary isn't a tribute act. You hand it a track, and it re-performs that track in a style you specify - the bones stay, the sound changes. Country version of your synth demo. Ambient version of a folk song. This node is the V4.5ALL version of that endpoint.

Mechanism, briefly

It's an API call, not a local model. The node builds the request, ships it to KIE.ai under the transport model ai-music-api/upload-and-cover-audio, passes V4_5ALL as the version, then blocks polling until the task resolves or timeout_seconds (default 1200 seconds) expires. You get back a decoded ComfyUI AUDIO object, same as any audio-generating node in this pack.

What you'll actually set

upload_url is required, and it's the raw material: a publicly reachable URL to the source. In this build it's a plain string widget rather than an audio socket, so a track you just made in the same graph needs to exist online before KIE can fetch it - the pack's upload utilities under KIE Next / Utility are the intended bridge. Source limit is 8 minutes; longer files are rejected rather than trimmed.

instrumental (required toggle, default true) decides whether the cover sings. With it on, the docs say don't pass lyrics, prompt or vocal_gender at all - and the source alone is still enough to generate, so a cover of an unlabelled instrumental works without any text. With it off, lyrics is used as the words for the cover and falls back to prompt if lyrics is empty.

style is the heart of the node: this is where the cover gets its new genre. title is cosmetic-ish but worth setting, since it lands in file names and player UIs downstream. negative_tags is your exclusion list. Then style_weight, weirdness_constraint, audio_weight and variety - the same optional nudges as the generation node, and just as mild. duration and persona_model are documented as V5.5/V6-family features, so they're dead weight on V4.5ALL.

Outputs

Seven. audio is the cover, ready for SaveAudio or a video pipeline. all_urls_json holds every result URL - Suno returns multiple takes and audio is only the first, so this is where the alternate versions hide. url, task_id and raw_json cover linking and debugging, and raw_json also contains the provider's source_audio_url alongside the new audio, which is handy when you're covering your own material and want to check the right source went up. credits_consumed and credits_left report the cost; the node also displays both on its face after each run.

Installation

Manager → search the title ComfyUI-KIE-Nodes-Next ("KIE.ai Nodes Next"). Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/felipederosilva/ComfyUI-KIE-Nodes-Next

Restart ComfyUI when it's done. The package needs requests, Pillow, numpy and PyYAML - no model files, no VRAM. Then set your key: Settings → KIE.ai Nodes Next → Connection → Paste / replace KIE.ai API key. KIE validates it before the pack overwrites anything, keeps it in Comfy's user config (not in workflow JSON), and shows a masked fingerprint with a ✅ CONNECTED status. If you run ComfyUI as a service, KIE_API_KEY in the environment takes precedence.

Honest caveats

This version is on the way out. KIE's own parameter docs flag V4.5ALL (Discontinued), along with V4, V4.5, V4.5PLUS, V5 and V5.5; V6/V6_MINI/V6_WILD are the current family. The node exists because the page still documents it. New setups should start from the V6 sibling.

A cover is a fresh generation, not a remix. You don't get stem control or a partial swap - if you want to keep the original vocals and change the backing, look at Add Instrumental or the stem-separation nodes instead. Swapping one section is Replace Music Section.

Credits go whether or not the cover works. Long sources with dense arrangements are the most likely to come back strange, and you pay for the attempt. Keep source clips short while you're learning what the style field will actually do.

Mind what you're uploading. Covering someone else's released track sends it to a third-party API and comes back as a derivative - that's a licensing question, not a node question, but it's the one people forget.