Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > OpenKatana > OpenKatana · Build recipe

ComfyUI Node: OpenKatana · Build recipe

Class Name

OpenKatana_build_recipe

Category
OpenKatana/Tools
Author
rk0neki (Account age: 235days)
Extension
OpenKatana
Latest Updated
2026-11-05
Github Stars
0.05K

How to Install OpenKatana

Install this extension via the ComfyUI Manager by searching for OpenKatana
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter OpenKatana in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

OpenKatana · Build recipe Description

Creates editable short-form video timelines using eight built-in OpenKatana editing styles.

OpenKatana · Build recipe:

OpenKatana_build_recipe creates an editable starting-point timeline for a short-form video using one of OpenKatana’s eight built-in editing styles. Rather than requiring you to arrange every cut and effect manually, it applies a coordinated recipe to your selected media: beat_cut_punch follows a music beat grid with punch-ins and impact or riser cues; xerox_ink creates a photocopy-inspired look with accented keying, rhythmic hard cuts, and grain; mono_noir combines a noir studio look with slow push-ins, letterboxing, and a final white dip; cutout_collage introduces two-panel compositions before showing their clips full-frame; speed_ramp_freeze combines normal speed, slow motion, a freeze, and a white flash; facelock_strobe combines face-locked camera movement with a strobe burst; timed_type places typewriter-style phrases over clean shots; and glitch_hits adds glitch transitions and beat-related RGB splitting. These recipes give you a consistent creative direction while leaving the edit available for review and adjustment. The generated timeline is a draft, not an automatically saved edit or a finished video render.

OpenKatana · Build recipe Input Parameters:

project_id

A required STRING identifying the OpenKatana project in which the recipe-building operation runs. Use the identifier of the project containing the media you want to edit so that the operation can resolve the selected assets in the appropriate project context. This is an identifier, not the project’s display name unless your project system explicitly uses that name as its identifier. The supplied node interface does not specify a default value, allowed identifier format, or minimum or maximum length.

arguments

A required STRING carrying the recipe-building arguments as a JSON object. The exposed node has no separate controls for recipe selection, media selection, or canvas settings, so those settings belong inside this text rather than in additional node inputs. The underlying API accepts the required fields family and asset_ids, plus optional fields music_asset_id, text, font_family, font_file, seconds, width, height, and fps. The supported family values are beat_cut_punch, xerox_ink, mono_noir, cutout_collage, speed_ramp_freeze, facelock_strobe, timed_type, and glitch_hits; asset_ids is a list of media asset identifiers. For example, {"family":"mono_noir","asset_ids":["clip_01"],"seconds":6,"width":1080,"height":1920,"fps":30} requests a six-second portrait draft using the noir recipe. The underlying API defaults are None for music, text, and both font settings; 6 for seconds; 1080 for width; 1920 for height; and 30 for fps. These are API defaults for fields inside the JSON object, not a documented default value for the STRING input itself. The supplied interface does not specify a default string, length limits, or numeric validation ranges for this operation.

after

An optional STRING accepted by the node wrapper. In the supplied execution code, this value is not forwarded into the recipe arguments, passed to the tool invocation, or otherwise inspected, so it has no demonstrated effect on the recipe’s appearance or timing. The interface does not document a required string format, allowed options, or length limits. Its execution-method default is None when omitted; leave it unconnected unless your surrounding workflow has an established reason to supply it.

OpenKatana · Build recipe Output Parameters:

result_json

A STRING containing the JSON-formatted response produced by the OpenKatana tool invocation. This is the node’s only output, so it is where you inspect the recipe-building response and any returned draft-edit information. A timeline describes editing decisions—such as canvas settings, shot placement, effects, and audio arrangements—rather than containing rendered video pixels. Treat this output as structured text for inspection or further processing, not as a video file or a ComfyUI image batch. The supplied code shows that the tool response is passed through a response-formatting helper, but does not show the exact response envelope or guarantee specific top-level JSON keys; inspect the returned content before designing downstream parsing around particular field names. Recipe generation does not automatically save the resulting edit.

OpenKatana · Build recipe Usage Tips:

  • Start with a small, valid JSON object containing family and asset_ids. For example, use {"family":"xerox_ink","asset_ids":["clip_01","clip_02"]}, replacing the example identifiers with assets imported into your project.
  • Keep the project identifier in project_id and place recipe settings inside arguments. The node exposes only these two required inputs and the optional after input; settings such as fps are not separate node sockets.
  • For a portrait short-form draft, the underlying defaults already provide a 1080 × 1920 canvas at 30 fps for a requested six seconds. Set width, height, fps, and seconds explicitly in the JSON when you want a different format.
  • Choose beat_cut_punch when music should drive the cutting rhythm, and supply music_asset_id referencing imported audio. Its implementation requires music and audio analysis, and limits the planning duration to the shorter of the analyzed music duration and the requested duration.
  • Use xerox_ink for a photocopy-style treatment that can also work without music analysis. When analysis is available, its cut interval is calculated as four beats; otherwise, it uses an approximately 0.8-second interval.
  • Choose timed_type when text is central to your edit, and provide text in the JSON. The API also accepts font_family and font_file, but the supplied excerpts do not establish font-selection precedence or the expected text-splitting rules.
  • Prepare a clip face track before choosing facelock_strobe. The recipe is explicitly described as needing one; selecting footage that merely contains a face does not establish that tracking data is available.
  • Review the draft before saving or rendering it. Check shot choices, timing, text readability, and the intensity of flashes, strobes, and glitch effects, especially when the result will be viewed by an audience sensitive to flashing imagery.

OpenKatana · Build recipe Common Errors and Solutions:

beat_cut_punch needs music (an imported audio asset) to find the beat grid

  • Explanation: This exact error is raised when the beat-cut recipe does not have both music and the analysis needed to establish its beat grid.
  • Solution: Import an audio asset into the project and provide its identifier as music_asset_id inside arguments. If the error persists, check that the audio is accessible and that the tool can obtain its analysis, or choose another recipe.

unexpected inputs: ...

  • Explanation: The node explicitly raises this error if execution receives extra named fields that are not in its declared typed inputs. Adding recipe settings as separate execution fields can trigger this check.
  • Solution: Use only the exposed inputs project_id, arguments, and optionally after. Put settings such as family, asset_ids, and seconds inside the JSON string supplied to arguments.

Invalid JSON in arguments

  • Explanation: This is a descriptive troubleshooting label, not a confirmed exact error message from the supplied code. The argument-processing step needs a readable JSON object; single-quoted strings, trailing commas, or missing quotation marks can prevent processing before the recipe is built.
  • Solution: Use double quotes around JSON keys and string values, and supply asset identifiers in an array. Start with {"family":"mono_noir","asset_ids":["clip_01"]} and add other settings only after that succeeds.

Missing required recipe arguments

  • Explanation: The underlying API requires family and asset_ids in addition to the project identifier supplied by the node. Omitting either leaves the operation without a required recipe choice or media selection. The exact resulting error text is not shown in the supplied context.
  • Solution: Include both keys inside arguments. Use a supported recipe name and a list of identifiers for the imported media you want to use.

Unsupported recipe family

  • Explanation: The documented recipe builder supports eight specific family names. A misspelling, different capitalization, or a recipe name from another OpenKatana planning feature is not a documented option for this operation. The exact validation message is not provided.
  • Solution: Copy one of the supported values exactly: beat_cut_punch, xerox_ink, mono_noir, cutout_collage, speed_ramp_freeze, facelock_strobe, timed_type, or glitch_hits.

Project or asset cannot be resolved

  • Explanation: This describes a possible project or media lookup failure; the supplied excerpts do not show its exact error message. Incorrect identifiers, references to another project’s assets, or using a file path where an imported asset identifier is expected can prevent the operation from accessing the intended media.
  • Solution: Verify project_id and copy asset identifiers from the project’s imported assets. Use video or image assets for asset_ids and an imported audio asset for music_asset_id.

Face track unavailable for facelock_strobe

  • Explanation: The recipe documentation explicitly states that this family needs a clip face track. The supplied code does not show the exact failure message or how missing tracking data is reported.
  • Solution: Use a clip with face-tracking data already available through your OpenKatana workflow, or select a recipe that does not depend on face tracking.

OpenKatana · Build recipe Related Nodes

Go back to the extension to check out more related nodes.
OpenKatana
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

OpenKatana · Build recipe