IAMCCS-SuperNodes AU+IMG2VID Exec Finalize

The AU+IMG2VID SuperNodes split a full LTX 2.3 audio-plus-image-to-video pipeline into three stages - Render, VAE, Finalize - so you can inspect and re-run each without touching the whole graph. Finalize is the closer: it takes the decoded frame directory, muxes the audio, and writes the final video file.

By the time you reach this node, Render has produced frames (or you decoded them in the VAE stage) and you have your audio track. Finalize's whole job is ffmpeg assembly: frames at a set frame rate, encoded with a chosen CRF and pixel format, optionally trimmed to the audio length. It's the IAMCCS_VideoCombineFromDir engine wearing a SuperNode costume, wired to accept the linx metadata that ties the whole run together.

Inputs

• frames_dir - where the rendered/decoded frames live.
• audio - the AUDIO track to mux. Required.
• frame_rate (default 25) - output FPS.
• filename_prefix (default IAMCCS/GC_AUIMG2VID_EXEC) - output path.
• crf (default 19) - encode quality.
• pix_fmt - yuv420p or yuv444p.
• trim_to_audio (default on) - cut the video to the audio duration, the right call for lipsync.
• linx (optional) - the SuperNode metadata object; pass it through so the run stays linked and reporting works.
• debug_verbose (optional) - louder logging.

Outputs

• video_path - the finished file. The one you actually want.
• linx - metadata for whatever you want to chain after.
• report - summary of the encode.

Install

The SuperNodes ship inside IAMCCS-nodes:

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

or via ComfyUI Manager (search "IAMCCS"), restart. SuperNodes don't add their own Python deps, but they do expect the underlying machinery - native LTX/LTXV nodes in your ComfyUI build, VideoHelperSuite for video paths, and ffmpeg available. Missing any of those and the graph may load but fail at validation.

Troubleshooting

The pack's own requirements doc flags the classic symptoms. If the output looks fine but runs long or short, check trim_to_audio against whether audio is actually wired - with no audio connected the trim is a no-op. If the muxed video has audio drift, verify the frame_rate here matches the rate your Render/VAE stage used; Finalize trusts your number and won't reconcile it. And the universal SuperNode gotcha: don't let duplicate copies of the pack sit in custom_nodes, or node registration breaks. If a saved workflow's widgets look shuffled after an update, recreate the Finalize node rather than fighting stale state.