AD_Latent_Diffusion_Keyframe

Straight talk first: this node's own home in the pack is a menu folder literally labeled Deprecated. That's the author telling you not to build a new workflow around it. Apt_Preset's active video work has moved to the LTX_video branch (AD_LTX_load_model, AD_LTX_config, AD_LTX_sampler, and friends), which is where the README's recent update log points too. This article exists so that if you find AD_Latent_Diffusion_Keyframe sitting in an old saved workflow, you know what it was doing and where to go instead - not as a recommendation to reach for it fresh.

What it looks like it did

Per its own node description, "AD video keyframe auto relay." Reading the schema, it took a positive/negative conditioning pair plus an image latent (img_latent/img_vae) and re-emitted them alongside a trend_data output and an optional carried-forward history - the shape of a segment-by-segment video generator, where each call processes one keyframe segment and threads state to the next one via history, with history_strength and history_fade_frames controlling how much of the previous segment's influence decays as you move forward.

The inputs and outputs, for the record

Required: positive (CONDITIONING), negative (CONDITIONING), img_latent (LATENT), img_vae (VAE), history_strength (FLOAT, default 0.5, 0–1), history_fade_frames (INT, default 16, 1–100), and num_guides (a dynamic-combo type). Optional: history (HISTORY) - presumably fed back in from a companion node's output on the previous segment. Outputs: positive, negative, img_latent, img_vae (pass-throughs), plus history (HISTORY) and trend_data (KEYFRAME_TREND) - the latter being the type that AD_keyframe_trend_preview exists to visualize.

Installing the pack (if you're maintaining an old workflow)

Through ComfyUI Manager: search "ComfyUI-Apt_Preset". Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/cardenluo/ComfyUI-Apt_Preset.git

Then run install.bat (Windows) or pip install -r requirements.txt (Linux/Mac) per the pack's README, and restart. Note that a deprecated node can still ship with the pack and still load fine - deprecated in this author's convention means "moved out of the active menu group," not "removed from the codebase."

What to actually use today

If you're starting fresh and want segment-by-segment or history-aware video keyframing on LTX, look at the LTX_video category instead: AD_LTX_load_model builds the initial config, AD_LTX_sampler runs the actual sampling with its own crop_ outputs, and AD_LTX_vae_combine decodes and can hand you a last_image specifically for chaining into the next segment - which is the modern equivalent of what history here was trying to do. If your workflow depends on this node's exact HISTORY/trend_data types and nothing else in the pack currently produces or consumes them, that's a sign the surrounding pipeline it was designed for has moved on without it - treat it as a rebuild, not a patch.

Common issues & troubleshooting

Given its deprecated status, the honest troubleshooting advice is: if this node is erroring, breaking, or producing garbage, the fix most consistent with how the author has treated it elsewhere is to migrate off it rather than debug it - there's no indication it's still receiving fixes.