Bubba Metadata Debug

The whole Bubba pack runs on metadata you can't see. A BUBBA_METADATA object rides through the pipe invisibly - model name, seed, steps, CFG, sampler, prompts, LoRAs, save prefix - and unless something displays it, it might as well not exist. Bubba Metadata Debug is the x-ray: it converts that metadata object to pretty-printed JSON and displays it right on the node, and also passes the same text out as a string you can wire somewhere.

If you've ever wondered "did my workflow actually record the seed correctly?" or "is the save prefix what I think it is?" - this is the node that answers it, and it's the first thing to drop into a Bubba workflow that isn't behaving as expected.

How to use it

The node has no required inputs. Wire either (or both):

• pipe - the tooltip says it plainly: "Optional incoming pipe containing metadata to debug." It reads the pipe's metadata.
• metadata - a BUBBA_METADATA object directly.

If you connect both, the explicit metadata wins. The single output, metadata_text, is the pretty JSON as a STRING.

The frontend part is the point: the JSON renders on the node body itself, so you see the record at a glance - no console, no separate viewer, no serializing to a file. Because it's also an output node (terminal), it's meant to sit at the end of a debug branch: wire a pipe through it to inspect, then on to the real destination, or keep it as a dead-end inspection tap.

What you'll actually learn

The metadata fields the pack tracks give you the complete generation receipt: schema_version, model_name, clip_skip, sampler_time_seconds, steps, cfg, sampler_name, scheduler, denoise, seed, positive_prompt, negative_prompt, loras, and save_prefix. In practice, the three things people use this node to check:

• Did the metadata survive? If you loaded a PNG that was saved without Bubba metadata, the fields come back empty/default - this node makes that obvious instead of mysterious.
• Is the seed right? The classic "the seed in the box isn't the seed that ran" confusion (the after-generate control rewrites the widget) - the metadata records what actually ran, and this node shows it.
• What's in the pipe? When a pipe node isn't carrying what you expect, seeing the metadata object's actual contents beats guessing.

It also has a quiet forensic use: because Bubba Save Image embeds this exact metadata into the PNG, and Bubba Load Image (With Metadata) reads it back, you can load an old image and debug its metadata to confirm the record made the round trip.

Install and context

Bubba Nodes, standard install:

cd ComfyUI/custom_nodes
git clone https://github.com/bubbafett5611/Bubba_Nodes

or ComfyUI Manager → search "Bubba Nodes", restart. ComfyUI 0.27.0+, no extra dependencies.

Honest take: this is a pure debug utility, and it's the node you install the pack for only if you've already bought into the metadata model. It shares a job with Bubba View Text (which displays arbitrary text on a node) but is specific to metadata. If you're not using the pipe, you probably don't need it - but the moment something in a Bubba workflow "doesn't record," this is where you look first.