Prompt Travel Helper

Prompt Travel Helper is the node you reach for when your animation is driven by a wall of auto-generated captions and you need it to become a timeline, fast. If you caption a frame sequence with a BLIP model, you end up with one caption per line - a description of what's on screen at each point. This node takes that stream and lays it out as a prompt-travel schedule, the same way every other node in ComfyUI-FrameFX thinks: hold frames, transition frames, end padding.

The core skill this saves you is arithmetic. Writing a prompt-travel schedule by hand means computing frame offsets for every caption, escaping quotes, and making sure the loop wraps back to the start cleanly. It's error-prone and boring, and this node does it in one pass.

How it works

Drop your caption block into bulk_text_input (one caption per line - this is the BLIP convention, and the delimiter matters, more on that below). The node splits on newlines, then walks the timeline:

• each caption holds for hold_length frames,
• then transitions for transition_length frames,
• and at the end, the first caption is appended again with end_padding_frames of pad before the loop point closes.

Quotes inside captions get escaped so the schedule stays valid, and overlapping captions on the same frame get joined into one entry. The output formatted_prompts is a single STRING of "frame": "prompt" lines - the standard format prompt-travel consumers expect, ready to wire into your keyframe/schedule input.

The inputs

• bulk_text_input - multiline BLIP caption stream. The only input you feed by hand.
• hold_length (default 5) - frames each caption is static.
• transition_length (default 5) - frames to morph into the next caption.
• end_padding_frames (default 10) - tail pad so the loop back to the first caption isn't abrupt.

Installing it

Same install as every node in this pack - ComfyUI Manager, search ComfyUI-FrameFX, install, restart. Or the manual route:

cd ComfyUI/custom_nodes
git clone https://github.com/mgfxer/ComfyUI-FrameFX

No requirements.txt, no model downloads. It's pure string processing - the whole node is about 40 lines.

Where people get burned

Delimiter confusion is the classic mistake, and it's symmetric with the pack's other travel node. This node splits on newlines; its Florence sibling splits on .,. Paste a Florence-2 caption stream (which comes back as "tag., tag., tag., ...") into this node and the entire line gets treated as one caption - one giant hold, no meaningful transitions. Match the node to the captioner: BLIP goes here, Florence goes to the Florence Prompt Travel Helper. And if formatted_prompts comes back empty, you fed it an empty or whitespace-only string - it returns "" rather than erroring, so the failure is silent and easy to miss.