Nodes/playbook-nodes/Playbook Beauty Render Pass Sequence
ComfyUI Node

Playbook Beauty Render Pass Sequence

Your animation's beauty frames, unzipped into a batch

By playbook3d·Created 2 years ago·Updated about a year ago· 21
Playbook Beauty Render Pass Sequence
    • Images
    api_key
    run_id

    Playbook Beauty Sequence is the animation version of Playbook Beauty. Where the single node grabs one finished render, this one fetches a whole zip of beauty frames and hands you a batched IMAGE tensor, ready for frame-by-frame processing. If you're retexturing an animated scene - or feeding an image-to-video model a real render's frames - this is the node you start from.

    The context matters: Playbook3D is a cloud 3D render service that streams scene data into ComfyUI. Back when it launched in open beta (late 2024), someone asked on Reddit whether it worked for animation, and the answer was basically "give us two weeks." This sequence node is that promise delivered. A single beauty frame is nice; a zip of frames is a workflow.

    How it works

    Inputs are exactly two: api_key (required) and run_id (optional). No default-image fallback here - the sequence nodes are less forgiving than their single-frame siblings.

    The mechanism mirrors Playbook Beauty: exchange api_key for a user token at accounts.playbook3d.com/token-wrapper/get-tokens/<key>, then request download URLs (with or without run_id). The difference is the key it expects in the response: beauty_zip. The node downloads that zip, unzips it into a temp directory, sorts the image files by name, decodes each to a float tensor, and stacks them into one [frames, height, width, channels] batch. Output Images is that batch - feed it straight into a video-frame node or a per-frame loop.

    Because the frames are sorted by filename, naming matters on the render side: zero-padded sequence names (frame_0001.png, frame_0002.png…) come out in order; a mix like frame_1.png and frame_10.png sorts lexically, and you'll get 10 before 2. If your footage looks out of order, that's a naming issue, not a code bug.

    Install

    Identical to the rest of the pack. ComfyUI Manager → search Playbook Nodes, or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/playbook3d/playbook3d-comfyui-nodes
    

    Restart ComfyUI. No models, no extra dependencies - zipfile, tempfile, and the usual image stack are all standard library or already in ComfyUI. You do need the Playbook3D API key from beta.playbook3d.com.

    Troubleshooting

    This node fails loudly where the single-frame versions fail quietly. A missing key raises "API Key not found or incorrect." No zip found raises "No beauty zip found for the provided parameters." - which usually means the render hasn't finished, or you gave a run_id that doesn't have a sequence uploaded. The honest advice: check your console for the exact error text; the node prints it before raising. And remember there's no default_value escape hatch here, so a failed run stops the graph. If you want graceful degradation, keep an eye on the render status in the Playbook3D web app before you hit queue.

    CategoryPlaybook 3D

    Inputs (2)

    NameTypeDefaultDescription
    api_keySTRING
    run_idoptSTRING

    Outputs (1)

    NameTypeDescription
    ImagesIMAGE