MiniMax H3 Creator Shot Override / 可编辑镜头卡 (Advanced/T8)

A Studio Timeline is the ground truth for your H3 project, but you don't want to rebuild it every time one shot changes. That's the job of MiniMaxH3CreatorShotOverrideT8Advanced: it stacks a non-destructive overlay onto one shot of an existing timeline - new prompt, seed variants, media roles, retention policy, hold metadata - and hands the result forward as an edit plan. Chain one node per shot you want to touch, and the timeline underneath stays untouched. This is the "editable shot card" of the Creator Workspace flow, and it's built to be reversible: disable the node and the shot goes back to whatever the timeline said.

How it works

Each override targets one shot_index (0-based) in the timeline. You can rewrite the compiled prompt (compiled_prompt_override), force a specific seed (use_seed_override + seed_override), or - the more interesting route for a production pass - expand into variants: variant_count and variant_seed_stride define how many seeds this shot gets and how far apart they step. media_roles_json maps your reference media to roles (the default shows the shape: picture_1 is your first_frame, audio_1 is your voice_reference). You also set the retention_policy - keep_all, keep_winner_and_metadata (default), keep_accepted_only, or metadata_only - and the hold_policy/hold_frames for how many frames the shot holds (first, last, both, or custom). Multiple overrides chain through previous_edits.

Why the retention/hold stuff matters

This is the T8mars philosophy in miniature. H3 clips are expensive, so the pack makes you decide up front what survives: keep only the winner, keep accepted ones, or keep just metadata. Nothing here deletes a file - the retention policy is recorded, and the separate Retention Plan node later turns it into a keep/proposed-delete manifest you actually review. The enabled toggle per node is the kill switch; the whole design assumes you will change your mind.

Inputs and outputs

The two outputs are edit_plan (the H3_T8_CREATOR_EDIT_PLAN you chain into the Workspace node) and edit_plan_json for reading. Everything else is inputs, and honestly you only touch a few: shot_index, the prompt override, variant_count, and retention_policy. Leave the rest at defaults until you have a reason.

Installing it

It's part of the MiniMax H3 Audio T8 pack. ComfyUI Manager → search MiniMax H3 Audio T8, or:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8

then restart. No forced pip deps; models are your responsibility (models/diffusion_models, text_encoders, vae, loras). Reminder that the H3 weights' Community License excludes the US, EU, UK and South Korea.

The trap

Because overrides are invisible once they're mid-chain, people forget they're there - you changed variant_count three nodes ago, and now every shot renders four seeds and you can't remember why. The edit_plan_json output is there precisely so you can check. If a shot isn't honoring your override, verify shot_index actually matches (0-based bites again) and that enabled is true. And remember: an override edits the plan, not the timeline - reconnect or disable it and you're back to stock.