FLUX.2 Cover – On / Off

A one-boolean node, doing real work

Music toolkits love to bolt a diffusion model onto the end so you get cover art. That's great until you're on a 12GB card and the artwork branch is the thing that pushes you over - FLUX.2 dev sits at 18–24GB even quantized, which is why the consumer path is Klein 4B and why "do I really need the picture this run?" is a question worth answering with a switch instead of by deleting nodes.

This is that switch. enabled in, cover_enabled out, default on. The interesting part isn't what it computes (nothing) - it's what it's wired to in the bundled workflow, and how ComfyUI behaves when it's off.

How the off actually happens

Two wires come off the output, and both matter.

The first goes to Save Image Smart Prefix, the artwork saver, into its optional enabled input. That node's image input is declared lazy, and its check_lazy_status only asks for the image when it's enabled. So with the cover off, ComfyUI walks backwards and finds no reason to execute the FLUX sampling branch at all - the render is skipped, not rendered-and-thrown-away. The author's own field description states it exactly: off skips FLUX execution and downloads in the bundled workflow, and audio export continues without artwork.

The second wire goes to the model-check node's flux2_models input, which is the download group. That's the half people forget: skipping the render doesn't stop the model preflight from pulling the FLUX.2 files, so the switch also turns off the download. In a fresh install that's three files you no longer fetch - the FLUX.2 Klein 4B diffusion model, the Qwen3 text encoder and the Flux2 VAE, all listed in the pack's models_config.json.

One consequence worth knowing before you flip it: the artwork saver returns an empty path instead of writing a file, so whatever consumes that path - the central production JSON in this pack - gets nothing rather than an error. The audio side is untouched.

When you'd actually use it

Three honest cases. You're iterating on the song and the cover costs you a minute and a couple of gigs of VRAM per run - turn it off until the mix is final. You installed the pack for the mastering chain and the Audio Enhancement Lab, and never wanted generated artwork in the first place. Or you already have a cover image and you're pasting it in yourself, in which case the FLUX branch is pure overhead.

If you just want the render skipped for one experiment, muting the node group in the canvas does the same thing to the picture. The difference is the download suppression, and having one labelled switch in the timeline you're working in rather than hunting for the right group to mute.

Install

It ships with the toolkit: ComfyUI Manager → search MiniMax Music Production Toolkit, or clone into custom_nodes and install the requirements with ComfyUI's interpreter.

cd ComfyUI/custom_nodes
git clone https://github.com/jplenio/ComfyUI-MiniMax-Music-Production-Toolkit.git
cd ComfyUI-MiniMax-Music-Production-Toolkit
python -m pip install -r requirements.txt

Restart and hard-refresh. If you left the cover on and want to see what the preflight will do before you commit to a download, the pack exposes it over HTTP:

# report only, transfers nothing
curl http://127.0.0.1:8188/minimax_music_toolkit/model_preflight

Gotchas

The toolkit's own troubleshooting file is a good reminder of the general rule here: model weights are not bundled, they're fetched by the catalog and some are licence- or auth-gated. A cover that fails silently on a fresh install is usually a missing FLUX.2 file rather than the switch.

And if your workflow's final production JSON stops appearing, remember it only writes after the original audio, release FLAC, release MP3 and artwork saves have all completed. That's intentional in this pack - a record claiming artifacts exist is worse than no record - but it means the artwork branch is not a place to leave half-configured. Turning the cover off is a supported operation; leaving it on with no FLUX weights is not.