Nodes/MKRShift_Nodes/Premiere Sequence Import
ComfyUI Node

Premiere Sequence Import

Pull your Premiere timeline into the graph as JSON

By criskb·Created 7 months ago·Updated 5 months ago· 0
Premiere Sequence Import
    • premiere_packet_json
    • clip_manifest_json
    • summary_json
    premiere_payload_json

    Premiere can't read a ComfyUI graph, and ComfyUI can't open a .prproj. MKRPremiereSequenceImport is the bridge's translator: it takes a JSON payload that a companion Premiere Pro addon exports from your sequence and normalizes it into a clean, predictable packet your workflow can actually reason about. If you've ever hand-copied clip names and frame rates from an NLE into a prompt, this is the node that replaces the copy-paste.

    What it's for

    The MKRShift Premiere lane is packet-first: the addon on the Premiere side packages up what it knows about your project - project name, sequence name, fps, resolution, and the clip list - as JSON. That raw payload isn't guaranteed to be tidy, so this node's job is to parse it, clean the text fields, and emit three views of the same data: the full normalized packet, just the clip list, and a human summary.

    The practical payoff is feeding a timeline into the graph. Clip names from your sequence become strings you can match against generated frames; the sequence's fps and resolution become numbers a downstream node can use. It turns "the edit" into data instead of a mental note.

    How it works

    The build method parses premiere_payload_json, pulls the clips array out of it, and wraps everything in a mkrshift_premiere_bridge_v1 packet with project_name, sequence_name, fps, resolution, and clips. Missing fields fall back to sensible defaults (Untitled.prproj, Sequence 01), and anything unparseable lands in a warnings list rather than crashing the graph.

    Inputs and outputs

    Just one required input: premiere_payload_json - the JSON the Premiere addon exports (or that you paste from it). Three outputs:

    • premiere_packet_json - the normalized full packet; the canonical version of the sequence.
    • clip_manifest_json - just the clips array, ready to feed a per-clip workflow.
    • summary_json - sequence name, clip count, and warnings, for a quick glance.

    Installing it

    Pack-level install, same as its siblings. ComfyUI Manager → search MKRShift_Nodes → Install → restart, or:

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

    then restart ComfyUI. No Python dependencies beyond what ComfyUI ships, and no ffmpeg needed here - this is pure JSON processing.

    Common issues

    The one genuine gotcha: this node doesn't read .prproj files and doesn't open Premiere. It consumes the addon's exported JSON, full stop. If you feed it an empty string you get an empty packet (and a warning), not an error, which can make a "why is my clip list empty" moment. And because it's a normalizer, the shape of the output only changes when the addon's export changes - if you're not getting the fields you expect, check the addon version on the Premiere side, not the node.

    CategoryMKRShift Nodes/Addons/Premiere Pro

    Inputs (1)

    NameTypeDefaultDescription
    premiere_payload_jsonSTRING

    Outputs (3)

    NameTypeDescription
    premiere_packet_jsonSTRING
    clip_manifest_jsonSTRING
    summary_jsonSTRING