SMC Describe Config

SMC Describe Config (class SMCDescribe) is a one-trick pony, and the trick is useful: it takes the SMC_CONFIG object built by SMC Config and dumps every field as a plain string. No processing, no image output - just "here's what's actually in the config."

Why would you want that? Because SMC_CONFIG is an opaque bundle, and if you're like most people, you've set twelve knobs in SMC Config, run the workflow, and later have zero idea what values produced a good result. Wire SMCDescribe into a Show Text node and the config becomes copy-pasteable and comparable. Save it next to your good images and you've got a poor man's settings history. It's the pack's answer to "wait, which warp_strength did that?" - which, given how sensitive this heuristic pack is to its knobs, is a real question.

Input and output

• Input: config (SMC_CONFIG) - straight from SMC Config.
• Output: STRING - one line per field, matching the CompandConfig fields: anchor_mp, base_blur_radius, mask_falloff_radius, warp_strength, radial_strength, anisotropy_strength, lowfreq_anchor_mix, chroma_restore, contrast_restore, detail_preservation, max_inward_shift_px, edge_softness.

Install & gotchas

Same pack, trivial install:

cd ComfyUI/custom_nodes
git clone https://github.com/xmarre/ComfyUI-StableManifoldCompander

or ComfyUI Manager (search "Stable Manifold Compander"). No extra dependencies.

The only mild annoyance: the output is a single multi-line string, not separate string ports, so if you want one value you're parsing it yourself - that's fine for its job. And it only reads the anchor-guided SMC_CONFIG; if you're tuning the affine path's SMC Affine Profile, use that node's profile_json output instead, which does the same thing for the profile dict. For tracking your settings across runs, the simplest habit is to also save the string to a text file alongside your output images - a one-node "config recall" system that costs you nothing.