PrintExpData:

Once you start chaining ExpData nodes together, loading saved presets, and layering add_exp inputs on top of each other, an expression stops being something you can eyeball. PrintExpData is the debug tool for that: splice it into a chain and it prints whatever's actually flowing through the EXP_DATA blob at that point, the same instinct as a print statement in code, applied to a face.

What it does

It's a pass-through inspection node. Wire an EXP_DATA object in, and it logs the contents while forwarding the (optionally cleaned-up) data onward - so you can leave it inline in a working chain rather than needing to unplug it once you're done debugging. It's an output node, meaning running it is treated as a terminal action with a side effect (the print), the same pattern as Save Image.

The one real parameter is cut_noise (0–100), a thresholding control. When you've composited a few expressions together - several add_exp layers, a loaded preset blended with live slider edits - small non-zero jitter tends to accumulate across the vector even where nothing meaningful is happening. cut_noise zeroes out values below the threshold before printing (and before passing the data on), so what you see and what you pass downstream is the deliberate expression, not accumulated floating-point noise.

Inputs and outputs

Required: cut_noise (float, 0–100). Optional: exp, the EXP_DATA blob to inspect. Output: exp, the same data (with noise cut if cut_noise is above zero), passed straight through.

One small aside, purely cosmetic: the pack's own source names this node's class PrintExpData: - with a trailing colon baked right into the class name. It doesn't affect anything, ComfyUI doesn't care, it's just a reminder these are one-person node packs shipped fast, not code reviewed against a style guide.

Installing it

Same install as the rest of the pack - ComfyUI Manager, search ComfyUI-AdvancedLivePortrait, or:

cd ComfyUI/custom_nodes
git clone https://github.com/PowerHouseMan/ComfyUI-AdvancedLivePortrait

Restart ComfyUI. Nothing extra to install for this node specifically.

Where people get stuck

The one thing that actually trips people up: where the output goes. This isn't a UI widget - the printed values show up in the ComfyUI server console/terminal, not anywhere in the browser. If you're looking at the web UI wondering where the numbers are, check the terminal window ComfyUI is running in instead.

Past that, there's not much to troubleshoot - it's a small, honest debug node. If exp is left unconnected, there's nothing to print or pass through, so make sure it's actually wired to whatever expression chain you're trying to inspect before expecting useful output.

If you're not sure whether cut_noise is doing anything, drop it to 0 first and compare the printed output against a nonzero value - that's the fastest way to see which of your values were genuine and which were noise the threshold is quietly stripping out.