OpenKatana · Validate timeline:
OpenKatana_validate_timeline checks whether an OpenKatana timeline follows the rules expected by the timeline system, helping you catch structural and value-related problems before continuing your editing or rendering workflow. The underlying validation process converts supported authoring shorthand into a consistent internal representation, then checks the timeline’s structure and settings, including canvas dimensions, frame rate, frame count, colors, and supported effect-related sections. For example, it rejects odd-numbered canvas dimensions and requires numerical settings to stay within their supported limits. Supported authoring conveniences include time expressions, palette-based colors, and look presets, which are normalized before the contract checks are applied. This makes the node useful as a quality-control step when you create or revise an edit, although passing validation should not be treated as a guarantee of visual quality or successful rendering in every environment.
OpenKatana · Validate timeline Input Parameters:
project_id
A required STRING that supplies project context to the tool’s argument-building step. Use the identifier associated with the project you intend to validate so that the request is prepared in the correct project context. The node passes this value to its argument-preparation helper together with the tool name and the argument text; the supplied source does not show how the identifier is resolved or what happens if the project is missing. No default value, minimum or maximum length, or list of allowed identifiers is specified in the provided interface.
arguments
A required STRING containing the argument text used to prepare the validation tool’s request. This is the entry point for supplying the tool-specific request data that is not exposed as separate node inputs. The node processes this text through argument-building helpers before invoking the tool, so it must follow the format and argument schema expected by the installed OpenKatana tool. The provided source does not include that schema or the helper implementation, so it does not establish the exact timeline argument key, whether a project’s saved timeline can be selected implicitly, or the accepted text format. No default value, minimum or maximum length, or selectable options are specified; use the installed tool’s signature or documentation rather than assuming that a raw timeline object alone is the complete request.
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, combined with the tool arguments, or forwarded to the validation call. Consequently, the supplied code does not establish any effect on the validation result or timeline selection. If your surrounding OpenKatana workflow uses this socket for sequencing, follow that workflow’s documented convention; the provided implementation alone does not define such behavior. No string default, minimum or maximum length, or selectable options are shown.
OpenKatana · Validate timeline Output Parameters:
result_json
A STRING containing the tool response after it has been processed by the node’s response helper. This is the node’s only output and is the place to inspect the returned validation information. The underlying contract validator checks a timeline and returns its canonical form internally, meaning a consistent representation in which supported shorthand has been expanded; however, the supplied node code does not show whether the tool response includes that timeline, a status summary, diagnostic details, or another response structure. Read the actual returned content before relying on particular fields, and do not assume that this socket directly supplies a timeline object ready for another node. The source also does not establish whether validation failures are returned in this string or raised as execution errors.
OpenKatana · Validate timeline Usage Tips:
- Run validation after changing canvas settings, timing, clip definitions, text, or effects so you can catch contract problems before moving on to rendering.
- Use even canvas dimensions between 2 and 7680 pixels, inclusive. For example, 1920 × 1080 satisfies the shown dimension checks, while 1919 × 1080 does not.
- Keep
canvas.fpsbetween 1 and 120, inclusive, andcanvas.framesbetween 1 and 216000, inclusive. The frame count must be an integer; the shown frame-rate check does not require an integer. - If you specify
canvas.boil, use an integer between 1 and 120. The validator uses 2 when this setting is absent; that is a timeline-field default, not a node-input default. - Use supported authoring shorthand when it makes editing easier, such as palette colors or documented time expressions. Validation normalizes these forms before checking the canonical timeline, so investigate shorthand definitions as well as the resulting settings when troubleshooting.
- Start troubleshooting with a small, known-valid timeline and add optional sections incrementally. The shown validator restricts allowed fields and checks sections such as camera settings, post effects, looks, and hooks.
- Confirm the validation tool’s request schema before filling
arguments. The node interface exposes a general text field rather than documenting individual timeline request fields, so guessing argument names can introduce problems before timeline validation begins. - Treat validation as a structural check, not a preview or a save operation. Use your normal preview and save workflow afterward; the supplied node implementation does not demonstrate rendering or saving changes.
OpenKatana · Validate timeline Common Errors and Solutions:
Canvas dimensions must be even
- Explanation: This exact error is raised when a canvas width or height is an odd integer. The validator requires both dimensions to be even.
- Solution: Change the affected dimension to a nearby even number, such as changing 1919 to 1920. Keep both dimensions within the supported range of 2 to 7680.
clips must be an object
- Explanation: This exact error is raised when
clipsis present but is not an object containing named entries. A list, text value, or null value does not satisfy this check. - Solution: Store clip definitions in an object keyed by clip identifier. If your timeline does not need clip definitions, the shown validator allows this section to be omitted and uses an empty object for this check.
unexpected inputs: …
- Explanation: The node explicitly raises a
TypeErrorwith this prefix if additional execution fields are supplied that are not recognized as typed inputs. This check concerns extra execution inputs, not necessarily keys inside theargumentstext. - Solution: Use the documented sockets:
project_id,arguments, and optionalafter. If another script or integration invokes the node, remove unrecognized execution fields.
Invalid or out-of-range canvas values — exact message not shown
- Explanation: The validator checks
canvas.w,canvas.h,canvas.fps,canvas.frames, andcanvas.boilnumerically. Missing required values, nonnumeric values, values outside the supported ranges, or fractional values where integers are required can fail validation; the numerical helper’s exact error messages are not included in the supplied code. - Solution: Supply integer width and height values from 2 to 7680, a frame rate from 1 to 120, and an integer frame count from 1 to 216000. If you include
boil, use an integer from 1 to 120. Ensure width and height are also even.
Unsupported timeline or canvas field — exact message not shown
- Explanation: The validator restricts the fields allowed in the canonical timeline and canvas sections. Misspelled names or fields placed in the wrong section can fail these checks, although supported native authoring fields are normalized before this stage.
- Solution: Check spelling and placement against the installed timeline documentation. The shown canonical top-level fields are
canvas,clips,shots,text,fonts,audio,cam,post,look,specials,hooks,assets,stickers, andoverlays; canvas fields arew,h,fps,frames,bg, andboil.
Non-finite numerical value — exact message not shown
- Explanation: The validator checks the timeline for non-finite numbers before normalization. Values such as infinity or NaN do not represent usable timeline settings.
- Solution: Replace these values with ordinary finite numbers. If your timeline was generated automatically, check any calculations that divide by zero or produce undefined timing, dimensions, or effect values.
Invalid color or unresolved authoring shorthand — exact message not shown
- Explanation: Native authoring syntax is normalized before validation, and a supplied canvas background is checked as a color. An invalid color expression or shorthand that cannot be resolved may prevent validation from completing; the exact diagnostics are not shown.
- Solution: Use a documented color format, such as
#000000, and verify palette references and look names against their definitions. Temporarily replace shorthand with explicit values to help locate the problem.
Invalid tool arguments or project context — exact message not shown
- Explanation: The node prepares its request from
project_idandargumentsbefore invoking the tool. Problems at this stage may prevent the timeline validator from being reached, but the supplied source does not reveal the argument schema or project-resolution errors. - Solution: Verify the project identifier and compare the argument text with the installed validation tool’s documented signature. Distinguish request-format errors from timeline-content errors before changing your edit.
