OpenKatana · Assemble render clips:
OpenKatana_assemble_render_clips exposes OpenKatana’s assemble_render_clips tool as a ComfyUI workflow node, allowing you to request a clip-assembly operation through OpenKatana’s project-based tool system. Its role is to connect a visual ComfyUI workflow to the corresponding OpenKatana operation: it prepares the supplied arguments, calls the tool, and returns the tool’s response. This gives you a way to include the operation alongside other project-processing steps without writing the tool invocation yourself. The supplied source shows the node’s calling mechanism but does not include the implementation or signature of assemble_render_clips itself, so its precise assembly behavior, rendering settings, supported media, and generated files cannot be established from this context.
OpenKatana · Assemble render clips Input Parameters:
project_id
A required STRING identifying the OpenKatana project for the operation. The node passes this value to its argument-preparation helper together with the operation name and the supplied arguments, allowing the request to be associated with a project. Use the identifier supplied by your OpenKatana project-management workflow; the provided code does not establish that a project name or folder path can be substituted for it. No default value, length limits, or list of accepted identifiers is shown in the authoritative interface. Selecting the correct project matters because the request is prepared using this value, although the exact project lookup and validation rules are not included.
arguments
A required STRING containing the arguments to prepare for the assemble_render_clips tool call. The node processes this text through its argument-preparation helpers before invoking the tool; it does not send the text directly to a renderer. Use the argument format and fields documented by the installed OpenKatana tool, rather than adding separate node inputs for settings that do not appear in this interface. The provided source does not show the parser, the tool’s argument schema, any default text, or permitted field values, so a verified JSON example, required argument list, or numeric range cannot be supplied. The contents of this parameter determine the tool request, but specific effects such as clip ordering, output destination, or rendering quality are not documented in the supplied implementation.
after
An optional STRING accepted by the node’s execution method, with a Python default of None when omitted. In the shown method, this value is not read, merged into the tool arguments, or forwarded to the tool invocation. Consequently, the supplied implementation does not support treating its contents as a timing setting, clip position, or assembly instruction. A connection may provide a workflow dependency according to ComfyUI’s execution behavior, but no additional ordering logic is implemented in the displayed method. No string default, allowed values, or minimum and maximum lengths are specified; leave this input unconnected unless your surrounding workflow requires it.
OpenKatana · Assemble render clips Output Parameters:
result_json
The node’s only output, a STRING carrying the response produced by the OpenKatana tool call through the shared response helper. It is the result-reporting connection for this operation, rather than a declared ComfyUI IMAGE, video, or frame-sequence output. Inspect it to understand what the tool returned before continuing to later workflow steps. Although its name indicates a JSON-oriented response, the supplied code does not include the response helper or the tool’s return schema, so specific keys, file paths, success flags, and error fields cannot be guaranteed. If you need to consume the result automatically, first verify its actual structure in your installed OpenKatana version.
OpenKatana · Assemble render clips Usage Tips:
- Confirm the installed
assemble_render_clipstool’s argument documentation before configuringarguments. The surrounding snippets describe other OpenKatana operations and do not establish which settings this tool accepts. - Use a known, valid
project_idfrom your project workflow. Do not assume that entering a media filename or a project directory selects the same project. - Keep operation settings inside
argumentsusing the tool’s supported format. This node exposes no separate inputs for frame rate, resolution, clip selection, or output location. - Start with the smallest valid request supported by the tool, then inspect
result_jsonbefore building a larger workflow. This helps you establish the actual response structure without relying on undocumented field names. - Leave
afterunconnected unless you need a workflow dependency. Its text is not forwarded to the tool, so it cannot configure where clips are placed or how they are rendered. - Do not apply the supplied SAM2, matte, retiming, or recipe settings to this node without confirming support in the assembly tool. Those settings belong to other code paths and are not verified configuration options here.
OpenKatana · Assemble render clips Common Errors and Solutions:
unexpected inputs: …
- Explanation: This is the explicit error format shown in the node’s execution code. It occurs when additional keyword inputs are supplied that are not recognized by the node’s typed input definitions. A normal node using the authoritative interface should expose only
project_id,arguments, andafter. - Solution: Remove unsupported inputs from custom API calls or modified workflows. Put supported tool settings into
argumentsusing the documented tool schema rather than inventing new node sockets.
Argument preparation or validation fails
- Explanation: The node prepares the request before calling the tool. A failure at this stage can prevent the assembly operation from starting. The argument-preparation implementations are not supplied, so the exact error text and validation rules cannot be quoted.
- Solution: Check
argumentsagainst the installed tool’s documented format and required fields. If that format is JSON, check quotation marks, commas, and brackets. Remove fields copied from unrelated OpenKatana operations unless the assembly tool explicitly supports them.
Project or tool invocation fails
- Explanation: The node delegates execution to OpenKatana’s shared tool-calling mechanism. An unavailable tool or a project identifier that the underlying system cannot resolve may therefore prevent the request from completing, but the supplied source does not show the corresponding error messages.
- Solution: Verify that your OpenKatana installation exposes
assemble_render_clipsand thatproject_idmatches an accessible project. Inspect the returned response and execution logs for the actual failure before changing unrelated rendering or analysis settings.
No direct image or video output is available
- Explanation: This interface declares only a STRING output. A workflow expecting an IMAGE or other media connection cannot treat
result_jsonas rendered frames, even if the underlying operation produces files. - Solution: Inspect the response for documented result information. If the tool reports generated media paths, use an appropriate loading node for that media rather than connecting the response string directly to an image-processing input.
Changing after does not change assembly behavior
- Explanation: This is a behavior mismatch rather than a documented exception. The displayed execution method accepts
afterbut does not use its contents when preparing or invoking the operation. - Solution: Configure assembly behavior through supported fields in
arguments. Useafteronly as a workflow dependency where appropriate, not as a clip-order or timing control.
