Analysis and edit lists

The analysis and edit list tools read existing recordings and turn them into structured data or finished cuts. video_analysis and video_audit break a video down scene by scene so it can be re-created, silence_detect and audio_sync measure recordings, and plan_edit and apply_edl plan and render cuts from a transcript. Every tool needs the workflows:execute permission and returns a job id.

video_analysis

Analyzes a video into a scene-by-scene breakdown built for AI re-creation. It works like the Video Analysis node.

• Scenes are cut at natural boundaries and last at most 8 seconds, one image or video generation per scene.
• visualResolved is a self-contained, prompt-ready description of each scene. It is the field that later steps read.
• Each scene also has a shot type, a camera movement, and a list of audio layers. Speech is quoted word for word, music and sound effects are described so they can be generated, and an empty list means silence.
• Slots are the people, objects and places that recur, so you can re-cast them with your own characters.

Permission: workflows:execute. Credits: by tier and video length, in the table below.

Returns: a job id. The analysis, meta, slots and scenes, is in the job's output_data.

The price depends on the tier and on the length bucket, the smallest of 60, 180, 360 or 600 seconds that fits the video:

The tool's own description always carries the current prices. If this table and the tool disagree, the tool is right.

video_audit

Watches a video again against its analysis and fixes what is wrong. Every correction is applied under checks and reported, and what could not be fixed is flagged, not changed. It works like the AI Audit node.

Permission: workflows:execute. Credits: by length, and cheaper when you pass an analysis.

Returns: a job id. The job's output_data holds the report: what was checked, what changed and what was left open.

silence_detect

Finds the silent ranges in a recording, from its audio only: no transcript and no pictures. It works like the Silence Detect node.

Permission: workflows:execute. Credits: 10.

Returns: a job id. The result is output_data.json, { ranges, durationMs }. Pass that object, not the whole output_data, as the silence of plan_edit, or use ranges to write an edit list by hand.

audio_sync

Measures how far apart the clocks of 2 to 6 recordings of one conversation are, such as camera files and a main microphone, by comparing their audio. It works like the Audio Sync node.

Permission: workflows:execute. Credits: 10 for each recording aligned to the reference, so 10 times the number of sources minus one.

Returns: a job id. The result is output_data.json: { reference, offsets, notes }, where each offset has sourceId, offsetMs, confidence and driftMsPerHour. A time on the reference clock is the time in the source plus offsetMs. Low confidence and clock drift are reported in notes, never corrected.

plan_edit

Turns a timed transcript into an edit decision list for a recording. It reads the transcript, never the pictures. It works like the Edit Plan node.

Permission: workflows:execute. Credits: from 30 to 1,480, by the recording's length, the mode and the tier. Nodaro Cloud only.

Returns: a job id. The plan is in the job's output_data, ready for apply_edl.

apply_edl

Renders an edit decision list into a finished cut. It works like the Apply EDL node, which also gives the price per minute.

Permission: workflows:execute. Credits: priced per minute of rendered output.

A render can produce at most 180 minutes. A malformed list, or one that is too long, is refused before anything runs, with the segment and the rule it breaks.

Returns: a job id. The rendered file is the job's result.

Edit a recording from its transcript

The podcast-editing recipe guides an assistant through the same steps; see Content recipes. For several cameras and a separate microphone, run audio_sync first and pass each source's offset_ms to plan_edit.