Premiere Export Plan

MKRPremiereExportPlan builds the plan that brings generated stills back into a Premiere sequence: the file path, how Premiere should consume it, and which sequence to target. It's a pure builder - no filesystem, no pixels - and it feeds MKRPremiereExportOutput, which does the writing, and ultimately the Premiere UXP plugin, which does the importing.

The use case is the classic edit-roundtrip: you've got a sequence in Premiere, you want AI-generated frames or plates dropped in - maybe a new graphic, maybe replacing an existing clip's content, maybe a poster frame into the Graphics panel. This node is where you declare which of those three things you mean, without touching Premiere at all.

The inputs that matter

• asset_path - where the generated file gets written. Shared filesystem, reachable by both ComfyUI and Premiere. The field that has to be right.
• apply_mode - the three ways Premiere can take a file:
  • new_track_item - default. Drop it onto a track as a new item. The safe, iterative choice.
  • replace_clip - swap the content of an existing clip in place, keeping its position and duration. The compositing-into-the-cut choice.
  • graphics_panel - hand it to the Essential Graphics panel, for titles and lower-thirds style assets.
• target_sequence_name - which sequence to act on (Sequence 01 default). Get this exact; the plugin matches by name.

Optional transport_plan_json attaches a transport/endpoint plan to the same payload.

The outputs

• premiere_export_plan_json - the plan, schema mkrshift_premiere_export_plan_v1. Wire it into MKRPremiereExportOutput.
• manifest_line - a compact sequence,apply_mode,path line for manifests and logs.
• summary_json - target sequence, whether a path exists, whether a transport plan is attached, warnings.

Installing

Pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/criskb/MKRShift_Nodes

restart, or Manager → "MKRShift". Nothing extra to install on the ComfyUI side.

Gotchas

The pure-builder truth applies: clean output ≠ working roundtrip. The path still has to be shared, and target_sequence_name must match the sequence in your project by name - Premiere sequences are commonly renamed, so "Sequence 01" is a guess. With replace_clip especially, an exact clip target matters and the plan carries only the sequence name, so expect some plugin-side setup on first use. And remember: the plan is metadata, the output node is the write, the plugin is the import. Debug in that order.