OpenKatana · Make edit:
OpenKatanaMakeEdit creates and saves a preset-based video edit from media already imported into an OpenKatana project. Rather than requiring you to arrange a timeline manually, it uses a selected editing recipe to build the timeline, providing a convenient starting point for a short creative sequence. It supports several preset families and can work with multiple imported media items, with a music option for music-oriented editing. The node checks for an existing timeline before making changes and requires explicit permission to replace it, helping protect work you have already saved. Its purpose is to build and save an editable timeline, not to render or export a finished video.
OpenKatana · Make edit Input Parameters:
project_id
A required STRING identifying the OpenKatana project where the edit will be created and saved. The node retrieves this project's current timeline and revision before building the new edit, then saves the result back to the same project. Use the identifier of a project available in your OpenKatana setup; this node does not explicitly create a project. The default is my-film. No list of allowed identifiers or string-length limits is defined in the node interface.
media_id
A required STRING connection containing the identifier of an imported media item, rather than a file path or the media content itself. This item is placed first in the collection of assets passed to the editing recipe, followed by any additional media you supply. The interface requires a connection and provides no default value or length limits. An empty string is ignored, allowing an import node with no selected media to contribute nothing; if additional media IDs are supplied, the edit can still proceed using those. If all supplied media IDs are empty, the node skips edit creation.
preset
A required selection defining which editing recipe builds your timeline. The available options are ramp-freeze, travel-diary, beat-montage, split-collage, and glitch-drop. The selected value is passed to OpenKatana as the recipe family, so it determines the editing approach rather than merely naming the result. The node description recommends choosing beat-montage with music or choosing a silent preset. The supplied class does not show the internal construction of these recipes, so exact effects, transitions, clip-selection rules, and music synchronization behavior cannot be specified from this code alone. No separate default is explicitly declared; ramp-freeze is the first listed option.
seconds
A required FLOAT setting the requested edit duration in seconds. It is passed to the recipe builder to control the length of the generated timeline. The default is 6, the minimum is 0.5, and the maximum is 600. For example, 6 requests a six-second edit, while 30 requests a thirty-second edit. This is a duration request for the recipe, not a command to render that many seconds of video; handling of source clips that are shorter than the requested duration belongs to the recipe implementation and is not shown here.
width
A required INT specifying the requested timeline frame width in pixels. Together with height, it establishes the intended frame dimensions and aspect ratio for the generated edit. The default is 1280, the minimum is 64, and the maximum is 3840, with an interface adjustment step of 2. For example, a width of 1280 combined with a height of 720 defines a landscape 16:9 frame. The value is passed to the recipe builder; the supplied node code does not specify how each preset scales, crops, or positions source media within that frame.
height
A required INT specifying the requested timeline frame height in pixels. It works with width to determine whether your edit uses a landscape, portrait, or square frame. The default is 720, the minimum is 64, and the maximum is 2160, with an interface adjustment step of 2. For example, setting width to 1080 and height to 1920 requests a portrait 9:16 frame, while equal width and height values request a square frame. As with width, the recipe determines how individual media items are fitted into the chosen dimensions.
fps
A required FLOAT setting the requested timeline frame rate, measured in frames per second. The recipe builder receives this value as part of the timeline settings. The default is 24, the minimum is 1, and the maximum is 120. A setting of 24 requests a timeline with 24 frames per second, while 30 or 60 can suit workflows that use those frame rates. This setting does not itself perform frame interpolation or guarantee additional motion detail beyond what exists in your source media.
replace_existing
A required BOOLEAN controlling whether the node may replace a timeline already saved in the selected project. The default is False, and the available values are False and True. When False, the node raises an error if the project already has a timeline, preventing an accidental overwrite. When True, it allows a newly generated timeline to be saved in place of the existing one. This is permission to replace the timeline, not an instruction to append clips or merge the new recipe with the previous edit.
music_asset_id
An optional STRING connection supplying an imported music asset identifier to the recipe builder. The node description specifically recommends music when choosing beat-montage. Connect the identifier of an available imported audio asset rather than entering a local audio file path. The interface requires a connection when this input is used and declares no widget default; when omitted, execution uses an empty string and passes None to the recipe builder. No length limits are specified. Whether a particular preset requires music or how it incorporates that music is handled by the recipe implementation, not validated in this node class.
extra_media_ids
An optional STRING supplying additional imported media identifiers beyond media_id. The default is [], meaning no additional media. You can provide a JSON list of strings, such as ["media_002", "media_003"], or one plain media identifier, such as media_002, including an identifier connected from an import node. The node trims surrounding whitespace, parses text beginning with [ as JSON, and otherwise treats nonempty text as one identifier. A parsed list must contain only strings, and empty-string entries are excluded from the assets sent to the recipe builder. Additional IDs are passed after the primary media ID in their supplied order, although the recipe determines their final timeline arrangement. No maximum list size or string length is declared.
OpenKatana · Make edit Output Parameters:
result_json
A STRING containing the OpenKatana response for the edit-building and saving operation. On successful execution, the node combines the recipe builder's result with the timeline-saving response and includes project_id so the response identifies the affected project. The recipe result contains a timeline entry, which the node uses when saving; the supplied code does not enumerate all other response fields or define the exact serialized response layout. Treat this output as structured result information for inspection or downstream processing, not as rendered video frames or a video file path. If no nonempty media IDs are supplied, the node returns a skipped response with the message No media imported; no edit made. instead of creating a timeline.
OpenKatana · Make edit Usage Tips:
- Import your media first and connect its media identifier to
media_id. An identifier refers to an asset already known to OpenKatana; a file path is not a substitute for that identifier. - Start with the default
6seconds,1280×720, and24fps to test recipe creation before committing to a longer timeline. This keeps your initial review focused on whether the selected recipe suits your material. - For a music-oriented edit, select
beat-montageand connect an imported music identifier tomusic_asset_id. For a silent workflow, choose a silent preset as recommended by the node description rather than assuming the beat-based recipe will work without audio. - Use
extra_media_idsto supply several imported assets in one edit. Enter a valid JSON list such as["media_002", "media_003"]; a comma-separated string such asmedia_002, media_003is treated as one identifier, not two. - Choose dimensions for your intended presentation:
1280×720for landscape,1080×1920for portrait, or1080×1080for square. Inspect the resulting timeline because the node interface does not define each preset's crop or layout behavior. - Keep
replace_existingset toFalsewhile experimenting with projects containing work you want to preserve. If you deliberately regenerate an edit, verify the project identifier before enabling replacement. - Remember that running the node again against a project with a saved timeline requires
replace_existing=True. This applies even if the existing timeline was created by an earlier run of the same node. - Use a separate rendering or export step after saving the timeline.
result_jsonreports the operation's result; it is not the finished movie.
OpenKatana · Make edit Common Errors and Solutions:
Project already has an edit; choose another project or enable replace_existing
- Explanation: The selected project has a timeline, and
replace_existingisFalse. The node stops before building a replacement to protect the saved edit. - Solution: Select another available project or enable
replace_existingif you intentionally want to replace the current timeline. Preserve any work you need before allowing replacement.
extra_media_ids must be a JSON list of media IDs or one media ID
- Explanation: The additional-media value parsed as a list but contains an entry that is not a string, such as
["media_002", 3]. The node explicitly checks that every parsed list entry is a string. - Solution: Supply a list containing only quoted media identifiers, such as
["media_002", "media_003"], or provide one plain identifier. Use[]when you do not need additional media.
Invalid JSON in extra_media_ids
- Explanation: Text beginning with
[is processed as JSON. Missing closing brackets, trailing commas, unquoted identifiers, or single quotes can cause a JSON parsing error. The exact error text depends on the malformed input and may include messages such asExpecting valueorExpecting ',' delimiter. - Solution: Use valid JSON with double-quoted strings, such as
["media_002", "media_003"]. For one identifier, you can avoid JSON syntax entirely by entering justmedia_002.
No media imported; no edit made.
- Explanation: This is a skipped-operation message, not an exception. After removing empty-string IDs, the node has no media assets to pass to the recipe builder, so it does not retrieve or modify the project's timeline.
- Solution: Select media in your import node and connect its resulting identifier, or supply at least one nonempty imported media identifier through
extra_media_ids. Leavingmusic_asset_idconnected does not replace the need for media in the primary or additional media inputs.
Project or asset lookup failure
- Explanation: The node relies on OpenKatana services to retrieve the project and build an edit from asset identifiers. An unavailable project, an identifier from the wrong context, or a file path supplied where an asset ID is expected can cause a service-level failure. The exact error messages are not included in the supplied class.
- Solution: Verify that the project is available and that every media and music identifier comes from a successful import accessible to that project. Check
extra_media_idsfor accidental comma-separated text being interpreted as a single ID.
Recipe-building failure
- Explanation: The recipe builder may reject a requested combination of media, music, or settings. The node forwards those values without implementing the recipe's detailed compatibility checks, and the supplied context does not list specific recipe error messages.
- Solution: Check the reported service error, confirm that your media assets are available, and test with a single valid media item and the default duration and dimensions. If using
beat-montage, supply an imported music asset as recommended by the node description.
Timeline-saving or revision-related failure
- Explanation: The node saves the generated timeline using the project revision retrieved before recipe creation. A saving failure is possible if the project becomes unavailable or the service rejects that revision, for example after another process changes the project. The supplied code does not specify the exact save-error wording.
- Solution: Check the underlying error message, avoid editing the same project simultaneously from multiple workflows, and rerun against the current project state. If a timeline is now present, confirm whether you want to enable
replace_existingbefore retrying.
