ITDA Open Editor

ITDA (잇다, Korean for "stitch") is a frame-accurate, layered video editor that runs entirely inside ComfyUI, and ITDA Open Editor is its front door. The whole point of the pack is the problem anyone who generates AI video eventually hits: you make five clips, and joining them into one continuous piece is manual, fiddly work - two clips usually overlap in content, and finding the exact frame where one should end is a pain. ITDA gives you a real timeline with five layers, per-clip audio, and a tool called Auto Stitch that analyzes the overlap between two clips and suggests where to cut. This node is how you get to all of it from inside the graph.

What it actually does

Mechanically, it's almost embarrassingly simple: pick a project, and the node returns two strings - the project name and a relative URL like /itda/editor?project=my-project. The editor itself is served by the pack's own routes on your existing ComfyUI server, so "embedding the editor in the graph" really means opening that URL in a panel while the node sits there holding the project name for you. That's a bridge node, not a heavyweight one, and the work it saves is wiring: you pick the project once, and everything downstream knows what you meant.

You can skip the node entirely and just open http://127.0.0.1:8188/itda/editor in a browser tab (use your actual ComfyUI port). The node's real value is keeping the project name as a live value you can hand to the rest of the workflow.

Inputs and outputs

One input, two outputs - this node is a thin thing, and that's fine.

• project_name - a dropdown of projects, read from ComfyUI/input/ITDA/projects. If it's empty, you haven't created a project yet; open the editor via the URL and make one.
• project_name (STRING output) - connect this to ITDA Load Export's project_name_override input. That's the loop: Open Editor picks the project, Load Export reads its latest export. The output is ordered first deliberately, so dragging off the node's first socket lands straight into Load Export's own override - one less thing to set twice.
• editor_url (STRING) - the relative URL for this project's editor. Useful for handing the link to something or just opening it in a browser.

The workflow it's built for: Open Editor → stitch and trim your generated clips on the timeline → Export → Load Export turns the result back into an IMAGE batch plus AUDIO for whatever you do next (upscale, regen a section, save out).

Worth knowing before you rely on it

Auto Stitch is the headline feature, and the author's honesty about it is refreshing. It scores cut candidates on frame similarity and motion continuity and shows the top five - but it deliberately does not rank by audio. The README explains that audio-based ranking was measured against known-correct cuts on generated footage and made the right cut worse, so audio level is shown beside each candidate as reference only, and nothing gets applied until you click Apply. An editor that tells you its scoring rationale in the docs is one you can trust to not clobber your work.

The pack is also unusually careful about paths: every file it touches lives inside ComfyUI's official input/ITDA and output/ITDA directories, and it refuses paths outside those roots - it resolves .. and symlinks rather than doing sloppy string checks. In an ecosystem where custom nodes run arbitrary code on import, a pack that actively contains its own file access is a genuinely nice signal.

Installing it

Same as every node in this pack - it's one install.

cd ComfyUI/custom_nodes
git clone https://github.com/designloves2/itda
# restart ComfyUI

Or ComfyUI Manager → search ITDA → install. Requirements are minimal: just aiohttp and numpy, plus ffmpeg and ffprobe on PATH (standard ComfyUI installs have them). OpenCV and librosa enable motion match and beat detect but are optional - the features degrade gracefully without them.

Gotchas

The project dropdown being empty is the #1 confusion - the list only fills after you've actually created a project. The editor assumes it's only reachable from localhost, exactly like ComfyUI itself, so don't try to expose it over the network without auth. And if you're on a non-standard port, remember the node's editor_url is relative - it resolves against whatever host and port you loaded ComfyUI on, which is usually the thing you want anyway. It's not a node that rewrites your workflow; it's the doorway to the tool that does the real work.