stitch

Places multiple files end-to-end on a timeline level.

When to use

Use stitch when you have several pre-cut source files that should play back-to-back. Its sources input reads files only, so files that still need cutting are trimmed by their own trim steps rather than fed through this one.

In the editor

Add it from the Library (Utility group), or with + add step and a search for stitch.

There are no parameters. Under Inputs, add one entry with the id sources and choose file, naming the files you want joined. They play in the order you list them, so the order of that list is the order of the finished sequence. Set Output Level to the level the joined clips should sit on, usually main.

In the run timeline you see one clip per file, laid end to end with no gaps. This step only reads files, not the output of other steps, so a file that needs cutting down first is a job for trim steps placing their own clips rather than for stitch.

YAML Example

- id: concat_clips
  processor: stitch
  input:
    - id: sources
      files:
        - footage-a
        - footage-b
        - footage-c
  output:
    timeline: main

Inputs

Params

This processor has no configurable parameters.

Output

EditDecisions: one edit decision per source file, placed sequentially.

Notes

• Files are placed in the order listed under files:. When the input is a glob, that means filename order.
• Each file's full duration is used, and each clip starts where the previous one ends. Run trim on individual files first if you need to cut them before stitching.
• The duration of every file is read up front, so the step fails if one of them cannot be read.
• Clips keep their own format. Stitching sources that differ in resolution or frame rate works, but the result changes size or cadence at each join.