Documentation Index
Fetch the complete documentation index at: https://docs.roughy.ai/llms.txt
Use this file to discover all available pages before exploring further.
What is a processor
Each processor takes one or more input assets, applies a single transformation, and produces one or more output assets. Processors are composed inside a pipeline by listing them as steps; a downstream step reads either the original pipeline input or a prior step’s output, depending on the processor.Cut
Produces cut decisions for video material. The cut processor runs ElevenLabs speech-to-text on the input, groups the resulting segments, sends them to Claude for cut analysis, and emits an SRT file describing which spans to keep and which to drop.| Property | Value |
|---|---|
| Input | Original pipeline input (AUDIO or VIDEO). |
| Output | CUT_FILE asset (SRT). |
| Pricing | Per second of input audio. |
| Queue | I/O. |
Render
Applies cut decisions to the original media and produces a flattened MP4. The render processor reads the original pipeline input and the SRT output from a prior cut step, then runs ffmpeg to trim, concat, and encode the result under a render preset.| Property | Value |
|---|---|
| Input | Original pipeline input + SRT from a prior step. |
| Output | RENDERED_VIDEO asset (MP4). |
| Pricing | Per second of output video. |
| Queue | CPU. |
web_1080p, web_720p, social_vertical_1080p.
cut_step_order is the zero-based index of the cut step whose SRT
should drive the render — usually 0 if cut is the first step.
Composing them
The typical two-step pipeline iscut → render:
cut alone if you only want the SRT — useful when
the downstream tool is an NLE rather than Roughy’s renderer.