# Archived example workflows The complete maintained 0.5 catalog is preserved unchanged in [`0.5/`](0.5/). Those files retain their historical node types, positional widget values, frontend metadata, prompts, and asset bindings for exact reproduction; they are not recommended for a new 0.6 project. The additional files directly in this Archive are still older mixed and experimental examples retained for compatibility and reference. The clean 0.6 workflow catalog lives one level above this folder, beginning with [`T2V Normal - MiniMax H3 0.6.json`](<../T2V Normal - MiniMax H3 0.6.json>) and [`T2V Studio - MiniMax H3 0.6.json`](<../T2V Studio - MiniMax H3 0.6.json>). `Ref2V Legacy Scheduled - MiniMax H3.json` and `Ref2V Studio Legacy Scheduled - MiniMax H3.json` preserve the former active Ref2V examples with explicit numeric scene selectors. The recommended Ref2V examples now use prompt-driven Tagged nodes one level above this folder. ## V2 demos: choose single-image I2VA, core FL2VA, or Scheduled Ref2VA [`Looping Single Image I2VA 20s V2 - MiniMax H3.json`]() is the simple long-form image-to-video starting point. It uses one opening image, no last-frame input, and two requested 10-second scenes. The included **First-Scene Image Gate** passes `` to ComfyUI's stock `MiniMaxH3ImageToVideo` only for scene 1; later recursive scenes receive no first-frame keyframe and continue from saved H3 Motion Context. The prompt editor marks Picture 1 active for scene 1 and inactive for scene 2. H3 rounds each 10-second request up to 243 raw frames. With the example's five-frame head overlap, the final delivery is `243 + (243 - 5) = 481` frames, or 20.04 seconds at 24 fps. Duplicate the second Plan scene to extend the chain; each additional requested 10-second continuation contributes 238 frames (about 9.92 seconds). Replace the opening image and both generic motion prompts before queueing. [`Looping Core FL2VA V2 - MiniMax H3.json`]() is the scheduler-free starting point. It uses ComfyUI's stock `MiniMaxH3ImageToVideo` with a deliberately one-scene, 124-frame plan so one first/last keyframe pair is applied exactly once. The prompt follows H3's FL2VA format and the Scene Prompt Editor previews both connected native Picture labels. Disconnect the last image for a one-scene I2VA render, the first for L2VA, or both for T2VA. For a multi-scene I2VA chain use the dedicated example above; a globally connected keyframe would otherwise constrain every recursive scene. [`Looping Seamless Chain V2 - Scheduled Refs - MiniMax H3.json`]() is the full fourteen-scene Ref2VA demonstration. It includes the large Scene Prompt Editor, reference hover previews, Review Gate, muted recovery assembly, and date/version-safe final filenames. Its schedule exercises every media route: - `@hero_face` is active only in scenes 1–7; - `@hero_look` is always active and therefore renumbers from `` to `` beginning in scene 8; - `@performance` and paired `@performance_audio` are active in scenes 4–6; - the frame-exact `@song` slice is always active, moving from `