OpenKatana · Source contact sheet:
OpenKatana_source_contact_sheet provides a visual overview of source footage by requesting a contact sheet: a collection of sampled video frames arranged in a grid. This format helps you review the appearance and progression of footage without watching every moment, making it useful for finding promising sections, comparing compositions, and planning an edit or an AI-assisted visual workflow. The supplied context identifies a contact-sheet operation with controls for the sampling interval and grid layout, which support balancing coverage against visual detail. Treat the sheet as a browsing aid rather than a complete analysis: sampled images can help you spot changes, but brief events between samples may not appear.
OpenKatana · Source contact sheet Input Parameters:
project_id
A required STRING that identifies the OpenKatana project associated with the request. The node passes this value into its argument-preparation process together with the requested tool and the supplied arguments, allowing the operation to be prepared in a project context. Use the identifier supplied by your existing OpenKatana project workflow rather than assuming that a project title or folder path is interchangeable with it. The provided code does not show project lookup, validation rules, or how a project is created. No default value, permitted identifier list, or string-length limits are available in the supplied interface.
arguments
A required STRING containing the argument text used to prepare the contact-sheet request. This is the node’s exposed way to supply operation-specific settings; the interface does not provide separate source, sampling, or layout sockets. The contextual contact-sheet function names settings for the source, output destination, start, end, step, and columns, but its signature alone does not establish the exact argument format accepted by this node, the units for sampling values, or which values the backend supplies automatically. Use the argument format documented by your installed OpenKatana tool, and, if it requires JSON, supply a valid serialized JSON object rather than ordinary descriptive text. These settings determine what footage is sampled and how the sheet is arranged once interpreted by the backend. No default string, numerical limits, or accepted options are shown in the supplied node code.
after
An optional STRING that can carry a connection from an earlier workflow step. The execution method accepts this value with a Python default of None, but its body does not read it, merge it into the arguments, or forward it to the tool call. Consequently, the supplied implementation does not use its contents to change the source footage, sampling choices, or contact-sheet layout. A connection can express a graph dependency, but you should not treat this field as a way to pass contact-sheet settings or validate a preceding operation’s success. No string default, supported value list, or length limits are shown in the interface.
OpenKatana · Source contact sheet Output Parameters:
result_json
A STRING containing the response returned through OpenKatana’s response-handling function after the contact-sheet tool is invoked. This is the node’s only output, so it should be treated as response data rather than a ComfyUI image tensor that can be connected directly to an image-preview socket. Inspect the returned text to understand the operation’s outcome and any artifact information the backend supplies. The provided code does not show the response serializer or the contact-sheet response schema, so specific success fields, file-path keys, image counts, or error fields cannot be guaranteed. If the response contains a generated-file location, use a compatible file-loading or viewing step to access that artifact.
OpenKatana · Source contact sheet Usage Tips:
- Begin with a short, known section of footage and a valid project identifier. Confirm that the tool can access the source and produce a usable response before requesting a sheet for a long clip.
- Confirm the accepted format of
argumentsin your installed OpenKatana version. The contextual helper signature is not enough to establish a complete, valid request, so avoid copying its parameter names into a payload without checking the exposed tool’s requirements. - Where the backend supports the contextual sampling controls, use a larger sampling step for a broad overview and a smaller step to inspect a short section more closely. Confirm the step’s units first; the supplied code does not establish whether it represents time, frames, or another measure.
- Where start and end controls are supported, narrow the interval around material you want to compare. This can keep the contact sheet focused and reduce the amount of unnecessary sampling.
- Where the columns control is supported, choose fewer columns when frame readability is most important and more columns when you want a compact overview. Review the resulting sheet at its intended viewing size before processing more footage.
- Use
afteronly as a workflow connection, not as a substitute forarguments. Inspect the earlier operation’s result separately when successful completion is important, because this node does not examine the contents ofafter. - Inspect
result_jsonbefore building downstream automation. Establish the actual response structure from your installation rather than assuming that every OpenKatana tool returns the same fields.
OpenKatana · Source contact sheet Common Errors and Solutions:
unexpected inputs: ...
- Explanation: This is the explicit error pattern present in the node’s execution code. It raises a
TypeErrorwhen additional keyword inputs are supplied that are not recognized by the generated tool definition. The error lists the unexpected names. - Solution: Use only the exposed inputs:
project_id,arguments, and optionalafter. Do not add source or layout sockets manually; supply operation settings through the supported argument format.
Required input missing: project_id or arguments
- Explanation: Both fields are required by the interface. Leaving either input unavailable can prevent execution during workflow validation or invocation. This heading describes a possible validation issue, not an exact error message shown in the supplied code.
- Solution: Provide a valid project identifier and an argument string in the format your installed tool expects. Check that any upstream nodes supplying these strings are connected and have executed successfully.
Arguments could not be parsed or validated
- Explanation: The node prepares arguments before invoking the tool. An incorrectly formatted string, unsupported setting, or unsuitable value may fail during that preparation or backend validation. The relevant parser implementation and exact error messages are not supplied.
- Solution: Check the installed tool’s argument specification. If it expects JSON, verify quotation marks, commas, and value types, then retry with the smallest documented request before adding optional settings.
Project or source could not be resolved
- Explanation: An incorrect project identifier or an inaccessible source can prevent a contact-sheet operation from reaching the footage it needs. The supplied excerpts do not show the lookup rules or an exact error message for this condition.
- Solution: Confirm that the project exists and that the source reference is valid in that project’s tool context. If the source is a file path, verify that it is accessible to the machine or container running OpenKatana, not merely to your local browser.
Sampling settings are rejected or the sheet contains no useful frames
- Explanation: If supported sampling settings describe an interval outside the footage or use unsuitable values, the operation may fail or produce an unhelpful result. Exact range checks, units, and empty-result behavior are not shown in the provided code.
- Solution: Confirm the source duration and documented sampling units. Test a known section within the clip, use a positive sampling step where required, and choose a valid positive column count according to the backend’s specification.
The result cannot connect directly to an image preview
- Explanation: The output is a STRING, not an IMAGE output. A response describing an image artifact is not itself decoded image data.
- Solution: Inspect
result_jsonfor the actual result structure. If it supplies a contact-sheet file location, open that file or load it with an appropriate image-loading step.
Changing after does not change the contact sheet
- Explanation: The execution body accepts
afterbut does not use its contents when preparing or invoking the tool. Changing its text therefore does not configure the contact-sheet request. - Solution: Put supported contact-sheet settings in
arguments. Keepafterfor an upstream dependency connection, and check upstream results independently when needed.
