OpenKatana · Import media:
OpenKatana_import_media brings source media into an OpenKatana project so you can use it in later editing and rendering steps. It supports importing media as well as preparing a trimmed or resized video excerpt or extracting its audio, while leaving the original source unchanged. This makes it useful for turning a long recording into a manageable creative asset without modifying your original footage. The node accesses OpenKatana’s import tool through a text-based tool interface rather than direct image, video, or audio sockets. For efficient workflows, inspect your source first and import only the section you need. Media-rights records help document provenance, but they do not establish legal permission, and HDR footage or rotated footage requires explicit conformance rather than assuming the import will automatically correct it.
OpenKatana · Import media Input Parameters:
project_id
A required STRING identifying the OpenKatana project targeted by the import. Use the intended project identifier consistently across your import, editing, and rendering steps so that your workflow operates on the same project. The node passes this value into its tool-argument preparation process before calling OpenKatana. The provided interface does not specify a default value, allowed options, length limits, or formatting restrictions. In particular, the default shown for the separate “OpenKatana · Import media” node should not be assumed to apply to this tool node.
arguments
A required STRING supplying the import tool’s arguments as a JSON object written as text. This is where you describe the source and any supported import adjustments; these settings are entries inside this string, not additional node sockets. The underlying import method accepts a required source string, plus rights with a default of "review_pending", start with a default of 0, duration with a default of None, max_width with a default of None, and audio_only with a default of False. For example, {"source": "/path/to/clip.mp4", "start": 0, "duration": 3, "max_width": 1280, "audio_only": false} describes a short, width-limited import rather than requesting an unspecified-length import. Replace the example path with a source accessible to your OpenKatana environment. The node interface specifies no default string, length range, or selectable options for arguments, and the supplied import signature does not establish numeric limits for its nested settings. JSON uses lowercase true, false, and null, even though the Python method uses True, False, and None.
after
An optional STRING accepted by the tool wrapper. Its execution-method default is None when omitted, and no minimum, maximum, selectable options, or default text is specified. The shown execution code accepts this value but does not reference it when constructing the import arguments or invoking the tool, so the supplied source does not establish any direct effect on the imported media or returned result. Leave it unconnected unless your surrounding workflow requires this connection; do not treat it as an import setting or assume it changes trimming, resizing, or audio extraction.
OpenKatana · Import media Output Parameters:
result_json
A STRING containing the import tool’s response in the wrapper’s JSON response format. This is the node’s only output and is the place to inspect the information returned by OpenKatana about the import. The supplied source does not show the import response schema, so specific field names, asset identifiers, status fields, or error structures cannot be guaranteed from this context alone. Inspect the actual response before extracting information for later steps. Unlike the separate media-import node described elsewhere in the context, this tool node does not expose dedicated media_id or music_asset_id sockets; do not assume the entire JSON response can be used directly wherever an individual asset identifier is required.
OpenKatana · Import media Usage Tips:
- Start with a short excerpt by including
"start": 0and"duration": 3inarguments. The import method explicitly recommends inspecting the source first and avoiding unnecessary extraction of an entire long video. - Use
max_widthinsideargumentswhen you need a resized video excerpt. For example,"max_width": 1280requests a width limit suitable for a lighter working asset; no supported minimum or maximum is documented in the supplied implementation. - Set
"audio_only": trueinsideargumentswhen you want the source’s audio rather than a video excerpt. You still need to supply the source; this node has no direct AUDIO input. - Keep
argumentsvalid JSON: use double quotes around keys and text, lowercase Boolean values, and no trailing commas. For a minimal request, begin with{"source": "/path/to/clip.mp4"}and add adjustments after the basic import succeeds. - Record rights information accurately using the nested
rightssetting. The import method defaults to"review_pending"; changing this record is not a substitute for checking that you have permission to use the material. - Use the same
project_idin related project operations, and inspectresult_jsonbefore passing returned information downstream. A JSON response and an individual media identifier are not interchangeable. - Do not copy the IMAGE, VIDEO, AUDIO, or
fpssocket configuration from the separate “OpenKatana · Import media” node. This node exposes onlyproject_id,arguments, andafter; the supplied standard import method also has nofpsargument. - Treat HDR import and batch import as separate operations. Their methods appear in the context, but their specialized settings are not established as supported arguments of this node’s standard import operation.
OpenKatana · Import media Common Errors and Solutions:
unexpected inputs: ...
- Explanation: This is an explicit error pattern in the shown wrapper. It occurs when execution receives keyword inputs outside the wrapper’s declared typed fields. A common integration mistake is supplying settings such as
sourceordurationas extra node inputs rather than placing them insidearguments. - Solution: Use only the three documented node inputs. Put supported import settings inside the JSON object supplied through
arguments, and remove unsupported sockets or keyword fields from custom workflow calls.
Invalid JSON in arguments — possible validation failure; exact message not shown
- Explanation: Malformed argument text can prevent the request from being prepared correctly. Typical mistakes include single-quoted strings, trailing commas, unquoted paths, or Python-style
TrueandFalse. The supplied code does not show the exact parser error. - Solution: Start with a small valid object such as
{"source": "/path/to/clip.mp4"}. Use double quotes for text and lowercasetrueorfalsefor Boolean settings, then add one setting at a time.
Missing source — possible import failure; exact message not shown
- Explanation: The underlying import method requires
sourceand provides no default for it. Supplying a project identifier alone does not tell OpenKatana which media to import. - Solution: Include a
sourcestring insideargumentsand confirm that it identifies the intended media in a form your OpenKatana environment supports.
Source cannot be accessed — possible import failure; exact message not shown
- Explanation: An import may fail if the source is missing, its location is incorrect, or the process performing the import cannot read it. A path available on your own computer is not necessarily available in the environment running OpenKatana.
- Solution: Check the source location, confirm that the file exists in the importing environment, and verify read permissions. Retry with a known accessible source before investigating optional import settings.
Unsupported import argument — possible tool-call failure; exact message not shown
- Explanation: The standard import signature does not include parameters such as
fps,source_color,peak_nits, orexcerpts. Some of these belong to separate methods in the supplied context, and including them here may cause argument validation or execution to fail. - Solution: Limit nested settings to those documented for the standard import method:
source,rights,start,duration,max_width, andaudio_only. Use the appropriate separate operation for HDR-specific or batch-import controls.
Incorrect argument value type — possible validation or processing failure; exact message not shown
- Explanation: Import settings have expected types:
sourceandrightsare strings,startanddurationare numeric,max_widthis an integer when supplied, andaudio_onlyis Boolean. Quoting every value can turn numbers and Boolean settings into text. - Solution: Write numeric and Boolean settings without quotes, for example
{"source": "/path/to/clip.mp4", "duration": 3, "max_width": 1280, "audio_only": false}. Omit optional settings you do not need rather than supplying empty strings.
JSON response used as a media identifier — downstream connection problem; exact message not shown
- Explanation: The node returns a response string, not a dedicated media-identifier output. Passing the complete response into a later field that expects one identifier can cause downstream processing to fail.
- Solution: Inspect
result_json, identify the relevant value in the actual response, and extract it before supplying it to a downstream identifier field. Do not assume a response field name that has not been confirmed.
