KfDebug_Vae
Proof of life for the decoder, nothing more
- item
- VAE
Like its sibling KfDebug_Model, KfDebug_Vae is a proof-of-life node. A VAE is an opaque object - no tensor shape, no dtype, no meaningful value to dump - so the inspector logs the type and calls it a day. What you get out of it is a definitive answer to one question: did a VAE object actually arrive on this wire? If you've got a VAE switcher, a conditional path, or you're just paranoid that the VAE you think you're using is the VAE you're actually using, this node settles it.
It logs to the console, not the canvas - the family rule - and passes the VAE through untouched. If you came here expecting VAE diagnostics like "which VAE is this" or its resolution, you'll be disappointed, because the node doesn't know either. It's a wire tracer, not a profiler.
Why you'd reach for it
VAE misrouting is a real failure mode, especially in bigger graphs. You load a checkpoint, get a VAE from it, then somewhere a VAE Loader or a switch replaces it, and suddenly your decodes look wrong. A KfDebug_Vae right before the VAE Decode tells you a valid VAE is present, so you can rule the plumbing in or out of your troubleshooting. It's a niche need, but when you need it, it's exactly right.
The inputs that matter
item- theVAEto inspect, force-input off a wire.label- multiline string, default"debugging passthrough". Here, the label is the payload: it's the only distinguishing text your console line will have, so name it for the wire it's watching ("decode vae","refiner vae").
Output: a single VAE - the identical object, passed through so you can keep the node inline without changing anything.
How it works
KfDebug_Vae is KfDebug_Passthrough with RETURN_TYPES = ("VAE",). The shared inspector logs the type, checks for dtype/shape/size (none present on a VAE), finds no dict keys and no list-ness, and prints the object. You get a line confirming the type, and that's the whole report - honest about what it can and can't tell you.
Installing it
Part of ComfyUI-Keyframed. ComfyUI Manager: search "Keyframed". Or:
cd ComfyUI/custom_nodes
git clone https://github.com/dmarx/ComfyUI-Keyframed
Restart ComfyUI. The pack pip-installs keyframed and toolz on first load; no model files to download.
Troubleshooting
If the console line shows the VAE type, your plumbing is fine and your decode problem is elsewhere - check the latent, check the sampler. If it shows something that isn't a VAE, you've found your misroute. And don't expect more from it than that: this node's job is a single boolean, "is a VAE here?", and it does that one job without pretending to do more.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| item | VAE | — | |
| label | STRING | debugging passthrough | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| VAE | VAE | — |