Video filter 300 s source cap: trim a long clip first, then filter

Sume video filter rejects sources over 300 seconds while trim and detach take 1800. The output_duration_exceeded error, and a trim then filter order that fits.

4 min readSume
All posts

Sume video filter works on clips up to 300 seconds. A longer source fails in the worker with output_duration_exceeded. Video trim and audio detach are more generous: both accept sources up to 1800 seconds, with a 900-second output cap. The caps come from the contract, as the video filter docs and video trim docs quote them, read 2026-10-05.

The 300 second ceiling is described as the compose clip ceiling, one shot rather than a show. If you have a 12-minute recording and want it dimmed or cropped, trim a part out first.

Trim, then filter

Because every step reads a media.sume.com file and returns a new artifact, you can chain them: the trim result video_url goes straight into the filter request.

  • Submit video-trim with start and duration of 300 or less. Use precision: "exact" if the next step is a filter.
  • Poll GET /v1/jobs/:id/result, and read video_url from the trim result.
  • Submit video-filter with that URL and your ops.

Cost of the chain

Public rates from the Sume docs, read 2026-10-05
StepRateSource cap
Video trim$0.02 per job1800 s
Video filter$0.02 per encode300 s
Filter checkFreen/a

Two jobs cost $0.04 in total, and the intermediate trim file is a normal artifact you can reuse. Neither job calls a model, since both run only worker ffmpeg. For the live prices, GET /v1/catalog is the source of truth.

Sources

Related posts

More in Media tools

All Media tools posts

Written by Sume