Mureka Mock Generation

Mureka Mock Generation is the pack's cost-saving cheat: it replays an old generation response without calling the API at all, so you can build and test everything downstream of the generation step without spending a single credit. The name is honest - it doesn't generate anything, it pretends to.

What it takes and gives

One input: json_text, a multiline STRING holding a complete Mureka generation response in JSON. One output: result, typed MUREKA_GENERATION_RESULT - the exact same package the real Mureka Song and Mureka Instrumental nodes emit, which is the whole trick. Everything downstream (Mureka Save, Mureka Decode Audio) can't tell the difference, so your save/decode/mix/export graph gets exercised for real while the generation step is a lie.

Where do you get valid JSON? The README gives two paths: run a real generation into a Preview Any node and copy its content, or grab the metadata JSON file that Mureka Save wrote for an earlier run. Both produce the same structure. Paste it in, and the mock node hands it straight through.

Why you want this

Because generations cost credits and debugging a graph shouldn't. If you're wiring up a complex chain - decode, trim, re-encode, mix, export - you don't want to spend real money on every failed attempt while you sort out a misplaced wire. Mock Generation is the README's first cost-management tip, and it's a good one: build the graph against a mock, and only spend credits once the pipeline is actually correct.

Installing

The whole pack installs one way - ComfyUI Manager → Install Custom Nodes → search "Mureka API" → restart, or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/leewinder/comfyui-mureka-api.git

No models, no GPU, nothing heavy. Just the pack.

Gotchas

• It needs a valid response from a real run - the README is explicit that Mock Generation needs a valid generation response to work correctly. Random or truncated JSON will error, not fail gracefully.
• It won't produce audio. If you expected a track, you're in the wrong node; this one only replays the result object.
• The JSON can get long and ugly in the box. That's fine, it's just data, and the field is multiline so you can paste it as-is.

There's a workflows/Mureka-Mock-Workflow.json in the repo showing the intended layout - mock generation feeding the post-processing nodes. Load it and you'll see the point instantly.