OpenKatana · Assemble blender clips:
OpenKatana_assemble_blender_clips provides a ComfyUI interface to OpenKatana’s Blender clip-assembly tool, allowing you to request a project operation from a node-based workflow rather than calling the tool directly. Its role is to pass a project-scoped assembly request to OpenKatana and return the tool’s response in a text-based format. The visible implementation prepares the supplied arguments and dispatches the request through OpenKatana’s tool-calling system; it does not perform the assembly inside the node itself. This makes the node a bridge between your ComfyUI workflow and the underlying project tool. The supplied context does not include the assembly tool’s implementation or argument schema, so it does not establish how clips are arranged, which Blender resources are required, or whether assembly includes rendering, transitions, or other editing operations.
OpenKatana · Assemble blender clips Input Parameters:
project_id
A required STRING identifying the OpenKatana project for the request. The node passes this value into its argument-preparation step together with the selected tool and the supplied arguments, providing the project context for the operation. Use the identifier associated with the project you intend to work on rather than assuming that a project name or folder path is interchangeable with it. The provided source does not specify the identifier’s format, permitted values, length limits, or default value. No minimum, maximum, or selectable options are shown.
arguments
A required STRING containing the arguments to prepare for the assembly-tool call. This is the node’s tool-specific configuration channel: the visible interface exposes no separate controls for clip selection, arrangement, or Blender settings. The string is processed by OpenKatana’s argument-preparation helpers before the tool is invoked, so its contents must follow the format and parameter schema expected by the installed tool. The supplied code does not show those helpers’ parsing rules or the assembly tool’s accepted argument fields; consequently, no particular JSON structure, field names, defaults, ranges, or options can be documented reliably from this context. Obtain the assembly tool’s schema before constructing the request, and do not assume that an empty string or an empty object is a valid configuration.
after
An optional STRING accepted by the execution method, with a Python default of None when omitted. The shown method does not read this value, merge it into the tool arguments, or explicitly pass it to the tool invocation. It therefore provides no visible control over clip order, assembly settings, or the returned response. Although an optional connection may serve a workflow-level role elsewhere, that behavior is not established by the supplied code, so do not treat this parameter as a confirmed scheduling or success-checking mechanism. No string default in the interface, minimum or maximum length, or selectable options are shown.
OpenKatana · Assemble blender clips Output Parameters:
result_json
A STRING containing the response produced after the OpenKatana tool invocation is passed through the node’s response-formatting helper. This is the node’s single output and the place to inspect the returned tool information before continuing your workflow. Its name indicates a JSON-formatted result, but the provided source does not define the response structure, its fields, or the formatting helper’s behavior. Do not assume that it contains an image batch, video, Blender file, output path, or a particular success flag. When consuming it downstream, inspect the actual returned structure and extract only fields confirmed by the installed tool’s response.
OpenKatana · Assemble blender clips Usage Tips:
- Confirm the installed assembly tool’s argument schema before filling in
arguments. The supplied interface does not establish any supported clip, timing, rendering, or output-location settings. - Use the
project_idfor the project containing the material you intend to assemble. Keep the same project context across related OpenKatana operations to avoid sending a request to the wrong project. - If the tool expects JSON in
arguments, validate that JSON before running the node: use double-quoted property names and strings, and remove trailing commas. JSON parsing requirements are not shown in the supplied implementation, so first confirm the expected format. - Configure tool-specific settings through the documented contents of
arguments, rather than adding new node inputs. The wrapper explicitly rejects unrecognized extra input fields. - Inspect
result_jsonafter an initial test run before connecting downstream processing. Confirm the actual response fields instead of assuming the output is a media file or that receiving text proves assembly succeeded. - Leave
afterunconnected unless your installed OpenKatana workflow documents a reason to use it. The visible execution method does not use its value to configure the assembly operation. - Do not apply settings or error guidance from the supplied masking, retiming, or sequence-processing snippets automatically. Those snippets describe other operations and do not establish assembly-tool requirements.
OpenKatana · Assemble blender clips Common Errors and Solutions:
unexpected inputs: ...
- Explanation: This is the explicit error template shown in the node wrapper. It occurs when execution receives extra named fields that are not included in the tool’s recognized typed inputs. The error lists the unexpected names.
- Solution: Use only the exposed inputs:
project_id,arguments, and optionalafter. Put tool-specific settings insideargumentsonly when the assembly tool’s schema documents those settings.
Argument preparation or validation failure — exact message not provided
- Explanation: The node prepares arguments before calling the tool. A failure at this stage may indicate that the supplied text does not match the expected argument format or schema; however, the helper implementation and its exact error messages are not included.
- Solution: Check the complete reported error against the installed tool’s argument documentation. Correct the text format, supply any documented required fields, and remove unsupported fields rather than guessing parameter names.
Project-related tool failure — exact message not provided
- Explanation: The request includes a project identifier, but the supplied context does not show how the assembly tool validates or opens a project. A reported project error must therefore be interpreted from the actual tool response, not from a confirmed error string in this excerpt.
- Solution: Verify that the project exists and that you copied its identifier correctly. If the response identifies a missing project resource, check that resource in the intended project before retrying.
Assembly-tool execution failure — exact message not provided
- Explanation: The wrapper delegates the operation to another tool, whose implementation is absent from the supplied context. Blender-specific requirements, resource checks, and assembly failure messages cannot be established from this node class alone.
- Solution: Read the full returned error and the OpenKatana or ComfyUI execution log. Follow the specific requirement reported there, and verify Blender configuration or media availability only when the error indicates those are involved.
Downstream result parsing failure — exact message not provided
- Explanation: A downstream node may fail if it expects media data or assumes particular JSON fields that are not present in
result_json. The documented output type is STRING, and its detailed response schema is not supplied. - Solution: Preview the output text first. If it contains JSON, parse it and use the fields actually returned; if it reports a tool failure, resolve that failure before attempting to load any referenced output.
